** Description changed:

  System: HP ZBook Firefly G8 laptop, Intel Iris Xe / Tiger Lake graphics,
  Xubuntu/Ubuntu 26.04, kernel 7.0.0-22-generic.
  
  Problem:
  The system hard-locks and requires a forced power-off. The power LED remains 
on, the system is completely unresponsive, and in earlier crashes the Caps Lock 
LED flickered/blinked. This is not a normal application crash or clean shutdown.
  
  The issue has occurred more than once. It previously appeared related to
  Intel i915/DRM display handling. Earlier logs showed a stack trace
  involving:
  
  - i915_hotplug_work_func [i915]
  - drm_kms_helper_connector_hotplug_event
  - drm_atomic_commit
  - intel_atomic_commit
  - intel_audio_codec_disable
  
  For the latest crash, kdump was enabled and reported ready, and
  crashkernel memory was reserved, but no vmcore was captured. /var/crash
  only contained kdump_lock and kexec_cmd. This suggests a hard
  hang/deadlock rather than a clean kernel panic.
  
  Current boot/debug parameters:
  zswap.enabled=1 i915.enable_psr=0 i915.enable_dc=0 drm.debug=0x1e 
log_buf_len=4M
  
  After the next reboot I also added:
  i915.enable_fbc=0
  
  The XFCE compositor was already disabled when the crash occurred. I had
  previously installed Intel OpenCL packages but removed them; this crash
  appears to be in the kernel DRM/i915 display path, not an OpenCL compute
  workload.
  
  Programs running:  Qgis 3.44, firefox with Gmail on one tab and youtube
- playing music on another, Chrome browser with multiple tabs open
+ playing music on another, Chrome browser with multiple tabs open,
+ Syncthing running in background, Libreoffice and imwheel
  
  my setup has 4 displays running simultaneously, laptop built in + HDIM +
  2 connected to a lenovo usbC dock using alt mode (the dock is also
  providing power, network and connecting to my keyboard and mouse)
  
  I was also listening to music via a bluetooth headset
+ 
+ the crash occurred when moving a browser window between a screen
+ connected through the USB-C dock and the one connected via HDMI.
  
  Latest observed evidence:
  The previous boot ended abruptly. With drm.debug=0x1e enabled, the final 
kernel messages before the lockup show repeated i915/DRM atomic display 
activity, including atomic cursor/plane updates such as 
drm_atomic_set_fb_for_plane, intel_plane_atomic_calc_changes, 
drm_atomic_commit, and CRTC/cursor plane references. There was no clean 
shutdown, no vmcore, and no obvious storage/NVMe/MCE error in the captured 
evidence.
  
  External display/dock involvement is suspected but not fully proven.
  Earlier evidence pointed more clearly at display hotplug/modesetting;
  the latest crash looked more like atomic cursor/plane activity before
  the lockup.
  
  Expected result:
  System should remain responsive and not hard-lock during normal desktop use.
  
  Actual result:
  System hard-locks and requires forced power-off.
  
  Impact:
  This is severe because it causes full system lockup and possible data loss.
  
  I have attached:
  - previous-boot-kernel-full.txt
  - previous-boot-kernel-filtered.txt
  - previous-boot-end.txt
  - boots.txt
  - cmdline.txt
  - uname.txt
  - kdump-status.txt
  - var-crash-files.txt
  - system-product.txt
  - bios-version.txt
  - bios-release-date.txt
  - xrandr-after-reboot.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   2578 F.... pipewire
-                       notabrick   2592 F.... wireplumber
-  /dev/snd/controlC1:  notabrick   2592 F.... wireplumber
-  /dev/snd/seq:        notabrick   2578 F.... pipewire
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC0:  notabrick   2578 F.... pipewire
+                       notabrick   2592 F.... wireplumber
+  /dev/snd/controlC1:  notabrick   2592 F.... wireplumber
+  /dev/snd/seq:        notabrick   2578 F.... pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Jun 10 10:46:23 2026
  InstallationDate: Installed on 2026-05-10 (31 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 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

** Description changed:

  System: HP ZBook Firefly G8 laptop, Intel Iris Xe / Tiger Lake graphics,
- Xubuntu/Ubuntu 26.04, kernel 7.0.0-22-generic.
+ Xubuntu/Ubuntu 26.04, kernel 7.0.0-22-generic.  (all installed software
+ updated via apt on June 9, 2026)
  
  Problem:
  The system hard-locks and requires a forced power-off. The power LED remains 
on, the system is completely unresponsive, and in earlier crashes the Caps Lock 
LED flickered/blinked. This is not a normal application crash or clean shutdown.
  
  The issue has occurred more than once. It previously appeared related to
  Intel i915/DRM display handling. Earlier logs showed a stack trace
  involving:
  
  - i915_hotplug_work_func [i915]
  - drm_kms_helper_connector_hotplug_event
  - drm_atomic_commit
  - intel_atomic_commit
  - intel_audio_codec_disable
  
  For the latest crash, kdump was enabled and reported ready, and
  crashkernel memory was reserved, but no vmcore was captured. /var/crash
  only contained kdump_lock and kexec_cmd. This suggests a hard
  hang/deadlock rather than a clean kernel panic.
  
  Current boot/debug parameters:
  zswap.enabled=1 i915.enable_psr=0 i915.enable_dc=0 drm.debug=0x1e 
log_buf_len=4M
  
  After the next reboot I also added:
  i915.enable_fbc=0
  
  The XFCE compositor was already disabled when the crash occurred. I had
  previously installed Intel OpenCL packages but removed them; this crash
  appears to be in the kernel DRM/i915 display path, not an OpenCL compute
  workload.
  
  Programs running:  Qgis 3.44, firefox with Gmail on one tab and youtube
  playing music on another, Chrome browser with multiple tabs open,
  Syncthing running in background, Libreoffice and imwheel
  
  my setup has 4 displays running simultaneously, laptop built in + HDIM +
  2 connected to a lenovo usbC dock using alt mode (the dock is also
  providing power, network and connecting to my keyboard and mouse)
  
  I was also listening to music via a bluetooth headset
  
  the crash occurred when moving a browser window between a screen
  connected through the USB-C dock and the one connected via HDMI.
  
  Latest observed evidence:
  The previous boot ended abruptly. With drm.debug=0x1e enabled, the final 
kernel messages before the lockup show repeated i915/DRM atomic display 
activity, including atomic cursor/plane updates such as 
drm_atomic_set_fb_for_plane, intel_plane_atomic_calc_changes, 
drm_atomic_commit, and CRTC/cursor plane references. There was no clean 
shutdown, no vmcore, and no obvious storage/NVMe/MCE error in the captured 
evidence.
  
  External display/dock involvement is suspected but not fully proven.
  Earlier evidence pointed more clearly at display hotplug/modesetting;
  the latest crash looked more like atomic cursor/plane activity before
  the lockup.
  
  Expected result:
  System should remain responsive and not hard-lock during normal desktop use.
  
  Actual result:
  System hard-locks and requires forced power-off.
  
  Impact:
  This is severe because it causes full system lockup and possible data loss.
  
  I have attached:
  - previous-boot-kernel-full.txt
  - previous-boot-kernel-filtered.txt
  - previous-boot-end.txt
  - boots.txt
  - cmdline.txt
  - uname.txt
  - kdump-status.txt
  - var-crash-files.txt
  - system-product.txt
  - bios-version.txt
  - bios-release-date.txt
  - xrandr-after-reboot.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   2578 F.... pipewire
                        notabrick   2592 F.... wireplumber
   /dev/snd/controlC1:  notabrick   2592 F.... wireplumber
   /dev/snd/seq:        notabrick   2578 F.... pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Jun 10 10:46:23 2026
  InstallationDate: Installed on 2026-05-10 (31 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 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/2156374

Title:
  HP ZBook Firefly G8 hard lockup in Intel i915/DRM atomic display path
  on 7.0.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156374/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to