Hi, Try setting it up without 11n enabled:
ifconfig wlan0 create wlandev ath0 wlanmode hostap channel 6:g .. and if that doesn't help, try with 11n enabled but without ampdutx: ifconfig wlan0 -ampdutx I'm not using the AR5416 as an AP at the moment but it should be ok. I'm definitely using it as a station though. Can your try -HEAD instead? I don't plan on MFCing things myself back to stable/10; i rely on others who are actively using stable/10 to do it. -a On 21 April 2014 17:59, Greg Byshenk <[email protected]> wrote: > On Mon, Apr 21, 2014 at 09:30:47AM -0700, Adrian Chadd wrote: > >> Which NIC? > > It is a TP-Link TL-WN951N "Wireless N PCI Adapter". > > dmesg: > ath0: <Atheros 5416> mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci4 > ath0: AR5416 mac 13.10 RF2133 phy 8.1 > > pciconf: > ath0@pci0:4:0:0: class=0x028000 card=0x3071168c chip=0x0023168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5008 Wireless Network Adapter' > class = network > > On 9-STABLE, I see an occasional "stuck beacon" error, but all > carries on more or less happily after. On 10-STABLE, the errors > as mentioned. (It is 10-STABLE, revision 264683). > > -greg > > >> On 21 April 2014 08:58, Greg Byshenk <[email protected]> wrote: >> > On Sun, Apr 20, 2014 at 07:09:33PM -0700, Adrian Chadd wrote: >> >> I didn't say it in the commit message, but this should be MFCed to >> >> stable/10 . >> > >> > >> > Adrian- >> > >> > I'm curious as to what this addresses. >> > >> > I attempted to move a router/access point to FreeBSD 10 over the >> > weekend, and had to revert back to 9 as it was a terrible failure. >> > >> > It would invariably spew out masses of 'stuck beacon; resetting' >> > errors, and then at some point (not obviuously correlated with >> > those errors) lock up (hard, requiring a hard reset). >> > >> > If it is something that the patch might address, then I'll watch >> > for an MFC to stable/10 >> > >> > Thanks, >> > -greg >> > >> > >> >> On 20 April 2014 19:05, Adrian Chadd <[email protected]> wrote: >> >> > Author: adrian >> >> > Date: Mon Apr 21 02:05:51 2014 >> >> > New Revision: 264710 >> >> > URL: http://svnweb.freebsd.org/changeset/base/264710 >> >> > >> >> > Log: >> >> > Make sure bf_next is NULL'ed out when we're completing up an aggregate >> >> > frame through the cleanup path. >> >> > >> >> > Whilst here, fix the indenting for something I messed up. >> >> > >> >> > Tested: >> >> > >> >> > * AR5416, STA mode >> >> > >> >> > Modified: >> >> > head/sys/dev/ath/if_ath_tx.c >> >> > >> >> > Modified: head/sys/dev/ath/if_ath_tx.c >> >> > ============================================================================== >> >> > --- head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:04:37 2014 >> >> > (r264709) >> >> > +++ head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:05:51 2014 >> >> > (r264710) >> >> > @@ -4600,10 +4600,11 @@ ath_tx_comp_cleanup_aggr(struct ath_soft >> >> > >> >> > ATH_TX_UNLOCK(sc); >> >> > >> >> > - /* Handle frame completion */ >> >> > + /* Handle frame completion as individual frames */ >> >> > bf = bf_first; >> >> > while (bf) { >> >> > bf_next = bf->bf_next; >> >> > + bf->bf_next = NULL; >> >> > ath_tx_default_comp(sc, bf, 1); >> >> > bf = bf_next; >> >> > } >> >> > @@ -5849,7 +5850,7 @@ ath_tx_node_reassoc(struct ath_softc *sc >> >> > ":", >> >> > i); >> >> > /* >> >> > - * In case there's a followup call to this, only call it >> >> > + * In case there's a followup call to this, only call it >> >> > * if we don't have a cleanup in progress. >> >> > */ >> >> > if (! tid->cleanup_inprogress) { >> >> > >> >> _______________________________________________ >> >> [email protected] mailing list >> >> http://lists.freebsd.org/mailman/listinfo/svn-src-all >> >> To unsubscribe, send any mail to "[email protected]" >> > >> > -- >> > greg byshenk - [email protected] - Portland, OR USA > > -- > greg byshenk - [email protected] - Portland, OR USA _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[email protected]"
