Bugzilla – Bug 1219147
Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface
Last modified: 2024-01-24 16:17:36 UTC
Created attachment 872149 [details] Screen photos showing kernel oops and systemd output. Since the update to kernel 5.14.21-150500.55.44-default, I experience a spontaneous kernel bug during boot (for the first time on Monday 2024-Jan-22). This did not happen with kernel 5.14.21-150500.55.39-default or the kernels before. This bug appears in about 50% of all starts. This is the sequence of actions: * I power-on my Laptop (Lenovo 20QN-005YGE "P53", NVIDIA GPU) with USB-C docking station connected. * I get the Grub2 menu and let it start the default entry. * I get the usual green text screen to enter the password to decrypt the disk and enter the phrase (see img_1.jpg). * A moment later I see the green kernel oops message (attached as screen photo img_2.jpg). * When I press a key, I can see that systemd got to the point where it wanted to decrypt the disk but then hangs in a filesystem check (see img_4.jpg). * I power my Laptop off (waiting for 15 minutes has no effect). I "believe" the system fails to mount "/" and "/home". Consequently, I cannot find any entry of this oops or the boot at all in /var/log/messages, the journal or with "last". Workaround: * In the Grub2 menu, I choose the "Advanced" entry and boot kernel 5.14.21-150500.55.39-default. * In /etc/zypp/zypp.conf I changed one line multiversion.kernels = latest,latest-1,running to multiversion.kernels = latest,latest-1,running,5.14.21-150500.55.39 in order to prevent the "good" Kernel from beeing deleted.
A known regression, some info found in bsc#1218948 (although the original issue of that bug entry is different from your issue). The latest SLE15-SP5 git branch already contains the fix. Try the kernel in OBS Kernel:SLE15-SP5 repo http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/
Thanks for the fast response Takashi Iwai. I installed kernel 5.14.21-150500.228.g3903735-default and made five reboots with it. The bug did not appear and the machine started normal. You may set this bug to DUPLICATE or CLOSED or whaterver you think is appropriate.
Marking as duplicate *** This bug has been marked as a duplicate of bug 1218948 ***