IRQ mapping problem, 2.2.0pre[5,6], SMP related?

Jamie Raymond (jraymond@gnu.org)
Sat, 9 Jan 1999 19:21:18 -0600


This is my first bug report so I apologize if it's not complete.

I'm running a PPRO 200 SMP capable system with only one processor.
When I compile with non-SMP support my system hangs during init when
the network (eepro100) is configured.

I've traced this down in /proc/pci to a conflict between IRQs of my
eepro (onboard) and the AIC7880 SCSI controller (also onboard).*

When I compile with SMP support, this problem doesn't occur. The two
devices get mapped to different IRQs.**

Is this a true bug? Shouldn't I be able to run a non-SMP kernel if I
want to? If I run in non-SMP mode am I supposed to do some manual
device configuring so that the conflicts don't happen?

Sorry is this is a FAQ. I've read the linux-kernel archives and don't
remember a discussion of this.

Thanks,
==Jamie

* NON-SMP
Bus 0, device 6, function 0:
Ethernet controller: Intel 82557 (rev 2).
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Latency=72. Min Gnt=8.Max Lat=56.
Prefetchable 32 bit memory at 0xffe7f000 [0xffe7f008].
I/O at 0xff40 [0xff41].
Non-prefetchable 32 bit memory at 0xff800000 [0xff800000].
Bus 0, device 9, function 0:
SCSI storage controller: Adaptec AIC-7880U (rev 0).
Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=72. Min Gnt=8.Max Lat=8.
I/O at 0xf800 [0xf801].
Non-prefetchable 32 bit memory at 0xffbee000 [0xffbee000].

** SMP
Bus 0, device 6, function 0:
Ethernet controller: Intel 82557 (rev 2).
Medium devsel. Fast back-to-back capable. IRQ 18. Master Capable. Latency=72. Min Gnt=8.Max Lat=56.
Prefetchable 32 bit memory at 0xffe7f000 [0xffe7f008].
I/O at 0xff40 [0xff41].
Non-prefetchable 32 bit memory at 0xff800000 [0xff800000].
Bus 0, device 9, function 0:
SCSI storage controller: Adaptec AIC-7880U (rev 0).
Medium devsel. Fast back-to-back capable. IRQ 17. Master Capable. Latency=72. Min Gnt=8.Max Lat=8.
I/O at 0xf800 [0xf801].
Non-prefetchable 32 bit memory at 0xffbee000 [0xffbee000].

-- 
Jamie Raymond
Sabetha, Kansas
jraymond@gnu.org

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/