RX 9070 XT crashing in RE8. journalctl points to kernel

Support Graphics & Display
1

So basically after three hours of streaming and playing RE8 through Steam crashes my RX 9070 XT and it takes down all of the running apps with it.

I managed to find journalctl logs for kernel.

helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32796)
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:  Process re8.exe pid 26621 thread vkd3d_queue pid 28511
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:   in page starting at address 0x00008000aedae000 from client 10
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          MORE_FAULTS: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          WALKER_ERROR: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          MAPPING_ERROR: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          RW: 0x0
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State
helmi 06 06:06:51 user-pc NetworkManager[743]: <info>  [1770350811.4024] dhcp4 (enp9s0f3u2): state changed new lease, address=10.140.77.237
helmi 06 06:06:51 user-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
helmi 06 06:06:51 user-pc systemd[1]: Started Network Manager Script Dispatcher Service.
helmi 06 06:07:01 user-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32796)
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:  Process re8.exe pid 26621 thread vkd3d_queue pid 28511
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:   in page starting at address 0x00008000aedae000 from client 10
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          MORE_FAULTS: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          WALKER_ERROR: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          MAPPING_ERROR: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          RW: 0x0
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State Completed
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=24628686, emitted seq=24628688
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:  Process re8.exe pid 26621 thread vkd3d_queue pid 28511
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Starting gfx_0.0.0 ring reset
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=RESET
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to reset legacy queue
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: reset via MES failed and try pipe reset -110
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Ring gfx_0.0.0 reset failed
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset begin!. Source:  1
helmi 06 06:27:02 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to suspend display audio
helmi 06 06:27:05 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:05 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:08 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:08 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:11 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:11 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:13 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:13 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:16 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:16 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:19 user-pc kernel: [drm:gfx_v12_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MODE1 reset
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU smu mode1 reset
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset succeeded, trying to resume
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: PCIE GART of 512M enabled (table at 0x00000083DAB00000).
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: VRAM is lost due to GPU reset!
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: PSP is resuming...
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: RAP: optional rap ta ucode is not available
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: smu driver if version = 0x0000002e, smu fw if version = 0x00000032, smu fw program = 0, >
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SMU driver if version not matched
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: program CP_MES_CNTL : 0x4000000
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: program CP_MES_CNTL : 0xc000000
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x0A000700
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma0 uses VM inv eng 9 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma1 uses VM inv eng 10 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
helmi 06 06:27:21 user-pc flatpak[37589]: amdgpu: The CS has cancelled because the context is lost. This context is innocent.
helmi 06 06:27:21 user-pc steam[25183]: radv/amdgpu: The CS has been cancelled because the context is lost. This context is innocent.
helmi 06 06:27:21 user-pc steam[25183]: radv: GPUVM fault detected at address 0x8000aedae000.
helmi 06 06:27:21 user-pc steam[25183]: GCVM_L2_PROTECTION_FAULT_STATUS: 0x501430
helmi 06 06:27:21 user-pc steam[25183]:          CLIENT_ID: (SQC (data)) 0xa
helmi 06 06:27:21 user-pc steam[25183]:          MORE_FAULTS: 0
helmi 06 06:27:21 user-pc steam[25183]:          WALKER_ERROR: 0
helmi 06 06:27:21 user-pc steam[25183]:          PERMISSION_FAULTS: 3
helmi 06 06:27:21 user-pc steam[25183]:          MAPPING_ERROR: 0
helmi 06 06:27:21 user-pc steam[25183]:          RW: 0
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset(1) succeeded!
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: [drm] device wedged, but recovered through reset
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] *ERROR* Failed to initialize parser -125!
helmi 06 06:27:21 user-pc kwin_wayland[1203]: A graphics reset not attributable to the current GL context occurred.
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc systemd-coredump[70537]: Process 37589 (obs) of user 1000 terminated abnormally with signal 6/ABRT, processing...
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc systemd[1]: Started Process Core Dump (PID 70537/UID 0).
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: 0x3: GL_CONTEXT_LOST in context lost
helmi 06 06:27:21 user-pc kwin_wayland[1203]: BlurConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: GlideConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: KscreenConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: OverviewConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: SlideConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: SlidingPopupsConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: WindowViewConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: ZoomConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc lact[10675]: 2026-02-06T04:27:21.441775Z  INFO lact_daemon: got kernel drm subsystem event, reloading GPUs
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc plasmashell[1470]: QRhiGles2: Context is lost.
helmi 06 06:27:21 user-pc plasmashell[1470]: Graphics device lost, cleaning up scenegraph and releasing RHI
helmi 06 06:27:21 user-pc flatpak[58684]: Crash Annotation GraphicsCriticalError: |[0][GFX1-]: GFX: CanvasTranslator failed creating WebGL shared conte>
helmi 06 06:27:21 user-pc lact[10675]: 2026-02-06T04:27:21.466016Z  INFO lact_daemon::server::handler: initialized amdgpu controller for GPU 1002:7550->
helmi 06 06:27:21 user-pc lact[10675]: 2026-02-06T04:27:21.466031Z  INFO lact_daemon::server::handler: GPU list reloaded with 1 devices, reapplying con>
helmi 06 06:27:21 user-pc plasmashell[1470]: QRhiGles2: Context is lost.
helmi 06 06:27:21 user-pc plasmashell[1470]: Graphics device lost, cleaning up scenegraph and releasing RHI
helmi 06 06:27:21 user-pc lact[10675]: 2026-02-06T04:27:21.475582Z  INFO lact_daemon::server::handler: configuration applied
helmi 06 06:27:21 user-pc kwin_wayland[1203]: WindowViewConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: ZoomConfig::instance called after the first use - ignoring
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc lact[10675]: 2026-02-06T04:27:21.441775Z  INFO lact_daemon: got kernel drm subsystem event, reloading GPUs
helmi 06 06:27:21 user-pc kwin_wayland[1203]: Could not delete render time query because no context is current
helmi 06 06:27:21 user-pc plasmashell[1470]: QRhiGles2: Context is lost.
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          MAPPING_ERROR: 0x0
helmi 06 06:26:45 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:          RW: 0x0
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State Completed
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=24628686, emitted seq=24628688
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:  Process re8.exe pid 26621 thread vkd3d_queue pid 28511
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Starting gfx_0.0.0 ring reset
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=RESET
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to reset legacy queue
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: reset via MES failed and try pipe reset -110
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Ring gfx_0.0.0 reset failed
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset begin!. Source:  1
helmi 06 06:27:02 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to suspend display audio
helmi 06 06:27:05 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:05 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:08 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:08 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:11 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:11 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:13 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:13 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:16 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:16 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:19 user-pc kernel: [drm:gfx_v12_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MODE1 reset
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU smu mode1 reset
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset succeeded, trying to resume
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: PCIE GART of 512M enabled (table at 0x00000083DAB00000).
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: VRAM is lost due to GPU reset!
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: PSP is resuming...
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: RAP: optional rap ta ucode is not available
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: smu driver if version = 0x0000002e, smu fw if version = 0x00000032, smu fw program = 0, >
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SMU driver if version not matched
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: program CP_MES_CNTL : 0x4000000
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: program CP_MES_CNTL : 0xc000000
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x0A000700
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
helmi 06 06:27:21 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma0 uses VM inv eng 9 on hub 0
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=24628686, emitted seq=24628688
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu:  Process re8.exe pid 26621 thread vkd3d_queue pid 28511
helmi 06 06:26:56 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Starting gfx_0.0.0 ring reset
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=RESET
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to reset legacy queue
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: reset via MES failed and try pipe reset -110
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: Ring gfx_0.0.0 reset failed
helmi 06 06:26:58 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset begin!. Source:  1
helmi 06 06:27:02 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to suspend display audio
helmi 06 06:27:05 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:05 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:08 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:08 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:11 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:11 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:13 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:13 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:16 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:16 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MES(1) failed to respond to msg=REMOVE_QUEUE
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: failed to unmap legacy queue
helmi 06 06:27:19 user-pc kernel: [drm:gfx_v12_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: MODE1 reset
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset
helmi 06 06:27:19 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU smu mode1 reset
helmi 06 06:27:20 user-pc kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset succeeded, trying to resume
2

What should i do in this situation?
Where should i report this?

3

With the developers of the Windows game you were playing, or alternatively, to Steam. :grin:

Seriously, GNU/Linux gamers don’t realize this, but most games available for GNU/Linux through Steam are actually recompiled Windows games, and in this case, you were effectively running a non-ported Windows game — re8.exe — via Steam’s own implementation of a wine-like ABI on top of the Linux kernel. And it was this process that crashed your GPU.

4

But why does my GPU not have overheat protection and it says errors about that etc.?
Also the VRAM clocks are maxed out constantly.

5

You would have to ask AMD about that. They’re the ones who manufactured it. :man_shrugging:

The game did that. Or more precisely, the Steam application did that while running the game.

6

The game did not just put my VRAM clocks to max. Those are maxed out when idle all times.

7

Well, I’m not a gamer and I don’t have an AMD GPU, but I presume that there would be some power-savings-related kernel parameter to tweak that. It would be strange if there weren’t.

8

Are we talking about Application Crashes or Full Freezing System or a Kernel Panic?

When you are sure its related to your GPU then check VRAM Temps, Hotspot Temp, Core Temps and even VRM Temps can be important.
Its more of a question if your Card even have this sensors.

Big question is also which 9070 XT Vendor are you using, there are some bad design cooling solutions. Maybe improve Case cooling, thinking about buying a better tower?

But i need more informations… for a fair judgement.

Im running into Kernel Panic with this newest Manjaro stable release when im gaming… but with a nvidia 2080Ti and not with a AMD GPU.

48hours ago i could play day/night without problems… but at the moment im still investigating what is wrong with the update.

How long do you have problems with your games? And are other games are involved is the next question.

9

I was just dumb. It was the ProtonGE and or NTSync that i was using with the game. Thought that i would need it for videos to play back, but those play fine on Proton 10 and it’s stable for five hours at least.

I checked the temps and all were fine. Temps were basically max 64C hotspot and 58C for VRAM with that title. The usage was around 30% for GPU and 12% for CPU.

It was a GPU hang probably cause the screen froze and then came back up again after a black screen. It just seemed to take down all my running apps and made the cursor in Steam tiny until reboot.

From what i gather, i think it’s best to use the Valves Proton on Steam and ProtonGE with UMU on Heroic.

10

Try CoreCTRL package (don’t break your card with overclocking and ■■■■ like that be careful) and see if you can switch profiles :wink:

12

I only undervolt and do a fan profile for more aggressive fan curves. I had CoreCtrl before, but i switched to LACT. But when i was testing i had completely removed all the undervolts, but ProtonGE still made the game and system freeze and crash after around 3h mark.

CoreCtrl or LACT does not work with VRAM adjustments on my GPU at all also the VRAM steps don’t seem to work. It just blasts full tilt with the VRAM.

13

Both of those technologies are for running binary code written for Microsoft Windows. Windows code has no access to privileged functionalities — such as regulating fans or applying power savings functions — in a UNIX operating system.

14

And what about the profiles?

image
image778Ă—654 33.8 KB

15

The profiles only seem to change the core clock amounts that fluctuate. VRAM still stays maxed even if i change profiles. I tend to use Compute as my profile.

16

Also, I can’t find it in the thread, what Kernel are you using? Maybe the kernel is an important part of the GPU handling in the system.

17 
WARNING: radv is not a conformant Vulkan implementation, testing use only.
Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.8-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 Ă— AMD Ryzen 9 5950X 16-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 9070 XT

It’s basically the only LTS kernel that i can use for my GPU as the support came in with Kernel 6.13 something.

I now disabled NTSync and probably will test if it crashes with that. Shame that the testing seems to take three hours or so.

18

I would have guessed at least 6.12 would support it, maybe you would get different result with another kernel regarding the behavior you see with memory always maxed out. It is worth a try it cost only the time of installation of the kernel, and a couple reboot at most.

//EDIT: I asked GPT, and 6.12 supports it, but newer kernels get more stability/features according to it. Anyway worth a try to see the difference. Same for experimental kernel, for the sake of testing the difference.

19

ChatGPT often lies when it doesn’t know the answer straight up.

There is a Level1Techs forums post that reads that kernel 6.13.5 is the minimum.
https://forum.level1techs.com/t/9070-and-9070-xt-setup-notes-for-linux/227038

Also i think that probably firmware has more to do with it than kernel. Don’t know for sure, just a guess.

1 Like
20

Yes, the kernel, the firmware, and MESA are all important parts for the card.

21

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.