On Mon, 7 Apr 2025 08:28:01 +0300 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> wrote: > On Sun, 6 Apr 2025 19:36:03 +0300 > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> > wrote: > > On Sun, 6 Apr 2025 13:02:29 +0300 > > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> > > wrote: > > > On Sun, 6 Apr 2025 10:00:45 +0300 > > > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> > > > wrote: > > > > On Sat, 05 Apr 2025 22:56:46 +0300 =?utf-8?q?Martin-=C3=89ric_Racine?= > > > > <martin-eric.rac...@iki.fi> wrote: > > > > > Package: upgrade-reports > > > > > Severity: important > > > > > X-Debbugs-Cc: martin-eric.rac...@iki.fi > > > > > > > > > > After upgrading an amd64 host from Bookworm to Trixie (2025-04-05 > > > > > EEST), on reboot, the host gets a kernel panic with: > > > > > > > > > > initramfs unpacking failed invalid magic at start of compressed > > > > > archive > > > > > > > > I just checked whether I can rescue the host using the Trixie mini.iso > > > > on a USB stick: > > > > > > > > Debian GNU/Linux 13 (trixie) amd64 - netboot mini.iso 20241227 > > > > > > > > I get the same kernel panic as soon as GRUB loads the kernel. > > > > > > > > If I try with the Bookworm mini.iso, the kernel boots just fine and > > > > gets me to the rescue menu. > > > > > > > > Debian GNU/Linux 12 (bookworm) amd64 - netboot mini.iso 20230607+deb12u9 > > > > > > > > However, using the Bookworm rescue mode is a PITA, because it doesn't > > > > know how to mount brtfs sub-volumes (not even with Debian's default > > > > @rootfs) so even just chroot'ing myself in using the above recipe > > > > requires a LOT of command typing inside the rescue mode's shell. > > > > > > As a further test, I've tried booting the following Trixie USB stick > > > in BIOS mode via the rescue menu: > > > > > > Debian GNU/Linux trixie-DI-alpha1 "Trixie" - Official Alpha amd64 > > > NETINST with firmware 20241230-11:26 > > > > > > This succesfully gets me to the rescue process and allows me to chroot > > > into the host after typing the long commandline series above. > > > > > > Basically, a/b testing shows that Trixie kernels per-se work fine, but > > > something fishy is going on with the grub-efi-amd64 in Trixie. The > > > same host was originally installed with a Bookworm mini.iso on USB and > > > booted fine via EFI, so the problem really does seem to be the > > > grub-efi-amd64 in Trixie. > > > > Given the above, reassigned to bin:grub-efi-amd64. > > And, after checking, bumping severity to Critical, since this bug > prevents common hardware (ASUS P8H61 motherboard via UEFI) from > booting.
Is there any way I can help the maintainers pinpoint the source of the problem? Martin-Éric
