From owner-freebsd-stable@FreeBSD.ORG Wed Mar 2 13:07:58 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 3EA00106566B; Wed, 2 Mar 2011 13:07:58 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id EBF768FC0A; Wed, 2 Mar 2011 13:07:57 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:b465:c134:204f:fc84] ([IPv6:2607:f3e0:0:4:b465:c134:204f:fc84]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id p22D7twR065572 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 2 Mar 2011 08:07:55 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D6E412F.6080208@sentex.net> Date: Wed, 02 Mar 2011 08:07:59 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: John Baldwin References: <4D6DA259.4050307@sentex.net> <20110302020412.GA50962@icarus.home.lan> <4D6DAC5A.6080904@sentex.net> <201103020755.54147.jhb@freebsd.org> In-Reply-To: <201103020755.54147.jhb@freebsd.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 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 13:07:58 -0000 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/