[lkml]   [2001]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: oops on 2.4.13-pre5 in prune_dcache

On Wed, 31 Oct 2001, Udo A. Steinberg wrote:
> For what it's worth - I've had a very similar oops ages ago. Back then it
> was blamed on bad RAM, but ever since then I've run numerous memtest's
> over it without finding anything and never had any problems later either.
> See here:

Indeed. Same exact thing, different bit.

It could easily be a wild pointer corruption - single-bit errors in RAM
are not entirely uncommon (and as Al points out, they usually end up
showing up in things like the dcache which can have long lists that are
traversed fairly infrequently).

But blaming the thing on bad RAM is not a good strategy if there are many
of these reports. I'd love to see more of a pattern, though, because
without a pattern there is nothing to really start from..

The pattern might be something as simple as "we're both using minixfs"
or whatever.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.117 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site