Debian's 6.1.0-55 kernel freezes servers minutes after boot

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

A critical Debian bug report describes a server that stops responding to SSH, IMAP, SMTP, and HTTP within minutes of updating to linux-image 6.1.0-55. A VGA console shows an Oops, and the machine eventually locks up entirely. Booting the previous 6.1.0-54 kernel restores normal operation, and the reporter's dmesg output from an ASUS PRIME H410M-K with an Intel CPU is attached for diagnosis.

After updating to 6.1.0-55 package, and reboot my system, I found my server not responding remotely after few minutes (imap, smtp, http, ssh...).
  1. flowerthoughts

    (Happy I upgraded to trixie two weeks ago.)

    > From: Salvatore Bonaccorso <[email protected]>

    > I think this is this one:

    https://lore.kernel.org/linux-ext4/20261102-ext4-ntfs3-null-...

    https://salsa.debian.org/kernel-team/linux/-/merge_requests/...

    Seems people are happy with the proposed fix.

  2. walrus01

    When people say "this is a VM on xen" I really wish they would provide on essential piece of troubleshooting data. As a domU, is it PV, PVH, full HVM, or HVM with PV drivers? There's a huge difference for how a modern xen dom0 handles the bootloader and kernel boot for those.

    At this point trixie is also extremely mature and has been out for a long time, and while I'm not saying this isn't a major issue, if lots of people are seeing it, it's also a solid argument in favor of upgrading those bookworm systems to the latest bookworm and then to trixie to begin following the 13.x stable branch. The 6.12.x kernel in trixie fixes a lot of issues related to both being a hypervisor and running inside a hypervisor.

  3. anthk

    I always set two different kernels at boot because of this, an LTS one and the mainline version.

  4. mitchweaver

    Oof. This is bad.

    I couldn't understand which Debian ran this strange kernel version, until I realized all my oldstable boxes run a backport kernel.

    Phew.

    Because oldstable was... pretty freaking old even when it was new.

    Either that or Santa Altman came down the chimney during the night and swapped all their RAM sticks out for bad ones.

  5. okeuro49

    Weren't people criticising Ubuntu recently for putting the TCP bug kernel update through thorough testing?

More from this day

2026-11-16