From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 11:53:21 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 2B90816A4CE; Fri, 2 Jan 2004 11:53:21 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A213443D31; Fri, 2 Jan 2004 11:53:15 -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) i02Jr2N1026304 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 2 Jan 2004 20:53:04 +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 i02JqlMO060034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Jan 2004 20:52:48 +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 i02JqkBE020596; Fri, 2 Jan 2004 20:52:46 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.10/8.12.10/Submit) id i02JqkRv020595; Fri, 2 Jan 2004 20:52:46 +0100 (CET) (envelope-from ticso) Date: Fri, 2 Jan 2004 20:52:45 +0100 From: Bernd Walter To: John Baldwin Message-ID: <20040102195244.GE17023@cicely12.cicely.de> References: <20040101172803.GJ11668@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline In-Reply-To: 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: Bernd Walter 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 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: Fri, 02 Jan 2004 19:53:21 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 02, 2004 at 02:19:53PM -0500, John Baldwin wrote: > > 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 It can't know about my bridges because all of them are on cards and they wouldn't won't fit with just 7 entries. > 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 It's not that simple. The chips behind the bridges are layed out to all use INTA on the primary bus, but INTA is correctly routed for non-bridged cards. I have no clue about $PIR and therefor have no idea where irq4 comes from - any pointer to $PIR documents are welcome. > IRQ4 when we route PCI devices if you have IRQ4 used for an ISA > device anyway. ISA device are probed later - how would you know that IRQ4 is used by ISA? Warner already asked for boot -v output. I hope things become clear then. It's just that the system is the NFS server with /home on it. Therefor I have to wait for a good moment to reboot the box. Attached is the non -v output with int routing disabled. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.c5" Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #1: Wed Dec 31 19:18:11 CET 2003 root@:/var/d9/obj/var/d7/builder/c5-2003-12-30/src/sys/CICELY5 Preloaded elf kernel "/boot/kernel/kernel" at 0xc070b000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD-K6tm w/ multimedia extensions (233.03-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> real memory = 268435456 (256 MB) avail memory = 257196032 (245 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00f09b0 pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe800-0xe80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 7.2 (no driver attached) pcib1: at device 9.0 on pci0 pci1: on pcib1 ahc0: port 0xd800-0xd8ff mem 0xe5000000-0xe5000fff irq 5 at device 4.0 on pci1 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs ahc1: port 0xd400-0xd4ff mem 0xe7000000-0xe71fffff,0xe4800000-0xe4800fff irq 10 at device 5.0 on pci1 RAID functionality unsupported device_probe_and_attach: ahc1 attach returned 6 ahc1: port 0xd000-0xd0ff mem 0xe4000000-0xe4000fff irq 5 at device 8.0 on pci1 aic7870: Single Channel B, SCSI Id=7, 16/253 SCBs ahc2: port 0xb800-0xb8ff mem 0xe3800000-0xe3800fff irq 5 at device 12.0 on pci1 aic7870: Single Channel C, SCSI Id=7, 16/253 SCBs pcib2: at device 10.0 on pci0 pci2: on pcib2 ahc3: port 0xa800-0xa8ff mem 0xe3000000-0xe3000fff irq 12 at device 4.0 on pci2 aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs ahc4: port 0xa400-0xa4ff mem 0xe2800000-0xe2800fff irq 5 at device 5.0 on pci2 aic7880: Ultra Single Channel B, SCSI Id=7, 16/253 SCBs de0: port 0x9800-0x987f mem 0xe2000000-0xe200007f irq 11 at device 11.0 on pci0 de0: Cogent 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:92:9b:20:e7 pcib3: at device 12.0 on pci0 pci3: on pcib3 ahc5: port 0x8800-0x88ff mem 0xe1800000-0xe1800fff irq 10 at device 4.0 on pci3 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs ahc6: port 0x8400-0x84ff mem 0xe6000000-0xe61fffff,0xe1000000-0xe1000fff irq 11 at device 5.0 on pci3 RAID functionality unsupported device_probe_and_attach: ahc6 attach returned 6 ahc6: port 0x8000-0x80ff mem 0xe0800000-0xe0800fff irq 10 at device 8.0 on pci3 aic7870: Single Channel B, SCSI Id=7, 16/253 SCBs ahc7: port 0x7800-0x78ff mem 0xe0000000-0xe0000fff irq 10 at device 12.0 on pci3 aic7870: Single Channel C, SCSI Id=7, 16/253 SCBs orm0: