From owner-freebsd-current@FreeBSD.ORG Thu Jan 1 07:51:40 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 19D5516A4CE for ; Thu, 1 Jan 2004 07:51:40 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1F5C43D1D for ; Thu, 1 Jan 2004 07:51:22 -0800 (PST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i01FpAN1011871 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Thu, 1 Jan 2004 16:51:12 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i01Fp3MO045658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Jan 2004 16:51:04 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.10/8.12.10) with ESMTP id i01Fp2BE015414; Thu, 1 Jan 2004 16:51:02 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.10/8.12.10/Submit) id i01Fp1UT015413; Thu, 1 Jan 2004 16:51:01 +0100 (CET) (envelope-from ticso) Date: Thu, 1 Jan 2004 16:51:01 +0100 From: Bernd Walter To: "M. Warner Losh" Message-ID: <20040101155100.GF11668@cicely12.cicely.de> References: <20040101013224.GC11668@cicely12.cicely.de> <20031231.222230.01438468.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031231.222230.01438468.imp@bsdimp.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.61 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on cicely5.cicely.de cc: ticso@cicely12.cicely.de cc: ticso@cicely.de cc: current@freebsd.org Subject: Re: Still IRQ routing problems with bridged devices. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2004 15:51:40 -0000 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? > : At least I know that bridge irq routing works fine on alpha. > : $PIR table claims to only have 7 entries - does this make sense for > : a 4 slot board? > > Maybe you could post it. It makes sense if you have on-board PCI > devices. Is it shown with a boot -v or how can I get it? The board has 4 slots and the usual bunch of southbridge devices. > : If this is a board specific problem - can we at least add a loader > : variable to disable routing, so I don't have to patch the source on > : every update and can run a standart boot disk again? > > Did it used to work when we were re-routing all the time? It would be > easy to add this as an option, but maybe understanding your setup > might help a little to make our routing code a little smarter. It never worked if FreeBSD decides which int to use. I have to disable routing in pci.c to get back to intline entries. What do you mean with "when we were re-routing all the time"? If I don't get it wrong we are re-routing all the time and take the result if it's a valid int. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de