From owner-freebsd-hackers  Mon Apr  3 20:54:01 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA01486 for hackers-outgoing; Mon, 3 Apr 1995 20:54:01 -0700
Received: from seagull.rtd.com (root@Seagull.rtd.com [198.102.68.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA01459 for <freebsd-hackers@freefall.cdrom.com>; Mon, 3 Apr 1995 20:53:59 -0700
Received: (from dgy@localhost) by seagull.rtd.com (8.6.9/8.6.9.1) id UAA24847 for freebsd-hackers@freefall.cdrom.com; Mon, 3 Apr 1995 20:53:38 -0700
From: Don Yuniskis <dgy@seagull.rtd.com>
Message-Id: <199504040353.UAA24847@seagull.rtd.com>
Subject: NMI message
To: freebsd-hackers@freefall.cdrom.com (FreeBSD hackers)
Date: Mon, 3 Apr 1995 20:53:38 -0700 (MST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 462       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

Greetings!
    My 1.1.5.1R system gasped:
	NMI... going to debugger
	kernel: type 19 trap, code=0
shall I assume this was an intermittent parity error (system had been
up for 40 days or so...) like maybe a Vcc glitch or alpha particle, etc.?
Haven't dug out any schematics, etc. but I suspect parity is the only
thing that would yank on NMI (looked like CPU was doing a memory to memory
transfer at the time ... possibly faulting in a page, etc.)
    Thx, --don