From owner-freebsd-stable@FreeBSD.ORG Wed Jul 21 17:36:25 2010 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 BC1A4106567A for ; Wed, 21 Jul 2010 17:36:25 +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 8B2388FC14 for ; Wed, 21 Jul 2010 17:36:25 +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 2FA9146B66; Wed, 21 Jul 2010 13:36:25 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0282A8A04E; Wed, 21 Jul 2010 13:36:24 -0400 (EDT) From: John Baldwin To: Andriy Gapon Date: Wed, 21 Jul 2010 10:10:53 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100217; KDE/4.4.5; amd64; ; ) References: <6B57591F-9FA2-45EB-825F-1DB025C0635D@hostpoint.ch> <4C46B0C6.4020400@icyb.net.ua> <4C46BB12.6090903@icyb.net.ua> In-Reply-To: <4C46BB12.6090903@icyb.net.ua> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201007211010.53176.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 21 Jul 2010 13:36:24 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-stable@freebsd.org, Markus Gebert Subject: Re: 8.1-RC2 MCE caused by some LAPIC/clock changes? 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, 21 Jul 2010 17:36:25 -0000 On Wednesday, July 21, 2010 5:17:06 am Andriy Gapon wrote: > on 21/07/2010 11:33 Andriy Gapon said the following: > > Not sure how to interpret this properly. > > One possibility is a hardware problem where interrupt message route between > > ioapic2 and CPU to which lapic3 belongs is flaky. > > Or, I/O path between that CPU and the PCI slot where the device resides. Or the > CPU. Or... > I think that lapic2 and lapic3 reside in a different physical package/socket, > given that you have 2x2 CPU/core configuration. > > BTW, John, could there be any problem because of this: > ioapic1: WARNING: intbase 48 != expected base 24 > ioapic2: WARNING: intbase 56 != expected base 55 > ioapic3: WARNING: intbase 24 != expected base 63 You can ignore this, this just means ACPI enumerated the I/O APICs out of order in the MADT. -- John Baldwin