Sine last Monday (16 Nov) we have a similar freeze problem (at around 02:16, Tue and Wed, nothing at this time in the crontab).

One machine works fine (m3) one machine (m4) freezes.

The difference:

root@m3:/# ll
lrwxrwxrwx   1 root root   30 Nov 17 06:50 initrd.img -> boot/initrd.img-6.1.0-56-amd64 lrwxrwxrwx   1 root root   30 Nov 17 06:50 initrd.img.old -> boot/initrd.img-6.1.0-55-amd64 lrwxrwxrwx   1 root root   27 Nov 17 06:50 vmlinuz -> boot/vmlinuz-6.1.0-56-amd64 lrwxrwxrwx   1 root root   27 Nov 17 06:50 vmlinuz.old -> boot/vmlinuz-6.1.0-55-amd64

root@m3:/# uname -a
Linux m3 6.1.0-55-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.192-1 (2026-11-14) x86_64 GNU/Linux


root@m4:/# ll
lrwxrwxrwx   1 root root   30 Nov 17 06:23 initrd.img -> boot/initrd.img-6.1.0-56-amd64 lrwxrwxrwx   1 root root   30 Nov 17 06:23 initrd.img.old -> boot/initrd.img-6.1.0-55-amd64 lrwxrwxrwx   1 root root   27 Nov 17 06:23 vmlinuz -> boot/vmlinuz-6.1.0-56-amd64 lrwxrwxrwx   1 root root   27 Nov 17 06:23 vmlinuz.old -> boot/vmlinuz-6.1.0-55-amd64

root@m4:/# uname -a
Linux m4 6.1.0-56-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.192-2 (2026-11-16) x86_64 GNU/Linux


The one machine which works fine was NOT rebooted after the upgrade. The machine which freezes WAS rebooted. But this contradicts your bug report and the resolution... :-(

So I am scared now to reboot m3 as well..

If I can provide any more info please let me know (which one you need). It is acceptable for us for some more days to keep this state and not roll back the kernel...


Regards,
Oli

Reply via email to