On Fri, 31 Mar 2000, Lawrence Manning wrote:
> 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.
I'm seeing similar problems (either an Oops, BUG(), hang or random SEGVs)
under a heavy write load. So far I haven't reproduced it under pre1, but
that might be simply due to the fact that it isn't nearly as swap happy as
pre3. Hopefully one of the patchlets in pre2 will turn out to be the
culprit.
-ben
-
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