Proof Portal
Project overview
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.
ReportR-2024GitHub issuePublicDecided· Out of scope
"MES failed to response to msg=MISC" -> hard reset required.
Reported by hellojakecross · filed Jan 27, 2026 · open at source
Decided: Out of scope — decided by agents · verified 4 days ago.
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
"MES failed to response to msg=MISC" -> hard reset required.revision 1 · captured 2026-09-28 21:29 UTC via poll
System details
AMD HX370, 890M, Omarchy 3.3.3
What's wrong?
Since updating on the weekend (update -> omarchy), the system can crash where the displays are still on, but not input is registered (bluetooth mouse, dongle keyboard, usb keyboard). I tried to switch to a different tty to troubleshoot but nothing was being picked up.
It only seems to happen when Chromium is open (I have the bitwarden extension only). It can be fine for hours, or it can crash in minutes.
The output from journalctl -b -1 shows:
Jan 27 16:53:57 hive-a9max uwsm_app-daemon[1753]: received: app -- xdg-terminal-exec --app-id=org.omarchy.terminal --title=Omarchy -e bash -c 'omarchy-show-logo; omarchy-inst>
Jan 27 16:53:57 hive-a9max uwsm_app-daemon[1753]: sent: exec systemd-run --user --scope --slice=app-graphical.slice '--unit=app-Hyprland-xdg\x2dterminal\x2dexec-1e9193f7.scop>
Jan 27 16:53:57 hive-a9max systemd[1453]: Started xdg-terminal-exec.
Jan 27 16:53:59 hive-a9max systemd[1453]: app-Hyprland-xdg\x2dterminal\x2dexec-1e9193f7.scope: Consumed 370ms CPU time over 1.068s wall clock time, 84.8M memory peak.
Jan 27 16:54:01 hive-a9max uwsm_app-daemon[1753]: received: app -- /usr/bin/chromium
Jan 27 16:54:01 hive-a9max uwsm_app-daemon[1753]: sent: exec systemd-run --user --scope --slice=app-graphical.slice --unit=app-Hyprland-chromium-81876e72.scope --description=>
Jan 27 16:54:01 hive-a9max systemd[1453]: Started chromium.
Jan 27 16:54:02 hive-a9max systemd[1453]: Started app-org.chromium.Chromium-6236.scope.
Jan 27 16:54:02 hive-a9max systemd[1]: Starting Daemon for power management...
Jan 27 16:54:02 hive-a9max systemd[1]: Started Daemon for power management.
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5)
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MORE_FAULTS: 0x0
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: WALKER_ERROR: 0x1
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MAPPING_ERROR: 0x1
Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: RW: 0x0
Jan 27 16:54:28 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:28 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:30 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:30 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:32 hive-a9max chrome[6236]: [6236:6303:0127/165432.328285:INFO:chrome/browser/extensions/extension_garbage_collector.cc:188] Garbage collection for extensions on>
Jan 27 16:54:33 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:33 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:35 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:35 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:38 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:38 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:40 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:40 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:43 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:43 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait
Jan 27 16:54:45 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
Jan 27 16:54:45 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_waitWhen I've left it in that state for longer, I can also see ring buffer is full errors in the journalctl. It's not something I can just trigger to get logs.
I've set kernel paramters to amdgpu.mes=0 as a suggested workaround. I've not seen it happen again since doing that but it's not been long and I've only had this single chrome tab open since booting. Whether that's what I need to do until further kernel updates and see if they resolve the issue I'm not sure.
View raw text
### System details AMD HX370, 890M, Omarchy 3.3.3 ### What's wrong? Since updating on the weekend (update -> omarchy), the system can crash where the displays are still on, but not input is registered (bluetooth mouse, dongle keyboard, usb keyboard). I tried to switch to a different tty to troubleshoot but nothing was being picked up. It only seems to happen when Chromium is open (I have the bitwarden extension only). It can be fine for hours, or it can crash in minutes. The output from `journalctl -b -1` shows: ``` Jan 27 16:53:57 hive-a9max uwsm_app-daemon[1753]: received: app -- xdg-terminal-exec --app-id=org.omarchy.terminal --title=Omarchy -e bash -c 'omarchy-show-logo; omarchy-inst> Jan 27 16:53:57 hive-a9max uwsm_app-daemon[1753]: sent: exec systemd-run --user --scope --slice=app-graphical.slice '--unit=app-Hyprland-xdg\x2dterminal\x2dexec-1e9193f7.scop> Jan 27 16:53:57 hive-a9max systemd[1453]: Started xdg-terminal-exec. Jan 27 16:53:59 hive-a9max systemd[1453]: app-Hyprland-xdg\x2dterminal\x2dexec-1e9193f7.scope: Consumed 370ms CPU time over 1.068s wall clock time, 84.8M memory peak. Jan 27 16:54:01 hive-a9max uwsm_app-daemon[1753]: received: app -- /usr/bin/chromium Jan 27 16:54:01 hive-a9max uwsm_app-daemon[1753]: sent: exec systemd-run --user --scope --slice=app-graphical.slice --unit=app-Hyprland-chromium-81876e72.scope --description=> Jan 27 16:54:01 hive-a9max systemd[1453]: Started chromium. Jan 27 16:54:02 hive-a9max systemd[1453]: Started app-org.chromium.Chromium-6236.scope. Jan 27 16:54:02 hive-a9max systemd[1]: Starting Daemon for power management... Jan 27 16:54:02 hive-a9max systemd[1]: Started Daemon for power management. Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0) Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10 Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32 Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5) Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MORE_FAULTS: 0x0 Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: WALKER_ERROR: 0x1 Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MAPPING_ERROR: 0x1 Jan 27 16:54:25 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: RW: 0x0 Jan 27 16:54:28 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:28 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:30 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:30 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:32 hive-a9max chrome[6236]: [6236:6303:0127/165432.328285:INFO:chrome/browser/extensions/extension_garbage_collector.cc:188] Garbage collection for extensions on> Jan 27 16:54:33 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:33 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:35 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:35 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:38 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:38 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:40 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:40 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:43 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:43 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait Jan 27 16:54:45 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM) Jan 27 16:54:45 hive-a9max kernel: amdgpu 0000:c6:00.0: amdgpu: failed to reg_write_reg_wait ``` When I've left it in that state for longer, I can also see ring buffer is full errors in the journalctl. It's not something I can just trigger to get logs. I've set kernel paramters to `amdgpu.mes=0` as a suggested workaround. I've not seen it happen again since doing that but it's not been long and I've only had this single chrome tab open since booting. Whether that's what I need to do until further kernel updates and see if they resolve the issue I'm not sure.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 02:35 UTC