From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 21:34: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 CAD5577; Fri, 26 Apr 2013 21:34:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 370011F78; Fri, 26 Apr 2013 21:34:25 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so1230447wie.5 for ; Fri, 26 Apr 2013 14:34:24 -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 :content-transfer-encoding; bh=WGe5BKbvrGUjaYAxL3Kb+HMj2k5NnRW7Oprf8hx1/ik=; b=dJ9fgzF88GcyBzAtGx5cC5u6mmhAdaa6gbP0Xp57iU3mWOnbFgQkN1+9qxA3/2C0A8 02wATKvRzMjaLtvBaLz5yO5v7KgJoJYYhhmgZYlUSFeA12+BQS44GbZvX2dDQgqaxCXZ UM5YJvKvBP+gVebAGm9gX05i5JqMf2bBtYDY6oSwLKCyeIvVc5hD5UfCsk0cI5M/WtQz bgyAb8/oCM8+cZgc2wzPJjff7EubFP/ibWhzuSPQSjJcT2J1oPJs5GVTTuQF/jgB8B6I WnnyzKr5Av9lUPDCok51/RNwlwINiGhA+OQSJHkclyLyQUQFMYRfBF+Relw8CIBSw8f9 bFWg== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr6534693wib.22.1367012064338; Fri, 26 Apr 2013 14:34:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 14:34:24 -0700 (PDT) In-Reply-To: <1977535276.20130427012851@serebryakov.spb.ru> 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> <1977535276.20130427012851@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 14:34:24 -0700 X-Google-Sender-Auth: v8u6-D0JiY2Rv9nKB2svTkmEPnE 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=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 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, 26 Apr 2013 21:34:25 -0000 You're not doing something like leaving bgscan enabled, or not defining a channel up front? There's a lot of resets hre. adrian On 26 April 2013 14:28, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 12:51:17: > >>> Wait. sysctl dev.ath.0.forcebstuck=3D1 didn't fix it? > Ok, several such commands helps without down/up of interface. > Log attached: a lot of traffic, several BAR retransmits, interface > hangs, several "forcebstuck=3D1", client could associate again and > interface passes traffic. > > Maybe, there were too many "forcebstuck=3D1", but one ro two doesn't > fix situation for sure, client was not able to assotate after first > two of them. > > -- > // Black Lion AKA Lev Serebryakov