Date: 09 Mar 2001 14:41:45 -0800 From: Kevin Mills <kmills@a6l.net> To: "Kevin Van Maren" <vanmaren@fast.cs.utah.edu> Cc: freebsd-smp@freebsd.org Subject: Re: APIC_IO warning Message-ID: <85r906o992.fsf@diablo.in.a6l.net> In-Reply-To: "Kevin Van Maren"'s message of "Fri, 9 Mar 2001 14:43:37 -0700 (MST)" References: <200103092143.OAA28717@fast.cs.utah.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kevin Van Maren" <vanmaren@fast.cs.utah.edu> writes: > > 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 > > It's telling you that the "mptable", which contains configuration > information about your machine (in this case, it says which pin on > the interrupt controller used for SMP vinterupt sources are connected > to), has incorrect information (it lies). This is just a diagnoistic > message -- FreeBSD detects this condition since so many motherboards > get this part wrong, and runs fine. > > Personally, I think this diagnostic message should be eliminated > because so many people ask this same question :-) Ah, thank you. It is interesting that another server I have here that uses the 440GX chipset is fine. However, the other two servers I have that use the ServerWorks chipset both are "broken". Is this just Intel changing things without telling the rest of the world? Thanks for the explanation! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85r906o992.fsf>