Description of problem: I have a CPU: Quad Core AMD A8-6410 APU with AMD Radeon R5 Graphics (-MCP-) For every linux distribution I get this error: mcelog: ERROR: AMD Processor family 22: mcelog does not support this processor. Please use the edac_mce_amd modul Version-Release number of selected component (if applicable): Fedora 27, mcelog How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Please fix this bug.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.
re-opening this bug as it's reproduced on current release (f28, but I guess later also). The point of a failure is that something went unexpected and that there is a something to fix. If mcelog isn't supposed to be run, then the error code should probably be changed so that it's not reported as a failure on end-users system. mcelog: ERROR: AMD Processor family 16: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported If the mcelog.service can be made to be inhibited if there is a special path in /proc or /sys that show that edac_mce_amd is loaded, it should probably avoid the issue.
I now have: # systemctl status mcelog ● mcelog.service - Machine Check Exception Logging Daemon Loaded: loaded (/etc/systemd/system/mcelog.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Thu 2019-03-28 08:03:27 CET; 51s ago └─ ConditionPathExists=!/sys/module/edac_mce_amd/initstate was not met [root@arrakis kwizart]# cat /etc/systemd/system/mcelog.service [Unit] Description=Machine Check Exception Logging Daemon ConditionPathExists=!/sys/module/edac_mce_amd/initstate [Service] ExecStart=/usr/sbin/mcelog --ignorenodev --daemon --foreground [Install] WantedBy=multi-user.target
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Here's what I get: $ systemctl status mcelog.service ● mcelog.service - Machine Check Exception Logging Daemon Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-09-12 11:26:09 EDT; 2h 46min ago Process: 871 ExecStart=/usr/sbin/mcelog --ignorenodev --daemon --foreground (code=exited, status=1/FAILURE) Main PID: 871 (code=exited, status=1/FAILURE) Sep 12 11:26:09 infinity.localdomain systemd[1]: Started Machine Check Exception Logging Daemon. Sep 12 11:26:09 infinity.localdomain mcelog[871]: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Sep 12 11:26:09 infinity.localdomain mcelog[871]: CPU is unsupported Sep 12 11:26:09 infinity.localdomain systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE Sep 12 11:26:09 infinity.localdomain systemd[1]: mcelog.service: Failed with result 'exit-code'. It looks like the module is loaded: $ lsmod | grep amd edac_mce_amd 32768 0 If you are in the same situation as me, it is probably safe to ignore this error.
Forgot to add, I found this related bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1069652
There is no point to throw and error and even less a warning if the edac_mce_amd module is loaded. That the very much reason to add "ConditionPathExists=!/sys/module/edac_mce_amd/initstate" ! https://bugzilla.redhat.com/show_bug.cgi?id=1526725#c4 Is there a maintainer for this package ?
*** Bug 1069652 has been marked as a duplicate of this bug. ***
(In reply to Nicolas Chauvet (kwizart) from comment #8) > There is no point to throw and error and even less a warning if the > edac_mce_amd module is loaded. > That the very much reason to add > "ConditionPathExists=!/sys/module/edac_mce_amd/initstate" ! > https://bugzilla.redhat.com/show_bug.cgi?id=1526725#c4 > > > Is there a maintainer for this package ? Yup, me. I'll look into it. P.
Error similarly is seen on Fedora 31. My Environment is below: DE KDE (X11) SecureBoot Enabled Kernel 5.3.13-300.fc31.x86_64 System Fedora 31 Arch x86_64 CPU Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx systemctl status mcelog.service message: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module I have masked the service now. Hopefully no message should be seen on next boot
(In reply to Prarit Bhargava from comment #10) > (In reply to Nicolas Chauvet (kwizart) from comment #8) > > There is no point to throw and error and even less a warning if the > > edac_mce_amd module is loaded. > > That the very much reason to add > > "ConditionPathExists=!/sys/module/edac_mce_amd/initstate" ! > > https://bugzilla.redhat.com/show_bug.cgi?id=1526725#c4 > > > > > > Is there a maintainer for this package ? > > Yup, me. I'll look into it. Any news on your side ?
Oof. I forgot to hit the pull request button. I just did that now and it is in Andi's queue. https://github.com/andikleen/mcelog/pulls P.
(In reply to Prarit Bhargava from comment #13) ... > https://github.com/andikleen/mcelog/pulls Thx a lot for having this issue to progress. That been said, I'm a little disapointed that you have created a commit without mentionning me as an "author" of the change (I would give my signed-off anyway) : https://bugzilla.redhat.com/show_bug.cgi?id=1526725#c4 At the very least I'd like to be mentionned in the commit. I was not aware of the mcelog github, or I would have created the commit directly there, indeed.
(In reply to Nicolas Chauvet (kwizart) from comment #14) > (In reply to Prarit Bhargava from comment #13) > ... > > https://github.com/andikleen/mcelog/pulls > Thx a lot for having this issue to progress. > > That been said, I'm a little disapointed that you have created a commit > without mentionning me as an "author" of the change (I would give my > signed-off anyway) : > https://bugzilla.redhat.com/show_bug.cgi?id=1526725#c4 > At the very least I'd like to be mentionned in the commit. > > I was not aware of the mcelog github, or I would have created the commit > directly there, indeed. Oof. Sorry, my bad. I absolutely should have included you in the commit message. Please excuse me and accept my apologies. P.
Okay let's pass on that. Next step would be to update mcelog in fedora...
Hello Anyone to consider reviewing this updated change. https://src.fedoraproject.org/rpms/mcelog/pull-request/2 Here a scratch build for f31: https://koji.fedoraproject.org/koji/taskinfo?taskID=41860894 Tested with amd phenom x4 just fine.
Fresh Installation, Fedora 32 (beta): X570 AORUS ELITE; Version -CF; BIOS American Megatrends Inc.; BIOS version F12f; BIOS date 03/20/2020; CPU 16x AMD Ryzen 7 3700X 8-Core Processor Services mcelog.service Machine Check Exception Logging Daemon Status Failed to start Automatically starts Path /usr/lib/systemd/system/mcelog.service Requires system.slice sysinit.target Wanted By multi-user.target Conflicts shutdown.target Before shutdown.targetmulti-user.target After systemd-journald.socket basic.target sysinit.target system.slice Service Logs March 20, 2020 10:34 AM mcelog.service: Failed with result 'exit-code'. systemd 10:34 AM mcelog.service: Main process exited, code=exited, status=1/FAILURE systemd 10:34 AM CPU is unsupported mcelog 10:34 AM mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. mcelog 10:34 AM Started Machine Check Exception Logging Daemon. systemd Reboot 10:14 AM mcelog.service: Failed with result 'exit-code'. systemd 10:14 AM mcelog.service: Main process exited, code=exited, status=1/FAILURE systemd 10:14 AM CPU is unsupported mcelog 10:14 AM mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. mcelog 10:14 AM Started Machine Check Exception Logging Daemon. systemd
Fresh install on Fedora Server 33. Server is running under libvirt, on a host that runs a AMD Ryzen 5 2600 cpu. Machine Check Exception Logging Daemon Status: Failed to start Automatically starts Path /usr/lib/systemd/system/mcelog.service Requires sysinit.targetsystem.slice Wanted by multi-user.target Conflicts shutdown.target Before multi-user.targetshutdown.target After basic.targetsysinit.targetsyslog.targetsystem.slicesystemd-journald.socket Service Logs November 8, 2020 11:29 AM mcelog.service: Failed with result 'exit-code'. systemd 11:29 AM mcelog.service: Main process exited, code=exited, status=1/FAILURE systemd 11:29 AM CPU is unsupported mcelog 11:29 AM mcelog: ERROR: AMD Processor family 23: mcelog mcelog does not support this processor. Please use the edac_mce_amd module instead. 11:29 AM Started Machine Check Exception Logging Daemon. systemd 11:29 AM mcelog.service: Failed with result 'exit-code'. systemd 11:29 AM mcelog.service: Main process exited, code=exited, status=1/FAILURE systemd 11:29 AM CPU is unsupported mcelog 11:29 AM mcelog: ERROR: AMD Processor family 23: mcelog mcelog does not support this processor. Please use the edac_mce_amd module instead. 11:29 AM Started Machine Check Exception Logging Daemon. systemd
(In reply to Charlie Candergart from comment #19) > Fresh install on Fedora Server 33. > Server is running under libvirt, on a host that runs a AMD Ryzen 5 2600 cpu. What do you call "running under libvirt" ? Are you using lxc, xen, kvm, qemu or else ? While "running under libvirt" is the /sys/module/edac_mce_amd/initstate file present ? or is the directory empty or non-existant ? Is the /sys directory even available at all (or you are running under a container or chroot) ? What is the output of the virt-what command ? Please answear using a separate ticket (and mention it there) as this is a little different issue. Thanks.
Sorry, I have no idea what to select when trying to create a new separate ticket. This bug reporting system is all way too confusing to me. I am running QEMU on a Fedora 32 server. The guest machine (virtual machine) is running Fedora 33 server. The guest shows this: ls -alh /sys/module/edac_mce_amd/initstate ls: cannot access '/sys/module/edac_mce_amd/initstate': No such file or directory The QEMU host shows this: ls -alh /sys/module/edac_mce_amd/initstate -r--r--r--. 1 root root 4.0K Nov 8 10:01 /sys/module/edac_mce_amd/initstate I will try to figure out how to make a new ticket but for now, this is what you get. /Charlie
link to new ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1895711
On Fedora 34, systemctl --failed says : ● mcelog.service loaded failed failed Machine Check Exception Logging Daemon Because /sys/module/edac_mce_amd is created after mcelog.service start : ls -l --full-time /sys/module/edac_mce_amd ; systemctl status -l mcelog.service total 0 -r--r--r-- 1 root root 4096 2021-06-21 10:31:01.866261716 +0200 coresize drwxr-xr-x 2 root root 0 2021-06-21 10:31:01.866261716 +0200 holders -r--r--r-- 1 root root 4096 2021-06-21 10:31:24.336055396 +0200 initsize -r--r--r-- 1 root root 4096 2021-06-21 10:29:32.279307790 +0200 initstate drwxr-xr-x 2 root root 0 2021-06-21 10:31:24.336055396 +0200 notes -r--r--r-- 1 root root 4096 2021-06-21 10:31:01.866261716 +0200 refcnt drwxr-xr-x 2 root root 0 2021-06-21 10:31:24.336055396 +0200 sections -r--r--r-- 1 root root 4096 2021-06-21 10:31:24.336055396 +0200 taint --w------- 1 root root 4096 2021-06-21 10:29:32.994301323 +0200 uevent × mcelog.service - Machine Check Exception Logging Daemon Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2021-06-21 10:29:30 CEST; 4min 49s ago Process: 1629 ExecStart=/usr/sbin/mcelog --daemon --foreground (code=exited, status=1/FAILURE) Main PID: 1629 (code=exited, status=1/FAILURE) CPU: 2ms juin 21 10:29:30 chappie mcelog[1629]: mcelog: ERROR: AMD Processor family 21: mcelog does not support this processor. Please use the edac_mce_amd module instead. juin 21 10:29:30 chappie mcelog[1629]: CPU is unsupported juin 21 10:29:30 chappie systemd[1]: Started Machine Check Exception Logging Daemon. juin 21 10:29:30 chappie systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE juin 21 10:29:30 chappie systemd[1]: mcelog.service: Failed with result 'exit-code'. "ConditionPathExists=!/sys/module/edac_mce_amd/initstate" isn't enough. Perhaps, the service mcelog must be launched after systemd-modules-load.service.
Please use a separate report eventually referencing this one.