Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

There are reports of issues following update to revision 0x2000065 of 06-55-04 microcode:

https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/21

Since, per [1], this revision is not required for recently unembargoed Intel CPU vulnerabilities and errata, it may be wise to disable update to it by default, the same way it has been done for SNB-EP (06-2d-07) microcode revision 0x718.

[1] https://www.intel.com/content/dam/www/public/us/en/documents/corporate-information/SA00270-microcode-update-guidance.pdf

Verified with microcode_ctl-1.17-33.23.el6_10.  The default microcode version is 0x2000064, but it gets upgraded to 0x2000065 with the "force" file in place.


[root@lenovo-sr650-01 ~]# lscpu | grep -i -e family -e model -e stepping
CPU family:            6
Model:                 85
Model name:            Intel(R) Xeon(R) Silver 4116 CPU @ 2.10GHz
Stepping:              4

[root@lenovo-sr650-01 ~]# rpm -q microcode_ctl
microcode_ctl-1.17-33.23.el6_10.x86_64

[root@lenovo-sr650-01 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version
0x2000064

[root@lenovo-sr650-01 ~]# install -D /dev/null /etc/microcode_ctl/ucode_with_caveats/force-intel-06-55-04

[root@lenovo-sr650-01 ~]# reboot
...

[root@lenovo-sr650-01 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version
0x2000065

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:4155