[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5009170E.1080807@linux.vnet.ibm.com>
Date: Fri, 20 Jul 2012 16:30:06 +0800
From: Michael Wang <wangyun@...ux.vnet.ibm.com>
To: Mike Galbraith <mgalbraith@...ell.com>
CC: LKML <linux-kernel@...r.kernel.org>,
"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>,
mmokrejs@...d.natur.cuni.cz, dan.carpenter@...cle.com
Subject: Re: [QUESTION ON BUG] the rcu stall issue could not be reproduced
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?
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?
Regards,
Michael Wang
>
> -Mike
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists