pe 2.5.2025 klo 19.44 Chris Hofstaedtler (z...@debian.org) kirjoitti: > > On Sun, Apr 13, 2025 at 10:23:17AM +0300, Martin-Éric Racine wrote: > > Is there any way I can help the maintainers pinpoint the source of the > > problem? > > This bug needs two things: > > 1) A full reproducer step list, starting from "I have nothing but an empty > amd64 VM".
There isn't much to reproduce: 1) Start with a fully functional host running Bookworm with GRUB-EFI on a brtfs filesystem created using d-i/Bookworm's default @rootfs subvolume name. 2) Change APT sources from Bookworm to Trixie. 3) Dist-upgrade. 4) Reboot. 5) Find the above kernel panic. 6) Using Bookworm d-i's rescue mode via EFI, APT pin and downgrade grub* to Bookworm. All other packages remain at Trixie versions. 7) Reboot. 8) The host boots normally. Validation: 1) Try using Trixie d-i's rescue mode via EFI. Same error as above. 2) Try using Trixie d-i's rescue mode via BIOS. Boots fine, but obviously is useless as far as performing maintenance on an EFI host. > 2) A bisect of GRUB between 2.06 and 2.12. Too big of a delta. If someone had made regular uploads since 2.06, I could quickly go through what's in snapshot.d.o and report at which version it failed. While there's a stream of 2.12-RC releases there, it's still a jump from 2.06 to 2.12, and there's good chances are that the commit we're looking for happened between those 2 releases. As amazing as it might sound to some people, some of us have a life outside of FLOSS, and spending days bisecting and building incremental versions of the same package over code spanning a good 2 years is not on the agenda. Anyhow, from my perspective, someone ought to interpret my bug report as something better acted upon now before other users report the same issue once Trixie is out the door. Besides, the signs were already there at Ubuntu derivatives for a while, and could have been acted upon there much earlier, since the maintainers are the same. Martin-Éric
