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 a lilo or grub entry for it (if the package didn't do this for you), and select it on the next boot. Otherwise, it will not run at all. > 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 and got the same > behavior. My only insight is that, under the 2.2 kernel, when I left > the machine alone (no other jobs running) it stayed up. When I invoked > vi, the job crashed with an exit 139 (seg violation) I would guess this really is a hardware problem (RAM, cache or CPU) Frank > > Art Edwards > > On Tue, Jan 07, 2003 at 05:14:49PM +1100, David Cureton wrote: > > Compilers are very good tools for finding memory problems. I would suspect > > the system memory may be bad. Especially given it is a new system of which > > you have not had a chance to gain confidence in. Have a look at the memtest86 > > package that you can use to test the memory of the system. > > > > Just a thought, > > > > Cheers > > David > > > > On Tuesday 07 January 2003 15:48, Arthur H. > > Edwards,1,505-853-6042,505-256-0834 wrote: > > > tal 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 would either die immedieately, or start running and then die. > > > When I say die I mean that I can't login. I have backed off to a 2.2.20 > > > kernel and g77 2.95. Now the program dies with an exit 139, but the > > > system stays up. > > > > > > What is an exit 139? > > > > > > -- > Arthur H. Edwards > 712 Valencia Dr. NE > Abq. NM 87108 > > (505) 256-0834 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
