diff options
| author | Andreas Herrmann <andreas.herrmann3@amd.com> | 2007-11-07 02:12:58 +0100 |
|---|---|---|
| committer | Thomas Gleixner <tglx@apollo.(none)> | 2007-11-17 16:27:00 +0100 |
| commit | 903675569e278af86aa08c2af238b0ab997065d1 (patch) | |
| tree | f46ca0146d62c15bfc7e46979669ad8d3ed362a6 /arch/m68knommu | |
| parent | 4307d1e5ada595c87f9a4d16db16ba5edb70dcb1 (diff) | |
| download | linux-903675569e278af86aa08c2af238b0ab997065d1.tar.bz2 | |
x86: fix cpu-hotplug regression
Commit d435d862baca3e25e5eec236762a43251b1e7ffc
("cpu hotplug: mce: fix cpu hotplug error handling")
changed the error handling in mce_cpu_callback.
In cases where not all CPUs are brought up during
boot (e.g. using maxcpus and additional_cpus parameters)
mce_cpu_callback now returns NOTFIY_BAD because
for such CPUs cpu_data is not completely filled when
the notifier is called. Thus mce_create_device fails right
at its beginning:
if (!mce_available(&cpu_data[cpu]))
return -EIO;
As a quick fix I suggest to check boot_cpu_data for MCE.
To reproduce this regression:
(1) boot with maxcpus=2 addtional_cpus=2 on a 4 CPU x86-64 system
(2) # echo 1 >/sys/devices/system/cpu/cpu2/online
-bash: echo: write error: Invalid argument
dmesg shows:
_cpu_up: attempt to bring up CPU 2 failed
Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'arch/m68knommu')
0 files changed, 0 insertions, 0 deletions