I confirm this bug; same platform (AMD64), same kernel (6.11.7). > The last line I see says how many files and blocks are ok.
This is also what I see -- fsck status (both clean) for root and /usr filesystems (split on this system; current usrmerge package applied). After that, nothing happens. <CTRL><ALT><DEL> successfully resets the system, so the kernel is still awake, at least to some extent. Interestingly, after this boot hang with kernel v6.11.7, the exact same thing happens with kernel v6.11.5, although this previously worked fine before the v6.11.7 boot failure. Fortunately, I still have kernel v6.1.0-26 installed (Debian package, as are the others), and this boots without issue. The swap partition on this system is supposed to be encrypted, but none of the boot-time filesystems are, although there is an encrypted filesystem on another attached drive, not specified in /etc/fstab. This seems to be a serious problem, which has arisen between the linux-image-6.11.5-amd64 and linux-image-6.11.7-amd64 packages. The fact that v6.11.5 now fails, whereas it worked before the attempted v6.11.7 boot, is surely a significant fact. -- Ian Bruce
