[mrintegrity]

This was exceptionally annoying for me, some ec2 instances are used only during the day and we stop/start them with an in house scheduling application outside office hours. Also automatic security upgrades are enabled. Came in to work one day last week and all of our UAT environment was down.

It is possible to ssh in for about 2 seconds before the kernel panic so I solved it by doing this:

while true; do ssh <servername> sudo mv /usr/bin/containerd /usr/bin/containerd.backup ; sleep 1; done

On the next reboot i was able to ssh in and change to the (then just released within the past hour) kernel that doesn't have this stupid bug. After another reboot you can move containderd back and it should be working again

affected: linux-image-5.13.0-1028 not affected: >linux-image-5.13.0-1029

[kubanczyk]

I love the approach. Nowadays you can even

    sleep 0.1

on most systems. (And on Busybox, you should have usleep.)