Re: Oops with 2.4.23

[Mike Fedyk]

On Mon, Dec 22, 2003 at 01:36:12PM -0500, Disconnect wrote:
> Evidently many people can look at an oops or crash path and be 90%
> certain its bad/misperforming memory.  (How they do this I don't
> know..)  I've noticed that 'check your ram' is not always given as the
> answer, but it seems that most of the time when it is given its also
> correct.

Single bit changes on high bits (especially when they're not used in any bit
tests), are usually suspect from what I see on the list...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/