Re: >64MB RAM problems, why?

From: David Whysong (dwhysong@physics.ucsb.edu)
Date: Wed Apr 05 2000 - 17:40:09 EST


On Wed, 5 Apr 2000, Richard B. Johnson wrote:
>On Wed, 5 Apr 2000, Bob Lorenzini wrote:
>> On Wed, 5 Apr 2000, Richard B. Johnson wrote:
>>
>> > Upon startup Win/NT writes to (most) all RAM above 1 Megabyte, then reads
>> > it back. You can watch this with a logic analyzer. It does this with
>> > parity-check disabled and, FYI, never enables it after.
>> >
>>
>> Your saying parity memory is totally useless on Win/NT?
>>
>> Bob
>
>Well. It may be useless on most modern RAM. I haven't seen any
>RAM, rated at 100MHz or higher (P100) that even has the extra bit.
>
>The last time I saw parity RAM was the 65 ns stuff. PC RAM Vendors,
>when questioned, have responded; "It's now built-in...". Which
>translated means; "Missing...".
>
>None of the PC stuff ever corrected RAM errors with a CRC, even though
>there was some RAM called "ECC" RAM which implied that it did. The
>ECC RAM just accumulated bits from multiple columns to save parity
>bits. It still hit MNI when it detected an error. Alpha and Suns
>have (or had the last time I looked), real ECC RAM.

Are you sure? I have PC100 ECC SDRAM. My BIOS claims the ability to
correct single bit errors and catch (NMI) two bit errors.

There is a BIOS setting to the effect of "cause NMI on single-bit
correction."

Dave

David Whysong dwhysong@physics.ucsb.edu
Astrophysics graduate student University of California, Santa Barbara
My public PGP keys are on my web page - http://www.physics.ucsb.edu/~dwhysong
DSS PGP Key 0x903F5BD6 : FE78 91FE 4508 106F 7C88 1706 B792 6995 903F 5BD6
D-H PGP key 0x5DAB0F91 : BC33 0F36 FCCD E72C 441F 663A 72ED 7FB7 5DAB 0F91

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:15 EST