Date: Tue, 17 Sep 1996 20:21:06 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: asami@FreeBSD.org (Satoshi Asami) Cc: current@FreeBSD.org Subject: Re: RAM parity error Message-ID: <199609180321.UAA01366@GndRsh.aac.dev.com> In-Reply-To: <199609180222.TAA09684@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Sep 17, 96 07:22:06 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> * If you have ``logic parity'' instead of true parity you have defeated > * 75 % of the purpose of even having parity on memory. > > 75%? I thought that was 100% ;) (Ok, maybe it can check the memory > bus failure, but how often would that happen?) > > * I would highly > * encorage you to try a swapout with some ``real parity'' memory and > * more than likely watch your problem go away... > > I'd never buy a "logic parity" board myself, but unfortunately, these > machines are donated to our project (they aren't even supposed to be > running FreeBSD!) so I can't change anything in them. :( > > So, do you think this is a memory problem? Yes, ``memory parity error'' == hardware fault in the memory subsystem. > Is there some other test I > can run, other than stressing the SCSI system? Yes, ``make world''. > (It doesn't crash when > I run the "fast bcopy" benchmark, and I think that thing stresses the > memory system a lot....) That is only stressing the memory system from the ``host'' port, not from the PCI bus master port. Interactions between the two is what really streeses the memory system to the limits. > > Satoshi > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609180321.UAA01366>