Security: microcode-20201118 / ucode-intel boot problem
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: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890 Nothing much happens with Intel: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/3... 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 process? Lastly, I went to https://build.opensuse.org/package/show/openSUSE:Factory/ucode-intel to 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 regression)? 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 Description : This package contains the microcode update blobs for Intel x86 and x86-64 CPUs. Many thanks for looking into this. Cheers Martin
Hi, On 02 Jan 17:40 2021, Martin wrote:
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: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890 Nothing much happens with Intel: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/3...
This is tracked at https://bugzilla.suse.com/show_bug.cgi?id=1179284 Regards, ismail -- You will become way less concerned with what other people think of you when you realize how seldom they do. — David Foster Wallace, Infinite Jest SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
İsmail Dönmez composed on 2021-01-02 18:15 (UTC+0100):
This is tracked at https://bugzilla.suse.com/show_bug.cgi?id=1179284
And for openSUSE users: https://bugzilla.opensuse.org/show_bug.cgi?id=1179284 -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
02.01.2021 19:40, Martin пишет:
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: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890 Nothing much happens with Intel: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/3...
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?
Open bug report.
On 02/01/2021 17.40, Martin wrote:
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 process?
opening a Bugzilla, but that has already been done, so you just add a comment to that one and thus you will keep informed. <https://en.opensuse.org/openSUSE:Submitting_bug_reports> -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Sat, 2 Jan 2021, Carlos E. R. wrote:
opening a Bugzilla, but that has already been done, so you just add a comment to that one and thus you will keep informed.
If you just need to follow the bug, then you can just go to the bug's page, leave the box checked to add your email address to the CC: list, and click save; no need to add a comment. -Mike
On 02/01/2021 19.09, Mike Gorse wrote:
On Sat, 2 Jan 2021, Carlos E. R. wrote:
opening a Bugzilla, but that has already been done, so you just add a comment to that one and thus you will keep informed.
If you just need to follow the bug, then you can just go to the bug's page, leave the box checked to add your email address to the CC: list, and click save; no need to add a comment.
Ah, good to know, thanks. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
İsmail Dönmez -
Martin -
Mike Gorse