Bug 1138923 - mcelog fails to run: cpu is unsupported
Summary: mcelog fails to run: cpu is unsupported
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mcelog
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Prarit Bhargava
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-06 09:57 UTC by hw
Modified: 2015-06-29 22:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:24:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description hw 2014-09-06 09:57:30 UTC
Description of problem:

mcelog fails to run:


[root@yun:~]$ systemctl status mcelog
mcelog.service - Machine Check Exception Logging Daemon
   Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled)
   Active: failed (Result: exit-code) since Fri 2014-09-05 19:30:36 CEST; 16h ago
  Process: 702 ExecStart=/usr/sbin/mcelog --ignorenodev --daemon --foreground (code=exited, status=1/FAILURE)
  Process: 649 ExecStartPre=/etc/mcelog/mcelog.setup (code=exited, status=0/SUCCESS)
 Main PID: 702 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/mcelog.service

Sep 05 19:30:36 yun.yagibdah.de systemd[1]: Starting Machine Check Exception Logging Daemon...
Sep 05 19:30:36 yun.yagibdah.de mcelog.setup[649]: CPU is unsupported
Sep 05 19:30:36 yun.yagibdah.de systemd[1]: Started Machine Check Exception Logging Daemon.
Sep 05 19:30:36 yun.yagibdah.de mcelog[702]: mcelog: AMD Processor family 16: Please load edac_mce_amd module.
Sep 05 19:30:36 yun.yagibdah.de mcelog[702]: : Success
Sep 05 19:30:36 yun.yagibdah.de mcelog[702]: CPU is unsupported
Sep 05 19:30:36 yun.yagibdah.de systemd[1]: mcelog.service: main process exited, code=exited, status=1/FAILURE
Sep 05 19:30:36 yun.yagibdah.de systemd[1]: Unit mcelog.service entered failed state.
[root@yun:~]$ 


The CPU is an AMD Phenom 965.

Mcelog cannot be started manually, either, and there even is no failure message when started manually:


[root@yun:~]$ systemctl start mcelog
[root@yun:~]$ systemctl status mcelog                                                                                                                                                                                                        
mcelog.service - Machine Check Exception Logging Daemon
   Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled)
   Active: failed (Result: exit-code) since Sat 2014-09-06 11:49:26 CEST; 6s ago
  Process: 14051 ExecStart=/usr/sbin/mcelog --ignorenodev --daemon --foreground (code=exited, status=1/FAILURE)
  Process: 14048 ExecStartPre=/etc/mcelog/mcelog.setup (code=exited, status=0/SUCCESS)
 Main PID: 14051 (code=exited, status=1/FAILURE)

Sep 06 11:49:26 yun.yagibdah.de mcelog.setup[14048]: CPU is unsupported
Sep 06 11:49:26 yun.yagibdah.de systemd[1]: Started Machine Check Exception Logging Daemon.
Sep 06 11:49:26 yun.yagibdah.de mcelog[14051]: mcelog: AMD Processor family 16: Please load edac_mce_amd module.
Sep 06 11:49:26 yun.yagibdah.de mcelog[14051]: : Success
Sep 06 11:49:26 yun.yagibdah.de mcelog[14051]: CPU is unsupported
Sep 06 11:49:26 yun.yagibdah.de systemd[1]: mcelog.service: main process exited, code=exited, status=1/FAILURE
Sep 06 11:49:26 yun.yagibdah.de systemd[1]: Unit mcelog.service entered failed state.
[root@yun:~]$ 


[root@yun:~]$ lsmod |grep mce
ir_mce_kbd_decoder     13214  0 
rc_core                27490  13 ir_sharp_decoder,lirc_dev,ir_lirc_codec,rc_hauppauge,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,cx88xx,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder
edac_mce_amd           22349  0 
[root@yun:~]$ 


Version-Release number of selected component (if applicable):

[root@yun:~]$ mcelog --version
mcelog 1.0pre
[root@yun:~]$ 


How reproducible:

boot the system


Actual results:

mcelog does not run

Expected results:


Additional info:

This CPU used to be supported by mcelog.


[root@yun:~]$ uname -a
Linux yun.yagibdah.de 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@yun:~]$ cat /proc/cpuinfo | grep -i model
model           : 4
model name      : AMD Phenom(tm) II X4 965 Processor
model           : 4
model name      : AMD Phenom(tm) II X4 965 Processor
model           : 4
model name      : AMD Phenom(tm) II X4 965 Processor
model           : 4
model name      : AMD Phenom(tm) II X4 965 Processor
[root@yun:~]$

Comment 1 Fedora End Of Life 2015-05-29 12:48:28 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 2 Fedora End Of Life 2015-06-29 22:24:36 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.


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