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 1897684 - [rhel-7.9.z] Re-enable 06-5e-03 (SKL-H/S, CPUID 0x506e3) latest microcode updates
Summary: [rhel-7.9.z] Re-enable 06-5e-03 (SKL-H/S, CPUID 0x506e3) latest microcode upd...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: microcode_ctl
Version: 7.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Eugene Syromiatnikov
QA Contact: Jeff Bastian
Depends On: 1897673
Blocks: 1972332 1972333 1972334 1972335 1972336
TreeView+ depends on / blocked
Reported: 2020-11-13 18:36 UTC by Eugene Syromiatnikov
Modified: 2021-08-09 10:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1897673
: 1972332 1972333 1972334 1972335 1972336 (view as bug list)
Last Closed: 2021-08-09 10:09:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:3028 0 None None None 2021-08-09 10:10:01 UTC

Comment 2 Eugene Syromiatnikov 2021-06-10 19:07:05 UTC
microcode-20210608 comes with a new revision 0xea of 06-4e-03/06-5e-03, that seems to solve[1][2] the issue.

[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-857507126
[2] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/47#issuecomment-857815716

Comment 4 Eugene Syromiatnikov 2021-06-17 14:01:59 UTC
Revision 0xea still hasn't fixed the issue[1], at least for 06-4e-03.  It may be worth enabling 06-5e-03 only, as this is the CPUID that includes some server (Xeon E3 v5) models, contrary to 06-4e-03, that is mobile-only.

[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-861674762

Comment 5 Eugene Syromiatnikov 2021-07-22 15:08:00 UTC
06-4e-03 continues to have (possibly unrelated) issues[1]; on the other hand, there are no new reports for 06-5e-03, it can't be reproduced in-house, and enabling microcode-provided protections is more pertinent for it, thus, the bug is re-scoped to include 06-5e-03 only.

[1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-861674762

Comment 13 errata-xmlrpc 2021-08-09 10:09:55 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 (Important: microcode_ctl security, bug fix and enhancement update), and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.