[Fedora 43 KDE Plasma] Framework 13 Function keys cause system to freeze, forcing a power off

Framework Laptop 13 Linux
1

Which Linux distro are you using?
Fedora

Which release version?
43

Which kernel are you using?
6.19.6-200.fc43.x86_64 (64-bit)

Which BIOS version are you using?
03.18

Which Framework Laptop 13 model are you using?
AMD Ryzen™ 7640U

Recently I’ve found that if I try to use the function keys on my laptop (holding down the Fn key and using the F row to increase volume or brightness), my laptop will freeze up and I’ll be unable to recover, and will be forced to power the laptop off by holding the power button down. I first noticed this after I received an update to KDE Plasma a few days ago, to version 6.6.2. Before this, I was able to use the function keys without issue.

I am unfortunately very new to Linux so have no idea where to find any useful logs that may help to diagnose this issue.

2

FW13 7840U running F43 kernel 6.19.7-200.fc43.x86_64 but GNOME instead of KDE. Fn-F{7,8} work without issues.

What you’re describing sounds like the desktop (compositor) might be crashing. Can you try:

  • Ctrl-Alt-F4 to get to a text console - you should see a login prompt. Then try Alt-F2 to get back to the desktop. Sometimes this works around the symptom.

  • After you’re back in the desktop/terminal, examine the logs starting “a few minutes ago” to see if anything shows a desktop/graphics error: journalctl --since "10 minutes ago"

3

Hi there, thanks very much for the response!

I’ve given this a try and I’m unfortunately unable to access the text console with Ctrl-Alt-F4, the screen remains frozen. I’ve tried this with Fn Lock toggled on as well as off, and get the same freeze result each time.

4

OK, in that case I assume you’re forced to reboot. The journal should still have captured something relevant.

5

That’s correct yes. At what point should I run the tool? After I’ve rebooted from a freeze?

6

Yup. --since parses simple time expressions like "10 minutes ago" so you don’t have to scroll through lots of logs or fret over timestamp syntax.

7

Alright, think I’ve got something:

Mar 13 19:29:30 fedora systemd[1855]: app-flatpak-net.waterfox.waterfox-3891311430.scope: Consumed 9min 25.194s CPU time, 2.3G memory peak.
Mar 13 19:29:46 fedora systemd[1]: Started dbus-:1.2-org.kde.powerdevil.backlighthelper@2.service.
Mar 13 19:29:46 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.2-org.kde.powerdevil.backlighthelper@2 comm=“systemd” exe=“/usr/li>
Mar 13 19:29:47 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:47 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:48 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:48 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:48 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:49 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:49 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:49 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:49 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Mar 13 19:29:59 fedora kernel: amdgpu 0000:c1:00.0: amdgpu: [drm] *ERROR* [CRTC:363:crtc-0] hw_done or flip_done timed out
Mar 13 19:29:59 fedora kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:363:crtc-0] flip_done timed out
Mar 13 19:29:59 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:29:59 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:29:59 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:29:59 fedora systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@2.service: Deactivated successfully.
Mar 13 19:29:59 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.2-org.kde.powerdevil.backlighthelper@2 comm=“systemd” exe=”/usr/lib>
Mar 13 19:29:59 fedora systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@2.service: Consumed 1.350s CPU time, 4.1M memory peak.
Mar 13 19:30:00 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:00 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:00 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:01 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:01 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:01 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:02 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:02 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:02 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:03 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:03 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:03 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:04 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:04 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:04 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:05 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:05 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:05 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:06 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:06 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:06 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:08 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:08 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:08 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:09 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:09 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:09 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:10 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:10 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:10 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:11 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:11 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
Mar 13 19:30:11 fedora kwin_wayland[2165]: With the output of ‘sudo dmesg’ and ‘journalctl --user-unit plasma-kwin_wayland --boot 0’
Mar 13 19:30:12 fedora kwin_wayland[2165]: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 13 19:30:12 fedora kwin_wayland[2165]: Please report this at Making sure you're not a bot!
lines 1-55

8

Seems like the amdgpu driver is the culprit. I’ve tried booting in with older kernel versions and still hit the issue after booting in and adjusting the brightness.

Is this just what Linux is? Stuff randomly breaking with a driver update?

9

Long-tracked (and apparently hard to pinpoint) bug in the AMD graphics stack, it seems. Since you have a very reproducible case it’s worth posting about it in the AMDGPU driver bugtracker thread

Workaround is to add a kernel command line argument (which I have also had active since I opened that issue):

10

Will do, thanks very much for your help with this matter dimitris!