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.

This bug has been copied from bug #1846023 and has been proposed to be backported to 7.2 z-stream (EUS).

Verified with microcode_ctl-2.1-12.30.el7_2.

Sandy Bridge EP microcode was updated by default (there was no need for a "force" file since it's no longer blacklisted).

The failed tasks are due to the blacklisted microcode for the CPU models due to the potential for a system freeze at boot.  The failure is because the system is not running the latest version of the microcode due to the blacklist, thus the failure is expected and it means the blacklist is working.

When the microcode update was forced, the 06-4e-03 system did hang on boot and I had to interrupt grub and add dis_ucode_ldr to get the system to boot and finish running the job.

The /sys/devices/system/cpu/vulnerabilities/srbds file reports "Mitigation: Microcode" on systems with affected CPUs and successful microcode updates.


https://beaker.engineering.redhat.com/jobs/4372582
https://beaker.engineering.redhat.com/jobs/4372582  (Skylake-SP re-run)

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/RHSA-2020:2679