Kernel Panic because of DKMS

Support and Help
,
1

Hi :slight_smile:

It refers to:

As I understand it, users sometimes get Kernel Panics after updates, because some kernel modules are not updated in the same time, so they are incompatibles.

  1. Is there a procedure in Ubuntu Project to avoid this de-synchronization as often as possible?

  2. Would it be possible to improve the DKMS design so that when some kernel modules are incompatibles, instead of making a Kernel Panic, it just disable the incompatible modules and continue to boot?

3 Likes
2

Welcome to Ubuntu Discourse :slight_smile:

Moved to Support and Help.

Please note the Project Discussion category is not for technical support.

Thanks

1 Like
3

Thank you. :slight_smile:

As you like.

In my opinion, it was a matter of:

  1. Ubuntu policy for managing kernel updates
  2. kernel design

but not of technical support.
Do you disagree?

4

Tough call, really.

After review, the moderation team suggest you file a report on Launchpad in the form of a feature request against either DKMS or the kernel.

No guarantee the devs will take action on it but worth trying and definitely brings visibility.

Thanks for sharing with the community.

1 Like
5

Does this suggestion apply to both points?

Where can I find help for Launchpad, please? :slight_smile:
I am not familiar enough with the whole Ubuntu ecosystem.

I know, no matter. :slight_smile:

6

This link should have all the information you need:

Actually, for a feature request you might also want to try the ubuntu-devel-discuss mailing list.

Hope this helps :folded_hands:

7

55-initrd.install silently exits 0 when initrd missing causing undetectable kernel panic on NVMe systems is the bug that’s causing the issue of the kernel panics. This bug was filed in response to crashes on NVME systems, but the cause is the same for all systems (as I understand it):

  1. get kernel update
  2. dkms attempts to build out-of-tree module for new kernel
  3. dkms fails to build module for whatever reason
  4. initramfs-tools or dracut doesn’t build a new initrd
  5. grub still updates grub entry for new kernel pointing to non-existent initrd.
  6. Reboot and panic ensues.

the bug report goes into better detail. Supposedly this report was forwarded to kernel team, but apparently no solution has been presented on fixing the issue as I think this still happens on 26.04. I know it still happens on 24.04.

1 Like
8

A post was split to a new topic: Kernel panic in 7.0, works in 6.14