Re: Strange disk corruption with Linux >= 2.6.13

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Sat, Oct 01, 2005 at 06:28:06PM -0300, Rog?rio Brito wrote:
> Right now, I'm using just a single 512MB module, but it is single-sided
> (I guess that by double-sided you guys mean that it has chips on both
> sides of the module, right?). The only double-sided module that I have
> here is the 256MB module.
> 
> OTOH, with just one 512MB everything *seems* to be working fine, but,
> honestly, I'm not sure.

Well maybe a single sided 512M can still have the same interface as a
double sided.  Depends how it is wired I suppose.

> Hummm, nice to see that you have also experienced this. With 256 + 128,
> I had to use PC100 to have it work stably.
> 
> I'd obviously prefer to have everything working at PC133 speed, but
> wouldn't mind running at PC100 speed if I could use everything, since I
> sometimes need to use some large programs (for some dynamic programming
> problems).

Actually you probably DON'T want the ram to run PC133 since at PC133 the
latency is a bit higher (in clock counts) than at PC100, so overall the
latency stays about the same.  On the other hand running the ram
asynchrounous from the front side bus of the cpu makes getting memory
access aligned more complicated and inserts different delays.  So most
likely the system really runs fastest when the ram matches the cpu bus
speed which on an A7V is 100MHz (since it never did actually support any
133FSB cpus, you needed the fixed KT133A chipset for that that the A7V-E
had on it).  I also only run a 700MHz cpu so heat isn't a problem.  I
know the 1GHz cpu made a lot of heat and really needed good cooling.  I
don't remember what cpu speed you have.

Len Sorensen