linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+

[Georgi Georgiev]

I was happily running my Raspberry Pi 3 B+ with linux-image-5.0.0-1012-raspi2, then upgraded to linux-image-5.0.0-1013-raspi2 and now my system does not boot with the last message as:

---[ end kernel panic - not syncing: Attempted to kill init! exitcode 0x00000100 ]----

Lots of other errors on the screen, but I am having a hard time getting a netconsole or anything to dump these errors somewhere readable. All I can do is attach a screenshot, and maybe type up a few of them.

Reverting to 5.0.0-1012 is ok.

/init: line 263: log_end_msg: not found
/init: line 265: maybe_break: not found
/init: line 266: log_begin_msg: not found
(skip more of this)
/init: line 299: log_end_msg: not foudn
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
(repeat last line three more times)
/init: line 323: panic: not found
/init: line 325: maybe_break: not found
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
/init: line 359: can't open /root/dev/console: no such file
[ 36.246460] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 36.256383] CPU: 0 PID: 1 Comm: init Tainted: G B 5.0.0-1013-raspi2 #13-Ubuntu
[ 36.262133] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (D)T
[ 36.278383] Call trace:
(skip the rest)

[Khaled El Mously (kmously)]

Sorry to hear that @Georgi

It's a strange problem to have. That kernel worked fine in all our pre-release testing. Certainly _booting_ shouldn't be a problem.

Could there be some other root-cause for this problem? (e.g. filesystem corruption or bad install or changes in /etc/fstab or new hardware added/removed, etc.)

Are you able to boot the prior kernel again without issues?

[Khaled El Mously (kmously)]

@Georgi, I just noticed your comment "Reverting to 5.0.0-1012 is ok.", please ignore my last question.

I'm seeing if I can reproduce your problem on a Rpi3b+