Created attachment 627001 [details] dmesg output Description of problem: computer boots normally instead of resuming from hibernation since kernel 3.5. With my actual running kernel 3.4.6-2 resume/hibernation works like a charm Version-Release number of selected component (if applicable): kernel 3.6.1-1.fc17.i686.PAE fails at all How reproducible: hibernate the computer an reboot Steps to Reproduce: 1. hibernate 2. boot 3. Actual results: normal boot instead of resume from hibernation Expected results: reload the hibernation image correctly Additional info: couldn't find any helpful message either with dmesg nor in messages nor boot.log. the only I found out in dmesg is "PM: Hibernation image not present or could not be loaded." dmesg output added
resume from hibernation still fails with latest kernel 3.6.2-4.fc17.i686.PAE with message in dmesg output: PM: Hibernation image not present or could not be loaded.
Created attachment 632904 [details] dmesg output kernel 3.6.2-4
still the same error during resume from hibernation with latest kernel 3.6.9-2.fc17.i686.PAE: PM: Hibernation image not present or could not be loaded.
Does it work with resume=/dev/sda2 kernel boot parameter?
Yes, it works with this kernel parameter!
only for my clarification: is this not part of the kernel to find the swap partition itself or do I need to add the parameter permanently?
(In reply to comment #6) > only for my clarification: > > is this not part of the kernel to find the swap partition itself or do I > need to add the parameter permanently? I think this is job of dracut to autodetect your resume partition. Could you try to recreate your swap by: # swapoff /dev/sda2 # mkswap /dev/sda2 # swapon /dev/sda2 Let me know whether it helps.
No, recreation of swap partition didn't helped. on the other hand what I do not understand is why I have this issue only on one out of 3 operational fedora instances? And swap is always sda2 I guess...
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.