linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: omap4-panda-es boot issues with v3.15-rc4
Date: Sun, 11 May 2014 08:55:43 -0700	[thread overview]
Message-ID: <20140511155542.GD28266@atomide.com> (raw)
In-Reply-To: <7heh02ms82.fsf@paris.lan>

* 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?

Regards,

Tony

  reply	other threads:[~2014-05-11 15:55 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 [this message]
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
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=20140511155542.GD28266@atomide.com \
    --to=tony@atomide.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).