Description of problem: When I boot a fresh installation of Fedora 29 Cinnamon desktop and try to test one of the Fedora QA testcases that checks for failed services, I am able to find a failed service which is unwanted behaviour. Version-Release number of selected component (if applicable): Fedora 29 Beta 1.3 RC How reproducible: Always Steps to Reproduce: 1. Do a fresh install on my PC. 2. After start, run systemctl --all --failed. Actual results: Using the command above, I am getting the following: ==== UNIT LOAD ACTIVE SUB DESCRIPTION ● mcelog.service loaded failed failed Machine Check Exception Logging Daemon ==== Journal says this: ==== [bdylan@localhost ~]$ journalctl -u mcelog -- Logs begin at Tue 2018-09-18 15:17:56 CEST, end at Tue 2018-09-18 15:28:15 CEST. -- zář 18 15:18:02 localhost.localdomain systemd[1]: Started Machine Check Exception Logging Daemon. zář 18 15:18:02 localhost.localdomain mcelog[797]: mcelog: ERROR: AMD Processor family 21: mcelog does not support this processor. Please use the edac_mce_amd module instead. zář 18 15:18:02 localhost.localdomain mcelog[797]: CPU is unsupported zář 18 15:18:02 localhost.localdomain systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE zář 18 15:18:02 localhost.localdomain systemd[1]: mcelog.service: Failed with result 'exit-code'. ==== My machine is: ==== Architektura: x86_64 Operační režim(y) CPU: 32-bit, 64-bit Pořadí bajtů: Little Endian Počet CPU: 4 Seznam zapnutých CPU: 0-3 Vláken na jádro: 2 Jader na patici: 2 Patic: 1 Uzly NUMA: 1 ID výrobce: AuthenticAMD Rodina CPU: 21 Model: 56 Název modelu: AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G Stepping: 1 CPU MHz: 2001.744 CPU max. MHz: 3900,0000 CPU min. MHz: 1700,0000 BogoMIPS: 7780.84 Virtualizace: AMD-V L1d keš: 16K L1i keš: 96K L2 keš: 2048K CPU NUMA uzlu 0: 0-3 Příznaky: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc cpb hw_pstate proc_feedback ssbd vmmcall fsgsbase bmi1 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold overflow_recov ==== Expected results: mcelog should not fail.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.