Arch Linux

SomeRandomDude

Member

Registered: 2023-01-18

Posts: 5

Suspend hibernate failing to hibernate

Hey, for the last couple of weeks I've noticed that every time I close my laptop lid, it goes to sleep but once it tries to hibernate, the laptop wakes up, the fan spins up, drains the battery and/or the laptop gets very hot.

It used to work as expected before (can't really point to an exact version or date as I no longer use it on a daily basis), I'm running a ThinkPad E15 with a Ryzen 7 5825U running kernel 6.8.9. This is the relevant configuration from /etc/systemd/sleep.conf:

[Sleep]
AllowSuspend=yes
AllowHibernation=yes
AllowSuspendThenHibernate=yes

SuspendMode=suspend
SuspendState=mem standby freeze

HibernateMode=shutdown
HibernateState=disk
HibernateDelaySec=90min

And I also looked at the logs from the previous boot, I found this at the end:

may 07 14:32:17 ThinkPad kernel: PM: hibernation: Allocated 1491418 pages for snapshot
may 07 14:32:17 ThinkPad kernel: PM: hibernation: Allocated 5965672 kbytes in 9.26 seconds (644.24 MB/s)
may 07 14:32:17 ThinkPad kernel: Freezing remaining freezable tasks
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 5) timeout
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xff472700 flags=0x0000]
may 07 14:32:17 ThinkPad kernel: Freezing remaining freezable tasks completed (elapsed 0.422 seconds)
may 07 14:32:17 ThinkPad kernel: printk: Suspending console(s) (use no_console_suspend to debug)
may 07 14:32:17 ThinkPad kernel: amdgpu 0000:05:00.0: amdgpu: MODE2 reset
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 6) timeout
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xffcf6700 flags=0x0000]
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 7) timeout
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xfec5d700 flags=0x0000]
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 8) timeout
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xffc6af80 flags=0x0000]
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 9) timeout
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xffbcaf80 flags=0x0000]
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 10) timeout
may 07 14:32:17 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xff0aff80 flags=0x0000]
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00000010 (seq 11) timeout
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: Failed to get patch semaphore
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: chip reset failed
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: Message 00020007 (seq 12) timeout
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: PM: pci_pm_freeze(): mt7921_pci_suspend+0x0/0x240 [mt7921e] returns -110
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: PM: dpm_run_callback(): pci_pm_freeze+0x0/0xc0 returns -110
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: PM: failed to freeze async: error -110
may 07 14:32:51 ThinkPad kernel: mt7921e 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xfffe7790 flags=0x0000]

I did some digging and the wiki points to an issue with AMD and kernel 6 and above that seems to have been resolved. I think this is not the issue because it seems to be fixed in 6.1 but I'll leave it here in case it is.