The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: INFO: task rcu_kthread:6 blocked for more than 120 seconds.
Date: Thu, 13 Jan 2011 12:41:35 -0800	[thread overview]
Message-ID: <20110113204135.GK2500@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110113200526.GA31380@flint.arm.linux.org.uk>

On Thu, Jan 13, 2011 at 08:05:26PM +0000, Russell King wrote:
> On Wed, Jan 12, 2011 at 02:22:19PM -0800, Paul E. McKenney wrote:
> > Does the following patch help?
> 
> Yes it does, thanks.
> 
> Tested-by: Russell King <rmk+kernel@arm.linux.org.uk>
> 
> > commit 70ce43253a4465211a9c51e33d56a417c759a718
> > Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Date:   Wed Jan 12 14:18:11 2011 -0800
> > 
> >     rcu: avoid pointless blocked-task warnings
> >     
> >     If the RCU callback-processing kthread has nothing to do, it parks in
> >     a wait_event().  If RCU remains idle for more than two minutes, the
> >     kernel complains about this.  This commit changes from wait_event()
> >     to wait_event_interruptible() to prevent the kernel from complaining
> >     just because RCU is idle.
> >     
> >     Reported-by: Russell King <rmk@arm.linux.org.uk>
> 
> Please add '+kernel' in there, thanks.

Done!  FWIW, I copied the original from my email agent.

							Thanx, Paul

      reply	other threads:[~2011-01-13 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 17:43 INFO: task rcu_kthread:6 blocked for more than 120 seconds Russell King
2011-01-12 22:22 ` Paul E. McKenney
2011-01-13 15:17   ` Thomas Weber
2011-01-13 15:42     ` Paul E. McKenney
2011-01-13 20:05   ` Russell King
2011-01-13 20:41     ` 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=20110113204135.GK2500@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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