Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

5.14.0-4 & 5.15.0-1 Kernels Failed to Boot

User discussion about Debian Development, Debian Project News and Announcements. Not for support questions.
Message
Author
pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

5.14.0-4 & 5.15.0-1 Kernels Failed to Boot

#1 Post by pwzhangzz »

Machines: Two laptops (Asus and Lenovo, both with Ryzen 4700u apu), one home-made desktop (Ryzen 3700 + Radeon RX580).

Installation iso: debian-live-11.0.0-amd64-gnome+nonfree.iso

Upgrade to the 5.14 kernel: Changed repo from bullseye to sid; sudo apt update && sudo apt upgrade, kernel upgraded from 5.10 to 5.14

Boot failure: all three machines failed to boot after upgrade to the 5.14 kernel

Boot back to 5.10 kernel: all three machines boot when back-grubbed to the 5.10 kernel

However, all three machines failed to boot (even to the 5.10 kernel) if I used sudo apt full-upgrade .
Last edited by pwzhangzz on 2021-11-25 08:52, edited 4 times in total.

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14 Kernel Failed to Boot

#2 Post by pwzhangzz »

I tried to upgrade the Linux kernel on a fourth machine, HP Envy 360, Ryzen 5 2500u, same problem. Had to back-grub to the 5.10 kernel.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: 5.14 Kernel Failed to Boot

#3 Post by sunrat »

Use the kernel that works then. :wink:
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14 Kernel Failed to Boot

#4 Post by pwzhangzz »

Just for the sake of providing a reference point (I have no desire of running Fedora), I just tried Fedora 35 beta with the 5.14 kernel (6.14.0-60.fc35.x86_64). No problem.

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2082
Joined: 2010-06-07 16:59
Has thanked: 38 times
Been thanked: 225 times

Re: 5.14 Kernel Failed to Boot

#5 Post by FreewheelinFrank »

5.14 is in Bookworm (Testing) and working. (I type from it now). It will no doubt make its way into Bullseye backports at some point, and that's the way I've used newer kernels in the stable release.

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14 Kernel Failed to Boot

#6 Post by pwzhangzz »

I think as I mentioned in a separate thread, the 5.14 kernel boot problem is related to the amdgpu firmware. But since I was able to boot with Fedora 35 beta (also the 5.14 kernel) on the same machines (all our machines use the amdgpu driver) I am sure it will be solved sooner or later in Debian.

cynwulf

Re: 5.14 Kernel Failed to Boot

#7 Post by cynwulf »

pwzhangzz wrote: 2021-09-27 19:16Installation iso: debian-live-11.0.0-amd64-gnome+nonfree.iso
[...]
Upgrade to the 5.14 kernel: Changed repo from bullseye to sid; sudo apt update && sudo apt upgrade, kernel upgraded from 5.10 to 5.14
Well no, in fact you have not simply upgraded to kernel 5.14, you have upgraded the whole system to the unstable distribution - and most likely only partially.

After issuing

Code: Select all

# apt-get update && apt-get upgrade
You would need to follow up with

Code: Select all

# apt-get dist-upgrade
As the first will usually not fully upgrade the system, when moving between releases.

Even then, as you have upgraded to unstable, which is called that for a reason, you could hit bugs, including regressions. Where apt pinning and apt-listbugs comes in and why many experienced unstable users also mix the testing repositories to allow pinning / downgrades until a particular problem is resolved...

If all that sounds like too much effort - then you simply need to stick to the stable release. If all you need is a newer kernel, then you could compile your own for the stable release, without resorting to upgrading to unstable.

Edited by moderator to correct code.

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

[Solved]Re: 5.14 Kernel Failed to Boot

#8 Post by pwzhangzz »

(This problem was "temporarily" solved by adding the kernel parameter "mem_encrypt=off")

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: [Solved]5.14 Kernel Failed to Boot

#9 Post by pwzhangzz »

The extra kernel parameter "mem_encrypt=off" is no longer necessary after upgrading to Debian 5.14.9-2 (2021-10-03). Thanks!

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: [Solved]5.14 Kernel Failed to Boot

#10 Post by stevepusser »

It's relatively trivial to backport the Sid 5.14.9-2 kernel to Bullseye (this means rebuilding from the Debian source packages on Bullseye, not just trying to install the Sid debs), and only a bit more trouble to backport it to Buster (mostly changing the references to having it build with gcc-10 to gcc-8).

There's a Yiddish word that probably describes a lot of problems we see on these forums:

farpotshket

broken, because someone tried to fix it

This word doesn't just describe something that is broken, but something that is broken specifically because someone else tried to fix it, making it worse. It is used most commonly today to describe software engineering projects.
MX Linux packager and developer

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: [Solved]5.14 Kernel Failed to Boot

#11 Post by ticojohn »

stevepusser wrote: 2021-10-06 19:18
There's a Yiddish word that probably describes a lot of problems we see on these forums:

farpotshket

broken, because someone tried to fix it
@stevepusser Great word, and you summed it up precisely. I'll have to remember to use it as the word of the day
I am not irrational, I'm just quantum probabilistic.

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14 Kernel Failed to Boot

#12 Post by pwzhangzz »

After an apt upgrade today, I am having problem booting from kernel 5.14.0-4-amd64 (kernel panic). The following is the error I encountered when doing an apt upgrade (I am booting back from the 5.14.0-3 kernel now, no harm):

/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.14.0-4-amd64:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.14.0-4-amd64
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.14.0-4-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.14.0-4-amd64 (--configure):
installed linux-image-5.14.0-4-amd64 package post-installation script subproces
s returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-5.14.0-4-amd64 (= 5.14.16-1); however:
Package linux-image-5.14.0-4-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured

dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up libpam-systemd:amd64 (249.6-2) ...
Setting up python3-ibus-1.0 (1.5.25-3) ...
Processing triggers for libgtk-4-1:amd64 (4.4.1+ds1-2) ...
Processing triggers for mailcap (3.70) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for libglib2.0-0:amd64 (2.70.1-1) ...
Processing triggers for libgtk-3-0:amd64 (3.24.30-3) ...
Processing triggers for libgtk2.0-0:amd64 (2.24.33-2) ...
Processing triggers for libc-bin (2.32-4) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.20-3) ...
Setting up ibus (1.5.25-3) ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.14.0-3-amd64
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.14.0-3-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
linux-image-5.14.0-4-amd64
linux-image-amd64
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
Last edited by pwzhangzz on 2021-11-14 17:14, edited 1 time in total.

User avatar
@ttila
Posts: 139
Joined: 2017-12-13 16:57
Has thanked: 2 times
Been thanked: 14 times

Re: [Solved]5.14 Kernel Failed to Boot

#13 Post by @ttila »

My system installs successfully the kernel 5.14.0-4, but doesn't compily the nvidia kernel module.

First it does't find the source path of the kernel, but this runs:

Code: Select all

dkms build -m nvidia-current -v 470.82.00 -k linux-headers-5.14.0-4-amd64 --kernelsourcedir /usr/src/linux-headers-5.14.0-4-amd64
It fails with:
DKMS make.log for nvidia-current-470.82.00 for kernel linux-headers-5.14.0-4-amd64 (x86_64)
dom 14 nov 2021, 16:21:53, CET
make V=1 -C /lib/modules/linux-headers-5.14.0-4-amd64/build M=/var/lib/dkms/nvidia-current/470.82.00/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/linux-headers-5.14.0-4-amd64/build NV_KERNEL_OUTPUT=/lib/modules/linux-headers-5.14.0-4-amd64/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm nvidia-peermem" INSTALL_MOD_DIR=kernel/drivers/video NV_SPECTRE_V2=0 modules
make[1]: *** /lib/modules/linux-headers-5.14.0-4-amd64/build: File o directory non esistente. Arresto.
make: *** [Makefile:80: modules] Errore 2
the built directory is there and is a link like the kernel 5.14.0-2.
Hope this could help.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: 5.14 Kernel Failed to Boot

#14 Post by sunrat »

@pwzhangzz are you still using mixed sources? Show us

Code: Select all

apt policy
@ttila wrote: 2021-11-14 15:32 My system installs successfully the kernel 5.14.0-4, but doesn't compily the nvidia kernel module.
There is no nvidia driver available in bullseye repos for kernel 5.14 yet. Maybe one day it will be backported but for now you need to use kernel 5.13 or lower. The default kernel 5.10.x should work fine and if so there is no reason to upgrade.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14 Kernel Failed to Boot

#15 Post by pwzhangzz »

sunrat wrote: 2021-11-14 20:44 @pwzhangzz are you still using mixed sources? Show us

Code: Select all

apt policy
ryzen@L32:~$ apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
release v=1.0,o=Google LLC,a=stable,n=stable,l=Google,c=main,b=amd64
origin dl.google.com
500 http://deb.debian.org/debian sid/non-free amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian sid/contrib amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian sid/main amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: 5.14 Kernel Failed to Boot

#16 Post by sunrat »

OK so you are running Sid now. Do

Code: Select all

apt update && apt full-upgrade
You really need to do full-upgrade in Sid rather than just upgrade as packages change so often.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14 Kernel Failed to Boot

#17 Post by pwzhangzz »

Yes, I did use apt full-upgrade. I think the problem is in generating the initrd.img file.

As shown below, there is no initrd.img-5.14.0-4-amd64; no wonder kernel panic when tried to boot from the vmlinuz-5.14.0-4-amd64 kernel:

ryzen@L32:~$ cd /boot
ryzen@L32:/boot$ ls
config-5.10.0-8-amd64 initrd.img-5.10.0-8-amd64 vmlinuz-5.10.0-8-amd64
config-5.14.0-3-amd64 initrd.img-5.14.0-3-amd64 vmlinuz-5.14.0-3-amd64
config-5.14.0-4-amd64 System.map-5.10.0-8-amd64 vmlinuz-5.14.0-4-amd64
efi System.map-5.14.0-3-amd64
grub System.map-5.14.0-4-amd64

User avatar
@ttila
Posts: 139
Joined: 2017-12-13 16:57
Has thanked: 2 times
Been thanked: 14 times

Re: 5.14 Kernel Failed to Boot

#18 Post by @ttila »

sunrat wrote: 2021-11-14 20:44 @pwzhangzz are you still using mixed sources? Show us

Code: Select all

apt policy
@ttila wrote: 2021-11-14 15:32 My system installs successfully the kernel 5.14.0-4, but doesn't compily the nvidia kernel module.
There is no nvidia driver available in bullseye repos for kernel 5.14 yet. Maybe one day it will be backported but for now you need to use kernel 5.13 or lower. The default kernel 5.10.x should work fine and if so there is no reason to upgrade.
Nvidia kernel drivers in testing compile correctly with the kernel 5.14.0-2 but not with the 5.14.0-4. I'll wait for a fix

pwzhangzz
Posts: 420
Joined: 2020-11-11 17:42
Has thanked: 9 times
Been thanked: 26 times

Re: 5.14.0-4 Kernel Failed to Boot

#19 Post by pwzhangzz »

When I tried to re-install the 5.14.0-4 kernel, I got the following error message:

E: Internal Error, No file name for linux-image-5.14.0-4-amd64:amd64

Looks like the 5.14.0-4 kernel was not properly installed (Debianese "unconfigured"), thus can't generate the initrd.img-5.14.0-4-amd64 file.
Last edited by pwzhangzz on 2021-11-20 17:44, edited 1 time in total.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: 5.14 Kernel Failed to Boot

#20 Post by stevepusser »

@ttila wrote: 2021-11-15 18:02
sunrat wrote: 2021-11-14 20:44 @pwzhangzz are you still using mixed sources? Show us

Code: Select all

apt policy
@ttila wrote: 2021-11-14 15:32 My system installs successfully the kernel 5.14.0-4, but doesn't compily the nvidia kernel module.
There is no nvidia driver available in bullseye repos for kernel 5.14 yet. Maybe one day it will be backported but for now you need to use kernel 5.13 or lower. The default kernel 5.10.x should work fine and if so there is no reason to upgrade.
Nvidia kernel drivers in testing compile correctly with the kernel 5.14.0-2 but not with the 5.14.0-4. I'll wait for a fix
We've two different users complaining about the latest 5.14 kernels, but they have to be clear about what dkms packages they are trying to build with those kernels. The one that most commonly gives dkms and boot failures is the nvidia-kernel-dkms build, which requires both the new kernel and its headers package.

I'm currently trying to backport kernel 5.15.1 from Debian Experimental, and anticipate lots of those kind of issues.
MX Linux packager and developer

Post Reply