Description of problem: When using, e.g., pm-hibernate to hibernate my Acer Aspire 1690, immediately after the system has been put into hibernation it wakes up and resumes. pm-suspend works and no keys are pressed. Version-Release number of selected component (if applicable): acpid-1.0.6-9.fc10.i386 kernel-2.6.27.7-134.fc10.i686 How reproducible: Always. Steps to Reproduce: 1. Boot Acer Aspire 1690 2. Run pm-hibernate 3. See how it resumes immediately Actual results: System resumes immediately from hibernation. Expected results: System stays in hibernation. Additional info: This used to work with F9. I tested from runlevel 3 with parameter "nomodeset" to make sure this is a acpi/kernel issue. I will attach lscpi and dmesg before/after.
Created attachment 326874 [details] dmesg from Acer Aspire 1690
Created attachment 326875 [details] dmesg from Acer Aspire 1690 before hibernation
Created attachment 326876 [details] dmesg from Acer Aspire 1690 after resume from hibernation
Well, I compiled few kernel.org kernels and noticed that this breaks between 2.6.23 and 2.6.24. I'll try to debug this further with upstream developers.
I bisected this to commit 9cd9a0058dd35268b24fa16795a92c800f4086d4. I will follow up with a proposal from upstream developers on how to fix this for good. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9cd9a0058dd35268b24fa16795a92c800f4086d4
reassigned from ACPI to ACPID
This is a kernel issue and a fix is in the works in the upstream: https://lists.linux-foundation.org/pipermail/linux-pm/2009-January/019251.html I will update this bug as soon as more information is available.
In that case, reassigned from acpid to kernel.
Intel engineering is now hopefully looking into this.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
It's best that this bug will autoclose as if anything happens it will be at the upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=9258 Thanks.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.