From owner-freebsd-questions Sat Jun 26 12:27:32 1999 Delivered-To: freebsd-questions@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id D96C51504B for ; Sat, 26 Jun 1999 12:27:29 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id TAA43178; Sat, 26 Jun 1999 19:27:25 GMT Message-ID: <377528FE.6D9B2F97@tdx.co.uk> Date: Sat, 26 Jun 1999 20:24:46 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Theodore Cekan Cc: freebsd-questions@FreeBSD.ORG Subject: Re: smp question References: <01d001bec005$ac249280$5c691ace@theodore.mho.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Theodore Cekan wrote: > > Thanks, then I have another question :) On bootup I get these messages: > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin > 2 > APIC_IO: routing 8254 via 8259 on pin 0 > > It seems that either the motherboard is incompatible, or there really is > something wrong with the mp table. > > Any thoughts? Yeah, don't worry about it! - it means what it says... That the output of the 8254 controller/chip isn't connected to the APIC (used to handle IRQ's when in SMP mode)... Both the SMP boards I have here (both SuperMicro) come up with the same message... FreeBSD has a work-around for it (as it says, it's re-routing the 8254 via the 8259 on pin 0) and should work fine... Some would argue it's a 'broken' motherboard... If so, motherboards these days are mostly broken... A fact I don't find hard to believe! -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message