Kernel panic after automatic upgrade from 6.14 to 6.17

I have a kernel panic on boot after automatic upgrade from 6.14 to 6.17
Simple workaround: boot in grup from previous kernel.

But I am affraid that the next update will discart the working 6.14

how can i

  • fix the 6.17 issue
  • prevent the working 6.14 from being deleted ?

thx !

1 Like

Probably need more information, e.g. do you see any signs of errors in the journal? (you can look at the previous boot's log via journalctl -b -1)

2 Likes

Are you booting into the 6.14 kernel or using a different machine to post here?

If booting into the 6.14 kernel with safe mode, then shut off any auto upgrades for now, until you get help.

2 Likes

The previous bootlog is from the previous working boot (also 6.14)

2 Likes

ok, done !

thx for the help so far !

1 Like

You may wish to look at this thread on the Ubuntu Discourse:

3 Likes

You can look at older boots by changing the number, e.g. -b -2 for the boot before last.

1 Like

I tried… all boots I get are 6.14

2 Likes

Well, at least you can keep 6.14 installed via sudo apt install linux-generic-6.14.

When does the kernel panic occur? You said "on boot" but that's quite vague ... How do you know its a kernel panic if there aren't any kernel panics in the logs?

1 Like

when switching the computer on (or after resetting it) I get my grub screen. when I choose 6.17 (or choose nothing since 6.17 is the default value) I get immediately a pink screen containing the tekst Kernal Panic.

2 Likes

I found this online:

https://medium.com/@imadsaddik/how-to-fix-the-kernel-panic-after-installing-a-new-version-of-the-kernel-a02b63bb3bb7

I will test it tomorow

2 Likes

I suspect something went wrong when you installed 6.17. Maybe try installing linux-generic-6.14, booting off of that, then purge the HWE (or however else you have installed 6.17) and install it again in the terminal, and look for any issues in the output?

You can also look in /var/log/apt/term.log

I actually just noticed some errors myself with the NVIDIA DKMS :confused: Yet everything is running OK. Can't wait to see what is broken!

1 Like

I tried sudo apt install linux-generic-6.14
after setting up 6.14 apt starts also setting up 6.17.
There i see that this conflicts in some way with virtual-box (not running)

sudo apt install linux-generic-6.14
[sudo] password for eldendo:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libwayland-server0:i386
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
linux-headers-generic-6.14 linux-image-generic-6.14
The following NEW packages will be installed:
linux-generic-6.14 linux-headers-generic-6.14 linux-image-generic-6.14
0 upgraded, 3 newly installed, 0 to remove and 9 not upgraded.
4 not fully installed or removed.
Need to get 6.554 B of archives.
After this operation, 27,6 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://mirror.unix-solutions.be/ubuntu noble-updates/main amd64 linux-image-generic-6.14 amd64 6.14.0-37.37~24.04.1 [2.486 B]
Get:2 https://mirror.unix-solutions.be/ubuntu noble-updates/main amd64 linux-headers-generic-6.14 amd64 6.14.0-37.37~24.04.1 [2.316 B]
Get:3 https://mirror.unix-solutions.be/ubuntu noble-updates/main amd64 linux-generic-6.14 amd64 6.14.0-37.37~24.04.1 [1.752 B]
Fetched 6.554 B in 0s (29,2 kB/s)
Selecting previously unselected package linux-image-generic-6.14.
(Reading database ... 413957 files and directories currently installed.)
Preparing to unpack .../linux-image-generic-6.14_6.14.0-37.37~24.04.1_amd64.deb
...
Unpacking linux-image-generic-6.14 (6.14.0-37.37~24.04.1) ...
Selecting previously unselected package linux-headers-generic-6.14.
Preparing to unpack .../linux-headers-generic-6.14_6.14.0-37.37~24.04.1_amd64.de
b ...
Unpacking linux-headers-generic-6.14 (6.14.0-37.37~24.04.1) ...
Selecting previously unselected package linux-generic-6.14.
Preparing to unpack .../linux-generic-6.14_6.14.0-37.37~24.04.1_amd64.deb ...
Unpacking linux-generic-6.14 (6.14.0-37.37~24.04.1) ...
Setting up linux-headers-generic-6.14 (6.14.0-37.37~24.04.1) ...
Setting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
Setting up linux-image-generic-6.14 (6.14.0-37.37~24.04.1) ...
Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:

  • dkms: running auto installation service for kernel 6.17.0-14-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build
M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms
.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 6.17.0-14-generic
    ...fail!
    run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-headers-6.17.0-14-generic (--configure):
    installed linux-headers-6.17.0-14-generic package post-installation script subp
    rocess returned error exit status 11
    Setting up linux-generic-6.14 (6.14.0-37.37~24.04.1) ...
    dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.
    04:
    linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; how
    ever:
    Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup erro
r from a previous failure.
dpkg: dependency problems prevent configuration of lin
ux-generic-hwe-24.04:
linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14
.14~24.04.1); however:
Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup erro
r from a previous failure.
Processing triggers for linux-image-6.17.0-14-generic
(6.17.0-14.14~24.04.1) ...
/etc/kernel/postinst.d/dkms:

  • dkms: running auto installation service for kernel 6.17.0-14-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build
M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms
.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 6.17.0-14-generic
    ...fail!
    run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-image-6.17.0-14-generic (--configure):
    installed linux-image-6.17.0-14-generic package post-installation script subpro
    cess returned error exit status 11
    No apport report written because MaxReports is reached already
    Errors were encoun
    tered while processing:
    linux-headers-6.17.0-14-generic
    linux-headers-generic-hwe-24.04
    linux-generic-hwe-24.04
    linux-image-6.17.0-14-generic
    E: Sub-process /usr/bin/dpkg returned an error code (1)
1 Like

Using this I deleted the 6.17 and it seems not to try to reinstallate itself.

4 Likes

Yep, remove 6.17 via sudo apt purge linux-generic-hwe-24.04 and sudo apt autoremove --purge. Then install sudo apt install linux-generic-6.14.

I have to do the same thing because NVIDIA's 550 driver does not build on 6.17. I tried patching it but there's a deeper problem with GPL license constraints that I wont have the time to understand and fix.

3 Likes