Public bug reported:
System:
HP ZBook Firefly G8 laptop, Intel Iris Xe / Tiger Lake graphics, Xubuntu/Ubuntu
26.04.
Problem:
The system intermittently hard-locks and requires forced power-off. The power
LED remains on, the system becomes completely unresponsive, and previous
crashes showed Caps Lock LED flickering/blinking. This is not a normal
application crash or clean shutdown.
Latest crash:
On 2026-06-18 the boot ended abruptly at 10:59:06 MDT. The next boot started at
11:00:45 MDT. kdump was enabled and reported ready, with crashkernel memory
reserved, but no vmcore was captured. /var/crash contained only kdump_lock and
kexec_cmd for the hard lock. This suggests a hard hang/deadlock rather than a
clean kernel panic.
Kernel/debug configuration at time of crash:
The system was booted with:
zswap.enabled=1 i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0
drm.debug=0x1e log_buf_len=4M
XFCE compositor was already disabled. Intel OpenCL packages had been
removed. The crash therefore appears unrelated to compositor effects or
OpenCL workloads.
Observed kernel evidence:
The final kernel messages before logging stopped repeatedly show i915 / DRM
atomic cursor-plane updates on the same pipe/plane:
[CRTC:584:pipe D] with [PLANE:578:cursor D]
drm_atomic_set_fb_for_plane
intel_plane_atomic_calc_changes
visible 1 -> 1, off 0, on 0, ms 0
The same cursor D / pipe D messages repeat continuously at the final
timestamp, 2026-06-18 10:59:06, until logging stops. No clean shutdown,
panic, oops, or vmcore was captured.
Earlier related crash evidence:
Previous crashes also pointed at Intel i915 / DRM display handling, including
stack traces involving:
- i915_hotplug_work_func [i915]
- drm_kms_helper_connector_hotplug_event
- drm_atomic_commit
- intel_atomic_commit
- intel_audio_codec_disable
Expected result:
The system should remain responsive during normal desktop use.
Actual result:
The system hard-locks and requires forced power-off, risking data loss.
Impact:
High/severe. Full system lockup.
Suspected area:
Intel i915 / DRM atomic modesetting, specifically hardware cursor plane
handling on pipe D. External display/dock involvement is possible but not fully
proven.
Next test: I will force Xorg software cursor using the modesetting
driver option SWCursor=true. If this stops the crashes, I will update
the bug because the final logs currently point strongly at the hardware
cursor plane path.
Attachments provided:
- previous-boot-kernel-full.txt
- previous-boot-kernel-filtered.txt
- previous-boot-end.txt
- boots.txt
- cmdline.txt
- uname.txt
- version_signature.txt
- lspci-vvnn.txt
- xrandr.txt
- kdump-status.txt
- var-crash-files.txt
- system-product.txt
- bios-version.txt
- bios-release-date.txt
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-22-generic 7.0.0-22.22
ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0
Uname: Linux 7.0.0-22-generic x86_64
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: notabrick 2889 F.... pipewire
notabrick 2898 F.... wireplumber
/dev/snd/controlC1: notabrick 2898 F.... wireplumber
/dev/snd/seq: notabrick 2889 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Jun 18 11:11:29 2026
InstallationDate: Installed on 2026-05-10 (39 days ago)
InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1)
MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash zswap.enabled=1
i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0 drm.debug=0x1e
log_buf_len=4M
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2026
dmi.bios.release: 24.1
dmi.bios.vendor: HP
dmi.bios.version: T76 Ver. 01.24.01
dmi.board.name: 880D
dmi.board.vendor: HP
dmi.board.version: KBC Version 30.57.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 48.87
dmi.modalias:
dmi:bvnHP:bvrT76Ver.01.24.01:bd03/06/2026:br24.1:efr48.87:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvrSBKPFV3:rvnHP:rn880D:rvrKBCVersion30.57.00:cvnHP:ct10:cvr:sku3V328UT#ABA:pfa103C_5336ANHPZBook:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
dmi.product.sku: 3V328UT#ABA
dmi.product.version: SBKPFV3
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute
** Attachment added: "i915-bug-report-2026-06-18.tar.gz"
https://bugs.launchpad.net/bugs/2157524/+attachment/5978006/+files/i915-bug-report-2026-06-18.tar.gz
** Description changed:
System:
HP ZBook Firefly G8 laptop, Intel Iris Xe / Tiger Lake graphics,
Xubuntu/Ubuntu 26.04.
Problem:
The system intermittently hard-locks and requires forced power-off. The power
LED remains on, the system becomes completely unresponsive, and previous
crashes showed Caps Lock LED flickering/blinking. This is not a normal
application crash or clean shutdown.
Latest crash:
On 2026-06-18 the boot ended abruptly at 10:59:06 MDT. The next boot started
at 11:00:45 MDT. kdump was enabled and reported ready, with crashkernel memory
reserved, but no vmcore was captured. /var/crash contained only kdump_lock and
kexec_cmd for the hard lock. This suggests a hard hang/deadlock rather than a
clean kernel panic.
Kernel/debug configuration at time of crash:
The system was booted with:
zswap.enabled=1 i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0
drm.debug=0x1e log_buf_len=4M
XFCE compositor was already disabled. Intel OpenCL packages had been
removed. The crash therefore appears unrelated to compositor effects or
OpenCL workloads.
Observed kernel evidence:
The final kernel messages before logging stopped repeatedly show i915 / DRM
atomic cursor-plane updates on the same pipe/plane:
[CRTC:584:pipe D] with [PLANE:578:cursor D]
drm_atomic_set_fb_for_plane
intel_plane_atomic_calc_changes
visible 1 -> 1, off 0, on 0, ms 0
The same cursor D / pipe D messages repeat continuously at the final
timestamp, 2026-06-18 10:59:06, until logging stops. No clean shutdown,
panic, oops, or vmcore was captured.
Earlier related crash evidence:
Previous crashes also pointed at Intel i915 / DRM display handling, including
stack traces involving:
- i915_hotplug_work_func [i915]
- drm_kms_helper_connector_hotplug_event
- drm_atomic_commit
- intel_atomic_commit
- intel_audio_codec_disable
Expected result:
The system should remain responsive during normal desktop use.
Actual result:
The system hard-locks and requires forced power-off, risking data loss.
Impact:
High/severe. Full system lockup.
Suspected area:
Intel i915 / DRM atomic modesetting, specifically hardware cursor plane
handling on pipe D. External display/dock involvement is possible but not fully
proven.
+ Next test: I will force Xorg software cursor using the modesetting
+ driver option SWCursor=true. If this stops the crashes, I will update
+ the bug because the final logs currently point strongly at the hardware
+ cursor plane path.
+
Attachments provided:
- previous-boot-kernel-full.txt
- previous-boot-kernel-filtered.txt
- previous-boot-end.txt
- boots.txt
- cmdline.txt
- uname.txt
- version_signature.txt
- lspci-vvnn.txt
- xrandr.txt
- kdump-status.txt
- var-crash-files.txt
- system-product.txt
- bios-version.txt
- bios-release-date.txt
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-22-generic 7.0.0-22.22
ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0
Uname: Linux 7.0.0-22-generic x86_64
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
- USER PID ACCESS COMMAND
- /dev/snd/controlC0: notabrick 2889 F.... pipewire
- notabrick 2898 F.... wireplumber
- /dev/snd/controlC1: notabrick 2898 F.... wireplumber
- /dev/snd/seq: notabrick 2889 F.... pipewire
+ USER PID ACCESS COMMAND
+ /dev/snd/controlC0: notabrick 2889 F.... pipewire
+ notabrick 2898 F.... wireplumber
+ /dev/snd/controlC1: notabrick 2898 F.... wireplumber
+ /dev/snd/seq: notabrick 2889 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Jun 18 11:11:29 2026
InstallationDate: Installed on 2026-05-10 (39 days ago)
InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64
(20260423.1)
MachineType: HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC
ProcEnviron:
- LANG=en_US.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash zswap.enabled=1
i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0 drm.debug=0x1e
log_buf_len=4M
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2026
dmi.bios.release: 24.1
dmi.bios.vendor: HP
dmi.bios.version: T76 Ver. 01.24.01
dmi.board.name: 880D
dmi.board.vendor: HP
dmi.board.version: KBC Version 30.57.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 48.87
dmi.modalias:
dmi:bvnHP:bvrT76Ver.01.24.01:bd03/06/2026:br24.1:efr48.87:svnHP:pnHPZBookFirefly14inchG8MobileWorkstationPC:pvrSBKPFV3:rvnHP:rn880D:rvrKBCVersion30.57.00:cvnHP:ct10:cvr:sku3V328UT#ABA:pfa103C_5336ANHPZBook:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Firefly 14 inch G8 Mobile Workstation PC
dmi.product.sku: 3V328UT#ABA
dmi.product.version: SBKPFV3
dmi.sys.vendor: HP
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2157524
Title:
HP ZBook Firefly G8 hard lock in Intel i915 DRM atomic cursor plane
path
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157524/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
