[Solved] Pogo E02 Kernel Panic moving to Linux-kirkwood

[technosf]

Updated uboot to davy gravy and rolled out linux-kirkwood to my usbssd in a two partition layout. Pogo complains though - I think I'm missing an init param I need to set with fw_setenv.

Any ideas?

$this->bbcode_second_pass_code('', 'Loading file "/boot/uImage" from usb device 0:1 (usbda1)
3688208 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.11.4-3-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3688144 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 20.217259] rtc-mv rtc-mv: internal RTC not ticking
[ 21.070704] sd 0:0:0:0: [sda] No Caching mode page found
[ 21.076065] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 21.098948] sd 0:0:0:0: [sda] No Caching mode page found
[ 21.104289] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 21.136199] sd 0:0:0:0: [sda] No Caching mode page found
[ 21.147279] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 23.608659] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 33.620913] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 33.633406] CPU: 0 PID: 1 Comm: swapper Not tainted 3.11.4-3-ARCH #1
[ 33.639812] [<c000e124>] (unwind_backtrace+0x0/0xf0) from [<c000ba4c>] (show_stack+0x10/0x14)
[ 33.648389] [<c000ba4c>] (show_stack+0x10/0x14) from [<c04cd9f4>] (panic+0x88/0x1dc)
[ 33.656170] [<c04cd9f4>] (panic+0x88/0x1dc) from [<c04cbbf4>] (kernel_init+0xc0/0xe4)
[ 33.664043] [<c04cbbf4>] (kernel_init+0xc0/0xe4) from [<c0009370>] (ret_from_fork+0x14/0x24)')

The environment is:
$this->bbcode_second_pass_code('', '-sh-3.2# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_i
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rei
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd;i
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage e
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0i
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:00:A5:64
arcNumber=2998')

[technosf]

Solved.

I noticed the nand param usb_root pointed to /dev/sda1 - changed that to /dev/sda2 (because I split /boot and / to different devices) and everything boots fine.

This broke after I upgraded uBoot and then moved to linux-kirkwood. Before, when I initially moved to separate boot/root I hadn't touched usb_root (if it existed in prior uBoots) - Setting usb_scan_1 etc. was supposed to identify the rootfs.

Now I'm guessing that either the newer uBoot passes in usb_root to the kernel when it didn't before, or the kernel looks for usb_root where it didn't before.

Either-way - that's a new step in the pre-flight check.