Top Document: SGI hardware Frequently Asked Questions (FAQ) Previous Document: -17- How can I find a bad SIMM? Next Document: -19- Should I worry about a "recoverable memory parity error"? See reader questions & answers on this topic! - Help others by sharing your knowledge Date: 30 Apr 1994 00:00:01 EST Dave Olson <olson@sgi.com> explains: Long, long story. Short synopsis: if you don't get memory errors, don't worry about it. Slightly longer: A number of vendors' 16 Mbit chips had a bug in them. We found it, and they agreed it was their bug, but they were looking at a long, long DRAM spin time, so we worked around it in a new rev (rev C) of the memory controller. The symptom was primarily parity errors; this could be confused with the other parity error problem we have, thus the warning message in 5.2. At least some of the vendors that had the problem should have fixed DRAM shipping by now, which is not to say that SIMMs you buy now have the new DRAMs on them. Not all vendors had the problem. User Contributions:Top Document: SGI hardware Frequently Asked Questions (FAQ) Previous Document: -17- How can I find a bad SIMM? Next Document: -19- Should I worry about a "recoverable memory parity error"? Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: sgi-faq@viz.tamu.edu (The SGI FAQ group)
Last Update March 27 2014 @ 02:12 PM
|
Comment about this article, ask questions, or add new information about this topic: