From: Andi Kleen <andi@firstfloor.org>
To: mingo@elte.hu, linux-kernel@vger.kernel.org, rjw@sisk.pl
Subject: scheduler hang on cpu re-hotplug with 2.6.27rc8
Date: Mon, 6 Oct 2008 16:12:20 +0200 [thread overview]
Message-ID: <20081006141220.GA14160@basil.nowhere.org> (raw)
[Rafael, something for the regression list]
While testing cpu hotunplug/hotreplug (first
setting two CPUs to offline and then to online again) on a 16 thread machine
with 2.6.27rc8 the first
# echo 1 > ./devices/system/cpu/cpu14/online
after hotunplug deadlocked somewhere in the scheduler:
bash D 00000000ffffcb5b 0 4683 4671
ffff8804bc583c68 0000000000000086 ffff8804bc9d8640 0000000000000296
ffff8804bdd34730 ffff8804be6fc090 ffff8804bdd34978 0000000c805a1e2a
ffff8804be4fd780 ffffffff802298b4 ffffffff808acd98 ffff88027d0b1168
Call Trace:
[<ffffffff802298b4>] __dequeue_entity+0x25/0x68
[<ffffffff805a1b4b>] schedule_timeout+0x1e/0xad
[<ffffffff8022a11f>] __disable_runtime+0x57/0x155
[<ffffffff8025cc47>] cpupri_set+0xbe/0xcd
[<ffffffff805a19b3>] wait_for_common+0xcd/0x131
[<ffffffff8022c918>] default_wake_function+0x0/0xe
[<ffffffff80241f3a>] synchronize_rcu+0x30/0x36
[<ffffffff80241fac>] wakeme_after_rcu+0x0/0xc
[<ffffffff8022dab6>] partition_sched_domains+0x9b/0x1dd
[<ffffffff8022dc26>] update_sched_domains+0x2e/0x35
[<ffffffff805a5297>] notifier_call_chain+0x29/0x4c
[<ffffffff8059ef76>] _cpu_up+0xd0/0x10a
[<ffffffff8059f004>] cpu_up+0x54/0x61
[<ffffffff805837d5>] store_online+0x43/0x67
[<ffffffff802c51e9>] sysfs_write_file+0xd2/0x110
[<ffffffff8028656b>] vfs_write+0xad/0x136
[<ffffffff802869f3>] sys_write+0x45/0x6e
[<ffffffff8020b22b>] system_call_fastpath+0x16/0x1b
It just hung forever, but the machine was otherwise fully functional.
This was without frame pointers so the backtrace presumably has
some garbage. Haven't looked too closely.
-Andi
--
ak@linux.intel.com
next reply other threads:[~2008-10-06 14:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 14:12 Andi Kleen [this message]
2008-10-06 23:28 ` RCU hang on cpu re-hotplug with 2.6.27rc8 Andi Kleen
2008-10-07 3:08 ` Paul E. McKenney
2008-10-07 7:15 ` Andi Kleen
2008-10-07 15:26 ` Paul E. McKenney
2008-10-07 15:49 ` Andi Kleen
2008-10-07 16:34 ` Paul E. McKenney
2008-10-07 21:09 ` Andi Kleen
2008-10-07 21:22 ` Paul E. McKenney
2008-10-09 1:08 ` [PATCH] rudimentary tracing for Classic RCU Paul E. McKenney
2008-10-09 6:20 ` Lai Jiangshan
2008-10-09 6:55 ` Andi Kleen
2008-10-09 7:05 ` Lai Jiangshan
2008-10-09 7:14 ` KOSAKI Motohiro
2008-10-09 7:26 ` Lai Jiangshan
2008-10-09 8:06 ` Andi Kleen
2008-10-10 11:48 ` Paul E. McKenney
2008-10-09 11:50 ` Paul E. McKenney
2008-10-09 11:50 ` Paul E. McKenney
2008-10-09 10:23 ` Frédéric Weisbecker
2008-10-09 10:53 ` Andi Kleen
2008-10-09 11:44 ` Frédéric Weisbecker
2008-10-09 11:54 ` Paul E. McKenney
2008-10-09 13:01 ` Frédéric Weisbecker
2008-10-10 3:44 ` [PATCH] v2 " Paul E. McKenney
2008-10-13 23:09 ` [PATCH] v3 " Paul E. McKenney
2008-10-14 3:53 ` Lai Jiangshan
2008-10-14 14:35 ` Paul E. McKenney
2008-10-23 11:12 ` Lai Jiangshan
2008-10-26 21:59 ` Paul E. McKenney
2008-10-27 21:50 ` Paul E. McKenney
2008-10-27 23:57 ` Paul E. McKenney
2008-10-29 1:16 ` Paul E. McKenney
2008-10-29 1:31 ` Lai Jiangshan
2008-10-30 15:52 ` Paul E. McKenney
2008-10-09 1:33 ` RCU hang on cpu re-hotplug with 2.6.27rc8 Paul E. McKenney
2008-10-09 4:56 ` Andi Kleen
2008-10-09 7:24 ` Thomas Gleixner
2008-10-09 8:22 ` Andi Kleen
2008-10-09 11:44 ` 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=20081006141220.GA14160@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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.