On Wed, 15 Sep 1999 22:01:02 +0100 (GMT), Tim Waugh
<tim@cyberelk.demon.co.uk> said:
> Here's an oops that came out of 2.2.13pre4. This bug has been around for
> most if not all of the 2.2 series, as far as I can tell.
> Has anyone else seen this kind of thing before?
Well, I've never seen this particular one reported anywhere through
2.2. What you are looking at seems to be:
> eax: e0292c18 ebx: 00000008 ecx: e0292c18 edx: c0fc15c0
^ ^
single-bit memory corruption. The usual suspects in these cases are
overheated CPU, or memory. Disable L1 and/or L2 cache often clears
things up (and points to the fault).
--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/