According to Intel, this bug has been fixed in the microcode updates
released in the 20210608 package.
HOWEVER one must go from BIOS to the newest microcode update directly,
using kernel early updates. This is how it is supposed to happen by
default in Debian (and, AFAIK, Ubuntu nowadays) so it s
So, according to Intel, the probable cause for 0x406e3 and 0x506e3
processors to fail loading the microcode update *early* is an
incompatibility when you update from a very old microcode release in
BIOS/UEFI (BIOS has a revision older/smaller than 0x80) to the newer
microcode updates.
This informa
Hi, looks like this bug is back with the latest microcode update.
My ASUS PC only boot with dis_ucode_ldr kernel parameter.
4.4.0-194-generic #226-Ubuntu
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 78
model name : Intel(R) Core(TM) i7-6500U CPU @
This bug was fixed in the package intel-microcode -
3.20200609.0ubuntu0.20.04.2
---
intel-microcode (3.20200609.0ubuntu0.20.04.2) focal-security; urgency=medium
* REGRESSION UPDATE: revert the tmpfiles snippet to do late
loading of microcode, this would also happen during packag
This bug was fixed in the package intel-microcode -
3.20200609.0ubuntu0.16.04.1
---
intel-microcode (3.20200609.0ubuntu0.16.04.1) xenial-security; urgency=medium
* REGRESSION UPDATE: some CPUs in the Skylake family sig=0x406e3
fail to boot (LP: #1882890).
- revert 06-4e-03/0
This bug was fixed in the package intel-microcode -
3.20200609.0ubuntu0.19.10.2
---
intel-microcode (3.20200609.0ubuntu0.19.10.2) eoan-security; urgency=medium
* REGRESSION UPDATE: some CPUs in the Skylake family sig=0x406e3
fail to boot (LP: #1882890).
- revert 06-4e-03/0x0
This bug was fixed in the package intel-microcode -
3.20200609.0ubuntu0.18.04.1
---
intel-microcode (3.20200609.0ubuntu0.18.04.1) bionic-security; urgency=medium
* REGRESSION UPDATE: some CPUs in the Skylake family sig=0x406e3
fail to boot (LP: #1882890).
- revert 06-4e-03/0
This bug was fixed in the package intel-microcode -
3.20200609.0ubuntu0.20.04.1
---
intel-microcode (3.20200609.0ubuntu0.20.04.1) focal-security; urgency=medium
* REGRESSION UPDATE: some CPUs in the Skylake family sig=0x406e3
fail to boot (LP: #1882890).
- revert 06-4e-03/0x
** Also affects: intel-microcode (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: intel-microcode (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: intel-microcode (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: i
I grabbed the updated package from Steve's PPA (#19), installed it, made
sure intramfs were all properly updated (update-initramfs -u -k all) and
rebooted.
I confirm my laptop now boot properly (running Ubuntu 20.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Rodman: no, that's an older issue affecting a difference processor
family.
This issue is specifically affecting processors with id 0x406e3; if the
output of dmesg | grep microcode does not contain "sig=0x406e3" then you
have a different issue, and should open a new bug report.
I am working on rev
Philipp Classen: indeed, a full /boot/ will cause problems on upgrade
that can result in failure to boot, unrelated to microcode issues. With
that corrected, are you still having an issue?
And again, can you confirm that
dmesg | grep microcode
contains "sig=0x406e3"?
** Changed in: intel-micr
Looks like this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882890
Title:
intel-ucode/06-4e-03 from release 20200609 hangs system
Ok it worked.
1)
I went here: https://launchpad.net/ubuntu/+source/intel-microcode
to check what version of intel-microcode to downgrade to. Basically I wanted
the previous one that had no issues.
2)
I used an ubuntu-live-usb to chroot into my yoga 710-11ISK laptop (intel
m3-6Y30)
3)
$ sudo
Same problem with Ubuntu 20.04 on a ThinkPad X1 Carbon 4th.
"apt-get upgrade" froze at the installing the intel-ucode update. Then
it also refused to start. As a workaround, I followed similar steps
Paulo:
* Booting into recovery mode
* Step 1: dpkg --configure -a
* Step 2: apt --purge remove int
I have the exact problem and laptop as @Cole
I have chroot into the laptop using an ubuntu-live-usb to figure out
what the heck is going on.
The microcode that got installed is 3.20200609.0ubuntu0.20.04.0
I am uninstalling now.
I'll advise here if it worked.
--
You received this bug notificat
Same problem here on Ubuntu 20.04 in a Dell Latitude E7470 with a Core
i5-6300U. The machine hangs on boot. I can not even reboot the machine
using the alt-prtsc-b. It was completely frozen. Only a long press on
the power button would work. My workaround was to boot into recovery
mode (maybe you a
** Tags added: bionic eoan focal groovy xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882890
Title:
intel-ucode/06-4e-03 from release 20200609 hangs system in early boot
To manage notificat
@You-Sheng Thanks, I copied my `lscpu` output to the GitHub issue
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-
Files/issues/31#issuecomment-641907791
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
@You-Sheng Yang
"dmesg | microcode:"
[0.00] microcode: microcode updated early to revision 0xd6, date =
2019-10-03
[0.985877] microcode: sig=0x406e3, pf=0x80, revision=0xd6
[0.986019] microcode: Microcode Update Driver: v2.2.
--
You received this bug notification because you ar
@Jérôme, copying from comment on github[1]:
```
The differences between 0xd6 and 0xdc were quite minimal, to work around an
SGX issue.
Does disabling SGX in the BIOS work around the hang using 0xdc?
```
Is it possible to have a try and reply on github?
[1]: https://github.com/intel/Int
@Cole, although it's true that this should affects all series as intel-
microcode package is updated to all series. But, we will still need you
to comment the output of "dmesg | microcode:" to make sure you both are
victims of the same problematic blob.
--
You received this bug notification becau
I am having this issue on ubuntu 20.04. I have an Intel® Core™ m3-6Y30
Processor and I was on 5.4.0-33-generic kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882890
Title:
intel-ucode/06-4e-0
** Summary changed:
- 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
24 matches
Mail list logo
