From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: rcub1 task hung for > 180 seconds.
Date: Tue, 12 Jul 2011 13:55:27 -0700 [thread overview]
Message-ID: <4E1CB4BF.2020302@candelatech.com> (raw)
This is same 3.0-rc7 system that had the lockdep splat I just
posted...
Is this task blockage serious?
INFO: task rcub1:11 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rcub1 D ffff880128f6b6c8 0 11 2 0x00000000
ffff880128f73cd0 0000000000000046 ffff880100000000 0000000000012940
ffff880128f6b3f0 ffff880128f73fd8 ffff880128f72000 0000000000012940
ffff880128f73fd8 0000000000012940 ffff8801079e9150 ffff880128f6b3f0
Call Trace:
[<ffffffff81481f0d>] ? sub_preempt_count+0x92/0xa6
[<ffffffff8147e1d1>] __rt_mutex_slowlock+0x84/0xb6
[<ffffffff8147e3c9>] rt_mutex_slowlock+0xc5/0x132
[<ffffffff8147e4d4>] rt_mutex_lock+0x46/0x4a
[<ffffffff810a6bed>] rcu_boost_kthread+0x125/0x169
[<ffffffff810a6ac8>] ? rcu_initiate_boost+0x8a/0x8a
[<ffffffff81066f80>] kthread+0x7d/0x85
[<ffffffff81486164>] kernel_thread_helper+0x4/0x10
[<ffffffff8147f358>] ? retint_restore_args+0x13/0x13
[<ffffffff81066f03>] ? __init_kthread_worker+0x56/0x56
[<ffffffff81486160>] ? gs_change+0x13/0x13
INFO: lockdep is turned off.
INFO: task rcub1:11 blocked for more than 180 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rcub1 D ffff880128f6b6c8 0 11 2 0x00000000
ffff880128f73cd0 0000000000000046 ffff880100000000 0000000000012940
ffff880128f6b3f0 ffff880128f73fd8 ffff880128f72000 0000000000012940
ffff880128f73fd8 0000000000012940 ffff8801079e9150 ffff880128f6b3f0
Call Trace:
[<ffffffff81481f0d>] ? sub_preempt_count+0x92/0xa6
[<ffffffff8147e1d1>] __rt_mutex_slowlock+0x84/0xb6
[<ffffffff8147e3c9>] rt_mutex_slowlock+0xc5/0x132
[<ffffffff8147e4d4>] rt_mutex_lock+0x46/0x4a
[<ffffffff810a6bed>] rcu_boost_kthread+0x125/0x169
[<ffffffff810a6ac8>] ? rcu_initiate_boost+0x8a/0x8a
[<ffffffff81066f80>] kthread+0x7d/0x85
[<ffffffff81486164>] kernel_thread_helper+0x4/0x10
[<ffffffff8147f358>] ? retint_restore_args+0x13/0x13
[<ffffffff81066f03>] ? __init_kthread_worker+0x56/0x56
[<ffffffff81486160>] ? gs_change+0x13/0x13
INFO: lockdep is turned off.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2011-07-12 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E1CB4BF.2020302@candelatech.com \
--to=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox