From owner-freebsd-stable Sun Mar 12 11:33:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id 4FC9137BCAD for ; Sun, 12 Mar 2000 11:33:19 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA08972; Sun, 12 Mar 2000 11:34:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003121934.LAA08972@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Carroll Kong Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Detecting ECC errors In-reply-to: Your message of "Sun, 12 Mar 2000 14:33:10 EST." <4.2.2.20000312143119.00b4f300@email.eden.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Mar 2000 11:34:49 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. I took a look over the archives and noticed this ancient > thread. (1998) However, I checked the handbook and LINT for options on > how FreeBSD logs ECC errors, but I could not find anything. Has this > finally been implemented? Or is there currently no way for the OS to > detect the # of corrections / detections of errors by DIMM slot? You're correct; there isn't. It's a relatively simple task that's been waiting for a junior hacker to come along and take it up. It's also devillishly difficult to _test_ such code... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message