From owner-freebsd-current Sat Oct 3 09:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22422 for freebsd-current-outgoing; Sat, 3 Oct 1998 09:32:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22416 for ; Sat, 3 Oct 1998 09:32:42 -0700 (PDT) (envelope-from smp@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id KAA11891; Sat, 3 Oct 1998 10:32:12 -0600 (MDT) Message-Id: <199810031632.KAA11891@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: ulf@Alameda.net cc: current@FreeBSD.ORG Subject: Re: 3.0-19980930-BETA, Tyan TomCat II Dual P5-166 is having problems In-reply-to: Your message of "Sat, 03 Oct 1998 04:28:21 PDT." <19981003042821.A10733@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Oct 1998 10:32:12 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Ok, I moved the Intel card from slot 4 to slot 2 and the IRQs got > swapped (GFX had 17, now 19. Fxp had 19, now 17). No more problems > with the amount of interrupts. This sounds like flakey hardware... > 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 > SMP: AP CPU #1 Launched! > > I am getting the same APIC_IO message with and without the fxp card. This is acceptable. I originally believed that this situation meant that there was NO physical path on the board from 8254 to APIC pin #2, and that the statement to the contrary (ie that there is) in the mptable meant a defective mptable. I now suspect that the issue might be that something in the motherboard chipset is improperly set, and if we could determine what that was we could program it and skip the redirection of the 8254 thru the PIC (not APIC) as we now do in this case. However, none of the SMP systems I have access to exhibit this behaviour so I can't be the one to chase it. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message