Problem with resume from hibernation

My new TW/KDE system will not resume from hibernation but always reboots instead. This is new hardware and has never resumed since it was installed, the old hardware (also UEFI) used to resume just fine. Looking at the journal I can see:-


Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0x09d82000-0x09ffffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0x0a200000-0x0a20afff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0x0b000000-0x0b01ffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd7233000-0xd7233fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd7240000-0xd7240fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd7241000-0xd7241fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd724f000-0xd724ffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd7309000-0xd7365fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd7367000-0xd7367fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd736f000-0xd736ffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xd739d000-0xd739dfff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xdb5b7000-0xdb6d5fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xdbb56000-0xdbc63fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xdbc64000-0xdcb56fff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xdf000000-0xdfffffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xf7ffffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xfc000000-0xfcffffff]
Oct 22 09:18:11 Tumbleweed kernel: PM: hibernation: Registered nosave memory: [mem 0xfd000000-0xffffffff]


but the strange thing is that these happen on a normal boot as well as an attempt to resume which ends in a boot.

I have run memtest86 but no errors - this is a new system with a new install. My total memory is 16gb and my swap is 32gb (I plan to add another 16gb). Now I have no idea if these messages actually are a problem or not. The only messages relating to resume were:-


Oct 22 09:18:11 Tumbleweed kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.14-1-default root=UUID=190442a2-32b3-47e7-bac7-a39e6841236f splash=silent resume=/dev/disk/by-id/nvme-KINGSTON_SA2000M8250G_50026B728266A552-part3 quiet mitigations=auto
Oct 22 09:18:11 Tumbleweed kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.8.14-1-default root=UUID=190442a2-32b3-47e7-bac7-a39e6841236f splash=silent resume=/dev/disk/by-id/nvme-KINGSTON_SA2000M8250G_50026B728266A552-part3 quiet mitigations=auto
Oct 22 09:18:11 Tumbleweed dracut-cmdline[255]: Using kernel command line parameters: root=UUID=190442a2-32b3-47e7-bac7-a39e6841236f rootfstype=ext4 rootflags=rw,relatime BOOT_IMAGE=/boot/vmlinuz-5.8.14-1-default root=UUID=190442a2-32b3-47e7-bac7-a39e6841236f splash=silent resume=/dev/disk/by-id/nvme-KINGSTON_SA2000M8250G_50026B728266A552-part3 quiet mitigations=auto

Anyone any ideas why this wont resume or how to move forwards with diagnosing it?

Stuart

I see the same thing on my laptop. What’s interesting is that I have been rolling with TW for a few months now and have always used Hybrid Sleep which works okay.
Just 2 days ago i switched to hibernation and when I wake up the laptop I only see a black screen on my laptop and external monitor with a mouse that does not move.
Ctrl+Alt+ any F key does nothing and I have to do a hard reset.
After the reboot my laptop screen is not working and the system moves in slow motion meaning when I click, the system responds about 2 seconds later until I get the laptop monitor back on and then it responds normally.

Operating System: openSUSE Tumbleweed 20201021
KDE Plasma Version: 5.20.0
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.8.15-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

I also have a laptop running an i7 3537U also with TW/KDE and just checked and I also see those messages but the laptop boots just fine. I have also tried hibernation on it and resume works fine.

Stuart

I have just updated this laptop today and re-tested hibernate resume and all worked OK. The journal shows these messages:-


Oct 23 11:24:30 ASUS-Tumbleweed kernel: PM: hibernation: hibernation entry
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000fffff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0x20000000-0x201fffff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0x40004000-0x40004fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbc321000-0xbc335fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbd75c000-0xbd75dfff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbd75f000-0xbd762fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbd768000-0xbdd6bfff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdd7c000-0xbdd7ffff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdd81000-0xbdd86fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdf32000-0xbdf35fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdf7f000-0xbdf80fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdf83000-0xbdf94fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdf98000-0xbdf99fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdfb1000-0xbdfb6fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdfc5000-0xbdfc5fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdfc8000-0xbdfc8fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbdfd4000-0xbdfd8fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe005000-0xbe005fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe016000-0xbe03bfff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe04f000-0xbe04ffff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe051000-0xbe052fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe054000-0xbe058fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe06e000-0xbe897fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbe899000-0xbe8dbfff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbecec000-0xbeff3fff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Marking nosave pages: [mem 0xbf000000-0xffffffff]
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Basic memory bitmaps created
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Preallocating image memory
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Allocated 420117 pages for snapshot
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Allocated 1680468 kbytes in 0.40 seconds (4201.17 MB/s)
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Creating image:
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Need to copy 414443 pages
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Normal pages needed: 414443 + 1024, available pages: 1538594
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: Basic memory bitmaps freed
Oct 23 11:25:13 ASUS-Tumbleweed kernel: PM: hibernation: hibernation exit


so those messages are not stopping the resume.

So where to now debugging this on the desktop which will not resume?

Stuart

  1. Diagnosing Boot Problems
  2. Diagnosing Shutdown Problems
  3. Status and Logs of Services
  4. Reporting systemd Bugs

I’ll take a look at that but I don’t have any boot or shutdown issues per se, hibernate finishes and turns off the PC, boot boots normally with no apparent issues except it should have resumed!

I’ll scan the journal some more to try to find and indications there as to what might have gone wrong and see if anything turns up.

Stuart

There’s nothing untoward in those messages, the repeated “Marking nosave pages” is normal, it’s not necessary to save those memory pages.

So where to now debugging this on the desktop which will not resume?

In addition to the links that @karlmistelberger provided, you may find the following useful if you decide to investigate further.

Debugging hibernation and suspend.Debugging hibernation and suspend — The Linux Kernel documentation

Personally, I’ve always found hibernate/resume to be rather hit and miss, in the past kernel updates have caused a working system to fail and also vice versa. I’ve long gave up on it. Maybe some hardware is better suited than others, or perhaps it’s just down to the phase of the moon etc…

Just ran memtest and had errors, guess I’ll just keep using hybrid sleep and not hibernate.