https://bugs.kde.org/show_bug.cgi?id=498280
--- Comment #7 from Rolf Schröder ---
As a short update here: I currently have an alias `recover-amdgpu` (`sudo cat
/sys/kernel/debug/dri/1/amdgpu_gpu_recover'`) which I only use when necessary.
Because: At work, I connect the machine (Thinkpad T14) to
https://bugs.kde.org/show_bug.cgi?id=498280
--- Comment #6 from Rolf Schröder ---
I could not find any obvious (error) messages related to amdgpu but `sudo cat
/sys/kernel/debug/dri//amdgpu_gpu_recover` seems to have helped here,
too. I have GPU_ID 1 and 128 (i.e. two subfolders in .../dri) and o
https://bugs.kde.org/show_bug.cgi?id=498280
Rolf Schröder changed:
What|Removed |Added
CC||rolf.schroeder@limbus-medte
|
https://bugs.kde.org/show_bug.cgi?id=498280
--- Comment #4 from jackyzy...@gmail.com ---
Some updates:
I encountered this again with 6.12.11-100.fc40.x86_64.
in the log i found `Feb 19 00:12:42 code01 kernel: amdgpu :62:00.0: [drm]
*ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collec
https://bugs.kde.org/show_bug.cgi?id=498280
--- Comment #3 from jackyzy...@gmail.com ---
Some updates: due to 6.12+ kernels bug on glitching display, i revert to
kernel 6.8.9 and the other KDE/plamsa components remain the newest. and seems
that the input lag didn't happen again ( at least for two
https://bugs.kde.org/show_bug.cgi?id=498280
Nate Graham changed:
What|Removed |Added
Summary|KDE suddenly become laggy |Compositor latency causes
|
