intel-ucode/06-4e-03 from release 20200609 hangs system in early boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
intel-microcode (Ubuntu) |
Fix Released
|
Critical
|
Steve Beattie | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
This morning I applied the latest updates on my Ubuntu 16.04 (kernel 4.15.0-106-generic + intel-microcode 3.20200609.
I tried booting the previous kernel 4.15.0-101 and it seems to be the same : in grub I select the 4.15.0-101 kernel, press enter, a message "Loading initrd..." is printed but nothing else happens.
Tried even older kenrel 4.4.0-184-generic : same problem, "Loading initrd...", and nothing happens.
I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-functionnal.
I mounted the /boot partition from a USB rescue drive, and it seems that all the initrd images that got updated this morning are not bootable anymore :
- initrd.
- initrd.
- initrd.
I tried regenerating the images with update-initramfs but it's the same : "Loading initrd" message but nothing happens.
Changed in intel-microcode (Ubuntu): | |
status: | New → Confirmed |
no longer affects: | linux (Ubuntu) |
summary: |
- Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04 + intel-ucode/06-4e-03 from release 20200609 hangs system in early boot |
tags: | added: bionic eoan focal groovy xenial |
Changed in intel-microcode (Ubuntu Bionic): | |
status: | New → Confirmed |
Changed in intel-microcode (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in intel-microcode (Ubuntu Eoan): | |
status: | New → Confirmed |
Changed in intel-microcode (Ubuntu Focal): | |
status: | New → Confirmed |
Hi, since you mentioned you also upgraded intel-microcode, does it help if you regenerate initramfs after purging intel-microcode?
In addition, could you also paste your microcode info when booted with USB rescue drive?
$ dmesg |grep microcode: