Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-192GitHub issuePublicDecided· Out of scope

linux-omarchy kernel: 7.2.5-3 hard freezes on HP ZBook 15 G5 (i7-8850H + UHD 630 + Quadro P2000) — arch 7.2.3 fine

Reported by Smittttttt · filed Sep 22, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 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

linux-omarchy kernel: 7.2.5-3 hard freezes on HP ZBook 15 G5 (i7-8850H + UHD 630 + Quadro P2000) — arch 7.2.3 finerevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

  • Laptop: HP HP ZBook 15 G5/842A, BIOS Q70 Ver. 01.32.00 - CPU: Intel i7-8850H, iGPU UHD 630 [8086:3e9b] driver i915 - dGPU: NVIDIA Quadro P2000 Mobile [10de:1cba], nvidia-580xx-dkms 580.178.04, supergfxd mode Vfio - Omarchy: 4.0.4-1 - Good: linux 7.2.3.arch1-3 - Bad: linux-omarchy 7.2.5-3 (installed 2026-09-21) - DE: Hyprland 0.56.2-2, mpv 1:0.41.0-6, yazi 26.9.1-2

What's wrong?

What's wrong?
Boot linux-omarchy 7.2.5-3 hard-freezes requiring power-button reset. No mouse/keyboard, can't switch tty no panic on disk, journal just stops.
linux 7.2.3.arch1-3 on same system/config runs for hours.

Repro (freezes everytime on this kernel):
- boot linux-omarchy
- open mpv, scrub back/forth quickly through a movie, or open yazi and move fast up and down through files
- freeze within seconds. Observed boots lasting 2s, 36s, 37s, 54s.
- one freeze 4s after uwsm_app-daemon: ... yazi (14:30:44 launch, 14:30:48 last kernel line vfio-pci 0000:01:00.0: Enabling HDA controller).

Logs:
- journalctl --list-boots shows omarchy boots with no shutdown sequence vs clean arch shutdowns.
- journalctl -b -4 -k / -b -3 -k end with repeated NVRM: GPU 0000:01:00.0 is already bound to vfio-pci / No NVIDIA devices probed and final vfio-pci: Enabling HDA controller. No i915 ERROR/HANG, BUG, lockup flushed.
- journalctl -p 0..3 on bad boots only shows pre-existing ACPI BIOS errors (AE_AML_BUFFER_LIMIT, AE_AML_PACKAGE_LIMIT), also present on good boots.
- No OOM, no relevant coredump.

Diffs noticed:
- diff <(zcat /proc/config.gz) <(cat /lib/modules/7.2.5-3-omarchy/build/.config): CONFIG_INTEL_IOMMU_DEFAULT_ON=y in omarchy, not in arch; plus DRM debug options off, TSX_MODE_OFF, etc.
- PKGBUILD linux-omarchy 7.2.5 adds i915 patches 0400-drm-i915-alpm-limit, 0401-psr-exit, 0402-psr2-early-transport, 0430-fbc, plus 0200-idle, 0210-pstate, sched/MM patches.
- Binding differs: omarchy kernel -> vfio-pci wins, nvidia fails; arch kernel (current boot) -> vfio-pci probe failed -22, nvidia wins, nvidia-smi works.

Expected:
omarchy kernel at least as stable as arch on CoffeeLake + Pascal hybrid.

Tried:
staying on arch kernel (works as expected).

Happy to provide any logs give me instructions

This was written with the help of ai

View raw text
### System details

- Laptop: HP HP ZBook 15 G5/842A, BIOS Q70 Ver. 01.32.00 - CPU: Intel i7-8850H, iGPU UHD 630 [8086:3e9b] driver i915 - dGPU: NVIDIA Quadro P2000 Mobile [10de:1cba], nvidia-580xx-dkms 580.178.04, supergfxd mode Vfio - Omarchy: 4.0.4-1 - Good: linux 7.2.3.arch1-3 - Bad: linux-omarchy 7.2.5-3 (installed 2026-09-21) - DE: Hyprland 0.56.2-2, mpv 1:0.41.0-6, yazi 26.9.1-2

### What's wrong?

**What's wrong?**
Boot linux-omarchy 7.2.5-3 hard-freezes requiring power-button reset. No mouse/keyboard, can't switch tty no panic on disk, journal just stops. 
linux 7.2.3.arch1-3 on same system/config runs for hours.

**Repro (freezes everytime on this kernel):**
- boot linux-omarchy
- open mpv, scrub back/forth quickly through a movie, or open yazi and move fast up and down through files
- freeze within seconds. Observed boots lasting 2s, 36s, 37s, 54s.
- one freeze 4s after `uwsm_app-daemon: ... yazi` (14:30:44 launch, 14:30:48 last kernel line `vfio-pci 0000:01:00.0: Enabling HDA controller`).

**Logs:**
- `journalctl --list-boots` shows omarchy boots with no shutdown sequence vs clean arch shutdowns.
- `journalctl -b -4 -k` / `-b -3 -k` end with repeated `NVRM: GPU 0000:01:00.0 is already bound to vfio-pci / No NVIDIA devices probed` and final `vfio-pci: Enabling HDA controller`. No i915 ERROR/HANG, BUG, lockup flushed.
- `journalctl -p 0..3` on bad boots only shows pre-existing ACPI BIOS errors (`AE_AML_BUFFER_LIMIT`, `AE_AML_PACKAGE_LIMIT`), also present on good boots.
- No OOM, no relevant coredump.

**Diffs noticed:**
- `diff <(zcat /proc/config.gz) <(cat /lib/modules/7.2.5-3-omarchy/build/.config)`: `CONFIG_INTEL_IOMMU_DEFAULT_ON=y` in omarchy, not in arch; plus DRM debug options off, TSX_MODE_OFF, etc.
- PKGBUILD `linux-omarchy 7.2.5` adds i915 patches `0400-drm-i915-alpm-limit`, `0401-psr-exit`, `0402-psr2-early-transport`, `0430-fbc`, plus `0200-idle`, `0210-pstate`, sched/MM patches.
- Binding differs: omarchy kernel -> vfio-pci wins, nvidia fails; arch kernel (current boot) -> `vfio-pci probe failed -22`, nvidia wins, `nvidia-smi` works.

**Expected:** 
omarchy kernel at least as stable as arch on CoffeeLake + Pascal hybrid.

**Tried:** 
staying on arch kernel (works as expected).

Happy to provide any logs give me instructions

This was written with the help of ai

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 17:23 UTC