Messages in this thread | | | Date | Sat, 17 Mar 2001 14:04:02 -0500 | From | John Jasen <> | Subject | Re: [OT] how to catch HW fault |
| |
On Sat, 17 Mar 2001, Aaron Lunansky wrote:
> It could very well be your ram (I don't suspect the cpu). If you can, try a > different stick of ram.
I've found a good exercise for exercising memory faults is to recompile the kernel with a -j16 flag; and in a second virtual console, do something like dd if=/dev/hda of=/dev/null bs=2048k
Either the kernel compile will fail with a sig11, or the dd will fail and lock the system, in my experience.
I've used this method, crudely, to chase down memory problems in systems using 256-512MB ram.
YMMV.
-- -- John E. Jasen (jjasen1@umbc.edu) -- In theory, theory and practise are the same. In practise, they aren't.
- 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/
| |