Re: Possible dcache BUG

[Denis Vlasenko]

> > I think, based on the last 25 hours of running both memburn and
> > setiathome at a -nice 19, and there have been no errors, that I might
> > have stumbled onto a fix.
> >
> > It seems the dram is marked DDR400, so I was trying to run it that
> > way.  Unforch, on checking the invoice for the umpteenth time, it
> > finally dawned on me that this particular AMD 2800XP is supposedly a
> > 333mhz FSB chip, and not rated for use with DDR400 memory.  Switching
> > the bios setting for the memory to 'auto' from 'spd' seems to effect
> > this particular item, and the memory now signs in as DDR333 Dual
> > Channel.
> >
> > And after 25 hours, no errors, nothing unusual in the logs.
> >
> > I guess I should go paint my face with egg or something...
>
> Not necessarily.  :-)  Some mobos based on the nforce2 chipsets should be
> able to clock FSB and memory asynchronously.   The very fact that you can
> set the memory clock separately in the BIOS indicates that your mobo is one
> of these. So, if it runs well at synchronous FSB and memory clock rates,
> but causes problems otherwise, the northbridge is probably fishy.  Or the
> memory is not up to the spec.  Anyway, the symptoms are quite "interesting"
> and it's good to know what they are.

The best thing is, we got another RAM test program which seems to be better
than memtest86 in some cases!
--
vda

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