Laptop freeze on suspend [SOLVED]

markJT · 2023-05-24 20:58:24

Hi all,

I'm looking for some help in how to identify the possible cause of an issue I've been having for a couple of months now - my laptop won't awake from suspend mode. The screen wakes up and shows the last state captured prior to suspend mode, but is then completely frozen; all display elements are fixed and keyboard input won't work. The keyboard command to switch to another TTY also doesn't work (e.g. CTRL, FN, ALT + F2). The only thing I can action is a hard reboot of my laptop using the power button.

I'm running Arch on a Dell XPS 13 9350 with the most up-to-date system BIOS (although for some time I have had a firmware warning thrown which may or may not be related - see below output from dmesg -l err). I recently moved to tiling windows manager sway after having used i3wm for many years. At first I thought the issue may be with sway/wayland, but I've tested just from outside of sway, in the linux console, and the issue still occurs there.

I don't quite know where to begin to diagnose this issue, but I'll share a few outputs in case that's a useful starting point - if someone could give me some steer on where to look next that would be much appreciated. Thanks.

Output of:

dmesg -l err

[    0.124725] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000007b800000-0x000000007fffffff], contact BIOS vendor for fixes
[    0.155911] x86/cpu: SGX disabled by BIOS.
[   10.439831] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8
[   10.487103] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   10.489204] Bluetooth: hci0: BCM: 'brcm/BCM4350C5-0a5c-6412.hcd'
[   10.491211] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-6412.hcd'
[   10.845029] brcmfmac_wcc: brcmf_wcc_attach: executing
[   10.847045] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   10.848113] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4350/8 wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176

dmesg -l warn

[    0.124731] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000007b800000-0x000000007fffffff]
               BIOS vendor: Dell Inc.; Ver: 1.13.0; Product Version: 
[    0.191565] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.191565] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[    0.191587]  #3
[    0.199645] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.817112] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
[    1.641771] i8042: Warning: Keylock active
[    1.659127] usb: port power management may be unreliable
[    8.484210] memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=1 'systemd'
[    8.752302] vboxdrv: loading out-of-tree module taints kernel.
[    8.811040] VBoxNetAdp: Successfully started.
[    8.816520] VBoxNetFlt: Successfully started.
[    8.960707] systemd-journald[225]: File /var/log/journal/d4bab06332244ecfae6cac37e916e231/system.journal corrupted or uncleanly shut down, renaming and replacing.
[    9.477744] ACPI Warning: \_SB.IETM._ART: Return Package type mismatch at index 0 - found Integer, expected Reference (20221020/nspredef-260)
[    9.477756] _ART package 0 is invalid, ignored
[   10.041420] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   10.334895] snd_hda_intel 0000:00:1f.3: NHLT table not found
[   10.449387] brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.Dell Inc.-XPS 13 9350.bin failed with error -2
[   10.498064] brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.txt failed with error -2
[   10.501418] brcmfmac 0000:3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.clm_blob failed with error -2

A sample of the most recent output from journalctl -b -1 following suspend, freeze and then hard reboot:

May 24 21:38:50 hostname NetworkManager[418]: <warn>  [1684960730.5107] platform-linux: do-add-ip6-address[2: fe80::134d:d127:30eb:8f51]: failure 13 (Permission denie>
May 24 21:38:52 hostname NetworkManager[418]: <warn>  [1684960732.5132] platform-linux: do-add-ip6-address[2: fe80::8f94:57e0:ef89:60e9]: failure 13 (Permission denie>
May 24 21:38:54 hostname systemd-logind[375]: The system will suspend now!
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.3841] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.3842] device (p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-ifac>
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.3847] manager: NetworkManager state is now ASLEEP
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.3850] device (wlp58s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state:>
May 24 21:38:54 hostname dbus-daemon[366]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.serv>
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.3991] device (tun0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'rem>
May 24 21:38:54 hostname systemd[1]: Starting Network Manager Script Dispatcher Service...
May 24 21:38:54 hostname dbus-daemon[366]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 24 21:38:54 hostname systemd[1]: Started Network Manager Script Dispatcher Service.
May 24 21:38:54 hostname wpa_supplicant[384]: wlp58s0: CTRL-EVENT-DISCONNECTED bssid=22:b0:01:bf:b3:d5 reason=3 locally_generated=1
May 24 21:38:54 hostname wpa_supplicant[384]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4186] device (wlp58s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-sta>
May 24 21:38:54 hostname wpa_supplicant[384]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4188] dhcp4 (wlp58s0): canceled DHCP transaction
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4188] dhcp4 (wlp58s0): activation: beginning transaction (timeout in 45 seconds)
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4188] dhcp4 (wlp58s0): state changed no lease
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4190] dhcp6 (wlp58s0): canceled DHCP transaction
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4190] dhcp6 (wlp58s0): activation: beginning transaction (timeout in 45 seconds)
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.4190] dhcp6 (wlp58s0): state changed no lease
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.9389] device (wlp58s0): set-hw-addr: set MAC address to 0E:DD:67:01:5D:CC (scanning)
May 24 21:38:54 hostname expressvpnd[2182]: RTNETLINK answers: No such process
May 24 21:38:54 hostname expressvpnd[2184]: RTNETLINK answers: No such process
May 24 21:38:54 hostname expressvpnd[2186]: RTNETLINK answers: No such process
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.9849] device (wlp58s0): supplicant interface state: completed -> disconnected
May 24 21:38:54 hostname NetworkManager[418]: <info>  [1684960734.9855] device (wlp58s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state:>
May 24 21:38:55 hostname NetworkManager[418]: <info>  [1684960735.5050] device (wlp58s0): set-hw-addr: reset MAC address to 74:DF:BF:31:92:3B (unmanage)
May 24 21:38:55 hostname wpa_supplicant[384]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
May 24 21:38:55 hostname wpa_supplicant[384]: p2p-dev-wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
May 24 21:38:55 hostname wpa_supplicant[384]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0
May 24 21:38:55 hostname systemd[1]: Reached target Sleep.
May 24 21:38:55 hostname wpa_supplicant[384]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
May 24 21:38:55 hostname systemd[1]: Starting System Suspend...
May 24 21:38:55 hostname wpa_supplicant[384]: wlp58s0: CTRL-EVENT-DSCP-POLICY clear_all
May 24 21:38:55 hostname wpa_supplicant[384]: nl80211: deinit ifname=wlp58s0 disabled_11b_rates=0
May 24 21:38:55 hostname systemd-sleep[2213]: Entering sleep state 'suspend'...
May 24 21:38:55 hostname kernel: PM: suspend entry (deep)

In order to accommodate some scaling issues as well, I recently applied some environment variables directly in /etc/environment

 GDK_BACKEND=wayland
 GDK_DPI_SCALE=0.6

Lastly, when configuring my machine originally (around 2016 now), there were also some recommendations at the time for some system-specific details in /etc/modprobe.d/i915.conf. I believe some of these relate to power saving. These are below:

options i915 enable_fbc=1 enable_psr=0

And the opening section of my /etc/mkinitcpio.conf below (sharing in case I'm pulling in these modules incorrectly).

# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="i915 intel_agp nvme"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES="/etc/modprobe.d/modprobe.conf"

Any support is much appreciated!

Thx

Last edited by markJT (2023-10-31 20:22:42)

V1del · 2023-05-24 21:45:08

See https://bbs.archlinux.org/viewtopic.php?id=285948 which mentions a suspension freeze due to the brcmfmac driver with a potential workaround and a possibly fixing patch that landed in the 6.3.4 kernel, which will likely be packaged shortly is currently in core-testing: https://archlinux.org/packages/core-tes … _64/linux/

Last edited by V1del (2023-05-24 21:47:44)

markJT · 2023-06-06 19:58:13

Thanks v1del. That possible fixing patch - do you know if that's been released?

I'm on kernel 6.3.5-arch1-1 - am I right in thinking that potential patch may be coming now in 6.3.6?

V1del · 2023-06-06 21:28:15

The possibly fixing patch is/was part of 6.3.4. if this didn't fix it then this won't have been the patch to fix the issue. In order to properly identify the issue you'd have to bisect the kernel https://wiki.archlinux.org/title/Bisect … s_with_Git

kamocat · 2023-06-07 22:02:06

I'm having a similar issue, but the LTS kernel doesn't seem to have a workaround anymore,
Plugging in a USB mouse or keyboard didn't help either.
Any suggestions?

markJT · 2023-10-31 20:20:13

Just to note that the issue now appears to have resolved for me, possibly with a patch in subsequent kernel updates since the issue occurred. As a temporary measure, I had modified /etc/systemd/logind.conf to uncomment:

HandleLidSwitch=ignore

This meant that closing the lid on my laptop for a while would not enter suspend mode, which was usefully practical for portability but frustrating as I wasn't able to save battery life in clamshell mode.

I've reverted this change today and it seems like suspend mode is working again, with no freezing occuring.

Thanks all for initial replies.

markJT · 2023-10-31 20:21:21

Just to note that the issue now appears to have resolved for me, possibly with a patch in subsequent kernel updates since the issue occurred. As a temporary measure, I had modified /etc/systemd/logind.conf to uncomment:

HandleLidSwitch=ignore

This meant that closing the lid on my laptop for a while would not enter suspend mode, which was usefully practical for portability but frustrating as I wasn't able to save battery life in clamshell mode.

I've reverted this change today and it seems like suspend mode is working again, with no freezing occuring.

Thanks all for initial replies.

Arch Linux

#1 2023-05-24 20:58:24

Laptop freeze on suspend [SOLVED]

#2 2023-05-24 21:45:08

Re: Laptop freeze on suspend [SOLVED]

#3 2023-06-06 19:58:13

Re: Laptop freeze on suspend [SOLVED]

#4 2023-06-06 21:28:15

Re: Laptop freeze on suspend [SOLVED]

#5 2023-06-07 22:02:06

Re: Laptop freeze on suspend [SOLVED]

#6 2023-10-31 20:20:13

Re: Laptop freeze on suspend [SOLVED]

#7 2023-10-31 20:21:21

Re: Laptop freeze on suspend [SOLVED]

Board footer