From owner-freebsd-smp Wed Dec 4 12:24:36 2002 Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2C1737B401 for ; Wed, 4 Dec 2002 12:24:34 -0800 (PST) Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E3E643EB2 for ; Wed, 4 Dec 2002 12:24:34 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 7071 invoked from network); 4 Dec 2002 20:24:40 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail13.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 4 Dec 2002 20:24:40 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gB4KOWuH042034; Wed, 4 Dec 2002 15:24:32 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3DEE5F37.000003.43942@ns.interchange.ca> Date: Wed, 04 Dec 2002 15:24:39 -0500 (EST) From: John Baldwin To: tlambert2@mindspring.com Subject: Re: Intel SE7500CW2 narrowed down... Cc: freebsd-smp@freebsd.org, Michael Richards 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 04-Dec-2002 Michael Richards wrote: >>> I'm not convinced it's a tables problem as I read the spec and >>> verified the CPU entries in this table byte for byte. It appears >>> valid. Besides, Linux works and so do a host of other OSes. More >>> than likely we're just doing something slightly different that >>> happens to work find with all the other boards out there. >>> >>> My next step is to start looking at how linux works and compare >>> it to how FreeBSD doesn't work. >> >> You will find it in the APIC I/O code and the interrupt routing >> code, with a tiny part in the shipset initialization. >> >> You could fix it in FreeBSD by disregarding what the BIOS says, >> and manually initializing the ServerWorks chipset the way FreeBSD >> wants it (i.e. MPSpec v1.4, mode 2 interrupt processing >> compliant). FreeBSD doesn't run in real "virtual wire mode", it >> makes the interrupts follow Giant. Terry. We are having problems sending _interprocess_interrupts_. IPI's do _not_ go through the IO APIC. They are sent from one local APIC over to another local APIC. The problems we are seeing have nothing to do with I/O interrupts. The box runs fine with one processor and using the I/O APIC if you ignore the failure of the AP to respond to the startup IPI. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message