Kernel upgrade fails (with a kernel panic upon reboot) after installing from the 2017.10 "Goedel" release and/or upgrading linux from 4.12.4-1 to 4.16.6-2
Edit by @totte:
Installing Chakra from the 2017.10 "Goedel" release, and then running
pacman -Syu followed by rebooting will lead to a kernel panic, like so:
[ 0.682627] Failed to execute /init (error -2) [ 0.682777] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. [ 0.682832] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.16.6-2-CHAKRA #2 [ 0.682875] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./IMB-A180, BIOS P1.00 10/09/2013 [ 0.682921] Call Trace: [ 0.682974] dump_stack+0x5c/0x85 [ 0.683015] ? rest_init+0x50/0xd0 [ 0.683057] panic_0xe4/0x253 [ 0.683101] ? do_execveat_common.isra.39+0x87/0x830 [ 0.683142] ? rest_init+0xd0/0xd0 [ 0.683185] kernel_init+0xeb/0x100 [ 0.683228] ret_from_fork+0x22/0x40 [ 0.683305] Kernel Offset: 0xa000000 from 0xffffffff81000000 (reloaction range: 0xffffffff80000000-0xffffffffbfffffff) [ 0.683354] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. _
See this comment below for a workaround.
Original report follows below the horizontal line.
Installed from Goedel live media. After initial pacman -Syu upgrade, had kernel panic on next restart with no init found, as described by this user: https://community.chakralinux.org/t/kernel-panic-after-update/7752 Hardware info attached. hwinfo