From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michael Wang <wangyun@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
mgalbraith@novell.com, mmokrejs@fold.natur.cuni.cz
Subject: Re: [QUESTION ON BUG] the rcu stall issue could not be reproduced
Date: Fri, 20 Jul 2012 11:36:19 +0300 [thread overview]
Message-ID: <20120720083619.GM16348@mwanda> (raw)
In-Reply-To: <500915B9.2030104@linux.vnet.ibm.com>
On Fri, Jul 20, 2012 at 04:24:25PM +0800, Michael Wang wrote:
> On 07/20/2012 02:41 PM, Dan Carpenter wrote:
> > My bug was fixed in March. There was an email thread about it when
> > the merge window opened but I can't find it...
> Hi, Dan
>
> Thanks for your reply.
>
> Currently this issue won't appear because the
> CONFIG_RCU_CPU_STALL_TIMEOUT=60, which is big enough to avoid the
> warning info.
>
> So is this the fix you mentioned? or someone has find out the true
> reason and fixed it?
I don't think there was an email thread on the RCU stall issue after
all. I'm not sure what how it was fixed.
The 60 second time out would have still triggered with my bug. It
was a complete system hang, the RCU stall message was just a
debugging hint. I was hitting the bug every couple days reliably on
all my systems.
regards,
dan carpenter
next prev parent reply other threads:[~2012-07-20 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 3:09 [QUESTION ON BUG] the rcu stall issue could not be reproduced Michael Wang
2012-07-20 6:41 ` Dan Carpenter
2012-07-20 8:24 ` Michael Wang
2012-07-20 8:36 ` Dan Carpenter [this message]
2012-07-20 8:53 ` Michael Wang
2012-07-20 7:00 ` Mike Galbraith
2012-07-20 8:30 ` Michael Wang
2012-07-20 9:08 ` Mike Galbraith
2012-07-20 10:18 ` Martin Mokrejs
2012-07-23 2:46 ` Michael Wang
2012-07-23 2:37 ` Michael Wang
2012-07-23 18:46 ` Martin Mokrejs
2012-07-24 1:19 ` Michael Wang
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=20120720083619.GM16348@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalbraith@novell.com \
--cc=mmokrejs@fold.natur.cuni.cz \
--cc=paulmck@linux.vnet.ibm.com \
--cc=wangyun@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