Fedora KDE becomes suddenly slow

Hi! My UI suddenly became very slow during usage, this reset when I rebooted. This is the second time this happened, the first was a few days ago. I managed to open system monitor and see that neither my CPU nor my GPU usage was high (in fact, very low). Also no process seemed suspicious from a first glance. I didn’t check for RAM, but I doubt that’s a problem, as I only had a few Firefox tabs open, Thunderbird and PyCharm, and I have 32GB.
Any ideas where to start looking when this happens the next time?

Which Linux distro are you using?
Fedora (was using GNOME, until I installed KDE and uninstalled all GNOME packages. This was months ago, the symptom started showing a few days ago.)

Which release version?
(if rolling release without a release version, skip this question)
Fedora 40

(If rolling release, last date updated?)
now.

Which kernel are you using?
6.10.11-200.fc40.x86_64 (64-bit)

Which BIOS version are you using?
3.05

Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD Ryzen™ 7840

5 Likes

I currently have this problem. System is incredibly sluggish and slow to react on mouse movement or key presses. Low CPU and memory usage.

Framework 16
Fedora 40, Kernel 6.10.11-200.fc40.x86_64
KDE Plasma 6.1.5
AMD Ryzen 7 7840HS

Just had the same thing happening on arch linux, 6.11.1-arch1-1.
No memory pressure, no temperature issues, low cpu usage.
Everything started lagging quite hard and waiting didn’t improve it. A reboot fixed it.

A reboot fixed it here as well, but it just occurred again here three days after…

1 Like

I have the same issue. The UI starts lagging, waiting doesn’t fix it, nothing strange in system monitor, restarting fixes it.
AMD Ryzen 7 7840U
Fedora 40
KDE Plasma 6.2.0
Kernel 6.10.12-200.fc40.x86_64

1 Like

Anything notable in syslog?

I couldn’t find anything in journalctl, except a message complaining about the system lagging.

On another note, one of the updates must have fixed it, because I’ve had days with multiple UI lags, but it’s completely gone (for now, will update if that changes).

I don’t know which update did it, but I’m on the latest fedora updates.

EDIT: It’s back, and after the reboot, the system even froze after about 15mins. Audio stopped coming out, screen froze, blacked out, back to frozen screen and system was completely frozen.

2 Likes

I’ve had similar issues with my AMD Framework 13 with Fedora 40 (usually running the latest updates) that I think have been coming and going for the last several weeks (happened again just now).

A reboot always fixes it, and maybe after running some updates things were helped somewhat, but it’s definitely happened more than once.

Usually I’m watching Netflix at the time (in Chrome) when it happens, so I assume it could be something related to playing video, but nothing relevant-looking really stands out in logs. If there was some other thing to search by I’d do it but I don’t know what to look for specifically.

I just had it again tonight as well.

It feels a lot like it’s graphics related, and I did see after looking at the end of the logs out of journalctl that I got something like Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! in the logs. I’m not sure if that by itself is indicative of some sort of graphics issue with the OS or a driver or something, or if it’s just noting that everything is slow and therefore Wayland is slow.

Again, a restart fixed it, and it seems like the rest of the system was fine (e.g. I could play the audio on my Netflix movie but the video and overall video UI interactions with the OS were lagging a lot).

As mentioned in previous posts, this probably has only been happening to me for the last few weeks, so it seems like it could be some sort of bug from an update from within the last few weeks, but I’m not sure where to go from there as there have likely been a lot of things updated since then.

I’m also seeing this. It’s happened twice so far. I’ve had the fw, since Monday. Arch linux. Kernel 6.11.3-arch1-1. Kde plasma. Both times a reboot fixed it. KDE 6.2 just came out, so maybe there’s some sort of memory leak in KDE? 6.2.1 came out today, so maybe they fixed something. I’ll update if it happens again.

I’ve been using the laptop most of today and I haven’t experienced much in the way of slowdown since upgrading to kde 6.2.1. Hopefully that fixed whatever leak was causing the issue. I even tested hot plugging a usb-c monitor and it worked beautifully, with independent scaling per monitor.

I think I’ve been hitting this issue lately running fedora 40, kernel 6.10.12 and plasma 6.2.0. It happens maybe once every few days. Lockscreen is really sluggish, moving the cursor has noticeable lag, basically takes multiple seconds to interact with… anything. Just like everyone else, rebooting the machine clears the problem.

Weirdly, I can switch to a nongraphical tty session and even typing has noticeable lag.

Journalctl full of messages telling me my machine is too slow:

Oct 16 17:51:37 fedora kwin_wayland[2586]: kwin_libinput: Libinput: event6 - Touchpad: client bug: event processing lagging behind by 241ms, your system is too slow
Oct 16 17:51:35 fedora kwin_wayland[2586]: kwin_libinput: Libinput: client bug: timer event6 hold: scheduled expiry is in the past (-69ms), your system is too slow

This is the only thing I can find that might indicate whatever is setting it off:

Oct 16 17:29:28 fedora kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Oct 16 17:29:27 fedora kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Oct 16 17:29:27 fedora kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Oct 16 17:29:27 fedora kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

It looks like plasma 6.2.1 hasn’t been pushed out to fedora repos yet, I guess I can wait and see if that makes the problem stop happening.

1 Like

I think there is a known bug in AMD gpu driver that triggers when screen brightness changes rapidly.
I saved this script to a shortcut key so that in case it happens to me (once a week), I can restart the AMD driver…

sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover
2 Likes

This issue is tracked here:

It’s still unclear whether there is a fix. Maybe @Mario_Limonciello has an update?

There is a mention on that issue that the newer DMCUB may help. Try upgrading?

There has been a new linux-firmware release yesterday. This needs a day to trickle into the NixOS stable. I will report back whether this helps. But I see the issue too rarely to say something quickly.

Also have this issue, Fedora KDE with latest everything as of now. Low cpu/ram usage. Using 7640U and 16GB ram.

Happened to me again same system information except I upgraded to KDE Plasma 6.2.1.
This time it happened as it was waking up from sleep when I opened the lid.

I copied some journalctl logs from when I think it happened

Oct 23 13:56:23 fedora systemd-resolved[1581]: Clock change detected. Flushing caches.
Oct 23 13:56:23 fedora rtkit-daemon[1642]: The canary thread is apparently starving. Taking action.
Oct 23 13:56:23 fedora systemd-logind[1648]: Lid opened.
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Demoting known real-time threads.
Oct 23 13:56:23 fedora sssd_kcm[373355]: Shutting down (status = 0)
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 373937 of process 373560 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora systemd[1]: sssd-kcm.service: Deactivated successfully.
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 365440 of process 364527 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora kwin_wayland[3132]: kwin_libinput: Libinput: client bug: timer event7 keyboard: scheduled expiry is in the past (-6582ms), your system is too slow
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 365222 of process 364181 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora kwin_wayland[3132]: kwin_libinput: Libinput: client bug: timer event7 keyboard: scheduled expiry is in the past (-3239ms), your system is too slow
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 335749 of process 334421 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora kwin_wayland[3132]: kwin_libinput: Libinput: client bug: timer event7 keyboard: scheduled expiry is in the past (-2767ms), your system is too slow
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 323525 of process 323260 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora kwin_wayland[3132]: kwin_libinput: Libinput: client bug: timer event7 keyboard: scheduled expiry is in the past (-2587ms), your system is too slow
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 33615 of process 29393 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora kwin_wayland[3132]: kwin_libinput: Libinput: client bug: timer event7 keyboard: scheduled expiry is in the past (-2428ms), your system is too slow
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 5380 of process 5142 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora kwin_wayland[3132]: kwin_libinput: Libinput: WARNING: log rate limit exceeded (5 msgs per 3600000ms). Discarding future messages.
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 175217 of process 4655 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 4830 of process 4655 (/usr/lib64/firefox/firefox).
Oct 23 13:56:23 fedora systemd[1]: dbus-:1.3-org.kde.powerdevil.backlighthelper@180.service: Deactivated successfully.
Oct 23 13:56:23 fedora rtkit-daemon[1642]: Successfully demoted thread 3126 of process 3126 (/usr/bin/wireplumber).
Oct 23 13:56:23 fedora systemd[1]: Starting sssd-kcm.service - SSSD Kerberos Cache Manager…

I’m using amdgpu.dcdebugmask=0x10on the kernel command line as a workaround as suggested in the upstream ticket.

1 Like

Same issue, Fedora 40. Everything just grinds to a near halt. The mouse cursor moves but it’s EXTREMELY sluggish. I reverted to Kernel 6.10.12 but same issue. I don’t know what to look for in the logs to determine the root cause of the issue. This is now happening about 3-4 times a day and just started happening a few days ago.

1 Like