[Mvapich-discuss] using 2.3.5 on ethernet

Lana Deere lana.deere at gmail.com
Thu Feb 11 13:55:04 EST 2021


This seems to be due to the patch for the bus error issue I was having in
mvapich2-2.3.5-1, and it appears it can be worked around if I use
   -genv MV2_USE_SHARED_MEM 1
when I try to run on my desktop.

.. Lana (lana.deere at gmail.com)




On Thu, Feb 11, 2021 at 12:44 PM Lana Deere <lana.deere at gmail.com> wrote:

> I tried running a simple command using 2.3.5-1 on my desktop today,
>     mpiexec.hyrdra -np 2 program_name
> and got errors because there is no recognized HCA.  I thought it would
> fall back to using Ethernet or something rather than looking for InfiniBand
> (which I don't have).  Is there a way to tell the MPI command to do this?
>
> [twkrh3:mpi_rank_0][mv2_get_hca_type]
> **********************WARNING***********************
> [twkrh3:mpi_rank_0][mv2_get_hca_type] Failed to automatically detect the
> HCA architecture.
> [twkrh3:mpi_rank_0][mv2_get_hca_type] This may lead to subpar
> communication performance.
> [twkrh3:mpi_rank_0][mv2_get_hca_type]
> ****************************************************
> [twkrh3:mpi_rank_0][rdma_open_hca] Unknown HCA type: this build of
> MVAPICH2 does notfully support the HCA found on the system (try with other
> build options)
> [cli_0]: aborting job:
> Fatal error in MPI_Init:
> Other MPI error, error stack:
> MPIR_Init_thread(490)............:
> MPID_Init(397)...................: channel initialization failed
> MPIDI_CH3_Init(445)..............: rdma_get_control_parameters
> rdma_get_control_parameters(1913):
> rdma_open_hca(930)...............: Failed to open HCA number 0
>
>
> .. Lana (lana.deere at gmail.com)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/mvapich-discuss/attachments/20210211/9230344b/attachment-0022.html>


More information about the Mvapich-discuss mailing list