topic This means default machine in Intel® MPI Library

bug: mpiexec segmentation fault

Levrel__Lucas — Mon, 08 Apr 2019 10:08:03 GMT

Hello,

Starting from Parallel Studio 2019 Update 1, mpiexec fails to run any executable. Example: "mpiexec -np 1 /bin/ls". Any call to mpiexec (except calls like "mpiexec -help") results in Segmentation fault.

Please help. I can provide additional information if necessary. However testing is a bit complicated because I had to revert to the Initial release, and Updates cannot be installed concurrently AFAIK, so please request testing only if absolutely necessary.

Note 1: It is on Linux Mint 19. As you may know, this distribution is heavily based on Ubuntu 18.04. By "heavily" I mean that only cosmetic packages differ, like the desktop environment packages. System packages (libc and the like) are taken directly from the Ubuntu repositories.

Note 2: This problem was originally reported in the C++ compiler forum, here. It was spotted on Opensuse (which shares most code with SLES, a distribution completely independent of Ubuntu).

Please try

Maksim_B_Intel — Tue, 09 Apr 2019 06:25:18 GMT

Please try

I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra --verbose -n 1 /bin/ls

and if it fails too, could you provide a coredump or run

( export I_MPI_HYDRA_TOPOLIB=ipl; gdb --args mpiexec.hydra --verbose -n 1 /bin/ls )

and post a backtrace?

Hi,

Levrel__Lucas — Thu, 11 Apr 2019 14:33:01 GMT

Hi,

Thank you for answering

Maksim B. (Intel) wrote:
Please try
I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra --verbose -n 1 /bin/ls

It works and outputs:

[mpiexec@maxwell] Launch arguments: /opt/intel/compilers_and_libraries_2019.3.199/linux/mpi/intel64/bin//hydra_bstrap_proxy --upstream-fd 7 --pgid 0 --proxy-id 0 --node-id 0 --launcher ssh --base-path /opt/intel/compilers_and_libraries_2019.3.199/linux/mpi/intel64/bin/ --subtree-size 1 --tree-width 16 --tree-level 1 --time-left -1 --debug /opt/intel/compilers_and_libraries_2019.3.199/linux/mpi/intel64/bin//hydra_pmi_proxy --usize -1 --auto-cleanup 1

<directory contents>

So what now?

This means default machine

Maksim_B_Intel — Thu, 11 Apr 2019 14:55:10 GMT

This means default machine topology detection library, hwloc crashes on your system. You can switch to Update 3, which contains related fixes, if convenient, or

export I_MPI_HYDRA_TOPOLIB=ipl;

at some point before starting mpirun.

I'm already running Update 3!

Levrel__Lucas — Thu, 11 Apr 2019 15:14:42 GMT

I'm already running Update 3!

Thank you. Is there anything to do at compile time?

No, compile-time switches do

Maksim_B_Intel — Fri, 12 Apr 2019 06:42:29 GMT

No, compile-time switches do not impact process manager.

Hi,

Levrel__Lucas — Fri, 19 Apr 2019 12:34:44 GMT

Hi,

It looks like this impacts performance. Is this expected?

I compared the running times of the Quantum Espresso "pw" binary: (i) compiled with 2019 initial release and launched with the default topo lib, and (ii) compiled with 2019 update 1 and launched with the ipl topo lib. Results on three test cases, which differ only by parallelization parameters:

- case 1: (i) 2h24 (ii) 2h08

- case 2: (i) 2h29 (ii) 3h00

- case 3: (i) 1h20 (ii) 1h26

(note: the variability of these times is less than 1 minute so the differences are significant)

I should add that I'm setting CPU and memory affinity using the "cset" package tools, to ensure the software is running alone on reserved sockets of the server.

Hello,

Levrel__Lucas — Tue, 04 Jun 2019 15:22:18 GMT

Hello,

(Not sure if I should have started a new thread, forum moderators feel free to split this.)

Update on the situation. I have just installed PS XE 2019 Update 4 Cluster Edition and it is worse.

"raw" mpiexec still does not work
using I_MPI_HYDRA_TOPOLIB=ipl now fails for some -n values, but not all! Some tests:

(cd to some dir containing only a dir called "rpm")

> I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra --verbose -n 1 /bin/ls
[mpiexec@maxwell] Launch arguments: /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/bin//hydra_bstrap_proxy --upstream-host maxwell --upstream-port 45565 --pgid 0 --launcher ssh --launcher-number 0 --base-path /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/bin/ --tree-width 16 --tree-level 1 --time-left -1 --collective-launch 1 --debug --proxy-id 0 --node-id 0 --subtree-size 1 --upstream-fd 7 /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/bin//hydra_pmi_proxy --usize -1 --auto-cleanup 1 --abort-signal 9
rpm

> I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra  -n 2 /bin/ls
malloc(): memory corruption
[mpiexec@maxwell] wait_proxies_to_terminate (../../../../../src/pm/i_hydra/mpiexec/intel/i_mpiexec.c:538): downstream from host maxwell was killed by signal 6 (Aborted)
[mpiexec@maxwell] main (../../../../../src/pm/i_hydra/mpiexec/mpiexec.c:2041): assert (exitcodes != NULL) failed

(same for -n ranging from 3 to 5; from 10 to 12; from 17 to 24)

> I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra  -n 6 /bin/ls
rpm
rpm
rpm
rpm
rpm
rpm

(OK as well for -n from 7 to 9, and from 25 upwards AFAICT)

> I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra  -n 13 /bin/ls
rpm
rpm
rpm
rpm
rpm
rpm
rpm
rpm
rpm
double free or corruption (out)
[mpiexec@maxwell] wait_proxies_to_terminate (../../../../../src/pm/i_hydra/mpiexec/intel/i_mpiexec.c:538): downstream from host maxwell was killed by signal 6 (Aborted)
[mpiexec@maxwell] main (../../../../../src/pm/i_hydra/mpiexec/mpiexec.c:2041): assert (exitcodes != NULL) failed

(same kind of failure with partial execution for -n from 14 to 16)

See also that bug report I made, which is why I installed Update 4 (supposedly contains a fix for 4 socket systems).

Please help.

Hi, Lucas.

Anatoliy_R_Intel — Wed, 05 Jun 2019 06:45:56 GMT

Hi, Lucas.

Could you set HYDRA_BSTRAP_VALGRIND=1 variable, run failed case and provide me the output? It can help to understand where we have memory corruption and double free or corruption.

Also from the letter above, I see that you use cset for setting CPU and memory affinity. Could you run without "cset" to check that it does not affect?

Best regards, Anatoliy.

Hi Anatoliy,

Levrel__Lucas — Thu, 06 Jun 2019 20:11:00 GMT

Hi Anatoliy,

Thank you for helping.

Anatoliy R. (Intel) wrote:
Could you set HYDRA_BSTRAP_VALGRIND=1 variable, run failed case and provide me the output? It can help to understand where we have memory corruption and double free or corruption.

> HYDRA_BSTRAP_VALGRIND=1 I_MPI_HYDRA_TOPOLIB=ipl mpiexec.hydra  -n 2 /bin/ls >& /tmp/log.log

log.log

Also from the letter above, I see that you use cset for setting CPU and memory affinity. Could you run without "cset" to check that it does not affect?

You hit the spot, it does affect. No error when run "outside" the cpusets (i.e. in the root cpuset). But I need to be able to isolate tasks; is there a way other than cpusets, if the mpiexec bug cannot be fixed quickly?

I did not find something

Anatoliy_R_Intel — Fri, 07 Jun 2019 07:31:16 GMT

I did not find something wrong in valgrind output.

We can also try HYDRA_BSTRAP_XTERM=1 variable, that will run xterm windows with launched gdb.

Please set this variable and run mpirun. After that you will see xterm windows with launched gdb. Then type `run` in each windows and you will see fail in one of the windows. Then type `bt`, it will show backtrace. Please send me this backtrace.

But I need to be able to isolate tasks; is there a way other than cpusets, if the mpiexec bug cannot be fixed quickly?

You can specify on which cpus to run mpi processes via I_MPI_PIN* variables. For example I_MPI_PIN_PROCESSOR_LIST=0,1 will run rank 0 on cpu 0 and rank 1 on cpu 1:

$ I_MPI_PIN_PROCESSOR_LIST=0,1 mpiexec -n 2 -genv I_MPI_DEBUG=4 ./test.exe
..
[0] MPI startup(): Rank Pid Node name Pin cpu
[0] MPI startup(): 0 64298 host 0
[0] MPI startup(): 1 64299 host 1

Quote:Anatoliy R. (Intel)

Levrel__Lucas — Fri, 07 Jun 2019 09:33:50 GMT

Anatoliy R. (Intel) wrote:
I did not find something wrong in valgrind output.
We can also try HYDRA_BSTRAP_XTERM=1 variable, that will run xterm windows with launched gdb.
Please set this variable and run mpirun. After that you will see xterm windows with launched gdb. Then type `run` in each windows and you will see fail in one of the windows. Then type `bt`, it will show backtrace. Please send me this backtrace.

The "-n 2" run failed in the second xterm. Backtrace:

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff704b801 in __GI_abort () at abort.c:79
#2  0x00007ffff7094897 in __libc_message (action=action@entry=do_abort, 
    fmt=fmt@entry=0x7ffff71c1b9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x00007ffff709b90a in malloc_printerr (
    str=str@entry=0x7ffff71bfe0e "malloc(): memory corruption") at malloc.c:5350
#4  0x00007ffff709f994 in _int_malloc (av=av@entry=0x7ffff73f6c40 <main_arena>, 
    bytes=bytes@entry=8) at malloc.c:3738
#5  0x00007ffff70a20fc in __GI___libc_malloc (bytes=8) at malloc.c:3057
#6  0x0000000000435b47 in ipl_domain_ordering (info=0x2, ord=0x7fffffffa930, lord=0)
    at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/ipl_service.c:1505
#7  0x000000000043a02d in ipl_create_domains (pi=0x2, scale=-22224)
    at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/ipl_service.c:2233
#8  0x00000000004345e7 in ipl_one_to_many_pinning (info=0x2)
    at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/ipl_service.c:2281
#9  0x0000000000444fa4 in i_mpi_bind_init (
    binding=0x2 <error: Cannot access memory at address 0x2>, 
    bindlib=0x7fffffffa930 "", map=0x0, nrank=2)
    at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/i_mpi_bind.c:372
#10 0x000000000040a563 in launch_processes ()
    at ../../../../../src/pm/i_hydra/proxy/proxy.c:387
#11 0x0000000000408785 in main (argc=2, argv=0x7fffffffa930)
    at ../../../../../src/pm/i_hydra/proxy/proxy.c:895

But I need to be able to isolate tasks; is there a way other than cpusets, if the mpiexec bug cannot be fixed quickly?

You can specify on which cpus to run mpi processes via I_MPI_PIN* variables. For example I_MPI_PIN_PROCESSOR_LIST=0,1 will run rank 0 on cpu 0 and rank 1 on cpu 1:

$ I_MPI_PIN_PROCESSOR_LIST=0,1 mpiexec -n 2 -genv I_MPI_DEBUG=4 ./test.exe
..
[0] MPI startup(): Rank Pid Node name Pin cpu
[0] MPI startup(): 0 64298 host 0
[0] MPI startup(): 1 64299 host 1

I'd like the process to have exclusive access to some sockets (CPU+memory); with cset I can both pin the computation task to sockets 1-3 and pin all other tasks (user and system tasks) to socket 0. If I pin the computation task to sockets 1-3 with your method, I suppose the CPU allocator of the OS will "naturally" move other tasks to socket 0 (if I disable hyperthreading); but what will the RAM allocator do? We are investigating RAM bandwidth issues, so I have to prevent other tasks from using the RAM of sockets 1-3.

Thanks again for your help.

Thank you for backtrace. I

Anatoliy_R_Intel — Fri, 07 Jun 2019 09:42:33 GMT

Thank you for backtrace. I will see what can be wrong.

As a workaround you can use legacy hydra process manager.

Please try to run `PATH=${I_MPI_ROOT}/intel64/bin/legacy:${PATH} mpiexec.hydra ...`

Best regards, Anatoliy.

Quote:Anatoliy R. (Intel)

Levrel__Lucas — Fri, 07 Jun 2019 09:51:06 GMT

Anatoliy R. (Intel) wrote:
As a workaround you can use legacy hydra process manager.
Please try to run `PATH=${I_MPI_ROOT}/intel64/bin/legacy:${PATH} mpiexec.hydra ...`

Great, it works! And I don't have to set the "topolib" anymore.

Yes, ipl is the default

Anatoliy_R_Intel — Fri, 07 Jun 2019 09:55:39 GMT

Yes, ipl is the default topolib in legacy hydra.

I will create a ticket for new hydra process manager.

Best regards, Anatoliy.

Hi, Lucas

Anatoliy_R_Intel — Tue, 11 Jun 2019 12:40:05 GMT

Hi, Lucas

Could you also run lscpu?

Best regards, Anatoliy.

Hi Anatoliy,

Levrel__Lucas — Tue, 11 Jun 2019 13:00:00 GMT

Hi Anatoliy,

Here you go

> lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              192
On-line CPU(s) list: 0-191
Thread(s) per core:  2
Core(s) per socket:  24
Socket(s):           4
NUMA node(s):        4
Vendor ID:           GenuineIntel
CPU family:          6
Model:               85
Model name:          Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz
Stepping:            4
CPU MHz:             3000.000
BogoMIPS:            5400.00
Virtualization:      VT-x
L1d cache:           32K
L1i cache:           32K
L2 cache:            1024K
L3 cache:            33792
NUMA node0 CPU(s):   0,4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,
84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,
172,176,180,184,188
NUMA node1 CPU(s):   1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61,65,69,73,77,81,
85,89,93,97,101,105,109,113,117,121,125,129,133,137,141,145,149,153,157,161,165,169
173,177,181,185,189
NUMA node2 CPU(s):   2,6,10,14,18,22,26,30,34,38,42,46,50,54,58,62,66,70,74,78,82,
86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162,166,170,
174,178,182,186,190
NUMA node3 CPU(s):   3,7,11,15,19,23,27,31,35,39,43,47,51,55,59,63,67,71,75,79,83,
87,91,95,99,103,107,111,115,119,123,127,131,135,139,143,147,151,155,159,163,167,171,
175,179,183,187,191
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx
smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2
smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap
clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1
xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln
pts pku ospke md_clear flush_l1d

(Edit : last lines looked truncated, I wrapped them.)

Also, please have a look at

Levrel__Lucas — Tue, 11 Jun 2019 15:25:22 GMT

Also, please have a look at my recent comment in the other thread, because my other problem turns out to be linked to CPU sets as well, and I have done some detailed testing: some CPU sets work but not all!

Hi Lucas,

Anatoliy_R_Intel — Mon, 16 Sep 2019 07:38:00 GMT

Hi Lucas,

Could you check 2019 Update 5? The issue bellow should be fixed there.

The "-n 2" run failed in the second xterm. Backtrace:
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff704b801 in __GI_abort () at abort.c:79
#2 0x00007ffff7094897 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff71c1b9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3 0x00007ffff709b90a in malloc_printerr ( str=str@entry=0x7ffff71bfe0e "malloc(): memory corruption") at malloc.c:5350
#4 0x00007ffff709f994 in _int_malloc (av=av@entry=0x7ffff73f6c40 <main_arena>, bytes=bytes@entry=8) at malloc.c:3738
#5 0x00007ffff70a20fc in __GI___libc_malloc (bytes=8) at malloc.c:3057
#6 0x0000000000435b47 in ipl_domain_ordering (info=0x2, ord=0x7fffffffa930, lord=0) at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/ipl_service.c:1505
#7 0x000000000043a02d in ipl_create_domains (pi=0x2, scale=-22224) at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/ipl_service.c:2233
#8 0x00000000004345e7 in ipl_one_to_many_pinning (info=0x2) at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/ipl_service.c:2281
#9 0x0000000000444fa4 in i_mpi_bind_init ( binding=0x2 <error: Cannot access memory at address 0x2>, bindlib=0x7fffffffa930 "", map=0x0, nrank=2) at ../../../../../src/pm/i_hydra/../../intel/ipl/include/../src/i_mpi_bind.c:372
#10 0x000000000040a563 in launch_processes () at ../../../../../src/pm/i_hydra/proxy/proxy.c:387
#11 0x0000000000408785 in main (argc=2, argv=0x7fffffffa930) at ../../../../../src/pm/i_hydra/proxy/proxy.c:895

Hello Anatoliy,

Levrel__Lucas — Mon, 16 Sep 2019 09:20:49 GMT

Hello Anatoliy,

Thank you very much for your followup. I keep this topic bookmarked and will test as soon as possible, but it might have to wait for one or two months (the server is currently loaded for production, not the right time to run tests :-) ).