Re: Confusing /proc/pci output
On Wed, Mar 05, 2003 at 01:51:06PM +0100, Benjamin Herrenschmidt wrote:
> > 'dmesg' doesn't show any obvious errors, but I'm confused..
> > Is it normal that some devices share the same IRQ (22) ?
Actually, switching kernels (2.4.21-pre5 -> 2.4.20-ben7) cause dmesg
to output more information :
Linux version 2.4.20-ben7 (root@uqbar) (gcc version 3.2.1 20020924 (Debian prerelease)) #1 Wed Mar 5 00:46:43 CET 2003
Found a OHare mac-io controller, rev: 1, mapped at 0xfdf00000
PowerMac motherboard: Alchemy
Cache coherency enabled for bandit/PSX
Found Bandit PCI host bridge at 0xf2000000. Firmware bus number: 0->0
hose bandit, pci_mem_offset: 00000000, start0: f3000000
io_base_virt: fd6fd000, io_base_phys: f2000000, isa_mem_base: 00000000
On node 0 totalpages: 34816
zone(0): 34816 pages.
zone(1): 0 pages.
zone(2): 0 pages.
[...]
PCI: Probing PCI hardware
Scanning bus 00
Found 00:58 [106b/0001] 000600 00
Found 00:70 [1002/4c49] 000300 00
Found 00:80 [106b/0007] 00ff00 00
Found 00:88 [1011/0014] 000200 00
Fixups for bus 00
Bus scan for 00 returning with max=00
PCI:00:0e.0: Resource 0: 81000000-81ffffff (f=200), vd: 1002, dev: 4c49
PCI:00:0e.0: Resource 2: 80801000-80801fff (f=200), vd: 1002, dev: 4c49
PCI:00:10.0: Resource 0: f3000000-f307ffff (f=200), vd: 106b, dev: 0007
PCI:00:0e.0: Resource 1: 00000400-000004ff (f=101), vd: 1002, dev: 4c49
PCI:00:11.0: Resource 0: 00000400-0000047f (f=101), vd: 1011, dev: 0014
resource conflict with: 400..4ff (101), name: ATI Technologies Inc 3D Rage LT Pro
PCI: Cannot allocate resource region 0 of device 00:11.0
PCI: parent is c0286030: 00000000-007fffff (f=100)
PCI:00:11.0: Resource 1: 80800000-8080007f (f=200), vd: 1011, dev: 0014
[...]
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
PCI: Enabling device 00:11.0 (0004 -> 0007)
tulip0: 21041 Media table, default media ffff (Autosense).
tulip0: 21041 media #0, 10baseT.
tulip0: 21041 media #1, 10base2.
tulip0: 21041 media #2, AUI.
eth0: Digital DC21041 Tulip rev 33 at 0xc9912000, 21041 mode, 00:A0:40:61:9D:5C, IRQ 22.
> Look at /proc/interrupts after the driver is loaded to see what
> interrupts are actually used.
eqdar@uqbar:~$ cat /proc/interrupts
CPU0
4: 0 PMAC-PIC Edge SCC-txdma
5: 854 PMAC-PIC Edge SCC-rxdma
6: 0 PMAC-PIC Edge SCC-txdma
7: 0 PMAC-PIC Edge SCC-rxdma
8: 1 PMAC-PIC Edge Built-in Sound out
9: 1 PMAC-PIC Edge Built-in Sound in
12: 53 PMAC-PIC Edge MESH
13: 6725 PMAC-PIC Edge ide0
15: 69665 PMAC-PIC Edge SCC
16: 0 PMAC-PIC Edge SCC
17: 0 PMAC-PIC Edge Built-in Sound misc
18: 777385 PMAC-PIC Edge ADB
19: 0 PMAC-PIC Edge SWIM3
BAD: 0
all drivers are build into the kernel (no modules)
Simon
--
Simon Vallet
Institut National Agronomique Paris-Grignon
svallet@inapg.inra.fr
Reply to: