Re: how to determine the cause of kernel lock ups

Hirling Endre (
Tue, 13 Jul 1999 10:10:55 +0200 (CEST)

On Tue, 13 Jul 1999, Petru Paler wrote:

> On Mon, Jul 12, 1999 at 01:40:14PM -0400, Jon 'tex' Boone wrote:
> > I tried looking through the kernel messages that klogd puts in
> > syslog, but when the machine locks up, nothing is logged. Rebooting
> > is enough to start the system working again, although heavy use will
> > cause it to lock up again.
> >
> > Any thoughts?
> I had the same problem and it was caused by a bad DIMM.

And how do you determine whether your DIMM is bad? I have the above
problem too - except that it only shows in X -, and I've tried running
md5sum-s several times or compiling kernel, but those showed no error.

How can one determine _if_ the lockup is caused by bad hardware, and
if it is, _which_ piece of hardware is bad?

(I have an old Trident 9680, a K6-2/300, 128M RAM, an SMC Ultra ISA
and an NE2k PCI Ethernet card, two IDE disks and an IDE cd-rom. Nearly
the same hw worked fine with a 486 dx4-100 w/64M RAM)


..all in all it's just another rule in the firewall. 

/Ping Flood/

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to Please read the FAQ at