I filtered out the repeated messages and found this. Is this of any help?
Found repeated reference to this.
May 10 07:47:22 Lain inetd[577]: fork: Cannot allocate memory
Found this only a couple of times.
May 10 07:50:34 Lain kernel: Unable to handle kernel NULL pointer
dereference at
virtual address 00000010
May 10 07:50:34 Lain kernel: current->tss.cr3 = 00101000, %cr3 = 00101000
May 10 07:50:34 Lain kernel: *pde = 00000000
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Anthony Barbachan" <barbacha@hinako.ambusiness.com>
Cc: <linux-kernel@vger.rutgers.edu>
Sent: Wednesday, May 10, 2000 5:48 PM
Subject: Re: Error in 2.2.14 and 2.2.15: kmem_alloc: Bad slab magic
(corrupt) (name=buffer_head)
> >
> > May 6 11:58:12 Lain last message repeated 137 times
> > May 6 11:58:12 Lain kernel: kmem slab magic (corrupt)
(name=buffer_head)
>
> Unfortunately your log starts after whatever triggered this. Something
> be it code or hardware caused memory corruption. If it was anything like
> an I/O error or an oops first its been lost from your log
>
-
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/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:16 EST