From owner-freebsd-stable Thu Oct 22 15:35:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13396 for freebsd-stable-outgoing; Thu, 22 Oct 1998 15:35:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13388 for ; Thu, 22 Oct 1998 15:35:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01440; Thu, 22 Oct 1998 15:37:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222237.PAA01440@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis cc: Burkard Meyendriesch , freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your message of "Thu, 22 Oct 1998 15:17:26 PDT." <199810222217.PAA17041@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 15:37:06 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Oct 22, 11:57pm, Burkard Meyendriesch wrote: > } Subject: Re: ECC memory support > > } But my original questions are still pending: Isn't there any possibility > } to detect 1-bit errors even if they are detected and corrected by my > } ECC electronics? Isn't there any register of the 82430HX chip set which > } can be examined after an memory error NMI? > > Yes there is. It's documented in the chipset datasheet that you can > download from Intel's web site. Also your BIOS should have a setting > to configure whether a 1-bit error causes an NMI. > > The last time this subject came up, some folks wanted to use the BIOS > (which should understand the chipset on that motherboard) to retrieve > this information rather than build knowledge of specific chipsets into > the kernel. That would be the "nice" way to do it. I haven't made much progress pursuing things related to DMI lately, and it does look as though the way Microsoft want to do it you need to have motherboard-specific drivers installed. Some systems will preserve it in the BIOS event log, which theoretically can be retrieved - there's no guarantee that you will be able to arrange a trap on soft ECC, so you may have to live with this sort of deferred notification. There may also be some hope via ACPI, but more on that in a separate message. > On an unrelated thread, someone mentioned that there were some unresolved > issues with rearming NMI. Steve Passe (fsmp@freebsd.org). I don't recall if he was going to pass his code/comments back or not. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message