Bug 1694290

Summary: Long shutdown - Hardware RNG Entropy Gatherer Daemon
Product: [Fedora] Fedora Reporter: Artem <ego.cordatus>
Component: rng-toolsAssignee: Neil Horman <nhorman>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: bugzilla, jaromir.capik, jgarzik, lewk, nhorman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-01 13:36:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artem 2019-03-30 07:14:59 UTC
Description of problem:
  After last updates system shutting down take a long time because of:
    A stop job is running for Hardware RNG Entropy Gatherer Daemon (1min 30s)

Version-Release number of selected component (if applicable):
  kernel-5.0.4-300.fc30
  systemd-241-4.gitcbf14c9.fc30
  rng-tools-6.7-1.fc30

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Artem 2019-03-30 07:19:28 UTC
Oops, since editing messages not possible:

Description of problem:
  After last updates system shutting down take a long time because of:
    A stop job is running for Hardware RNG Entropy Gatherer Daemon (1min 30s)

Version-Release number of selected component (if applicable):
  kernel-5.0.4-300.fc30
  systemd-241-4.gitcbf14c9.fc30
  rng-tools-6.7-1.fc30

How reproducible:
  Turn off Fedora 30 (real system or VM).

Actual results:
  Shutdown take about 1min 30s.

Expected results:
  Shutdown take about 1-2s as before.

Comment 2 Chris Murphy 2019-04-01 06:15:18 UTC
If you can edit /usr/lib/systemd/system/rngd.service and add -d flag to set debug option for rngd; and then also do a one time edit of linux command line parameter in GRUB adding `systemd.log_level=debug systemd.debug-shell=1` then boot. Then reboot, and during the hang you should be able to get to tty9 (debug shell) and do `systemctl list-jobs > bug1694290_systemdlistjobs.txt` Following reboot you can get the previous journal with `sudo journalctl -b-1 -o short-monotonic > bug1694290_journaldebug.txt`

And attach them both. You can also reedit the rngd service file to remove -d.

Comment 3 Artem 2019-04-01 13:14:33 UTC
> And attach them both.

Will do. But probably last kernel-5.0.5 update fixed this because i haven't this issue on my PC and in VM too.

Comment 4 Neil Horman 2019-04-01 13:36:06 UTC
then I'll close this, and you can reopen if the problem re-appears