On Oct 27, 2005, at 7:12 PM, Brian Barrett wrote:
I think we just committed a fix for this one on both the trunk and
v1.0 branch. Will be in the tarballs tomorrow morning.
Minor clarification just so that everyone is on the same sheet of music
-- these fixes will be in the nightly tarballs t
On Oct 24, 2005, at 10:21 PM, Troy Benjegerdes wrote:
On Mon, Oct 24, 2005 at 06:03:02PM -0500, Troy Benjegerdes wrote:
troy@opteron1:/usr/src/netpipe3-dev$ mpirun -np 2 -mca
btl_base_exclude
openib NPmpi
1: opteron1
0: opteron1
mpirun noticed that job rank 1 with PID 352 on node "localhost"
Troy --
We've managed to replicate this problem and are looking into it. Thanks
for reporting it!
Troy Benjegerdes wrote:
On Mon, Oct 24, 2005 at 06:03:02PM -0500, Troy Benjegerdes wrote:
troy@opteron1:/usr/src/netpipe3-dev$ mpirun -np 2 -mca btl_base_exclude
openib NPmpi
1: opteron1
0: o
I'm assuming that this is a production version of NP, right? (i.e., not
a development version)
Can you run the MPI processes through valgrind to see where the error
really occurs? This corefile only shows the final results, not the
actual cause.
Troy Benjegerdes wrote:
On Mon, Oct 24, 20
On Mon, Oct 24, 2005 at 06:03:02PM -0500, Troy Benjegerdes wrote:
> troy@opteron1:/usr/src/netpipe3-dev$ mpirun -np 2 -mca btl_base_exclude
> openib NPmpi
> 1: opteron1
> 0: opteron1
> mpirun noticed that job rank 1 with PID 352 on node "localhost" exited
> on signal 11.
> 1 process killed (possibl
