From owner-freebsd-wireless@FreeBSD.ORG Thu May 9 21:13:25 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 99519522; Thu, 9 May 2013 21:13:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id 57570200; Thu, 9 May 2013 21:13:25 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id 9so6203736iec.8 for ; Thu, 09 May 2013 14:13:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:to:cc:reply-to:subject:in-reply-to :x-mailer:mime-version:content-type; bh=aicJzp/dXQK1Zy4dYTzMWiPDgXOBgLFYo0R5Kzk6zqg=; b=r9SJvnIJAdkD05+7KumZB3A/s0IpC4LWV8LIfnpF0Wc8+i1PVBCIx/PWAyRSAPURqS bK08h4zmEC/olJ4H0PfnjFrc/KYgvwuUvvjt9V84ocJeh+E0CQo9e/FYjPwxhgl4jiV3 4WrPrBEAaSnarK6rSTrAtfvlHnb7iSiN3e8kS2Zvk4UubPMSslSXOdhoNmqPqlt2TIl2 G8mPj0xC9lGf8FBQuNKoRwHx3wgpqtq8zMUDkY+rt1DzJ6XDzKKzsLNQucY5LG9rmpVz OjhYrzhelPE/XAo1eXtYXbV3GXKFlvg7VpCFh/24LzfPCfRSbxGflziMTztOOgFvwHcM 3oWw== X-Received: by 10.50.51.226 with SMTP id n2mr6624308igo.25.1368134005047; Thu, 09 May 2013 14:13:25 -0700 (PDT) Received: from www.palm.com (i-global235-qca.qualcomm.com. [199.106.103.235]) by mx.google.com with ESMTPSA id d9sm9419997igr.4.2013.05.09.14.13.15 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 09 May 2013 14:13:23 -0700 (PDT) Message-ID: <518c1173.093c320a.331b.fffff874@mx.google.com> Date: Thu, 9 May 2013 14:13:14 -0700 From: "Adrian Chadd" To: "Adrian Chadd" , "lev@freebsd.org" Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Adrian Chadd 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: Thu, 09 May 2013 21:13:25 -0000 Ah. So these non aggregate tests are showing a problem - there shouldn't be= 500 frames in the txq. Ever. That's just plain dumb. Because of this, the logic I introduced to limit queue depth for a node isn= 't working - the node software queue depth never grows past a handful. They= 're immediately queued to the hardware. I'll go and 'fix' the queue handling for non aggregate traffic sometime in= the next few days. I'll modify it so I only queue up to some threshold of= non aggregate frames into the hardware queue. Thanks, Adrian Sent from my Palm Pre on AT&T On May 9, 2013 1:33 PM, Adrian Chadd <adrian@freebsd.org> wrote:=20 Yup, looks like the TX queue is just too deep and the EAPOL messages aren't making out. I thought I fixed this. I'll see if I can replicate this on holidays, but it may take a while. But luckily this looks like I've fixed the hardware TX queue stall! adrian