diff options
| author | Thomas Renninger <trenn@suse.de> | 2012-07-12 12:24:33 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <rjw@sisk.pl> | 2012-07-12 22:39:32 +0200 |
| commit | c4686c71a9183f76e3ef59098da5c098748672f6 (patch) | |
| tree | b577b21cd2d384ff9ddafef803e03e873aa4f8d3 /arch/x86/kernel/vsyscall_64.c | |
| parent | bd0a521e88aa7a06ae7aabaed7ae196ed4ad867a (diff) | |
cpufreq / ACPI: Fix not loading acpi-cpufreq driver regression
Commit d640113fe80e45ebd4a5b420b introduced a regression on SMP
systems where the processor core with ACPI id zero is disabled
(typically should be the case because of hyperthreading).
The regression got spread through stable kernels.
On 3.0.X it got introduced via 3.0.18.
Such platforms may be rare, but do exist.
Look out for a disabled processor with acpi_id 0 in dmesg:
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x10] disabled)
This problem has been observed on a:
HP Proliant BL280c G6 blade
This patch restricts the introduced workaround to platforms
with nr_cpu_ids <= 1.
Signed-off-by: Thomas Renninger <trenn@suse.de>
CC: stable@vger.kernel.org
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'arch/x86/kernel/vsyscall_64.c')
0 files changed, 0 insertions, 0 deletions