AVILA getting close!

[John Hay]

On Wed, Jun 18, 2014 at 04:14:51PM -0700, John-Mark Gurney wrote:
> Nathan Whitehorn wrote this message on Wed, Jun 18, 2014 at 16:09 -0700:
> > 
> > On 06/18/14 15:58, John-Mark Gurney wrote:
> > >So, w/ the recent couple of patches that alc has provided, I no longer
> > >receive kernel panics on my AVILA board!
> > >
> > >$ uname -a
> > >FreeBSD avila.funkthat.com 11.0-CURRENT FreeBSD 11.0-CURRENT #27 
> > >r267333:267349M: Wed Jun 11 09:57:58 PDT 2014     
> > >jmg at carbon.funkthat.com:/usr/obj/arm.armeb/usr/src.avila/sys/AVILA  arm
> > >$ uptime
> > >12:15AM  up 1 day, 15 mins, 2 users, load averages: 0.13, 0.11, 0.08
> > >
> > >This survived a portsnap extract...  This is all over NFS...
> > >
> > >Though the issue that I'm now having is that some binaries (newsyslog)
> > >and sometimes other binaries (awk, grep) core dump...
> > >
> > >I believe this is an issue w/ rtld, or related...  If I compile newsyslog
> > >-static, it works fine...  Otherwise I get a SIGILL, and that is
> > >because it jumps off into the weeds..  Though gdb on arm isn't very
> > >useful..
> > >
> > >The trouble appears to be when resolving a symbol that hasn't been
> > >called yet...  The trouble starts when newsyslog starts parsing a
> > >line that isn't a comment line and tries to strdup it...  stepi'ing
> > >has me go into
> > >_rtld_bind_start ->
> > >	_rtld_bind ->
> > >		rlock_acquire ->
> > >			thread_mask_set ->
> > >				def_thread_set_flag (via function pointer)
> > >			def_rlock_acquire ->
> > >				atomic_add_acq_int
> > >
> > >Turning on rtld's debug doesn't tell me anything I didn't know already:
> > >"memchr" in "libc.so.7" ==> 0x2017af30 in "libc.so.7"
> > >"strdup" in "newsyslog" ==> 0x200cc8b0 in "libc.so.7"
> > >Bus error (core dumped)
> > >
> > >I've posted both a gdb log showing the stepi, and my copy of
> > >ld-elf.so.1 to:
> > >https://www.funkthat.com/~jmg/20140619/
> > >
> > >Let me know if there is any additional information...
> > >
> > What happens if you set LD_BIND_NOW=1 in the environment first?
> 
> That causes newsyslog to work.

Yes, that fix it for me too. On my box newsyslog seemed to crash early
when it called getuid(). But I'm not nfs booting, but from a CF card.
I still need "vfs.unmapped_buf_allowed=0" set in the env to have md
ramdisks work for /var and /etc though. With this the box boot to
multi-user. Now to see if all of this fixed the CAMBRIA boards too
and starting to test the Atheros cards.

Thanks to all for helping this along.

Regards

John
-- 
John Hay -- jhay at meraka.csir.co.za / jhay at meraka.org.za