From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 11:20:30 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 F2C1E16A4FD for ; Fri, 2 Jan 2004 11:20:28 -0800 (PST) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D49F43D6A for ; Fri, 2 Jan 2004 11:19:56 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 26936 invoked from network); 2 Jan 2004 19:19:55 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 2 Jan 2004 19:19:55 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i02JJqM0003185; Fri, 2 Jan 2004 14:19:52 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040101172803.GJ11668@cicely12.cicely.de> Date: Fri, 02 Jan 2004 14:19:53 -0500 (EST) From: John Baldwin To: Bernd Walter X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: current@freebsd.org cc: ticso@cicely.de Subject: Re: Still IRQ routing problems with bridged devices. 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, 02 Jan 2004 19:20:30 -0000 On 01-Jan-2004 Bernd Walter wrote: > On Thu, Jan 01, 2004 at 10:12:23AM -0700, M. Warner Losh wrote: >> In message: <20040101155100.GF11668@cicely12.cicely.de> >> Bernd Walter writes: >> : On Wed, Dec 31, 2003 at 10:22:30PM -0700, M. Warner Losh wrote: >> : > In message: <20040101013224.GC11668@cicely12.cicely.de> >> : > Bernd Walter writes: >> : > : The board is an old Asus T2P4 with 3 bridged cards and $PIR table. >> : > : All IRQs behind bridges get bogusly IRQ4 instead of the right ones. >> : > : Is this only a problem on some boards or do we have a general irq >> : > : routing problem with bridges? >> : > >> : > It is a problem with some bridges and PCI BIOS interrupt routing. >> : >> : The intline registers are correct - that's what used to run since years. >> : What has the kind of bridge to do with it? >> >> just what the code does :-) > > But bridges are handled generic so why would only some bridges show > this problem? > The bridges are 21050 types btw. Sounds like a BIOS bug. If a bridge isn't listed in the $PIR, we use the barber-pole swizzle to route across it. However, that is technically only defined for bridges on add-in cards. The only way we can tell if a bridge is on an add-in card is if it is not listed either in ACPI's namespace with a _PRT or it is not listed in the $PIR. Part of teh problem is that we shouldn't be using IRQ4 when we route PCI devices if you have IRQ4 used for an ISA device anyway. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/