On Thursday 20 April 2006 01:48, Arlin Davis wrote: > >Here is a back trace of the hanged process: > >(gdb) bt > >#0 0x00002aaaab31c86a in pthread_cond_wait@@GLIBC_2.3.2 () from > >/lib64/tls/libpthread.so.0 > >#1 0x00002aaaab42ef5b in dapl_os_wait_object_wait (wait_obj=0x516650, > >timeout_val=<value optimized out>) at dapl_osd.c:276 > >#2 0x00002aaaab42e9ab in dapl_evd_wait (evd_handle=0x516560, > >time_out=4294967295, threshold=1, event=0x7fffffdd7bf0, > >nmore=0x7fffffdd7c2c) > > at dapl_evd_wait.c:233 > >#3 0x00000000004021ab in disconnect_ep () at dtest.c:894 > >#4 0x0000000000404cad in main (argc=4, argv=<value optimized out>) at > > > > > > > Yes, looks like the disconnect event was dropped. Couple of questions: > > Does this only happen with the scm provider? > Can you reproduce on the OpenIB trunk or 1.0 branch? > > Thanks, > > -arlin > >
I tried to execute this test on the following driver: openib_gen2-20060420-0800, svn REV=6520 (trunk) and i get the same results. Here are the results of this test execution with all of dapl provider names: OpenIB-cma : passed OpenIB-cma-ip : passed OpenIB-cma-netdev : passed OpenIB-scm1 : never ends i guess that as you suspected, the problem is with the scm provider. Dotan _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
