Linux-headers-6.17.0-14-generic kernel panic

Support and Help
1

Ubuntu unity 24.04

Hi.

I thought I had this under control via an earlier post, but it appears that I am still in ‘trouble’.

A recent OS update brought in Kernel 6.17 to replace 6.14. A subsequent boot led to a Kernel Panic. A restore got me back to kernel 6.14. Then I did this:

sudo apt-get purge linux-image-6.17.0-14-generic

sudo apt-get purge linux-headers-6.17.0-14-generic

sudo apt-get purge linux-image-generic-hwe-24.04

After some reading on this forum, I was informed that purging 6.17 Kernel header files would prevent future updates of Kernel 6.17 to be installed on my system, so I tried to re-instate the 6.1.7 Kernel header files:

apt list ~i~nheaders |cut -d/ -f1

and this was displayed:

linux-hwe-6.17-headers-6.17.0-14

I thought I had resolved the problem, but unfortunately I am still getting issues with Kernel 6.17 header files. For example, I tried installing wine and I got:

dpkg:error processing package linux-headers-6.17.0-14-generic (--configure):
installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned err
or exit status 11
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; however:
Package linux-headers-6.17.0-14-generic is not configured yet.

Seems strange to me as I am booting with Kernel 6.14.

So then I tried this

sudo apt --fix-broken install

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
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
Binary update-secureboot-policy not found, modules won't be signed

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.17.0-14-generic KVER=6.17.0-14-generic...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/broadcom-sta-dkms.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
Sign command: /usr/bin/kmodsign
Binary update-secureboot-policy not found, modules won't be signed

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/vi
rtualbox/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 broadcom-sta(10) 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 subprocess returned err
or exit status 11
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; however:
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 error from a previous f
ailure.
Errors were encountered while processing:
linux-headers-6.17.0-14-generic
linux-headers-generic-hwe-24.04
E: Sub-process /usr/bin/dpkg returned an error code (1)

An ancient error with broadcom appeared - something I thought I fixed by by adding ‘noble-backports’ to ‘Other Software’ in OS Updates. Now I’m also seeing issues with Virtual Machine.

Will these problems be resolved when a revised version of Kernel 6.17 comes around ? If so I have no problem waiting as my system appears to be working just fine. Or do I have to do something to get the 6.17 headers fixed ?

Thanks for listening,

M…

2

This has nothing to do with the headers. It doesn’t have anything directly to do the 6.17 kernel. This problem is a failure of QA to make sure the virtualbox-dkms (and broadcom-sta-dkms) package successfully build its kernel module to work with the 6.17 kernel in noble. It’s that package that needs to be updated if it can be.

Purge virtualbox and broadcom driver, fix broken packages or reinstall linux-generic-hwe-24.04

If you need virtualbox, get it from the virtualbox.org website. Only do this after you get the 6.17 kernel package installation sorted out, i.e no errors.

$ sudo apt autopurge virtualbox broadcom-sta-dkms

$ sudo apt install --fix-broken
or, since I am not completely sure what you have and haven't installed/removed 
$ sudo apt install --reinstall linux-generic-hwe-24.04

now install updated broadcom-sta-dkms package 
$ wget http://archive.ubuntu.com/ubuntu/pool/restricted/b/broadcom-sta/broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb
$ sudo apt install ./broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb

I believe this has been covered in other threads on this topic, though

3 Likes
3

Hi.

Okay I tried this (I didn’t do Virtual Box at this time):

sudo apt autopurge broadcom-sta-dkms

sudo apt install --reinstall linux-generic-hwe-24.04

I got a slew of these errors:

“Something wicked happened resolving …..”

Kernel Panic and Something wicked - yikes.

E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/llvm-toolchain-18/libllvm18_18.1.3-
1ubuntu1_amd64.deb Something wicked happened resolving ‘archive.ubuntu.com:http’ (-5 - No address
associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/llvm-toolchain-18/libclang-cpp18_18
.1.3-1ubuntu1_amd64.deb Something wicked happened resolving ‘archive.ubuntu.com:http’ (-5 - No add
ress associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/b/bpfcc/libbpfcc_0.29.1%2Bds-1ubuntu7
_amd64.deb Something wicked happened resolving ‘cz.archive.ubuntu.com:http’ (-5 - No address assoc
iated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/b/bpfcc/python3-bpfcc_0.29.1%2Bds-1ub
untu7_all.deb Something wicked happened resolving ‘cz.archive.ubuntu.com:http’ (-5 - No address as
sociated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/i/ieee-data/ieee-data_20220827.1_all.
deb Something wicked happened resolving ‘cz.archive.ubuntu.com:http’ (-5 - No address associated w
ith hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/python-netaddr/python3-netaddr_0.8.
0-2ubuntu1_all.deb Something wicked happened resolving ‘cz.archive.ubuntu.com:http’ (-5 - No addre
ss associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/b/bpfcc/bpfcc-tools_0.29.1%2Bds-1ubun
tu7_all.deb Something wicked happened resolving ‘cz.archive.ubuntu.com:http’ (-5 - No address asso
ciated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/llvm-toolchain-18/libclang1-18_18.1
.3-1ubuntu1_amd64.deb Something wicked happened resolving ‘archive.ubuntu.com:http’ (-5 - No addre
ss associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/b/bpftrace/bpftrace_0.20.2-1ubuntu4.3
_amd64.deb Something wicked happened resolving ‘archive.ubuntu.com:http’ (-5 - No address associat
ed with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/i/iucode-tool/iucode-tool_2.3.1-3buil
d1_amd64.deb Something wicked happened resolving ‘cz.archive.ubuntu.com:http’ (-5 - No address ass
ociated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-6.17/linux-modules-6.17.0
-14-generic_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.ubuntu.
com:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-signed-hwe-6.17/linux-image-6
.17.0-14-generic_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.ub
untu.com:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-6.17/linux-modules-extra-
6.17.0-14-generic_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.u
buntu.com:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.2
0250812.0ubuntu0.24.04.1_amd64.deb Something wicked happened resolving ‘security.ubuntu.com:http’
(-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/a/amd64-microcode/amd64-microcode_3.2
0250311.1ubuntu0.24.04.1_amd64.deb Something wicked happened resolving ‘security.ubuntu.com:http’
(-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-meta-hwe-6.17/linux-image-gen
eric-hwe-24.04_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.ubun
tu.com:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-meta-hwe-6.17/linux-generic-h
we-24.04_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.ubuntu.com
:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-6.17/linux-hwe-6.17-tools
-6.17.0-14_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.ubuntu.c
om:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-6.17/linux-tools-6.17.0-1
4-generic_6.17.0-14.14%7e24.04.1_amd64.deb Something wicked happened resolving ‘security.ubuntu.co
m:http’ (-5 - No address associated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/t/thermald/thermald_2.5.6-2ubuntu0.24
.04.3_amd64.deb Something wicked happened resolving ‘archive.ubuntu.com:http’ (-5 - No address ass
ociated with hostname)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/u/ubuntu-meta/ubuntu-kernel-accessori
es_1.539.2_amd64.deb Something wicked happened resolving ‘archive.ubuntu.com:http’ (-5 - No addres
s associated with hostname)
E: Unable to fetch some archives, try running apt-get update or apt-get --fix-missing.

I don’t know if I’ve done any damage, so I will Restore the OS.

Should I just wait for a revised version of 6.17? Will it install in spite of what appears to be a problem with linux-generic-hwe-24.04 ?

Thanks,

M….

4

Hmm… The broadcom wl module should have remained inserted and providing wifi networking even after purging the broadcom-sta-dkms package, so I am at a loss as to why you don’t have network connectivity to install the header packages, related dependencies and the updated broadcom-sta-dkms.

I am afraid that won’t help. You’ll have to find an alternate way to get network connectivity to that machine since without the headers you won’t be able to build a broadcom kernel module with the dkms package.

5

Hi.

What makes you think I don’t have network connectivity ? How else could I respond to these posts ?

Anyhow, I do have network connectivity. Everything is working just fine, but it would be nice to be able to upgrade to Kernel 6.17 without ‘Panics’ and ‘Wicked Errors’.

So, should I just wait for a revised version of 6.17?

Thanks,

M….

6

Because you posted a whole slew of apt error messages that demonstrating that it couldn’t fetch a number packages it need to install because it couldn’t resolve server addresses which is indicative of network loss at some level that affects dns not working.

Nothing will get resolved until you install the updated broadcom-sta-dkms package, the linux-headers packages and dependencies for 6.17 and fixing the broken state of the 6.17 kernel image package.

Though if you have network connectivity even after purging the broadcom-sta-dkms package, then why do you need it at all?

7

Hi

Are you saying I should purge the broadcom-sta-dkms package and that would solve my problem and allow future 6.17 Kernels to be installed ?

Note that I am running kernel 6.14.

I’m not sure how to proceed from here.

Thanks for your patience,

M….

8

According to what you posted before, you already purged it:

At this point I’m going to bow out from offering any more technical assistance as I’m thoroughly confused as to the state of your system. I think any more of my attempts to remedy the broken state of the 6.17 kernel package on your system is highly likely to be ineffectual.

I’m sorry that I couldn’t help. Hopefully, someone else more knowledgeable reading this topic can step in to provide assistance to you.

9

Hi and I fully understand. I wouldn’t have hung in this long :grinning_face_with_smiling_eyes: .

I gave the instructions another try:

$ sudo apt autopurge virtualbox broadcom-sta-dkms

$ sudo apt install --fix-broken

$ sudo apt install --reinstall linux-generic-hwe-24.04

$ wget http://archive.ubuntu.com/ubuntu/pool/restricted/b/broadcom-sta/broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb
$ sudo apt install ./broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb

And all went well.

I booted again and I got
….unexpected inconsistency for fsck. File system check of the root filesystem failed.

In busybox I did an fsck /dev/sda2 and it found problems. When it was done I did an exit and 6.17 came up. This made no sense to me - why the fsck problems all of a sudden?

And, my system was not right. Thunderbird calendar was hung, libreoffice menu was an old version, surshark complained about some java script error, and my Data partition was suddenly Read Only. And there were other issues.

I tried booting again, and this led me another round of fsck and ‘file system check of the
root filesystem failed.’

At this point I restored and I did this:

$ sudo apt autopurge virtualbox broadcom-sta-dkms

$ sudo apt install --fix-broken

$ wget http://archive.ubuntu.com/ubuntu/pool/restricted/b/broadcom-sta/broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb
$ sudo apt install ./broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb

leaving out the all important

sudo apt install --reinstall linux-generic-hwe-24.04

I gather the broadcom issue is resolved and I will re-install Virtual Box.

So here I am at Kernel 6.14. Am I cooked, or will a future kernel 6.17 update get me out of my mess ?

Thanks and If you don’t answer I understand.

M….