Port-sparc64 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: mlx on sparc?



On Mon, Jun 02, 2008 at 11:14:13PM +0200, Jan-Hinrich Fessel wrote:

> # mlxctl -v cstatus
> DAlignment error: pid=14.1 comm=mlxctl dsfsr=00000000:00800001  
> dsfar=ffffffff:ffffba26 isfsr=00000000:00000000 pc=101908
> AC960P/PD, 3 channels, fpid 14 (mlxctl), uid 0: exited on signal 10  
> (core dumped)
> irmware 3.51-0-09, 4MB RAM
> [1]   Bus error (core dumped) mlxctl -v cstatus
> # mlxctl -f /dev/mlx1 -v cstatus
> DAlignment error: pid=15.1 comm=mlxctl dsfsr=00000000:00800001  
> dsfar=ffffffff:ffffba06 isfsr=00000000:00000000 pc=101908
> AC960PG, 2 channels, firmware 4.06-0-pid 15 (mlxctl), uid 0: exited on  
> signal 10 (core dumped)
> 85, 16MB RAM
> [1]   Bus error (core dumped) mlxctl -f /dev/mlx1 -v cstatus
> # iopctl showstatus
> iopctl: /dev/iop0: Device not configured
> 
> gdb isn't that helpful:
> # gdb obj/mlxctl mlxctl.core
> GNU gdb 6.5
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and  
> you are
> welcome to change it and/or distribute copies of it under certain  
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for  
> details.
> This GDB was configured as "sparc64--netbsd"...
> Reading symbols from /usr/lib/libkvm.so.5...done.
> Loaded symbols for /usr/lib/libkvm.so.5
> Reading symbols from /usr/lib/libc.so.12...done.
> Loaded symbols for /usr/lib/libc.so.12
> Reading symbols from /usr/libexec/ld.elf_so...done.
> Loaded symbols for /usr/libexec/ld.elf_so
> Core was generated by `mlxctl'.
> Program terminated with signal 10, Bus error.
> #0  0x0000000000101908 in cmd_cstatus ()
> (gdb) bt
> #0  0x0000000000101908 in cmd_cstatus ()
> #1  0x0000000000102dfc in main (argc=3, argv=0xffffffffffffbcb8)
>     at /usr/src/usr.sbin/mlxctl/main.c:145
> (gdb)

Stick "LDADD=-g -static" and "COPTS=-g" in the Makefile, export USETOOLS=no,
rebuild and re-run, then gdb should give you some useful info.

Andrew


Home | Main Index | Thread Index | Old Index