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:

[..]

> 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

I have found PR #48337 (reported on 23rd of Oct 2013 against 6.99.24)
which seems (to me) to be refering to this exact problem:

> >Description:
> non-EABI5 userland fails to run on evbarmeb.
>
> as soon as /sbin/init loads the kernel starts spewing
>
> Process (pid 1) got sig 11
>
> The only kernel/userland combinations that work involve using a EABI5 userland.
> Obviously adding COMPAT_NETBSD32 for the-other-ABI support was necessary to test
> this.  A non-COMPAT_NETBSD32,non-EABI5 kernel fails the same way with a non-EABI5 userland.
>
> Additionally, a netbsd-5-1 userland works on a -current non-EABI5 kernel, so something in userland changed.
>
> >How-To-Repeat:
> build NetBSD/evbarm for armeb for the NSLU2,  try to use userland.
> compare with NetBSD/evbarm for earmeb on same hardware.


Could somebody more knowledgeable than me on NetBSD stuff confirm this
is the same issue?

> I tried to confirm that the problem is indeed with the filesystem by

Since now I have netbsd_6_1 booting, I suppose trying to combine the
6.1 userland with the trunk kernel should (in theory) work. Is this
correct or am I missing some tighter coupling between the kernel and
the userland?

-- 
Eddy