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 1580584 - Enable early microcode update for AMD linux-firmware
Summary: Enable early microcode update for AMD linux-firmware
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: linux-firmware
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bruno Meneguele
QA Contact: Rachel Sibley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-21 20:41 UTC by Rachel Sibley
Modified: 2019-02-19 23:38 UTC (History)
2 users (show)

Fixed In Version: linux-firmware-20180518-64.git2a9b2cf.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:11:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3119 0 None None None 2018-10-30 10:13:03 UTC

Description Rachel Sibley 2018-05-21 20:41:44 UTC 
Description of problem:

For AMD updates, the microcode isn't updated early as it is for Intel systems when updating
the microcode_ctl rpm. Can we please add a %posttrans script for linux-firmware to force an
update using 'dracut -f' to rebuild the initramfs.img

Version-Release number of selected component (if applicable):
linux-firmware-20180518-63.git2a9b2cf.el7.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1. Find an AMD system that requires an update
2. Provision with RHEL7
3. yum update linux-firmware and reboot
4. Note the logs do not indicate an early microcode update

Actual results:
 no indication that microcode was updated early in the logs

Expected results:
 microcode updated early to new patch_level ... is seen in the logs

Additional info:
From jbastian:
"The linux-firmware %posttrans script may want to be a bit more selective
i.e., check if the system has an AMD CPU, something like

if [ -d /run/systemd/system ]; then
  if grep -q AuthenticAMD /proc/cpuinfo ; then
    dracut -f
  fi
fi"

~]# cat /sys/devices/system/cpu/cpu0/microcode/version
0x600084f

~]# yum update linux-firmware-20180518-63.git2a9b2cf.el7.noarch.rpm
...

~]# reboot
...

~]# grep -i microcode /var/log/dmesg
[    3.671328] microcode: CPU0: patch_level=0x0600084f
[    3.676233] microcode: CPU1: patch_level=0x0600084f
[    3.681276] microcode: CPU2: patch_level=0x0600084f
[    3.686207] microcode: CPU3: patch_level=0x0600084f
[    3.691250] microcode: CPU4: patch_level=0x0600084f
[    3.696187] microcode: CPU5: patch_level=0x0600084f
[    3.701050] microcode: CPU6: patch_level=0x0600084f
[    3.705918] microcode: CPU7: patch_level=0x0600084f
[    3.710790] microcode: CPU8: patch_level=0x0600084f
[    3.715656] microcode: CPU9: patch_level=0x0600084f
[    3.720668] microcode: CPU10: patch_level=0x0600084f
[    3.725622] microcode: CPU11: patch_level=0x0600084f
[    3.730752] microcode: CPU12: patch_level=0x0600084f
[    3.735770] microcode: CPU13: patch_level=0x0600084f
[    3.740898] microcode: CPU14: patch_level=0x0600084f
[    3.745918] microcode: CPU15: patch_level=0x0600084f
[    3.751154] microcode: Microcode Update Driver: v2.01 <tigran.co.uk>, Peter Oruba
[    5.386180] [drm] Loading R100 Microcode

~]# cat /sys/devices/system/cpu/cpu0/microcode/version
0x6000852

~]# dracut -f

~]# reboot

~]#  grep -i microcode /var/log/dmesg
[    3.662735] microcode: microcode updated early to new patch_level=0x06000852
[    3.669792] microcode: CPU0: patch_level=0x06000852
[    3.674656] microcode: CPU1: patch_level=0x06000852
[    3.679668] microcode: CPU2: patch_level=0x06000852
[    3.684533] microcode: CPU3: patch_level=0x06000852
[    3.689546] microcode: CPU4: patch_level=0x06000852
[    3.694414] microcode: CPU5: patch_level=0x06000852
[    3.699428] microcode: CPU6: patch_level=0x06000852
[    3.704296] microcode: CPU7: patch_level=0x06000852
[    3.709166] microcode: CPU8: patch_level=0x06000852
[    3.714033] microcode: CPU9: patch_level=0x06000852
[    3.719047] microcode: CPU10: patch_level=0x06000852
[    3.724002] microcode: CPU11: patch_level=0x06000852
[    3.729102] microcode: CPU12: patch_level=0x06000852
[    3.734056] microcode: CPU13: patch_level=0x06000852
[    3.739005] microcode: CPU14: patch_level=0x06000852
[    3.743958] microcode: CPU15: patch_level=0x06000852
[    3.749106] microcode: Microcode Update Driver: v2.01 <tigran.co.uk>, Peter Oruba
[    5.649682] [drm] Loading R100 Microcode
Comment 8 errata-xmlrpc 2018-10-30 10:11:33 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/RHBA-2018:3119
Note You need to log in before you can comment on or make changes to this bug.