From: Tony Lindgren <tony@atomide.com>
To: Alex Shi <alex.shi@linaro.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"naresh.kamboju@linaro.org Kamboju" <naresh.kamboju@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Linaro Kernel <linaro-kernel@lists.linaro.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
Mark Brown <broonie@linaro.org>,
linux-omap@vger.kernel.org
Subject: Re: RCU stall on panda
Date: Tue, 13 May 2014 08:32:20 -0700 [thread overview]
Message-ID: <20140513153220.GC16837@atomide.com> (raw)
In-Reply-To: <5371BD69.8010600@linaro.org>
* Alex Shi <alex.shi@linaro.org> [140512 23:37]:
> On 05/13/2014 05:21 AM, Tony Lindgren wrote:
> > * Paul E. McKenney <paulmck@linux.vnet.ibm.com> [140505 11:11]:
> >> On Mon, May 05, 2014 at 05:39:43PM +0800, Alex Shi wrote:
> >>> I keep seeing the RCU stall problem on panda board from 3.10 kernel to latest upstream kernel
> >>> and google find some one report it before: https://lkml.org/lkml/2012/9/20/519
> >>>
> >>> Is it the hardware issue or a real software problem?
> >>
> >> I cannot distinguish between hardware and software from the trace below,
> >> but given that you are also seeing a soft lockup, either way you do
> >> appear to have a real problem as opposed to an RCU CPU stall warning
> >> false positive.
> >
> > Looks like you have CPU_IDLE enabled on panda. Hangs with current linux
> > next with CPU_IDLE are currently being discussed on the linux-omap list
> > in thread "omap4-panda-es boot issues with v3.15-rc4"
> >
> > I've seen occasional system hangs, and I've also noticed that doing
> > ctrl-a-f h or ctrl-a-f l for sysrq backtrace can unlock the system
> > producing similar errors to the below.
> >
>
> Thanks a lot for the info.
> In fact, the oops keeps in upstream kernel from 3.10 to latest.
Care to test if the revert of commit cb7094 Santosh posted as
"[PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled"
solves the problem for you?
Regards,
Tony
next prev parent reply other threads:[~2014-05-13 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53675C5F.10509@linaro.org>
[not found] ` <20140505180617.GM8754@linux.vnet.ibm.com>
2014-05-12 21:21 ` RCU stall on panda Tony Lindgren
2014-05-13 6:36 ` Alex Shi
2014-05-13 15:32 ` Tony Lindgren [this message]
2014-05-15 8:44 ` Alex Shi
2014-05-15 9:05 ` Daniel Lezcano
2014-05-15 13:26 ` Alex Shi
2014-05-15 18:32 ` Tony Lindgren
2014-05-15 18:36 ` Santosh Shilimkar
2014-05-16 7:41 ` Alex Shi
2014-05-16 13:37 ` Santosh Shilimkar
2014-05-22 8:59 ` Alex Shi
2014-05-22 13:36 ` 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=20140513153220.GC16837@atomide.com \
--to=tony@atomide.com \
--cc=alex.shi@linaro.org \
--cc=broonie@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).