The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
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 20:05:26 +0000	[thread overview]
Message-ID: <20110113200526.GA31380@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20110112222219.GA17328@linux.vnet.ibm.com>

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.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  parent reply	other threads:[~2011-01-13 20:06 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 [this message]
2011-01-13 20:41     ` Paul E. McKenney

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=20110113200526.GA31380@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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