Date: Thu, 7 Feb 2002 23:01:29 +0100 (CET) From: Michal Mertl <mime@traveller.cz> To: "Dorr H. Clark" <dclark@applmath.scu.edu> Cc: Igor Lepechin <gogi@themoscowtimes.com>, <freebsd-smp@FreeBSD.ORG> Subject: Re: Troubles with MP on ServerWorks NB6635 platform Message-ID: <Pine.BSF.4.41.0202072258360.50897-100000@prg.traveller.cz> In-Reply-To: <Pine.GHP.4.21.0202071011360.25435-100000@hpux38.dc.engr.scu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 7 Feb 2002, Dorr H. Clark wrote: > > On Mon, 4 Feb 2002, Igor Lepechin wrote: > > > Feb 4 02:44:49 web /kernel: APIC_IO: Testing 8254 interrupt delivery > > Feb 4 02:44:49 web /kernel: APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 > > Feb 4 02:44:49 web /kernel: APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > --------------------------------------^^^^^^^^^^^^^ > > I've seen this on a prototype board also, > which didn't involve the ServerWorks chips. > The system otherwise appeared to function > although the testing was not extensive. > > Is it possible this is just an alarming tone > for an otherwise acceptable code path? > I don't know what does it mean either but I can confirm that we have several ASUS CUR-DLS boards with ServerWorks chipset, they all write this on boot too and they work just fine. -- Michal Mertl mime@traveller.cz 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?Pine.BSF.4.41.0202072258360.50897-100000>