Anytime rngd is started it generates lots of the following messages in /var/log/messages: Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources Jul 15 10:12:04 localhost rngd[1939]: Entropy Generation is slow, consider tuning/adding sources This is on a system with the following older CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz SSD for a boot drive This is a fresh install of Fedora 32 MATE This did not happen on a slightly older CPU on Fedora 30 I am wondering if this is the cause of some intermittent failures of other software components that I am having during boot: NetworkManager intermittently fails to start at boot (https://bugzilla.redhat.com/show_bug.cgi?id=1857011) LightDM intermittently fails to start at boot LightDM intermittently fails to autologin at boot
My fresh installation of Fedora 33 workstation also have this issue. Jan 20 13:48:57 xxxx.lan rngd[233]: Entropy Generation is slow, consider tuning/adding sources Jan 20 13:48:57 xxxx.lan rngd[233]: Entropy Generation is slow, consider tuning/adding sources Jan 20 13:48:57 xxxx.lan rngd[233]: Entropy Generation is slow, consider tuning/adding sources Jan 20 13:48:57 xxxx.lan rngd[233]: Entropy Generation is slow, consider tuning/adding sources
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.