From owner-freebsd-hackers Fri Apr 7 11:18:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 10C8B37BE5E for ; Fri, 7 Apr 2000 11:18:08 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id LAA76324; Fri, 7 Apr 2000 11:17:54 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: wc.bulte@chello.nl Cc: "Koster, K.J." , "'Bob.Gorichanaz@midata.com'" , "'FreeBSD Hackers mailing list'" Subject: Re: bad memory patch? In-Reply-To: Message from Wilko Bulte of "Fri, 07 Apr 2000 15:36:46 +0200." <20000407153646.A7558@yedi.wbnet> X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Fri, 07 Apr 2000 11:17:54 -0700 Message-ID: <76320.955131474@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not necessarily a bad idea, but certainly incomplete. Being able to detect and run with bad RAM is only about halfway there. The other half is being able to remove and replace the bad RAM without taking the machine down. Like some of the old mainframes (ie TOPS-10, I think). This not only needs quite a bit more hardware support, but the software also has to be able to shuffle everything else out of the bad DIMM/SIMM/thunk into good memory before it's pulled and replaced. If you have to take the machine down anyway to replace the bad RAM once it's detected, you may as well just use a good ECC design instead. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message