Fails to wake up from hibernation

ltg · 2023-05-29 14:12:06

I'm new to arch, this system is just a few weeks old.

Set up the system by following the guide on https://wiki.archlinux.org/title/installation_guide
And set up hibernation by following the guide on https://wiki.archlinux.org/title/Power_ … _hibernate

It manages to wake up and reinstate the machine state sometimes, seems to be when i have restarted the laptop recently. But not consistently for some reason.

Using systemd-boot & swap partition
Hibernated by using systemctl hibernate

Journalctl -b
http://0x0.st/Hbsn.txt

Let me know if there is anything else you need to know.

Thanks!
Linus

(Sorry if i did something wrong with this post, it is the first time posting!)

Natpunk · 2023-05-30 00:22:38

Do you have Wayland or Xorg?

ltg · 2023-05-30 06:09:03

Natpunk wrote:

Do you have Wayland or Xorg?

I use Wayland with Hyprland currently.

seth · 2023-05-30 07:24:49

May 29 17:39:13 surface kernel: PM: Loading and decompressing image data (365884 pages)...
May 29 17:39:13 surface kernel: Hibernate inconsistent memory map detected!
May 29 17:39:13 surface kernel: PM: hibernation: Image mismatch: architecture specific data
May 29 17:39:13 surface kernel: PM: hibernation: Read 1463536 kbytes in 0.01 seconds (146353.60 MB/s)
May 29 17:39:13 surface kernel: PM: Error -1 resuming
May 29 17:39:13 surface kernel: PM: hibernation: Failed to load image, recovering.
May 29 17:39:13 surface kernel: PM: hibernation: Basic memory bitmaps freed
May 29 17:39:13 surface kernel: OOM killer enabled.
May 29 17:39:13 surface kernel: Restarting tasks ... done.
May 29 17:39:13 surface kernel: PM: hibernation: resume failed (-1)

May 29 17:39:14 surface kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

https://bugzilla.redhat.com/show_bug.cgi?id=1442601#c6
Are you changing anything about the HW condition when this fails (removing/adding devices, un/docking the notebook) or is there a parallel windows installation?

In addition: are there nvme errors in the previous boot?
You might have to https://wiki.archlinux.org/title/Solid_ … leshooting (iommu=soft and nvme_core.default_ps_max_latency_us=0)

ltg · 2023-05-30 07:52:02

seth wrote:

May 29 17:39:13 surface kernel: PM: Loading and decompressing image data (365884 pages)...
May 29 17:39:13 surface kernel: Hibernate inconsistent memory map detected!
May 29 17:39:13 surface kernel: PM: hibernation: Image mismatch: architecture specific data
May 29 17:39:13 surface kernel: PM: hibernation: Read 1463536 kbytes in 0.01 seconds (146353.60 MB/s)
May 29 17:39:13 surface kernel: PM: Error -1 resuming
May 29 17:39:13 surface kernel: PM: hibernation: Failed to load image, recovering.
May 29 17:39:13 surface kernel: PM: hibernation: Basic memory bitmaps freed
May 29 17:39:13 surface kernel: OOM killer enabled.
May 29 17:39:13 surface kernel: Restarting tasks ... done.
May 29 17:39:13 surface kernel: PM: hibernation: resume failed (-1)
May 29 17:39:14 surface kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
https://bugzilla.redhat.com/show_bug.cgi?id=1442601#c6
Are you changing anything about the HW condition when this fails (removing/adding devices, un/docking the notebook) or is there a parallel windows installation?
In addition: are there nvme errors in the previous boot?
You might have to https://wiki.archlinux.org/title/Solid_ … leshooting (iommu=soft and nvme_core.default_ps_max_latency_us=0)

The only OS on this machine is this arch install, booted using systemd-boot.

I do sometimes use a dock and some external screens but this problem persists while completely undocked as well.

normal reboot log:
https://0x0.st/HbXa.txt

reboot with the iommu=soft and latency set to 0:
https://0x0.st/HbXB.txt
It still fails to hibernate with these variables set, and to my untrained eye it looks like the log is giving the same errors.

Thanks!

seth · 2023-05-30 07:56:00

The filesystem is still corrupt and you need to fix that, the idea was more that whatever corrupted the filesystem might have corrupted the hibernation image (and that something possibly being APST)

ltg · 2023-05-30 08:24:26

seth wrote:

The filesystem is still corrupt and you need to fix that, the idea was more that whatever corrupted the filesystem might have corrupted the hibernation image (and that something possibly being APST)

I am pretty sure I fixed my filesystem now. Those specific errors are gone at least.

Here is the boot log, still fails to recover the system state.
https://0x0.st/HbXp.txt

Thank you for the assistance.

seth · 2023-05-30 14:30:33

May 30 12:20:04 surface kernel: Hibernate inconsistent memory map detected!
May 30 12:20:04 surface kernel: PM: hibernation: Image mismatch: architecture specific data
May 30 12:20:04 surface kernel: PM: hibernation: Read 3058920 kbytes in 0.01 seconds (305892.00 MB/s)
May 30 12:20:04 surface kernel: PM: Error -1 resuming
May 30 12:20:04 surface kernel: PM: hibernation: Failed to load image, recovering.
May 30 12:20:04 surface kernel: PM: hibernation: Basic memory bitmaps freed
May 30 12:20:04 surface kernel: OOM killer enabled.
May 30 12:20:04 surface kernel: Restarting tasks ... done.
May 30 12:20:04 surface kernel: PM: hibernation: resume failed (-1)

May 30 12:20:05 surface systemd-fsck[242]: fsck.fat 4.2 (2021-01-31)
May 30 12:20:05 surface systemd-fsck[242]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
May 30 12:20:05 surface systemd-fsck[242]:  Automatically removing dirty bit.
May 30 12:20:05 surface systemd-fsck[242]: *** Filesystem was changed ***
May 30 12:20:05 surface systemd-fsck[242]: Writing changes.
May 30 12:20:05 surface systemd-fsck[242]: /dev/nvme0n1p1: 15 files, 23849/261628 clusters

Might just be because of the failing resume (you hibernated w/ /boot mounted, wake up, fail to resume, so /boot was never properly unmounted)

May 30 12:20:04 surface kernel: DMI: Microsoft Corporation Surface Pro 7/Surface Pro 7, BIOS 15.11.140 07/08/2022

Is there a BIOS/Firmware update available?
Do you have secure boot enabled?
Can you trigger this when the notebook is permanently docked (ie. you boot on the dock, hibernate on the dock and resume on the dock and don't remove it from the dock ever during the test)?

ltg · 2023-05-30 19:46:08

seth wrote:

May 30 12:20:04 surface kernel: Hibernate inconsistent memory map detected!
May 30 12:20:04 surface kernel: PM: hibernation: Image mismatch: architecture specific data
May 30 12:20:04 surface kernel: PM: hibernation: Read 3058920 kbytes in 0.01 seconds (305892.00 MB/s)
May 30 12:20:04 surface kernel: PM: Error -1 resuming
May 30 12:20:04 surface kernel: PM: hibernation: Failed to load image, recovering.
May 30 12:20:04 surface kernel: PM: hibernation: Basic memory bitmaps freed
May 30 12:20:04 surface kernel: OOM killer enabled.
May 30 12:20:04 surface kernel: Restarting tasks ... done.
May 30 12:20:04 surface kernel: PM: hibernation: resume failed (-1)

May 30 12:20:05 surface systemd-fsck[242]: fsck.fat 4.2 (2021-01-31)
May 30 12:20:05 surface systemd-fsck[242]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
May 30 12:20:05 surface systemd-fsck[242]:  Automatically removing dirty bit.
May 30 12:20:05 surface systemd-fsck[242]: *** Filesystem was changed ***
May 30 12:20:05 surface systemd-fsck[242]: Writing changes.
May 30 12:20:05 surface systemd-fsck[242]: /dev/nvme0n1p1: 15 files, 23849/261628 clusters

Might just be because of the failing resume (you hibernated w/ /boot mounted, wake up, fail to resume, so /boot was never properly unmounted)

May 30 12:20:04 surface kernel: DMI: Microsoft Corporation Surface Pro 7/Surface Pro 7, BIOS 15.11.140 07/08/2022

Is there a BIOS/Firmware update available?
Do you have secure boot enabled?
Can you trigger this when the notebook is permanently docked (ie. you boot on the dock, hibernate on the dock and resume on the dock and don't remove it from the dock ever during the test)?

I updated the firmware with the "latest"(doesnt seem very late though) just a few weeks ago before switching to Arch.

I do have secure boot enabled and working.

Can try to trigger this while docked tomorrow when I am back at my docking station.

On the topic of the /boot mount. When i manually unmount it and then hibernate it seems like I have better odds to get a successful hibernation. Still pretty rare for it to come back successfully though.

Here is a successful hibernation:
https://0x0.st/HbNE.txt

Here is a failed one even though /boot was unmounted prior:
https://0x0.st/HbNg.txt

thanks again!

seth · 2023-05-30 20:09:33

I do have secure boot enabled and working.

I'd try to disable that…

Arch Linux

#1 2023-05-29 14:12:06

Fails to wake up from hibernation

#2 2023-05-30 00:22:38

Re: Fails to wake up from hibernation

#3 2023-05-30 06:09:03

Re: Fails to wake up from hibernation

#4 2023-05-30 07:24:49

Re: Fails to wake up from hibernation

#5 2023-05-30 07:52:02

Re: Fails to wake up from hibernation

#6 2023-05-30 07:56:00

Re: Fails to wake up from hibernation

#7 2023-05-30 08:24:26

Re: Fails to wake up from hibernation

#8 2023-05-30 14:30:33

Re: Fails to wake up from hibernation

#9 2023-05-30 19:46:08

Re: Fails to wake up from hibernation

#10 2023-05-30 20:09:33

Re: Fails to wake up from hibernation

Board footer