• 2019 Update 7
  • 03/31/2020

Problem: MPI Application Hangs

Intel® MPI Library Developer Guide for Linux* OS


MPI application hangs without any output.

Case 1


Application does not use MPI in a correct way.


Run your MPI application with the
option to perform correctness checking. The correctness checker is specifically designed to find MPI errors, and provides tight integration with the Intel® MPI Library.
In case of a deadlock, the checker will set up a one-minute timeout and show the state of each rank.
For more information, refer to this page.

Case 2


The remote service (for example, SSH) is not running on all nodes or it is not configured properly.


Check the state of the remote service on the nodes and connection to all nodes.

Case 3


The Intel® MPI Library runtime scripts are not available, so the shared space cannot be reached.


Check if the shared path is available across all the nodes.

Case 4


Different CPU architectures are used in a single MPI run.


export I_MPI_PLATFORM=<arch>
, where
is the oldest platform you have, for example
. Note that usage of different CPU architectures in a single MPI job negatively affects application performance, so it is recommended not to mix different CPU architecture in a single MPI job.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804