kernel panic after upgrade to 5.13.8
by vladimir1986 from LinuxQuestions.org on (#5N156)
Hey, I want to heads up about a bug, problem with certain config, or not sure what, but just make aware of a problem I found. I experienced this on a fresh, full install of Slackware 15 (-current).
First, about my system:
It is an EFI system. During install I selected ELILO, but I am currently using reFind, to make it easier to boot into other partitions (I share Slackware with Gentoo, Arch and FreeBSD on two different drives and partitions). Actually, just tested ELILO and doesn't even work (kicks me into the ELILO prompt), so I have to rely on reFind to boot Slackware.
I just did a slackpkg upgrade-all and got a new kernel version: 5.13.8. After upgrade, I' ll get a kernel panic, as it couldn't mount the root system (it won't load the ext4 module)
Tried to compile the new kernel manually, with ext4 into the kernel, instead of a module, and was able to boot. Noticed it complains about lilo not being installed (expected, but I notice only Slackware seems to do that)
I also tried the old kernel binary wile manually creating an initrd (with the -m ext4 flag), worked without warning, but kernel will panic again.
So not sure if it is that the standard slackpkg doesn't like not having conventional LILO configured (it is installed tho, as I have a full install), there is a problem with initrd (I usually just compile the kernel in other distros, but pass making an initrd image, so not an expert there.), but system was broken up to when I recompiled the kernel with ext4 on it, at least by doing the conventional upgrade way with slackpkg.
First, about my system:
It is an EFI system. During install I selected ELILO, but I am currently using reFind, to make it easier to boot into other partitions (I share Slackware with Gentoo, Arch and FreeBSD on two different drives and partitions). Actually, just tested ELILO and doesn't even work (kicks me into the ELILO prompt), so I have to rely on reFind to boot Slackware.
I just did a slackpkg upgrade-all and got a new kernel version: 5.13.8. After upgrade, I' ll get a kernel panic, as it couldn't mount the root system (it won't load the ext4 module)
Tried to compile the new kernel manually, with ext4 into the kernel, instead of a module, and was able to boot. Noticed it complains about lilo not being installed (expected, but I notice only Slackware seems to do that)
I also tried the old kernel binary wile manually creating an initrd (with the -m ext4 flag), worked without warning, but kernel will panic again.
So not sure if it is that the standard slackpkg doesn't like not having conventional LILO configured (it is installed tho, as I have a full install), there is a problem with initrd (I usually just compile the kernel in other distros, but pass making an initrd image, so not an expert there.), but system was broken up to when I recompiled the kernel with ext4 on it, at least by doing the conventional upgrade way with slackpkg.