Created attachment 692657 [details] pm-suspend.log +++ This bug was initially created as a clone of Bug #815973 +++ I had imagined that this was just something flaky about my laptop but now I have a second laptop with the same behavior. Hibernate does work. Suspend turns things off but I can't resume. This is in fedora 16 (3.3.2-1.fc16.i686) patches up to date (or nearly) Here's what looks to me like relevant output in /var/log/messages ... I now have a new laptop on which I've just installed fedora 17 and then yum update, and I find that neither suspend nor hibernate work. Or perhaps they do, but resume doesn't in either case. I hope to get at least ONE of them working! My last attempt left this in /var/log/messages ... Feb 3 14:38:22 number13 kernel: [261699.883915] PM: Syncing filesystems ... done. Feb 3 14:38:22 number13 kernel: [261699.906714] Freezing user space processes ... (elapsed 0.01 seconds) done. Feb 3 14:38:22 number13 kernel: [261699.918577] PM: Preallocating image memory... done (allocated 847597 pages) Feb 3 14:38:22 number13 kernel: [261702.394206] PM: Allocated 3390388 kbytes in 2.47 seconds (1372.62 MB/s) Feb 3 14:38:22 number13 kernel: [261702.394208] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Feb 3 14:38:22 number13 kernel: [261702.405600] Suspending console(s) (use no_console_suspend to debug) Feb 3 14:38:22 number13 kernel: [261702.409232] pciehp 0000:00:04.0:pcie04: pciehp_suspendFeb 3 22:40:47 number13 kernel: imklog 5.8.10, log source = /proc/kmsg started. looks like that last line ended without a newline, the 22:40 message was reboot. In pm-suspend.log I see stuff that looks like it was trying to resume, but I couldn't get the screen to show me anything.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.