Description of problem: rngd.service fails on AMD Processor Family 21 and issues Version-Release number of selected component (if applicable): rng-tools.x86_64 5-3.fc21 How reproducible: always Steps to Reproduce: 1. boot f21 beta on an AMD FX-8350 box. 2. 3. Actual results: service fails to start, logs ugly errors unnecessarily Expected results: quiet behavior when the daemon fails to start on hardware that does not support it, hardware upon which it is not supposed to start. Additional info:
# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● mcelog.service loaded failed failed Machine Check Exception Logging Daemon ● rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon # systemctl status rngd.service ● rngd.service - Hardware RNG Entropy Gatherer Daemon Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled) Active: failed (Result: exit-code) since Sat 2014-11-22 03:57:46 CST; 4min 36s ago Process: 11724 ExecStart=/sbin/rngd -f (code=exited, status=1/FAILURE) Main PID: 11724 (code=exited, status=1/FAILURE) Nov 22 03:57:46 ************ systemd[1]: Started Hardware RNG Entropy Gatherer Daemon. Nov 22 03:57:46 ************ rngd[11724]: Unable to open file: /dev/tpm0 Nov 22 03:57:46 ************ rngd[11724]: can't open any entropy source Nov 22 03:57:46 ************ rngd[11724]: Maybe RNG device modules are not loaded Nov 22 03:57:46 ************ systemd[1]: rngd.service: main process exited, code=exited, status=1/FAILURE Nov 22 03:57:46 ************ systemd[1]: Unit rngd.service entered failed state. Nov 22 03:57:46 ************ systemd[1]: rngd.service failed. # systemctl start rngd.service # systemctl status rngd.service ● rngd.service - Hardware RNG Entropy Gatherer Daemon Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled) Active: failed (Result: exit-code) since Sat 2014-11-22 04:03:54 CST; 5s ago Process: 11945 ExecStart=/sbin/rngd -f (code=exited, status=1/FAILURE) Main PID: 11945 (code=exited, status=1/FAILURE) Nov 22 04:03:54 ************** systemd[1]: Started Hardware RNG Entropy Gatherer Daemon. Nov 22 04:03:54 ************** systemd[1]: rngd.service: main process exited, code=exited, status=1/FAILURE Nov 22 04:03:54 ************** systemd[1]: Unit rngd.service entered failed state. Nov 22 04:03:54 ************** systemd[1]: rngd.service failed. Nov 22 04:03:54 ************** rngd[11945]: Unable to open file: /dev/tpm0 Nov 22 04:03:54 ************** rngd[11945]: can't open any entropy source Nov 22 04:03:54 ************** rngd[11945]: Maybe RNG device modules are not loaded
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.