Bug 1744315 - Rngd consume 100% cpu
Summary: Rngd consume 100% cpu
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: jitterentropy-rngd
Version: 29
Hardware: x86_64
OS: Mac OS
unspecified
urgent
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-21 20:13 UTC by lottabugs indacode
Modified: 2019-11-27 23:19 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 23:19:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description lottabugs indacode 2019-08-21 20:13:35 UTC
Description of problem:

The computer is unusable with rngd drawing 100% of cpu.


Version-Release number of selected component (if applicable):
5.2.9-200.fc30.x86_64 #1 SMP Fri Aug 16 21:37:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 


How reproducible:
Fresh install from 29 to 30 on a macbookpro late 2013.

Comment 1 Julian Stecklina 2019-08-30 09:35:30 UTC
I see the same issue of rngd occasionally starting to use 100% of CPU until I restart the service. This is particularly annoying, because if it happens it drains the battery pretty fast.

This is with Fedora 30 on a Dell XPS 13 with:

rng-tools-6.7-2.fc30.x86_64

Comment 2 Julian Stecklina 2019-08-30 09:37:57 UTC
Other interesting tidbit: I have a Yubikey Nano in my laptop and it seems that rngd has at least some logic to gather entropy from smartcards. Maybe it is related.

This may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1739730

Comment 3 Ben Cotton 2019-10-31 18:53:51 UTC
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.

Comment 4 Ben Cotton 2019-11-27 23:19:57 UTC
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.


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