On 2018-05-02 21:10, Tim Chase wrote: > On 2018-05-02 23:21, Adrian Chadd wrote: > > CAn you try booting freebsd-head and see if it's any better? > > At your advice, I created a boot image of 12.0-CURRENT r333017 but > see the same "could not map interrupt" in my dmesg that I got on > 11.x
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. -tim _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
