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

HP EliteBook X Flip G2i: every resume freezes ~13 s on tas2783-sdw speaker amp timeouts — please carry the pending tas2783 resume patches in linux-omarchy

Reported by robbyproc87 · filed Oct 3, 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

HP EliteBook X Flip G2i: every resume freezes ~13 s on tas2783-sdw speaker amp timeouts — please carry the pending tas2783 resume patches in linux-omarchyrevision 1 · captured 2026-10-03 21:10 UTC via poll

What happens

On the HP EliteBook X Flip G2i (Panther Lake, board 8E86), every resume from s2idle freezes the machine for about 13 s. The panel comes back at once and shows the lock screen from before sleep, but userspace is still frozen: keyboard, touchpad and fingerprint do nothing until the kernel finishes resuming. Keys typed in that window are replayed afterwards as a wrong password.

The whole delay is the TI TAS2783 SoundWire speaker amps (snd_soc_tas2783_sdw, four amps on SoundWire link 0-2) timing out in their resume path. Every other device resumes in about 0.5 s.

Evidence

Kernel resume timeline from today's wake (journalctl -k -o json, _SOURCE_MONOTONIC_TIMESTAMP, t=0 at ACPI: EC: interrupt unblocked):

  0.00  ACPI: EC: interrupt unblocked
  0.26  xe 0000:00:02.0: vgaarb: VGA decodes changed ...      <- panel back, lock screen visible
  5.92  slave-tas2783 sdw:0:2:0102:0000:01:9: Initialization not complete
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:c: fw request, wait_event timeout
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:c: Update Slave status failed:-11
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:9: PM: dpm_run_callback(): acpi_subsys_resume returns -110
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:9: PM: failed to resume: error -110
  9.76  slave-tas2783 sdw:0:2:0102:0000:01:a: fw request, wait_event timeout
  9.76  slave-tas2783 sdw:0:2:0102:0000:01:a: Update Slave status failed:-11
 12.90  Restarting tasks: Starting                             <- input/fingerprint usable from here
 12.96  PM: suspend exit

It happens on every wake. Across the last 15 resumes (2026-09-27 to 2026-10-03) the freeze lasted 12.3–13.1 s, and every one showed the amp timeouts. Firmware 8E86-2-0x{9,A,C,D}.bin is present, and the speakers work again after resume. S0ix residency is healthy (about 85 s of hardware sleep in a 98 s suspend).

Upstream status

The latency is a known tas2783-sdw problem with patches in flight on linux-sound:

  • "ASoC: tas2783-sdw: add firmware download status check" (Baojun Xu, TI). It skips the firmware re-download on resume, which the commit message says causes "significant wake-up latency". v3 was posted 2026-08-22 and later versions followed through September. It is not merged as far as I can find. https://ratatoskr.run/lkml/2026/08/17447828
  • "ASoC: tas2783-sdw: drop stale regcache on uninitialized re-attach" is applied to broonie/sound for-7.3 (b627da430357). https://ratatoskr.run/lkml/2026/07/17322574/t

Ask

When the firmware-download-status patch is accepted, please carry it (and the related for-7.3 tas2783 fixes) in linux-omarchy ahead of 7.3. Any TAS2783 SoundWire laptop pays this cost on every wake, and on a lock-on-suspend desktop it looks like a frozen lock screen. I can test a build on this machine.

System

  • Omarchy 4.0.4, kernel 7.2.5-3-omarchy (no newer kernel available as of 2026-10-03)
  • HP EliteBook X Flip G2i 14" (Panther Lake), card sof-soundwire, rt712-sdca (jack/DMIC, link 0-3) + 4x tas2783 (speakers, link 0-2)
  • sof-firmware 2025.12.2-1, linux-firmware 20260810-2

Filed by Claude Opus 5.5 via Claude Code, at the request of the machine's owner.

View raw text
## What happens

On the HP EliteBook X Flip G2i (Panther Lake, board `8E86`), every resume from s2idle freezes the machine for about 13 s. The panel comes back at once and shows the lock screen from before sleep, but userspace is still frozen: keyboard, touchpad and fingerprint do nothing until the kernel finishes resuming. Keys typed in that window are replayed afterwards as a wrong password.

The whole delay is the TI TAS2783 SoundWire speaker amps (`snd_soc_tas2783_sdw`, four amps on SoundWire link 0-2) timing out in their resume path. Every other device resumes in about 0.5 s.

## Evidence

Kernel resume timeline from today's wake (`journalctl -k -o json`, `_SOURCE_MONOTONIC_TIMESTAMP`, t=0 at `ACPI: EC: interrupt unblocked`):

```
  0.00  ACPI: EC: interrupt unblocked
  0.26  xe 0000:00:02.0: vgaarb: VGA decodes changed ...      <- panel back, lock screen visible
  5.92  slave-tas2783 sdw:0:2:0102:0000:01:9: Initialization not complete
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:c: fw request, wait_event timeout
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:c: Update Slave status failed:-11
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:9: PM: dpm_run_callback(): acpi_subsys_resume returns -110
  6.68  slave-tas2783 sdw:0:2:0102:0000:01:9: PM: failed to resume: error -110
  9.76  slave-tas2783 sdw:0:2:0102:0000:01:a: fw request, wait_event timeout
  9.76  slave-tas2783 sdw:0:2:0102:0000:01:a: Update Slave status failed:-11
 12.90  Restarting tasks: Starting                             <- input/fingerprint usable from here
 12.96  PM: suspend exit
```

It happens on every wake. Across the last 15 resumes (2026-09-27 to 2026-10-03) the freeze lasted 12.3–13.1 s, and every one showed the amp timeouts. Firmware `8E86-2-0x{9,A,C,D}.bin` is present, and the speakers work again after resume. S0ix residency is healthy (about 85 s of hardware sleep in a 98 s suspend).

## Upstream status

The latency is a known tas2783-sdw problem with patches in flight on linux-sound:

- "ASoC: tas2783-sdw: add firmware download status check" (Baojun Xu, TI). It skips the firmware re-download on resume, which the commit message says causes "significant wake-up latency". v3 was posted 2026-08-22 and later versions followed through September. It is not merged as far as I can find. https://ratatoskr.run/lkml/2026/08/17447828
- "ASoC: tas2783-sdw: drop stale regcache on uninitialized re-attach" is applied to broonie/sound for-7.3 (`b627da430357`). https://ratatoskr.run/lkml/2026/07/17322574/t

## Ask

When the firmware-download-status patch is accepted, please carry it (and the related for-7.3 tas2783 fixes) in `linux-omarchy` ahead of 7.3. Any TAS2783 SoundWire laptop pays this cost on every wake, and on a lock-on-suspend desktop it looks like a frozen lock screen. I can test a build on this machine.

## System

- Omarchy 4.0.4, kernel `7.2.5-3-omarchy` (no newer kernel available as of 2026-10-03)
- HP EliteBook X Flip G2i 14" (Panther Lake), card `sof-soundwire`, rt712-sdca (jack/DMIC, link 0-3) + 4x tas2783 (speakers, link 0-2)
- sof-firmware 2025.12.2-1, linux-firmware 20260810-2

Filed by Claude Opus 5.5 via Claude Code, at the request of the machine's owner.

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 21:07 UTC