Strange - that shouldn't be happening. However, to get thru it, just restrict the interfaces OMPI uses. If it's the hardwired Ethernet that is causing the problem, then add

-mca oob_tcp_if_exclude en0 -mca btl_tcp_if_exclude en0

to your cmd line. If it's the wireless, then substitute en1 for en0 in the above.



On Tue, Dec 4, 2012 at 5:16 PM, Valentin Clement <valentin.clement@riken.jp> wrote:
Hi, 

It seems, the problem is happening if I have two active interfaces on my computer. Is there any configuration to use MPI_Comm_spawn_multiple on a machine with multiple interfaces ? 

Regards, 

Valentin 

On Dec 3, 2012, at 3:00 PM, Valentin Clement <valentin.clement@riken.jp> wrote:

Hi, 

I'm using call to MPI_Comm_spawn_multiple in a quite big application. I've seen a deadlock occurred in a very strange situation. If I'm running my application on my Ubuntu 12.10 with OpenMPI 1.6.3 there is absolutely no problem. 

On my Mac OS X 10.8.2 with also OpenMPI 1.6.3, I'm experiencing a dead lock on an intrecommunicator resulting from the MPI_Comm_spawn_multiple only if my ethernet interface is enable. If I disable it, the deadlock is gone. 

Anyone has an idea of what is happening ? I joined the output of ompi_info on both OS X and Linux. 

Regards,

Valentin 


-----------------------------------------------------------------------------------------
Valentin Clement - Student trainee at RIKEN AICS
Programming Environment Research Team
Master thesis project
POP-C++ on the K Computer 
Project homepage: https://forge.tic.eia-fr.ch/projects/poponk
Project board: https://forge.tic.eia-fr.ch/projects/poponk/wiki/Wiki
-----------------------------------------------------------------------------------------
<ompi_info.tar.bz2>
_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

On Dec 3, 2012, at 3:00 PM, Valentin Clement <valentin.clement@riken.jp> wrote:

Hi, 

I'm using call to MPI_Comm_spawn_multiple in a quite big application. I've seen a deadlock occurred in a very strange situation. If I'm running my application on my Ubuntu 12.10 with OpenMPI 1.6.3 there is absolutely no problem. 

On my Mac OS X 10.8.2 with also OpenMPI 1.6.3, I'm experiencing a dead lock on an intrecommunicator resulting from the MPI_Comm_spawn_multiple only if my ethernet interface is enable. If I disable it, the deadlock is gone. 

Anyone has an idea of what is happening ? I joined the output of ompi_info on both OS X and Linux. 

Regards,

Valentin 


-----------------------------------------------------------------------------------------
Valentin Clement - Student trainee at RIKEN AICS
Programming Environment Research Team
Master thesis project
POP-C++ on the K Computer 
Project homepage: https://forge.tic.eia-fr.ch/projects/poponk
Project board: https://forge.tic.eia-fr.ch/projects/poponk/wiki/Wiki
-----------------------------------------------------------------------------------------
<ompi_info.tar.bz2>
_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

-----------------------------------------------------------------------------------------
Valentin Clement - Student trainee at RIKEN AICS
Programming Environment Research Team
Master thesis project
POP-C++ on the K Computer 
Project homepage: https://forge.tic.eia-fr.ch/projects/poponk
Project board: https://forge.tic.eia-fr.ch/projects/poponk/wiki/Wiki
-----------------------------------------------------------------------------------------


_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users