Hi, On Tue, Mar 17, 2026 at 2:09 AM Paul Gevers <[email protected]> wrote: > > Hi Aron, > > On 3/16/26 10:47, Aron Xu wrote: > > The test passed after a manual retry. The initial failure was caused > > by a version mismatch: the testbed is running an older kernel than the > > headers being installed, which led to a modprobe failure. > > > I thought I at least peered at the logs and decided that I saw that the > testbed was restarted: > > 73s autopkgtest [20:08:59]: rebooting testbed after setup commands > that affected boot > 101s autopkgtest [20:09:27]: testbed running kernel: Linux > 6.19.6+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.19.6-1 (2026-03-06) > > Looks like the new kernel to me? >
Look at these lines in the log: 49s Setting up linux-image-6.19.6+deb14+1-amd64 (6.19.6-2) ... 57s I: /vmlinuz is now a symlink to boot/vmlinuz-6.19.6+deb14+1-amd64 57s I: /initrd.img is now a symlink to boot/initrd.img-6.19.6+deb14+1-amd64 57s /etc/kernel/postinst.d/dracut: 57s dracut: Generating /boot/initrd.img-6.19.6+deb14+1-amd64 65s dracut-install: WARNING: could not locate dlopen dependency for gcrypt feature requested by '/usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-260.so' 71s /etc/kernel/postinst.d/zz-update-grub: 71s Generating grub configuration file ... 71s Found linux image: /boot/vmlinuz-6.19.6+deb14-amd64 71s Found initrd image: /boot/initrd.img-6.19.6+deb14-amd64 71s Found linux image: /boot/vmlinuz-6.19.6+deb14+1-amd64 71s Found initrd image: /boot/initrd.img-6.19.6+deb14+1-amd64 The testbed contains two kernel versions: 6.19.6+deb14 (running) and 6.19.6+deb14+1 (pulled by newer linux-headers-amd64). Because only the headers for deb14+1 are present on the system, the ZFS kernel modules were built exclusively for that newer version. Later, when the test scripts try to execute modprobe, it fails because it looks for modules matching the currently running kernel (6.19.6+deb14), which do not exist. Regards, Aron
