Attached are the outputs when rping and krping are run. The dmesg output when krping is run is quite verbose. Hopefully, you can throw some light by looking at it. The rping server core dumped as soon as the client was run.
Thanks, Ravi -----Original Message----- From: Pradipta Kumar Banerjee [mailto:[EMAIL PROTECTED] Sent: Friday, July 07, 2006 11:57 AM To: [EMAIL PROTECTED] Cc: [email protected] 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:[EMAIL PROTECTED] > Sent: Friday, July 07, 2006 11:37 AM > To: Ravinandan Arakali > Cc: [email protected] > 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:[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. > > 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 >> [email protected] >> http://openib.org/mailman/listinfo/openib-general >> >> To unsubscribe, please visit > http://openib.org/mailman/listinfo/openib-general >> >
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 cma_event type 4 cma_id 0x804e968 (child) child cma 0x804e968 Segmentation fault 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 created pd 0x506e60 created channel 0x506e80 created cq 0x506ea0 created qp 0x506f40 rping_setup_buffers called on cb 0x505010 allocated & registered buffers... cq_thread started. dmesg output from openfab2: -------------------------- c2: AMSO1100 Gigabit Ethernet driver v1.1 loaded ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 24 (level, low) -> IRQ 193 eth0 renamed to eth3 krping_init Virtual device iw0 asks to queue packet! Virtual device iw0 asks to queue packet! eth3: no IPv6 routers present Virtual device iw0 asks to queue packet! iw0: no IPv6 routers present dmesg output from openfab: -------------------------- c2: AMSO1100 Gigabit Ethernet driver v1.1 loaded GSI 18 sharing vector 0xB9 and IRQ 18 ACPI: PCI Interrupt 0000:01:03.0[A] -> GSI 28 (level, low) -> IRQ 185 krping_init Virtual device iw1 asks to queue packet! Virtual device iw1 asks to queue packet! eth1: no IPv6 routers present Virtual device iw1 asks to queue packet! iw1: no IPv6 routers present
openfab:~ # echo client,port=9999,addr=17.2.2.102,validate >/proc/krping openfab:~ # cat /proc/krping 1-amso0 2918224 182389 2918208 182388 0 0 0 0 Content of /var/log/messages on openfab: ---------------------------------------- Jul 7 06:56:01 openfab kernel: krping: proc write |client,port=9999,addr=17.2.2.102,validate| Jul 7 06:56:01 openfab kernel: client Jul 7 06:56:01 openfab kernel: port 9999 Jul 7 06:56:01 openfab kernel: ipaddr (17.2.2.102) Jul 7 06:56:01 openfab kernel: validate data Jul 7 06:56:01 openfab kernel: created cm_id ffff81000d207a00 Jul 7 06:56:01 openfab kernel: cma_event type 0 cma_id ffff81000d207a00 (parent) Jul 7 06:56:01 openfab kernel: cma_event type 2 cma_id ffff81000d207a00 (parent) Jul 7 06:56:01 openfab kernel: rdma_resolve_addr - rdma_resolve_route successful Jul 7 06:56:01 openfab kernel: created pd ffff81000cdbf600 Jul 7 06:56:01 openfab kernel: created cq ffff81000c33b9c0 Jul 7 06:56:01 openfab kernel: created qp ffff81001fa099c0 Jul 7 06:56:01 openfab kernel: krping_setup_buffers called on cb ffff81000d8eb800 Jul 7 06:56:01 openfab kernel: allocated & registered buffers... Jul 7 06:56:01 openfab kernel: cma_event type 9 cma_id ffff81000d207a00 (parent) Jul 7 06:56:01 openfab kernel: ESTABLISHED Jul 7 06:56:01 openfab kernel: rdma_connect successful Jul 7 06:56:01 openfab kernel: RDMA addr cfa4f40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion Jul 7 06:56:01 openfab kernel: RDMA addr cfa4d40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion Jul 7 06:56:01 openfab kernel: RDMA addr cfa4f40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion Jul 7 06:56:01 openfab kernel: RDMA addr cfa4d40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion Jul 7 06:56:01 openfab kernel: RDMA addr cfa4f40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion Jul 7 06:56:01 openfab kernel: RDMA addr cfa4d40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion Jul 7 06:56:01 openfab kernel: RDMA addr cfa4f40 rkey 17c5c00 len 64 Jul 7 06:56:01 openfab kernel: send completion Jul 7 06:56:01 openfab kernel: recv completion < Above messages repeated thousands of times > Jul 7 06:57:32 openfab kernel: krping: cq completion failed status 5 Jul 7 06:57:32 openfab kernel: krping: wait for RDMA_WRITE_ADV state 10 Jul 7 06:57:32 openfab kernel: cm_close_handler:658 cm_id_priv=ffff81000c33b8c0, state=5 Jul 7 06:57:32 openfab kernel: cma_event type 10 cma_id ffff81000d207a00 (parent) Jul 7 06:57:32 openfab kernel: krping: DISCONNECT EVENT... Jul 7 06:57:32 openfab kernel: krping_free_buffers called on cb ffff81000d8eb800 Jul 7 06:57:32 openfab kernel: destroy cm_id ffff81000d207a00 Jul 7 07:00:28 openfab kernel: krping: proc read called... openfab2:~ # echo server,port=9999,addr=17.2.2.102,validate >/proc/krping openfab2:~ # cat /proc/krping 1-amso0 5523312 345207 5523328 345208 11046656 172604 11046656 172604 Content of /var/log/messages on openfab2: ----------------------------------------- Jul 7 04:41:44 openfab2 kernel: krping: proc write |server,port=9999,addr=17.2.2.102,validate| Jul 7 04:41:44 openfab2 kernel: server Jul 7 04:41:44 openfab2 kernel: port 9999 Jul 7 04:41:44 openfab2 kernel: ipaddr (17.2.2.102) Jul 7 04:41:44 openfab2 kernel: validate data Jul 7 04:41:44 openfab2 kernel: created cm_id f7e59200 Jul 7 04:41:44 openfab2 kernel: rdma_bind_addr successful Jul 7 04:41:44 openfab2 kernel: rdma_listen Jul 7 04:42:08 openfab2 kernel: cma_event type 4 cma_id f7e6a200 (child) Jul 7 04:42:08 openfab2 kernel: child cma f7e6a200 Jul 7 04:42:08 openfab2 kernel: created pd f7267480 Jul 7 04:42:08 openfab2 kernel: created cq f6e88740 Jul 7 04:42:08 openfab2 kernel: created qp f6e14880 Jul 7 04:42:08 openfab2 kernel: krping_setup_buffers called on cb f7e59800 Jul 7 04:42:08 openfab2 kernel: allocated & registered buffers... Jul 7 04:42:08 openfab2 kernel: accepting client connection request Jul 7 04:42:08 openfab2 kernel: cma_event type 9 cma_id f7e6a200 (child) Jul 7 04:42:08 openfab2 kernel: ESTABLISHED Jul 7 04:42:08 openfab2 kernel: recv completion Jul 7 04:42:08 openfab2 kernel: Received rkey 17c5c00 addr cfa4f40 len 64 from peer Jul 7 04:42:08 openfab2 kernel: server received sink adv Jul 7 04:42:08 openfab2 kernel: server posted rdma read req Jul 7 04:42:08 openfab2 kernel: rdma read completion Jul 7 04:42:08 openfab2 kernel: server received read complete Jul 7 04:42:08 openfab2 kernel: server posted go ahead Jul 7 04:42:08 openfab2 kernel: send completion Jul 7 04:42:08 openfab2 kernel: recv completion Jul 7 04:42:08 openfab2 kernel: Received rkey 17c5c00 addr cfa4d40 len 64 from peer Jul 7 04:42:08 openfab2 kernel: server received sink adv Jul 7 04:42:08 openfab2 kernel: rdma write from lkey 17c4e00 laddr 36de8340 len 64 Jul 7 04:42:08 openfab2 kernel: rdma write completion Jul 7 04:42:08 openfab2 kernel: server rdma write complete Jul 7 04:42:08 openfab2 kernel: server posted go ahead Jul 7 04:42:08 openfab2 kernel: send completion Jul 7 04:42:08 openfab2 kernel: recv completion Jul 7 04:42:08 openfab2 kernel: Received rkey 17c5c00 addr cfa4f40 len 64 from peer Jul 7 04:42:08 openfab2 kernel: server received sink adv Jul 7 04:42:08 openfab2 kernel: server posted rdma read req Jul 7 04:42:08 openfab2 kernel: rdma read completion Jul 7 04:42:08 openfab2 kernel: server received read complete Jul 7 04:42:08 openfab2 kernel: server posted go ahead Jul 7 04:42:08 openfab2 kernel: send completion Jul 7 04:42:08 openfab2 kernel: recv completion Jul 7 04:42:08 openfab2 kernel: Received rkey 17c5c00 addr cfa4d40 len 64 from peer Jul 7 04:42:08 openfab2 kernel: server received sink adv Jul 7 04:42:08 openfab2 kernel: rdma write from lkey 17c4e00 laddr 36de8340 len 64 Jul 7 04:42:08 openfab2 kernel: rdma write completion Jul 7 04:42:08 openfab2 kernel: server rdma write complete Jul 7 04:42:08 openfab2 kernel: server posted go ahead Jul 7 04:42:08 openfab2 kernel: send completion Jul 7 04:42:08 openfab2 kernel: recv completion Jul 7 04:42:08 openfab2 kernel: Received rkey 17c5c00 addr cfa4f40 len 64 from peer Jul 7 04:42:08 openfab2 kernel: server received sink adv Jul 7 04:42:08 openfab2 kernel: server posted rdma read req Jul 7 04:42:08 openfab2 kernel: rdma read completion Jul 7 04:42:08 openfab2 kernel: server received read complete Jul 7 04:42:08 openfab2 kernel: server posted go ahead Jul 7 04:42:08 openfab2 kernel: send completion Jul 7 04:42:08 openfab2 kernel: recv completion <Above messages repeated thousands of times > Jul 7 04:44:25 openfab2 kernel: krping: wait for RDMA_READ_COMPLETE state 6 Jul 7 04:44:25 openfab2 kernel: rdma read completion Jul 7 04:44:25 openfab2 kernel: krping: cq completion failed status 5 Jul 7 04:44:25 openfab2 kernel: cm_close_handler:658 cm_id_priv=f6e887c0, state=6 Jul 7 04:44:25 openfab2 kernel: krping_free_buffers called on cb f7e59800 Jul 7 04:44:25 openfab2 kernel: destroy cm_id f7e59200 Jul 7 04:46:32 openfab2 zmd: ShutdownManager (WARN): Preparing to sleep... Jul 7 04:46:32 openfab2 zmd: ShutdownManager (WARN): Going to sleep, waking up at 07/08/2006 04:06:32
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
