From owner-freebsd-current@FreeBSD.ORG  Thu Jun 10 19:31:20 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B6F0816A4CE
	for <current@FreeBSD.org>; Thu, 10 Jun 2004 19:31:20 +0000 (GMT)
Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3B59D43D1F
	for <current@FreeBSD.org>; Thu, 10 Jun 2004 19:31:20 +0000 (GMT)
	(envelope-from bde@zeta.org.au)
Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au
	[61.8.0.87])i5AJV65v024225;	Fri, 11 Jun 2004 05:31:06 +1000
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	i5AJV4LS029149;	Fri, 11 Jun 2004 05:31:05 +1000
Date: Fri, 11 Jun 2004 05:31:04 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Andy Farkas <andyf@speednet.com.au>
In-Reply-To: <20040610202545.E9618@hewey.af.speednet.com.au>
Message-ID: <20040611052209.H10787@gamplex.bde.org>
References: <FE045D4D9F7AED4CBFF1B3B813C85337051D8F48@mail.sandvine.com>
	<20040610202545.E9618@hewey.af.speednet.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: "'current@freebsd.org'" <current@FreeBSD.org>
Subject: Re: kernel trap 19 with interrupts disabled
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2004 19:31:20 -0000

On Thu, 10 Jun 2004, Andy Farkas wrote:

> > Don Bowman wrote:
> >
> [... about a different type of NMI]

> My box did the following the other day (its a quad ppro-200 with ecc ram;
> dell 6100/200).  I'd like to know if it is safe to continue running the
> kernel as is, or should it be rebooted?  I pressed 'c' at the debugger
> prompt and nothing bad has happened so far. I've rebooted since.
>
> Jun  6 17:44:47 <kern.crit> hummer kernel: NMI ISA a8, EISA 0
> Jun  6 17:44:47 <kern.crit> hummer kernel: RAM parity error, likely hardware failure.
> Jun  6 17:44:47 <kern.crit> hummer kernel:
> Jun  6 17:44:47 <kern.crit> hummer kernel: Fatal trap 19: non-maskable interrupt trap while in kernel mode
> Jun  6 17:44:47 <kern.crit> hummer kernel: cpuid = 0; apic id = 00
> Jun  6 17:44:47 <kern.crit> hummer kernel: instruction pointer  = 0x8:0xc049cd12

Since the address of the memory with the parity error (if that's really what
caused the NMI) is unknown, there is no way to tell.  I don't know if NMI's
for parity errors are or can be delivered asynchronously, but guess that
they aren't, so the problem might not be near the instruction pointer.

Bruce