--- "Douglas J. Hunley" <[EMAIL PROTECTED]> wrote:
> On Thursday 09 August 2001 14:39, Net Llama babbled:
> >
> > Oops's are rarely that easy to resolve. In fact, they are very,
> very
> > rarely hardware based.
> >
> > Without more information, this is all purely speculation.
>
> to try memtest on it..
>
> what more info would help Lonni?
Mike thinks its memory. I'd say its rather difficult to determine that
without some more evidence. First, are there any other errors in
messages prior to the Oops?
If you want to test the memory hypothetis, and do not have spare memory
on hand, then you basically have 2 options:
1) memtest86 www.memtest86.com : run it for at least 24 hours. Errors
appear in real time.
2) Cerberus : http://sourceforge.net/projects/va-ctcs : this will do
very rigorous hardware loading of the system. Memory, HD, CPU, mobo
will all get heavily tested. Run for at least 24 hours. Errors appear
in real time.
With either of these the box will really need to be taken out of service
during the testing. This all, of course, assumes that there is a
hardware problem. However, realistically, hardware problems exhibit
themselves in other fashions, and not via a kernel Oops.
=====
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J. Friedman [EMAIL PROTECTED]
Linux FAQ & Step-by-step help: http://netllama.ipfox.com
.
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
