News for hackers. Stuff that matters.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by RetroTechie on Monday November 16, 2026 @08:43AM (#50517526)
In that dmesg log

  [    2.920022] i915 0000:00:02.0: firmware: failed to load i915/kbl_dmc_ver1_04.bin (-2)

  ...

  [    3.818174] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
And a few more, just search for "fail". If NIC doesn't come up that explains why machine unreachable over ssh etc, right?

Might be a filesystem hiccup, and some firmware blobs went missing, or something? Just speculating here.

Might also be handy to save dmesg output from the kernel version that works fine, and lay output side-by-side.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by whisperenjoyer on Monday November 16, 2026 @08:57AM (#50517649)
I was able to reproduce the ext4 issue with qemu/kvm guest using debian cloud bookworm qcow2 image. You just need to run stress-ng --class filesystem for some time. Definitely not network problem and not xen-specific one. I think most of ext4 users (at least with common mount options) are affected.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by artooro on Monday November 16, 2026 @10:16AM (#50518482)
Yep, I was initially experiencing this problem with VMs on GCP. The busier the VM was handling user traffic, the sooner it triggered the bug.