From owner-freebsd-wireless@FreeBSD.ORG  Mon Apr 29 07:49:05 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 6AEB66B8;
 Mon, 29 Apr 2013 07:49:05 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com
 [IPv6:2a00:1450:400c:c00::22e])
 by mx1.freebsd.org (Postfix) with ESMTP id CA5F71C37;
 Mon, 29 Apr 2013 07:49:04 +0000 (UTC)
Received: by mail-wg0-f46.google.com with SMTP id e11so3305574wgh.25
 for <multiple recipients>; Mon, 29 Apr 2013 00:49:03 -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;
 bh=YqI7G+EDM6unqhbN4Rt3UONldjHQ2gVVNB1ldN7x5Gw=;
 b=wG42edVdPDJ/SdRKC/nEG94BSmUI43dmWmta88bRJzYMqT9EuDmiNLJ5PaFeMpgxAe
 9LoKm/+HZ5ubOx7MJA2wCFAwO8vHE9dw5TMkjixyyKU3vwXFBlp/q48TX8MXlYs/Giul
 sD8ReSQCvBh6MZZdW1pTVDp309idHPyw9ubNErLfNjiq8t7Q78FT9EAV4RTYsKi2wl+A
 F3tolDsyXSNAulyhUP/kG4m7rzexqm56FV6K0MP6k+3abFF6t3SwqmxV8K2RXFJMorl5
 95e8GhSCkmcsFj4DlyNLPzrzWI/uO5Lcrv4AwXWnLdbh8ARKQJ/F1MpB2GPPc+JY/dzi
 8plA==
MIME-Version: 1.0
X-Received: by 10.180.107.6 with SMTP id gy6mr15698452wib.22.1367221743753;
 Mon, 29 Apr 2013 00:49:03 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.58.138 with HTTP; Mon, 29 Apr 2013 00:49:03 -0700 (PDT)
In-Reply-To: <187241224.20130429113623@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>
 <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com>
 <1467048277.20130428225006@serebryakov.spb.ru>
 <CAJ-VmokLKdwckXjzH64P=mYm9pZQzkCkJhDV4iojzJehXmJLLA@mail.gmail.com>
 <725880393.20130429004352@serebryakov.spb.ru>
 <CAJ-Vmokz=0rZM-nHtt9S+a-SxRLuyP+yDhSAbLpr0xFS+pO3vA@mail.gmail.com>
 <187241224.20130429113623@serebryakov.spb.ru>
Date: Mon, 29 Apr 2013 00:49:03 -0700
X-Google-Sender-Auth: 1XQFsUmwkeb437SyvQE6jiXH_1s
Message-ID: <CAJ-Vmo=MzeJsKHfVoipPQqCRmkOHWk6p-iZNaXDwye6oG+76xg@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=ISO-8859-1
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: Mon, 29 Apr 2013 07:49:05 -0000

There's likely some bugs with the AMPDU aggregation negotiating
kicking in when all the TX buffers are full. I thought that was fixed,
alas.

I'll investigate that later. I have to acquire some programmable
attenuators to do this.



adrian