Abnormal return value for 'mpirun -np 4 -wdir /home-2/khoste/.local/easybuild/build/GROMACS/4.6.5/goolfc-2.6.10-hybrid.3/regressiontests-4.6.5/simple/angles1 mdrun_mpi    -notunepme -table ../table -tablep ../tablep >mdrun.out 2>&1' was 127
No mdrun output files.
FAILED. Check mdrun.out, md.log files in angles1

$ cat /home-2/khoste/.local/easybuild/build/GROMACS/4.6.5/goolfc-2.6.10-hybrid.3/regressiontests-4.6.5/simple/angles1/mdrun.out 
mdrun_mpi: symbol lookup error: /home-2/khoste/.local/easybuild/software/OpenMPI/1.7.3-gcccuda-2.6.10/lib/openmpi/mca_pml_ob1.so: undefined symbol: progress_one_cuda_htod_event
mdrun_mpi: symbol lookup error: /home-2/khoste/.local/easybuild/software/OpenMPI/1.7.3-gcccuda-2.6.10/lib/openmpi/mca_pml_ob1.so: undefined symbol: progress_one_cuda_htod_event
mdrun_mpi: symbol lookup error: /home-2/khoste/.local/easybuild/software/OpenMPI/1.7.3-gcccuda-2.6.10/lib/openmpi/mca_pml_ob1.so: undefined symbol: progress_one_cuda_htod_event
mdrun_mpi: symbol lookup error: /home-2/khoste/.local/easybuild/software/OpenMPI/1.7.3-gcccuda-2.6.10/lib/openmpi/mca_pml_ob1.so: undefined symbol: progress_one_cuda_htod_event
--------------------------------------------------------------------------
mpirun has exited due to process rank 1 with PID 23929 on
node sb001 exiting improperly. There are three reasons this could occur:

1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

3. this process called "MPI_Abort" or "orte_abort" and the mca parameter
orte_create_session_dirs is set to false. In this case, the run-time cannot
detect that the abort call was an abnormal termination. Hence, the only
error message you will receive is this one.

This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).

You can avoid this message by specifying -quiet on the mpirun command line.

--------------------------------------------------------------------------