Boot hangs after kernel upgrade to 6.2.0-26-generic

[Wade Cline]

This could be a bug in the linux-image package, but it might also be an issue with missing firmware (ref: https://ubuntuforums.org/showthread.php?t=2489771&page=2&s=565081c5663bac1bf6994963b20e9f83).

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
Broken Linux kernel version: 6.2.0-26-generic
Working Linux kernel version: 5.19.0-50-generic

3) What you expected to happen
Successful boot

4) What happened instead
Hangs indefinitely (at least more than two minutes)

From the "DebuggingKernelBoot" Wiki page:

>The appropriate log(s) in their entirety from /var/log uncompressed.
No boots logs are generated; the boot hangs before the root filesystem is decrypted.

>An unedited video of the entire bad boot from start to finish via cellphone or camera recording.
Will try and upload as second attachment; may run into space constraints.

>A picture of the bad boot via cellphone or camera.
See: IMG20230814161928.jpg

>For example, if you notice ACPI errors, try booting with the acpi=off boot option. For a full description of these options, refer to the kernel parameters document.
This successfully boots the kernel, but neither the secondary HDMI-attached monitor nor the tertiary docking-station attached monitor then work.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: i3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-08 (293 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: HP HP ZBook Fury 16 G9 Mobile Workstation PC
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash
ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-50-generic N/A
 linux-backports-modules-5.19.0-50-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.18
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: jammy
Uname: Linux 5.19.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 06/26/2023
dmi.bios.release: 8.0
dmi.bios.vendor: HP
dmi.bios.version: U96 Ver. 01.08.00
dmi.board.name: 89C6
dmi.board.vendor: HP
dmi.board.version: KBC Version 15.63.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 21.99
dmi.modalias: dmi:bvnHP:bvrU96Ver.01.08.00:bd06/26/2023:br8.0:efr21.99:svnHP:pnHPZBookFury16G9MobileWorkstationPC:pvr:rvnHP:rn89C6:rvrKBCVersion15.63.00:cvnHP:ct10:cvr:sku78K31UP#ABA:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Fury 16 G9 Mobile Workstation PC
dmi.product.sku: 78K31UP#ABA
dmi.sys.vendor: HP

[Wade Cline (wtcline)]

Add video of boot hang.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2032538/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2032538

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

apport information

[Wade Cline (wtcline)]

Note that apport collected information for Linux 5.19.0-50-generic as I cannot boot into 6.2.0-X-generic.

[Wade Cline (wtcline)]

Version 6.2.0-39-generic is able to boot, though with one caveat. I have three monitors: one belonging to the laptop, one connected to the laptop via HDMI, and another connected via HDMI to a D6000S docking station which is connecting to the laptop via USB-C. The latter two monitors display the splash/login screen to decrypt a drive while the laptop's native screen does not.

So I think the original issue has been solved and this particular bug can be closed out.