Bug 1895711
| Summary: | mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charlie Candergart <charlie.candergart> |
| Component: | mcelog | Assignee: | Prarit Bhargava <prarit> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 40 | CC: | dwrobel, jonathan, prarit |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-05-16 07:37:50 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: | |||
mcelog is known not to work on newer AMD platforms. Hence, the error message. You can try using rasdaemon instead. P. I'm still observing failure on starting mcelog.service on the Fedora Server F39 using:
# rpm -qv mcelog
mcelog-175-10.fc40.x86_64
Here is the environment:
root@localhost:~# grep ConditionPathExists /usr/lib/systemd/system/mcelog.service
ConditionPathExists=!/sys/module/edac_mce_amd/initstate
ConditionPathExists=/dev/mcelog
root@localhost:~# ls -ls /sys/module/edac_mce_amd/initstate /dev/mcelog
0 crw------- 1 root root 10, 227 May 17 14:30 /dev/mcelog
0 -r--r--r-- 1 root root 4096 May 17 14:45 /sys/module/edac_mce_amd/initstate
root@localhost:~# systemctl status mcelog
× mcelog.service - Machine Check Exception Logging Daemon
Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Fri 2024-05-17 14:30:04 CEST; 20min ago
Duration: 255ms
Process: 773 ExecStart=/usr/sbin/mcelog --daemon --foreground (code=exited, status=1/FAILURE)
Main PID: 773 (code=exited, status=1/FAILURE)
CPU: 19ms
May 17 14:30:04 localhost.localdomain systemd[1]: Started mcelog.service - Machine Check Exception Logging Daemon.
May 17 14:30:04 localhost.localdomain mcelog[773]: mcelog: ERROR: AMD Processor family 21: mcelog does not support this processor. Please use the edac_mce_amd module instead.
May 17 14:30:04 localhost.localdomain mcelog[773]: CPU is unsupported
May 17 14:30:04 localhost.localdomain systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE
May 17 14:30:04 localhost.localdomain systemd[1]: mcelog.service: Failed with result 'exit-code'.
The problem is that there was an attemp to start the service, which normally shouldn't. Interestingly when you try to start it manually, later on:
root@localhost:~# systemctl start mcelog && echo success
success
root@localhost:~# systemctl status mcelog
× mcelog.service - Machine Check Exception Logging Daemon
Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Fri 2024-05-17 14:30:04 CEST; 25min ago
Duration: 255ms
Condition: start condition unmet at Fri 2024-05-17 14:55:31 CEST; 8s ago
└─ ConditionPathExists=!/sys/module/edac_mce_amd/initstate was not met
Process: 773 ExecStart=/usr/sbin/mcelog --daemon --foreground (code=exited, status=1/FAILURE)
Main PID: 773 (code=exited, status=1/FAILURE)
CPU: 19ms
May 17 14:30:04 localhost.localdomain systemd[1]: Started mcelog.service - Machine Check Exception Logging Daemon.
May 17 14:30:04 localhost.localdomain mcelog[773]: mcelog: ERROR: AMD Processor family 21: mcelog does not support this processor. Please use the edac_mce_amd module instead.
May 17 14:30:04 localhost.localdomain mcelog[773]: CPU is unsupported
May 17 14:30:04 localhost.localdomain systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE
May 17 14:30:04 localhost.localdomain systemd[1]: mcelog.service: Failed with result 'exit-code'.
May 17 14:51:19 localhost.localdomain systemd[1]: mcelog.service - Machine Check Exception Logging Daemon was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/edac_mce_amd/initstate).
it properly return success and report that is was skipped due to unmet condition check. So something seems to be wrong with dependencies that both of the conditions are met during bootup?
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. 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 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |
Problem: Service MCELOG fails to start Message: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. This is a fresh install of Fedora Server 33. Server is a (guest) virtual machine running under libvirt/QEMU, Physical server runs an AMD Ryzen 5 2600 cpu. Full output from the cockpit view of the service: 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 Answer to Nicolas Chauvet (Kwizart): * What do you call "running under libvirt" ? Are you using lxc, xen, kvm, qemu or else ? -- QEMU * 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) ? -- The guest is a full install of fedora server 33, full virtual server. It is in every regard the same as a physical server, except for the hardware. There are no containers, chroots or special circumstances involved. The guest show this: ls -alh /sys/module/edac_mce_amd/initstate ls: cannot access '/sys/module/edac_mce_amd/initstate': No such file or directory The closest I can get to that path is /sys/module/, the sub directory named edac_mce_amd does not exist. 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 Best Regards Charlie Candergart