From owner-freebsd-smp Mon Sep 25 10:14:43 2000 Delivered-To: freebsd-smp@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 1E74137B424; Mon, 25 Sep 2000 10:14:37 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8PHFnp93386; Mon, 25 Sep 2000 19:15:49 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 25 Sep 2000 19:15:49 +0200 (CEST) From: "O. Hartmann" To: freebsd-smp@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: TYAN Thunder 2500/MP Table Error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sirs. I run successfully a TYAN Thunder 2500 mainboard with FreeBSD 4.1-STABLE, BIOS Beta 1.03/896 for the LSI 53C896 based SCSI controler. When booting, I obtain a lot of SMP messages from the kernel, but at one stage, I receive this error: 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 works fine, but it seems that there is something wron with the MP table. Is this a serious error message or is it simply a warning? What kind of performance penalty does it results in? And: hopefully, is there a chance to get rid of it with a new BIOS update in the future? Thanks in advance, Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message