[openib-general] ping problem with ammasso cards(iWARP interface)

[Ravinandan Arakali]

I haven't yet tried with a fresh installation. But I did notice that,
compared to my current tree, several files under libamso and couple of files
under librdma have been removed by Steve Wise. I did the same change to my
tree and rebuilt librdmacm.so and amso.so but still see the same crash.

Ravi

-----Original Message-----
From: Pradipta Kumar Banerjee [mailto:bpradip at in.ibm.com]
Sent: Wednesday, July 12, 2006 10:31 AM
To: Ravinandan Arakali
Cc: openib-general at openib.org
Subject: Re: [openib-general] ping problem with ammasso cards(iWARP
interface)


Ravinandan,
  Do you still see the rping crash?

Thanks,
Pradipta Kumar.

Ravinandan Arakali wrote:
> Pradipta,
> Okay, thanks.. Initially, I was not sure since I don't remember non-zero
> values in /proc/krping. When I re-ran the krping test, I see following
> output
> openfab2:~ # cat /proc/krping
> 1-amso0 891376 55711 891376 55711 1782720 27855 1782784 27856
>
> As you mentioned, the RDMA traffic seems to be flowing indeed !
> Any idea why rping is dumping core ?
>
> Has any testing been done using SDP with ammasso cards ?
>
> Regards,
> Ravi
>
>
> -----Original Message-----
> From: Pradipta Kumar Banerjee [mailto:bpradip at in.ibm.com]
> Sent: Friday, July 07, 2006 11:20 PM
> To: Ravinandan Arakali
> Cc: Leonid. Grossman (E-mail); sivakumar.subramani at neterion.com;
> openib-general at openib.org
> Subject: Re: [openib-general] ping problem with ammasso cards(iWARP
> interface)
>
>
> Ravinandan Arakali wrote:
>> Pradipta,
>> Following is the output from gdb after core dump. I have also copy-pasted
>> the gdb output on client system.
>>
>> Attached is the dmesg output when krping test is run in verbose mode.
>> The ping data on the sender(client) seems okay. The content is shifted
>> forward by one character for each packet. On receiver, after receiving
> ping
>> pkt 9, it seems to jump to pkt no. 1935. Not sure if it's because
messages
>> can be lost during writing to /var/log/messages ?
> krping is indeed working!!...Using 'verbose' allows you to see the ping
> data.
> When not using 'verbose' you see only 'send/recv' messages.
>> -----------------------------------------
>> (gdb) run -s -vV -C100 -d -a 0.0.0.0 -p 9999
>> Starting program:
>> /tmp/ib/src/userspace/librdmacm/examples/.libs/rping -s -vV -C100 -d -a
>> 0.0.0.0 -p 9999
>> [Thread debugging using libthread_db enabled]
>> [New Thread -1210054992 (LWP 3668)]
>> ipaddr (0.0.0.0)
>> port 9999
>> created cm_id 0x804e6e0
>> [New Thread -1210057824 (LWP 3671)]
>> rdma_bind_addr successful
>> rdma_listen
>> cma_event type 4 cma_id 0x804e968 (child)
>> child cma 0x804e968
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread -1210054992 (LWP 3668)]
>> rping_setup_qp (cb=0x0, cm_id=0x804e968) at examples/rping.c:514
>> 514             cb->pd = ibv_alloc_pd(cm_id->verbs);
>> (gdb) bt
>> #0  rping_setup_qp (cb=0x0, cm_id=0x804e968) at examples/rping.c:514
>> #1  0x0804a716 in main (argc=9, argv=Cannot access memory at address 0x6
>> ) at examples/rping.c:767
>> (gdb)
>>
>> ---------------------------------
>> (gdb) run -c -vV -C100 -d  -a 17.2.2.102 -p 9999
>> Starting program:
>> /tmp/ib/src/userspace/librdmacm/examples/.libs/rping -c -vV -C100 -d  -a
>> 17.2.2.102 -p 9999
>> [Thread debugging using libthread_db enabled]
>> [New Thread 47388824908032 (LWP 4620)]
>> ipaddr (17.2.2.102)
>> port 9999
>> created cm_id 0x506b00
>> [New Thread 1082132800 (LWP 4623)]
>> cma_event type 0 cma_id 0x506b00 (parent)
>> cma_event type 2 cma_id 0x506b00 (parent)
>> rdma_resolve_addr - rdma_resolve_route successful
>> created pd 0x506e60
>> created channel 0x506e80
>> created cq 0x506ea0
>> created qp 0x506f40
>> rping_setup_buffers called on cb 0x505010
>> allocated & registered buffers...
>> [New Thread 1090525504 (LWP 4624)]
>> cq_thread started.
>>
>>
>
>
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
>
> To unsubscribe, please visit
http://openib.org/mailman/listinfo/openib-general
>
>