From owner-freebsd-hardware Fri Dec 31 4: 0: 2 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 1458F15091 for ; Fri, 31 Dec 1999 03:59:59 -0800 (PST) (envelope-from robert.schofield@philips.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id MAA24016 for ; Fri, 31 Dec 1999 12:59:57 +0100 (MET) (envelope-from robert.schofield@philips.com) From: robert.schofield@philips.com Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma024014; Fri, 31 Dec 99 12:59:57 +0100 Received: from notessmtp-nl1.philips.com (notessmtp-nl1.philips.com [130.139.36.10]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id MAA00679 for ; Fri, 31 Dec 1999 12:59:57 +0100 (MET) Received: from EHLMS01.DIAMOND.PHILIPS.COM (ehlms01sv1.diamond.philips.com [130.139.54.212]) by notessmtp-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id MAA28791 for ; Fri, 31 Dec 1999 12:59:56 +0100 (MET) Received: by EHLMS01.DIAMOND.PHILIPS.COM (Soft-Switch LMS 4.0) with snapi via EMEA2 id 0056890007714602; Fri, 31 Dec 1999 12:59:54 +0100 To: Subject: RE: ECC RAM useless with FreeBSD? Message-ID: <0056890007714602000002L922*@MHS> Date: Fri, 31 Dec 1999 12:59:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; name="MEMO 12/31/99 12:58:04" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >The SCO Unix I am using on my multi-processor DEC has an ECC daemon ru= nning >to carry this out, almost exactly as you describe; I think it can corr= ect one >bit errors. >The hardware must correct the errors. Maybe the daemon supports turni= ng >this on, and detecting what's happening. Yup, the hardware does the correction work and the running daemon polls= the ECC hardware for info so that it can be tabulated and logged. I seem to remember it can handle requests from clients asking for stati= stics for plotting fault rates, etc. and there is something about=20 memory pool management, hardware management and activity control too. Rob Schofield -- "Not quick, but brilliant!" - quote from a (good) friend. = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message