proper GPU reset handling #12234

aljus7 · 2025-11-08T16:24:18Z

aljus7
Nov 8, 2025

Right now becouse of the "crashy" mesa drivers, using Hyprland is kind of a dealbreaker. For example KDE plasma has recovery mechanysm, i think hyprland should implement one. Also 99% of apps on plasma did recover on similar crashes, idk how. Maybe ctrl+c and ctrl+v this part from plasma.

''' Aborting, glGetGraphicsResetStatus returned GL_INNOCENT_CONTEXT_RESET. Cannot continue until proper GPU reset handling is implemented. '''

Mesa or AMDGPU crashes :
#10804
#11514
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13808#note_3131920
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13324
https://gitlab.freedesktop.org/mesa/mesa/-/issues?sort=created_date&state=opened&search=ring%20timeouts&first_page_size=20

aljus7 · 2025-11-16T15:24:27Z

aljus7
Nov 16, 2025
Author

Hier Hyprland crashed first, other apps diedent crash until hyprland did
Except trivalent browser

nov 16 16:04:46 aljosa-arch systemd[1]: Started Process Core Dump (PID 411552/UID 0).
nov 16 16:04:46 aljosa-arch systemd-coredump[411552]: Process 2229 (Hyprland) of user 1000 terminated abnormally with signal 6/ABRT, processing...
nov 16 16:04:46 aljosa-arch uwsm_hyprland.desktop[2229]:   what():  filesystem error: cannot make canonical path: No such file or directory [/proc/self/exe]
nov 16 16:04:46 aljosa-arch uwsm_hyprland.desktop[2229]: terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
nov 16 16:04:46 aljosa-arch systemd[1]: Started Process Core Dump (PID 411543/UID 0).
nov 16 16:04:46 aljosa-arch systemd-coredump[411543]: Process 298294 (trivalent) of user 1000 terminated abnormally with signal 5/TRAP, processing...
nov 16 16:04:46 aljosa-arch uwsm_hyprland.desktop[2229]: Hyprland has crashed :( Consult the crash report at /home/aljosa/.cache/hyprland/hyprlandCrashReport2229.txt for more information.
nov 16 16:04:46 aljosa-arch kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
nov 16 16:04:46 aljosa-arch waybar[298242]: [298294:298294:1116/160446.546865:ERROR:ui/gl/gl_fence_android_native_fence_sync.cc:67] eglDupNativeFenceFDANDROID duplication failure. Returned error=-1
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(1) succeeded!
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
nov 16 16:04:46 aljosa-arch kernel: [drm] DMUB hardware initialized: version=0x02020021
nov 16 16:04:46 aljosa-arch kernel: [drm] kiq ring mec 2 pipe 1 q 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b3100 (59.49.0)
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0xa00000 from 0x81fd000000 for PSP TMR
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
nov 16 16:04:46 aljosa-arch kernel: [drm] VRAM is lost due to GPU reset!
nov 16 16:04:46 aljosa-arch kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process trivalent pid 298294 thread trivalent:cs0 pid 298321
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=12960108, emitted seq=12960111
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e16000 from client 0x1b (UTCL2)
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73664.1762365562000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73653.1762365556000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73641.1762365549000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73629.1762365543000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73618.1762365537000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73606.1762365531000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73595.1762365524000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411553]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73584.1762365518000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73573.1762365512000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73547.1762365506000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73536.1762365499000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73525.1762365493000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411545]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73513.1762365487000000.zst.
nov 16 16:04:46 aljosa-arch systemd-coredump[411553]: Removed old coredump core.fanCommander.0.f5c5a47ec0134bf19d52537216b73a3d.73502.1762365481000000.zst.
nov 16 16:04:46 aljosa-arch systemd[1]: Started Process Core Dump (PID 411552/UID 0).
nov 16 16:04:46 aljosa-arch systemd-coredump[411552]: Process 2229 (Hyprland) of user 1000 terminated abnormally with signal 6/ABRT, processing...
nov 16 16:04:46 aljosa-arch uwsm_hyprland.desktop[2229]:   what():  filesystem error: cannot make canonical path: No such file or directory [/proc/self/exe]
nov 16 16:04:46 aljosa-arch uwsm_hyprland.desktop[2229]: terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
nov 16 16:04:46 aljosa-arch systemd[1]: Started Process Core Dump (PID 411543/UID 0).
nov 16 16:04:46 aljosa-arch systemd-coredump[411543]: Process 298294 (trivalent) of user 1000 terminated abnormally with signal 5/TRAP, processing...
nov 16 16:04:46 aljosa-arch uwsm_hyprland.desktop[2229]: Hyprland has crashed :( Consult the crash report at /home/aljosa/.cache/hyprland/hyprlandCrashReport2229.txt for more information.
nov 16 16:04:46 aljosa-arch kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
nov 16 16:04:46 aljosa-arch waybar[298242]: [298294:298294:1116/160446.546865:ERROR:ui/gl/gl_fence_android_native_fence_sync.cc:67] eglDupNativeFenceFDANDROID duplication failure. Returned error=-1
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(1) succeeded!
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
nov 16 16:04:46 aljosa-arch kernel: [drm] DMUB hardware initialized: version=0x02020021
nov 16 16:04:46 aljosa-arch kernel: [drm] kiq ring mec 2 pipe 1 q 0
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b3100 (59.49.0)
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0xa00000 from 0x81fd000000 for PSP TMR
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
nov 16 16:04:46 aljosa-arch kernel: [drm] VRAM is lost due to GPU reset!
nov 16 16:04:46 aljosa-arch kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
nov 16 16:04:46 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process trivalent pid 298294 thread trivalent:cs0 pid 298321
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=12960108, emitted seq=12960111
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
nov 16 16:04:45 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e16000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e17000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e13000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e10000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e11000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e07000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e00000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e16000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401031
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e01000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401031
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000800537e12000 from client 0x1b (UTCL2)
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu:  in process Hyprland pid 2229 thread Hyprland:cs0 pid 2246
nov 16 16:04:32 aljosa-arch kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32773)

Is that also a bug with UWSM:

what(): filesystem error: cannot make canonical path: No such file or directory [/proc/self/exe]
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
→ Hyprland has crashed :(

couse i thing same wouldnt happen i would not use UWSM

0 replies

Libadoxon · 2025-11-25T17:20:50Z

Libadoxon
Nov 25, 2025

@vaxerski pinging for promotion

0 replies

vaxerski · 2025-11-27T15:43:10Z

vaxerski
Nov 27, 2025
Maintainer

#12485

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

proper GPU reset handling #12234

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 3 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

proper GPU reset handling #12234

Uh oh!

Uh oh!

aljus7 Nov 8, 2025

Replies: 3 comments

Uh oh!

Uh oh!

aljus7 Nov 16, 2025 Author

Uh oh!

Libadoxon Nov 25, 2025

Uh oh!

vaxerski Nov 27, 2025 Maintainer

aljus7
Nov 8, 2025

aljus7
Nov 16, 2025
Author

Libadoxon
Nov 25, 2025

vaxerski
Nov 27, 2025
Maintainer