From owner-freebsd-hackers Sat Oct 25 15:30:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27480 for hackers-outgoing; Sat, 25 Oct 1997 15:30:49 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA27472 for ; Sat, 25 Oct 1997 15:30:45 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xPEhd-0006IQ-00; Sat, 25 Oct 1997 15:29:06 -0700 Date: Sat, 25 Oct 1997 15:29:02 -0700 (PDT) From: Tom To: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson cc: freebsd-hackers@freebsd.org Subject: Re: Parity Ram In-Reply-To: <345269F0.446B9B3D@est.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id PAA27474 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 25 Oct 1997, [iso-8859-1] Žoršur Ivarsson wrote: > Tom wrote: > > > > On Sat, 25 Oct 1997, Jamil J. Weatherbee wrote: > > > > > Can someone fill me in on when you would want to use parity ram as opposed > > > > Why? To discover memory problems before they corrupt data, and cause > > random panics, core dumps, hangs, or file system corruption. Personally, > > I use ECC capable motherboards that can actually use parity to fix some > > errors. > > You need EDO ram I think for this to work, You need some memory to keep > information of what is in your memory before. No. EDO is just like regular DRAM, except the timing is different (faster). ECC uses the parity bits in regular parity RAM. Tom