[openib-general] Problem running rping on chelsio T3 adapters
Steve Wise
swise at opengridcomputing.com
Thu Jul 20 12:32:31 PDT 2006
The server log indicates the T3 RNIC got the listen command for port
9999. The client log, however, shows no activity. So I _think_ there
is still some configuration problem and the RDMA CMA is choosing the
wrong rdma interface for the outgoing connection. Its certainly _not_
choosing the T3 rnic.
In fact, cma event 1 is 'ADDR ERROR' which I think means it couldn't
find a local rdma interface to reach the dst ipaddr -or- it found the
local interface, but couldn't resolve the neighbour ipaddr to a hw
address (ARP failed).
Lets re-examine the test:
> > > > > > > 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
> >
Given the above 'rping' command, 150.10.11.200 is supposed to be the
rping server's rnic address. However, your ifconfig output showed no
interface bound to 150.10.11.200.
Is this a pilot error, or did you change the config since you originally
sent out the 'rping' line above?
Steve.
More information about the general
mailing list