From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 21 21:05:17 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 C13441065672 for ; Wed, 21 Dec 2011 21:05:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 793698FC0A for ; Wed, 21 Dec 2011 21:05:17 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so10607879vcb.13 for ; Wed, 21 Dec 2011 13:05:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8NIdy+f3K17Evd+yK6BdTRrzQZRon+/e7wC4J9BzZAI=; b=iTUoeK5npB3oATemZ8qNetAylDrSI09k+P+KmIaCIZTrtwkl6N1L1eJlRocJltjTxK TVpUE7ueaIFvh7dA+pqHAflwDQVJ3hwuR18X2wbNiDbXbgGjfgwc2ILv6RqItQdxlqUm 3yHtNFk7+wy+OIKk291H5qW+0QH9s2khgzDoQ= MIME-Version: 1.0 Received: by 10.220.232.10 with SMTP id js10mr6060485vcb.22.1324501516614; Wed, 21 Dec 2011 13:05:16 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.158.104 with HTTP; Wed, 21 Dec 2011 13:05:16 -0800 (PST) In-Reply-To: <4EF23CD7.7090402@bettercom.de> References: <4EF23CD7.7090402@bettercom.de> Date: Wed, 21 Dec 2011 13:05:16 -0800 X-Google-Sender-Auth: hojFa5H2OrZIU5VqSd17zxTo-9c Message-ID: From: Adrian Chadd To: Martin Lesser Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: 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 21:05:17 -0000 Does this happen on -HEAD too? Adrian On 21 December 2011 12:08, Martin Lesser wrote: > Hi all, > > I'm wondering if anyone has an idea how to fix > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/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 =A0i386 > > [ml@fs ~]$ ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > =A0 =A0 =A0 =A0ether 00:1b:11:0d:69:2f > =A0 =A0 =A0 =A0inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.10= 0.255 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <= hostap> > =A0 =A0 =A0 =A0status: running > =A0 =A0 =A0 =A0ssid BC_Home2 channel 5 (2432 MHz 11g) bssid 00:1b:11:0d:6= 9:2f > =A0 =A0 =A0 =A0regdomain ETSI country DE indoor ecm authmode WPA1+WPA2/80= 2.11i > =A0 =A0 =A0 =A0privacy MIXED deftxkey 3 TKIP 2:128-bit TKIP 3:128-bit txp= ower 30 > =A0 =A0 =A0 =A0scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs > > Extract from /var/log/messages: > > ath0: mem 0xd4000000-0xd400ffff irq 17 at device 4.0 on pc= i5 > 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=3D"wlan0" > create_args_wlan0=3D"wlanmode hostap country DE" > ifconfig_wlan0=3D"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. T= his > 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. Final= ly > the error may crash the box if wireless traffic keeps on a high rate (for= mer > 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 > _______________________________________________ > 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"