Date: Mon, 20 Aug 2012 21:10:38 +0400 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP Message-ID: <20120820171038.GP98910@zxy.spb.ru> In-Reply-To: <CAJ-Vmo==FdM-pKCcw=afUxUTJqOn3cP-XqLHtFghbceTyPG_Ng@mail.gmail.com> References: <20120819071403.GF98910@zxy.spb.ru> <CAJ-Vmompt74rHx=C8Z5L978ciFN1LnPr2Mz=5PB3a%2BdgZJ8GVA@mail.gmail.com> <20120820125524.GL98910@zxy.spb.ru> <CAJ-VmokyTZyEEeodfmzFzA07tGVAu6QJHxNBWbrJpEMUb_Etig@mail.gmail.com> <20120820160344.GM98910@zxy.spb.ru> <CAJ-Vmo=wrZmTzObjRkoyNMvSQxTEehP9m3VTwaqHmDdU_kG1sg@mail.gmail.com> <20120820163118.GN98910@zxy.spb.ru> <CAJ-VmonybT879YHyJk3QWa8Dru2p4ogG0hHHq-fwgOtMzgNYug@mail.gmail.com> <20120820165435.GO98910@zxy.spb.ru> <CAJ-Vmo==FdM-pKCcw=afUxUTJqOn3cP-XqLHtFghbceTyPG_Ng@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120820171038.GP98910>