From owner-freebsd-smp@FreeBSD.ORG Thu Aug 28 09:25:48 2003 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7601916A4BF for ; Thu, 28 Aug 2003 09:25:48 -0700 (PDT) Received: from redhotmomma.ssr.com (redhotmomma.ssr.com [199.4.235.14]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C7D143FE1 for ; Thu, 28 Aug 2003 09:25:47 -0700 (PDT) (envelope-from sdb@ssr.com) Received: (qmail 2878 invoked from network); 28 Aug 2003 16:25:39 -0000 Received: from kimchee.ssr.com (199.4.235.5) by redhotmomma.ssr.com with QMQP; 28 Aug 2003 16:25:39 -0000 Date: 28 Aug 2003 16:25:39 -0000 Message-ID: <20030828162539.497.qmail@kimchee.ssr.com> From: Scott Ballantyne To: freebsd-smp@freebsd.org In-reply-to: (message from John Baldwin on Tue, 26 Aug 2003 17:18:07 -0400 (EDT)) References: Subject: Re: Unpredictable problems with APIC renumbering X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2003 16:25:48 -0000 John Baldwin writes: > > Is there a fix or work-a-round for this problem? > > It's not a problem you need to worry about and is common to many > MP motherboards. > It's odd that it only happens occasionally. The precise message is: Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> IRQ 0 AP#1 (PHY #1) failed! panic y/n? [y] mp-lock = 0000001; cpuid=0; 1apicid=0 Scott -- sdb@ssr.com