Re: Unable to boot NetBSD on Linksys NSLU2 (armbe / armv5tel)

[Eddy Petrișor <eddy.petrisor%gmail.com@localhost>]

2015-02-20 0:35 GMT+02:00 Eddy Petrișor <eddy.petrisor%gmail.com@localhost>:
> Hello,
>
> (Please excuse if I use unappropriate terminology, I have years of
> experience with Linux - even embedded Linux - but this is my first
> time trying to run NetBSD.)
>
> Following the great instructions found on the wiki[1] and doing a few
> tweaks here and there (IPL 2.4, using dnsmasq on the server) I have
> managed to build and setup things so that netbsd tries to start
> diskless (root on NFS) on one of my old Linksys NSLU2-s but it fails
> right when the kernel should start /sbin/init, or at least that's what
> I understand from the messages:
>
> [..]
> npe0: link state DOWN (was UNKNOWN)
> npe0: link state UP (was DOWN)
> nfs_boot: DHCP next-server: 192.168.77.250
> nfs_boot: my_name=kinder
> nfs_boot: my_domain=eddyp.homeunix.net
> nfs_boot: my_addr=192.168.77.251
> nfs_boot: my_mask=255.255.255.0
> nfs_boot: gateway=192.168.77.1
> root on 192.168.77.250:/export/netbsd-nslu2/root
> root time: 0x54e3d162
> kern.module.path=/stand/evbarm/7.99.4/modules
> init: copying out path `/sbin/init' 11
> 1.1(init): trap: signo=11 code=2 addr=0x40045d4d trap=0x17
> r0=40045d4d r1=4003f1bc r2=40045d51 r3=00000049
> r4=40050c55 r5=40050e3c r6=40045d4d r7=4003f224
> r8=00000007 r9=bfffd6a8 rA=400511b8 rB=bfffd678
> ip=00000073 sp=bfffd628 lr=40037b70 pc=4003d1b0 spsr=00000010
> Process (pid 1) got sig 11
> 1.1(init): trap: signo=11 code=2 addr=0x40045d4d trap=0x17
> r0=40045d4d r1=4003f1bc r2=40045d51 r3=00000049
> r4=40050c55 r5=40050e3c r6=40045d4d r7=4003f224
> r8=00000007 r9=bfffd6a8 rA=400511b8 rB=bfffd678
> ip=00000073 sp=bfffd628 lr=40037b70 pc=4003d1b0 spsr=00000010

Trying to go back in history looking for a working version, and after
talking to people on #netbsd on Freenode, I built a version from Oct 13, 2013:

commit 0a546fdcf7f6382275ac3aacd97163f9d7daaf2e (HEAD, nslu2-test)
Author: skrll <skrll>
Date:   Wed Oct 16 07:34:20 2013 +0000

    Apply patch from PR/48310 - kue(4) cannot receive multicast packets.

The result is different with this version, but still the system hasn't
reached the login:

[..]
nfs_boot: my_name=kinder
nfs_boot: my_domain=eddyp.homeunix.net
nfs_boot: my_addr=192.168.77.251
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.77.1
root on 192.168.77.250:/export/netbsd-nslu2/root
root time: 0x54fb349b
WARNING: clock lost 5545 days
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init: copying out path `/sbin/init' 11
exec /sbin/init: error 8
init: copying out path `/sbin/oinit' 12
exec /sbin/oinit: error 2
init: copying out path `/sbin/init.bak' 15
exec /sbin/init.bak: error 2
init: copying out path `/rescue/init' 13
exec /rescue/init: error 8
init path (default /sbin/init):

And there is no interaction possible via the serial console. Is it
normal at this point the serial console not to be enabled at this
point, or is it something wrong in my setup/serial adapter?

The full boot log is here:

http://pastebin.com/KvctkBLe

> Is there a way to get a more detailed trace or even connect to the
> target via the serial console to debug what's happening?
> Is there a way to get more detailed information?
> Is it possible to debug an ARM NetBSD with a Linux amd64/x86_64
> host/remote? If so, how?

-- 
Eddy Petrișor