From owner-freebsd-stable  Wed Jan 26  7:44: 5 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (port-8-140.adsl.one.net [216.23.16.140])
	by hub.freebsd.org (Postfix) with ESMTP id 6AA0814BDA
	for <freebsd-stable@FreeBSD.ORG>; Wed, 26 Jan 2000 07:44:03 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id KAA31437;
	Wed, 26 Jan 2000 10:47:04 -0500 (EST)
	(envelope-from cokane)
Date: Wed, 26 Jan 2000 10:47:04 -0500
From: Coleman Kane <cokane@one.net>
To: Bryan Bursey <bbursey@nipplehead.yi.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: IRQs appearing incorrectly in dmesg
Message-ID: <20000126104704.C31345@evil.2y.net>
References: <XFMail.000125003643.freebsd@cybcon.com> <Pine.BSF.4.20.0001252006340.21864-100000@nipplehead.yi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.BSF.4.20.0001252006340.21864-100000@nipplehead.yi.org>; from bbursey@nipplehead.yi.org on Tue, Jan 25, 2000 at 11:31:08PM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

These are not 'incorrect' as you say, they are just the way PCI is set up
(remember, the normal PIC is an x86 thing, but PCI is used on many other
 architectures). These IRQs get mapped around to their x86 counterparts after
the drivers that the PCI boards represent are inited. Check these out:

A Compaq Server:
Probing for devices on PCI bus 0:
chip0: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int v irq 176 on 
chip1: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 7 irq 160 on 
chip2: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 7 irq 32 on p
chip3: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 6 irq 160 on 
chip4: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 6 irq 32 on p
chip5: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 5 irq 160 on 
chip6: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 5 irq 32 on p
chip7: <Host to PCI bridge (vendor=0e11 device=4000)> rev 0x00 int 4 irq 160 on 
lnc1: <PCNet/PCI Ethernet adapter> rev 0x02 int b irq 3 on pci0.11.0
lnc1: PCnet-32 VL-Bus address 00:80:5f:06:69:6a
ncr0: <ncr 53c810 fast10 scsi> rev 0x02 int a irq 10 on pci0.12.0
xl0: <3Com 3c900B-TPO Etherlink XL> rev 0x04 int a irq 9 on pci0.13.0

--cokane

Bryan Bursey had the audacity to say:
> G'day folks...
> 
> My 3.4-STABLE box is incorrectly reporting the IRQs for many of my PCI
> devices in dmesg.  Some details are inserted below.  I'm wondering if
> 
> xl0: <3Com 3c900B-TPO Etherlink XL> rev 0x04 int a irq 19 on pci0.9.0
> es1: <AudioPCI ES1370> rev 0x01 int a irq 17 on pci0.13.0
> bktr0: <BrookTree 848> rev 0x11 int a irq 16 on pci0.15.0
> 
> Any help and/or advice much appreciated.
> 
> Regards,
> Bryan
> 
> 
> +----------------------------------------+
> | Drugs may be the road to nowhere,      |
> | but at least they're the scenic route. |
> +----------------------------------------+
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message