From: Alex Shi <alex.shi@intel.com>
To: "Chen, Tim C" <tim.c.chen@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: a non producible kernel panic
Date: Sun, 05 Feb 2012 12:28:54 +0800 [thread overview]
Message-ID: <4F2E0586.2090803@intel.com> (raw)
When do performance testing for rc2 kernel on our NHM EX machine( 4
sockets * 8 cores), I find a kernel panic. but never reproduced it. and
didn't find some useful info after enable lockdep, rcu debug etc.
Any ideas on this?
INFO: task umount:4280 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
umount D ffff883025443198 0 4280 4235 0x00000080
ffff883027805d28 0000000000000086 ffff883025442de0 ffff883027805fd8
ffff883027805fd8 0000000000013100 ffff8810292eade0 ffff883025442de0
0000000000000018 7fffffffffffffff 7fffffffffffffff ffffffff81c180c8
Call Trace:
[<ffffffff81452caa>] schedule+0x55/0x57
[<ffffffff81451a93>] schedule_timeout+0x2f/0xd9
[<ffffffff8109dfe0>] ? rcu_panic+0x12/0x12
[<ffffffff81028259>] ? physflat_send_IPI_allbutself+0x12/0x14
[<ffffffff81024a33>] ? native_send_call_func_ipi+0x71/0x91
[<ffffffff81452b67>] wait_for_common+0x95/0xeb
[<ffffffff8105dfe7>] ? try_to_wake_up+0x1e0/0x1e0
[<ffffffff8109dfe0>] ? rcu_panic+0x12/0x12
[<ffffffff8109eb41>] ? call_rcu_bh+0x12/0x12
[<ffffffff81452c53>] wait_for_completion+0x18/0x1a
[<ffffffff8109ef36>] _rcu_barrier+0x96/0xa6
[<ffffffff8109ef5d>] rcu_barrier_sched+0x17/0x19
[<ffffffff8109ef68>] rcu_barrier+0x9/0xb
[<ffffffff8110bac0>] deactivate_locked_super+0x32/0x52
[<ffffffff8110c536>] deactivate_super+0x32/0x36
[<ffffffff81120691>] mntput_no_expire+0xde/0xe7
[<ffffffff811212f2>] sys_umount+0x2cd/0x2ff
[<ffffffff81112699>] ? path_put+0x1a/0x1e
[<ffffffff81459a79>] system_call_fastpath+0x16/0x1b
INFO: task umount:4280 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
umount D ffff883025443198 0 4280 4235 0x00000080
ffff883027805d28 0000000000000086 ffff883025442de0 ffff883027805fd8
ffff883027805fd8 0000000000013100 ffff8810292eade0 ffff883025442de0
0000000000000018 7fffffffffffffff 7fffffffffffffff ffffffff81c18
next reply other threads:[~2012-02-05 4:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 4:28 Alex Shi [this message]
2012-02-06 5:19 ` a non producible kernel panic Alex,Shi
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=4F2E0586.2090803@intel.com \
--to=alex.shi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.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 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.