From owner-freebsd-current@FreeBSD.ORG Thu Sep 2 00:33:20 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 E323016A4CE; Thu, 2 Sep 2004 00:33:20 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FEBC43D39; Thu, 2 Sep 2004 00:33:20 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i820XJJt009632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Sep 2004 20:33:19 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i820XEGE043865; Wed, 1 Sep 2004 20:33:14 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16694.27210.415965.951382@grasshopper.cs.duke.edu> Date: Wed, 1 Sep 2004 20:33:14 -0400 (EDT) To: John Baldwin In-Reply-To: <200409011632.59507.jhb@FreeBSD.org> References: <412FB9FC.8030505@root.org> <200409011632.59507.jhb@FreeBSD.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 00:33:21 -0000 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".. ;) Drew