Bug 1639840 - Kernel after 4.18.10-200.fc28.x86_64 waits for random entropy on boot
Summary: Kernel after 4.18.10-200.fc28.x86_64 waits for random entropy on boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-16 17:51 UTC by Michael Convey
Modified: 2019-12-06 18:15 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-17 20:03:34 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Michael Convey 2018-10-16 17:51:46 UTC 
Fedora (currently, kernel 4.18.12-200.fc28.x86_64) waits for random entropy on boot. This is nearly 100% reproducible after a kernel update. 

Steps to Reproduce:
1. Update kernel
2. On reboot, after kernel selection screen, workstation hangs/waits indefinitely.
3. Force hard reboot multiple times. Each time, after kernel selection screen, I tap many keys to attempt to meet entropy requirement. Often takes more than four hard reboots to successfully complete start-up processes.

This is a follow-up to this closed bug: https://bugzilla.redhat.com/show_bug.cgi?id=1572916

I'm not able to access this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1593843
Comment 1 Maciej Żenczykowski 2019-01-26 00:38:37 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=1572944 is also relevant about previous such issues.
Comment 2 Justin M. Forbes 2019-01-29 16:24:35 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.
Comment 3 Michael Convey 2019-01-29 16:53:42 UTC 
I upgraded to Fedora 29 and I'm still having this issue, so I changed the version to Fedora 29
Comment 4 Maciej Żenczykowski 2019-01-30 05:53:16 UTC 
Could you perhaps clarify what sort of hardware this is on?
VM?
Architecture?
cpu?
cat /proc/cpuinfo
ssd? hdd?
Comment 5 Laura Abbott 2019-04-09 20:44:35 UTC 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora XX has now been rebased to 5.0.6  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30.
 
If you experience different issues, please open a new bug report for those.
Comment 6 Justin M. Forbes 2019-09-17 20:03:34 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Comment 7 Michael Convey 2019-12-06 18:15:27 UTC 
Got tired of Fedora's bugs and switched to a different distribution.
Note You need to log in before you can comment on or make changes to this bug.