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-4341GitHub issuePublicReceived

XPS 14 internal panel frozen after 3.7.0 upgrade — xe driver DSB timeout on Panther Lake

Reported by rblalock · filed May 4, 2026Closed upstream on 2026-05-04 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

XPS 14 internal panel frozen after 3.7.0 upgrade — xe driver DSB timeout on Panther Lakerevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.7, Dell XPS 2026

What's wrong?

Bug Report: XPS 14 (Dell DA14260) internal panel freezes on Omarchy 3.7 / kernel 7.0.3

Summary

After upgrading to Omarchy 3.7.0 (kernel 7.0.3-arch1-1-ptl), the laptop's internal panel (eDP-1) freezes completely during boot, before Hyprland starts. The external display (DP-1) works fine. Rolling back to the 3.6.0 snapshot (kernel 6.19.13-arch1-1-ptl) resolves the issue.

Hardware

  • Laptop: Dell XPS 14 DA14260 (firmware 1.2.1)
  • Panel: LG Display 0x07C6 (2880x1800)
  • GPU: Intel Panther Lake (Core Ultra X7 358H) — xe driver, device ID 8086:b080
  • External: LG TV via DP-1 (3840x2160) — works fine

Reproduction Steps

  1. Be on Omarchy 3.7.0 with kernel 7.0.3-arch1-1-ptl
  2. Boot with xe.enable_panel_replay=0 (already present from previous configs)
  3. Internal eDP-1 panel freezes during DRM init, external DP-1 works normally

Expected Behavior

Internal panel should initialize and remain responsive, as it did on kernel 6.19.13.

Actual Behavior

Internal panel is completely frozen. Hyprland IPC times out when trying to re-enable it. Only external display is usable.

Kernel Errors (from journalctl -b 0 -k)

xe 0000:00:02.0: [drm] Selective fetch area calculation failed in pipe A
xe 0000:00:02.0: [drm] *ERROR* Tile0: GT1: GSC proxy component not bound!
xe 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] DSB 0 poll error
xe 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
xe 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] DSB 0 timed out waiting for idle (current head=0x240, head=0x0, tail=0x280)

Boot Parameters

Current (broken): fred=on rtc_cmos.use_acpi_alarm=1 resume=/dev/mapper/root resume_offset=3260137 xe.enable_panel_replay=0 quiet splash loglevel=0 systemd.show_status=false rd.udev.log_level=0 vt.global_cursor_default=0 cryptdevice=PARTUUID=... root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs

Working Snapshot (for reference)

The 3.6.0 snapshot at 2026-05-04 11:48:36 (kernel 6.19.13-arch1-1-ptl) boots fine with identical boot parameters minus fred=on.

The 3.5.1 snapshot at 2026-04-23 (kernel 6.19.10-arch1-1-ptl) also worked and included xe.enable_psr=0.

What Was Tried (did not fix it)

  • Forcing 60Hz and scale=2 on eDP-1 via ~/.config/hypr/monitors.conf — config applies but panel was already frozen from kernel init
  • Cycling dpms off / dpms on via hyprctl — IPC timed out because the Xe DSB engine is deadlocked
  • Rebooting with the 60Hz config — same freeze pattern, because the failure occurs during kernel DRM init before userspace

Root Cause Analysis

The regression appears to be in the Intel xe driver between kernel 6.19.13 and 7.0.3 on Panther Lake (device ID 8086:b080). The "Selective fetch area calculation failed in pipe A" error happens during boot-time DRM initialization, corrupting the display state buffer (DSB) for the internal panel. Once DSB is deadlocked, no userspace compositor can recover it.

Version Info

  • Omarchy: 3.7.0
  • Kernel: 7.0.3-arch1-1-ptl (broken) vs 6.19.13-arch1-1-ptl (working)
  • Hyprland: 0.54.3
  • Firmware: Dell 1.2.1 (2026-01-09)
View raw text
### System details

Omarchy 3.7, Dell XPS 2026

### What's wrong?

## Bug Report: XPS 14 (Dell DA14260) internal panel freezes on Omarchy 3.7 / kernel 7.0.3

### Summary
After upgrading to Omarchy 3.7.0 (kernel `7.0.3-arch1-1-ptl`), the laptop's internal panel (eDP-1) freezes completely during boot, before Hyprland starts. The external display (DP-1) works fine. Rolling back to the 3.6.0 snapshot (kernel `6.19.13-arch1-1-ptl`) resolves the issue.

### Hardware
- **Laptop:** Dell XPS 14 DA14260 (firmware 1.2.1)
- **Panel:** LG Display 0x07C6 (2880x1800)
- **GPU:** Intel Panther Lake (Core Ultra X7 358H) — `xe` driver, device ID `8086:b080`
- **External:** LG TV via DP-1 (3840x2160) — works fine

### Reproduction Steps
1. Be on Omarchy 3.7.0 with kernel `7.0.3-arch1-1-ptl`
2. Boot with `xe.enable_panel_replay=0` (already present from previous configs)
3. Internal eDP-1 panel freezes during DRM init, external DP-1 works normally

### Expected Behavior
Internal panel should initialize and remain responsive, as it did on kernel 6.19.13.

### Actual Behavior
Internal panel is completely frozen. Hyprland IPC times out when trying to re-enable it. Only external display is usable.

### Kernel Errors (from `journalctl -b 0 -k`)
```
xe 0000:00:02.0: [drm] Selective fetch area calculation failed in pipe A
xe 0000:00:02.0: [drm] *ERROR* Tile0: GT1: GSC proxy component not bound!
xe 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] DSB 0 poll error
xe 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
xe 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] DSB 0 timed out waiting for idle (current head=0x240, head=0x0, tail=0x280)
```

### Boot Parameters
Current (broken): `fred=on rtc_cmos.use_acpi_alarm=1 resume=/dev/mapper/root resume_offset=3260137 xe.enable_panel_replay=0 quiet splash loglevel=0 systemd.show_status=false rd.udev.log_level=0 vt.global_cursor_default=0 cryptdevice=PARTUUID=... root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs`

### Working Snapshot (for reference)
The 3.6.0 snapshot at 2026-05-04 11:48:36 (kernel `6.19.13-arch1-1-ptl`) boots fine with identical boot parameters minus `fred=on`.

The 3.5.1 snapshot at 2026-04-23 (kernel `6.19.10-arch1-1-ptl`) also worked and included `xe.enable_psr=0`.

### What Was Tried (did not fix it)
- Forcing `60Hz` and `scale=2` on eDP-1 via `~/.config/hypr/monitors.conf` — config applies but panel was already frozen from kernel init
- Cycling `dpms off` / `dpms on` via `hyprctl` — IPC timed out because the Xe DSB engine is deadlocked
- Rebooting with the 60Hz config — same freeze pattern, because the failure occurs during kernel DRM init before userspace

### Root Cause Analysis
The regression appears to be in the Intel `xe` driver between kernel `6.19.13` and `7.0.3` on Panther Lake (device ID `8086:b080`). The "Selective fetch area calculation failed in pipe A" error happens during boot-time DRM initialization, corrupting the display state buffer (DSB) for the internal panel. Once DSB is deadlocked, no userspace compositor can recover it.

### Version Info
- **Omarchy:** 3.7.0
- **Kernel:** `7.0.3-arch1-1-ptl` (broken) vs `6.19.13-arch1-1-ptl` (working)
- **Hyprland:** 0.54.3
- **Firmware:** Dell 1.2.1 (2026-01-09)

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.