From owner-freebsd-wireless@FreeBSD.ORG Sat May 4 05:09:16 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 4D154A83; Sat, 4 May 2013 05:09:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id A4D2014B1; Sat, 4 May 2013 05:09:15 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id x51so1808816wey.14 for ; Fri, 03 May 2013 22:09:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2Q4m+SPzyC9bg3nkHsQkjn09kn9BvMnm9utByP50LPw=; b=EuOJCbxuEnSRkLwYmLfZ6IhYM89fNvWw+RmIRWqQPfY7Ngwk6RHsju9A+0Af3zhl8w nG2FdIDpx/7DLw8qo7HiZgVLKTKnz2TEIXLHB14THKvi2kDtz6L9kQGccRclxlv2QGm5 aE2rJQBuOsmxFT/peRwBDDWDp8x3KxBr2oLEAwco/0t1nnyNeokPz+zRdpwdBdHisrb7 TzIOU3gA5Sx2loTOTuHg0VxKDL8kn3fW0XAp9mWfx7CSiadbX9uRfUZrNwgqm5/d99ia 0mroCQRFhuKtC465WFdeo2vHot50ebGU06De+EfO4h/FLvxT+Ttk+nY+9I5S5dmTl6NJ 9a3w== MIME-Version: 1.0 X-Received: by 10.180.88.162 with SMTP id bh2mr906434wib.3.1367644154867; Fri, 03 May 2013 22:09:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 3 May 2013 22:09:14 -0700 (PDT) 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> <94971208.20130503122811@serebryakov.spb.ru> Date: Fri, 3 May 2013 22:09:14 -0700 X-Google-Sender-Auth: Y7vkfr1b1FHNTacFq4Xfze1RWTk Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 04 May 2013 05:09:16 -0000 Hi, So doing this testing as a station doing the UDP transmitting (to a FreeBSD AP) is showing some interesting behaviour. No, i don't think it's your bug. The key re-negotiation seems to be failing somewhere; I bet it's out of sequence or out of order crypto frames. I've seen this happen before but I only fixed it for the AP case (by overriding the QOS for said frames so it appeared in a different TID, thus different sequence number space.) Since it's reauthing, it's transitioning the node through disassociate / re-auth / re-associate, but the current code in -HEAD isn't resetting the local state (aggregation, BAR state, filtered frames state, etc.) So things can and do go weird. I'll do some further digging into this and see if I can resolve it. I thought I had fixed it but .. well, obviously not. Once I have resolved this rekey / disconnect issue I'll keep testing things out and see if I've fixed your issue. (And I'll do some testing in parallel in open mode, so I don't bite this bug.) adrian