Dear openSUSE community,
With the latest microcode-20201118 update, my Tumbleweed (on a Thinkpad T460) won't
boot anymore. I initially thought that it is kernel-related but it looks like a regression
was introduced after updating the intel-microcode from 20201110 to a version after that.
It is not openSUSE-related as I can confirm that the same problem occurs with other
operating systems (Ubuntu, Solus) too.
Ubuntu tracks it here:
Nothing much happens with Intel:
Adding the kernel parameter dis_ucode_ldr via Yast restores boot capability, however
leaves me without microcode protection.
After adding kernel parameter "dis_ucode_ldr":
dmesg | grep microcode
[ 0.028313] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
microcode to version: 0xb2 (or later)
[ 0.116757] SRBDS: Vulnerable: No microcode
[ 0.116758] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
What is the recommended way to proceed?
I looked via https://repology.org/project/intel-microcode/versions
to email the packager
but it looks like either Repology is configured in a way to not display any email
addresses of openSUSE packagers or openSUSE doesn't publish them during the packaging
Lastly, I went to https://build.opensuse.org/package/show/openSUSE:Factory/ucode-intel
check any current reported issues. Is this issue tracked elsewhere that I'm not aware
of? Is anyone familiar whether Ubuntu applies a patch to the microcode they ship or would
it rather make sense to rollback to 20201110 (I think this is the last one without the
Information for package ucode-intel:
Repository : openSUSE-Tumbleweed-Oss
Name : ucode-intel
Version : 20201118-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 3.5 MiB
Installed : Yes (automatically)
Status : up-to-date
Source package : ucode-intel-20201118-1.1.src
Summary : Microcode Updates for Intel x86/x86-64 CPUs
This package contains the microcode update blobs for Intel x86 and x86-64
Many thanks for looking into this.