From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
Cc: Mike Galbraith <mgalbraith@novell.com>,
LKML <linux-kernel@vger.kernel.org>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
dan.carpenter@oracle.com
Subject: Re: [QUESTION ON BUG] the rcu stall issue could not be reproduced
Date: Tue, 24 Jul 2012 09:19:36 +0800 [thread overview]
Message-ID: <500DF828.3050102@linux.vnet.ibm.com> (raw)
In-Reply-To: <500D9BFC.9090707@fold.natur.cuni.cz>
On 07/24/2012 02:46 AM, Martin Mokrejs wrote:
> Hi,
> I see few more RCU bugs reported in bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=43028
> https://bugzilla.kernel.org/show_bug.cgi?id=40092
> https://bugzilla.kernel.org/show_bug.cgi?id=42997
>
> And, I placed my previous long email with logs at
> https://bugzilla.kernel.org/show_bug.cgi?id=45091
>
> Hope this helps eventually once.
That's very helpful, I need some time to read and think about it, thanks
for the info ;-)
Regards,
Michael Wang
> Martin
>
> Mike Galbraith wrote:
>> On Fri, 2012-07-20 at 11:09 +0800, Michael Wang wrote:
>>> Hi, Mike, Martin, Dan
>>>
>>> I'm currently taking an eye on the rcu stall issue which was reported by
>>> you in the mail:
>>>
>>> rcu: endless stalls
>>> From: Mike Galbraith
>>> linux-3.4-rc7: rcu_sched self-detected stall on CPU
>>> From: Martin Mokrejs
>>> RCU stalls in linux-next
>>> From: Dan Carpenter
>>>
>>> I try to reproduce the issue on my X86 server with 12 cpu
>>
>> The 'endless stalls' box was 341.33333 times larger. Dunno if you can
>> even set a serial port slow enough to approximate all cores trying to
>> gripe through a single pinhole simultaneously.
>>
>> -Mike
>>
>>
>
>
prev parent reply other threads:[~2012-07-24 1:19 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
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 [this message]
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=500DF828.3050102@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.