Created attachment 152525 [details] Excerpt from system journal SUMMARY Every now and then, VAAPI video decoding (in Firefox, in particular) triggers a GPU reset on my AMD iGPU. Whenever that happens, the screen goes black for a second and then comes back but is entirely frozen. Sometimes I'm still able to switch to a tty, sometimes not. But in any case, the Plasma session never recovers. STEPS TO REPRODUCE 1. Have a GPU reset trigger somehow OBSERVED RESULT KWin freezes entirely (but doesn't crash?) EXPECTED RESULT KWin should be able to recover from the crash. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 Kernel Version: 5.19.11-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx Memory: 6.7 GiB of RAM Graphics Processor: AMD Radeon Vega 3 Graphics ADDITIONAL INFORMATION I have attached an excerpt of the system journal from the time of the GPU reset. It never shows any indication that KWin crashed or whatever. The GPU resets successfully, and Plasmashell detects it and claims to restart its GPU process. KWin never explicitly says anything about the reset at all, but for some reason it continuously prints OpenGL information the the journal several times a second, for about a minute until I switch to a TTY and then it stops, but continues once I try to switch back.
It looks like kwin and plasmashell are stuck thinking that the OpenGL context has been lost. Do you know how to reliably trigger a gpu reset? Would reading /sys/kernel/debug/dri/0/amdgpu_gpu_reset work? or does vaapi do something different?
(In reply to Vlad Zahorodnii from comment #1) > It looks like kwin and plasmashell are stuck thinking that the OpenGL > context has been lost. Do you know how to reliably trigger a gpu reset? > Would reading /sys/kernel/debug/dri/0/amdgpu_gpu_reset work? or does vaapi > do something different? Running > sudo cat /sys/kernel/debug/dri/0/amdgpu_gpu_recover does in fact seem to cause the exact same symptoms.
According to some debugging we did, there doesn't appear to be anything KWin does wrong, it's a driver issue. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/7460
In https://gitlab.freedesktop.org/mesa/mesa/-/issues/7460#note_1595216, Mesa folks say we need to handle it; re-opening.
*** This bug has been marked as a duplicate of bug 453147 ***