From owner-freebsd-wireless@FreeBSD.ORG  Fri Feb  3 07:03:11 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 A93AF106564A;
	Fri,  3 Feb 2012 07:03:11 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
	[IPv6:2a01:4f8:131:60a2::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 41B558FC16;
	Fri,  3 Feb 2012 07:03:11 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
	[IPv6:2001:470:923f:1:24ed:86dc:9f3b:9149])
	(Authenticated sender: lev@serebryakov.spb.ru)
	by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 70ECC4AC2D; 
	Fri,  3 Feb 2012 11:03:09 +0400 (MSK)
Date: Fri, 3 Feb 2012 11:03:04 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD Project
X-Priority: 3 (Normal)
Message-ID: <1167992329.20120203110304@serebryakov.spb.ru>
To: Adrian Chadd <adrian@freebsd.org>
In-Reply-To: <CAJ-Vmo=OuBC65ie7t2LeQof4mPngrEyNPwwuJuijk0W+VjGCDg@mail.gmail.com>
References: <743722267.20120202195757@serebryakov.spb.ru>
	<CAJ-Vmo=js__O2YfPuRQTH0WfaDg1oo0LmugoCV5hi6HUtksprQ@mail.gmail.com>
	<1292923023.20120202232810@serebryakov.spb.ru>
	<CAJ-VmonApDTGUU0JgFWQApktHW0Xi6Fq2dbDNkP_Hu_Q29KL9g@mail.gmail.com>
	<208667374.20120203002726@serebryakov.spb.ru>
	<CAJ-Vmo=OuBC65ie7t2LeQof4mPngrEyNPwwuJuijk0W+VjGCDg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-wireless@freebsd.org
Subject: Re: "ath0: device timeout" when environment is clear
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lev@FreeBSD.org
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: Fri, 03 Feb 2012 07:03:11 -0000

Hello, Adrian.
You wrote 3 =F4=E5=E2=F0=E0=EB=FF 2012 =E3., 1:46:57:

> The lack of TX buffers in that list (they're all RX buffers) means
>  that the TX queue is empty.

> So, the "device timeout" is incorrect - the device didn't timeout,
> we just didn't queue any frames to the device but somehow the TX
> watchdog was set. Or, the watchdog wasn't cleared upon TX queue
>  processing.

> I wonder why this is occuring. =20
  Is here any additional diagnostic I could do?
  BTW, here are a lot of "stuck beacon" too, but these don't break file tra=
nsfer, only slow it.

--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>