public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Mike Galbraith <mgalbraith@novell.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
	mmokrejs@fold.natur.cuni.cz, dan.carpenter@oracle.com
Subject: Re: [QUESTION ON BUG] the rcu stall issue could not be reproduced
Date: Mon, 23 Jul 2012 10:37:42 +0800	[thread overview]
Message-ID: <500CB8F6.3000208@linux.vnet.ibm.com> (raw)
In-Reply-To: <1342775305.7432.76.camel@marge.simpson.net>

On 07/20/2012 05:08 PM, Mike Galbraith wrote:
> On Fri, 2012-07-20 at 16:30 +0800, Michael Wang wrote: 
>> On 07/20/2012 03:00 PM, 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.
>>
>> Hi, Mike
>>
>> Thanks for your reply.
>>
>> So you mean this issue is still existing on you box and you can see it
>> without doing any special things?
> 
> It's not my box (thank god).  It was initially triggered by tasks
> exiting simultaneously on all cores.  They jammed up, endless stall
> followed.
> 
>> I just want to try to reproduce it but it's impossible for me to get
>> some hardware as yours...
>>
>> So is there any idea on how to reproduce it on normal hardware?
> 
> No, AFAIK this problem is restricted to size XXL boxen, with all the
> joys that come along with having way too many CPUs.

I see, thanks for your info, looks like it's hard to reproduce on normal
servers like mine...

Regards,
Michael Wang
> 
> -Mike
> 



  parent reply	other threads:[~2012-07-23  2:37 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 [this message]
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=500CB8F6.3000208@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox