From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 18:50:17 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 85010686; Sun, 28 Apr 2013 18:50:17 +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 542741126; Sun, 28 Apr 2013 18:50:15 +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 E596C4AC57; Sun, 28 Apr 2013 22:50:06 +0400 (MSK) Date: Sun, 28 Apr 2013 22:50:06 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1467048277.20130428225006@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> <777510536.20130427123352@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------05F0631F60EBC40C1" 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 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: Sun, 28 Apr 2013 18:50:17 -0000 ------------05F0631F60EBC40C1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Adrian. You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 22:56:30: AC> Anyway, leave it how it is for now. Just update to the latest -HEAD AC> ath code and redo the testing. It will now log the whole TX queue AC> contents, not just the completed frames. Hopefully it'll be more AC> obvious. Ok, same test: UDP stream from AP to client (with iperf), limited to 300M. Only 11-30M seen by client now, but no beacon stucks. After AP hangs several forced beacon stucks + hostaptd restart allow client to re-associate. Log with dev.ath.0.debug=3D0x900000020 attached ("sudo" messages are left= as "time marks"). -- // Black Lion AKA Lev Serebryakov ------------05F0631F60EBC40C1--