From owner-freebsd-hardware Thu May 16 03:59:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA17561 for hardware-outgoing; Thu, 16 May 1996 03:59:42 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA17537; Thu, 16 May 1996 03:59:29 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA19331; Thu, 16 May 1996 12:59:08 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA15713; Thu, 16 May 1996 12:59:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id MAA01458; Thu, 16 May 1996 12:31:53 +0200 (MET DST) From: J Wunsch Message-Id: <199605161031.MAA01458@uriah.heep.sax.de> Subject: Re: Triton chipset with 256k cache caches 32M only? To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 16 May 1996 12:31:53 +0200 (MET DST) Cc: jgreco@brasil.moneng.mei.com, davidg@Root.COM, mmead@Glock.COM, joerg_wunsch@uriah.heep.sax.de, blh@nol.net, hackers@freebsd.org, hardware@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199605151704.KAA04912@GndRsh.aac.dev.com> from "Rodney W. Grimes" at "May 15, 96 10:04:45 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Rodney W. Grimes wrote: > > > ECC has single bit error correction and 2 bit error detection. Better than > > > parity no matter how you slice it. > > Only if you have memory that is failing or you need extreamly reliable > operation (good memory should have a single bit error rate of something > like 1 in 10 years). I think most of the memory problems we've been observing lately are not related to the RAM itself, but rather to other hardware problems (timing, EMC problems). Remember all the reports about ``strange sig 10/11's'' or the Winbloze ``general protection failure'' mess where you never know whether it's actually hardware or rather an o/s failure. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)