Control: tag -1 + patch Quoting Johannes Schauer Marin Rodrigues (2025-04-13 23:28:32) > It seems that, if flash-kernel gets upgraded together with the kernel, then > flash-kernel is not run at the end of the installation and thus, the old > kernel stays referenced in /boot/boot.scr. Steps to reproduce: > > $ debvm-create -r unstable -- \ > http://snapshot.debian.org/archive/debian/20240401T000000Z/ \ > --aptopt='Acquire::Check-Valid-Until "false"' \ > --dpkgopt=force-confold \ > --include flash-kernel,u-boot-tools \ > --setup-hook='mkdir -p "$1"/etc/flash-kernel' \ > --setup-hook='printf "Machine: linux,dummy-virt\nKernel-Flavors: > any\nBoot-Script-Path: /boot/boot.scr\nU-Boot-Script-Name: > bootscr.uboot-generic\nRequired-Packages: u-boot-tools\n" > > "$1"/etc/flash-kernel/db' \ > --setup-hook='echo linux,dummy-virt > "$1"/etc/flash-kernel/machine' > [...] > $ debv-run > [...] > root@testvm:~# echo "deb > http://snapshot.debian.org/archive/debian/20250401T000000Z/ unstable main" >> > /etc/apt/sources.list && apt update && apt full-upgrade --yes > [...] > Setting up linux-image-6.12.21-cloud-arm64 (6.12.21-1) ... > I: /vmlinuz is now a symlink to boot/vmlinuz-6.12.21-cloud-arm64 > I: /initrd.img is now a symlink to boot/initrd.img-6.12.21-cloud-arm64 > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-6.12.21-cloud-arm64 > W: No zstd in /usr/bin:/sbin:/bin, using gzip > W: /sbin/fsck.ext4 doesn't exist, can't install to initramfs > flash-kernel: deferring update (trigger activated) > /etc/kernel/postinst.d/zz-flash-kernel: > flash-kernel: deferring update (trigger activated) > Setting up linux-image-cloud-arm64 (6.12.21-1) ... > Setting up flash-kernel (3.108) ... > debconf: unable to initialize frontend: Dialog > debconf: (No usable dialog-like program is installed, so the dialog based > frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line > 79.) > debconf: falling back to frontend: Readline > debconf: unable to initialize frontend: Readline > debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the > Term::ReadLine module) (@INC entries checked: /etc/perl > /usr/local/lib/aarch64-linux-gnu/perl/5.40.1 /usr/local/share/perl/5.40.1 > /usr/lib/aarch64-linux-gnu/perl5/5.40 /usr/share/perl5 > /usr/lib/aarch64-linux-gnu/perl-base /usr/lib/aarch64-linux-gnu/perl/5.40 > /usr/share/perl/5.40 /usr/local/lib/site_perl) at > /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 8.) > debconf: falling back to frontend: Teletype > Setting up dmsetup (2:1.02.205-1) ... > Setting up libdevmapper1.02.1:arm64 (2:1.02.205-1) ... > Setting up libcryptsetup12:arm64 (2:2.7.5-1) ... > Setting up systemd-cryptsetup (257.4-7) ... > Processing triggers for debianutils (5.21) ... > Processing triggers for libc-bin (2.41-6) ... > Processing triggers for systemd (257.4-7) ... > Processing triggers for initramfs-tools (0.147) ... > update-initramfs: /boot/initrd.img-6.12.21-cloud-arm64 has already been > updated since Sun Apr 13 21:19:34 2025. > root@testvm:~# grep -a 6.12.21 /boot/boot.scr > root@testvm:~# grep -a 6.7.9 /boot/boot.scr > setenv fk_kvers '6.7.9-cloud-arm64' > > So bottom line: if I upgrade flash-kernel together with the kernel, then > flash-kernel will not put the new kernel into /boot/boot.scr. This is of > course > fatal when at the same time that the new kernel got installed the new kernel > (the one still referenced by /boot/boot.scr) got removed. > > I hope having this easily reproducible will help you figure out what's going > on.
I patched flash-kernel with the changes from this MR: https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/41 I can confirm that this patch stack fixes the problem that I had and which can be demonstrated with above reproducer. Thus, I'm tagging this bug with "patch". Can we merge that MR now? :) Thanks! cheers, josch
signature.asc
Description: signature
