From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled
Date: Tue, 27 May 2014 17:03:59 -0400 [thread overview]
Message-ID: <5384FDBF.2050604@ti.com> (raw)
In-Reply-To: <20140527203452.GA32336@atomide.com>
On Tuesday 27 May 2014 04:34 PM, Tony Lindgren wrote:
> * Daniel Lezcano <daniel.lezcano@linaro.org> [140523 13:53]:
>> On 23 May 2014 20:32, Tony Lindgren <tony@atomide.com> wrote:
>>
>>> * Tony Lindgren <tony@atomide.com> [140523 07:45]:
>>>> * Tobias Jakobi <tjakobi@math.uni-bielefeld.de> [140519 14:19]:
>>>>>
>>>>> But even if I don't connect via WiFi at all, just boot and let me
>>> system
>>>>> run with serial console connected, after some time I get a kernel
>>> 'WARNING':
>>>>> http://www.math.uni-bielefeld.de/~tjakobi/archive/dmesg.1.log
>>>>
>>>> BTW, care to update the bugzilla page with the second warning
>>>> in this log?
>>>>
>>>> That's the WARNING: CPU: 1 PID: 0 at kernel/timer.c:1147 that's
>>>> at 238 seconds.
>>>
>>> Also, with Santosh's fix applied, can you also try disabling one
>>> or more of the idle states for cpuidle and see if that helps?
>>>
>>> Something like this patch below. If that helps with the WARNING
>>> above you're getting it narrows down the problem down quite a bit.
>>>
>>> Regards,
>>>
>>> Tony
>>>
>>> --- a/arch/arm/mach-omap2/cpuidle44xx.c
>>> +++ b/arch/arm/mach-omap2/cpuidle44xx.c
>>> @@ -44,11 +44,13 @@ static struct idle_statedata omap4_idle_data[] = {
>>> .mpu_state = PWRDM_POWER_RET,
>>> .mpu_logic_state = PWRDM_POWER_RET,
>>> },
>>> +#if 0
>>> {
>>> .cpu_state = PWRDM_POWER_OFF,
>>> .mpu_state = PWRDM_POWER_RET,
>>> .mpu_logic_state = PWRDM_POWER_OFF,
>>> },
>>> +#endif
>>>
>>
>> Hmm, I am afraid that will lead to a fault. Safer to set the state_count =
>> 2 instead.
>
> Hmm don't we have state_count = ARRAY_SIZE(omap4_idle_data) or am I
> missing something?
>
I don't think you are missing anything. The change should work.
next prev parent reply other threads:[~2014-05-27 21:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:39 [PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled Santosh Shilimkar
2014-05-14 15:22 ` Tony Lindgren
2014-05-14 19:44 ` Daniel Lezcano
2014-05-14 19:50 ` Santosh Shilimkar
2014-05-14 20:02 ` Daniel Lezcano
2014-05-14 20:56 ` Tony Lindgren
2014-05-14 23:31 ` Tony Lindgren
2014-05-16 0:13 ` Tony Lindgren
2014-05-16 0:40 ` Tony Lindgren
2014-05-14 21:18 ` Santosh Shilimkar
2014-05-15 17:03 ` Santosh Shilimkar
2014-05-15 17:50 ` Daniel Lezcano
2014-05-15 17:54 ` Santosh Shilimkar
2014-05-15 18:29 ` Santosh Shilimkar
2014-05-16 0:33 ` Alex Shi
2014-05-16 13:43 ` Santosh Shilimkar
2014-05-16 21:29 ` Tony Lindgren
2014-05-19 16:45 ` Daniel Lezcano
2014-05-19 17:23 ` Tony Lindgren
2014-05-19 17:34 ` Santosh Shilimkar
2014-05-19 17:51 ` Tony Lindgren
2014-05-19 18:06 ` Daniel Lezcano
2014-05-19 19:36 ` Tony Lindgren
2014-05-19 19:45 ` Daniel Lezcano
2014-05-19 21:18 ` Tobias Jakobi
2014-05-19 22:42 ` Tony Lindgren
2014-05-23 14:44 ` Tony Lindgren
2014-05-23 18:32 ` Tony Lindgren
[not found] ` <CAKnoXLxj42veWCbRjX98iT3FNAb92J4yR+UAL716JFSOb=pcrQ@mail.gmail.com>
2014-05-27 20:34 ` Tony Lindgren
2014-05-27 21:03 ` Santosh Shilimkar [this message]
2014-05-27 21:06 ` Daniel Lezcano
2014-05-19 20:00 ` Santosh Shilimkar
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=5384FDBF.2050604@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).