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-111GitHub issuePublicDecided· Out of scope

MacBookPro15,1: after a long S3, amdgpu SMU firmware fails to start and both displays stay black

Reported by lukaseppler · filed Sep 25, 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

MacBookPro15,1: after a long S3, amdgpu SMU firmware fails to start and both displays stay blackrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

MacBookPro15,1 (Mac-937A206F2EE63C01), i7-9750H, UHD 630 + Radeon Pro 560X (1002:67ef). The internal panel and the external DisplayPort are both on amdgpu. Omarchy 4.0.4-1, kernel 7.2.6-arch2-Watanare-T2-3-t2. Cmdline has pm_async=off mem_sleep_default=deep and no pcie_ports=compat.

What's wrong?

Lid-closed S3 from 2026-09-23 17:26 to 2026-09-25 07:40 (about 38 h). The kernel resumed (PM: suspend exit, t2bce status 0). The 560X did not, so both displays stayed black until a forced power-off about a minute later:

amdgpu: SMU Firmware start failed!
amdgpu: Failed to load SMU ucode.
amdgpu 0000:01:00.0: amdgpu_device_ip_resume failed (-22).
amdgpu 0000:01:00.0: ring sdma0 timeout, signaled seq=537896, emitted seq=537899
amdgpu 0000:01:00.0: GPU reset begin!

hyprmoncfgd logged could not wake displays: context deadline exceeded. The same boot had five shorter suspends with no SMU error. A reboot brought both displays back.

Not #6862: that journal ends during suspend entry on a t2bce_vhci desync. Here resume completed. Not #8668: that black lid wake recovers in about 22 s. pcie_ports=compat is absent and untested.

Expected: displays come back after a long S3, as they do after a short one.

Filed by Grok 4.7 via Grok Build.

View raw text
### System details

MacBookPro15,1 (`Mac-937A206F2EE63C01`), i7-9750H, UHD 630 + Radeon Pro 560X (`1002:67ef`). The internal panel and the external DisplayPort are both on amdgpu. Omarchy 4.0.4-1, kernel `7.2.6-arch2-Watanare-T2-3-t2`. Cmdline has `pm_async=off mem_sleep_default=deep` and no `pcie_ports=compat`.

### What's wrong?

Lid-closed S3 from 2026-09-23 17:26 to 2026-09-25 07:40 (about 38 h). The kernel resumed (`PM: suspend exit`, `t2bce` status 0). The 560X did not, so both displays stayed black until a forced power-off about a minute later:

```
amdgpu: SMU Firmware start failed!
amdgpu: Failed to load SMU ucode.
amdgpu 0000:01:00.0: amdgpu_device_ip_resume failed (-22).
amdgpu 0000:01:00.0: ring sdma0 timeout, signaled seq=537896, emitted seq=537899
amdgpu 0000:01:00.0: GPU reset begin!
```

`hyprmoncfgd` logged `could not wake displays: context deadline exceeded`. The same boot had five shorter suspends with no SMU error. A reboot brought both displays back.

Not #6862: that journal ends during suspend entry on a `t2bce_vhci` desync. Here resume completed. Not #8668: that black lid wake recovers in about 22 s. `pcie_ports=compat` is absent and untested.

Expected: displays come back after a long S3, as they do after a short one.

Filed by Grok 4.7 via Grok Build.

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 19:41 UTC