cpuburn will help you rule out defective CPU theory.
Also you can start removing/swapping hardware parts.
> I would appreciate any insight anyone can provide. Let me know if I
> can provide any more info.
Test with some vanilla 2.4 kernels, not a distro one. If 2.4.20 crashes,
try some of the earlier kernels too. Compile them for 386 uniprocessor
with debugging and magic SysRq enabled. Provide your .config
Run your klogd with -x to make it stop decoding oopses.
Run oopses thru ksymoops and provide result.
Provide lsmod, lspci output, some of /proc/* files (interrupts etc)
> I haven't suscribed to this ML because I don't want the volume in my
> mailbox - but will monitor this thread through google groups.
People are going to CC you I believe, so don't worry.
-- vda- 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/