From owner-freebsd-wireless@FreeBSD.ORG Fri May 3 08:28:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5D2A0B56; Fri, 3 May 2013 08:28:18 +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 144B61DEB; Fri, 3 May 2013 08:28:18 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c5e0:df4d:ce7d:bcd9]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id DD2D74AC57; Fri, 3 May 2013 12:28:15 +0400 (MSK) Date: Fri, 3 May 2013 12:28:11 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <94971208.20130503122811@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 08:28:18 -0000 Hello, Adrian. You wrote 3 =EC=E0=FF 2013 =E3., 8:22:40: >> I'll do some further digging. It may be that I just give in and add >> the TXQ stall workaround. I'd however like to avoid doing that if >> possible. :-) AC> Hm, I'm reproducing it here and I see some odd descriptor behaviour. AC> I'll tinker with it a bit more locally. AC> There's at least one bug in the TX code to do with descriptor AC> handling, but it didn't fix everything. I'll have to re-review things AC> to make sure everything is handled in the correct order. AC> I'll let you know when I have something to test! Adrian! I want to thank you for your hard and fantastic work! If I visit USA (when I visit?) and will be near your place of living I want to buy your at least beer :) Or two :) --=20 // Black Lion AKA Lev Serebryakov