Stephen,
Could also be SMP corrupting memory since the buffer cache is not
threaded in 2.2.15 (perhaps theres a driver race condition). I've seen
a similiar Oops while calling ll_rw_block() without lock_kernel() being
called on SMP systems. He should try a different system or replace the
memory and if the problem persists, get a listing of what apps/drivers
he's running.
Hey, hows EXT3 coming? When is it getting rolled is as Default?
:-)
Your friend,
Jeff
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Tue, May 16, 2000 at 09:49:04AM +0200, Michael Stiller wrote:
> >
> > we use 2.2.15 at our company's samba/nfs server. This is a PIII machine
> > (UP) using 128Mb Ram
> > and about 17 Gb disk. Every morning i get (mostly non-fatal) Oops
> > messages which look
> > like a buffer list corruption to me. The location in the code is
> > fs/buffer.c:find_buffer
> > Something seems to corrupt the buffer list, the value of
>
> It's bad memory, 99% sure.
>
> >
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000834
> > eax: 00000800 ebx: c6db75c0 ecx: c6db75c0 edx: c62a8e00
>
> You've got 0x00000800 in %eax, and the oops is on a field access
> for a structure at that address. There's a null, list-terminating
> pointer in the buffer chains which has had a single bit flipped to
> one. This is nearly always bad ram, but it can also be cache or
> an overheating CPU. It definitely sounds like hardware, though.
>
> --Stephen
>
> -
> 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/
-
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 : Tue May 23 2000 - 21:00:13 EST