From owner-freebsd-current@FreeBSD.ORG Thu Sep 2 19:44:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEB2716A4CE for ; Thu, 2 Sep 2004 19:44:29 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9928943D31 for ; Thu, 2 Sep 2004 19:44:29 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 16417 invoked from network); 2 Sep 2004 19:44:29 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 2 Sep 2004 19:44:27 -0000 Received: from [10.50.41.228] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i82JiGS6069754; Thu, 2 Sep 2004 15:44:24 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Andrew Gallatin Date: Thu, 2 Sep 2004 14:17:03 -0400 User-Agent: KMail/1.6.2 References: <412FB9FC.8030505@root.org> <200409011632.59507.jhb@FreeBSD.org> <16694.27210.415965.951382@grasshopper.cs.duke.edu> In-Reply-To: <16694.27210.415965.951382@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409021417.03152.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org Subject: Re: spurrious interrupt problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2004 19:44:29 -0000 On Wednesday 01 September 2004 08:33 pm, Andrew Gallatin wrote: > John Baldwin writes: > > On Friday 27 August 2004 06:47 pm, Nate Lawson wrote: > > > I don't see anything wrong with your acpi pci link routing. In fact, > > > all your irqs are hardwired meaning acpi shouldn't touch them. This > > > must be something with ioapic. (BTW, acpi is non-optional on amd64). > > > > Talk to phk@. He had an opteron motherboard that had a busted BIOS that > > left the links between PCI IRQs that are used in atpic mode setup even > > when in apic mode so that you get 'alias' IRQs in apic mode. In his > > case the vendor provided a BIOS update that fixed the issue. > > I had our onsite guy update the bios, but that ended up disabling USB. > So its "fixed".. ;) Ouch. :-P -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org