From owner-freebsd-stable@FreeBSD.ORG Wed Mar 2 16:47:52 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C3561065670 for ; Wed, 2 Mar 2011 16:47:52 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E43A78FC13 for ; Wed, 2 Mar 2011 16:47:51 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 9747646B2E; Wed, 2 Mar 2011 11:47:51 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2C41D8A02A; Wed, 2 Mar 2011 11:47:51 -0500 (EST) From: John Baldwin To: Mike Tancsa Date: Wed, 2 Mar 2011 10:18:52 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <4D6DA259.4050307@sentex.net> <201103020755.54147.jhb@freebsd.org> <4D6E412F.6080208@sentex.net> In-Reply-To: <4D6E412F.6080208@sentex.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201103021018.52403.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 02 Mar 2011 11:47:51 -0500 (EST) Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 16:47:52 -0000 On Wednesday, March 02, 2011 8:07:59 am Mike Tancsa wrote: > 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? No, was trying to think if there was a scenario where an I/O APIC pin or MSI message could specify an illegal vector. Can you reproduce this at all? -- John Baldwin