fedora 32: no hibernate/resume

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everybody

Environment here:

[root@caprioli ~]# cat /etc/fedora-release
Fedora release 32 (Thirty Two)
[root@caprioli ~]#


root@caprioli ~]# uname -r
5.6.10-300.fc32.x86_64
[root@caprioli ~]#

[root@caprioli ~]# grub2-editenv - list
saved_entry=966c5755b3384d1192dbf3d3658c1e29-5.6.10-300.fc32.x86_64
kernelopts=root=UUID=3f218a1e-7f30-48b1-add4-fb17bff5a6b5 ro resume=UUID=0d51db0e-8463-4741-8bbe-d907fb2b1cb2
boot_success=1
boot_indeterminate=0
[root@caprioli ~]#


[cellino@caprioli ~]$ cat /proc/cmdline
BOOT_IMAGE=(hd3,gpt5)/boot/vmlinuz-5.6.10-300.fc32.x86_64 root=UUID=3f218a1e-7f30-48b1-add4-fb17bff5a6b5 ro resume=UUID=0d51db0e-8463-4741-8bbe-d907fb2b1cb2
[cellino@caprioli ~]$


suspend works fine on this machine, but hibernate does›nt. Another installation on the same machine with fedora 31 hibernates/resumes flawlessly.

I assume very much that when closing down for hibernate, no image is created, because after booting up from (so to speak) hibernate, the last lines in the journal are:

[root@caprioli ~]# journalctl -b -1

<snip>

May 10 09:47:53 caprioli.dyn.lan systemd[1]: Reached target Sleep.
May 10 09:47:53 caprioli.dyn.lan systemd[1]: Starting Hibernate...
May 10 09:47:53 caprioli.dyn.lan kernel: PM: Image not found (code -22)
May 10 09:47:53 caprioli.dyn.lan kernel: PM: hibernation: hibernation entry
May 10 09:47:53 caprioli.dyn.lan systemd-sleep[3134]: Suspending system...
lines 2285-2371/2371 (END)

where the 3rd line tells me, that no image has been created and written to swap.

The swap partition has 19.6 GB. The memory is 16 GB. I tried to give the system a much larger (1 TB) swap partition, no joy.

I also tried to go down to runlevel 3 before hibernating, and then resume into runlevel 3: no joy.

I also tried to adapt the dracut command-line.

[root@caprioli ~]# dracut --print-cmdline
root=UUID=3f218a1e-7f30-48b1-add4-fb17bff5a6b5 rootfstype=ext4 rootflags=rw,relatime
[root@caprioli ~]#

to include the resume parameter, but dracut did not even take my dracut.conf file into consideration.

Because the Fedora 31 installation on the same machine works flawlessly as far as hibernate/resume is concerned, I assume the BIOS parameters are such, that suspending/resuming is allowed.
Does the Fedora 32 Kernel, by default, prevent hibernate/resume?

I am at a loss of ideas on how to investigate further.

Any hint is highly  appreciated. Thank you very much.

suomi

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux