what's going on here isn't immediately obvious to me.
maybe it should be.  any ideas would be appreciated.

i have a machine that is very happy with a mv50xx
controller, usb and ether0 all sitting on irq 11.

chula# cat /dev/irqalloc
          3           0 debugpt
          7           0 mathemu
          8           0 doublefault
          9           0 mathover
         14           0 fault386
         15           0 unexpected
         16           0 matherror
         50          18 clock
         51          19 lapicerror
         63          31 lapicspurious
         65           1 kbd
         73          11 sdF (mv50xx)
         73          11 usbuhci
         73          11 ether0
         81          10 sdC (ata)
         81          10 ether1
         89           4 COM1
         97           7 usbehci
         97           7 usbuhci
        105          14 sdE (ahci)
        105          14 usbuhci
        113          15 usbehci
        113          15 usbuhci

if i add another controller (orion) to the mix
irq 11 has this sitting on it:

         73          11 sdF (mv50xx)
         73          11 sda (orion)
         73          11 usbuhci
         73          11 ether0
 
and things are no longer good;  with the machine doing
nothing i have:

        chula# cat /dev/sysstat
        0        3097       33083         896         901           0           
0         197          78           0 
        1        3553       28350        1274        1241           0           
0           0          76           0 
        2         940     1294487        1049         409           0           
0           0           8          86 
        3        3639       28389        1394        1149           0           
0           0          80           0 

disabling the mv50xx pci controller restores order;
disabling the sdata pci, ahci pci-e, or usb controllers
does not.  the orion is a pci-e controller.

so any combination is okay as long as the mv50xx and
orion aren't running at the same time.  and oddly
the machine runs reasonably even with the screaming
irq.

chula# pci | grep disk
0.31.2: disk 01.06.01 8086/3a22  14 0:0000a401 16 1:0000a081 16 2:0000a001 16 
3:00009c01 16 4:00009881 32 5:fa4da000 2048
3.0.0:  disk 01.00.00 11ab/6485  11 2:0000bc01 128 4:fa5f0004 65536 5:00000000 
16
8.0.0:  disk 01.00.00 11ab/6081  11 0:fbe00004 1048576 1:00000000 16 2:0000e801 
256 3:fb800004 4194304 4:00000000 16
8.1.0:  disk 01.80.85 105a/4d69  10 0:0000ec01 16 1:0000e481 16 2:0000e401 16 
3:0000e081 16 4:0000e001 16 5:fbdfc000 16384

chula# pci | grep ' 11 '
0.22.0: ---  08.80.00 8086/3430  11 0:fa4fc004 16384 1:00000000 16
0.22.4: ---  08.80.00 8086/3429  11 0:fa4ec004 16384 1:00000000 16
0.26.0: usb  0c.03.00 8086/3a37  11 4:0000ac01 32
3.0.0:  disk 01.00.00 11ab/6485  11 2:0000bc01 128 4:fa5f0004 65536 5:00000000 
16
6.0.0:  net  02.00.00 8086/10d3  11 0:fa6e0000 131072 2:0000cc01 32 3:fa6dc000 
16384
8.0.0:  disk 01.00.00 11ab/6081  11 0:fbe00004 1048576 1:00000000 16 2:0000e801 
256 3:fb800004 4194304 4:00000000 16

- erik

Reply via email to