From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 23 19:57: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 3302B5F4; Tue, 23 Apr 2013 19:57:17 +0000 (UTC) (envelope-from bordjukov@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id CA1401BC7; Tue, 23 Apr 2013 19:57:16 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id b12so533716qca.18 for ; Tue, 23 Apr 2013 12:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DJlX9UAO4YjUW3GNKzkX2GKByth65iq1VL4Tdq1NMFM=; b=fPnDSYGelj0V/jB92kpMRstOo6A+UQ3YiIw3xsK+c4Z+TJ9fbwZYJg9M/t8uv63bhJ tYF64Mph3c4FbzswCJf81yorDSSJjwPLjKTCrtfhrRA88Fi4HTpPfLzBkQ+fvxzu8WKn OfrpwX0DeCDo935tIlMiO4zpkd9ix+kkNC165mUwwJFg97YpfwiijLUq7WkR3nzbRGPm NA9VXdikVE7yd7pryJTLac0lRxc4VMvkKQJItJvjYx1v3a1dbAe6zmltU+oCJq/gP9Ll YXZCAy9KK4aU1pmM3Dart3L6+rFbPXud5WhabjugPNIQwZMHQdmF8hua546pjV0lKqAZ ar+w== MIME-Version: 1.0 X-Received: by 10.49.16.99 with SMTP id f3mr30895985qed.27.1366747035535; Tue, 23 Apr 2013 12:57:15 -0700 (PDT) Received: by 10.49.39.39 with HTTP; Tue, 23 Apr 2013 12:57:15 -0700 (PDT) In-Reply-To: <1813905823.20130423184528@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> Date: Tue, 23 Apr 2013 22:57:15 +0300 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Petko Bordjukov To: lev@freebsd.org 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 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, 23 Apr 2013 19:57:17 -0000 Falling back to a ht:20- channel did considerably lower the number of stuck beacon messages on my AR9220. It still periodically hangs though (is this why ``baseband hangs?'' is listed in the wiki?). On Tue, Apr 23, 2013 at 5:45 PM, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 23 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 18:43:45: > > AC> Try dropping it down to a HT20 channel. > AP or client or both? Is it enough to disable HT40 channels on > client? > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " >