Re: kernel panic when booting netbsd head on rockpi4c

[John Klos <john%ziaspace.com@localhost>]

> > > I've unsuccessfully tried to boot netbsd head from nvme on my
> > > rockpi4c. I didn't see anything output via HDMI when booting but maybe
> > > thats not surprising because the crash seems to be due to rkdrm.
> > > Hopefully there is a netbsd developer on this list who might be able
> > > to look into this?
> > >
> > > U-Boot TPL 2020.10-armbian (Aug 08 2021 - 18:04:16)
> >
> > We only "support" u-boot from pkgsrc and DTBs from base.  The DTBs
> > especially need to match the kernel version.

The issue isn't u-boot, or at least that's not what's causing the panic, 
because recent invisible.ca images and a newly built arm64.img.gz with 
rksd_loader.img from pkgsrc panic in the same way, too, on a RockPro64.

A big endian kernel compiled with rkdrm*, rkfb* and rkvop* boots fully 
single user for me, but trying to go multi user panics with:

Updating fontconfig cache:[   3.7589405] panic: Trap: Data Abort (EL1): 
Translation Fault L0 with read access for 0000000000000000: pc 
ffffc000001795e0: ldr x5, [x2]

[   3.7589405] cpu4: Begin traceback...
[   3.7589405] trace fp ffffc000ae421740
[   3.7589405] fp ffffc000ae421770 vpanic() at ffffc000005720ec 
netbsd:vpanic+0x14c
[   3.7589405] fp ffffc000ae4217d0 panic() at ffffc000005721e4 
netbsd:panic+0x44
[   3.7589405] fp ffffc000ae421860 data_abort_handler() at 
ffffc000000adcac netbsd:data_abort_handler+0x1ec
[   3.7589405] tf ffffc000ae4218d0 el1_trap() at ffffc000000af784 
netbsd:el1_vectors+0x784
[   3.7689409] ---- trapframe 0xffffc000ae4218d0 (304 bytes) ----
[   3.7689409]     pc=ffffc000001795e0,   spsr=0000000020000005
[   3.7689409]    esr=0000000096000004,    far=0000000000000000
[   3.7689409]     x0=0000000000000000,     x1=ffffc000ae770e80
[   3.7689409]     x2=0000000000000000,     x3=0000000000000000
[   3.7689409]     x4=ffff000000ae4d20,     x5=ffff0000f5172a00
[   3.7689409]     x6=0000000000000000,     x7=ffffffffffffffff
[   3.7689409]     x8=00000000000010c0,     x9=0000000000000010
[   3.7689409]    x10=ffffc000000a3f14,    x11=0000000003b1c000
[   3.7689409]    x12=fffffffffffff000,    x13=ffffffffffffffe0
[   3.7689409]    x14=0000000000000020,    x15=ffff0000035db900
[   3.7689409]    x16=ffffc000000a3f14,    x17=0000fc48ab97bc74
[   3.7689409]    x18=0000000000001000,    x19=ffffc00000ee4b20
[   3.7689409]    x20=00,    x21=0000000000000008
[   3.7689409]    x22=ffffc0000123c00000000002,    x25=0000000000000000
[   3.7689409]    x26=00000000002,    x27=0000000000031128
[   3.7689409]    x28=00000000p=x29=ffffc000ae421c00
[   3.7689409] lr=x30=ffffc000001795c8, -------------------------------
[   3.7789427] fp ffffc000ae421c00 usb_allocmem() at ffffc000001795e0 
netbsd:usb_allocmem+0x7c
[   3.7789427] fp ffffc000ae421c60 ohci_open() at ffffc000002171d0 
netbsd:ohci_open+0x19c
[   3.7789427] fp ffffc000ae421cd0 usbd_setup_pipe_flags() at 
ffffc00000177e2c netbsd:usbd_setup_pipe_flags+0xdc
[   3.7789427] fp ffffc000ae421d20 usbd_new_device() at ffffc000001787ac 
netbsd:usbd_new_device+0x33c
[   3.7789427] fp ffffc000ae421dc0 uhub_explore() at ffffc0000017cad0 
netbsd:uhub_explore+0x5f0
[   3.7789427] fp ffffc000ae421e70 usb_discover() at ffffc0000016fc60 
netbsd:usb_discover+0xb0
[   3.7889407] fp ffffc000ae421ea0 usb_event_thread() at ffffc0000017000c 
netbsd:usb_event_thread+0x7c
address 0x100 is invalid
address 0xf0 is invalid
address 0xe8 is invalid
[   3.7889407] cpu4: End traceback...

John