[openfabrics-ewg] [openib-general] OFED 1.1-rc3 is ready

Robert Walsh rjwalsh at pathscale.com
Fri Sep 1 14:33:50 PDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Walsh wrote:
>> Hi all, I installed the RC3 package on my Xeon/Lindenhurst platforms
>> and with the pathscale card I have the following problem
>> when trying to run Intel MPI and NetPipe.
> 
> Actually, I've been trying to run Intel MPI myself, but haven't gotten 
> very far yet.  My attempts die like this:
> 
>    $ mpiexec -n 2 ./mpitest
>    I_MPI: [0] set_up_devices(): will use device: libmpi.rdma.so
>    I_MPI: [0] set_up_devices(): will use DAPL provider: OpenIB-cma
>    I_MPI: [0] set_up_devices(): will use device: libmpi.rdma.so
>    I_MPI: [0] set_up_devices(): will use DAPL provider: OpenIB-cma
>    [0][rdma_iba_priv_intel.c:429] error(0x60029): OpenIB-cma: Could not
> create DAPL endpoint: DAT_INVALID_PARAMETER(DAT_INVALID_ARG6)
>    [1][rdma_iba_priv_intel.c:429] error(0x60029): OpenIB-cma: Could not
> create DAPL endpoint: DAT_INVALID_PARAMETER(DAT_INVALID_ARG6)
>    rank 0 in job 2  ib-idev-05_51713   caused collective abort of all ranks
>      exit status of rank 0: return code 254
> 
> dapltest seems to work just fine, so I'm a little confused.  Do you have 
> any insight on what the DAT_INVALID_PARAMETER(DAT_INVALID_ARG6) stuff is 
> referring to?

FWIW: I'm seeing a similar problem with the Intel MPI 3.0 beta release:

  $ mpiexec -n 2 ./a.out
  I_MPI: [1] MPIDI_CH3I_RDMA_init(): will use DAPL provider from
registry: OpenIB-cma
  I_MPI: [0] MPIDI_CH3I_RDMA_init(): will use DAPL provider from
registry: OpenIB-cma
  I_MPI: [0] MPIDI_CH3_Init(): I_MPI: [1] MPIDI_CH3_Init(): will use
rdma configuration
  will use rdma configuration
  [1:ib-idev-06][rdma_iba_init_d.c:154] error(0x60029): OpenIB-cma:
could not create DAPL endpoint: DAT_INVALID_PARAMETER(DAT_INVALID_ARG6)
  Hello world: rank 0 of 2 running on ib-idev-05
  rank 1 in job 2  ib-idev-05_42160   caused collective abort of all ranks
    exit status of rank 1: killed by signal 9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iQEVAwUBRPinPfzvnpzTd9fxAQJnzQf+OYOYjZwUpEQ0OtMiKJW94nAEa2okXh7H
LV/WcyH4p8q0dDmzPaEXh1dEwD+DkPWjTb0uh8r+b1Dt1f5jfC98ZXb/2sMqIW4d
93sSIoDWWPN2R2WuGnsvuQcNQBkk7h0HbCBi5vJELPQcXrQAjYPNtRXCPwjXqiGE
qefmsFXlUa+avWXQ+WbXBR+ldaBePvYGwFk+G4SwibgMhzyFwsSCzSc4FGrRvg7u
YLUIehmV2j0snxbgFK1jVCOQ+QPo8dEhR6OcwXEMbJwUqqslnwK16zUCo2IUTTdN
IROQ+kyuecaXfnH0gA2sDIKzGZxkw5zRU1cWN5cq92HPxnhjsCoa/A==
=mS+M
-----END PGP SIGNATURE-----




More information about the ewg mailing list