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.

Bug 1774329

Summary: [RHEL 7] Do not update SKL-SP/W/X (CPUID 0x50654, 06-55-04) to revision 0x2000065 by default
Product: Red Hat Enterprise Linux 7 Reporter: Eugene Syromiatnikov <esyr>
Component: microcode_ctlAssignee: Eugene Syromiatnikov <esyr>
Status: CLOSED ERRATA QA Contact: Jeff Bastian <jbastian>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.8CC: efuller, jbastian, lmiksik, skozina
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: microcode_ctl-2.1-61.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1774322
: 1774635 (view as bug list) Environment:
Last Closed: 2020-03-31 20:08:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1774322    
Bug Blocks: 1774635    

Description Eugene Syromiatnikov 2019-11-20 03:10:40 UTC 
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
Comment 7 Jeff Bastian 2019-12-06 22:32:05 UTC 
Verified with microcode_ctl-2.1-61.el7

By default, the microcode is not updated to 0x2000065 due to the blacklist (it stays one revision behind which, as far as we know, is "safe" for all hardware):

[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-2.1-61.el7.x86_64

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



With the proper "force" file in place, though, the update works:

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

[root@lenovo-sr650-01 ~]# /usr/libexec/microcode_ctl/update_ucode

[root@lenovo-sr650-01 ~]# dracut --force

[root@lenovo-sr650-01 ~]# lsinitrd /boot/initramfs-3.10.0-1118.el7.x86_64.img | grep GenuineIntel.bin
-rw-r--r--   1 root     root        34816 Dec  6 17:22 kernel/x86/microcode/GenuineIntel.bin

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

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

[root@lenovo-sr650-01 ~]# journalctl -b0 -o short-monotonic | sed "s/$(hostname) //" | grep microcode
[    0.000000] kernel: microcode: microcode updated early to revision 0x2000065, date = 2019-09-05
[    6.111887] kernel: microcode: sig=0x50654, pf=0x1, revision=0x2000065
[    6.112190] kernel: microcode: Microcode Update Driver: v2.01 <tigran.co.uk>, Peter Oruba
[   12.666502] systemd[1]: Starting Load CPU microcode update...
[   12.761976] reload_microcode[1447]: find: ‘standard output’: Broken pipe
[   12.762594] reload_microcode[1447]: find: write error
[   12.793580] systemd[1]: Started Load CPU microcode update.



Note: the reload_microcode broken pipe errors appear to be a new bug, but that is unrelated to this bug.  I'll do some more investigation and open a new BZ if necessary.
Comment 9 errata-xmlrpc 2020-03-31 20:08:53 UTC 
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-2020:1166