RE: IRQ conflict between twa0 and skc0
From: Brandon Fosdick [mailto:[EMAIL PROTECTED] Darren Pilgrim wrote: Try switching slots with the RAID and video cards. It's silly, but then so is PCI interrupt routing. Unbelievable. Who ever wrote the PCI spec should have been shot. I believe the IEEE was involved. :) I switched the cards and now the network card is sharing an interrupt with the video card, but neither seems to mind. More importantly it isn't sharing with the raid card and they all appear to be happy. IRQ sharing is a known issue with many RAID cards and even some gigabit ethernet cards. It seems to correlate to cards that push the performance limit of the bus. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Darren Pilgrim wrote: I believe the IEEE was involved. :) That explains a lot :) IRQ sharing is a known issue with many RAID cards and even some gigabit ethernet cards. It seems to correlate to cards that push the performance limit of the bus. And here I am with both a RAID card and a gigabit ethernet chip. Fortunately the slot swap seems to have sorted everything out. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
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 0xfd00-0xfd7f,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) --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Mike Jakubik wrote: 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. I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
On Sun, August 14, 2005 12:47 am, Brandon Fosdick said: I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing. You can always use ssh and a serial console. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
On Sun, August 14, 2005 12:47 am, Brandon Fosdick said: I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing. Forgot to mention. You can always buy a cheap pciE video card :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IRQ conflict between twa0 and skc0
From: Brandon Fosdick Mike Jakubik wrote: 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. I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing. Try switching slots with the RAID and video cards. It's silly, but then so is PCI interrupt routing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Mike Jakubik wrote: Forgot to mention. You can always buy a cheap pciE video card :) You're a big help :) I was fiddling and I noticed something odd. Previously, the ESCD screen at boot showed the raid controller and network controller both at IRQ 5. The dmesg I sent before showed both at IRQ 18. That seemed odd to me. I also noticed that unused drive channels were being assigned IRQs so I disabled them in the BIOS. The idea being to free up an IRQ and maybe one of the controllers would use it. Now the ESCD table shows both the raid and the network on IRQ 10 and dmesg still shows them at IRQ 18. This seems screwy to me, but I have no idea what it means. Now that I know both IRQs 10 and 18 are useable, is there some way to force the drivers? Aren't there some boot hints that handle this? Or was it done in the kernel config. I can't remember. BTW, this is all with the stock SMP kernel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Darren Pilgrim wrote: Try switching slots with the RAID and video cards. It's silly, but then so is PCI interrupt routing. Unbelievable. Who ever wrote the PCI spec should have been shot. I switched the cards and now the network card is sharing an interrupt with the video card, but neither seems to mind. More importantly it isn't sharing with the raid card and they all appear to be happy. Thanks, that was a big help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
