On Fri, 31 Mar 2000, Stephen C. Tweedie wrote:
> That almost always just means that the kernel has a pointer to a
> structure, that the pointer is NULL, and that the code in question
> has tried to access a field at offset 8 bytes into the structure.
> Still looks like a null pointer dereference to me.
Yep, I see that now. Still, yesterday I removed a DIMM out of my machine
on suspision it was faulty and since then I haven't had any oopses, even
when running dbench tests for getting on 4 hours streight. I don't know
what the memory addresses I was seeing in my oopses means - they were all
of the pattern 0101010X, which looked peculiar to me - but the fact that I
added a new 128Meg DIMM about 3 weeks ago, and the funny addresses,
pointed me to suspect bad memory in my comp.
But now, the call trace in mine and Joerg's oopses is nearly identical,
and this aseems to point the finger back at the code....
If I don't get any more oopses soon, I will probably put the suspect
memory back in and maybe I'll see some then. I don't know what else to
do.
Lawrence
-
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 : Fri Mar 31 2000 - 21:00:29 EST