QLogic OFED+ Host Software User Guide, Rev. B

F–Troubleshooting
QLogic MPI Troubleshooting
NOTE:
It is important that /dev/shm be writable by all users, or else error
messages like the ones in this section can be expected. Also, non-QLogic
MPIs that use PSM may be more prone to stale shared memory files when
processes are abnormally terminated.
gdb Gets SIG32 Signal Under mpirun -debug with the
PSM Receive Progress Thread Enabled
When you run mpirun -debug and the PSM receive progress thread is enabled,
gdb (the GNU debugger) reports the following error:
(gdb) run
Starting program: /usr/bin/osu_bcast < /dev/null [Thread debugging
using libthread_db enabled] [New Thread 46912501386816 (LWP
13100)] [New Thread 1084229984 (LWP 13103)] [New Thread 1094719840
(LWP 13104)]
Program received signal SIG32, Real-time event 32.
[Switching to Thread 1084229984 (LWP 22106)] 0x00000033807c0930 in
poll () from /lib64/libc.so.6
This signal is generated when the main thread cancels the progress thread. To fix
this problem, disable the receive progress thread when debugging an MPI
program. Add the following line to $HOME/.mpirunrc:
export PSM_RCVTHREAD=0
NOTE:
Remove the above line from $HOME/.mpirunrc after you debug an MPI
program. If this line is not removed, the PSM receive progress thread will be
permanently disabled. To check if the receive progress thread is enabled,
look for output similar to the following when using the mpirun -verbose
flag:
idev-17:0.env PSM_RCVTHREAD Recv thread flags
0 disables thread) => 0x1
The value 0x1 indicates that the receive thread is currently enabled. A value
of 0x0 indicates that the receive thread is disabled.
F-24 D000046-005 B