From owner-freebsd-smp Thu Feb 7 14: 1:39 2002 Delivered-To: freebsd-smp@freebsd.org Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.77]) by hub.freebsd.org (Postfix) with ESMTP id 24AFB37B405 for ; Thu, 7 Feb 2002 14:01:36 -0800 (PST) Received: from prg.traveller.cz (localhost [127.0.0.1]) by prg.traveller.cz (8.12.1[KQ-CZ](1)/8.12.1/pukvis) with ESMTP id g17M1TOJ051208; Thu, 7 Feb 2002 23:01:29 +0100 (CET) Received: from localhost (mime@localhost) by prg.traveller.cz (8.12.1[KQ-CZ](1)/pukvis) with ESMTP id g17M1TRT051205; Thu, 7 Feb 2002 23:01:29 +0100 (CET) Date: Thu, 7 Feb 2002 23:01:29 +0100 (CET) From: Michal Mertl To: "Dorr H. Clark" Cc: Igor Lepechin , Subject: Re: Troubles with MP on ServerWorks NB6635 platform In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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