From owner-freebsd-wireless@FreeBSD.ORG  Fri Apr 26 21:17:27 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 878268EE;
 Fri, 26 Apr 2013 21:17:27 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com
 [IPv6:2a00:1450:400c:c05::22d])
 by mx1.freebsd.org (Postfix) with ESMTP id E89961E4E;
 Fri, 26 Apr 2013 21:17:26 +0000 (UTC)
Received: by mail-wi0-f173.google.com with SMTP id c10so1065966wiw.6
 for <multiple recipients>; Fri, 26 Apr 2013 14:17:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type
 :content-transfer-encoding;
 bh=3SbV+6+MmirHC02tri7I7lCUpKwgcfnqm2mI5qTQj4E=;
 b=DGAS2/xgyi63eSBnxu9KT80F7DY5B71+y69HA4vQ6ys+AHn9rcpMLeQ0g39Rl5m2tC
 xg+cnZqHH+7dYUY456DtdvUWKDNqw4vsf7Az7xW7HkZfN+GmyGa/Gp6vnEZfzYbR4Qqi
 6TSuL1dXyUx1IpuC1SZX2V5qjWj6Q/I8NCggz7yxLylZ6GmZIlzGrK5cFQOwRco5z03g
 KVlDBVx7u/JoSs1keY8i3OHfRckAbcOyVqfAy5rBtB2Th1DsHfjPb5rK6u5Le2ryNtA1
 UxIxP0ys5d81iVud2iUBoeEbNorE83QP5SO3BQtgWV6DREmgMAZTO1/VKMe/py7XwvsX
 uvlQ==
MIME-Version: 1.0
X-Received: by 10.194.119.33 with SMTP id kr1mr4039288wjb.36.1367011046030;
 Fri, 26 Apr 2013 14:17:26 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 14:17:25 -0700 (PDT)
In-Reply-To: <1091133497.20130427011423@serebryakov.spb.ru>
References: <2810538978.20130423164137@serebryakov.spb.ru>
 <CAJ-Vmom4UDoz7EgdnVeQ+ALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com>
 <1813905823.20130423184528@serebryakov.spb.ru>
 <CAJ-VmomhRaKODxis09MjAhUbAUOw+6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com>
 <184105677.20130424002002@serebryakov.spb.ru>
 <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com>
 <1936997795.20130424003555@serebryakov.spb.ru>
 <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com>
 <886711115.20130424004702@serebryakov.spb.ru>
 <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com>
 <6010292503.20130426001447@serebryakov.spb.ru>
 <CAJ-VmomUsPgHTVGaKHZ_YE+u1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com>
 <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com>
 <99510815.20130426122508@serebryakov.spb.ru>
 <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com>
 <766430457.20130426125828@serebryakov.spb.ru>
 <CAJ-Vmo=kGvPmejzsMw_T5MtL0HyLGa9kNnX_tt0PnFo6M4g37A@mail.gmail.com>
 <1091133497.20130427011423@serebryakov.spb.ru>
Date: Fri, 26 Apr 2013 14:17:25 -0700
X-Google-Sender-Auth: XmiFOMHpsRzLmoj0tDGCquhx9pQ
Message-ID: <CAJ-Vmom5kKL5YZEXvkqiWWWLY69PJPHES7Np=byr+c7NjH_u-Q@mail.gmail.com>
Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic
From: Adrian Chadd <adrian@freebsd.org>
To: lev@freebsd.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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, 26 Apr 2013 21:17:27 -0000

On 26 April 2013 14:14, Lev Serebryakov <lev@freebsd.org> wrote:
> Hello, Adrian.
> You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 18:56:57:
>
> AC> And please cc -wireless with your debugging results :)
>  Ok.
>    It is interesting how throughput is not connected to rate after
>  these problems. Now I have client at stable 270M rate with RSSI ~28,
>  and only 15-20Mbit/s of UDP traffic AP->Client... :(
>
>    It looks like throughput is bad after card reset without reboot...
>   But no ath_bar_suspend!
>
>    Yes, after full reboot throughput is osscilate between 65 and
>  120Mbit/s! But with bar_suspsends!
>
>    Maybe, it is coincidence, but I npotice this for second time...

All kinds of reasons for this behaviour. We'll look into it after we
nail down why the TX queue is stalling.



adrian