Summary: | [2.6.27.5 regression] suspend/hibernate issues with ThinkPad T41 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | hwoarang |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=12149 | ||
Whiteboard: | linux-2.6.27.5-regression | ||
Package list: | Runtime testing required: | --- | |
Attachments: | /var/log/message excerpt |
Description
Toralf Förster
2008-12-01 16:47:07 UTC
Dont CC maintainers when you cannot assign bugs. Tested 2.6.28-rc7 where that issue seems to be gone. So, to clarify: You boot the system You suspend-to-ram You wake it up everything fine so far? Then you attempt to suspend-to-disk, but the system does not suspend, and you end up with some messages in /var/log/messages ? Does it work if you avoid the suspend-to-ram first? Your /var/log/messages is lossy. Some important messages are missing from near the top. Please get the messages from dmesg instead, you may need to increase CONFIG_LOG_BUF_SHIFT for them all to be saved. Please provide dmesg output when you are trying to suspend-to-disk. Created attachment 174155 [details]
/var/log/message excerpt
I booted 2.6.27-gentoo-r4 with "init 2", therefore only acpid, syslog-ng and dnsmasq were started.
Then I suspended the system 3 times in a row w/o any problems each by pressing Fn+F4. Then I pressed Fn+F12 to hibernate the system, got the expected, but unwanted result, pulled a face and rebooted into working kernel 2.6.26-gentoo-r3.
Toralf, please reply to comment #3. I'm not sure if I'm understanding the bug correctly, you're suspending-to-ram and then to disk? Does it make any difference if you don't suspend to ram first? (In reply to comment #6) Yep, with these terms : Fn+F4 == "suspend" == supend-to-ram Fn+F12 == "hibernate" == suspend-to-disk I booted some minutes ago into that kernel (init 2) and could hibernate 2 times in a row w/o problems. Then I suspended, waked up and hibernated the system. That worked as expected. therefore it looks currently to me as a problem, if I first suspend a system after a (re-)boot and later try to hibernate it (which is unfortunately exactly my workflow when I travel from work to home and go back to my work location next day, which is too long for the battery). Seems to be an upstream bug. Please report it on kernel bugzilla ( http://bugzilla.kernel.org/ ). Please make sure to clarify on which kernel works and on which it doesnt. Remember to post your newest /var/log/messages while submitting the bug When you open the bug on kernel bugzilla, please post the link here. Many thanks Thanks for your hard work on this issue, reopening to include the fix. Fixed in gentoo-sources-2.6.27-r6 |