Re: Ram lost.

Michael Neuffer (neuffer@nomis.i-Connect.Net)
Mon, 3 Mar 1997 17:34:13 -0800 (PST)

On Mon, 3 Mar 1997, Chad Page wrote:
> At least with parity
> or ECC a less experienced user will be able to know for sure if it's the
> memory or not and can adjust memory timings and/or replace simms
> accordingly depending on the problem. I've gotten a 'bug' report on the
> ramdisk driver caused by someone with ~224MB of non-parity memory - and
> one of the simms became flaky and corrupted kernel buffer-cache tables. Ouch.

Using larger amounts of memory WITHOUT PARITY or ECC is madness.

Even in "stable" systems you will always have twiches where here or there
a bit flips for whatever reason in otherwise perfectly OK memory.
In large machines (in terms of Gigabytes of memory) this is a
normal fact of life.

The problem just scales down when you have less memory, but it still


Michael Neuffer i-Connect.Net, a Division of iConnect Corp.
mike@i-Connect.Net 14355 SW Allen Blvd., Suite 140
503.641.8774 Beaverton, OR 97005