Ask Your Question

Hard reboot during upgrade to Fedora 24; now kernel panic

asked 2016-06-22 07:40:47 -0500

DMH gravatar image

Last night I tried to upgrade from Fedora 23 to Fedora 24 using the dnf system-upgrade method.

When the system rebooted, it appeared to hang during the boot, so I did a hard reboot by holding down the power button. (This was not my smartest moment.)

Now when I try to boot the system, I get something like the following:

    Starting Switch Root
systemd-journald[186]: Received SIGTERM from PID 1 (systemd).
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

[12...] CPU: 0 PID: 1 Comm: systemd Not tainted #1
[...] Hardware name: ...
[...] #
[...] #
[...] #
[...] Call Trace
[...] # dump_stack
[...] # panic
[...] # do_exit
[...] # do_group_exit
[...] # SyS_exit_group
[...] # entry_SYSCALL_64_fastpath
[...] Kernel Offset: disabled
[...] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

Where I am using # to represent the hexadecimal numbers printed as part of the trace and ellipses to represent other (non-essential?) detail.

Grub shows boot options for Fedora 23 with the following kernels:

  • 4.5.5-201
  • 4.5.6-200
  • 4.5.7-200

As well as a "rescue" option, but I get the same kernel panic message no matter which I try to boot.

Is there a way to recover from this without wiping the partition and re-installing from scratch? My current plan is to copy all my data, since I can still boot into Windows and access the Fedora partition just fine, and do the re-install, but I am hoping there's a better solution

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2016-06-22 15:20:51 -0500

jexner gravatar image

Very similar issue here. I did NOT hard-reset. Just followed the upgrade, and then it rebooted itself and kernel panicked.

I tried booting a live Fedora and setting SELINUX=permissive to no avail.

edit flag offensive delete link more


Does your kernel panic also relate to systemd? At what point in the boot process does it panic? Mine is every time it reaches "Starting Switch Root".

DMH gravatar imageDMH ( 2016-06-22 18:30:23 -0500 )edit

Same here. I see the exact same message.

jexner gravatar imagejexner ( 2016-06-22 23:50:48 -0500 )edit

I just tried installing debian on the system, and I get the same kernel panic (well, it complains about "init Not tainted" rather than "systemd Not tainted").

How can that even be?

jexner gravatar imagejexner ( 2016-06-26 13:44:02 -0500 )edit

Question Tools

1 follower


Asked: 2016-06-22 07:40:47 -0500

Seen: 803 times

Last updated: Jun 22 '16