From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: omap4-panda-es boot issues with v3.15-rc4
Date: Mon, 12 May 2014 16:56:27 -0700 [thread overview]
Message-ID: <7hiopah7pw.fsf@paris.lan> (raw)
In-Reply-To: <53713FCF.3000006@ti.com> (Santosh Shilimkar's message of "Mon, 12 May 2014 17:40:31 -0400")
Santosh Shilimkar <santosh.shilimkar@ti•com> writes:
> On Sunday 11 May 2014 11:55 AM, Tony Lindgren wrote:
>> * Kevin Hilman <khilman@linaro•org> [140509 16:46]:
>>> Roger Quadros <rogerq@ti•com> writes:
>>>
>>>> Kevin,
>>>>
>>>> On 05/09/2014 01:15 AM, Kevin Hilman wrote:
>>>>> Tony Lindgren <tony@atomide•com> writes:
>>>>>
>>>>> [...]
>>>>>
>>>>>> ..but I think I found the cause for recent hangs on panda, just a wild
>>>>>> guess based on looking at the recent cpuidle patches after v3.14.
>>>>>>
>>>>>> Looks like reverting 0b89e9aa2856 (cpuidle: delay enabling interrupts
>>>>>> until all coupled CPUs leave idle) makes booting work reliably again
>>>>>> on panda.
>>>>>>
>>>>>> Can you guys confirm, so far no issues here after few boot tests,
>>>>>> but it might be too early to tell.
>>>>>
>>>>> Reverting that makes things a bit more stable, but it still eventually
>>>>> fails in the same way. For me it took 8 boots for it to eventually
>>>>> fail.
>>>>>
>>>>> However, if I build with CONFIG_CPU_IDLE=n, it becomes much more stable
>>>>> (20+ boots in a row and still going.)
>>>>>
>>>>
>>>> Can you please test with CPU_IDLE enabled but C3 disabled as in below patch?
>>>> It worked for me 10/10 boots.
>>>
>>> Yup, it worked for me too for 10/10 boots in a row.
>>
>> But what has caused this regression, does it work reliably with let's
>> say v3.13 or v3.12?
>>
> IIRC things were stable till some CPUIDLE code consolidation happened.
> I don't recall exactly but some one did discuss about it a while back.
>
> Can you re-run your test-cases with patch at end of the email. This
> is just a hunch so don't blame me if I waste your time testing the
> patch.
With your patch applied on top of next-20140512, my 4460 Panda-ES has
booted 25 times in a row, and still going.
Kevin
next prev parent reply other threads:[~2014-05-12 23:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 12:53 omap4-panda-es boot issues with v3.15-rc4 Roger Quadros
2014-05-08 15:31 ` Kevin Hilman
2014-05-08 15:40 ` Kevin Hilman
2014-05-08 16:55 ` Tony Lindgren
2014-05-08 18:40 ` Tony Lindgren
2014-05-08 22:15 ` Kevin Hilman
2014-05-09 8:23 ` Roger Quadros
2014-05-09 23:45 ` Kevin Hilman
2014-05-11 15:55 ` Tony Lindgren
2014-05-12 21:40 ` Santosh Shilimkar
2014-05-12 22:07 ` Tony Lindgren
2014-05-13 8:10 ` Roger Quadros
2014-05-13 14:19 ` Santosh Shilimkar
2014-05-12 23:56 ` Kevin Hilman [this message]
2014-05-09 8:20 ` Roger Quadros
2014-05-08 17:12 ` Grygorii Strashko
2014-05-09 8:30 ` Roger Quadros
2014-05-09 12:33 ` Nishanth Menon
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=7hiopah7pw.fsf@paris.lan \
--to=khilman@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