From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Alex Shi <alex.shi@linaro.org>, Tony Lindgren <tony@atomide.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"naresh.kamboju@linaro.org Kamboju" <naresh.kamboju@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" <linux-omap@vger.kernel.org>
Subject: Re: RCU stall on panda
Date: Fri, 16 May 2014 09:37:51 -0400 [thread overview]
Message-ID: <537614AF.50100@ti.com> (raw)
In-Reply-To: <5375C145.6070904@linaro.org>
On Friday 16 May 2014 03:41 AM, Alex Shi wrote:
> On 05/16/2014 02:36 AM, Santosh Shilimkar wrote:
>>>>>> yes.
>>>>>> My board is panda ES. without this revert, it works.
>>>>
>>>> Care to specify what linux version you are testing against?
>>>>
>>>> Does it hang in idle always immediately on booting?
>>>>
>>>> Or does the serial console first hang with sysrq still
>>>> working (ctrl-a h in minicom for help) with device
>>>> eventually locking up hard?
>>>>
>> I just posted an updated patch Alex on other thread.
>> Attaching here again for your reference. Please try
>> it out and see if the you still get a hang.
>
> it does not hang this time.
>
This is good news and exactly what I expected.
> but I am not sure it can solve my problem, since RCU stall is not easy
> to reproduce in short time.
>
You may want to run the system longer if you can. I suspect the RCU stall
was also side effect of missing interrupts.
Regards,
Santosh
next prev parent reply other threads:[~2014-05-16 13:38 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
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 [this message]
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=537614AF.50100@ti.com \
--to=santosh.shilimkar@ti.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 \
--cc=tony@atomide.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).