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 1307179 - microcode.service failure on AMD CPU family 0xf
Summary: microcode.service failure on AMD CPU family 0xf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: microcode_ctl
Version: 7.2
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Rachel Sibley
URL:
Whiteboard:
: 1348987 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 22:41 UTC by Orion Poplawski
Modified: 2016-11-04 05:33 UTC (History)
2 users (show)

Fixed In Version: microcode_ctl-2.1-15.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:33:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2399 0 normal SHIPPED_LIVE microcode_ctl bug fix and enhancement update 2016-11-03 13:55:32 UTC

Description Orion Poplawski 2016-02-12 22:41:16 UTC 
Description of problem:

# systemctl status microcode.service -l
● microcode.service - Load CPU microcode update
   Loaded: loaded (/usr/lib/systemd/system/microcode.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2016-02-12 13:55:49 MST; 1h 40min ago
 Main PID: 479 (code=exited, status=1/FAILURE)

Feb 12 13:55:46 phlebas.cora.nwra.com systemd[1]: Starting Load CPU microcode update...
Feb 12 13:55:46 phlebas.cora.nwra.com bash[479]: /usr/bin/bash: /sys/devices/system/cpu/microcode/reload: No such file or directory
Feb 12 13:55:49 phlebas.cora.nwra.com systemd[1]: microcode.service: main process exited, code=exited, status=1/FAILURE
Feb 12 13:55:49 phlebas.cora.nwra.com systemd[1]: Failed to start Load CPU microcode update.
Feb 12 13:55:49 phlebas.cora.nwra.com systemd[1]: Unit microcode.service entered failed state.
Feb 12 13:55:49 phlebas.cora.nwra.com systemd[1]: microcode.service failed.

I think the service should run if /sys/devices/system/cpu/microcode/reload does not exist to avoid having a spurious service failure by using:

ConditionPathExists=/sys/devices/system/cpu/microcode/reload

# dmesg | grep -Fi microcode
[    0.967818] microcode: AMD CPU family 0xf not supported

Version-Release number of selected component (if applicable):
microcode_ctl-2.1-12.el7.x86_64
Comment 2 Petr Oros 2016-06-29 12:58:27 UTC 
*** Bug 1348987 has been marked as a duplicate of this bug. ***
Comment 4 Rachel Sibley 2016-08-18 18:33:48 UTC 
I was able to reproduce on an amd-dinar system by adding the dis_ucode_ldr on the kernel command line, here is the before/after output. After the fix the service is inactive with no failures as the ConditionPathExists=/sys/devices/system/cpu/microcode/reload was not met


Before
===============
[root@amd-dinar-04 ~]# uname -r
3.10.0-327.el7.x86_64

[root@amd-dinar-04 ~]# rpm -q microcode_ctl
microcode_ctl-2.1-12.el7.x86_64

[root@amd-dinar-04 ~]# systemctl status microcode.service -l
● microcode.service - Load CPU microcode update
   Loaded: loaded (/usr/lib/systemd/system/microcode.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2016-08-18 13:05:44 EDT; 2min 53s ago
  Process: 937 ExecStart=/usr/bin/bash -c echo 1 > /sys/devices/system/cpu/microcode/reload (code=exited, status=1/FAILURE)
 Main PID: 937 (code=exited, status=1/FAILURE)

Aug 18 13:05:43 amd-dinar-04.lab.bos.redhat.com systemd[1]: Starting Load CPU microcode update...
Aug 18 13:05:43 amd-dinar-04.lab.bos.redhat.com bash[937]: /usr/bin/bash: /sys/devices/system/cpu/microcode/reload: No such file or directory
Aug 18 13:05:44 amd-dinar-04.lab.bos.redhat.com systemd[1]: microcode.service: main process exited, code=exited, status=1/FAILURE
Aug 18 13:05:44 amd-dinar-04.lab.bos.redhat.com systemd[1]: Failed to start Load CPU microcode update.
Aug 18 13:05:44 amd-dinar-04.lab.bos.redhat.com systemd[1]: Unit microcode.service entered failed state.
Aug 18 13:05:44 amd-dinar-04.lab.bos.redhat.com systemd[1]: microcode.service failed.

After
===================
[root@amd-dinar-04 ~]# yum update microcode_ctl-2.1-15.el7.x86_64

- reboot

[root@amd-dinar-04 ~]# systemctl status microcode.service -l 
● microcode.service - Load CPU microcode update
   Loaded: loaded (/usr/lib/systemd/system/microcode.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Thu 2016-08-18 14:17:16 EDT; 1min 24s ago
           ConditionPathExists=/sys/devices/system/cpu/microcode/reload was not met

Aug 18 14:17:16 amd-dinar-04.lab.bos.redhat.com systemd[1]: Started Load CPU microcode update.
Comment 6 errata-xmlrpc 2016-11-04 05:33:31 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://rhn.redhat.com/errata/RHEA-2016-2399.html
Note You need to log in before you can comment on or make changes to this bug.