From: Russell King <rmk@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: INFO: task rcu_kthread:6 blocked for more than 120 seconds.
Date: Wed, 12 Jan 2011 17:43:00 +0000 [thread overview]
Message-ID: <20110112174300.GA6504@flint.arm.linux.org.uk> (raw)
I'm seeing rcu_kthread get stuck from time to time on ARM Versatile PB
(ARM926). Kernel is based upon commit 9e9bc973 (immediately prior to
the merge of the OMAP tree.)
~ # ps aux|grep rcu
root 6 0.0 0.0 0 0 ? S 02:31 0:01 [rcu_kthread]
root 502 9.0 0.3 3740 472 ttyAMA0 S+ 02:59 0:00 grep rcu
~ # ps aux|grep rcu
root 6 0.0 0.0 0 0 ? D 02:31 0:01 [rcu_kthread]
root 504 0.0 0.3 3740 472 ttyAMA0 S+ 03:00 0:00 grep rcu
~ # ps aux|grep rcu
root 6 0.0 0.0 0 0 ? D 02:31 0:01 [rcu_kthread]
root 506 0.0 0.3 3740 472 ttyAMA0 S+ 03:00 0:00 grep rcu
~ # ps aux|grep rcu
root 6 0.0 0.0 0 0 ? D 02:31 0:01 [rcu_kthread]
root 508 0.0 0.3 3740 472 ttyAMA0 S+ 03:00 0:00 grep rcu
~ # cat /proc/6/wchan
rcu_kthread
~ # INFO: task rcu_kthread:6 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rcu_kthread D c02c6684 0 6 2 0x00000000
Backtrace:
[<c02c6388>] (schedule+0x0/0x354) from [<c00836a0>] (rcu_kthread+0x78/0xf4)
[<c0083628>] (rcu_kthread+0x0/0xf4) from [<c00633ac>] (kthread+0x88/0x90)
[<c0063324>] (kthread+0x0/0x90) from [<c004d12c>] (do_exit+0x0/0x5f8)
r7:00000013 r6:c004d12c r5:c0063324 r4:c181df28
no locks held by rcu_kthread/6.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next reply other threads:[~2011-01-12 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 17:43 Russell King [this message]
2011-01-12 22:22 ` INFO: task rcu_kthread:6 blocked for more than 120 seconds 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
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=20110112174300.GA6504@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.