port-evbarm/48337: non-EABI5 armeb userland fails in -current

[jakllsch%kollasch.net@localhost]

>Number:         48337
>Category:       port-evbarm
>Synopsis:       non-EABI5 armeb userland fails in -current
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-evbarm-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 23 17:35:00 +0000 2013
>Originator:     Jonathan A. Kollasch
>Release:        NetBSD 6.99.24
>Organization:
>Environment:
        
        
System: NetBSD 6.99.24 NetBSD 6.99.24 (NSLU2) #25: Wed Oct 23 11:59:29 CDT 2013 
jakllsch%trantor.kollasch.net@localhost:/raid0i/jakllsch/NetBSD/obj-evbearmeb/sys/arch/evbarm/compile/NSLU2
 evbarm
Architecture: earmeb
Machine: evbarm
>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.
>Fix:
unknown.

>Unformatted: