freebsd stable - Aug 2005 - IRQ conflict between twa0 and skc0

So I'm having yet another problem with my AMD64x2/nforce4 system. Of the two
builtin NICs 5.4-S is only recognizing the marvell gigabit chip, which
wasn't a problem until I added a 3ware 9500S-12. With the 3ware card in the
network doesn't work, take it out and it works. From the dmesg bits below it
looks like both twa0 and skc0 are trying to use irq 18 and twa0 is winning. I
have the bios set to handle pnp stuff so I don't know whats going on. Any
suggestions?

---
pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci1: <ACPI PCI bus> on pcib1
3ware device driver for 9000 series storage controllers, version: 3.50.00.017
twa0: <3ware 9000 series Storage Controller> port 0xac00-0xacff mem
0xfd000000-0xfd7fffff,0xfcfff000-0xfcfff0ff irq 18 at device 6.0 on pci1
twa0: INFO: (0x15: 0x1300): Controller details:: 12 ports, Firmware FE9X
2.06.00.009, BIOS BE9X 2.03.01.051
pci1: <display, VGA> at device 7.0 (no driver attached)
skc0: <Marvell Gigabit Ethernet> port 0xa800-0xa8ff mem
0xfcff8000-0xfcffbfff irq 18 at device 10.0 on pci1
skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:01:29:fc:8c:59
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
skc0: couldn't set up irq
e1000phy0: detached
miibus0: detached
sk0: detached
device_attach: skc0 attach returned 22
pci0: <bridge> at device 10.0 (no driver attached)
---

On Sat, August 13, 2005 8:02 pm, Brandon Fosdick said:
> So I'm having yet another problem with my AMD64x2/nforce4 system. Of
the
> two builtin NICs 5.4-S is only recognizing the marvell gigabit chip,
> which wasn't a problem until I added a 3ware 9500S-12. With the 3ware
> card in the network doesn't work, take it out and it works. From the
> dmesg bits below it looks like both twa0 and skc0 are trying to use irq
> 18 and twa0 is winning. I have the bios set to handle pnp stuff so I
> don't know whats going on. Any suggestions?
The easiest thing would probably be to disable the onboard sk card, and
put in an em (intel gigabit card). The marvell chipset and driver is known
to be problematic.