Memory type? (ECC vs non-ECC) - memory testing
jared_hodge at iat.utexas.edu
Mon Aug 20 11:43:20 PDT 2001
Actually, parity memory will usually detect the errors (usually, as in
as usually as ECC will correct them). You can set up the BIOS (assuming
it supports Parity memory) to halt on a memory error (or there may be
other, more viable options). I'd stay away from non-parity if possible.
Thomas R Boehme wrote:
> > i think that the scope of the question for "how certain you are of the
> > results of the computation" is beyond the scope of memory and should also
> > include cpu, disks, io, motherboard, cables, programs, etc..etc..
> That is correct. Like I said, our problems were heat related and not a
> memory problem.
> > -- when was the last time you had a memory failure compared to
> > other things that needed fixing...
> > - power cable, programming bugs, disk cabling, etc..etc..
> Well I don't know - without ECC I have no way of telling when I had the last
> memory failure. And with all the bad cheap memory chips out there, I would
> prefer knowing it. That's why ECC makes sense.
> Sure, it is not the only source. And I do agree that programming bugs are
> probably the biggest problem that can't really be fixed.
> I know my codes have numerous bugs -- I just don't know where :-)
> Bye, Thommy
> Beowulf mailing list, Beowulf at beowulf.org
> To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
Institute for Advanced Technology
The University of Texas at Austin
3925 W. Braker Lane, Suite 400
Austin, Texas 78759
Email: Jared_Hodge at iat.utexas.edu
More information about the Beowulf