error errno 32

Joshua Thomas thomasj at engr.uconn.edu
Sat Jul 20 01:35:39 EDT 2002


After long hours of debugging, it turned out to be a routine coding error.

Remember folks, don't forget the 'status' return variable in MPI_RECV().... 

Joshua Thomas
 


On Friday 19 July 2002 13:55, Joshua Thomas wrote:
> On second glance, the problem is still here. It just took longer to show 
> itself. Any other ideas? This is a show-stopper for me.
> 
> Don't make me go back to PVM! :(
> 
> Joshua Thomas
> 
> 
> 
> Subject: Re: errno 32 errors
> Date: Fri, 19 Jul 2002 13:45:40 -0400
> From: Joshua Thomas <thomasj at engr.uconn.edu>
> To: <alex at compusys.co.uk>
> 
> 
> Alex,
> 
> Thank you! This fixed my problem!
> [This on Slackware 8.0]
> 
> Shouldn't this be on the FAQ?
> 
> Joshua Thomas
> 
> 
> On Friday 19 July 2002 05:21, you wrote:
> > Redhat have somehow broken their sem.h and ipc.h. If you use your own
> > kernel, copy from ../src/kernel/include/asm & ../src/kernel/include/linux
> > the file ipc.h and sem.h to /usr/include/sys, recompile your mpich and
> > everything might start working.  (it did for us)
> > 
> > I think the SMP patch you are talking about was for 1.2.3.
> > 
> > Alex
> > 
> > 
> > On Fri, 19 Jul 2002, Joshua Thomas wrote:
> > 
> > > Hello all. This is my first posting here.
> > > 
> > > I'm using MPICH 1.2.4, with the ch_p4mpd device, on a cluster of SMP 
> Athlons.
> > > Compilation and install went w/o any problems, and all the test 
programs 
> ran 
> > > without trouble. The first programs I wrote myself even ran without any 
> > > problems.
> > > 
> > > Now, however, I've written something a bit more complex, and about 50% 
of 
> the 
> > > time it dies with:
> > > 
> > > p0_29708: (0.055913) net_recv failed for fd = 17
> > > p0_29708:  p4_error: net_recv read, errno = : 104
> > > 
> > > or
> > > 
> > > p0_29713: (0.022796) net_send: could not write to fd=17, errno = 32
> > > p0_29713:  p4_error: net_send write: -1
> > > 
> > > I did some google searching, and noted that at one point this might 
have 
> been 
> > > a SMP issue, and a patch had been provided, though I could not locate 
it.
> > > 
> > > Any help would be GREATLY appreciated!
> > > 
> > > 
> > 
> 
> -- 
> Joshua F. Thomas
> Research Assistant | Fiber Optics Manufacturing
> University of Connecticut
> Lab: 860-486-0624
> thomasj at engr.uconn.edu
> http://www.engr.uconn.edu/ofmrl/
> 
> 
> -------------------------------------------------------
> 
> -- 
> Joshua F. Thomas
> Research Assistant | Fiber Optics Manufacturing
> University of Connecticut
> Lab: 860-486-0624
> thomasj at engr.uconn.edu
> http://www.engr.uconn.edu/ofmrl/
> 
> _______________________________________________
> mpiexec mailing list
> mpiexec at osc.edu
> http://email.osc.edu/mailman/listinfo/mpiexec
> 

-- 
Joshua F. Thomas
Research Assistant | Fiber Optics Manufacturing
University of Connecticut
Lab: 860-486-0624
thomasj at engr.uconn.edu
http://www.engr.uconn.edu/ofmrl/




More information about the mpiexec mailing list