From owner-freebsd-questions  Fri Oct  6 03:44:33 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA22806
          for questions-outgoing; Fri, 6 Oct 1995 03:44:33 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA22799
          for <questions@freebsd.org>; Fri, 6 Oct 1995 03:44:27 -0700
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id DAA27409; Fri, 6 Oct 1995 03:41:50 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id DAA00469; Fri, 6 Oct 1995 03:43:10 -0700
Message-Id: <199510061043.DAA00469@corbin.Root.COM>
To: Julian Elischer <julian@ref.tfs.com>
cc: elh_fbsd@spnet.com, questions@freebsd.org, elh@spnet.com
Subject: Re: kernel options for > 64mby 
In-reply-to: Your message of "Fri, 06 Oct 95 03:32:16 PDT."
             <199510061032.DAA07467@ref.tfs.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 06 Oct 1995 03:43:10 -0700
Sender: owner-questions@freebsd.org
Precedence: bulk

>well if you get an NMI you can pretty safely assume it's past the end of memory
>then, as you just WROTE there as part of the ram test..
>works like a charm here..

   :-)
   Someone told me that certain revision Compaq motherboards generate
RESET rather than NMI for parity errors. The source of that information is
often unreliable, however, so this might just be fantasy.

-DG