public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Subject: Re: INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies)
Date: Fri, 18 Jan 2013 09:35:16 -0800	[thread overview]
Message-ID: <20130118173516.GL3159@linux.vnet.ibm.com> (raw)
In-Reply-To: <1358050431.4514.57.camel@deadeye.wl.decadent.org.uk>

On Sun, Jan 13, 2013 at 04:13:51AM +0000, Ben Hutchings wrote:
> On Wed, 2013-01-02 at 19:49 -0500, Steven Rostedt wrote:
> > 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.
> 
> If I read the Ubuntu changelog correctly, Ralf's machine is running a
> version based on 3.2.34, which already has this change (I applied it in
> 3.2.32).

OK, another possibility is c8020a67.  Ralf, if that does not help, is
it possible for you to run either a 3.7 or a -rcu kernel [*]?  There are
some other fixes that could be related, but the probability seems low.

							Thanx, Paul

[*]  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
	branch rcu/next


      reply	other threads:[~2013-01-18 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 19:09 INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies) Ralf Hildebrandt
2013-01-02 20:56 ` Steven Rostedt
2013-01-02 21:29   ` Paul E. McKenney
2013-01-03  0:49     ` Steven Rostedt
2013-01-03  3:14       ` Paul E. McKenney
2013-01-13  4:13       ` Ben Hutchings
2013-01-18 17:35         ` Paul E. McKenney [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=20130118173516.GL3159@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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