From owner-freebsd-smp@FreeBSD.ORG  Thu Aug 28 13:45:45 2003
Return-Path: <owner-freebsd-smp@FreeBSD.ORG>
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 ED87016A4BF
	for <freebsd-smp@freebsd.org>; Thu, 28 Aug 2003 13:45:45 -0700 (PDT)
Received: from redhotmomma.ssr.com (redhotmomma.ssr.com [199.4.235.14])
	by mx1.FreeBSD.org (Postfix) with SMTP id B5F3E43FDF
	for <freebsd-smp@freebsd.org>; Thu, 28 Aug 2003 13:45:44 -0700 (PDT)
	(envelope-from sdb@ssr.com)
Received: (qmail 7340 invoked from network); 28 Aug 2003 20:45:41 -0000
Received: from kimchee.ssr.com (199.4.235.5)
  by redhotmomma.ssr.com with QMQP; 28 Aug 2003 20:45:41 -0000
Date: 28 Aug 2003 20:45:41 -0000
Message-ID: <20030828204541.703.qmail@kimchee.ssr.com>
From: Scott Ballantyne <sdb@ssr.com>
To: freebsd-smp@freebsd.org
In-reply-to: <XFMail.20030828152325.jhb@FreeBSD.org> (message from John
	Baldwin on Thu, 28 Aug 2003 15:23:25 -0400 (EDT))
References: <XFMail.20030828152325.jhb@FreeBSD.org>
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 <freebsd-smp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-smp>,
	<mailto:freebsd-smp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-smp>
List-Post: <mailto:freebsd-smp@freebsd.org>
List-Help: <mailto:freebsd-smp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-smp>,
	<mailto:freebsd-smp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2003 20:45:46 -0000

John Baldwin <jhb@FreeBSD.org> writes:
> On 28-Aug-2003 Scott Ballantyne wrote:
> > John Baldwin <jhb@FreeBSD.org> 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
> 
> This is a different message and has nothing to do with the
> I/O APIC code.  Try the attached patch.
> 

John, thanks so much for your help! Unfortunately, the 4.8-p3 kernel
doesn't link with this patch:

p_machdep.o: In function `start_ap':
mp_machdep.o(.text+0x212c): undefined reference to `intr_disable'
mp_machdep.o(.text+0x21d9): undefined reference to `intr_restore

I'm using the make buildkernel KERNCONF= method, if that makes any
difference.

Thanks again,
Scott
-- 
sdb@ssr.com