[openib-general] Problem running rping on chelsio T3 adapters

[Steve Wise]

hmm.

Lets recap for my brain:

1) krping works over T3.  So the physical connectivity is ok.

2) rping doesn't work...rping client gets an error 110 from cma event 1.
Event 1 is ADDR_ERROR, which means something balled up trying to figure
out which local interface to use, or the ARP resolution failed (timed
out).

3) I seem to remember from the T3 debug logs, that the client isn't
getting any connect request from the iwarp CM.  This jives with #2.

Does the server ever get any connection indication at all?

Can I log into these systems and poke around?  It'll definitely expedite
things...

Also, a network sniffer trace of pkts going in/out of the client's port
would help too...

Steve.




On Tue, 2006-07-25 at 13:47 -0400, Sundeep Narravula wrote:
> > > > > > > > > > > We are using kernel 2.6.16.3 and installed the latest code/drivers from
> > > > > > > > > > > the iwarp branch. Currently, we are seeing an address resolution problem
> > > > > > > > > > > while using rping.
> > > > > > > > > > >
> > > > > > > > > > > [narravul at d1-as4 examples]$ ./rping -c -VvC100 -a 150.10.11.200 -p 9999
> > > > > > > > > > > libibverbs: Warning: couldn't load driver
> > > > > > > > > > > /usr/local/lib/infiniband/mthca.so: /usr/local/lib/infiniband/mthca.so:
> > > > > > > > > > > undefined symbol: ibv_cmd_query_pkey
> > > > > > > > > > > cma event 1, error -110
> > > > > >
> >
> > Why don't you go ahead and build/install libmthca -or- remove the IB
> > card and see if that helps.  This is still some basic
> > configuration/installation problem here...
> 
> Hi Steve,
>   We have tried both these options. Building libmthca / removing the IB
> cards did not help. We are still running the same errors. The dmesg log
> are also identical.
> 
>   --Sundeep.
> 
> >
> > Steve.
> >
>