Edit: I’m fairly certain @exupulosion@sh.itjust.works got it right when linking it to this unresolved issue.
The title pretty much sums it up. The freezes can happen while I am not doing anything, and while no additional software is running. I don’t really know where to start with this one.
Here’s journalctl -b -1 -e from the latest crash, as I found online that this could be useful:
okt. 29 16:28:29 framework systemd[2793]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories...
okt. 29 16:28:29 framework systemd[2793]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories.
okt. 29 16:32:02 framework systemd[2793]: Starting flatpak-portal.service - flatpak portal...
okt. 29 16:32:02 framework systemd[2793]: Started flatpak-portal.service - flatpak portal.
okt. 29 16:32:02 framework systemd[2793]: Started app-flatpak-org.gnome.Geary-307090962.scope.
okt. 29 16:32:03 framework xdg-desktop-portal[6482]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 15:32:03.036: getpwuid_r(): failed due to unknown user id (1000)
okt. 29 16:32:03 framework xdg-desktop-portal[6482]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 15:32:03.036: Could not find home directory: $HOME is not set, and user database could not be read.
okt. 29 16:32:03 framework xdg-desktop-portal[6482]: (xdg-desktop-portal-validate-icon:2): GLib-WARNING **: 15:32:03.037: Could not find home directory: $HOME is not set, and user database could not be read.
okt. 29 16:32:03 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
okt. 29 16:32:03 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
okt. 29 16:32:03 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
okt. 29 16:32:13 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:80:crtc-0] flip_done timed out
okt. 29 16:33:16 framework systemd[1]: flatpak-system-helper.service: Deactivated successfully.
okt. 29 16:33:16 framework audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=flatpak-system-helper comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
journalctl -b -2 -e, just 11 minutes earlier:
okt. 29 16:22:21 framework NetworkManager[1132]: <info> [1761751341.1716] device (wlp1s0): supplicant interface state: disconnected -> interface_disabled
okt. 29 16:22:21 framework NetworkManager[1132]: <info> [1761751341.1721] device (wlp1s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
okt. 29 16:22:21 framework systemd[2911]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories...
okt. 29 16:22:21 framework chronyd[938]: Source 172.232.132.19 offline
okt. 29 16:22:21 framework chronyd[938]: Source 194.58.202.148 offline
okt. 29 16:22:21 framework chronyd[938]: Source 172.232.157.27 offline
okt. 29 16:22:21 framework chronyd[938]: Can't synchronise: no selectable sources (4 unreachable sources)
okt. 29 16:22:21 framework chronyd[938]: Source 192.36.143.134 offline
okt. 29 16:22:21 framework NetworkManager[1132]: <info> [1761751341.1984] device (wlp1s0): set-hw-addr: reset MAC address to F4:4E:B4:15:7E:51 (unmanage)
okt. 29 16:22:21 framework systemd[2911]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories.
okt. 29 16:22:21 framework wpa_supplicant[1272]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: nl80211: deinit ifname=p2p-dev-wlp1s0 disabled_11b_rates=0
okt. 29 16:22:21 framework wpa_supplicant[1272]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
okt. 29 16:22:21 framework wpa_supplicant[1272]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
okt. 29 16:22:25 framework systemd-logind[956]: Power key pressed short.
okt. 29 16:22:25 framework kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:80:crtc-0] flip_done timed out
okt. 29 16:22:25 framework systemd-logind[956]: Delay lock is active (UID 1000/redacted, PID 3200/gnome-shell) but inhibitor timeout is reached.
okt. 29 16:22:25 framework systemd[1]: Reached target sleep.target - Sleep.
okt. 29 16:22:25 framework systemd[1]: Starting systemd-suspend.service - System Suspend...
okt. 29 16:22:25 framework systemd[1]: user@1000.service: Unit now frozen-by-parent.
okt. 29 16:22:25 framework systemd[1]: session-2.scope: Unit now frozen-by-parent.
okt. 29 16:22:25 framework systemd[1]: user-1000.slice: Unit now frozen-by-parent.
okt. 29 16:22:25 framework systemd[1]: user.slice: Unit now frozen.
okt. 29 16:22:25 framework systemd-sleep[7487]: Successfully froze unit 'user.slice'.
okt. 29 16:22:25 framework systemd-sleep[7487]: Performing sleep operation 'suspend'...
okt. 29 16:22:25 framework kernel: PM: suspend entry (s2idle)
Any help would be greatly appreciated!
The laptop is rather new, but with the AMD Ryzen™ 5 7640U w/ Radeon™ 760M Graphics × 12 processor from the previous generation.
@cabbage For me, it also depended if I was working with a 2nd screen attached or only my laptop.
With only the laptop it happened more often.
The 2nd screen never froze, but sometimes the laptop screen would with the 2nd screen still working fine.
I had problems while an external monitor was connected on Fedora 42, but as I don’t use it often I figured I could live with it. Now it seemed to have gotten worse. Once the second monitor was working but GNOME was acting weird. So yes, that absolutely does seem related.