You are not logged in.

#1 2024-02-01 15:31:50

qwemaze
Member
Registered: 2018-10-01
Posts: 12

Screen freeze on wake after suspend

After one of the recent system updates I am no longer able to wake up the system from suspend.
Keyboard backlight lights up, but the screen remains frozen, unable to open F2-F4 terminals, only able to hold power button till full shutdown.

Host: 21CF003DMX ThinkPad T14 Gen 3
Kernel: 6.7.2-arch1-2
CPU: AMD Ryzen 7 PRO 6850U with Radeon Graphics (16) @ 4.768GHz
GPU: AMD ATI Radeon 680M

I've tried running powertop calibrate and auto-tune with an assumption that it's a powermanagement issue -- didn't help.

Also found https://bbs.archlinux.org/viewtopic.php … 8#p1873058
Tried amd_iomm=off kernel param and xorg config suggested there -- didn't help.

Here's journalctl -r from the moment of suspension via power key to next boot:

-- Boot 38bd8ebe7a8843e89445913dfc4da58c --
Feb 01 16:22:37 zoopmaze systemd-sleep[7087]: Performing sleep operation 'suspend'...
Feb 01 16:22:37 zoopmaze systemd[1]: Starting System Suspend...
Feb 01 16:22:37 zoopmaze wpa_supplicant[2526]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 01 16:22:37 zoopmaze wpa_supplicant[2526]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=NO
Feb 01 16:22:37 zoopmaze systemd[1]: Reached target Sleep.
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.9639] device (wlp2s0): set-hw-addr: reset MAC address to 04:7B:CB:B8:88:40 (unmanage)
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.7742] device (wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.7740] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.7739] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.6635] device (wlp2s0): set-hw-addr: set MAC address to 4A:02:76:42:75:52 (scanning)
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5681] dhcp6 (wlp2s0): state changed no lease
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5681] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5681] dhcp6 (wlp2s0): canceled DHCP transaction
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5680] dhcp4 (wlp2s0): state changed no lease
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5680] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5680] dhcp4 (wlp2s0): canceled DHCP transaction
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5674] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.5672] device (wlp2s0): supplicant interface state: completed -> disconnected
Feb 01 16:22:36 zoopmaze wpa_supplicant[2526]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 01 16:22:36 zoopmaze wpa_supplicant[2526]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=1c:74:0d:45:15:df reason=3 locally_generated=1
Feb 01 16:22:36 zoopmaze kernel: wlp2s0: deauthenticating from 1c:74:0d:45:15:df by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 01 16:22:36 zoopmaze systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 01 16:22:36 zoopmaze systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.3311] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.3308] manager: NetworkManager state is now ASLEEP
Feb 01 16:22:36 zoopmaze brave-browser.desktop[5633]: [5633:5665:0201/162236.321927:ERROR:get_updates_processor.cc(263)] PostClientToServerMessage() failed during GetUpdates with error Network error (ERR_NETWORK_IO_SUSPENDED)
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.3208] device (enp1s0f0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 01 16:22:36 zoopmaze NetworkManager[1811]: <info>  [1706800956.3207] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Feb 01 16:22:36 zoopmaze systemd-logind[1813]: The system will suspend now!
Feb 01 16:22:36 zoopmaze systemd-logind[1813]: Power key pressed short.

After attempting to wake there's no logs in journalctl, so I'm not sure how to debug it further.

Offline

#2 2024-02-01 15:50:11

qwemaze
Member
Registered: 2018-10-01
Posts: 12

Re: Screen freeze on wake after suspend

Seems like it's caused by GNOME.
Tried to login to xfce4 and was able to suspend/wake without issues.

Offline

#3 2024-02-02 21:39:39

ryanabx
Member
Registered: 2024-02-02
Posts: 1

Re: Screen freeze on wake after suspend

Here's an issue tracking this problem: https://gitlab.freedesktop.org/drm/amd/-/issues/3132

Offline

#4 2024-02-03 21:37:30

qwemaze
Member
Registered: 2018-10-01
Posts: 12

Re: Screen freeze on wake after suspend

gnome-shell goes core dump after wake, so I opened issue on their tracker, but it indeed seems like related to drivers based on a stack trace
https://gitlab.gnome.org/GNOME/gnome-sh … ssues/7373

Last edited by qwemaze (2024-02-03 21:38:02)

Offline

#5 2024-02-05 00:14:30

qwemaze
Member
Registered: 2018-10-01
Posts: 12

Re: Screen freeze on wake after suspend

Seems like that's the same problem here
https://gitlab.freedesktop.org/drm/amd/-/issues/3153

Offline

#6 2024-02-05 06:18:33

gaelic
Member
Registered: 2010-08-01
Posts: 106

Re: Screen freeze on wake after suspend

Yes, I have the same (or similar) experience. Unfortunately there seem to be multiple bugs / regressions floating around at the same time, as also Mario Limonciello mentioned in this bug:

https://gitlab.freedesktop.org/drm/amd/-/issues/3132

Offline

Board footer

Powered by FluxBB