Graphic Resets when using some applications

I will edit this topic as information is requested. But for now I have some outputs from some commands for debugging.

I mostly notice this issue when running graphically intensive games, but it can also happen randomly at times when using other applications. It seems to be an issue of a GPU panic, causing KDE Plasma to reset the graphics card, crashing all applications using it and forcing the desktop to reset.
This wouldn’t be odd to me if it was a case of the GPU either overheating, or being overworked. But neither are the case whenever these resets happen. Checking temp logs, the average temperature on the GPU is stated as 63C when running a 100% work load. However these resets happen even when the GPU work load is not at 100%.
Helldivers for example at max graphics, 1440p only uses ~50-60% of the GPU and still suffers the same crashing issue. Sound, and applications continue to work in the background.
I can hear dialogue, music and even pause and un-pause media while the screen freezes. Then the desktop reappears and I get the dissapointing “Desktop effects were restarted due to a graphics reset”.

This isn’t a new issue, only new to Manjaro. I’ve been using it since Jan of last year. Was on 6.12.73 earlier and switched to 6.18.12-1 once it was made available. I also was on Stable for about 6 Months before switching to Testing and then back to Stable with a clean package reinstall. This issue still was effecting me then and now.

2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: Dumping IP State
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=4474792, emitted seq=4474794
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu:  Process GameThread pid 14026 thread vkd3d_queue pid 14082
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
2026-02-27 10:00 p.m.	systemd	Bluetooth service skipped, unmet condition check ConditionPathIsDirectory=/sys/class/bluetooth
2026-02-27 10:00 p.m.	kdeconnectd	Cannot find Bluez 5 adapter for device search false
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: failed to reset legacy queue
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: reset via MES failed and try pipe reset -110
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failed
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: GPU reset begin!. Source:  1
2026-02-27 10:00 p.m.	steam	radv/amdgpu: The CS has been cancelled because the context is lost. This context is innocent.
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: [drm] *ERROR* Failed to initialize parser -125!
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
2026-02-27 10:00 p.m.	kernel	[drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: MODE1 reset
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
2026-02-27 10:00 p.m.	kernel	[drm] PCIE GART of 512M enabled (table at 0x00000085FEB00000).
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: VRAM is lost due to GPU reset!
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x85fc000000 for PSP TMR
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e8300 (78.131.0)
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x07002F00
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: amdgpu: GPU reset(1) succeeded!
2026-02-27 10:00 p.m.	kernel	amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
2026-02-27 10:00 p.m.	org_kde_powerdevil	[  1607] Udev event detected
2026-02-27 10:00 p.m.	kwin_wayland	0x3: GL_CONTEXT_LOST in context lost
2026-02-27 10:00 p.m.	kwin_wayland	0x3: GL_CONTEXT_LOST in context lost
2026-02-27 10:00 p.m.	kwin_wayland	0x3: GL_CONTEXT_LOST in context lost
2026-02-27 10:00 p.m.	kwin_wayland	0x3: GL_CONTEXT_LOST in context lost
2026-02-27 10:00 p.m.	steam	Adding process 20605 for gameID 1285190
2026-02-27 10:00 p.m.	steam	Fossilize INFO: Overriding serialization path: "/home/kasideon/.local/share/Steam/steamapps/shadercache/1285190/fozpipelinesv6/steamapprun_pipeline_cache".
2026-02-27 10:00 p.m.	kwin_wayland_wrapper	amdgpu: The CS has cancelled because the context is lost. This context is innocent.
2026-02-27 10:00 p.m.	systemd-coredump	Process 1249 (Xwayland) of user 1000 terminated abnormally with signal 6/ABRT, processing...
2026-02-27 10:00 p.m.	systemd	Created slice Slice /system/systemd-coredump.
2026-02-27 10:00 p.m.	systemd	Started Process Core Dump (PID 20641/UID 0).
2026-02-27 10:00 p.m.	kded6	X connection to :1 broken (explicit kill or server shutdown).
2026-02-27 10:00 p.m.	xembedsniproxy	The X11 connection broke (error 1). Did the X11 server die?
2026-02-27 10:00 p.m.	kaccess	The X11 connection broke (error 1). Did the X11 server die?
2026-02-27 10:00 p.m.	ksmserver	The X11 connection broke (error 1). Did the X11 server die?
2026-02-27 10:00 p.m.	gmenudbusmenuproxy	The X11 connection broke (error 1). Did the X11 server die?
2026-02-27 10:00 p.m.	kwin_wayland	A graphics reset not attributable to the current GL context occurred.
2026-02-27 10:00 p.m.	kwin_wayland	0x3: GL_CONTEXT_LOST in context lost
2026-02-27 10:00 p.m.	systemd	plasma-kaccess.service: Main process exited, code=exited, status=1/FAILURE
2026-02-27 10:00 p.m.	systemd	plasma-kaccess.service: Failed with result 'exit-code'.
2026-02-27 10:00 p.m.	systemd	plasma-xembedsniproxy.service: Main process exited, code=exited, status=1/FAILURE
2026-02-27 10:00 p.m.	systemd	plasma-xembedsniproxy.service: Failed with result 'exit-code'.
2026-02-27 10:00 p.m.	gmenudbusmenuproxy	ICE default IO error handler doing an exit(), pid = 1422, errno = 32
2026-02-27 10:00 p.m.	gmenudbusmenuproxy	QThreadStorage: entry 1 destroyed before end of thread 0x55c073d37570
2026-02-27 10:00 p.m.	kwin_wayland	The X11 connection broke (error 1)
2026-02-27 10:00 p.m.	steam	XIO:  fatal IO error 10 (No child processes) on X server ":1"
2026-02-27 10:00 p.m.	steam	      after 306 requests (278 known processed) with 0 events remaining.
2026-02-27 10:00 p.m.	plasmashell	Graphics device lost, cleaning up scenegraph and releasing RHI
2026-02-27 10:00 p.m.	systemd	plasma-gmenudbusmenuproxy.service: Scheduled restart job, restart counter is at 1.
2026-02-27 10:02 p.m.	kernel	QSGRenderThread[8188]: segfault at 10 ip 00007f6b9feb437a sp 00007f6ab57f9550 error 4 in libc.so.6[a537a,7f6b9fe33000+171000] likely on CPU 4 (core 4, socket 0)
2026-02-27 10:02 p.m.	kernel	Code: 8b 4e 08 48 83 f9 0f 0f 86 0b 04 00 00 49 39 cd 0f 82 02 04 00 00 49 8b 3e 48 83 e7 f8 48 39 d7 0f 85 ca 06 00 00 49 8b 78 18 <4c> 39 47 10 0f 85 3c 05 00 00 4d 39 58 10 0f 85 32 05 00 00 f6 c1
2026-02-27 10:02 p.m.	systemd-coredump	Process 1379 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing...

I’ll keep this updated with info as best I can. Hardware info is in my profile I think.

:point_down: Please provide system information as described here:


[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:


Suggested inxi command (use either):

inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)

Command output should be presented as pre-formatted text in accordance with forum guidelines. :eyes:


Running inxi within a chroot environment

  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0

Your privacy is respected