From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 26 19:03:22 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 0C1A4E65 for ; Sat, 26 Jan 2013 19:03:22 +0000 (UTC) (envelope-from info@martenvijn.nl) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by mx1.freebsd.org (Postfix) with ESMTP id 8511CB63 for ; Sat, 26 Jan 2013 19:03:21 +0000 (UTC) Received: from [192.168.179.22] (vijn.xs4all.nl [80.101.129.129]) (authenticated bits=0) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id r0QJ3DXT071802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 26 Jan 2013 20:03:14 +0100 (CET) (envelope-from info@martenvijn.nl) Message-ID: <51042871.2090605@martenvijn.nl> Date: Sat, 26 Jan 2013 20:03:13 +0100 From: Marten Vijn User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: stuck beacon hung wifi adapter AR5008 References: <1359223263.8698.17.camel@eva02> In-Reply-To: <1359223263.8698.17.camel@eva02> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner 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, 26 Jan 2013 19:03:22 -0000 On 01/26/2013 07:01 PM, paranormal wrote: > Hi list. > > My system is -STABLE. > Since 9.1 MFC, may be a few months earlier, something was happened, and > stuck beacon errors make my wifi ap adapter unresponsible again. > I have to shutdown my ap once per week. > > How to figure it out? > > ifconfig: > wlan0: flags=8843 metric 0 mtu > 1500 > ether 00:1e:58:39:f8:7b > inet 192.168.11.1 netmask 0xfffffff0 broadcast 192.168.11.15 > inet 192.168.11.2 netmask 0xffffffff broadcast 192.168.11.2 > inet 192.168.11.3 netmask 0xffffffff broadcast 192.168.11.3 > inet 192.168.11.4 netmask 0xffffffff broadcast 192.168.11.4 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running > ssid mbsd channel 3 (2422 MHz 11g ht/40+) bssid 00:1e:58:39:f8:7b > regdomain ETSI indoor ecm authmode OPEN privacy OFF txpower 20 > scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme > burst dtimperiod 1 -dfs > > > There were after last adapter hung: > > 64 Jan 26 17:41:45 mbsd kernel: ath0: stuck beacon; resetting (bmiss > count 4) > 65 Jan 26 17:41:45 mbsd kernel: ath0: stuck beacon; resetting (bmiss > count 4) > 66 Jan 26 17:41:45 mbsd > kernel:~ > 67 Jan 26 17:41:45 mbsd kernel: ath0: stuck beacon; resetting (bmiss > count 4) > 68 Jan 26 17:41:48 mbsd last message repeated 14 > times > 69 Jan 26 17:41:48 mbsd > kernel:~ > 70 Jan 26 17:41:48 mbsd kernel: ath0: stuck beacon; resetting (bmiss > count 4) > 71 Jan 26 17:42:02 mbsd last message repeated 62 maybe: check you have antenna's on main + diversity, or make sure you have and a closing-end-connector (see documetentation of your ath card) on the diversity connector, and or maybe disable it in software, examples are in http://bsd.wifisoft.org/svn/projects/nek/events/ApacheCon-2012/accesspoint/Files/etc/sysctl.conf else install ath debug tools from /usr/src/tools/tools/ath 2ct, cheers Marten > times >