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.
:::::::::::::::::::::
:: Host info ::
:::::::::::::::::::::
- Grab the host specific details:
~]# hostname
intel-sharkbay-dh-02.lab.bos.redhat.com
~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.0 (Maipo)
~]# uname -r
3.10.0-123.el7.x86_64
~]# lscpu | egrep 'family|Model|Stepping'
CPU family: 6
Model: 60
Model name: Intel(R) Core(TM) i5-4670T CPU @ 2.30GHz
Stepping: 3
- Update the microcode
~]# yum update microcode_ctl-2.1-10.el7.x86_64.rpm
- reboot
- Display the current version of the microcode, note the old version 0x17 is still displayed in the early messages
root@intel-sharkbay-dh-02 ~]# grep -i microcode /var/log/dmesg
[ 0.000000] CPU0 microcode updated early to revision 0x17, date = 2013-08-16
[ 0.352737] CPU1 microcode updated early to revision 0x17, date = 2013-08-16
[ 0.384789] CPU2 microcode updated early to revision 0x17, date = 2013-08-16
[ 0.407709] CPU3 microcode updated early to revision 0x17, date = 2013-08-16
[ 3.812369] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x17
[ 3.818975] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x17
[ 3.825588] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x17
[ 3.832197] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x17
[ 3.838832] microcode: Microcode Update Driver: v2.00 <tigran.co.uk>, Peter Oruba
[ 13.462398] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x17
[ 13.471026] microcode: CPU0 updated to revision 0x1c, date = 2014-07-03
[ 13.478677] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x17
[ 13.486354] microcode: CPU1 updated to revision 0x1c, date = 2014-07-03
[ 13.493874] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x17
[ 13.501483] microcode: CPU2 updated to revision 0x1c, date = 2014-07-03
[ 13.509028] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x17
[ 13.516601] microcode: CPU3 updated to revision 0x1c, date = 2014-07-03
Note the early update was to version 0x17, and the failsafe microcode systemd service updated it later in boot to 0x1C.
- Update the ram disk with the new microcode:
~]# dracut -v -f
- reboot
- Display the current version of the microcode, note the early update lines now display 0x1c
[root@intel-sharkbay-dh-02 ~]# dmesg | grep -i microcode
[ 0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.352755] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.384804] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.407725] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[ 3.804512] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x1c
[ 3.811118] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x1c
[ 3.817731] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x1c
[ 3.824341] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x1c
[ 3.830974] microcode: Microcode Update Driver: v2.00 <tigran.co.uk>, Peter Oruba
For more details, please reference the following bugs about the early-load feature:
kernel: https://bugzilla.redhat.com/show_bug.cgi?id=876850
dracut: https://bugzilla.redhat.com/show_bug.cgi?id=1045096
microcode_ctl: https://bugzilla.redhat.com/show_bug.cgi?id=1049650
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://rhn.redhat.com/errata/RHBA-2015-2385.html