Date: Fri, 4 May 2018 10:37:17 -0500 From: Tim Chase <freebsd@tim.thechases.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath0: could not map interrupt (again?) Message-ID: <20180504103717.0417a0f6@bigbox.christie.dr> In-Reply-To: <20180504005448.GA89012@bluezbox.com> References: <20180502165745.59a5bfc4@bigbox.christie.dr> <CAJ-Vmo=uAB4Yv8fTu6yP5tDh82FtgFHQFDRWOGmNLYsABTvENw@mail.gmail.com> <20180502211001.550d290c@bigbox.christie.dr> <20180503192743.639240d0@bigbox.christie.dr> <20180504005448.GA89012@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-05-03 17:54, Oleksandr Tymoshenko wrote: > Tim Chase (freebsd@tim.thechases.com) wrote: > > If it makes any difference, booting OpenBSD 6.3 on the machine > > says they're both successfully on INT 17 (the ath0/athn0 works > > there) > > > > ppb0 at pci0 dev 28 function 0 "Intel SCH PCIE" rev 0x07: apic 2 > > int 17 ... > > athn0 at pci2 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2 > > int 17 athn0: AR9280 rev 2 (2T2R), ROM rev 22, address > > 00:24:d2:b3:8c:b4 > > > > so it looks like the interrupt *can* be shared, it just appears > > that FreeBSD is doing something peculiar with it. > > It looks like PCI bridge allocates interupt without RF_SHAREABLE > (see dev/pci/pci_pci.c, pcib_alloc_pcie_irq). Could you test > this patch [1]? I am not sure if non-shareable IRQs for PCI/PCI > bridge is a design decision or it's just that nobody has hit this > problem before. > > [1] > https://people.freebsd.org/~gonzo/patches/pci_pci-shareable-irq.diff Updated to head, applied the patch and am building world/kernel now. With this underpowered machine, I suspect it may take a while. Just wanted to let you know your suggestion didn't drop into the void ignored. -tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180504103717.0417a0f6>