From owner-freebsd-smp Thu Feb 15 21: 8:20 2001 Delivered-To: freebsd-smp@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 78B6337B65D for ; Thu, 15 Feb 2001 21:08:18 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id f1G58FT02748; Thu, 15 Feb 2001 23:08:15 -0600 (CST) (envelope-from dan) Date: Thu, 15 Feb 2001 23:08:15 -0600 From: Dan Nelson To: Andy C Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Hmm Message-ID: <20010215230815.A12821@dan.emsphone.com> References: <00f501c097b8$18ed85d0$01010a0a@DEDICATIONINET.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.14i In-Reply-To: <00f501c097b8$18ed85d0$01010a0a@DEDICATIONINET.local>; from "Andy C" on Fri Feb 16 01:30:50 GMT 2001 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Feb 16), Andy C said: > I get this error on boot, anyone know whats wrong with it?: > > -- > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > SMP: AP CPU #1 Launched! > -- I'd say exactly what the message says. The MP table doesn't match the actual setup. FreeBSD then compensates for it, and the kernel continues booting. My system prints the same message and it doesn't seem to hurt. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message