Bug#967919: marked as done (kernel panic at boot)
Your message dated Sun, 27 Sep 2020 21:42:35 +0000
with message-id <E1kMeRH-0000Cc-HU@mx1.net9.ga>
and subject line Closing this bug. My mistake.
has caused the Debian Bug report #967919,
regarding kernel panic at boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
967919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967919
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.19.0-10-amd64
Version: 4.19.132-1
Severity: critical
Causes a kernel panic at boot. I have only managed to capture
The bottom lines of the panic message. A screen shot is at
https://imgur.com/a/ETtMtT2 .
Both linux-image-4.19.0-9-amd64 4.19.118-2+deb10u1 and
linux-image-4.19.0-8-amd64 4.19.98-1+deb10u1, as well as older
kernels seem to work fluessly.
--- End Message ---
--- Begin Message ---
Closing this bug. My mistake.
I had a similar problem with linux-image-4.19.0-11-amd64 (4.19.146-1).
Turned out I ignored update-initramfs warning
cp: cannot stat '/lib/klibc-*.so': No such file or directory
I must have deleted thst file. After reinstalling libklibc,
and updating initramfs, linux-image-4.19.0-11-amd64 is booting.
I assume that would be the case with linux-image-4.19.0-10-amd64 too.
I purged linux-image-4.19.0-10-amd64 in the meantime, which is why I can not
verify that. The initramfs for linux-image-4.19.0-9-amd64, and older kernels,
were probably created before the deletion of /lib/klibc-*.so.
Sorry for the noise.
u34.
--- End Message ---
Reply to: