New ath code works well as AP

[Slawa Olhovchenkov]

On Mon, Aug 20, 2012 at 09:57:54AM -0700, Adrian Chadd wrote:

> >> Well, what do you mean by "lost traffic" ? I need some more
> >> information about that.
> >
> > Sometimes (may be one in 2-3 days) receiving packets on wlan0 stoped.
> > May be intesive traffic increase probability.
> > No messages in dmesg. tcpdump on wlan0 show only outgoing packets. Interface is UP.
> > No automatic recovery. For manual recovery I am need to kldunload/kldolad if_ath_pci.
> 
> The next time it happens:
> 
> * sysctl dev.ath.0.txagg=1 (I assume your interface is ath0) - that
> dumps some basic information about the state of the aggregation logic
> _AND_ the hardware TX queues;

This is one time diagnostic, not trigger logic?

> * check dmesg;
> * ifconfig -v wlan0 and ifconfig -v wlan0 list sta (to see if 11n is enabled).

My AP don't support 11n, only 11g.

> You shouldn't have to unload/reload the driver. A simple ifconfig
> wlan0 down ; ifconfig wlan0 up (and restarting wpa_supplicant if it
> was running) should be enough. (Oh, and running dhclient.)
> 
> You can also enable reset+TX debugging when things hang (sysctl
> dev.ath.0.debug=0x3) and then do something like 'ifconfig wlan0 down';
> it will then dump out the state of the hardware/software queue(s) and
> hopefully give me a better idea of what state the hardware/driver is
> in.

OK.