From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 21 20:35:56 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B69ED106566C for ; Wed, 21 Dec 2011 20:35:56 +0000 (UTC) (envelope-from ml-freebsd-wireless@bettercom.de) Received: from mail.bettermail.de (f0.bettercom.de [95.156.194.53]) by mx1.freebsd.org (Postfix) with ESMTP id 188FA8FC0C for ; Wed, 21 Dec 2011 20:35:55 +0000 (UTC) Received: (qmail 46385 invoked by uid 98); 21 Dec 2011 21:09:13 +0100 Received: from 178.203.181.49 by f0.bettercom.de (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.96.3/12172. Clear:RC:1(178.203.181.49):. Processed in 0.019454 secs); 21 Dec 2011 20:09:13 -0000 Received: from ip-178-203-181-49.unitymediagroup.de (HELO [192.168.178.5]) (martin@[178.203.181.49]) (envelope-sender ) by mail.bettermail.de (qmail-ldap-1.03) with CAMELLIA256-SHA encrypted SMTP for ; 21 Dec 2011 21:09:13 +0100 Message-ID: <4EF23CD7.7090402@bettercom.de> Date: Wed, 21 Dec 2011 21:08:55 +0100 From: Martin Lesser User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: stuck beacon with if_ath: old but unresolved issue X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 21 Dec 2011 20:35:56 -0000 Hi all, I'm wondering if anyone has an idea how to fix http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/155100 - it's occuring on newer kernels as well as on older ones: [ml@fs ~]$ uname -a FreeBSD fs.bettercom.de 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:07:27 UTC 2011 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 [ml@fs ~]$ ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:11:0d:69:2f inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid BC_Home2 channel 5 (2432 MHz 11g) bssid 00:1b:11:0d:69:2f regdomain ETSI country DE indoor ecm authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 3 TKIP 2:128-bit TKIP 3:128-bit txpower 30 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs Extract from /var/log/messages: ath0: mem 0xd4000000-0xd400ffff irq 17 at device 4.0 on pci5 ath0: AR5413 mac 10.5 RF5413 phy 6.1 ... Dec 21 19:43:56 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 21 19:44:12 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 21 19:46:31 fs last message repeated 3 times Dec 21 19:51:09 fs last message repeated 2 times Dec 21 20:04:33 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 21 20:05:01 fs last message repeated 11 times Dec 21 20:07:10 fs last message repeated 32 times Dec 21 20:11:49 fs last message repeated 32 times Extract from /etc/rc.conf: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap country DE" ifconfig_wlan0="inet 192.168.100.1 netmask 255.255.255.0 up channel 5:g" I'm not living in a crowded area instead my FreeBSD-box has channel 5 "exclusiv"; only 2 or 3 other APs are in range of the box but working on another frequency (channels 1,2 and 11). BUT: The lines above from messages occured when the box sent bytes via another AP on channel 1 to which the BSD-box is connected via ethernet. This other AP has another bssid. So no traffic was sent on wlan0 interface but ath0 was affected by traffic generated nearby as you can see above. Finally the error may crash the box if wireless traffic keeps on a high rate (former postings about this issue state that too). What can I provide to get this bug in if_ath.c fixed? I would really like to use my BSD-box also as AP but in the moment I cannot do that reliable. At the moment I'm concerned whether a 3rd may be able to crash my BSD-box by producing a large amount of wireless traffic... Regards Martin