Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Jun 2004 20:34:10 +1000 (EST)
From:      Andy Farkas <andyf@speednet.com.au>
To:        Bruce Evans <bde@zeta.org.au>
Cc:        "'current@freebsd.org'" <current@freebsd.org>
Subject:   Re: kernel trap 19 with interrupts disabled
Message-ID:  <20040610202545.E9618@hewey.af.speednet.com.au>
In-Reply-To: <20040610194112.S8078@gamplex.bde.org>
References:  <FE045D4D9F7AED4CBFF1B3B813C85337051D8F48@mail.sandvine.com> <20040610194112.S8078@gamplex.bde.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <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
Jun  6 17:44:47 <kern.crit> hummer kernel: stack pointer                = 0x10:0xd7d0ac70
Jun  6 17:44:47 <kern.crit> hummer kernel: frame pointer                = 0x10:0xd7d0ac9c
Jun  6 17:44:47 <kern.crit> hummer kernel: code segment         = base 0x0, limit 0xfffff, type 0x1b
Jun  6 17:44:47 <kern.crit> hummer kernel: = DPL 0, pres 1, def32 1, gran 1
Jun  6 17:44:47 <kern.crit> hummer kernel: processor eflags     = interrupt enabled, resume, IOPL = 0
Jun  6 17:44:47 <kern.crit> hummer kernel: current process              = 43 (irq14: ata0)
Jun  6 17:44:48 <kern.crit> 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/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040610202545.E9618>