[Bug 228409] PCI-PCI bridge IRQ not shared

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue May 22 00:43:02 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228409

            Bug ID: 228409
           Summary: PCI-PCI bridge IRQ not shared
           Product: Base System
           Version: CURRENT
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: freebsd at tim.thechases.com

I replaced the non-functioning Broadcom wifi card in my Dell Mini10 netbook
with an ath0 wireless card (https://www.amazon.com/gp/product/B00JESLUWQ/). The
dmesg output showed that it was identified, but that it couldn't allocate an
interrupt:

# dmesg | grep ath0
ath0: <Atheros 9280> mem 0xd8000000-0xd800ffff irq 17 at device 0.0 on pci2
ath0: could not map interrupt
device_attach: ath0 attach returned 6

Checking on it, IRQ17 was in use by my pcib1:

# dmesg | grep "irq 17"
pcib1: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
ath0: <Atheros 9280> mem 0xd8000000-0xd800ffff irq 17 at device 0.0 on pci2

Oleksandr Tymoshenko suggested a one-line diff
(https://people.freebsd.org/~gonzo/patches/pci_pci-shareable-irq.diff) to make
the PCI-PCI be RF_SHAREABLE.  Building with that diff resolved the issue and
now both the re0 (which AFAIC is the only item on pci1 on that pcib1) and the
ath0 are working fine.

So it *looks* like this solves the issue, but Adrian Chad informed me that
"warner says "pcie interrupts aren't shared."" and requested that I open a PR
on the matter to get more eyeballs on it.  So I'm opening this as requested.

Full conversation leading up to this can be found at
https://lists.freebsd.org/pipermail/freebsd-wireless/2018-May/thread.html#7968
including the initial dmesg output and the relevant new dmesg ath0 output after
applying Oleksandr's patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list