From owner-freebsd-current@FreeBSD.ORG Wed May 5 19:54: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 730A716A510 for ; Wed, 5 May 2004 19:54:19 -0700 (PDT) Received: from mailhub.sweetdreamsracing.biz (mailhub.sweetdreamsracing.biz [66.92.171.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90D4B43D3F for ; Wed, 5 May 2004 19:54:19 -0700 (PDT) (envelope-from culverk@sweetdreamsracing.biz) Received: by mailhub.sweetdreamsracing.biz (Postfix, from userid 80) id 8896F265; Wed, 5 May 2004 23:02:55 -0400 (EDT) Received: from hachigo (hachigo [66.92.171.91]) by www.sweetdreamsracing.biz (Horde) with HTTP for ; Wed, 5 May 2004 23:02:55 -0400 Message-ID: <20040505230255.nu4o4wwsg0gcs48k@www.sweetdreamsracing.biz> Date: Wed, 5 May 2004 23:02:55 -0400 From: Kenneth Culver To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: problem with pci interrupt routing table? 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, 06 May 2004 02:54:21 -0000 Hi, I was looking more closely at my dmesg to try to figure out why I can't get the nvidia drivers to work, and I noticed that the nvidia card was showing up on irq 11, where it was showing up at 16 in windows. I looked closer at the dmesg and found: agp0: mem 0xe0000000-0xefffffff at device 0.0 on pci0 agp0: Reserved 0x10000000 bytes for rid 0x10 type 3 at 0xe0000000 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_FOUND pci1: on pcib1 pci1: at device 0.0 (no driver attached) This looks like FreeBSD is unable to get the correct routing for IRQ's on the agp port for this motherboard. Is there anything I can do to fix this? (It's been doing this for several months, so it isn't JHB's recent fixes that cause this problem. Thanks. Ken