From owner-freebsd-current@FreeBSD.ORG Thu Jun 10 10:34:34 2004 Return-Path: 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 C486716A4CE for ; Thu, 10 Jun 2004 10:34:34 +0000 (GMT) Received: from hewey.af.speednet.com.au (udsl-3-062.QLD.dft.com.au [202.168.108.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6937443D46 for ; Thu, 10 Jun 2004 10:34:33 +0000 (GMT) (envelope-from andyf@speednet.com.au) Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au [172.22.2.1])i5AAYAQg009878; Thu, 10 Jun 2004 20:34:15 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Thu, 10 Jun 2004 20:34:10 +1000 (EST) From: Andy Farkas X-X-Sender: andyf@hewey.af.speednet.com.au To: Bruce Evans In-Reply-To: <20040610194112.S8078@gamplex.bde.org> Message-ID: <20040610202545.E9618@hewey.af.speednet.com.au> References: <20040610194112.S8078@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "'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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2004 10:34:34 -0000 Bruce Evans wrote: > Don Bowman wrote: > ... > > kernel trap 19 with interrupts disabled > > NMI ... going to debugger ... > > It means that the NMI was serviced by a CPU that has interrupts disabled > at the CPU level. The message for this is a little spurious because NMI > by definition is supposed to be able to occur when interrupts are masked, > but it can be useful to know when an unexpected or even an expected trap > occurs with interrupts disabled. Here it tells us that the interrupt > may really have needed to be non-maskable to break into some code that is > looping with interrupts disabled. 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 hummer kernel: NMI ISA a8, EISA 0 Jun 6 17:44:47 hummer kernel: RAM parity error, likely hardware failure. Jun 6 17:44:47 hummer kernel: Jun 6 17:44:47 hummer kernel: Fatal trap 19: non-maskable interrupt trap while in kernel mode Jun 6 17:44:47 hummer kernel: cpuid = 0; apic id = 00 Jun 6 17:44:47 hummer kernel: instruction pointer = 0x8:0xc049cd12 Jun 6 17:44:47 hummer kernel: stack pointer = 0x10:0xd7d0ac70 Jun 6 17:44:47 hummer kernel: frame pointer = 0x10:0xd7d0ac9c Jun 6 17:44:47 hummer kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Jun 6 17:44:47 hummer kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 6 17:44:47 hummer kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 6 17:44:47 hummer kernel: current process = 43 (irq14: ata0) Jun 6 17:44:48 hummer kernel: kernel: type 19 trap, code=0 (yes, there is a blank "kernel:" line!) -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/