Hi,
I add the same issue on AWS Xen powered instances. (t2, m4, c4, r4, ...).
Updating instances to newer family powered by Nitro (t3, m5, c5, r5, ...) fixed
the issue.
Envoyé de mon iPhone
Control: reassign -1 linux-image-amd64 4.9+80+deb9u12
Control: severity -1 critical
We have investigated this issue - analysis shows the following patch was
backported upstream to the 4.9 stable branch
(https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.235), and
subsequently to the Debian oldstable kernel
(https://tracker.debian.org/news/1187816/accepted-linu
Control: tags -1 + patch
Here is the upstream fix on lkml, CCing stable@
https://lore.kernel.org/lkml/20200930091614.13660-1-jgr...@suse.com/
Hi,
I can confirm this bug happening on Amazon Lightsail and EC2 instances
running Debian. After kernel upgrade the machines won't boot anymore and
end in kernel panic.
Here is a log from failed boot on EC2:
[0.16] [] ? rest_init+0x80/0x80
[0.16] [] ? kernel_init+0xa/0x100
[
Package: linux-image-4.9.0-14-amd64
Version: 4.9.240-1
After unattended-upgrade on Debian Stretch we noticed that all machines are not
booting with the new kernel. Sometimes after GRUB they just shut down sometimes
we get a kernel panic (it seems to be similar to
https://bugs.launchpad.net/ubun
6 matches
Mail list logo
