> Anyone know of a utility to extensively test a system's ram, in order to
> determine whether the ram has any faults?
It's called gcc :)
Seriously, a 24-hour repeated kernel compile will stress your memory much
harder than things like memtest86 (sunsite:/pub/linux/handware/somewhere)
because the CPU, RAM, cache and various other peripherals are working
hard, and probably not following some easily identifiable pattern.
( while true; do
make dep clean zImage modules
done ) >/dev/null 2>/tmp/errlog &
and wait. After a day or so, grep /tmp/errlog for "signal" (usually 11 or
6). Short of a gcc error (relatively unlikely :) each of those signals is
a bit-flip. (Don't rely on al of them being caught, either.)
See http://bitwizard.nl/sig11/ for more information.
Matthew.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/