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 Experimenting with the new laptop I find that it does resume part of the way. I can ssh into it. But I can't figure out how to get the display to show anything. I attach a transcript from /var/log/messages starting with the sleep and ending in the state where I'm trying (without success) to get the screen to come on by pressing function keys.
I now notice that after resume I see the following in pm-suspend.log ... /usr/lib/pm-utils/sleep.d/95packagekit suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: No quirk database entry for this system, using default. /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0 vbetool not installed! vbetool not installed! vbetool not installed! vbetool not installed! /usr/lib/pm-utils/sleep.d/99video suspend suspend: success. Wed May 9 02:14:43 EDT 2012: performing suspend Wed May 9 02:19:39 EDT 2012: Awake. Wed May 9 02:19:39 EDT 2012: Running hooks for resume Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend: vbetool not installed! vbetool not installed! vbetool not installed! vbetool not installed! /usr/lib/pm-utils/sleep.d/99video resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: Saving last known working quirks: --quirk-vbe-post --quirk-dpms-on --quirk-dpms-suspend --quirk-vbestate-restore --quirk-vbemode-restore --quirk-vga-mode-3 /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/95packagekit resume suspend: ... Perhaps something related to vbetool or quirks ??? I was sort of hoping I could find something in /proc or /sys that describes the current video state -- any suggestions?
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.