From owner-freebsd-smp Thu Feb 7 14:42:24 2002 Delivered-To: freebsd-smp@freebsd.org Received: from absinthe.carnagecopia.com (absinthe.carnagecopia.com [216.187.87.246]) by hub.freebsd.org (Postfix) with SMTP id D54A437B41A for ; Thu, 7 Feb 2002 14:42:18 -0800 (PST) Received: (qmail 45301 invoked by uid 85); 7 Feb 2002 22:42:13 -0000 Received: from random@carnagecopia.com by absinthe.carnagecopia.com with qmail-scanner-1.03 (uvscan: v4.0.50/v4184. . Clean. Processed in 0.314723 secs); 07 Feb 2002 22:42:13 -0000 Received: from firewall-vancouver.carnagecopia.com (HELO workstation-61) (66.38.134.97) by absinthe.carnagecopia.com with SMTP; 7 Feb 2002 22:42:13 -0000 Date: Thu, 7 Feb 2002 14:41:55 -0800 From: Vincent Janelle To: freebsd-smp@freebsd.org Subject: Re: Troubles with MP on ServerWorks NB6635 platform Message-Id: <20020207144155.2e43f800.random@carnagecopia.com> In-Reply-To: References: Organization: Goblin Studios X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 I've been getting this error on a SuperMicro P3TDLE, although the last time I rebooted it, it started to give me errors regarding the IDE bus. Booting in single processor mode works fine. On Thu, 7 Feb 2002 23:01:29 +0100 (CET) Michal Mertl wrote: > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message