[openib-general] Re: mstflint failing on sparc64

[Tom Duffy]

On Thu, 2005-01-06 at 20:28 +0200, Michael S. Tsirkin wrote:
> Crashes on access to mapped memory.
> Could you print mf->ptr and offset at that point?

(gdb) print mf->ptr
$1 = (void *) 0x70304000
(gdb) print offset
$2 = 984060

> Generally, do yo happend to know if mmapping /dev/mem
> to userspace works on this architecture?

I can't imagine that it would not.  I will see if I can dig info up.
The one thing that is weird on sparc64 is that the pci bus is virtually
(not physically) addressed.  I don't know if you take that into account.

> > 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.

On x86-64/Tavor, it looks like:

[root at sins-stinger-10 ~]# ./mstflint -d 04:00.0 q
Image type: FailSafe
Chip rev.:  A1
GUIDs:      0002c901097624c0 0002c901097624c1 0002c901097624c2 0002c9000100d050
Board ID:   Cougar Card

On x86-64/Arbel, it looks like:

[root at flopteron2 bin]# /root/mstflint -d 06:00.0 q
Image type: FailSafe
Chip rev.:  A0
GUIDs:      0002c9010a99e030 0002c9010a99e031 0002c9010a99e032 0002c9000100d050
Board ID:

no Board ID.

> > begin 600 devices
> 
> Woa , uuencode, haven't seen that  for a while.

It was mime text/plain base64 going out for me...

-tduffy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20050106/af1ac216/attachment.sig>