From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 27 18:42:52 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E829A16A5AC for ; Tue, 27 Jun 2006 18:42:52 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1029C44A25 for ; Tue, 27 Jun 2006 17:50:28 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k5RHoJCt009639; Tue, 27 Jun 2006 13:50:23 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Andrew Reilly Date: Tue, 27 Jun 2006 11:30:31 -0400 User-Agent: KMail/1.9.1 References: <200606231908.k5NJ8DTB009354@guild.plethora.net> <200606260940.48404.jhb@freebsd.org> <20060626232753.GB92989@duncan.reilly.home> In-Reply-To: <20060626232753.GB92989@duncan.reilly.home> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606271130.32300.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 27 Jun 2006 13:50:24 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1567/Tue Jun 27 12:42:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-amd64@freebsd.org Subject: Re: SMP system not running SMP X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 18:42:53 -0000 On Monday 26 June 2006 19:27, Andrew Reilly wrote: > On Mon, Jun 26, 2006 at 09:40:48AM -0400, John Baldwin wrote: > > Ok. That sounds like an interrupt routing issue. It could be that the > > interrupt routing info in the MP Table is incorrect. Let's stick with > > i386 for now (amd64 has the same code). > > For another, perhaps unrelated datum, my Athlon64-X2 box has > become wonderfully stable and seemingly fully functional ever > since I took all of the PCI cards out of it. I wasn't trying to > run SCSI disks (just on-board SATA), but I was trying to use PCI > network adaptors, since there was no driver for the on-board > NVidia MCP9 at the time. (I'm now using the experimental nfe > driver, and it seems to work great.) I tried a bog-standard crappy > RTL8139 and a good-as-gold Intel 21143, and they both displayed > symptoms consistent with missing interrupts: failure to detect > carrier, multiple up/downs from watchdog timeouts, etc. > > Now, my Gigabyte Nvidia4 board has a totally different motherboard > chipset from the MSI K8D Master-F in question, but the similar > behaviour just seemed interesting. > > There isn't any vm86-mode setup (bios calls?) involved in > routing interrupts, is there? Any similarity in BIOS vendors > between the two boards? (Maybe firmware bug?) It's all done via table lookups and ACPI calls, no vm86 stuff. The tables and ACPI code is provided by the BIOS though, so a horked BIOS can always break things. -- John Baldwin