Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Hard Crash with AMD GPU on 3.6 since upgrade. Triggered by Chromium use -
Reported by censey · filed Apr 28, 2026Closed upstream on 2026-05-08 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy 3.6, - Kernel: 6.19.11-arch1-1 - Hardware: Framework Desktop (AMD Ryzen AI Max 300 Series)
What's wrong?
Summary:
This appears to be an AMDGPU / SMU / power-management failure causing a GPU ring timeout. Hyprland was the compositor process attached to the failed graphics queue. Chromium also became blocked afterward, apparently waiting on the GPU/coredump path, but the root failure appears lower-level than a normal Chromium crash.
System:
- Arch Linux / Omarchy
- Hyprland session
- Kernel: 6.19.11-arch1-1
- Hardware: Framework Desktop (AMD Ryzen AI Max 300 Series)
- BIOS: 03.02 07/22/2025
- GPU driver: amdgpu
- User: [REDACTED]
- Hostname: [REDACTED]
Issue:
Hyprland froze / GPU became unrecoverable. Logs show AMDGPU ring timeout, failed GPU reset, SMU errors, and blocked Chromium/Hyprland tasks.
Key log extracts:
Apr 28 14:33:50 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Dumping IP State
Apr 28 14:33:53 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000
Apr 28 14:33:53 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Failed to power gate VPE!
Apr 28 14:33:53 [HOST] kernel: [drm:vpe_set_powergating_state [amdgpu]] *ERROR* Dpm disable vpe failed, ret = -62.
Apr 28 14:33:57 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Failed to power gate VCN instance 0!
Apr 28 14:33:57 [HOST] kernel: [drm:vcn_v4_0_5_stop [amdgpu]] *ERROR* Dpm disable uvd failed, ret = -62.
Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=302762, emitted seq=302764
Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Process Hyprland pid 1897 thread Hyprland:cs0 pid 1913
Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: MES failed to respond to msg=RESET
Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: failed to reset legacy queue
Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: reset via MES failed and try pipe reset -110
Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Ring gfx_0.0.0 reset failed
Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset begin!. Source: 1
Apr 28 14:35:29 [HOST] kernel: WARNING: drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_smu.c:175 at dcn35_smu_send_msg_with_param+0x10c/0x1d0 [amdgpu]
Apr 28 14:35:29 [HOST] kernel: CPU: 4 UID: 0 PID: 117126 Comm: kworker/u128:1 Not tainted 6.19.11-arch1-1 #1 PREEMPT(full)
Apr 28 14:35:29 [HOST] kernel: Hardware name: Framework Desktop (AMD Ryzen AI Max 300 Series)/FRANMFCP04, BIOS 03.02 07/22/2025
Apr 28 14:35:29 [HOST] kernel: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]
Apr 28 14:37:27 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: MODE2 reset
Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Failed to mode2 reset!
Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Mode2 reset failed!
Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: ASIC reset failed with error, -62 for drm dev, 0000:c3:00.0
Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset end with ret = -62
Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: GPU Recovery Failed: -62
Apr 28 14:37:34 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=302764, emitted seq=302764
Apr 28 14:37:34 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Process Hyprland pid 1897 thread Hyprland:cs0 pid 1913
Apr 28 14:37:41 [HOST] kernel: INFO: task chromi:traceq0:6372 blocked for more than 122 seconds.
Apr 28 14:37:41 [HOST] kernel: Tainted: G W 6.19.11-arch1-1 #1
Apr 28 14:37:41 [HOST] kernel: Blocked by coredump.
Apr 28 14:37:41 [HOST] kernel: task:chromi:traceq0 state:D stack:0 pid:6372 tgid:6341 ppid:1673
Apr 28 14:37:41 [HOST] kernel: Workqueue: ttm ttm_bo_delayed_delete [ttm]
Apr 28 14:37:41 [HOST] kernel: dma_fence_wait_timeout
Apr 28 14:37:41 [HOST] kernel: ttm_bo_delayed_delete
Additional related logs:
Apr 28 14:34:57 [HOST] kernel: xhci_hcd 0000:c3:00.4: Refused to change power state from D3hot to D0
Apr 28 14:34:57 [HOST] kernel: xhci_hcd 0000:c3:00.4: Controller not ready at resume -19
Apr 28 14:34:57 [HOST] kernel: xhci_hcd 0000:c3:00.4: HC died; cleaning up
Apr 28 14:35:12 [HOST] kernel: thunderbolt 0000:c5:00.6: Refused to change power state from D0 to D3hot
Apr 28 14:38:02 [HOST] kernel: thunderbolt 0000:c5:00.6: interrupt for TX ring 0 is already enabled
View raw text
### System details Omarchy 3.6, - Kernel: 6.19.11-arch1-1 - Hardware: Framework Desktop (AMD Ryzen AI Max 300 Series) ### What's wrong? Summary: This appears to be an AMDGPU / SMU / power-management failure causing a GPU ring timeout. Hyprland was the compositor process attached to the failed graphics queue. Chromium also became blocked afterward, apparently waiting on the GPU/coredump path, but the root failure appears lower-level than a normal Chromium crash. ``` System: - Arch Linux / Omarchy - Hyprland session - Kernel: 6.19.11-arch1-1 - Hardware: Framework Desktop (AMD Ryzen AI Max 300 Series) - BIOS: 03.02 07/22/2025 - GPU driver: amdgpu - User: [REDACTED] - Hostname: [REDACTED] Issue: Hyprland froze / GPU became unrecoverable. Logs show AMDGPU ring timeout, failed GPU reset, SMU errors, and blocked Chromium/Hyprland tasks. Key log extracts: Apr 28 14:33:50 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Dumping IP State Apr 28 14:33:53 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000032 SMN_C2PMSG_82:0x00000000 Apr 28 14:33:53 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Failed to power gate VPE! Apr 28 14:33:53 [HOST] kernel: [drm:vpe_set_powergating_state [amdgpu]] *ERROR* Dpm disable vpe failed, ret = -62. Apr 28 14:33:57 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Failed to power gate VCN instance 0! Apr 28 14:33:57 [HOST] kernel: [drm:vcn_v4_0_5_stop [amdgpu]] *ERROR* Dpm disable uvd failed, ret = -62. Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: [drm] AMDGPU device coredump file has been created Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=302762, emitted seq=302764 Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Process Hyprland pid 1897 thread Hyprland:cs0 pid 1913 Apr 28 14:34:52 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Starting gfx_0.0.0 ring reset Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: MES failed to respond to msg=RESET Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: failed to reset legacy queue Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: reset via MES failed and try pipe reset -110 Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: The CPFW hasn't support pipe reset yet. Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Ring gfx_0.0.0 reset failed Apr 28 14:34:55 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset begin!. Source: 1 Apr 28 14:35:29 [HOST] kernel: WARNING: drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_smu.c:175 at dcn35_smu_send_msg_with_param+0x10c/0x1d0 [amdgpu] Apr 28 14:35:29 [HOST] kernel: CPU: 4 UID: 0 PID: 117126 Comm: kworker/u128:1 Not tainted 6.19.11-arch1-1 #1 PREEMPT(full) Apr 28 14:35:29 [HOST] kernel: Hardware name: Framework Desktop (AMD Ryzen AI Max 300 Series)/FRANMFCP04, BIOS 03.02 07/22/2025 Apr 28 14:35:29 [HOST] kernel: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] Apr 28 14:37:27 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: MODE2 reset Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Failed to mode2 reset! Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Mode2 reset failed! Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: ASIC reset failed with error, -62 for drm dev, 0000:c3:00.0 Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: GPU reset end with ret = -62 Apr 28 14:37:32 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: GPU Recovery Failed: -62 Apr 28 14:37:34 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=302764, emitted seq=302764 Apr 28 14:37:34 [HOST] kernel: amdgpu 0000:c3:00.0: amdgpu: Process Hyprland pid 1897 thread Hyprland:cs0 pid 1913 Apr 28 14:37:41 [HOST] kernel: INFO: task chromi:traceq0:6372 blocked for more than 122 seconds. Apr 28 14:37:41 [HOST] kernel: Tainted: G W 6.19.11-arch1-1 #1 Apr 28 14:37:41 [HOST] kernel: Blocked by coredump. Apr 28 14:37:41 [HOST] kernel: task:chromi:traceq0 state:D stack:0 pid:6372 tgid:6341 ppid:1673 Apr 28 14:37:41 [HOST] kernel: Workqueue: ttm ttm_bo_delayed_delete [ttm] Apr 28 14:37:41 [HOST] kernel: dma_fence_wait_timeout Apr 28 14:37:41 [HOST] kernel: ttm_bo_delayed_delete Additional related logs: Apr 28 14:34:57 [HOST] kernel: xhci_hcd 0000:c3:00.4: Refused to change power state from D3hot to D0 Apr 28 14:34:57 [HOST] kernel: xhci_hcd 0000:c3:00.4: Controller not ready at resume -19 Apr 28 14:34:57 [HOST] kernel: xhci_hcd 0000:c3:00.4: HC died; cleaning up Apr 28 14:35:12 [HOST] kernel: thunderbolt 0000:c5:00.6: Refused to change power state from D0 to D3hot Apr 28 14:38:02 [HOST] kernel: thunderbolt 0000:c5:00.6: interrupt for TX ring 0 is already enabled
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.