Bug 28342
Summary: | suspend to RAM completely fails | ||
---|---|---|---|
Product: | Power Management | Reporter: | Werner Lemberg (wl) |
Component: | Hibernation/Suspend | Assignee: | power-management_other |
Status: | CLOSED DUPLICATE | ||
Severity: | high | CC: | rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.38-rc3 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7216, 27352 | ||
Attachments: | boot.msg for 2.6.38-rc3 |
The boot log does not show any sign of APM. A laptop this new would not use APM (it is an old legacy system) and is probably using ACPI. Does 2.6.37 work correctly? To Stephen: Ah, yes, sorry for mixing it up. To Rafael: Yes, with 2.6.37 suspend to RAM works just fine. Is the kernel 32-bit or 64-bit? 32bit (i586). In that case I think it's caused by commit 5bd5a45 (x86: Add NX protection for kernel data). It would be good to verify that, though. Perhaps some kernel `command line option' could be temporarily added to switch this feature on or off... Then I can test this easily as soon as it gets added to openSuSE's kernel repository. Unfortunately, that's just a kernel configuration option. I could prepare a test kernel for you, but I think it's better to wait until this (known) issue is fixed. I'll let you know when that happens. Ah, it's a known problem. I wasn't aware of this since I haven't found a bug report in bugzilla. Thanks for your help. It's bug #27472 . However, I'm still not sure you're seeing the same issue. At this point it's better to wait until the fix for that bug is merged and test a kernel containing it. Using 2.6.38-rc4-6-pae, it works again. Thanks for assistance. OK, closing. *** This bug has been marked as a duplicate of bug 27472 *** |
Created attachment 46562 [details] boot.msg for 2.6.38-rc3 [openSuSE kernel-pae 2.6.38-rc3.3.1] [openSuSE pm-utils 1.4.1-1.2] Starting with the 2.6.38 series, suspend to RAM completely fails. It simply reboots. This is a Dell Inspiron 6400 laptop. Attached is my boot.msg. Please tell me what further information you need for investigation.