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

[Ravinandan Arakali]

Sorry, I gave the wrong URL earlier. I checked out from:
svn co <https://openib.org/svn/gen2/branches/iwarp>



-----Original Message-----
From: Pradipta Kumar Banerjee [mailto:bpradip at in.ibm.com]
Sent: Friday, July 07, 2006 11:57 AM
To: ravinandan.arakali at neterion.com
Cc: openib-general at openib.org
Subject: Re: [openib-general] ping problem with ammasso cards(iWARP
interface)


Ravinandan Arakali wrote:
> Pradipta kumar,
> I had tried krping earlier but same result as with rping.
> I believe I am using latest stack since it was checked out from
> https://openib.org/svn/gen2/trunk
For iWARP use this https://openib.org/svn/gen2/branches/iwarp

I am not sure why, but the main trunk no longer contain iwarp specific code.

>
> I will try bumping up debug level on rdma_krping. Do you
> want the dmesg output while running rping or krping ?

anything will do. Also I only mentioned for rdma_krping, please do the same
for
the ammasso driver (modprobe iw_c2 debug=16) too


>
> Ravi
>
> -----Original Message-----
> From: Pradipta Kumar Banerjee [mailto:bpradip at in.ibm.com]
> Sent: Friday, July 07, 2006 11:37 AM
> To: Ravinandan Arakali
> Cc: openib-general at openib.org
> Subject: Re: [openib-general] ping problem with ammasso cards(iWARP
> interface)
>
>
> Ravinandan Arakali wrote:
>> I added -d to rping command. I am not seeing the core dump on
>> this run. Following is the output(and it blocks at this point).
>>
>> openfab2:~ # rping -s -vV -C100 -d -a 0.0.0.0 -p 9999
>> ipaddr (0.0.0.0)
>> port 9999
>> created cm_id 0x804e6e0
>> rdma_bind_addr successful
>> rdma_listen
>>
>> openfab:~ # rping -c -vV -C100 -d  -a 17.2.2.102 -p 9999
>> ipaddr (17.2.2.102)
>> port 9999
>> created cm_id 0x506b00
>> cma_event type 0 cma_id 0x506b00 (parent)
>> cma_event type 2 cma_id 0x506b00 (parent)
>> rdma_resolve_addr - rdma_resolve_route successful
>>
>>
>> -----Original Message-----
>> From: Steve Wise [mailto:swise at opengridcomputing.com]
>> Sent: Friday, July 07, 2006 11:07 AM
>> To: ravinandan.arakali at neterion.com
>> Cc: openib-general at openib.org
>> Subject: Re: ping problem with ammasso cards(iWARP interface)
>>
>>
>> adding -d to rping might give more debug info...
>>
>> Also if the server side core dumps, please get a stack trace and lets
>> see whats up...
>>
>> Steve.
>>
>>
>> On Fri, 2006-07-07 at 11:04 -0700, Ravinandan Arakali wrote:
>>> Hi,
>>> I have two systems connected back-to-back with ammasso cards. I have
>>> configured and built the libraries and drivers as mentioned in
>>>
> https://openib.org/tiki/tiki-index.php?page=Install+OpenIB+for+Ammasso1100
>>> I can ping on the regular ethX interface but both rping and krping on
>> iwarp
>>> interfaces fail (no packets sent/received).
>>> Following is the configuration:
>>> System1:
>>> eth interface: 17.1.1.101
>>> iwarp interface: 17.2.2.101
>>>
>>> System2:
>>> eth interface: 17.1.1.102
>>> iwarp interface: 17.2.2.102
>>>
>>> On System2 I run
>>> # rping -s -vV -C100 -a 0.0.0.0 -p 9999
>>>
>>> On System1 I run
>>> # rping -c -vV -C100  -a 17.2.2.102 -p 9999
>>>
>>> Sometimes I have noticed that when client is started, the server core
>> dumps.
>>> Other times, there is no core dump but there's no traffic flowing.
>
> Ravi,
>    Did you try with the 'krping' (kernel module) utility ? This is the
same
> as
> 'rping' but it's a kernel module instead of a user space application.
> Also hope you are using the latest stack.
> Also enable debugging for the Ammasso driver (modprobe rdma_krping
debug=3)
> and
> send us the dmesg output.
>
> Thanks,
> Pradipta Kumar
>
>>> Any help is appreciated.
>>>
>>> Thanks,
>>> Ravi
>>
>> _______________________________________________
>> 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
>>
>