Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1792527[details]
t4g.large_journal_20210620.log
Description of problem:
In aws, boot a RHEL-8.5(RHEL-8.5.0-20210619.n.0) arm instances, there are over 300 lines of the same log produced in the journal log.
# journalctl |grep -i 'Entropy Generation is slow,'|wc -l
312
# systemctl status rngd
● rngd.service - Hardware RNG Entropy Gatherer Daemon
Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-06-20 13:46:46 UTC; 11min ago
Main PID: 926 (rngd)
Tasks: 3 (limit: 11944)
Memory: 7.3M
CGroup: /system.slice/rngd.service
└─926 /usr/sbin/rngd -f --fill-watermark=0
Jun 20 13:46:48 ip-10-22-1-148.us-west-2.compute.internal rngd[926]: Entropy Generation is slow, consider tuning/adding sources
Jun 20 13:46:48 ip-10-22-1-148.us-west-2.compute.internal rngd[926]: Entropy Generation is slow, consider tuning/adding sources
Jun 20 13:46:48 ip-10-22-1-148.us-west-2.compute.internal rngd[926]: Entropy Generation is slow, consider tuning/adding sources
[root@ip-10-116-2-114 ec2-user]# rpm -q rng-tools
rng-tools-6.8-5.el8.aarch64
Version-Release number of selected components (if applicable):
RHEL Version:
RHEL-8.5(4.18.0-314.el8.aarch64)
How reproducible:
100%
Steps to Reproduce:
1. start a RHEL-8.5 arm instance, eg. t4g.large
2. Check journal log after boot.
Actual results:
Too many same log fill the journal log
Expected results:
1 or 2 lines are sufficient.
Additional info:
N/A
an update for the rng-tools is being added to RHEL8: rng-tools-6.13-1.git.d207e0b6.el8.
one of the features is a support for ARM v8.5 RNDR Instruction RNG (rndr).
with RNDR rng-tools should have enough entropy, you can test the candidate package at:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=38749313
i've double-checked that RNDR code is really built, unfortunately, a test ARM machine
itself does not support RNDR:
# uname -a
Linux apm-mustang-b0-11.khw4.lab.eng.bos.redhat.com 4.18.0-305.el8.aarch64 #1 SMP aarch64 aarch64 aarch64 GNU/Linux
# /usr/sbin/rngd -f -d -x jitter -n rndr
Disabling 6: JITTER Entropy generator (jitter)
Enabling 4: ARM v8.5 RNDR Instruction RNG (rndr)
Initializing available sources
[hwrng ]: Initialized
[rndr ]: No HW SUPPORT
[rndr ]: Initialization Failed
Kernel entropy pool size 4096, pool watermark 3072
Created attachment 1792527 [details] t4g.large_journal_20210620.log Description of problem: In aws, boot a RHEL-8.5(RHEL-8.5.0-20210619.n.0) arm instances, there are over 300 lines of the same log produced in the journal log. # journalctl |grep -i 'Entropy Generation is slow,'|wc -l 312 # systemctl status rngd ● rngd.service - Hardware RNG Entropy Gatherer Daemon Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-06-20 13:46:46 UTC; 11min ago Main PID: 926 (rngd) Tasks: 3 (limit: 11944) Memory: 7.3M CGroup: /system.slice/rngd.service └─926 /usr/sbin/rngd -f --fill-watermark=0 Jun 20 13:46:48 ip-10-22-1-148.us-west-2.compute.internal rngd[926]: Entropy Generation is slow, consider tuning/adding sources Jun 20 13:46:48 ip-10-22-1-148.us-west-2.compute.internal rngd[926]: Entropy Generation is slow, consider tuning/adding sources Jun 20 13:46:48 ip-10-22-1-148.us-west-2.compute.internal rngd[926]: Entropy Generation is slow, consider tuning/adding sources [root@ip-10-116-2-114 ec2-user]# rpm -q rng-tools rng-tools-6.8-5.el8.aarch64 Version-Release number of selected components (if applicable): RHEL Version: RHEL-8.5(4.18.0-314.el8.aarch64) How reproducible: 100% Steps to Reproduce: 1. start a RHEL-8.5 arm instance, eg. t4g.large 2. Check journal log after boot. Actual results: Too many same log fill the journal log Expected results: 1 or 2 lines are sufficient. Additional info: N/A