Laptop hangs while going to suspend (S3)

karthanistyr · 2024-10-13 21:24:54

Hi,

my Asus UX330UAK (Intel i5-7200U) has been having suspend issues for a good few months now and I'm only now trying to fix them.

Symptoms:
When attempting to suspend, the laptop will frequently (not always) fail to go to S3: screen turns off, keyboard backlight turns off but the fan keeps spinning and the power LED stays on. The system becomes unresponsive (cannot wakeup and cannot switch to a tty) and I must power-cycle the machine by long-pressing the power button.
As I mentioned, this does not always happen: my experience is that the longer the system has been running, the more likely it is to lock up on suspend. On fresh boots, the tests for going to suspend work well, but after leaving the machine unattended for a few hours, an attempt to suspend has so far always locked up the machine.

The machine has the latest BIOS installed (315), and is running the latest kernel to date (as of writing: Linux 6.11.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 30 Sep 2024 23:49:50 +0000 x86_64 GNU/Linux)

It's been happening for many months and many kernel versions.

Following instructions found on https://www.kernel.org/doc/html/latest/power/s2ram.html, I got the following trace in dmesg:

[    0.499445] PM:   Magic number: 15:303:178
[    0.499519] acpi device:0e: hash matches
[    0.499534]  platform: hash matches

I could not investigate further for lack of understanding on what is exactly "device:0e" and how to figure this out.

Thanks for any pointers into how to proceed from there ! Cheers.

[Edit]
As an example, a failed suspend leaves the following dmesg (last line is the last entry before I have to power cycle):

sept. 13 23:12:31 karth-dev-book systemd-logind[561]: Lid closed.
sept. 13 23:12:31 karth-dev-book pulseaudio[18428]: dbus: path=/org/freedesktop/UPower, interface=org.freedesktop.DBus.Properties, member=PropertiesChanged
sept. 13 23:12:31 karth-dev-book systemd-logind[561]: Suspending...
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8679] manager: sleep: sleep requested (sleeping: no  enabled: yes)
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8681] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8686] device (58:E2:8F:62:8A:AC): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8692] manager: NetworkManager state is now ASLEEP
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8695] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8696] dhcp4 (wlp2s0): canceled DHCP transaction
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8696] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8696] dhcp4 (wlp2s0): state changed no lease
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8698] dhcp6 (wlp2s0): canceled DHCP transaction
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8698] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
sept. 13 23:12:31 karth-dev-book NetworkManager[554]: <info>  [1726261951.8698] dhcp6 (wlp2s0): state changed no lease
sept. 13 23:12:31 karth-dev-book systemd-resolved[535]: wlp2s0: Bus client reset search domain list.
sept. 13 23:12:31 karth-dev-book systemd-resolved[535]: wlp2s0: Bus client set default route setting: no
sept. 13 23:12:31 karth-dev-book avahi-daemon[556]: Withdrawing address record for 192.168.37.55 on wlp2s0.
sept. 13 23:12:31 karth-dev-book systemd-resolved[535]: wlp2s0: Bus client reset DNS server list.
sept. 13 23:12:31 karth-dev-book avahi-daemon[556]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.37.55.
sept. 13 23:12:31 karth-dev-book avahi-daemon[556]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
sept. 13 23:12:31 karth-dev-book avahi-daemon[556]: Withdrawing address record for fe80::4b35:bc5:5bf3:ccdb on wlp2s0.
sept. 13 23:12:31 karth-dev-book avahi-daemon[556]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::4b35:bc5:5bf3:ccdb.
sept. 13 23:12:31 karth-dev-book avahi-daemon[556]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
sept. 13 23:12:31 karth-dev-book systemd[1]: Starting Network Manager Script Dispatcher Service...
sept. 13 23:12:31 karth-dev-book systemd[1]: Started Network Manager Script Dispatcher Service.
sept. 13 23:12:31 karth-dev-book kernel: wlp2s0: deauthenticating from 9c:a2:f4:68:99:09 by local choice (Reason: 3=DEAUTH_LEAVING)
sept. 13 23:12:31 karth-dev-book systemd-networkd[367]: wlp2s0: Lost carrier
sept. 13 23:12:31 karth-dev-book systemd-timesyncd[536]: No network connectivity, watching for changes.
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: nl80211: send_event_marker failed: Source based routing not supported
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=9c:a2:f4:68:99:09 reason=3 locally_generated=1
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.0964] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
sept. 13 23:12:32 karth-dev-book systemd-networkd[367]: wlp2s0: Link DOWN
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.1368] device (wlp2s0): set-hw-addr: set MAC address to A6:CD:E4:95:5E:98 (scanning)
sept. 13 23:12:32 karth-dev-book systemd-networkd[367]: wlp2s0: Link UP
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.1509] device (wlp2s0): supplicant interface state: completed -> disconnected
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.1513] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.1516] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.1520] device (wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
sept. 13 23:12:32 karth-dev-book kernel: usb 1-5: new full-speed USB device number 16 using xhci_hcd
sept. 13 23:12:32 karth-dev-book systemd-networkd[367]: wlp2s0: Link DOWN
sept. 13 23:12:32 karth-dev-book NetworkManager[554]: <info>  [1726261952.4213] device (wlp2s0): set-hw-addr: reset MAC address to 34:F3:9A:A4:4E:03 (unmanage)
sept. 13 23:12:32 karth-dev-book systemd-networkd[367]: wlp2s0: Link UP
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
sept. 13 23:12:32 karth-dev-book systemd[1]: Reached target Sleep.
sept. 13 23:12:32 karth-dev-book systemd[1]: Starting System Suspend...
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
sept. 13 23:12:32 karth-dev-book wpa_supplicant[613]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
sept. 13 23:12:32 karth-dev-book systemd-sleep[25221]: Successfully froze unit 'user.slice'.
sept. 13 23:12:32 karth-dev-book systemd-sleep[25221]: Performing sleep operation 'suspend'...
sept. 13 23:12:32 karth-dev-book kernel: PM: suspend entry (deep)

While a successful one will have such lines:

...
oct. 12 10:46:07 karth-dev-book kernel: PM: suspend entry (deep)
oct. 12 10:46:07 karth-dev-book kernel: Filesystems sync: 0.006 seconds
oct. 12 10:46:22 karth-dev-book kernel: Freezing user space processes
oct. 12 10:46:22 karth-dev-book kernel: Freezing user space processes completed (elapsed 0.001 seconds)
oct. 12 10:46:22 karth-dev-book kernel: OOM killer disabled.
...

Last edited by karthanistyr (2024-10-13 21:40:19)

gromit · 2024-10-14 20:22:56

So did this ever work? If so, which upgrade made it break?

Last edited by gromit (2024-10-14 20:23:04)

karthanistyr · 2024-10-14 20:47:05

Hi, thanks for your reply.

Yes it did work flawlessly for a number of years since I first installed arch back in 2017. I suspect a kernel upgrade might have broken it some time last year, but I can't recall very specifically. I see some people on the internet complain about a regression in 6.1, or with issues regarding video drivers (mostly about AMD, but I have an intel chipset), but I can't be certain. LTS kernel (6.6.56) is showing the same behaviour as far as I can tell.

I just don't know how to investigate further than what I described in OP.

gromit · 2024-10-14 21:17:59

Could you maybe try a few older kernels to narrow it down a bit? https://archive.archlinux.org/packages/l/linux/

lnvd · 2024-11-30 13:19:24

I got the exact same issue on my Asus UX310, but the first time this happened to me was at least a year ago.
Inspired by this thread, I went all the way back to 5.15.94-1-lts (needs decompressed firmware files!) and it actually fixed my problem as far as I can tell. Not a single failure in two weeks while it used to happen every other day.
I'll try to bisect, but that could take a while.
@karthanistyr have you tried other versions in the meantime?

gromit · 2024-12-04 15:07:50

If you want I could also provide you with prebuilt kernels in order to speed up the bisection ..

Last edited by gromit (2024-12-04 15:08:00)

lnvd · 2024-12-04 16:16:00

gromit wrote:

If you want I could also provide you with prebuilt kernels in order to speed up the bisection ..

thank you, but what's slowing me down here is the unreliable reproduction. I want each iteration to see some day to day usage to at least get some confidence on whether it's good.

002445 · 2024-12-04 21:09:23

I might have the same issue on an Asus UX430UA (i5-8250). Every time it tries to go to sleep it crashes as described in the first post and I need to power cycle it by holding down the power button.

What makes the laptop not crash is a simple (fish) script to reset the xdg-screensaver timer every minute so it simply never goes to sleep.

while true
      xdg-screensaver reset
      sleep 60
end

I installed Arch on this laptop this past 4th of September and the issue was there from the beginning. I used Manjaro since I got the laptop somewhere around 2018 before I installed Arch and I remember it was on some version of Kernel 5.X before I reinstalled it with Arch.

karthanistyr · 2024-12-26 20:36:16

So I went back to 6.0 for a good few weeks and got no issues with suspend. 6.1 did exhibit issues.

Something may have changed in 6.12 though. I let my machine update by mistake and ran 6.12 for a while and suspend seems to perhaps have been fixed on that release as it looks reliable again for the first time in a long while.

Linux 6.12.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 09 Dec 2024 14:31:57 +0000 x86_64 GNU/Linux

I admit I don't have the resources to hunt down the possible issue and fix in commits unfortunately.

lnvd · 2025-01-07 09:08:03

I'm glad it's working for you! I hope it remains stable as I tried 6.12.7 without success.
The most recent version that seems stable for me is 6.1.71-1-lts.
I know that 6.3.9 is "bad", but I didn't have any success booting a non-lts 6.2 or 6.1 version as it drops me into an unresponsive emergency shell.
I guess I'll cling to 6.1.71-1-lts for now.

karthanistyr · 2025-01-07 11:12:03

Yeah well I did speak too soon. It’s happening less but it is still happening. So that’s a false hope on 6.12 sorry.

Arch Linux

#1 2024-10-13 21:24:54

Laptop hangs while going to suspend (S3)

#2 2024-10-14 20:22:56

Re: Laptop hangs while going to suspend (S3)

#3 2024-10-14 20:47:05

Re: Laptop hangs while going to suspend (S3)

#4 2024-10-14 21:17:59

Re: Laptop hangs while going to suspend (S3)

#5 2024-11-30 13:19:24

Re: Laptop hangs while going to suspend (S3)

#6 2024-12-04 15:07:50

Re: Laptop hangs while going to suspend (S3)

#7 2024-12-04 16:16:00

Re: Laptop hangs while going to suspend (S3)

#8 2024-12-04 21:09:23

Re: Laptop hangs while going to suspend (S3)

#9 2024-12-26 20:36:16

Re: Laptop hangs while going to suspend (S3)

#10 2025-01-07 09:08:03

Re: Laptop hangs while going to suspend (S3)

#11 2025-01-07 11:12:03

Re: Laptop hangs while going to suspend (S3)

Board footer