From owner-freebsd-wireless@FreeBSD.ORG  Mon Aug 20 17:08:15 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 07B02106566C;
	Mon, 20 Aug 2012 17:08:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
	by mx1.freebsd.org (Postfix) with ESMTP id A91B68FC12;
	Mon, 20 Aug 2012 17:08:14 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD))
	(envelope-from <slw@zxy.spb.ru>)
	id 1T3VUs-000LnN-Sx; Mon, 20 Aug 2012 21:10:38 +0400
Date: Mon, 20 Aug 2012 21:10:38 +0400
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Adrian Chadd <adrian@freebsd.org>
Message-ID: <20120820171038.GP98910@zxy.spb.ru>
References: <20120819071403.GF98910@zxy.spb.ru>
	<CAJ-Vmompt74rHx=C8Z5L978ciFN1LnPr2Mz=5PB3a+dgZJ8GVA@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJ-Vmo==FdM-pKCcw=afUxUTJqOn3cP-XqLHtFghbceTyPG_Ng@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
Cc: freebsd-wireless@freebsd.org
Subject: Re: New ath code works well as AP
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussions of 802.11 stack,
	tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 17:08:15 -0000

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.