From: alex.shi@linaro•org (Alex Shi)
To: linux-arm-kernel@lists•infradead.org
Subject: panda board es failed on cpuidle
Date: Mon, 09 Dec 2013 18:27:54 +0800 [thread overview]
Message-ID: <52A59B2A.2030702@linaro.org> (raw)
In-Reply-To: <52A594D3.4060809@linaro.org>
Add Strashko,
On 12/09/2013 06:00 PM, Daniel Lezcano wrote:
> On 12/09/2013 10:54 AM, Alex Shi wrote:
>> my panda board ES failed to boot up when I use omap2plus_defconfig +
>> CPU_IDLE.
>> Is it a known issue or I missed sth in kernel?
>>
>> CONFIG_CPU_IDLE=y
>> # CONFIG_CPU_IDLE_MULTIPLE_DRIVERS is not set
>> CONFIG_CPU_IDLE_GOV_LADDER=y
>> CONFIG_CPU_IDLE_GOV_MENU=y
>> CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED=y
>>
>>
>> kernel hang after the following output.
>>
>> 2.276641] omap_hsmmc 4809c000.mmc: pins are not configured from
>> the driver
>> [ 2.325531] pinctrl-single 4a31e040.pinmux: mux offset out of
>> range: 0x38 (0x38)
>> [ 2.333648] pinctrl-single 4a31e040.pinmux: could not add functions
>> for pinmux_wl12xx_pins 56x
>> [ 2.343231] omap-dma-engine 4a056000.dma-controller: allocating
>> channel for 60
>> [ 2.351043] omap-dma-engine 4a056000.dma-controller: allocating
>> channel for 59
>> [ 2.358917] 480d5000.mmc supply vmmc_aux not found, using dummy
>> regulator
>> [ 2.383331] hw-breakpoint: Failed to enable monitor mode on CPU 0.
>> [ 2.390411] hw-breakpoint: CPU 0 failed to disable vector catch
>
> Yes, I saw an email talking about a hang with cpuidle + omap4.
>
> The thread is http://www.spinics.net/lists/linux-omap/msg99899.html
>
> and the patch bringing the fix is
> https://patchwork.kernel.org/patch/3084521/
>
Seems the patch still is not in v3.13-rc3 kernel
Any update for this issue?
> Hope that helps.
>
> -- Daniel
>
--
Thanks
Alex
prev parent reply other threads:[~2013-12-09 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 9:54 panda board es failed on cpuidle Alex Shi
2013-12-09 10:00 ` Daniel Lezcano
2013-12-09 10:27 ` Alex Shi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A59B2A.2030702@linaro.org \
--to=alex.shi@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox