http://bugzilla.kernel.org/show_bug.cgi?id=9772
------- Comment #3 from [EMAIL PROTECTED] 2008-01-24 09:31 ------- There's a couple of problems. /sys/devices/system/cpu/cpuX/online doesn't always correspond to /sys/bus/acpi/drivers/processor/ACPI0007:0X. Especially if you remove and then re-add CPUS, you can get a situation where CPU3 corresponds to ACPI0007:08, or something similar. I sent mail to lkml and linux-acpi describing the issue, but nobody responded. So you can't always offline the correct CPU before ejecting it. In my testing, I'm always careful to offline the CPU before ejecting it. It just seems really bad to make it this easy to accidentally hang the whole system. Ejecting a CPU really needs to fail if the CPU is online, or else it needs to automatically offline the CPU. Failing if the CPU is online seems to make the most sense. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
