From owner-freebsd-current@FreeBSD.ORG Thu Mar 5 21:38:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F90D1065676 for ; Thu, 5 Mar 2009 21:38:13 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 022438FC1D for ; Thu, 5 Mar 2009 21:38:12 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n25Lc7Cj094822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Mar 2009 13:38:08 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49B0463F.8090906@freebsd.org> Date: Thu, 05 Mar 2009 13:38:07 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Hugo Silva References: <49B02C40.9000407@barafranca.com> In-Reply-To: <49B02C40.9000407@barafranca.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: ath0: stuck beacon; resetting (bmiss count 4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2009 21:38:14 -0000 Hugo Silva wrote: > Mar 5 19:27:48 daedalus kernel: ath0: stuck beacon; resetting (bmiss > count 4) > Mar 5 19:28:19 daedalus last message repeated 95 times > Mar 5 19:30:20 daedalus last message repeated 359 times > Mar 5 19:32:54 daedalus last message repeated 481 times > Mar 5 19:32:54 daedalus kernel: > Mar 5 19:32:55 daedalus kernel: ath0: stuck beacon; resetting (bmiss > count 4) > Mar 5 19:33:23 daedalus last message repeated 80 times > Mar 5 19:33:23 daedalus kernel: ath0: stuck beacon; resetting (bmkss > ccunt 4e > Mar 5 19:33:23 daedalus kernel: > Mar 5 19:33:23 daedalus kernel: ath0: stuck beacon; resetting (bmiss > count 4) > Mar 5 19:33:27 daedalus last message repeated 11 times > > > ath0@pci0:5:1:0: class=0x020000 card=0x5a001385 chip=0x0013168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > class = network > subclass = ethernet dmesg|grep ath is more useful in identifying the device > > > wlan0: flags=8843 metric 0 mtu > 2290 > ether xxx > inet xxx netmask 0xffffff00 broadcast xxx.255 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid xxx channel 5 (2432 Mhz 11g) bssid xxx > regdomain ETSI country XX ecm authmode WPA privacy MIXED > deftxkey 2 > TKIP 2:128-bit txpower 30 scanvalid 60 pureg protmode CTS wme > burst ff > dturbo -apbridge dtimperiod 1 -dfs > > > After some time, the AP dies - my laptop scanning for an access point > will no longer show on tcpdump -pntttiath0 (on the AP). "AP dies" is not helpful > > The system itself is still up, it's just that it's no longer possible > to associate with the AP. > Rebooting makes the AP work again. > > > Suggestions? "stuck beacon" means the ap tried to xmit a beacon frame but for various reasons (where "various" is VERY large) it wasn't able to. After N consecutive attempts, 4 in this case) it gives up and resets the device (which should bring it back to life in case it's stuck because of a hardware bug). Often this occurs because you are using a slow platform and the time provided to prepare the beacon frame is insufficient to push it to the hardware fast enough to meet the realtime requirements. This can be exacerbated by operating on a busy channel. Unfortunately you've provided very little info so I can't advise you. I suggest you search for this subject and look at the discussions that have occurred for the last 5-6 years... Sam