| Summary: | kernel hangs on boot with Fedora 25 Kernel: Fatal: no entropy gathering module detected | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mauro Carvalho Chehab <mchehab> | ||||||||||
| Component: | dracut | Assignee: | dracut-maint-list | ||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 25 | CC: | cz172638, dracut-maint-list, gansalmon, hanspetersorge, harald, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mattdm, mchehab, rockonthemoonfm, zbyszek | ||||||||||
| 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: | 2017-12-12 10:25:24 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: | |||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1223107 [details]
partial stack dump with FC25 Kernel
Created attachment 1223131 [details]
dmesg with Kernel 4.8.8.fc25 (boot hangs)
Same problem with most recent version 4.8.15-300.fc25.x86_64 - After upgrade from 4.8.13-100.fc23.x86_64 (Booting from 4.8.13-100.fc23.x86_64 is still OK) - Booting from ssd on (/dev/sdc1) fstab: UUID=8fccab7a-f34f-4148-a360-a610db920919 /boot HW: CPUs: 2, processors 24 cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 63 model name : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz stepping : 2 microcode : 0x38 cpu MHz : 1200.146 cache size : 15360 KB physical id : 0 ... Additional Comments - entries from journalctl: From failed boot with 4.8.15-300.fc25.x86_64: ..... kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. kernel: usb 3-7: new high-speed USB device number 2 using xhci_hcd Fatal: no entropy gathering module detected In comparison to a regular boot with 4.8.13-100.fc23.x86_64: ..... kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. kernel: usb 3-7: new high-speed USB device number 2 using xhci_hcd kernel: random: systemd: uninitialized urandom read (16 bytes read) ...... Remark: There are multiple journalctl entries (however the file exists): Libgcrypt error: integrity check using `/lib64/.libgcrypt.so.20.hmac' failed: No such file or directory Hans-Peter Temporary solution:
1: dnf remove dracut-fips
2: cd /boot
3: dracut alt-4.8.15-300.fc25.x86_64 4.8.15-300.fc25.x86_64
4: mv initramfs-4.8.15-300.fc25.x86_64.img initramfs-4.8.15-300.fc25.x86_64.IMG
# just in case - it's open heart surgeory
5: mv alt-4.8.15-300.fc25.x86_64 initramfs-4.8.15-300.fc25.x86_64.img
6: you want to use your actual kernel-version
7: reboot
No more journalctl entries for:
Libgcrypt error: integrity check using `/lib64/.libgcrypt.so.20.hmac' failed: No such file or directory
Further readings:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/sect-Security_Guide-Federal_Standards_And_Regulations-Federal_Information_Processing_Standard.html
*********** MASS BUG UPDATE ************** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. The same issue still happens with Kernel 4.9.5. There's a difference, though: with Kernel 4.9.5, both F24 and F25 versions crash at boot time. Created attachment 1244800 [details]
dmesg with Kernel 4.9.5.fc24 (boot hangs)
Could it be some issue with systemd and glibc-2.24? It seems that the init task is crashing: [ 6.590787] traps: init[1] general protection ip:7f8b1e931642 sp:7fff0be5f130 error:0[ 6.600883] in libc-2.24.so[7f8b1e8fa000+1bd000] [ 6.607739] random: fast init done [ 6.612877] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b 6.623076] CPU: 0 PID: 1 Comm: init Not tainted 4.9.5-100.fc24.x86_64 #1 [ 6.630651] Hardware name: Dell Inc. PowerEdge T620/0F5XM3, BIOS 2.5.2 01/28/2015 [ 6.639002] ffff9dd3818b3c38 ffffffff8d3f40bd ffff8cc83606bd00 ffffffff8dc39ec8 [ 6.647302] ffff9dd3818b3cc0 ffffffff8d1bfb38 ffff8cc800000010 ffff9dd3818b3cd0 [ 6.655595] ffff9dd3818b3c68 00000000dad3e9f2 ffff8cc83606bd00 000000000000000b [ 6.663888] Call Trace: [ 6.666625] [<ffffffff8d3f40bd>] dump_stack+0x63/0x86 [ 6.672364] [<ffffffff8d1bfb38>] panic+0xe4/0x22d [ 6.677712] [<ffffffff8d0a6e51>] do_exit+0xaf1/0xb00 [ 6.683349] [<ffffffff8d0a6ee7>] do_group_exit+0x47/0xb0 [ 6.689376] [<ffffffff8d0b2369>] get_signal+0x289/0x630 [ 6.695308] [<ffffffff8d026067>] do_signal+0x37/0x690 [ 6.701041] [<ffffffff8d0ce7d0>] ? wake_up_state+0x10/0x20 [ 6.707259] [<ffffffff8d0afc45>] ? signal_wake_up_state+0x25/0x30 [ 6.714155] [<ffffffff8d0afd7d>] ? complete_signal+0xfd/0x1e0 [ 6.720664] [<ffffffff8d0b070e>] ? send_signal+0x3e/0x80 [ 6.726690] [<ffffffff8d003286>] exit_to_usermode_loop+0x76/0xb0 [ 6.733491] [<ffffffff8d003af0>] prepare_exit_to_usermode+0x40/0x50 [ 6.740585] [<ffffffff8d81d62f>] retint_user+0x8/0x10 [ 6.746390] Kernel Offset: 0xc000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 6.762504] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b (In reply to H.-P. Sorge from comment #4) > Temporary solution: > > 1: dnf remove dracut-fips Yeah, a workaround is to remove dracut-fips and re-creating initramfs with: dracut --force /boot/initramfs-4.9.5-100.fc24.x86_64.img 4.9.5-100.fc24.x86_64 dracut --force /boot/initramfs-4.9.5-100.fc25.x86_64.img 4.9.5-100.fc25.x86_64 Made both f24 and f25 Kernels to boot. There's something really wrong with dracut-fips and newer Kernels build. Yes, I think this is a known issue with dracut. I think this has been reported elsewhere but I can't remember what the bug is to duplicate to. ok, kernel panic introduced in my machine by kernel 4.11.6, then 4.11.7. Fatal: no entropy gathering module detected if in next upgrade it wan't be fixed, Fedora install will be bricked since dnf scripts will automatically uninstall probably the last working kernel.. > Yeah, a workaround is to remove dracut-fips and re-creating initramfs
worked. I'd like to encrypt my initram tough.
(In reply to rockonthemoonfm from comment #11) > if in next upgrade it wan't be fixed, Fedora install will be bricked since > dnf scripts will automatically uninstall probably the last working kernel.. You can breathe easy on this point, at least. DNF will always preserve the currently running kernel. (In reply to rockonthemoonfm from comment #12) > > Yeah, a workaround is to remove dracut-fips and re-creating initramfs > > worked. I'd like to encrypt my initram tough. dracut-fips does NOT encrypt the initramfs! The only thing dracut-fips does, is to load the crypto modules and lock them. Also *.hmac validation of some libraries is done in the running system. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |
Created attachment 1223105 [details] dmesg with Kernel 4.8.8.fc24 (boots OK) Booting Fedora 25 on a Dell T.620 machine makes it hang on a very early state ( after 3.9 seconds - close to TSC initialization), with Kernel 4.8.8-300.fc25.x86_64. The same issue also happens with Kernel 4.8.7-300.fc25.x86_64. Fedora boots fine if I use, instead, Kernel 4.8.8-200-fc24.