Bug 7786
Summary: | CPU hotplug generates OOPS the second time a CPU is unplugged | ||
---|---|---|---|
Product: | Platform Specific/Hardware | Reporter: | Mauro Carvalho Chehab (mchehab) |
Component: | x86-64 | Assignee: | Andi Kleen (andi-bz) |
Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
Severity: | low | CC: | akpm, pavel |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.19.1 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
dmesg with the oops
This patch fixed the oops. However, kernel still complains about recursive locking |
Description
Mauro Carvalho Chehab
2007-01-07 12:29:38 UTC
Created attachment 10020 [details]
dmesg with the oops
I suspect that this trouble may be related to the circular dependency, as
reported by kernel:
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.19.1 #1
-------------------------------------------------------
stress/5670 is trying to acquire lock:
(cpu_bitmask_lock){--..}, at: [<ffffffff8015af7d>] lock_cpu_hotplug+0x6d/0x80
but task is already holding lock:
(workqueue_mutex){--..}, at: [<ffffffff8014962f>]
workqueue_cpu_callback+0x16f/0x2d0
which lock already depends on the new lock.
stress is just a script doing echo to cpu hotplug sysfs interface:
echo Making CPU online
echo 0 >/sys/devices/system/cpu/cpu1/online
echo Making CPU offline
echo 1 >/sys/devices/system/cpu/cpu1/online
echo Making CPU online
echo 0 >/sys/devices/system/cpu/cpu1/online
Created attachment 10025 [details]
This patch fixed the oops. However, kernel still complains about recursive locking
Andrew Morton pointed to a patch from Christoph Lameter <clameter@sgi.com> that fixes the issue. It would be better to have this patch applied to -stable. After the patch, it still complains about bad locking. |