From owner-freebsd-wireless@FreeBSD.ORG  Tue Apr 30 08:25:04 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 EA36E34F;
 Tue, 30 Apr 2013 08:25:04 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 77E7B1269;
 Tue, 30 Apr 2013 08:25:04 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 211694AC57;
 Tue, 30 Apr 2013 12:25:02 +0400 (MSK)
Date: Tue, 30 Apr 2013 12:24:59 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD Project
X-Priority: 3 (Normal)
Message-ID: <124956607.20130430122459@serebryakov.spb.ru>
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic
In-Reply-To: <CAJ-Vmo=b-kBDWKz=Y709kYEsYQt3ZRczCN0wG9zDRk=sR60+tg@mail.gmail.com>
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.s
 pb.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>
 <CAJ-Vmo=MzeJsKHfVoipPQqCRmkOHWk6p-iZNaXDwye6oG+76xg@mail.gmail.com>
 <CAJ-Vmo=b-kBDWKz=Y709kYEsYQt3ZRczCN0wG9zDRk=sR60+tg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="----------0121790D21751CE77"
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
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/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: Tue, 30 Apr 2013 08:25:05 -0000

------------0121790D21751CE77
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: quoted-printable

Hello, Adrian.
You wrote 30 =E0=EF=F0=E5=EB=FF 2013 =E3., 8:53:00:

AC> Any follow-up with the latest stuff in -HEAD? I'd like to see if the
AC> hardware queue is behaving how I think it is.
  Sorry, was busy yesterday.
  Sources: r250041, TDMA is enabled in kernel config.

  Warm-up:  120  seconds  of  TCP, throughput osculate between 50 and
  100Mbit/, several BAR resets, no hangs.

  Test: 600 seconds of UDP. Throughput is 20Mbit/s. Hang on ~327s.
  traffic generator stopped, single "forced bstuck" helps.

  Log attached.


 Please, note: low throughput for UDP on these revisions. It was not
 so on older revisions, before all this additional debug stuff was
 added, latest good I tried was something like r249333, and I don't
 remember about r249767 (but I could try, firmware image is not
 removed, and I don't have images between r249333 and r249333).

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