Description of problem: After upgrading from F24 to F25 (running inside a VirtualBox VM), the new kernel panics with: ================================== Fatal: [ 1.783786] traps: init[1] general protection ip:b72db13b sp:bfb30c40 error:0no entropy gathering module detected in libc-2.24.so[b72ab000+1d4000] [ 1.788570] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 1.788570] [ 1.791385] CPU: 0 PID: 1 Comm: init Tainted: G W 4.8.8-300.fc25.i686+PAE #1 [ 1.796762] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 1.799887] c7a3a967 82eedaf0 00000086 f54d5dec c735cb40 f5511100 f551eae0 f54d5e04 [ 1.823340] c717158a f551eae0 f55111c0 f551eae0 f55111c0 f54d5e58 c70703ba c793fe30 [ 1.829579] 0000000b f49d01bc f5511680 00000000 f55116c0 f55111c0 f55111c0 01000000 [ 1.832609] Call Trace: [ 1.833365] [<c735cb40>] dump_stack+0x58/0x78 [ 1.834393] [<c717158a>] panic+0x94/0x1c2 [ 1.835334] [<c70703ba>] do_exit+0xa1a/0xa20 [ 1.836302] [<c7070437>] do_group_exit+0x37/0xa0 [ 1.837966] [<c707b228>] get_signal+0x258/0x600 [ 1.839671] [<c7071ace>] ? irq_exit+0x6e/0xb0 [ 1.840648] [<c7022139>] do_signal+0x29/0x530 [ 1.842300] [<c7078e68>] ? signal_wake_up_state+0x28/0x30 [ 1.843445] [<c7078f7d>] ? complete_signal+0xed/0x1e0 [ 1.844502] [<c70798fb>] ? send_signal+0x3b/0x70 [ 1.845509] [<c707a083>] ? force_sig_info+0xa3/0xc0 [ 1.846617] [<c70030e4>] exit_to_usermode_loop+0x94/0xe0 [ 1.863051] [<c7022d70>] ? do_error_trap+0x120/0x120 [ 1.864116] [<c7003608>] prepare_exit_to_usermode+0x18/0x20 [ 1.865231] [<c77578d6>] resume_userspace+0xe/0x13 [ 1.866651] Kernel Offset: 0x6c00000 from 0xc0400000 (relocation range: 0xc0000000-0xf7ffdfff) [ 1.868905] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ================================== Version-Release number of selected component (if applicable): kernel-4.8.8-300.fc25.i686+PAE How reproducible: Always Steps to Reproduce: 1. Boot first GRUB entry 2. Kernel boots 3. panic Actual results: Panic Expected results: No panic Additional info: Choosing a different kernel (4.8.8-200.fc24.i686+PAE from F24) in the same VM works just fine. The GRUB menu offers the following: fedora0# ls -gotr /boot/vmlinuz-* -rwxr-xr-x. 1 5820992 May 29 2015 /boot/vmlinuz-0-rescue-147df37cc2f5475ba91a411b20f06412 -rwxr-xr-x. 1 6299920 Oct 20 07:56 /boot/vmlinuz-4.7.9-200.fc24.i686+PAE -rwxr-xr-x. 1 6399184 Nov 15 10:48 /boot/vmlinuz-4.8.8-300.fc25.i686+PAE <== b0rked -rwxr-xr-x. 1 6399184 Nov 15 12:25 /boot/vmlinuz-4.8.8-200.fc24.i686+PAE Also, just before the panic, the kernel warns about "x86/mm: Found insecure W+X mapping at address", but these warnings show up in 4.8.8-200.fc24.i686+PAE too and the kernel continues to boot.
Created attachment 1224737 [details] dmesg
This isn't a kernel error per se but most likely a problem with the initrd. Can you share the output of lsinitrd?
Created attachment 1226621 [details] lsinitrd initramfs-4.8.10-300.fc25.i686+PAE.img
Created attachment 1226622 [details] lsinitrd initramfs-4.8.8-200.fc24.i686+PAE.img
I've attached two "lsinitrd" outputs to this bug, as they were too big to paste. I uninstalled the FC25 kernels and re-installed kernel-PAE-4.8.10-300.fc25.i686, so it would re-generate the initrd, but booting still fails with the same message. kernel-PAE-core-4.8.8-200.fc24.i686 still works. $ sha1sum /boot/vmlinuz-4.8.* 516cc4f4c3f0d483273ef6f5e9a163d66c15297c /boot/vmlinuz-4.8.10-300.fc25.i686+PAE fb3283200a04d21b4b9f0dde075d7b5569b37f35 /boot/vmlinuz-4.8.8-200.fc24.i686+PAE Again, this is all in a VirtualBox 5.0.30 virtual machine and since nobody else seems to complain, this may or may not be related to that fact.
*********** 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.
Upgrading to 4.9.3-200.fc25 did not help, same error. The only bootable kernel remains 4.8.8-200 on this system.
*********** 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.10.9-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.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.