ampersandrew OP , 3 hours ago

Alright, from journalctl, I can for sure identify exactly where my computer hung. That last line that repeats itself? It repeats itself thousands of times until I shut the machine down. Does that mean anything to you?

<span style="color:#323232;">Aug 03 12:58:26 Compy-5600X steam[4057]: 08/03 12:58:26 minidumps folder is set to /tmp/dumps
</span><span style="color:#323232;">Aug 03 12:58:26 Compy-5600X steam[4057]: 08/03 12:58:26 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20240716232148)/tid(1798223)
</span><span style="color:#323232;">Aug 03 12:58:26 Compy-5600X steam[4057]: 08/03 12:58:26 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(1798223)
</span><span style="color:#323232;">Aug 03 12:58:36 Compy-5600X kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input105
</span><span style="color:#323232;">Aug 03 13:00:04 Compy-5600X systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
</span><span style="color:#323232;">Aug 03 13:00:04 Compy-5600X systemd[1]: sysstat-collect.service: Deactivated successfully.
</span><span style="color:#323232;">Aug 03 13:00:04 Compy-5600X systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32798, for process WolfNewOrder_x6 pid 1798131 thread WolfNewOrd:cs0 pid 1798172)
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000e8674353a000 from client 0x1b (UTCL2)
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401430
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
</span><span style="color:#323232;">Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
</span><span style="color:#323232;">Aug 03 13:00:43 Compy-5600X kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=815617255, emitted seq=815617257
</span><span style="color:#323232;">Aug 03 13:00:43 Compy-5600X kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process WolfNewOrder_x6 pid 1798131 thread WolfNewOrd:cs0 pid 1798172
</span><span style="color:#323232;">Aug 03 13:00:43 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset succeeded, trying to resume
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: [drm] VRAM is lost due to GPU reset!
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: [drm] PSP is resuming...
</span><span style="color:#323232;">Aug 03 13:00:44 Compy-5600X kernel: [drm] reserve 0xa00000 from 0x83fd000000 for PSP TMR
</span><span style="color:#323232;">Aug 03 13:00:45 Compy-5600X plasmashell[1970]: amdgpu: amdgpu_cs_query_fence_status failed.
</span><span style="color:#323232;">Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed.
</span><span style="color:#323232;">Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed.
</span><span style="color:#323232;">Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed.
</span><span style="color:#323232;">Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed.
</span><span style="color:#323232;">Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed.
</span>

I can also get the Proton logs if you still need them, but that will have to come later, since it’s an ordeal to plan for a scenario where my desktop will crash.