Re: Atheros 9287 - no carrier . revision 249623.
Hi, I've just committed some changes to -HEAD. Please update to the latest -HEAD and paste me the ath0 dmesg output. It will include the chainmask information. Thanks, Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9287 - no carrier . revision 249623.
Adrian, I found the problem. I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define ATH_ENABLE_11N - everything work. Artyom Mirgorodskiy On Friday 19 April 2013 13:27:21 wrote: Updated. However I did not see chainmask information. See attached On Friday 19 April 2013 00:57:12 Adrian Chadd wrote: Hi, I've just committed some changes to -HEAD. Please update to the latest -HEAD and paste me the ath0 dmesg output. It will include the chainmask information. Thanks, Adrian -- Artyom Mirgorodskiy -- Artyom Mirgorodskiy ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9287 - no carrier . revision 249623.
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 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9287 - no carrier . revision 249623.
On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote: Ok, the relevant / interesting bit:s. John, any ideas? Only that this means absolutely nothing? These are the values the BIOS wrote into the registers which we use as hints about whether or not ACPI lies about which interrupts are used when APIC is disabled. The actually useful message shows the same interrupts used in both cases: HEAD: pcib2: slot 0 INTA hardwired to IRQ 18 ath0: Atheros 9287 mem 0xe050-0xe050 irq 18 at device 0.0 on pci10 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60 versus pcib2: slot 0 INTA hardwired to IRQ 18 ath0: Atheros 9287 mem 0xe050-0xe050 irq 18 at device 0.0 on pci10 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60 -- John Baldwin ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
