Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Alex Tumanov (atumanov_at_[hidden])
Date: 2007-02-08 21:15:26

Hello Troy,

This issue is fairly common and has to do with the maximum amount of
memory allowed to be allocated. See this FAQ for more detail:

I had the same issue and the FAQ resolves it.

Good luck,

On 2/8/07, Troy Telford <ttelford.groups_at_[hidden]> wrote:
> I've got a system that is running Open MPI 1.1.2, SLES 10, with the OFED
> 1.0 drivers.
> The code runs over Gigabit Ethernet/TCP without issues on Open MPI...
> The code does some memory allocation, communication, etc - the developer
> wrote it to stress the network fabric, and can be submitted if necessary.
> The job is being run on four nodes (two dual-core CPUs each, 16 cores
> total), with DDR IB.
> Non-MPI bandwidth tests don't seem to be having issues; but that doesn't
> necessarily mean things work great over MPI.
> The error is (upon job start), something to the extent of (transcribed
> from phone):
> mca_mpool_openib_register: cannot allocate memory
> .
> .
> .
> Error creating low priority CQ for MTHCA0: Cannot allocate memory.
> What has to happen for this message to get thrown? (I've seen IB fabric
> instability with OpenIB before, and I don't recall this being one of the
> errors I've seen).
> Also, is there any chance that the error can be caused by mismatched
> libraries (from a different compile of Open MPI?)
> (And I apologize for firing off this without knowing more; I'm still
> gathering data as I learn more...)
> --
> Troy Telford
> _______________________________________________
> users mailing list
> users_at_[hidden]