[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <500D9BFC.9090707@fold.natur.cuni.cz>
Date: Mon, 23 Jul 2012 20:46:20 +0200
From: Martin Mokrejs <mmokrejs@...d.natur.cuni.cz>
To: Mike Galbraith <mgalbraith@...ell.com>
CC: Michael Wang <wangyun@...ux.vnet.ibm.com>,
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
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.
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
>
>
--
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