Re: Possible dcache BUG

[Chris Shoemaker]

On Thu, Aug 05, 2004 at 11:33:44AM +0300, Denis Vlasenko wrote:
> 
> You may use cpuburn to test RAM/CPU too.
> 
> Although I have a memory which, when clocked a bit too high,
> pass both memtest86 and cpuburn for extended periods of time,
> yet large compile runs die with sig11 sometimes. Using a tiny
> bit less aggressive clocking helped. :)
> -- 
> vda

Oh yes, now I remember that it was you who recommened cpuburn to me back
in April/May or so.  I also was suspicious that neither memtest86 nor
cpuburn were really stressful enough, but the large-compiles-in-a-loop
weren't any better for me.  I would _love_ to just have some confident
test to say "yep, your hardware is bad, go buy a shiny new box"  :)

I've seen memtest86 actually find bad RAM on a machine before, so I know
it works _sometimes_.  Can anyone say the same for cpuburn?  What does
a failure look like, and were there correlated symptoms like kernel oopses?

-chris
> -
> 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/
-
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/