[openib-general] Re: mstflint failing on sparc64

[Michael S. Tsirkin]

Hello!
Quoting r. Tom Duffy (tduffy at sun.com) "Re: mstflint failing on sparc64":
> On Thu, 2005-01-06 at 12:39 +0200, Michael S. Tsirkin wrote:
> > I wander what 0000: is for? Anyway, I added support for names format
> > 0000:xx:xx.x just for convenience.
> > But its not a real issue.
> 
> Cool, thanks.
> 
> > By the way, looking at drivers/pci/proc.c it seems that domains>0 are
> not
> > really supported in linux yet. Do you see 8100 in a first column in
> > /proc/bus/pci/devices, too?
> > If not, could you cat /proc/bus/pci/devices please?
> > Please try sending it as an attachment, your mailer seems to wrap
> lines.
> 
> I thought I preformatted it, oh well.  It is attached.

Well, I see regular 8100 there, where does lspci get another 0000: ?
Its a mystery.

> > > tat:~# ./mstflint -d 81:00.0 q
> > > Bus error
> > 
> > Interesting. Maybe mmap does not work as it should?
> > Could you run it under gdb and do a backtrace? I also added
> > a sanity checks on mmap result, maybe that will help us
> > see what is the problem.
> 
> tat:~# gdb ./mstflint
> GNU gdb 6.3-debian
> Copyright 2004 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 "sparc-linux"...Using host libthread_db
> library "/lib/libthread_db.so.1".
> 
> (gdb) run -d 81:00.0 q
> Starting program: /root/mstflint -d 81:00.0 q
> warning: linux_test_for_tracefork: unexpected result from waitpid
> (10830, status 0xb7f)
> 
> Program received signal SIGBUS, Bus error.
> 0x00011400 in mread4 (mf=0x2c050, offset=984060, value=0xeffff1cc)
>     at mtcr.h:355
> 355     mtcr.h: No such file or directory.
>         in mtcr.h
> (gdb) bt
> #0  0x00011400 in mread4 (mf=0x2c050, offset=984060, value=0xeffff1cc)
>     at mtcr.h:355
> #1  0x00011b24 in Flash::open (this=0xeffff6e8, device=0x2c050 "")
>     at flint.cpp:909
> #2  0x00017554 in main (ac=4, av=0xeffffda4) at flint.cpp:3589


Crashes on access to mapped memory.
Could you print mf->ptr and offset at that point?
Generally, do yo happend to know if mmapping /dev/mem
to userspace works on this architecture?

[... snip ...]

> this looks ok except for the Board ID.
> 
> tat:~# ./mstflint -d /proc/bus/pci/0000\:81/00.0 q
> Image type: FailSafe
> Chip rev.:  A1
> GUIDs:      d05f760901c90200 d15f760901c90200 d25f760901c90200
> 50d0000100c90200
> Board ID:   guoCC ra

But on x86 it looks right? Thats not in mtcr, that will be
flint code proper. I'll look at it the net week, I 'm sure
its nothing critical.

> 
> -- 
> Tom Duffy <tduffy at sun.com>
> 
> 
> 
> begin 600 devices

Woa , uuencode, haven't seen that  for a while.

mst