From owner-freebsd-current@FreeBSD.ORG Fri Aug 27 22:47:44 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 37D2A16A4CE for ; Fri, 27 Aug 2004 22:47:44 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D28AD43D72 for ; Fri, 27 Aug 2004 22:47:43 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i7RMlQjn001815; Fri, 27 Aug 2004 15:47:26 -0700 Message-ID: <412FB9FC.8030505@root.org> Date: Fri, 27 Aug 2004 15:47:24 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gallatin@cs.duke.edu Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: 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: Fri, 27 Aug 2004 22:47:44 -0000 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). -- Nate