Another good test to run when you suspect bad hardware is the so called gcc test. Grab a linux kernel source and untar it anywhere you like with
tar zxvf linux2.4.20.tar.gz the cd into the directory it created and do the following make mrproper make menuconfig in the menuconfig program just immediately select exit and save the changes then do mek dep make bzImage make modules if at any point in the make bzImage or make modules the compilation stops on an error, go back in the output and look for "signal 11" if you see "signal 11" anywhere your hardware is almost certainly screwed. It could be CPU, cache memory or main memory if you see a signal 11. The following link has more information on this test and what it means. http://www.bitwizard.nl/sig11/ ----- Original Message ----- From: "Trevor Lauder" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, February 02, 2003 8:02 PM Subject: Re: (clug-talk) (RH8-Dell D. 2350) crashes > That doesn't make a difference with this problem :) Here is the link to > the memtest program everyone is recommending.... http://www.memtest86.com > > I have used it a lot and would highly recommend it. However, just because > it tells you there are errors doesn't mean the memory is bad. And just > because it tells you there are no errors doesn't mean the memory is good > :) I know that sounds dumb, but it's true. Computers is not an exact > science.... especially when it comes to testing errors in memory :) If > the program tells you there are errors, it could be bad memory but it > could also just be incompatible with the motherboard. In this case bad > memory would be the safe assumption over incompatibles as the computer was > a "package" from Dell. > > Cheers, >
