Thinkpad Z16 Zen 2 freezes until force reboot

[ashiqrniloy]

Laptop freezes and does not respond till it forced to shut down using Power Button and started again. Journalctl logs:

Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.5837] device (wlan0): new IWD device state is connec>
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.5845] device (wlan0): Activation: starting connectio>
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.5846] device (wlan0): state change: disconnected -> >
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.5847] manager: NetworkManager state is now CONNECTING
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.5849] device (wlan0): state change: prepare -> confi>
Jul 25 19:25:29 aerynos kernel: wlan0: authenticated
Jul 25 19:25:29 aerynos kernel: wlan0: associate with 20:23:51:74:32:42 (try 1/3)
Jul 25 19:25:29 aerynos kernel: wlan0: RX AssocResp from 20:23:51:74:32:42 (capab=0x1411 status=0 aid=5)
Jul 25 19:25:29 aerynos kernel: wlan0: associated
Jul 25 19:25:29 aerynos com.protonvpn.www.desktop[279658]: 2026-07-25T13:25:29.640112+00:00 | proton.vpn.app.gtk.serv>
Jul 25 19:25:29 aerynos kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 20:23:51:74:32:42
Jul 25 19:25:29 aerynos gnome-shell[3633]: [XWayland Indicator] Enabling extension xwayland-indicator@swsnr.de 50.1
Jul 25 19:25:29 aerynos iwd[828]: event: state, old: connecting (auto), new: connected
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.8218] device (wlan0): new IWD device state is connec>
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.8221] device (wlan0): state change: config -> ip-con>
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.8230] dhcp4 (wlan0): activation: beginning transacti>
Jul 25 19:25:29 aerynos avahi-daemon[822]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::79>
Jul 25 19:25:29 aerynos avahi-daemon[822]: New relevant interface wlan0.IPv6 for mDNS.
Jul 25 19:25:29 aerynos gnome-shell[3633]: [XWayland Indicator] Wayland session, monitoring focused window
Jul 25 19:25:29 aerynos avahi-daemon[822]: Registering new address record for fe80::79d5:4795:9d4b:5beb on wlan0.*.
Jul 25 19:25:29 aerynos gnome-shell[3633]: [XWayland Indicator] Extension xwayland-indicator@swsnr.de 50.1 successful>
Jul 25 19:25:29 aerynos gnome-shell[3633]: #PaperWM enabled
Jul 25 19:25:29 aerynos NetworkManager[820]: [1784985929.8784] dhcp4 (wlan0): state changed new lease, addres>
Jul 25 19:25:29 aerynos com.bitwarden.desktop.desktop[4769]: 19:25:29.933 › Retrieving application id
Jul 25 19:25:29 aerynos com.bitwarden.desktop.desktop[4769]: 19:25:29.940 › Unable to fetch ServerConfig from https:/>
Jul 25 19:25:29 aerynos ModemManager[986]: [base-manager] couldn't check support for device '/sys/devices/pci00>
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0499] dhcp4 (wlan0): state changed new lease, addres>
Jul 25 19:25:30 aerynos avahi-daemon[822]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.>
Jul 25 19:25:30 aerynos avahi-daemon[822]: New relevant interface wlan0.IPv4 for mDNS.
Jul 25 19:25:30 aerynos avahi-daemon[822]: Registering new address record for 192.168.0.206 on wlan0.IPv4.
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0570] policy: set 'Abu Darda Md Maaz' (wlan0) as def>
Jul 25 19:25:30 aerynos gsd-sharing[3759]: Failed to stop gnome-user-share-webdav.service: GDBus.Error:org.freedeskto>
Jul 25 19:25:30 aerynos systemd-resolved[650]: wlan0: Bus client set default route setting: yes
Jul 25 19:25:30 aerynos gsd-sharing[3759]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchU>
Jul 25 19:25:30 aerynos systemd-resolved[650]: wlan0: Bus client set DNS server list to: 192.168.0.1
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0690] device (wlan0): state change: ip-config -> ip->
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0703] device (wlan0): state change: ip-check -> seco>
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0704] device (wlan0): state change: secondaries -> a>
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0706] manager: NetworkManager state is now CONNECTED>
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0709] device (wlan0): Activation: successful, device>
Jul 25 19:25:30 aerynos NetworkManager[820]: [1784985930.0712] manager: NetworkManager state is now CONNECTED>
Jul 25 19:25:30 aerynos kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110)
Jul 25 19:25:30 aerynos com.bitwarden.desktop.desktop[4769]: 19:25:30.734 › Environment did not respond in time, emit>
Jul 25 19:25:32 aerynos com.bitwarden.desktop.desktop[4769]: 19:25:32.031 › Retrieving application id
Jul 25 19:25:32 aerynos appindicatorsupport@rgcjonas.gmail.com[3633]: Using Brute-force mode for StatusNotifierItem c>
Jul 25 19:25:32 aerynos systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 25 19:25:32 aerynos com.bitwarden.desktop.desktop[4769]: 19:25:32.831 › Environment did not respond in time, emit>
Jul 25 19:25:32 aerynos systemd[1]: Starting rtkit-daemon.service - RealtimeKit Scheduling Policy Service...
Jul 25 19:25:32 aerynos systemd[1]: Started rtkit-daemon.service - RealtimeKit Scheduling Policy Service.
Jul 25 19:25:32 aerynos rtkit-daemon[786909]: Handling system-suspend using logind.
Jul 25 19:25:33 aerynos com.protonvpn.www.desktop[279658]: 2026-07-25T13:25:33.792796+00:00 | proton.vpn.app.gtk.serv>
Jul 25 19:25:36 aerynos com.protonvpn.www.desktop[279658]: 2026-07-25T13:25:36.189342+00:00 | proton.vpn.session.util>
Jul 25 19:25:37 aerynos gnome-text-editor[10166]: Trying to snapshot GtkGizmo 0x55faf213ebf0 without a current alloca>
Jul 25 19:25:39 aerynos com.protonvpn.www.desktop[279658]: 2026-07-25T13:25:39.048653+00:00 | proton.vpn.session.util>
Jul 25 19:25:39 aerynos gnome-keyring-daemon[3482]: asked to register item /org/freedesktop/secrets/collection/login/>
Jul 25 19:25:39 aerynos com.protonvpn.www.desktop[279658]: 2026-07-25T13:25:39.119694+00:00 | proton.vpn.core.refresh>
Jul 25 19:25:48 aerynos ntp-daemon[1017]: 2026-07-25T13:25:48.766987Z WARN Ntp Source{index=SourceId(2) name="ntpd-r>
Jul 25 19:25:49 aerynos ntp-daemon[1017]: 2026-07-25T13:25:49.215439Z WARN Ntp Source{index=SourceId(1) name="ntpd-r>
Jul 25 19:26:20 aerynos ntp-daemon[1017]: 2026-07-25T13:26:20.204669Z WARN Ntp Source{index=SourceId(4) name="ntpd-r>
Jul 25 19:26:30 aerynos gnome-software[3963]: ignoring percentage 81% -> 0% as going down on app system/flatpak/flath>
Jul 25 19:27:00 aerynos gnome-text-editor[10166]: Trying to snapshot GtkGizmo 0x55faf195d7a0 without a current alloca>
lines 1753-1813/1813 (END)

Device info:
Thinkpad Z16 Zen 2
CPU: Ryzen 7940HS
GPU: RX 6550M

Using the GNOME desktop version.

[farfromexact]

The excerpt does not identify the freeze yet. It shows wlan0 completing association and NetworkManager reaching CONNECTED, but much of it looks like activity around the event rather than a kernel fault. Several lines are also truncated in the pasted journal.

For the next occurrence, capture the previous boot from another machine or after reboot:

journalctl -b -1 -k -e
journalctl -b -1 -p warning..alert
journalctl -b -1 | grep -Ei 'amdgpu|gpu|watchdog|mce|ucsi|firmware|oom|segfault'

Check whether SSH or ping still works during the freeze; that distinguishes a GNOME or display hang from a full kernel lockup. With the RX 6550M and Wayland, compare a current kernel and firmware, GNOME Wayland versus Xorg, and one run with ProtonVPN and nonessential shell extensions disabled. Avoid repeated hard power-offs until pstore or a crash dump is configured. The exact trigger - resume, external display, Wi-Fi, VPN, or idle - plus the previous boot kernel lines would make this much easier to triage.

[ermo]

@ashiqrniloy Does this happen in response to a sudo moss sync -u update?

[ashiqrniloy]

In my case, I did not find any relationship with the sync update. I am sure there is a pattern but for me it seemed kind of random. Has not been able to reproduce it again though. I will report here if I face the issue again. Is there anything particular you would like me to check if it happens again?

[ermo]

I can't think of anything. The hardware ought to be well-supported by the current kernel.