November 18, 2026

Omarchy works around an HP BIOS bug so the ZBook Ultra G3a 16 wakes in under a second

0

A single kernel parameter, scoped to one HP model, turns an 80-second freeze after sleep into a sub-second resume.

GitHub card for pull request 19233 in omacom/omarchy, 'Wake the HP ZBook Ultra G3a 16 from sleep without an 80 second freeze', by dhh

Image: omacom/omarchy pull request #19233 (GitHub)

Good news for anyone running Omarchy on the HP ZBook Ultra G3a 16: waking the laptop from sleep is about to go from painful to instant. DHH merged a fix on November 17, 2026 that brings resume time on that machine down to under a second. It’s coming in the next version of Omarchy.

The problem was severe. According to the pull request, every wake from sleep froze the whole machine for about 80 seconds. After a long sleep, it often never came back at all and needed a hard power-off.

The culprit isn’t Linux. The pull request traces it to a bug in HP’s BIOS (version Y86 01.01.07, the latest HP has published). When the kernel powers the SSD back on, the firmware fires HP’s Opal drive-unlock-on-resume handler, even on a drive with no Opal locking enabled. That handler makes the SSD DMA into a buffer in ACPI NVS memory that the IOMMU has no mapping for. The IOMMU blocks the access, the command never completes, and every CPU core waits until the handler times out. Each bad resume leaves an IO_PAGE_FAULT at address 0x49319000 in the logs.

The workaround is to boot with iommu.passthrough=1, which lets the handler’s DMA land. According to the PR, in a 60-second rtcwake suspend on the machine, NVMe resume dropped from 80.5 seconds to 0.83 seconds, with no page faults and no RCU stalls.

There is a trade-off, and the PR spells it out: internal devices lose DMA translation. Thunderbolt and other external devices are marked untrusted and stay translated. The issue has been reported to AMD and HP, and the fix is meant to be dropped once a BIOS update repairs the handler.

The change is tightly scoped. It only applies to machines that report the product name “ZBook Ultra G3a 16”, the only model tested. The 14-inch G3a and the ZBook Ultra G1a belong to the same product family but are left alone, and a test makes sure the G1a stays untouched.

New installs get the fix during hardware setup. Existing installs on the G3a 16 get it through a migration that writes the boot entry setting, rebuilds the boot image once and asks for a reboot.

Source: https://github.com/omacom/omarchy/pull/19233

Leave a Reply

Your email address will not be published. Required fields are marked *