diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2008-10-20 21:30:19 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2008-10-25 14:32:37 -0700 |
commit | bc79810633524ea09b77e3de3ba3f4a97f2152b7 (patch) | |
tree | a7f72aa93774424124439b8ff0405c4b0f9e0b85 /kernel | |
parent | 204d439e5c39809d05f15b93cfabac1cbb99e1a7 (diff) | |
download | linux-stable-bc79810633524ea09b77e3de3ba3f4a97f2152b7.tar.gz linux-stable-bc79810633524ea09b77e3de3ba3f4a97f2152b7.tar.bz2 linux-stable-bc79810633524ea09b77e3de3ba3f4a97f2152b7.zip |
x86 ACPI: fix breakage of resume on 64-bit UP systems with SMP kernel
commit 3038edabf48f01421c621cb77a712b446d3a5d67 upstream
x86 ACPI: Fix breakage of resume on 64-bit UP systems with SMP kernel
We are now using per CPU GDT tables in head_64.S and the original
early_gdt_descr.address is invalidated after boot by
setup_per_cpu_areas(). This breaks resume from suspend to RAM on
x86_64 UP systems using SMP kernels, because this part of head_64.S
is also executed during the resume and the invalid GDT address
causes the system to crash. It doesn't break on 'true' SMP systems,
because early_gdt_descr.address is modified every time
native_cpu_up() runs. However, during resume it should point to the
GDT of the boot CPU rather than to another CPU's GDT.
For this reason, during suspend to RAM always make
early_gdt_descr.address point to the boot CPU's GDT.
This fixes http://bugzilla.kernel.org/show_bug.cgi?id=11568, which
is a regression from 2.6.26.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@suse.cz>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Reported-and-tested-by: Andy Wettstein <ajw1980@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions