[Issue] FW13 Fedora 41/42 (kernel 6.14) hard freeze

Framework Laptop 13 Linux
1

I recently started encountering hard freezes while using my FW13 with Fedora. I usually do some programming with Chrome and maybe Slack, and suddenly everything stops, including the mouse and the keyboard, but audio still works for some reason.

It started a few weeks ago with Fedora 41, but I don’t remember exactly after what kernel version update (my guess would be after upgrading to 6.13 maybe?). Upgraded to Fedora 42 yesterday, and the issue persists even after upgrading the kernel to 6.14.2

I guess it’s a kernel issue, because it started after upgrading the kernel and persists across two different distro/DE versions.

Which Linux distro are you using?

Happened on Fedora 41 and Fedora 42

Which kernel are you using?

Currently, 6.14.2

Noticed the issue with the last few versions. I don’t remember at what version exactly this started happening.

Which BIOS version are you using?

3.07

Which Framework Laptop 13 model are you using?

AMD Ryzen 7 7840U Radeon 780M
120hz
64GB RAM

2 Likes
2

I’m having the same issue with Ubuntu 25.04, Framework 13 AMD Ryzen 7, tried kernels 6.14 and 6.14.2.

3

It looks like 7840U/780M: `*ERROR* [CRTC:83:crtc-1] flip_done timed out`, leads to frozen display and need to hard reboot (#4141) · Issues · drm / amd · GitLab
Can you also report your linux-firmware version, as well as kernel messages from last boot? (if it’s this issue you should be able to initiate a normal shutdown using your power button, it’ll take a while depending on how fast the hanging processes get killed)

I noticed yesterday that there were some very recent updates to amdgpu firmwares, not tagged yet. I am trying them out currently, and I haven’t had a freeze since :crossed_fingers:.

4

I downgraded to 6.13.6 (6.13.12 froze), and it’s working fine.

I can try 6.14 (if I still have it) again and get the logs if needed, but that would probably be around the weekend.

Can you share how to get these logs?

5

I don’t use a systemd-based distro myself, but journalctl -k -b -1 should give you the kernel messages (-k) of last boot (-b -1).

1 Like