Remember, the memory itself is only one area where there might be problems.
There are other memory related areas including the following that are not
covered by ECC memory:
North bridge (memory controller)
L1/L2/L3 cache levels (some processors have ECC checking in the cache)
Register corruption
In addition, the transfers between the CPU and memory could be corrupted in
transit before the ECC checksum is calculated (I've actually seen this happen
on a poorly designed motherboard). In other words, there are a lot of things
that could be wrong, see the FAQ in CTCS for more of my ramblings on the
subject.
One way to tell whether or not your memory is the problem is by examining your
files/coredumps for corruption. If entire page-sized chunks have been
substituted with chunks from other files, pages in RAM, etc, you're likely
dealing with a kernel MM bug rather than memory corruption. (I suppose an MMU
bug is possible too.. sigh...) A few bits swapped here and there points to
hardware/faulty memory. That's one reason why my memory checker displays that
nice context information, so those sorts of determinations can be made.
> I've just tried test 2 on another machine (with good memory) and it looks
> like it's a bug in memtst rather than the detection of an error.
This doesn't surprise me too much, the software is pretty new. The fact that
the expected and resulting memory contents in the log is the same would seem to
confirm that, plus the fact that the 'error' happened on the first byte in the
test array and other strange things. :) A quick check confirms it breaks for
me too, so I'll find this bug and whack it in a new release. Expect something
this weekend.
-- Jason T. Collins "Noone has lived to see even three of my techniques. It Software Engineer is almost sunset. How many will you see before you die?" VA Linux Systems 'Twilight' Suzuka, "Creeping Evil" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/