linux-kernel - Re: INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 02 Jan 2013 19:49:23 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org, Ben Hutchings <ben@...adent.org.uk>
Subject: Re: INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies)

On Wed, 2013-01-02 at 13:29 -0800, Paul E. McKenney wrote:
> On Wed, Jan 02, 2013 at 03:56:30PM -0500, Steven Rostedt wrote:
> > On Wed, Jan 02, 2013 at 08:09:20PM +0100, Ralf Hildebrandt wrote:
> > > This happened of a virtual guest (Linux mail 3.2.0-35-virtual #55-Ubuntu SMP Wed Dec 5 18:02:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux)
> > 
> > 3.2 is rather old and this looks to be a stock Ubuntu kernel. May want
> > to file a Bugzilla (or whatever they call it) with them.
> > 
> > > 
> > > Jan  2 13:24:08 mail kernel: [3531872.484283] INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies)
> > 
> > 0 jiffies?
> 
> One possibility is that they are missing commit a10d206e (rcu: Fix
> day-one dyntick-idle stall-warning bug), at least assuming that
> CONFIG_PREEMPT=n.  This went into 3.6, IIRC.

If that does fix the issue, we probably should send that off to Ben for
inclusion into 3.2 stable.

Thanks,

-- Steve

> 
> 							Thanx, Paul
> 



--
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/