Thread View: fa.netbsd.ports.alpha
5 messages
5 total messages
Started by Nadin
Sun, 02 Dec 2012 10:29
userland problem
Author: Nadin
Date: Sun, 02 Dec 2012 10:29
Date: Sun, 02 Dec 2012 10:29
33 lines
3238 bytes
3238 bytes
Hello everybody I have some weird problem with my NetBSD/alpha 6.0. The problem is that I can only run things which are originally residing in /bin. For example, my typical session looks like: # ls /bin [ csh ed ls pwd sh cat date expr mkdir rcmd sleep chio dd hostname mt rcp stty chmod df kill mv rm sync cp domainname ksh pax rmdir tar cpio echo ln ps rump.dd test # echo test test # /bin/echo test test # ls -la /bin/echo -r-xr-xr-x 1 root 0 8935 Dec 1 03:20 /bin/echo # ls -la /usr/bin/cc -r-xr-xr-x 2 root 0 285438 Dec 1 03:20 /usr/bin/cc # /usr/bin/cc -sh: /usr/bin/cc: not found My install cd system is able to exec files from /bin /sbin /usr/bin without any problems, but mount /dev/sd0a /mnt; /mnt/bin/mv doesn't work, while chroot /mnt; bin/mv works. Moving files around only leads to breaking them (in some cases). Has anyone met this problem? Cheers, Dmitry
Re: userland problem
Author: Martin Husemann
Date: Sun, 02 Dec 2012 10:46
Date: Sun, 02 Dec 2012 10:46
16 lines
2000 bytes
2000 bytes
On Sun, Dec 02, 2012 at 02:29:29PM +0400, Nadin wrote: > Hello everybody > > I have some weird problem with my NetBSD/alpha 6.0. The problem is > that I can only run things which are originally residing in /bin. Very strange - is this from a fresh install, or did you update from some ancient version? I assume /rescue/ls works? Could you check wether /libexec looks sane and if there are stale symlinks for libc.so.* in either /lib or /usr/lib ? Martin
Re: userland problem
Author: Matt Thomas
Date: Sun, 02 Dec 2012 12:54
Date: Sun, 02 Dec 2012 12:54
18 lines
2237 bytes
2237 bytes
On Dec 2, 2012, at 2:46 AM, Martin Husemann wrote: > On Sun, Dec 02, 2012 at 02:29:29PM +0400, Nadin wrote: >> Hello everybody >> >> I have some weird problem with my NetBSD/alpha 6.0. The problem is >> that I can only run things which are originally residing in /bin. > > Very strange - is this from a fresh install, or did you update from some > ancient version? > > I assume /rescue/ls works? > > Could you check wether /libexec looks sane and if there are stale > symlinks for libc.so.* in either /lib or /usr/lib ? I think the problem is more likely that it's having problems with /usr/libexec/ld.elf_so
Re: userland problem
Author: Martin Husemann
Date: Sun, 02 Dec 2012 13:03
Date: Sun, 02 Dec 2012 13:03
12 lines
2128 bytes
2128 bytes
On Sun, Dec 02, 2012 at 04:54:46AM -0800, Matt Thomas wrote: > I think the problem is more likely that it's having problems with /usr/libexec/ld.elf_so Yeah - please check that symlink, it should be something like: lrwxr-xr-x 1 root wheel 18 May 12 2005 /usr/libexec/ld.elf_so@ -> /libexec/ld.elf_so (not sure where it gets the date from, I certainly did install this machine way later than 2005) Martin
Re: userland problem
Author: Dmitry Kalinkin
Date: Sun, 02 Dec 2012 15:02
Date: Sun, 02 Dec 2012 15:02
3 lines
3546 bytes
3546 bytes
I found the problem using /rescue/ldd. It was that cc, for instance, was missing libintl.so.1. I just recompiled whole system, that helped. Now system works wonderfully (except for the system ignoring fstab and only mounting ro root). I also would like to use kgdb, but I have some difficulties here too. The problem is that gdb tries to set soft-breakpoint on main() of the kernel elf before doing any meaningfull operation (like continue or step). And the stub reports reading error for that operation. And I have determined that this happens because the address is not vmapped, it is in K0SEG. kgdb_acc function from alpha's kgdb_matchdep.c explicitly filters accessible addresses to be in K1SEG. Removing this check leads to a memory access trap. It seems like writing to K0SEG requires some more privileged mode. On the other end cross-gdb (on client side) is stubborn and doesn't want to work without making sw-breakpoints here and there. Any advice?
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads