Date: Fri, 11 Jun 2004 05:31:04 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Andy Farkas <andyf@speednet.com.au> Cc: "'current@freebsd.org'" <current@FreeBSD.org> Subject: Re: kernel trap 19 with interrupts disabled Message-ID: <20040611052209.H10787@gamplex.bde.org> In-Reply-To: <20040610202545.E9618@hewey.af.speednet.com.au> References: <FE045D4D9F7AED4CBFF1B3B813C85337051D8F48@mail.sandvine.com> <20040610202545.E9618@hewey.af.speednet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040611052209.H10787>