Date: Wed, 02 Mar 2011 08:07:59 -0500 From: Mike Tancsa <mike@sentex.net> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40 Message-ID: <4D6E412F.6080208@sentex.net> In-Reply-To: <201103020755.54147.jhb@freebsd.org> References: <4D6DA259.4050307@sentex.net> <20110302020412.GA50962@icarus.home.lan> <4D6DAC5A.6080904@sentex.net> <201103020755.54147.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/2/2011 7:55 AM, John Baldwin wrote: > > Hmm, the interrupt pins on the each lapic look fine (they all either have a > legal vector, are using NMI delivery, or are masked). > > All of the places that send IPIs have the interrupt vectors hard-coded as > constant values in the code. > > Unfortunately there is no register that tells us which illegal vector was > posted. > > Were you doing anything related to changing the state of device interrupts > (cpuset -x, kldload, kldunload, etc.) when this happened? Hi, No, nothing at all. I checked the logs again and nothing unusual leading up to it, nor was anything recorded on the serial console other than that error. Do you think its just a hardware issue? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D6E412F.6080208>