From owner-freebsd-current@FreeBSD.ORG Sat May 24 23:44:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0FE037B401 for ; Sat, 24 May 2003 23:44:55 -0700 (PDT) Received: from gunjin.wccnet.org (gunjin.wccnet.org [198.111.176.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id E619C43FA3 for ; Sat, 24 May 2003 23:44:54 -0700 (PDT) (envelope-from anthony@gunjin.wccnet.org) Received: from gunjin.wccnet.org (localhost.rexroof.com [127.0.0.1]) by gunjin.wccnet.org (8.12.3/8.12.2) with ESMTP id h4P6nVsn096736 for ; Sun, 25 May 2003 02:49:31 -0400 (EDT) Received: (from anthony@localhost) by gunjin.wccnet.org (8.12.3/8.12.3/Submit) id h4P6nUpL096735 for freebsd-current@freebsd.org; Sun, 25 May 2003 02:49:30 -0400 (EDT) Date: Sun, 25 May 2003 02:49:30 -0400 From: Anthony Schneider To: freebsd-current@freebsd.org Message-ID: <20030525064929.GA96588@x-anthony.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline User-Agent: Mutt/1.4i Subject: mpi + shmem issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 May 2003 06:44:56 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, My machine is a dual athlon: FreeBSD pickle. 5.1-BETA FreeBSD 5.1-BETA #6: Sun May 25 02:16:15 EDT 2003 anthony@pickle.:/usr/src/sys/i386/compile/PICKLE i386 I started having this issue, which may or may not exist on uniprocessor systems or 4.x systems. I built mpi with ch_shmem device for shared memory programs (instead of the more common rsh/ssh), and something strange happens. For even the most basic little program, the program will launch fine (usually) the first time i run it after the system boots, but after a few executions, execution starts failing consistently until after i reboot. as an example, here is a small acknowledgment program: #include #include int main (int argc, char *argv[]) { int mpiRank, mpiSize; MPI_Init (&argc, &argv); MPI_Comm_rank (MPI_COMM_WORLD, &mpiRank); printf ("#%d here\n", mpiRank); return 0; } and here is the history of executing it: pickle:anthony:/home/anthony/src/mpi:6% mpirun -np 2 ./foo #0 here #1 here Child process exited unexpectedly 0 Abort trap (core dumped) pickle:anthony:/home/anthony/src/mpi:7% mpirun -np 2 ./foo #0 here pickle:anthony:/home/anthony/src/mpi:8% #1 here pickle:anthony:/home/anthony/src/mpi:8% mpirun -np 2 ./foo #0 here #1 here pickle:anthony:/home/anthony/src/mpi:9% mpirun -np 2 ./foo #0 here #1 here pickle:anthony:/home/anthony/src/mpi:10% mpirun -np 2 ./foo #1 here #0 here Child process exited unexpectedly 0 Abort trap (core dumped) pickle:anthony:/home/anthony/src/mpi:11% mpirun -np 2 ./foo #0 here #1 here Child process exited unexpectedly 0 Abort trap (core dumped) pickle:anthony:/home/anthony/src/mpi:12% mpirun -np 2 ./foo #0 here #1 here pickle:anthony:/home/anthony/src/mpi:13% mpirun -np 2 ./foo #1 here #0 here Child process exited unexpectedly 0 Abort trap (core dumped) pickle:anthony:/home/anthony/src/mpi:14% mpirun -np 2 ./foo #0 here #1 here pickle:anthony:/home/anthony/src/mpi:15% mpirun -np 2 ./foo #0 here #1 here pickle:anthony:/home/anthony/src/mpi:16% mpirun -np 2 ./foo semget failed for setnum = 0 Abort trap (core dumped) pickle:anthony:/home/anthony/src/mpi:17% mpirun -np 2 ./foo semget failed for setnum = 0 Abort trap (core dumped) pickle:anthony:/home/anthony/src/mpi:18% mpirun -np 2 ./foo semget failed for setnum = 0 Abort trap (core dumped) ... (continues until i reboot) the first run that aborts is strange, but since it is not something i've witnessed previously, i'd like to forget that and focus on the repeated semget failures. i would normally be looking into the mpi implementation (mpich 1.2.5), but since after semget fails once it never seems to succeed again with other mpi programs, i think this to be a freebsd problem. i'm runing a (barely) custom kernel, with nothing added to it. i just cvsup'd and rebuilt less than an hour ago, and the problem has persisted from beta #5 through beta #6. any suggestions? thank you for your help. -Anthony. --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE+0Gd5KUeW47UGY2kRAjJxAJ9pgtjX0siafq+1AZ8FIeBrIF9tIwCaAxCj GdV8I/NePVDjCT2Zb8kTZ5E= =hYzt -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--