#22 dracut-fips may be causing kernel panic in F25
Closed: Fixed Opened by miabbott.

After doing a compose of F25 AH with commit 4633217, I see the following packages added:

Added:
  dracut-fips-044-77.fc25.x86_64
  hmaccalc-0.9.14-4.fc24.x86_64

When I rebooted into the compose that included those files, I saw the following kernel panic on the console

Fatal: no entropy gathering module detected
[    1.065689] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    1.065689]
[    1.066568] CPU: 0 PID: 1 Comm: init Not tainted 4.8.0-0.rc7.git0.1.fc25.x86_64 #1
[    1.067455] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.1-1.fc24 04/01/2014
[    1.069326]  0000000000000086 000000007f9cf7c5 ffff9ffbbd3f7c20 ffffffffb43e55ad
[    1.071354]  ffff9ffbbc899e00 ffffffffb4c312b8 ffff9ffbbd3f7ca8 ffffffffb41b616c
[    1.072861]  ffffffff00000010 ffff9ffbbd3f7cb8 ffff9ffbbd3f7c50 000000007f9cf7c5
[    1.074329] Call Trace:
[    1.074741]  [<ffffffffb43e55ad>] dump_stack+0x63/0x86
[    1.075524]  [<ffffffffb41b616c>] panic+0xe4/0x226
[    1.076246]  [<ffffffffb40a5430>] do_exit+0xb10/0xb10
[    1.076876]  [<ffffffffb40a54b7>] do_group_exit+0x47/0xb0
[    1.077677]  [<ffffffffb40b08c9>] get_signal+0x289/0x630
[    1.078474]  [<ffffffffb4026077>] do_signal+0x37/0x6b0
[    1.079258]  [<ffffffffb40cc090>] ? wake_up_state+0x10/0x20
[    1.080079]  [<ffffffffb40ae18a>] ? signal_wake_up_state+0x2a/0x30
[    1.080983]  [<ffffffffb40ae2c0>] ? complete_signal+0x100/0x1f0
[    1.081882]  [<ffffffffb40aec5e>] ? send_signal+0x3e/0x80
[    1.082679]  [<ffffffffb400329c>] exit_to_usermode_loop+0x8c/0xd0
[    1.083877]  [<ffffffffb4003b38>] prepare_exit_to_usermode+0x38/0x40
[    1.085091]  [<ffffffffb4801c6f>] retint_user+0x8/0x10
[    1.086254] Kernel Offset: 0x33000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    1.088023] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    1.088023]

I tried booting with fips=1 and met the same issue.


We backed out the fips.

@walters changed the status to Fixed

Metadata