From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 08:45:43 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 09B03415; Fri, 26 Apr 2013 08:45:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by mx1.freebsd.org (Postfix) with ESMTP id 6A2B21872; Fri, 26 Apr 2013 08:45:42 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id m6so325183wiv.15 for ; Fri, 26 Apr 2013 01:45:41 -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=lenNWukPhti1Sy6L3XzPHxa7Q5dto7QxwkeDxodqz5I=; b=FB4xrH+Gdkomhljny9VKCgPuHunzcF/6WCUrOkvEqbSU+YvkS54NAJwLKAxaA0L68C nPUrPQke5Po5BW+xNNMDhR92TaXUakZgDYQm3nzwkm9/XsEIu9zIJckG4TaPZTO5+KF5 SyMf8ga+JDDKZoDzqZyDPwKtllWaMAnBS2YVYYmd3pkm/uV1cDySuyqdejEtuCdHI0ts lRsWOyScX0cykc64ToKBeUmUBizbm/rz9l4neFriLpvhbF7D560vVKBigk93LwZfsIzZ MVeqbsGrPc7RQZnAXFUpnAGs2u6lbHxmVOZz6reGITox9f1Ptvk8i+sASo79EwikCxch A9VQ== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr2477163wib.22.1366965941611; Fri, 26 Apr 2013 01:45:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 01:45:41 -0700 (PDT) In-Reply-To: <99510815.20130426122508@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> Date: Fri, 26 Apr 2013 01:45:41 -0700 X-Google-Sender-Auth: GitMCmgmKVKutaBU7jAGxdiBIIs 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 08:45:43 -0000 Hi, Wait. sysctl dev.ath.0.forcebstuck=3D1 didn't fix it? adrian On 26 April 2013 01:25, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 4:11:44: > > AC> Ok. Next time it happens, force a stuck beacon: > GOT IT! > > You could use "sudo" messages as markers in log file. > It was: > > sysctl dev.ath.0.debug=3D0x900000020 > > > sysctl dev.ath.0.forsebstuck=3D1 > ifconfig wlan0 down > > ifconfig wlan0 up > /etc/rc.d/hostapd restart > > -- > // Black Lion AKA Lev Serebryakov