From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 20:07:27 2013 Return-Path: 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 7244FEC2; Tue, 30 Apr 2013 20:07:27 +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 2A10615F1; Tue, 30 Apr 2013 20:07:26 +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 DFC234AC57; Wed, 1 May 2013 00:07:17 +0400 (MSK) Date: Wed, 1 May 2013 00:07:14 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <146903383.20130501000714@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> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> MIME-Version: 1.0 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 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: Tue, 30 Apr 2013 20:07:27 -0000 Hello, Adrian. You wrote 30 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 19:41:12: >> Warm-up: 120 seconds of TCP, throughput osculate between 50 and >> 100Mbit/, several BAR resets, no hangs. AC> Ok. But did it negotiate A-MPDU? I'm not sure. Both ends showed typical N speeds (Windows in connection properties, FreeBSD in "list sta"). AC> It's fine. We'll worry about aggregation later. Yep. AC> So here we go: AC> Apr 30 12:21:26 gateway kernel: ath0: ath_stoptxdma: tx queue [9] AC> 0xd8c3000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [0] 0, AC> active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [1] AC> 0xc720ed00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [2] 0, AC> active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [3] AC> 0xd8bec00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [8] AC> 0xc720d2c0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Notice how the hardware queue isn't active at all. There's frames in AC> the TXQ and the hardware points to the next frame to transmit (but you AC> didn't provide the whole list of frames that were in the TXQ, so I'm AC> going on what it said before.) I've provided everything I've had in log :) --=20 // Black Lion AKA Lev Serebryakov