Bug#1057843: (no subject)

If it helps people, this is what I did on systems that automatically had rebooted into the problematic kernel. First, I uninstalled the 6.1.0-14 kernel and rebooted back into 6.1.0-13. Then I used `last` to identify the time between the problematic reboot into 6.1.0-14 and the deliberate

Bug#1057843: (no subject)

Would an fsck even be able to recognize corruption, if metadata were unaffected? Without file checksumming, can it discern?