Sigh. Someone's broken the bus or interrupt handling code between -9 and -head. Or ACPI, for all I know. It may even be something to do with RFKILL.
Can you please boot verbosely, both on -9 and -head? you don't have to do anything - just capture the logfile /var/run/dmesg.boot and attach them here. Hopefully something glaringly different will stand out. Thanks, adrian On 18 April 2013 07:05, Artyom Mirgorodskiy <artyom.mirgorod...@gmail.com> wrote: > No interrupts at all: > > > > interrupt total rate > > irq1: atkbd0 474 1 > > irq9: acpi0 95 0 > > irq22: ehci1 504 1 > > irq23: ehci0 1037 3 > > irq256: hpet0:t0 8426 30 > > irq257: hpet0:t1 1823 6 > > irq258: hpet0:t2 1992 7 > > irq259: hpet0:t3 2112 7 > > irq264: hdac0 118 0 > > irq265: ahci0 4026 14 > > Total 20607 75 > > > > > > On Thursday 18 April 2013 06:56:14 Adrian Chadd wrote: > >> I've just tested -HEAD on a WB197 (AR9287 + bluetooth.) It works fine. > >> > >> I think it's very likely something to do with the bus enumeration. Can > >> you do a vmstat -i, see if you've seen any ath interrupts? > >> > >> > >> > >> adrian > > -- > > Artyom Mirgorodskiy _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"