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:[EMAIL PROTECTED] Sent: Friday, July 07, 2006 11:07 AM To: [EMAIL PROTECTED] Cc: [email protected] 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. > > Any help is appreciated. > > Thanks, > Ravi _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
