Bug 1885114
Summary: | Unable to start mcelog service | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ashish Kumar <ashish.dav99> |
Component: | mcelog | Assignee: | Prarit Bhargava <prarit> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | ashish.dav99, jonathan, prarit, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-04-01 13:13:13 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: |
Description
Ashish Kumar
2020-10-05 06:25:58 UTC
I observed the same issue in a VMware virtual machine that is hosted on a AMD Ryzen 7 3700U. I replaced the mcelog package with the rasdaemon. Thanks @Thomas Neuber. That is the correct course of action. mcelog is known not to work on newer AMD platforms. P. |