[Voyage-linux] daily-build 6/05 - cant log in

[Jim Cromie]

having just updated desktop to a distro with an up-to-date udev,
Ive finally been able to write a voyage image to CF that boots.
Other attempts always broke at grub stage 1.5 I think ;
it was early enough to not get any error msg

(Ive been using a good image written to an older & smaller CF
back in Nov, 11 - newer udev in new desktop distro deals better
with some obscure flags displayable by udisks iirc)

Login appears to work (no password incorrect msg), but throws me
right back to the prompt. Ssh also doesnt work.
Needless to say, I cant login to see whats going on.

voyage login: root
Password:
Last login: Wed Jun  6 00:52:23 GMT 2012 on ttyS0
Linux voyage 3.2.17-voyage #1 SMP PREEMPT Mon May 14 01:36:16 HKT 2012 i586

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
 __  __
 \ \/ /___ __  __ ___  ___  ___    Useful Commands:
  \  // _ \\ \/ /,-_ |/ _ |/ -_)     remountrw - mount disk as read-write
   \/ \___/ \  / \___,\_  |\___|     remountro - mount disk as read-only
           _/_/        _'_|          remove.docs - remove all docs and manpages
     { V o y a g e } - L i n u x
      < http://linux.voyage.hk >   Version: 0.8 (Build Date 20120605)



Debian GNU/Linux 6.0 voyage ttyS0

voyage login: [  322.254030] run-parts[1735]: segfault at bf9c55b9 ip
b77013f8 sp bfe702a4 error ffff0004 in libc-2.11.3.so[b7650000+13e000]
[  322.492622] run-parts[1740]: segfault at bf9c55b9 ip b77243f8 sp
bff4bf54 error ffff0004 in libc-2.11.3.so[b7673000+13e000]




So, Im wondering if anyone recognizes this error, or can outline
what to do to find out what those hex numbers are -

this is on an i586 class box - soekris 4801,
is voyage built with i386 or i686 ??

Im gonna try checksumming everything on the CF now,
and see if they match up against whats in the distro tree on my desktop,
Also will objdump libc, and see if I can find those addys there.