If this is the problem, that's good -- it just means that we need a
better error detection in the case where we run out of memory, etc.
Stay tuned to that thread to see what happens.
On Nov 14, 2008, at 1:14 PM, Peter Cebull wrote:
Jeff Squyres wrote:
Could this issue actually be related
Jeff Squyres wrote:
Could this issue actually be related to:
http://www.open-mpi.org/community/lists/devel/2008/11/4882.php
(read through the thread to get to the error handling stuff)
You might be right that this issue is the problem. Our system has
diskless nodes, so /tmp uses a ramdisk.
Could this issue actually be related to:
http://www.open-mpi.org/community/lists/devel/2008/11/4882.php
(read through the thread to get to the error handling stuff)
On Nov 14, 2008, at 7:41 AM, Geraldo Veiga wrote:
Thanks Peter. Blocking the shared memory layer did the trick for
our p
Thanks Peter. Blocking the shared memory layer did the trick for our
program too.
For the record, we also have SGI Propack 6 installed
(sgi-propack-release-6-sgi600r3).
Is the on-node shared memory support completely blocked? What if the MPI
process calls a procedure that uses OpenMP threads, f
Geraldo,
The previous message you saw was for our Altix ICE system. Since we
started seeing these errors after upgrading to SGI Propack 6, I wonder
if there's a bug somewhere in the Propack software or an incompatibility
between Open MPI and OFED 1.3 (we had no problems under OFED 1.2). A
wor
