18
[issue identified] Framework 13 keeps freezing after upgrade to Fedora 43: flip_done timed out
(piefed.social)
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.
I'm having the same issue. I've seen it might not just be an AMD issue, it could be a GNOME issue, and it might be a wayland issue. Its driving me crazy. Some users said they were able to fix it by setting the kernel parameter amdgpu.dcdebugmask=0x10 which disables the Panel Self Refresh which is supposed to help with battery life. Someone said amdgpu.runpm=0 setting was also required (something to do with suspending the gpu). These didnt work for me and neither did switching desktop environments.
Heres a link to the kernel parameter discussion, and a guide I used.
The problem I've had with trying to debug this is that the journal logs are missing the last 5 minutes or so before the crash. I tried writing a script to log every half second, but had the same problem with missing logs. Could this indicate something? ctrl alt f3 doesn't work either when it freezes. Ran hardware tests and those all passed, BIOS and firmware are all up to date..
Considering some distro hopping.
It seems the running application remains responsive, but not anything else.
I was running RStudio on an external monitor once when it froze, and I could keep using the window. Even when I used touch gestures to "zoom" the window out, I remained in control over it and could execute code in the smaller window. But I could not interact with GNOME at all, including changing to another program on the same screen.
Another time it froze as I wrote a PieFed comment, and I pressed tab and enter a few times. The comment was published so I could continue where I left off.
First time in almost 20 years of Linux usage I'm encountering real problems, and I'm much too primitive to do anything clever about it.
Does it seem to be a Fedora problem?
I'm not sure if this is a Fedora problem, but this is a problem on a fresh install for me, so before I get too set up, I figured I can try something else. Your experience sounds a little different than mine though. I imagine an update will come around to fix this eventually, but maybe those kernel parameters will work for you?
I'll give it a shot, thanks!