True.
> memtest86 is great becuase it ONLY tests memory.
Yes, and because it also accurately tells you which memory location is bad.
(This can't be easily done from user space, I gather). You can use this
information to workaround the memory problem with the BadRam patch from Rick
Van Rein.
> CPUburn is similarly specific. A memory bus buster would be a good tool
> to add to the mix. (DMA is another common problem, but the more I look
> into it, the more it seems to be dependent on whatever peripheral you're
> talking to, which is more complication than I'm looking to bite off...)
True.
> It might be possible to put all three testers into a menu where you could
> switch on and off what you wanted to test, and run them overnight. That way,
> if you are testing for three things (perhaps alternating tests every few
> minutes?), and you get it to fail, you can switch some off to get more
> specific tests to narrow down the problem...
Actually lilo is just about enough for a such menu system...
Something like
image = /boot/memtest86
label = memtest86
image = /boot/vmlinux
label = cpuburn
root = /dev/hda2
append = "init=/usr/local/bin/burnP6"
read-only
image = /boot/vmlinux
label = cpuburn
root = /dev/hda2
append = "init=/usr/local/bin/testDMA"
read-only
It would take some scripting to alternate the tests automatically, but
perhaps it could be done.
> I've heard of ceberus but thought it was just a disk test suite... One more
> thing to download and look into... (If the tests in it can be switched
> on/off, maybe this is what I'm looking for...)
AFAIK it's a pretty complete test suite VA uses (used?) for testing their
hw. I'm not sure, though.
-- v --
v@iki.fi
-
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/