path: root/arch
diff options
authorWilliam Morrrow <>2006-08-14 22:37:31 -0700
committerLen Brown <>2006-08-16 17:59:05 -0400
commit4e6e6504a4572dee3afcb0925ce92ad559e1e0db (patch)
tree9c1d2798c5db07c4df7cddc5db8f12c4c8037ca3 /arch
parent9f737633e6ee54fc174282d49b2559bd2208391d (diff)
ACPI: Handle BIOS that resumes from S3 to suspend routine rather than resume vector
A BIOS has been found that resumes from S3 to the routine that invoked suspend, ignoring the resume vector. This appears to the OS as a failed S3 attempt. This same system suspend/resume's properly with Windows. It is possible to invoke the protected mode register restore routine (which would normally restore the sysenter registers) when the BIOS returns from S3. This has no effect on a correctly running system and repairs the damage from the deviant BIOS. Signed-off-by: William Morrow <> Signed-off-by: Jordan Crouse <> Signed-off-by: Andrew Morton <> Signed-off-by: Len Brown <>
Diffstat (limited to 'arch')
1 files changed, 4 insertions, 1 deletions
diff --git a/arch/i386/kernel/acpi/wakeup.S b/arch/i386/kernel/acpi/wakeup.S
index 9f408eee4e6f..b781b38131c0 100644
--- a/arch/i386/kernel/acpi/wakeup.S
+++ b/arch/i386/kernel/acpi/wakeup.S
@@ -292,7 +292,10 @@ ENTRY(do_suspend_lowlevel)
pushl $3
call acpi_enter_sleep_state
addl $4, %esp
- ret
+# In case of S3 failure, we'll emerge here. Jump
+# to ret_point to recover
+ jmp ret_point
.p2align 4,,7
call restore_registers