Re: Very wierd behavior on new nodes

2003-01-13 Thread user list
Thanks for replying. I have memtest now working on one of the nodes. We are usint the K7VTA3 Mainboard motherboard. Does anyone have experience with this board? Thanks Art Edwards On Sun, Jan 12, 2003 at 09:59:07PM +0100, Frank Gevaerts wrote: > On Sun, Jan 12, 2003 at 01:19:46PM -0700, Art Edwar

Re: Very wierd behavior on new nodes

2003-01-12 Thread Frank Gevaerts
On Sun, Jan 12, 2003 at 01:19:46PM -0700, Art Edwards wrote: > I have taken you advice and installed memtest86. The machine seemed to > boot without incident (I believe memtest86 runs at system boot?) so > memory seems not ot be the problem. memtest86 boots _instead_ of the kernel. You should add

Re: Very wierd behavior on new nodes

2003-01-12 Thread Art Edwards
This is a standalone box (now), so everything was compiled there. The only group of routines not compiledon the machine is ATLAS. I'll try using the native routines. Art On Tue, Jan 07, 2003 at 04:38:32PM -0600, Ron Johnson wrote: > On Tue, 2003-01-07 at 11:34, user list wrote: > > Under the 2.2 k

Re: Very wierd behavior on new nodes

2003-01-12 Thread Art Edwards
I have taken you advice and installed memtest86. The machine seemed to boot without incident (I believe memtest86 runs at system boot?) so memory seems not ot be the problem. I have tried to run the same job again and it got much further and then crashed. Out of curiosity, a colleague loaded RH 8

Re: Very wierd behavior on new nodes

2003-01-07 Thread Ron Johnson
On Tue, 2003-01-07 at 09:25, Arthur H. Edwards,1,505-853-6042,505-256-0834 wrote: > Under the 2.4.19 kernel, it depends on whether the job was spauned using > mpi. If I start it on the node, it does not kill communications. If I > start it from a head node, I can still ping. I have only tried the

Re: Very wierd behavior on new nodes

2003-01-07 Thread Arthur H. Edwards,1,505-853-6042,505-256-0834
Under the 2.4.19 kernel, it depends on whether the job was spauned using mpi. If I start it on the node, it does not kill communications. If I start it from a head node, I can still ping. I have only tried the 2.2 kernel job as a stand-alone. There it exits quite gracefully with exit 139. Do yo

Re: Very wierd behavior on new nodes

2003-01-07 Thread Colin Watson
On Mon, Jan 06, 2003 at 09:48:31PM -0700, Arthur H. Edwards,1,505-853-6042,505-256-0834 wrote: > Now the program dies with an exit 139, but the system stays up. > > What is an exit 139? 139 = 128 + 11 = signal 11 = segmentation fault. -- Colin Watson [[EMAIL PR

Re: Very wierd behavior on new nodes

2003-01-07 Thread Ron Johnson
On Mon, 2003-01-06 at 22:48, Arthur H. Edwards,1,505-853-6042,505-256-0834 wrote: > I'm having monumental difficulty getting a new set of PC's working. I > had been installing a 2.4.19 kernel with debian on a MB with a via chip > set, and athlon XP2100, a promise ide system. Debian semms to insta

Very wierd behavior on new nodes

2003-01-06 Thread Arthur H. Edwards,1,505-853-6042,505-256-0834
I'm having monumental difficulty getting a new set of PC's working. I had been installing a 2.4.19 kernel with debian on a MB with a via chip set, and athlon XP2100, a promise ide system. Debian semms to install correctly. However, when running large fortran jobs (under g77-3.2), the system wou