Proof Portal
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.
SoundWire bus clash/parity errors isolated to one link cause speaker dropout on Dell XPS 14 2026 (Panther Lake/HURACAN)
Reported by vitillo · filed Sep 3, 2026Closed upstream on 2026-09-03 by its own reporter vitillo. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
System details
Dell XPS 14 (DA14260, "HURACAN"), Intel Core Ultra X7 358H (Panther Lake), Omarchy 4.0.2, kernel 7.1.8-arch1-2-ptl
What's wrong?
Intermittent audio dropout on one side of the internal speakers: audio keeps playing on one channel while the other briefly goes silent, then recovers. Happens under normal desktop use, no particular trigger identified yet.
This isn't a PipeWire/software mixing issue — pactl list sinks shows the speaker sink's left/right volumes both at 100%/0dB with balance 0.00 and no mute, before/during/after the dropout.
The kernel log shows the real cause: recurring SoundWire bus-level faults, but isolated to one of the two SoundWire links driving the 4 internal speaker amps (cs35l56 x4, 2 amps per link):
$ journalctl -k --since "-7 days" | grep -iE "soundwire_intel.*(clash|parity)"
Sep 02 21:20:47 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 02 21:23:24 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 02 21:23:24 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 02 21:24:22 hyperion kernel: soundwire_intel soundwire_intel.link.3: Parity error
Sep 02 21:24:22 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 02 21:24:22 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 02 21:28:41 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 02 21:28:41 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 02 21:29:38 hyperion kernel: soundwire_intel soundwire_intel.link.3: Parity error
Sep 02 21:29:38 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 02 21:30:31 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 02 21:30:31 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 02 21:34:00 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 02 21:34:00 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 03 12:59:58 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 03 13:01:17 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 03 13:04:54 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 03 13:12:50 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 03 16:21:35 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 03 16:21:35 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word
Sep 03 16:26:12 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word
Sep 03 16:26:46 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word- 23 of 23 events over the last 7 days are on
soundwire_intel.link.3. - Zero on
soundwire_intel.link.2, the other link carrying the other 2 amps. - Recurs roughly daily, no audio-heavy workload needed to trigger it.
Amp/topology enumeration at boot, for reference:
sof-audio-pci-intel-ptl 0000:00:1f.3: loading topology 2: intel/sof-ipc4-tplg/sof-sdca-2amp-id2.tplg
cs35l56 sdw:0:2:01fa:3557:01:2: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid1-l2u2.bin (v1): v4.5.9
cs35l56 sdw:0:2:01fa:3557:01:3: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid0-l2u3.bin (v1): v4.5.9
cs35l56 sdw:0:3:01fa:3557:01:0: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid0-l3u0.bin (v1): v4.5.9
cs35l56 sdw:0:3:01fa:3557:01:1: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid0-l3u1.bin (v1): v4.5.9Why this looks like a driver issue, not a hardware defect
"Bus clash"/"parity error" reports from SoundWire slaves have a documented history of being spurious — slaves reporting a clash interrupt right after a bus reset, before the interrupt mask is even enabled, which is not a real electrical fault. That was fixed upstream around kernel 5.13 with a driver-level "master quirk" to discard the spurious ones, for the SoundWire generations that existed then. This is a very new Panther Lake platform (HURACAN) whose SoundWire enablement is still landing upstream, so it seems plausible the same class of quirk hasn't been extended to whatever SoundWire IP revision this platform uses — rather than an actual damaged amp/connector.
Steps to reproduce
No specific trigger isolated yet — happens intermittently during normal desktop use. Happy to capture a tighter repro (dmesg -w running live, correlated to the exact moment of an audible dropout) if that's useful.
Expected
No SoundWire bus faults; both amp pairs stay in sync with playback, no audible channel dropout.
View raw text
### System details Dell XPS 14 (DA14260, "HURACAN"), Intel Core Ultra X7 358H (Panther Lake), Omarchy 4.0.2, kernel 7.1.8-arch1-2-ptl ### What's wrong? Intermittent audio dropout on one side of the internal speakers: audio keeps playing on one channel while the other briefly goes silent, then recovers. Happens under normal desktop use, no particular trigger identified yet. This isn't a PipeWire/software mixing issue — `pactl list sinks` shows the speaker sink's left/right volumes both at 100%/0dB with balance 0.00 and no mute, before/during/after the dropout. The kernel log shows the real cause: recurring SoundWire bus-level faults, but isolated to **one of the two SoundWire links** driving the 4 internal speaker amps (`cs35l56` x4, 2 amps per link): ``` $ journalctl -k --since "-7 days" | grep -iE "soundwire_intel.*(clash|parity)" Sep 02 21:20:47 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 02 21:23:24 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 02 21:23:24 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 02 21:24:22 hyperion kernel: soundwire_intel soundwire_intel.link.3: Parity error Sep 02 21:24:22 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 02 21:24:22 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 02 21:28:41 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 02 21:28:41 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 02 21:29:38 hyperion kernel: soundwire_intel soundwire_intel.link.3: Parity error Sep 02 21:29:38 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 02 21:30:31 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 02 21:30:31 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 02 21:34:00 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 02 21:34:00 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 03 12:59:58 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 03 13:01:17 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 03 13:04:54 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 03 13:12:50 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 03 16:21:35 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 03 16:21:35 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word Sep 03 16:26:12 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for control word Sep 03 16:26:46 hyperion kernel: soundwire_intel soundwire_intel.link.3: Bus clash for data word ``` - **23 of 23** events over the last 7 days are on `soundwire_intel.link.3`. - **Zero** on `soundwire_intel.link.2`, the other link carrying the other 2 amps. - Recurs roughly daily, no audio-heavy workload needed to trigger it. Amp/topology enumeration at boot, for reference: ``` sof-audio-pci-intel-ptl 0000:00:1f.3: loading topology 2: intel/sof-ipc4-tplg/sof-sdca-2amp-id2.tplg cs35l56 sdw:0:2:01fa:3557:01:2: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid1-l2u2.bin (v1): v4.5.9 cs35l56 sdw:0:2:01fa:3557:01:3: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid0-l2u3.bin (v1): v4.5.9 cs35l56 sdw:0:3:01fa:3557:01:0: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid0-l3u0.bin (v1): v4.5.9 cs35l56 sdw:0:3:01fa:3557:01:1: DSP1: cirrus/cs35l57-b2-dsp1-misc-10280db9-spkid0-l3u1.bin (v1): v4.5.9 ``` ### Why this looks like a driver issue, not a hardware defect "Bus clash"/"parity error" reports from SoundWire slaves have a documented history of being *spurious* — slaves reporting a clash interrupt right after a bus reset, before the interrupt mask is even enabled, which is not a real electrical fault. That was fixed upstream around kernel 5.13 with a driver-level "master quirk" to discard the spurious ones, for the SoundWire generations that existed then. This is a very new Panther Lake platform (HURACAN) whose SoundWire enablement is still landing upstream, so it seems plausible the same class of quirk hasn't been extended to whatever SoundWire IP revision this platform uses — rather than an actual damaged amp/connector. ### Steps to reproduce No specific trigger isolated yet — happens intermittently during normal desktop use. Happy to capture a tighter repro (`dmesg -w` running live, correlated to the exact moment of an audible dropout) if that's useful. ### Expected No SoundWire bus faults; both amp pairs stay in sync with playback, no audible channel dropout.
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.