Dell XPS 14 DA14260 periodic hard reset after unplugging; power-button diagnostic blink code

[rblalock]

Summary

On a Dell XPS 14 DA14260 running Omarchy, the laptop periodically hard-resets/reboots after having been plugged in for a while and then unplugged. This happens roughly once a week. The most recent event occurred while running on battery only (no charger attached).

After the reboot, the power button was flashing a repeating diagnostic pattern that looked like 6 white flashes followed by 1 red/amber flash. If Dell's diagnostic sequence starts with amber/red after the pause, this may correspond to 1 amber/red + 6 white.

Hardware / system

• Machine: Dell XPS 14 DA14260
• Board: Dell 0RMV2Y
• BIOS: 1.2.1, 2026-01-09
• Omarchy: 3.8.1
• Kernel: 7.0.3-arch1-2-ptl
• CPU: Intel Core Ultra X7 358H / Panther Lake
• GPU driver: xe
• Battery health: good, ~94% charge at triage, 12 cycles
• No charger connected during triage; system correctly showed AC offline / battery discharging

Impact

The machine abruptly reboots without a clean shutdown. This appears to be a hard reset / firmware-platform event rather than a normal userspace crash.

last -x shows multiple unclean crashes over the last couple of weeks:

------- tty1  Wed May 20 13:12 - crash (2+08:52)
reboot   system boot  7.0.3-arch1-2-p* Wed May 20 13:12   still running
-------- tty1  Sat May 16 20:17 - crash  (19:23)
reboot   system boot  7.0.3-arch1-2-p* Sat May 16 20:17 - crash  (19:23)
--------- tty1  Sat May  9 13:12 - crash (5+08:40)
reboot   system boot  7.0.3-arch1-2-p* Sat May  9 13:12 - crash (5+08:40)

Most recent event

Previous boot stopped logging at about 2026-05-22 22:03:29. Current boot started at 2026-05-22 22:04:43. There was no clean shutdown record.

The final relevant kernel logs in the previous boot show a suspend/resume sequence shortly before the hard reset:

May 22 21:52:38 arch2 kernel: Freezing user space processes completed (elapsed 0.002 seconds)
May 22 21:52:38 arch2 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
May 22 21:52:38 arch2 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 22 21:52:38 arch2 kernel: Intel CVS driver i2c-INTC10E1:00: cvs_suspend:entered
May 22 21:52:38 arch2 kernel: Intel CVS driver i2c-INTC10E1:00: cvs_suspend:wait for fw update cancel
May 22 21:52:38 arch2 kernel: Intel CVS driver i2c-INTC10E1:00: cvs_suspend:fw update cancelled
May 22 21:52:38 arch2 kernel: Intel CVS driver i2c-INTC10E1:00: cvs_suspend:completed
May 22 21:52:38 arch2 kernel: ACPI: EC: interrupt blocked
May 22 21:52:38 arch2 kernel: ACPI: EC: interrupt unblocked
May 22 21:52:38 arch2 kernel: intel-ipu7 0000:00:05.0: IPU7 in secure mode
May 22 21:52:38 arch2 kernel: Intel CVS driver i2c-INTC10E1:00: cvs_resume entered
May 22 21:52:38 arch2 kernel: Intel CVS driver i2c-INTC10E1:00: cvs_resume:completed
May 22 21:52:38 arch2 kernel: irq 221, desc: 00000000515f9b86, depth: 0, count: 0, unhandled: 0
May 22 21:52:38 arch2 kernel: ->handle_irq():  00000000bd1e13be, handle_bad_irq+0x0/0x50
May 22 21:52:38 arch2 kernel: ->action->handler(): 0000000040eed274, irq_nested_primary_handler+0x0/0x20
May 22 21:52:38 arch2 kernel:    IRQ_NOPROBE set
May 22 21:52:38 arch2 kernel: unexpected IRQ trap at vector dd
May 22 21:52:38 arch2 kernel: PM: suspend exit

Current boot warnings after the reset

The current boot has recurring platform/IRQ warnings:

May 22 22:04:43 ----- kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
May 22 22:04:43 ------ kernel: handlers:
May 22 22:04:43 ------ kernel: [<00000000cf12be22>] idma64_irq [idma64]
May 22 22:04:43 ------ kernel: Disabling IRQ #16

And an Intel CVS warning during probe:

May 22 22:04:45 ---- kernel: Intel CVS driver i2c-INTC10E1:00: cvs_common_probe: probed as i2c device
May 22 22:04:45 ---- kernel: ------------[ cut here ]------------
May 22 22:04:45 ---- kernel: new->flags & IRQF_ONESHOT && !new->thread_fn
May 22 22:04:45 ---- kernel: WARNING: kernel/irq/manage.c:1502 at __setup_irq+0x641/0x750, CPU#13: (udev-worker)/847
May 22 22:04:45 ---- kernel: Call Trace:
May 22 22:04:45 ---- kernel:  request_threaded_irq+0xe7/0x1e0
May 22 22:04:45 ---- kernel:  devm_request_threaded_irq+0x94/0x160
May 22 22:04:45 ---- kernel:  cvs_common_probe.cold+0x2bf/0x4ba [intel_cvs]
May 22 22:04:45 ---- kernel:  i2c_device_probe+0x38d/0x3f0
May 22 22:04:45 ---- kernel:  really_probe+0xe9/0x3a0
May 22 22:04:45 ---- kernel:  driver_register+0x75/0xe0
May 22 22:04:45 ---- kernel:  i2c_register_driver+0x50/0xe0
May 22 22:04:45 ---- kernel:  icvs_init+0x1d/0xff0 [intel_cvs]

There have also been earlier USB-C / UCSI errors on prior boots/resumes:

ucsi_acpi USBC000:00: unknown error 0
ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)

Notes / hypothesis

Because the reboot is abrupt and the power button shows a Dell diagnostic blink code, this may be an EC / firmware / platform-power issue rather than an Omarchy userspace issue. However, since this is on Omarchy's Panther Lake kernel stack (linux-ptl) and seems correlated with plug/unplug / suspend/resume behavior, I'm filing here to see if this matches any known Dell XPS 14 DA14260 / Panther Lake / linux-ptl issue or if there is a recommended kernel/package mitigation.

Potential areas implicated by logs:

• ACPI EC / embedded controller
• USB-C / UCSI power negotiation after unplugging
• interrupt routing (unexpected IRQ trap, irq 16: nobody cared)
• Intel CVS / IPU7 camera stack on suspend/resume

[dhh]

cc @spencerbull

[spencerbull]

@rblalock What BIOS version are you on? cat /sys/class/dmi/id/bios_version

[rblalock]

@spencerbull

3.25

[spencerbull]

@spencerbull

3.25

@rblalock Can you try a firmware update. I'm on 1.5.1 and have not had the freezing issue on my XPS 14. You can try an Omarchy (copilot) key -> update -> firmware to see if it pulls it in via LVFS.

If nothing shows there, you will have to boot into bios and can do a remote firmware update from there over wifi to get you on 1.5.1.

[rblalock]

ok updated. will see how it works.

[rblalock]

I'm going to close this for now. i haven't had an issue since updating bios.