From owner-freebsd-smp Fri May 15 01:20:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05980 for freebsd-smp-outgoing; Fri, 15 May 1998 01:20:21 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05971 for ; Fri, 15 May 1998 01:20:16 -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.8.8/8.8.8) with ESMTP id JAA04638 for ; Fri, 15 May 1998 09:20:18 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <355BFAC4.B61E7CA0@tdx.co.uk> Date: Fri, 15 May 1998 09:20:20 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: smp@FreeBSD.ORG Subject: 8254 APIC broken? with P6DNF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got 3.0-CURRENT running on a dual p-pro SuperMicro P6DNF motherboard, the system works fine, but when it comes up the kernel says: " 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 " I can understand what this means (I think ;-) - And I would guess theres no way of 'fixing' it, apart from the workaround the system's installed, but should I be worried about it? Everything seems to work fine... I'd guess at the end of the day it might be a performance degrading workaround? - But so long as it works ;-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message