Bug 1199708
| Summary: | System does not wake up from hibernation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vít Ondruch <vondruch> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | bugzilla, gansalmon, greta_watson, Irwin.Sobel, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, sohnythomas | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-08-18 17:38:47 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Vít Ondruch
2015-03-07 09:34:17 UTC
The system was successfully put into hibernation with 'systemctl hibernate' and systemd thinks hibernation is possible. [ 30.489423] f22m.localdomain systemd-logind[747]: Hibernation is possible, Active(anon)=202204 kB, size=8388604 kB, used=0 kB, threshold=98% Later, when I press the power button, it boot like normal - there's no resume from hibernation. There's the same seemingly bogus message as this report "kernel: PM: Hibernation image not present or could not be loaded." Is the kernel supposed to find the image or systemd though? kernel-4.0.0-1.fc22.x86_64 systemd-219-11.fc22.x86_64 This is not a regression, as far as I'm aware, it's never worked. Fails on both Apple EFI hardware, as well as a Dell XPS UEFI system. Created attachment 1015968 [details]
journalctl, systemctl hibernate, debug
Created attachment 1015969 [details]
journalctl, resume from hibernate, debug
I've seen this bug in a number of previous Fedora releases. I'm currently experiencing it in Fedora 20, with kernel 3.19.5-100.fc20.x86_64, and systemd-208-30.fc20.x86_64. journalctl -b | grep ibernate gives the following: May 04 00:17:47 sparky kernel: PM: Hibernation image not present or could not be loaded. May 04 00:17:47 sparky kernel: PM: Hibernation image partition 8:51 present May 04 00:17:47 sparky kernel: PM: Looking for hibernation image. May 04 00:17:47 sparky kernel: PM: Hibernation image not present or could not be loaded. In previous versions, the bug has gone away or been fixed at some point. On 3.19.8-100.fc20.x86_64 #1 SMP with Gnome 3.10.2 on HP Z800 (5.8GBRAM, 12 cores) with NVidia Quadro FX 4800 Graphics (Driver 340.76) (Power Switch hibernate worked on previous kernels with restart bypassing BIOS) Now it fails apparently not writing the image file, judging from lack of significant disk activity. Subsequent power-on yields blank screen with <ctrl><alt><F2> giving only blinking active cursor. pm-suspend does work, but power-on goes through BIOS and grub before state is restored. systemctl hibernate fails as with power switch method (In reply to Chris Murphy from comment #1) > The system was successfully put into hibernation with 'systemctl hibernate' > and systemd thinks hibernation is possible. > > [ 30.489423] f22m.localdomain systemd-logind[747]: Hibernation is > possible, Active(anon)=202204 kB, size=8388604 kB, used=0 kB, threshold=98% > > Later, when I press the power button, it boot like normal - there's no > resume from hibernation. There's the same seemingly bogus message as this > report "kernel: PM: Hibernation image not present or could not be loaded." > > Is the kernel supposed to find the image or systemd though? probably this bug may help https://bugzilla.redhat.com/show_bug.cgi?id=1213131 (In reply to sohny thomas from comment #7) This might be workaround, but not solution. I don't have such parameter on other systems and they work just fine. Moreover, I believe that it should depend on kernel parameter in initram, which looks pretty reasonable: # dracut --print-cmdline rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap resume=/dev/mapper/fedora-swap root=/dev/mapper/fedora-root rootfstype=ext4 rootflags=rw,relatime,seclabel,data=ordered *** This bug has been marked as a duplicate of bug 1206912 *** |