RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1679010 - rngd: Failed to init entropy source hwrng
Summary: rngd: Failed to init entropy source hwrng
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rng-tools
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Neil Horman
QA Contact: Vilém Maršík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-20 05:56 UTC by Yongcheng Yang
Modified: 2019-05-22 05:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-21 12:21:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yongcheng Yang 2019-02-20 05:56:08 UTC
Description of problem:
"rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Failed to init entropy source hwrng"
is printed in journal after system boot.

Version-Release number of selected component (if applicable):
rng-tools-6.6-2.el8

How reproducible:
always

Steps to Reproduce:
1. clean boot and check the journal logs

Actual results:
[root ~]# journalctl -b 0 | grep rngd
Feb 19 22:37:44 rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Initalizing available sources
Feb 19 22:37:44 rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Failed to init entropy source hwrng
Feb 19 22:37:44 rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Enabling RDRAND rng support
Feb 19 22:37:44 rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Initalizing entropy source rdrand
Feb 19 22:37:45 rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Enabling JITTER rng support
Feb 19 22:37:45 rhel-8.0.rhts.eng.pek2.redhat.com rngd[1194]: Initalizing entropy source jitter
[root ~]# rpm -q rng-tools
rng-tools-6.6-2.el8.x86_64


Expected results:
Do not have such error/failed log.

Additional info:

Comment 1 Neil Horman 2019-02-20 12:11:52 UTC
do you have a hwrng device present on the system?

Comment 2 Yongcheng Yang 2019-02-21 01:38:26 UTC
(In reply to Neil Horman from comment #1)
> do you have a hwrng device present on the system?

I'm afraid not.

I'm just always seeing this message after booting each machine reserved from Beaker.
IMO it should be a warning instead of failing, which make me think there's something wrong occurs.


Note You need to log in before you can comment on or make changes to this bug.