Bug 513919

Summary:	System freezes, crashes, KWin restarts - DMESG gives amdgpu coredump
Product:	[Plasma] kwin	Reporter:	Jörg Tobias Borgert <tobias.borgert>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	kdedev
Priority:	NOR
Version First Reported In:	6.5.4
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Shortened DMESG output

Description Jörg Tobias Borgert 2025-12-28 17:02:47 UTC

Created attachment 188043 [details]
Shortened DMESG output

SUMMARY
Randomly after some time, my screen freezes, and after maybe half a minute, everything exits and KWin reports that it has been restarted.

Please note that this might be a problem in amdgpu, in the game Zephon or somewhere else, but I need to start somewhere.

STEPS TO REPRODUCE
 For me, it happens randomly while playing Steam games on Arch Linux with KDE.

1. Launch game
2. Play for some time
3. Experience crash
4. Wait for some seconds
5. Experience KWin restart

OBSERVED RESULT
The screen freezes, then KWin restarts. DMESG reports that an AMDGPU coredump was created. It names KWin and Zephon, the name of the game.

    [10347.562654] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
    [10347.564089] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
    [10347.564134] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
    [10347.564136] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
    [10347.564138] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1480531, emitted seq=1480533
    [10347.564140] amdgpu 0000:03:00.0: amdgpu:  Process kwin_wayland pid 1353 thread kwin_wayla:cs0 pid 1402
    [10347.564143] amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
    [10347.564414] amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
    [10347.564417] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
    [10357.802654] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
    [10357.803678] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
    [10357.803687] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
    [10357.803689] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
    [10357.803690] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1480532, emitted seq=1480535
    [10357.803692] amdgpu 0000:03:00.0: amdgpu:  Process kwin_wayland pid 1353 thread kwin_wayla:cs0 pid 1402
    [10357.803694] amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
    [10357.803809] amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
    [10357.803810] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
    [10368.042673] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
    [10368.043842] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
    [10368.043852] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
    [10368.043853] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
    [10368.043855] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1480533, emitted seq=1480537
    [10368.043857] amdgpu 0000:03:00.0: amdgpu:  Process kwin_wayland pid 1353 thread kwin_wayla:cs0 pid 1402
    [10368.043859] amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
    [10368.043972] amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
    [10368.043974] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
    [10378.282679] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
    [10378.283740] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
    [10378.283750] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
    [10378.283751] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
    [10378.283753] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1480535, emitted seq=1480539
    [10378.283755] amdgpu 0000:03:00.0: amdgpu:  Process kwin_wayland pid 1353 thread kwin_wayla:cs0 pid 1402
    [10378.283757] amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
    [10378.283887] amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
    [10378.283889] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
    [10378.283894] [drm:gfx_v11_0_bad_op_irq [amdgpu]] *ERROR* Illegal opcode in command stream 
    [10378.284067] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
    [10378.285041] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
    [10378.285045] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
    [10378.285046] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
    [10378.285047] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1480537, emitted seq=1480541
    [10378.285049] amdgpu 0000:03:00.0: amdgpu:  Process Zephon.bin pid 34221 thread Zephon.bin pid 34221
    [10378.285050] amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
    [10378.285162] amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
    [10378.285163] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
    [10388.522634] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
    [10388.523687] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
    [10388.523698] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
    [10388.523700] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
    [10388.523702] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1480539, emitted seq=1480543
    [10388.523704] amdgpu 0000:03:00.0: amdgpu:  Process Zephon.bin pid 34221 thread Zephon.bin pid 34221
    [10388.523705] amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
    [10388.523825] amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
    [10388.523827] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Shortened dmesg output attached.

Please find the amdgpu coredump here: https://app-share.mailbox.org/appsuite/api/share/0231e9ef0fbc09472b8f34dfbc0943d893d5559087e45654/1/8/Mjk4/Mjk4LzMxNzg

Comment 1 Jörg Tobias Borgert 2025-12-28 17:04:47 UTC

Operating System: Arch Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.2-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: AMD Radeon RX 7900 GRE
Graphics Processor 2: AMD Ryzen 7 7800X3D 8-Core Processor

Comment 2 TraceyC 2025-12-29 20:57:51 UTC

Thanks for the crash report. As the message at the top of the summary says, if something KDE related crashed, we need a backtrace of the KDE application / plasmashell so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

If the crash is only in the AMD driver, you need to report it to the AMD folks
https://gitlab.freedesktop.org/drm/amd/-/issues

Thanks.

Comment 3 Jörg Tobias Borgert 2025-12-30 02:06:28 UTC

Hi,

thank you for your fast response. I did a quick test to see whether it has anything to do with KWin at all, so I installed Hyprland and the crash happens there as well - KWin is blameless.

Should have checked that before, sorry for wasting your time.

I'll head over to AMDGPU then.