Bug 1047141

Summary: mcelog reports AMD family 15 (K8) is unsupported and exits.
Product: [Fedora] Fedora Reporter: otheos <bugzilla>
Component: mcelogAssignee: Prarit Bhargava <prarit>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 20CC: clintonminton, ferdnyc, iamdexpl, next.little.owl, prarit
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:55:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
mcelog.spec patch to build latest upstream release none

Description otheos 2013-12-29 11:59:37 UTC
Description of problem:
mcelog complains that the CPU AMD Family 15 is not supported and exits. Actual message on journalctl.

mcelog[18917]: mcelog: AMD Processor family 15: Please load edac_mce_amd module.


Version-Release number of selected component (if applicable):
mcelog-1.0-0.11.f0d7654.fc20.i686

How reproducible: Specific to K8 CPUs


Steps to Reproduce:
1. Install Fedora 20 on K8 CPU system
2. Boot up.
3. Check journalctl for mcelog entries

Actual results:
mcelog service fails with output.
mcelog[18917]: mcelog: AMD Processor family 15: Please load edac_mce_amd module.

Expected results:

mcelog service starting

Additional info:
BTW, this output message is unclear if edac_mce_amd is a prerequisite for the service to start or an alternative. It is also unclear if the module is loaded at that time.

Comment 1 otheos 2013-12-29 12:01:24 UTC
Forgot to mention that mcelog lists K8 as supported, obviously.

BTW, there is a discussion here which I think addresses the matter:

https://github.com/andikleen/mcelog/pull/3

(In reply to otheos from comment #0)
> Description of problem:
> mcelog complains that the CPU AMD Family 15 is not supported and exits.
> Actual message on journalctl.
> 
> mcelog[18917]: mcelog: AMD Processor family 15: Please load edac_mce_amd
> module.
> 
> 
> Version-Release number of selected component (if applicable):
> mcelog-1.0-0.11.f0d7654.fc20.i686
> 
> How reproducible: Specific to K8 CPUs
> 
> 
> Steps to Reproduce:
> 1. Install Fedora 20 on K8 CPU system
> 2. Boot up.
> 3. Check journalctl for mcelog entries
> 
> Actual results:
> mcelog service fails with output.
> mcelog[18917]: mcelog: AMD Processor family 15: Please load edac_mce_amd
> module.
> 
> Expected results:
> 
> mcelog service starting
> 
> Additional info:
> BTW, this output message is unclear if edac_mce_amd is a prerequisite for
> the service to start or an alternative. It is also unclear if the module is
> loaded at that time.

Comment 2 Václav Mocek 2014-02-08 20:46:24 UTC
I can confirm that the patch mentioned above fixes the issue.

Comment 3 Vadim Raskhozhev 2014-07-10 19:36:39 UTC
Same here on AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ with mcelog-1.0-0.11.f0d7654.fc20.x86_64

Comment 4 "FeRD" (Frank Dana) 2014-09-07 09:50:48 UTC
This was actually fixed upstream in mcelog, back on 2014-03-25 (the patch linked above was accepted).

However, the Fedora 20 mcelog-1.0-0.11.f0d7654.fc20 RPM hasn't been updated since 2013-08-14 (more than a year ago). It appears (though I didn't examine it in detail) that the latest rawhide mcelog-1.0-0.13.f0d7654.fc22 RPM, while rebuilt, is also still based off of the same upstream release.

This puts us a good three releases out of date, based on mcelog's new rolling release scheme. (See https://github.com/andikleen/mcelog/blob/master/README.releases )

The latest mcelog (which includes this fix) is tagged v102, from 2014-07-04.

https://github.com/andikleen/mcelog/releases/tag/v102

Comment 5 "FeRD" (Frank Dana) 2014-09-07 10:14:52 UTC
Created attachment 935126 [details]
mcelog.spec patch to build latest upstream release

mcelog v102 builds as a drop-in replacement for the latest Fedora RPM, it would seem — starting with the mcelog.spec from mcelog-1.0-0.11.f0d7654.fc20.src.rpm, I built a new package from upstream's v102 download with only minor housekeeping changes. specfile patch attached.

The resulting mcelog-102.0.1.fc20.x86_64.rpm does fix this bug, on my affected system.

Comment 6 Fedora End Of Life 2015-05-29 10:13:25 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-06-29 13:55:19 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.