Hi,
I'm experimenting with options to setup a headless Pi 5 with empty NVMe. I've configured BOOT_ORDER to include 7 (HTTP boot) plugged in LAN and power and am monitoring the boot process via a debug probe on the UART port. Download and boot of the net_install/boot.img works well but when on the login prompt it immediately kernel panics:
You can find a full boot log at in a Gist here: https://gist.github.com/tbussmann/92c4a ... 4473500d5c
I'm not sure, of text-mode use of the rpi-imager is supported, but I wouldn't expect a kernel panic of the buildroot system.
Is there anything I can do to trace this down, is this already known or even expected behaviour?
TIA!
I'm experimenting with options to setup a headless Pi 5 with empty NVMe. I've configured BOOT_ORDER to include 7 (HTTP boot) plugged in LAN and power and am monitoring the boot process via a debug probe on the UART port. Download and boot of the net_install/boot.img works well but when on the login prompt it immediately kernel panics:
Code:
NOTICE: BL31: v2.6(release):v2.6-240-gfc45bc492NOTICE: BL31: Built : 12:55:13, Dec 4 2024Starting rpi-imagerWelcome to Buildrootbuildroot login: [ 1.606686] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00008600[ 1.614378] CPU: 3 PID: 1 Comm: init Not tainted 6.6.31-imager #1[ 1.620493] Hardware name: Raspberry Pi 5 Model B Rev 1.1 (DT)[ 1.626344] Call trace:[ 1.628791] dump_backtrace+0x90/0xe8[ 1.632464] show_stack+0x18/0x24[ 1.635786] dump_stack_lvl+0x48/0x60[ 1.639458] dump_stack+0x18/0x24[ 1.642778] panic+0x31c/0x370[ 1.645838] do_exit+0x790/0x87c[ 1.649072] do_group_exit+0x34/0x90[ 1.652655] __wake_up_parent+0x0/0x2c[ 1.656413] invoke_syscall.constprop.0+0x50/0xec[ 1.661131] do_el0_svc+0x40/0xc4[ 1.664451] el0_svc+0x48/0x148[ 1.667598] el0t_64_sync_handler+0x120/0x12c[ 1.671966] el0t_64_sync+0x190/0x194[ 1.675636] SMP: stopping secondary CPUs[ 1.679567] Kernel Offset: 0x1004000000 from 0xffffffc080000000[ 1.685505] PHYS_OFFSET: 0x0[ 1.688388] CPU features: 0x0,00000001,70028143,0000720b[ 1.693716] Memory Limit: none[ 1.696776] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00008600 ]---I'm not sure, of text-mode use of the rpi-imager is supported, but I wouldn't expect a kernel panic of the buildroot system.
Is there anything I can do to trace this down, is this already known or even expected behaviour?
TIA!
Statistics: Posted by tbussmann — Sat Mar 29, 2025 6:04 pm — Replies 2 — Views 66