From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 10 02:17:11 2013 Return-Path: Delivered-To: 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 B5BE49BC for ; Sun, 10 Feb 2013 02:17:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by mx1.freebsd.org (Postfix) with ESMTP id 52BE7314 for ; Sun, 10 Feb 2013 02:17:11 +0000 (UTC) Received: by mail-vc0-f172.google.com with SMTP id l6so3161542vcl.17 for ; Sat, 09 Feb 2013 18:17:03 -0800 (PST) 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; bh=7YlAE0oFvw5pHL6cb7yX/tI8P0H6rUL55AlBNvGgs/0=; b=CKzN7Qj37p44pqoLILxi0JISiw12M6Fw3Snb3VJOrGyvm/J9mt6VXB9UJS4mjKIqrQ 2pMb0Ckx7wfdbXNf57R9jj89yi9Ax3rcFWqoDepWnMaDPut5A7l2K0Rkzu0iEMBIUeu7 hwR75xux/cPGnE8yAvJKFq8lI8vwWohGemK/lQeJ9Z14f9jz6bq+lxvpnl7U2xiavrFK MQYoe/6IeUwqZ4fOpaUHmcGq1p0UX8E7qnEW7O0ZZmG8Q6vY21adYZj3CPSdxdOJMLGN GDLfDYypdsFbia1fpTLEbJdDI4T6K0ZZSgUskLNNrhw8QqOYK3Kxl+sD81PAw80mD/xl SqZA== MIME-Version: 1.0 X-Received: by 10.58.206.99 with SMTP id ln3mr13308703vec.36.1360462623847; Sat, 09 Feb 2013 18:17:03 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.58.206.105 with HTTP; Sat, 9 Feb 2013 18:17:03 -0800 (PST) In-Reply-To: References: Date: Sat, 9 Feb 2013 18:17:03 -0800 X-Google-Sender-Auth: rhWCjq12q8HdUVBhfTTukI4LOBQ Message-ID: Subject: Re: panic on removing urtw0 From: Adrian Chadd To: Eitan Adler Content-Type: text/plain; charset=ISO-8859-1 Cc: wireless@freebsd.org, Hans Petter Selasky 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: Sun, 10 Feb 2013 02:17:11 -0000 Yes to both - i think some USB stack / memory buffer changes are responsible for your issue. :-) Adrian On 9 February 2013 15:51, Eitan Adler wrote: > On 9 February 2013 14:01, Adrian Chadd wrote: >> On 9 February 2013 06:47, Eitan Adler wrote: >>> I recently encountered a kernel panic upon removing a urtw0 device. >>> This removal occurred during machine shutdown. >>> >>> The crashing kernel and textdump is available upon request. >>> >>> Unread portion of the kernel message buffer: >>> urtw0: failed to stop (USB_ERR_NOT_CONFIGURED) >> >> I'm pretty sure Hans has just fixed this for uath? > > I'm confused. Does this means he fixed it for uath, but not for urtw? > Or does this mean that same fix likely to work for both? > > -- > Eitan Adler From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 10 08:04:36 2013 Return-Path: Delivered-To: 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 6A07BD3; Sun, 10 Feb 2013 08:04:36 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id A5DCEE32; Sun, 10 Feb 2013 08:04:35 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 377150550; Sun, 10 Feb 2013 09:04:27 +0100 From: Hans Petter Selasky To: Adrian Chadd Subject: Re: panic on removing urtw0 Date: Sun, 10 Feb 2013 09:05:37 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: In-Reply-To: X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: 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: Sun, 10 Feb 2013 08:04:36 -0000 On Sunday 10 February 2013 03:17:03 Adrian Chadd wrote: > Yes to both - i think some USB stack / memory buffer changes are > responsible for your issue. :-) > Hi, Can you send me the backtrace of the panic and I'll fix it. I fixed panic upon attach. --HPS From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 10 08:38:09 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 8137F5CF for ; Sun, 10 Feb 2013 08:38:09 +0000 (UTC) (envelope-from k.s.mail@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by mx1.freebsd.org (Postfix) with ESMTP id 180CFEEC for ; Sun, 10 Feb 2013 08:38:08 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MRhn5-1UWjpr0iVt-00SueW for ; Sun, 10 Feb 2013 09:38:02 +0100 Received: (qmail invoked by alias); 10 Feb 2013 08:38:02 -0000 Received: from ip-130-180-70-188.unitymediagroup.de (EHLO mba.local) [130.180.70.188] by mail.gmx.net (mp010) with SMTP; 10 Feb 2013 09:38:02 +0100 X-Authenticated: #32709443 X-Provags-ID: V01U2FsdGVkX18ocGwR0VYoRN7KZZK5xLTdakj2fKZqbcu3dDQOri IivbgXf8XSPYmv Message-ID: <51175C69.6050003@gmx.net> Date: Sun, 10 Feb 2013 09:38:01 +0100 From: Kamil Szczesny User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: ath0: device timeout on 9.1-RELEASE Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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: Sun, 10 Feb 2013 08:38:09 -0000 Hello, I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not existent on 8.x-RELEASE. The issue seems to be the similar to this one: http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html I do have the same NIC. pciconf -lv output is equal: ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5008 Wireless Network Adapter' class = network /etc/rc.conf: wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP" /etc/wpa_supplicant.conf: network={ ssid="home" psk="123" } However, it is not starting to work. I do not have /usr/src/tools/ath so that I can not provide the output. /var/log/messages is spammed with: Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) Feb 10 09:08:30 gomorrha kernel: ath0: device timeout Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with xx:xx:xx:xx:xx:xx timed out. Any idea what might be wrong or how I could fix this? regards, Kamil From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 10 19:18:03 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 3730B100 for ; Sun, 10 Feb 2013 19:18:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id C8306E07 for ; Sun, 10 Feb 2013 19:18:02 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hi8so2450740wib.13 for ; Sun, 10 Feb 2013 11:17:55 -0800 (PST) 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; bh=Ul0FsUIfN6EiGjBgaRHEamSwJVruu2bYsLSz7SqDUe0=; b=FQxlvjSkJhEnzhHVchpACmi58EN/oht536J2uwUsVkx4mJv4MsSloni1UTdUgCYG3F ic7cSjFItlP2DecqJn225H4TzJn7YuUCFiJDYSApsOCX+ORFNkkiiduXA8oZryUnC2Ei 8ZFjOW02DzGWyX1j2S4Z3qhQjBjEGf1XATbSMHALZz84r9rVYsiZPvi3rUTKKheyrjlN lvrDefMuZHnR2VuPOcWR/RN+dToB1850xlsRcL8EgPHfGr+tWi+Osyc/UBmcQ22rFuvh 6AkLk68Kyd4Fk5ZsUaBoHnYUOvgPLyZKScIY0MVrCKc65WnfJMs3TiA65KMg4hlr95Kn 8IeA== MIME-Version: 1.0 X-Received: by 10.180.99.227 with SMTP id et3mr12151963wib.6.1360523440592; Sun, 10 Feb 2013 11:10:40 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Sun, 10 Feb 2013 11:10:40 -0800 (PST) In-Reply-To: <51175C69.6050003@gmx.net> References: <51175C69.6050003@gmx.net> Date: Sun, 10 Feb 2013 11:10:40 -0800 X-Google-Sender-Auth: TFq6QvCNiBCmu9xllveDB6LJWAw Message-ID: Subject: Re: ath0: device timeout on 9.1-RELEASE From: Adrian Chadd To: Kamil Szczesny Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 10 Feb 2013 19:18:03 -0000 Hi, Would you please try 9.0-RELEASE too? Adrian On 10 February 2013 00:38, Kamil Szczesny wrote: > Hello, > > I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not existent > on 8.x-RELEASE. > > The issue seems to be the similar to this one: > http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html > > I do have the same NIC. pciconf -lv output is equal: > > ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c rev=0x01 > hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5008 Wireless Network Adapter' > class = network > > /etc/rc.conf: > wlans_ath0="wlan0" > ifconfig_wlan0="WPA DHCP" > > /etc/wpa_supplicant.conf: > network={ > ssid="home" > psk="123" > } > > However, it is not starting to work. > > I do not have /usr/src/tools/ath so that I can not provide the output. > > /var/log/messages is spammed with: > > Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with > xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) > Feb 10 09:08:30 gomorrha kernel: ath0: device timeout > Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with > xx:xx:xx:xx:xx:xx timed out. > > Any idea what might be wrong or how I could fix this? > > regards, > Kamil > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 07:30:39 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 556FABC0 for ; Mon, 11 Feb 2013 07:30:39 +0000 (UTC) (envelope-from k.s.mail@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id D2873A52 for ; Mon, 11 Feb 2013 07:30:38 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MARmu-1UByaa00LK-00BeWn for ; Mon, 11 Feb 2013 08:30:38 +0100 Received: (qmail invoked by alias); 11 Feb 2013 07:30:37 -0000 Received: from eduroam-13-128.eduroam.ruhr-uni-bochum.de (EHLO mba.local) [134.147.13.128] by mail.gmx.net (mp020) with SMTP; 11 Feb 2013 08:30:37 +0100 X-Authenticated: #32709443 X-Provags-ID: V01U2FsdGVkX1+ysWlxYD6yxe4fBapR2NQv0UZTY0nfTMr0hdbTHO GGRyM9Oec8ZPSn Message-ID: <51189E1E.70206@gmx.net> Date: Mon, 11 Feb 2013 08:30:38 +0100 From: Kamil Szczesny User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath0: device timeout on 9.1-RELEASE References: <51175C69.6050003@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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: Mon, 11 Feb 2013 07:30:39 -0000 Hi, after a downgrade to 9.0-RELEASE the issue remains the same. /var/log/messages is spamed by equal authentication timeout entries. regards, Kamil Am 10.02.13 20:10, schrieb Adrian Chadd: > Hi, > > Would you please try 9.0-RELEASE too? > > > > Adrian > > > On 10 February 2013 00:38, Kamil Szczesny wrote: >> Hello, >> >> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not existent >> on 8.x-RELEASE. >> >> The issue seems to be the similar to this one: >> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >> >> I do have the same NIC. pciconf -lv output is equal: >> >> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c rev=0x01 >> hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR5008 Wireless Network Adapter' >> class = network >> >> /etc/rc.conf: >> wlans_ath0="wlan0" >> ifconfig_wlan0="WPA DHCP" >> >> /etc/wpa_supplicant.conf: >> network={ >> ssid="home" >> psk="123" >> } >> >> However, it is not starting to work. >> >> I do not have /usr/src/tools/ath so that I can not provide the output. >> >> /var/log/messages is spammed with: >> >> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with >> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >> xx:xx:xx:xx:xx:xx timed out. >> >> Any idea what might be wrong or how I could fix this? >> >> regards, >> Kamil >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 08:09:52 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 DC240A00 for ; Mon, 11 Feb 2013 08:09:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x229.google.com (wi-in-x0229.1e100.net [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id 6306DC35 for ; Mon, 11 Feb 2013 08:09:52 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id l13so2922786wie.4 for ; Mon, 11 Feb 2013 00:09:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=xN8oIgc2yBwP3RyXbOhWHE7TtjDC7emVlGC4ecRo4sg=; b=wpRWe6yPTbTaH9l+4jq1sAXhMZS1mvR/L4yFO9KdFwTo2YjadfmFkhnNzyfjiRAgX0 uWZe7S120wqJXlupR7agU/qkBgMmYsc6+JtHEUSu+RtpsM+a6lScRMdsd2mlx3RdIljG oc+sanvQpui2CSwlA/3/sMhCxywCISNeGgxRuO1TU+b3G3rS0KfTwt4QQh40s27Ef3W5 RaOH0njKBYfnDR9GZ5pW4CydRK+ehgR3fwL+sz+HnHgkFJtQ8UhdnQnm9F69ovjGsKEk ZwM2vzN0MTGMBcbvu6Su6ocIPYHFUfBJ+RzBeINIkYwjwcMFPyjes5XSRiAr8Hlu3mmN zIgA== MIME-Version: 1.0 X-Received: by 10.180.93.234 with SMTP id cx10mr9122457wib.34.1360570191621; Mon, 11 Feb 2013 00:09:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Mon, 11 Feb 2013 00:09:51 -0800 (PST) Date: Mon, 11 Feb 2013 00:09:51 -0800 X-Google-Sender-Auth: DyGWE-OWHGcS7tBYuWHp8O_9_C8 Message-ID: Subject: [ath] headsup - I'm likely going to revert a bunch of work in ath(4) soon From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 11 Feb 2013 08:09:52 -0000 Hi all, I'm likely going to revert a bunch of my work in ath(4) soon. I've been trying to chase down some performance issues that have crept in with my if_transmit() and software queue changes and .. well, to be honest, I'm just plain unhappy with it. It's utterly terrible - performance seems to have dropped down from 150+mbit down to 80mbit when using a FreeBSD transmitter. In hostap mode it seems fine - but in station mode running iperf it just has _terrible_ performance. So I'm going to back things out to some point in time in the past where it behaved ok, then re-apply the bugfixes and spectral scan code. I'm sorry for this code churn. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 11:06:55 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 1511A2F6 for ; Mon, 11 Feb 2013 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id ED4B01BE7 for ; Mon, 11 Feb 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1BB6sfr081477 for ; Mon, 11 Feb 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1BB6sMH081475 for freebsd-wireless@FreeBSD.org; Mon, 11 Feb 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Feb 2013 11:06:54 GMT Message-Id: <201302111106.r1BB6sMH081475@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to 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: Mon, 11 Feb 2013 11:06:55 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 150 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 18:59:19 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 0A5DCFA1 for ; Mon, 11 Feb 2013 18:59:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by mx1.freebsd.org (Postfix) with ESMTP id 95843781 for ; Mon, 11 Feb 2013 18:59:18 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id 16so4854390wgi.15 for ; Mon, 11 Feb 2013 10:59:17 -0800 (PST) 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; bh=kVJTJIiNYI6uQzr1F8kR6SanGHk9O6qu9k2v31KpvG0=; b=g6Q7rmPJM2lIrYEUtAub9CCuoBHe6dgcM6wKSaK9OoWPUSvsfz+FpLqzQgKht/Uyil 7CdlE2Exh6gTGLRfc6HIxTQyp+eiimhnM8Csc1Z8yIeMc70O0ujFVFBNNWxMLgk9WcTs 0MlRKCJrLlTAsODgpO+uNh10ZYR9y4utfrGSgNhY4Jqun7nFNwVFoJNYdclLkVr+nykN PZCgqyS/WtTYuVVaS+j4n3+xjQO1+eeTYWjsk0VcpwRggFsRtt8v0TF9oFvdYNT4Rukx 2weVi9lxOUa3l7yzOGeL0DaoLYdXwSH9t9nUIgg6HVGIRpZEa0CPLERTp1jfa8OQmUme FjDA== MIME-Version: 1.0 X-Received: by 10.194.7.136 with SMTP id j8mr26203178wja.38.1360609157568; Mon, 11 Feb 2013 10:59:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Mon, 11 Feb 2013 10:59:17 -0800 (PST) In-Reply-To: <51189E1E.70206@gmx.net> References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> Date: Mon, 11 Feb 2013 10:59:17 -0800 X-Google-Sender-Auth: WDxL3h5q-ShKoG64epLyEdlMros Message-ID: Subject: Re: ath0: device timeout on 9.1-RELEASE From: Adrian Chadd To: Kamil Szczesny Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 11 Feb 2013 18:59:19 -0000 Hi, Would you please look at the output of vmstat -i, see if the ath0 device is receiving interrupts? Thanks, Adrian On 10 February 2013 23:30, Kamil Szczesny wrote: > Hi, > > after a downgrade to 9.0-RELEASE the issue remains the same. > /var/log/messages is spamed by equal authentication timeout entries. > > regards, > Kamil > > Am 10.02.13 20:10, schrieb Adrian Chadd: > >> Hi, >> >> Would you please try 9.0-RELEASE too? >> >> >> >> Adrian >> >> >> On 10 February 2013 00:38, Kamil Szczesny wrote: >>> >>> Hello, >>> >>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not >>> existent >>> on 8.x-RELEASE. >>> >>> The issue seems to be the similar to this one: >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>> >>> I do have the same NIC. pciconf -lv output is equal: >>> >>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>> rev=0x01 >>> hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> device = 'AR5008 Wireless Network Adapter' >>> class = network >>> >>> /etc/rc.conf: >>> wlans_ath0="wlan0" >>> ifconfig_wlan0="WPA DHCP" >>> >>> /etc/wpa_supplicant.conf: >>> network={ >>> ssid="home" >>> psk="123" >>> } >>> >>> However, it is not starting to work. >>> >>> I do not have /usr/src/tools/ath so that I can not provide the output. >>> >>> /var/log/messages is spammed with: >>> >>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with >>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>> xx:xx:xx:xx:xx:xx timed out. >>> >>> Any idea what might be wrong or how I could fix this? >>> >>> regards, >>> Kamil >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to >>> "freebsd-wireless-unsubscribe@freebsd.org" > > From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 19:30:04 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 461C9A2B for ; Mon, 11 Feb 2013 19:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2149A924 for ; Mon, 11 Feb 2013 19:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1BJU3qG078195 for ; Mon, 11 Feb 2013 19:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1BJU3Hf078194; Mon, 11 Feb 2013 19:30:03 GMT (envelope-from gnats) Date: Mon, 11 Feb 2013 19:30:03 GMT Message-Id: <201302111930.r1BJU3Hf078194@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Ahmed Charles Subject: Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Ahmed Charles 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: Mon, 11 Feb 2013 19:30:04 -0000 The following reply was made to PR kern/173898; it has been noted by GNATS. From: Ahmed Charles To: bug-followup@FreeBSD.org, xmj@chaot.net Cc: Subject: Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip. Date: Mon, 11 Feb 2013 11:22:05 -0800 Note: There is also a reference to the firmware in sys/conf/files. -- Ahmed Charles From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 19:33:45 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 39A7ABD1 for ; Mon, 11 Feb 2013 19:33:45 +0000 (UTC) (envelope-from k.s.mail@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by mx1.freebsd.org (Postfix) with ESMTP id BE36D960 for ; Mon, 11 Feb 2013 19:33:44 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MXkSn-1USKmG1xVH-00Wn2N for ; Mon, 11 Feb 2013 20:33:43 +0100 Received: (qmail invoked by alias); 11 Feb 2013 19:33:43 -0000 Received: from ip-130-180-70-188.unitymediagroup.de (EHLO mba.local) [130.180.70.188] by mail.gmx.net (mp020) with SMTP; 11 Feb 2013 20:33:43 +0100 X-Authenticated: #32709443 X-Provags-ID: V01U2FsdGVkX18xZ98VoqkxA6SMR4S220Eef90kFvBd94H2jU6sPV 0A1ALrYEpDnF3p Message-ID: <51194795.5070500@gmx.net> Date: Mon, 11 Feb 2013 20:33:41 +0100 From: Kamil Szczesny User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath0: device timeout on 9.1-RELEASE References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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: Mon, 11 Feb 2013 19:33:45 -0000 Still with 9.0-RELEASE: gomorrha% vmstat -i interrupt total rate irq1: atkbd0 6 0 irq16: ath0 ehci0 1367 13 irq23: ehci1 250 2 cpu0:timer 8014 77 irq256: em0 523 5 irq258: ahci0 15444 149 cpu1:timer 2797 27 cpu2:timer 3743 36 cpu3:timer 3053 29 Total 35197 341 Am 11.02.13 19:59, schrieb Adrian Chadd: > Hi, > > Would you please look at the output of vmstat -i, see if the ath0 > device is receiving interrupts? > > Thanks, > > > > Adrian > > > On 10 February 2013 23:30, Kamil Szczesny wrote: >> Hi, >> >> after a downgrade to 9.0-RELEASE the issue remains the same. >> /var/log/messages is spamed by equal authentication timeout entries. >> >> regards, >> Kamil >> >> Am 10.02.13 20:10, schrieb Adrian Chadd: >> >>> Hi, >>> >>> Would you please try 9.0-RELEASE too? >>> >>> >>> >>> Adrian >>> >>> >>> On 10 February 2013 00:38, Kamil Szczesny wrote: >>>> Hello, >>>> >>>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not >>>> existent >>>> on 8.x-RELEASE. >>>> >>>> The issue seems to be the similar to this one: >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>>> >>>> I do have the same NIC. pciconf -lv output is equal: >>>> >>>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>>> rev=0x01 >>>> hdr=0x00 >>>> vendor = 'Atheros Communications Inc.' >>>> device = 'AR5008 Wireless Network Adapter' >>>> class = network >>>> >>>> /etc/rc.conf: >>>> wlans_ath0="wlan0" >>>> ifconfig_wlan0="WPA DHCP" >>>> >>>> /etc/wpa_supplicant.conf: >>>> network={ >>>> ssid="home" >>>> psk="123" >>>> } >>>> >>>> However, it is not starting to work. >>>> >>>> I do not have /usr/src/tools/ath so that I can not provide the output. >>>> >>>> /var/log/messages is spammed with: >>>> >>>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with >>>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>>> xx:xx:xx:xx:xx:xx timed out. >>>> >>>> Any idea what might be wrong or how I could fix this? >>>> >>>> regards, >>>> Kamil >>>> _______________________________________________ >>>> freebsd-wireless@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> To unsubscribe, send any mail to >>>> "freebsd-wireless-unsubscribe@freebsd.org" >> From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 11 19:43:50 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 80522F85 for ; Mon, 11 Feb 2013 19:43:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22a.google.com (we-in-x022a.1e100.net [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 1CCB29E8 for ; Mon, 11 Feb 2013 19:43:49 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id z53so5399707wey.1 for ; Mon, 11 Feb 2013 11:43:49 -0800 (PST) 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; bh=CjjNqddLWIFNyN2hKbxxLRRFrW4wllGDoBWe/07m97Q=; b=yymXrvKSOSaoVS+b5NHVpNtlfJ6WPdrB99IX6lNCfmBTeN1Ywzz4w3Vb0WQ/z/dB6y qX17tua3ZXzdTsh4Rw6WDlwkkf75Z2A4OLQC0p67WS545Bs8rS+fFI2b6zpiwLkTf83J rZI/MEKSSW8P01by/scFAA9o24n6rPklWdJKieAt9f4ZFW79ffwvY9fmE/OSgX8HgfWy PTGsJeb5lR9Wd+rU7oDmGiA7wsJYdsdqtyFDjZ68fox1kANDphVtzTuzClmK+ToUwFIg GJ9SA3sz2J/Siz2W45lviT833Ud4XyLfc9oR+C2j4HmXKfeLxuu5WxJFOM3Y5KRwLmWH ywGg== MIME-Version: 1.0 X-Received: by 10.180.93.234 with SMTP id cx10mr13255033wib.34.1360611829352; Mon, 11 Feb 2013 11:43:49 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Mon, 11 Feb 2013 11:43:49 -0800 (PST) In-Reply-To: <51194795.5070500@gmx.net> References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> Date: Mon, 11 Feb 2013 11:43:49 -0800 X-Google-Sender-Auth: eTmQW74RzF7Gu4E-xxdPzY4Rr4E Message-ID: Subject: Re: ath0: device timeout on 9.1-RELEASE From: Adrian Chadd To: Kamil Szczesny Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 11 Feb 2013 19:43:50 -0000 Ok.. On 11 February 2013 11:33, Kamil Szczesny wrote: > Still with 9.0-RELEASE: > > gomorrha% vmstat -i > interrupt total rate > irq1: atkbd0 6 0 > irq16: ath0 ehci0 1367 13 .. I can't tell here whether there's any interrupts making it to the ath0 device or not. The driver in -HEAD logs the TX and RX interrupt counts in a ath sysctl which I can track. Can you please compile up athstats and recompile your kernel with: ATH_DEBUG AH_DEBUG ATH_DIAGAPI .. as we will need to establish whether you're actually queuing frames to the hardware, whether they're going out, whether the hardware is actually completing them, and whether the interrupt is being generated. Thanks, Adrian > irq23: ehci1 250 2 > cpu0:timer 8014 77 > irq256: em0 523 5 > irq258: ahci0 15444 149 > cpu1:timer 2797 27 > cpu2:timer 3743 36 > cpu3:timer 3053 29 > Total 35197 341 > > > > Am 11.02.13 19:59, schrieb Adrian Chadd: > >> Hi, >> >> Would you please look at the output of vmstat -i, see if the ath0 >> device is receiving interrupts? >> >> Thanks, >> >> >> >> Adrian >> >> >> On 10 February 2013 23:30, Kamil Szczesny wrote: >>> >>> Hi, >>> >>> after a downgrade to 9.0-RELEASE the issue remains the same. >>> /var/log/messages is spamed by equal authentication timeout entries. >>> >>> regards, >>> Kamil >>> >>> Am 10.02.13 20:10, schrieb Adrian Chadd: >>> >>>> Hi, >>>> >>>> Would you please try 9.0-RELEASE too? >>>> >>>> >>>> >>>> Adrian >>>> >>>> >>>> On 10 February 2013 00:38, Kamil Szczesny wrote: >>>>> >>>>> Hello, >>>>> >>>>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not >>>>> existent >>>>> on 8.x-RELEASE. >>>>> >>>>> The issue seems to be the similar to this one: >>>>> >>>>> >>>>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>>>> >>>>> I do have the same NIC. pciconf -lv output is equal: >>>>> >>>>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>>>> rev=0x01 >>>>> hdr=0x00 >>>>> vendor = 'Atheros Communications Inc.' >>>>> device = 'AR5008 Wireless Network Adapter' >>>>> class = network >>>>> >>>>> /etc/rc.conf: >>>>> wlans_ath0="wlan0" >>>>> ifconfig_wlan0="WPA DHCP" >>>>> >>>>> /etc/wpa_supplicant.conf: >>>>> network={ >>>>> ssid="home" >>>>> psk="123" >>>>> } >>>>> >>>>> However, it is not starting to work. >>>>> >>>>> I do not have /usr/src/tools/ath so that I can not provide the output. >>>>> >>>>> /var/log/messages is spammed with: >>>>> >>>>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with >>>>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>>>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>>>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>>>> xx:xx:xx:xx:xx:xx timed out. >>>>> >>>>> Any idea what might be wrong or how I could fix this? >>>>> >>>>> regards, >>>>> Kamil >>>>> _______________________________________________ >>>>> freebsd-wireless@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>> To unsubscribe, send any mail to >>>>> "freebsd-wireless-unsubscribe@freebsd.org" >>> >>> > From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 12 10:57:19 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 BC8A5940 for ; Tue, 12 Feb 2013 10:57:19 +0000 (UTC) (envelope-from VaNs9@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3AC666DF for ; Tue, 12 Feb 2013 10:57:19 +0000 (UTC) Received: from web7f.yandex.ru (web7f.yandex.ru [95.108.130.104]) by forward11.mail.yandex.net (Yandex) with ESMTP id 0CA1CE810AE for ; Tue, 12 Feb 2013 14:57:17 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web7f.yandex.ru (Yandex) with ESMTP id BC951CE0047; Tue, 12 Feb 2013 14:57:17 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1360666637; bh=rayLAAbNFN5zfxBrVzbYjm4R3L5tSSolkNFCX9/0p/k=; h=From:To:Subject:Date; b=Zf+mSrzuB9MRFAbAZwVFxEfyKTgT2GmYpa92skfrbFYwZmXlUffvI7ns4hyrIPw0N 4ysrbLcoUFfgm6sqkVRHT3OfDLuDdMA4iOhCKNIMVU21XFcheaZOAgGkVqzMoOnTMi Nr/isK2DcrktcqrvioAROeo4MpRG1F9mDUEcbp8w= Received: from client.yota.ru (client.yota.ru [178.176.78.186]) by web7f.yandex.ru with HTTP; Tue, 12 Feb 2013 14:57:17 +0400 From: N V Envelope-From: VaNs9@yandex.ru To: "freebsd-wireless@freebsd.org" Subject: D-Link DWA-140 Rev. B3 MIME-Version: 1.0 Message-Id: <180661360666637@web7f.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Tue, 12 Feb 2013 14:57:17 +0400 Content-Transfer-Encoding: 7bit Content-Type: text/plain 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: Tue, 12 Feb 2013 10:57:19 -0000 Hi. I have got D-Link DWA-140 Rev. B3. The problem: it's not even recognised by the system. Diag info: # uname -a FreeBSD sf1.local 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # dmesg ... ugen2.2: at usbus2 ... nothing else in dmesg. # usbconfig -d 2.2 dump_device_desc ugen2.2: <11n Adapter D-Link> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x2001 idProduct = 0x3c15 bcdDevice = 0x0101 iManufacturer = 0x0001 iProduct = 0x0002 <11n Adapter> iSerialNumber = 0x0003 <1.0> bNumConfigurations = 0x0001 I've tried preloading runfw vie loader.conf - no result. I've tried 9.1-RELEASE i386 also - no result. Googling on the internet gave me the idea this device is based on RT2870. Regards, Vans. From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 12 20:37:17 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 DF65EBFE for ; Tue, 12 Feb 2013 20:37:17 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm13.bullet.mail.ird.yahoo.com (nm13.bullet.mail.ird.yahoo.com [77.238.189.66]) by mx1.freebsd.org (Postfix) with SMTP id 39E2EF8D for ; Tue, 12 Feb 2013 20:37:16 +0000 (UTC) Received: from [212.82.105.244] by nm13.bullet.mail.ird.yahoo.com with NNFMP; 12 Feb 2013 20:37:09 -0000 Received: from [217.146.188.79] by tm16.bullet.mail.ird.yahoo.com with NNFMP; 12 Feb 2013 20:37:09 -0000 Received: from [127.0.0.1] by smtp103.mail.ird.yahoo.com with NNFMP; 12 Feb 2013 20:37:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1360701429; bh=WCZi/A6jtiPmMiWvq5IZJblafMW1snEHKEw+mKUjVZc=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Content-Type; b=YUSo3PQImxSP7aKEnaQed4QYbfm5byNVYESQhgx+QU7HjbRhKxaw7cZNpZap0L1whuEprCZoc7ZuWk2LEbg5W6kgkK+5c1RzZoM1N9TCwybtLm6QnXoLUQxwsEAVh9l2VcouS6nwozcd6FXbtwgblXylupYtu4dt7IXEEdM6mjg= X-Yahoo-Newman-Id: 790890.99864.bm@smtp103.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: qkxfUokVM1mQO0Y5qefB3OapFsLuC.wCLOavtICVcHcVvDQ WJOOTmRenPKKUDJjI0QwG2EzA5NaLjiDjk7y2F9ItMeCi4JH9VvoPa41Tz1D EZK9u2hwntJUySR1k28ubc8JSd.e2npyegSpyc14TcMrmcBZE3BVbKMxG0kJ TkjSZ.3v7Bj6dzaBfokBjY7fsk6HbMS51D1EHgQrae7FHJD0O7Hh61qPH3iu nW3z8cXvem9UpPNpR.YvaIO8gRGLmljMxHuwPNYQ31j3fm_7Rf_1Agadx68O wD0wSzRfY0GihjV6xlySbfx2ZcdYned2DnTzOZ1pZvQ2YOBDSdNzMJ.PuYqS PXiyuOKLtQK6l9GRZBNPbvtdsZxX.226TNSQkotC_uKO5HBcYntcvlCF7xHp OeisDSUnP7QSUjV4RxXZuziETJ7s3z5GMMC7wPMA5dKX2GnOwP4byOIiBnRD 2EQ021eDyXFmzNZp16w-- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-la0-f52.google.com (moonlightakkiy@209.85.215.52 with plain) by smtp103.mail.ird.yahoo.com with SMTP; 12 Feb 2013 12:37:09 -0800 PST Received: by mail-la0-f52.google.com with SMTP id fs12so502127lab.11 for ; Tue, 12 Feb 2013 12:37:08 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.130.131 with SMTP id oe3mr9742734lab.1.1360701428401; Tue, 12 Feb 2013 12:37:08 -0800 (PST) Received: by 10.112.1.37 with HTTP; Tue, 12 Feb 2013 12:37:08 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Feb 2013 13:37:08 -0700 Message-ID: Subject: Re: freebsd-wireless Digest, Vol 87, Issue 2 From: PseudoCylon To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Tue, 12 Feb 2013 20:37:17 -0000 > Message: 5 > Date: Tue, 12 Feb 2013 14:57:17 +0400 > From: N V > To: "freebsd-wireless@freebsd.org" > Subject: D-Link DWA-140 Rev. B3 > Message-ID: <180661360666637@web7f.yandex.ru> > Content-Type: text/plain > > Hi. > > I have got D-Link DWA-140 Rev. B3. > The problem: it's not even recognised by the system. > > Diag info: > > # uname -a > FreeBSD sf1.local 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > # dmesg > ... > ugen2.2: at usbus2 > ... > > nothing else in dmesg. > > # usbconfig -d 2.2 dump_device_desc > ugen2.2: <11n Adapter D-Link> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x2001 > idProduct = 0x3c15 That is a RT5372 chipset, and it is currently not supported by any of FreeBSD drivers. AK > bcdDevice = 0x0101 > iManufacturer = 0x0001 > iProduct = 0x0002 <11n Adapter> > iSerialNumber = 0x0003 <1.0> > bNumConfigurations = 0x0001 > > I've tried preloading runfw vie loader.conf - no result. > I've tried 9.1-RELEASE i386 also - no result. > > Googling on the internet gave me the idea this device is based on RT2870. > > Regards, > Vans. > > > ------------------------------ > From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 12 22:45:37 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 48E6AB4C for ; Tue, 12 Feb 2013 22:45:37 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id C916D890 for ; Tue, 12 Feb 2013 22:45:36 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id dr12so480059wgb.23 for ; Tue, 12 Feb 2013 14:45:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4KLT4r3fwz0wO0eiDtl4mC8PS4ppcIPCjGiVtDDqppw=; b=x6VEsUrCw/PlqT4myVwnGcClSJBvXX39zITDF4bY25+sce++Ehhmsr4DwZc6wnxeWB cVSeUykbHO6wDqcnhBht6cc952kpLSfQ3jyiwepbszchoVt3QA/c46mQ1jmPU9reMQvO 1PWq0pnov+qc7wnbMfIopa/+hEXH+amg4bP6A/wMj3sICroGkLuUcdvr3OEkAHKmIM9r prkQjBfn2aUIcIOcDOwG9cmjuC5cj2ZOzLxwdqKsxm8bXW7FesU8ztXRuBSum1C/dE2X 7Yma5OCWckFx4p56jm51kiLsvsooNSA/VjO+/hBtffx4SSWyweG42wUiwK3XGHElsija yv3Q== MIME-Version: 1.0 X-Received: by 10.194.57.206 with SMTP id k14mr34067415wjq.26.1360709130420; Tue, 12 Feb 2013 14:45:30 -0800 (PST) Received: by 10.227.59.19 with HTTP; Tue, 12 Feb 2013 14:45:30 -0800 (PST) Date: Tue, 12 Feb 2013 23:45:30 +0100 Message-ID: Subject: FreeBSD wireless event From: Monthadar Al Jaberi To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Tue, 12 Feb 2013 22:45:37 -0000 Hi, Is there a FreeBSD / BSD conference that all the wireless and network gurus of the BSD world gather? Is there a special event or is it more like adhoc on the different event scattered around? br, -- Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 12 22:53:43 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 564FEDFF for ; Tue, 12 Feb 2013 22:53:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by mx1.freebsd.org (Postfix) with ESMTP id E98D38FB for ; Tue, 12 Feb 2013 22:53:42 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id fg15so486834wgb.13 for ; Tue, 12 Feb 2013 14:53:41 -0800 (PST) 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; bh=bqW2bx8//J2Ebhu8h+JLohLeF3KznMfrVuOuUZSKHL4=; b=MDLlKVrJ7RxnV8uciTkBJsaIjtKKN7njc+I/a6w6wvWO4KI8FkTL+VAjQTDGnNuA/f EdhWcWzlqtNogdNTlhYCzd6WiIEFHGiUwOqH7cLFbXperdHblRVPMaExLYMdeVcNGqgY X0MjL2KevGHRscBWqRnlljRvCVvj3wtqk5yc9JcpJjwcMNyUw7TzIE3VTR2s3OrIKCtE jLBOcDwo9fIpN2fzIjr17MS8SZxuXKMdycPK+xXy0hT4vM0Fr9DVVBGFWdsy6ewP6X5X 7O4Q7VF1VK88RmqPobQy4ZO/4KzbN/xl8AZag/ng7CM2xm114vYNOg5l6er1VA559FGh RUhg== MIME-Version: 1.0 X-Received: by 10.180.84.165 with SMTP id a5mr6343834wiz.6.1360709621809; Tue, 12 Feb 2013 14:53:41 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Tue, 12 Feb 2013 14:53:41 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Feb 2013 14:53:41 -0800 X-Google-Sender-Auth: SRM3ywzbN59wFjHFy0h80JeG6b4 Message-ID: Subject: Re: FreeBSD wireless event From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 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: Tue, 12 Feb 2013 22:53:43 -0000 On 12 February 2013 14:45, Monthadar Al Jaberi wrote: > Hi, > > Is there a FreeBSD / BSD conference that all the wireless and network > gurus of the BSD world gather? Is there a special event or is it more > like adhoc on the different event scattered around? There's no specific event. Try to come to BSDCan this year? Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 13 06:16:23 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 C9EBEBDD; Wed, 13 Feb 2013 06:16:23 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by mx1.freebsd.org (Postfix) with ESMTP id 1AB9BD1E; Wed, 13 Feb 2013 06:16:22 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id 16so683227wgi.27 for ; Tue, 12 Feb 2013 22:16:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=nLAJY/o7QWfAO7j14csWz6qF6rwyq7W6xvl1W+25LfY=; b=gN4lU5DBdFYd3tJqsNw4yvIfxIKU/bqWp2r6hwa+XxmekOOZyZ/fGMPK2/TsHUbHMe QkhpKJwAO9JzNBCgLmh+pGSF5jMW+vfkBpwa4do1KBQouoT9tzLQFIOXTng48mZCExPo zR0ibWwa5DGxKSj0npcRHZ75L/oeWjjFyIGfTDsLqgPUzzTBW0V3/qdm9qPqEz3d5YNs LMe+R/u1e+0EKdvMpqSNltzf4pQRDe6NaPdTOAKrwnk51IK9mQlYZrO3k6fg0iaby+78 nlcCejy68Fj8rBiRw316L21fp0LJuiABDn/3AxR3lZXkff/LUzw/G/8gtxv/tkMu/dyE j5Sg== MIME-Version: 1.0 X-Received: by 10.180.77.9 with SMTP id o9mr7368144wiw.16.1360736182008; Tue, 12 Feb 2013 22:16:22 -0800 (PST) Received: by 10.227.59.19 with HTTP; Tue, 12 Feb 2013 22:16:21 -0800 (PST) In-Reply-To: References: Date: Wed, 13 Feb 2013 07:16:21 +0100 Message-ID: Subject: Re: FreeBSD wireless event From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Wed, 13 Feb 2013 06:16:23 -0000 On Tue, Feb 12, 2013 at 11:53 PM, Adrian Chadd wrote: > On 12 February 2013 14:45, Monthadar Al Jaberi wrote: >> Hi, >> >> Is there a FreeBSD / BSD conference that all the wireless and network >> gurus of the BSD world gather? Is there a special event or is it more >> like adhoc on the different event scattered around? > > There's no specific event. Try to come to BSDCan this year? Ok thnx for info, I will try. Interesting to see what the schedule will look like. br, > > > > Adrian -- Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 13 16:02:08 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.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 A44F1324; Wed, 13 Feb 2013 16:02:08 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC3ACC3; Wed, 13 Feb 2013 16:02:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1DG28sB085840; Wed, 13 Feb 2013 16:02:08 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1DG28du085836; Wed, 13 Feb 2013 16:02:08 GMT (envelope-from linimon) Date: Wed, 13 Feb 2013 16:02:08 GMT Message-Id: <201302131602.r1DG28du085836@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error 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: Wed, 13 Feb 2013 16:02:08 -0000 Old Synopsis: iwn0: iwn_intr: fatal firmware error New Synopsis: [iwn] iwn0: iwn_intr: fatal firmware error Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 13 16:01:42 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176104 From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 14 05:14:56 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 201F4943 for ; Thu, 14 Feb 2013 05:14:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id 9D789678 for ; Thu, 14 Feb 2013 05:14:55 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id l13so6820708wie.4 for ; Wed, 13 Feb 2013 21:14:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=4FIN8GDd6d1Qid4b6DdrHN/e/qLFFOzK9eA05Y3nvRo=; b=maYO7rVAHwzdMn1Lt5UWwdXRNNh/5w/wqfRtOCMvL/5ntnnOtN5+RjXaIM7uM8OsKh fWR6Kd78ya8+awU3Hr+FbQnSHZvnspPplWWnQTPn4XnHvRtD3NxsMFHEnOtWMrd5laTt PmSowPZxr5QJhLssN/2BaQsra3YOltW4bbz21TOYKL4mNGU1Ikuxvi5+JjB1hp/CyrTP sBdvnz+ZthBp2EbnUw+tQFfEtxFXYZQwM589pWVp4LLU9qovPQi4xfenqLo8i3tHZjzZ 1uat8sXVqYGDA1u3LkSniU0mumTCiMUf9uX/15eSSHEa3nimCQ1qMJrAlMdjrW42Xgcw nQ9Q== MIME-Version: 1.0 X-Received: by 10.181.12.103 with SMTP id ep7mr14327990wid.12.1360818893560; Wed, 13 Feb 2013 21:14:53 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Wed, 13 Feb 2013 21:14:53 -0800 (PST) Date: Wed, 13 Feb 2013 21:14:53 -0800 X-Google-Sender-Auth: Vjbsh_ndMO0sIOtMsENYpSYHU4w Message-ID: Subject: [RFC] serialising net80211 TX From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 14 Feb 2013 05:14:56 -0000 Hi, I'd like to work on the net80211 TX serialisation now. I'll worry about driver serialisation and if_transmit methods later. The 30 second version - it happens in parallel, which means preemption and multi-core devices can and will hit lots of subtle and hard-to-debug races in the TX path. We actually need an end-to-end serialisation method - not only for the 802.11 state (sequence number, correct aggregation handling, etc) but to line up 802.11 sequence number allocation with the encryption IV/PN values. Otherwise you end up with lots of crazy subtle out of order packets occuring. The other is the seqno/CCMP IV race between the raw transmit path and the normal transmit path. There are other nagging issues that I'm trying to resolve - but, one thing at a time. So there are three current contenders: * wrap everything in net80211 TX in a per-vap TX lock; grab it at the beginning of ieee80211_output() and ieee80211_start(), and don't release it until the frame is queued to something (a power save queue, an age queue, the driver.) That guarantees that the driver is called in lock-step with each frame being processed. * do deferred transmit- ie, the net80211 entry points simply queue mbufs to a queue, and a taskqueue runs over the ifnet queue and runs those frames in-order. There's no need for a lock here as there's only one sending context (either per-VAP or per-IC). * A hybrid setup - use a per-vap TX lock; do a try-acquire on it and direct dispatch from the queue head if we have it; otherwise defer frames into a queue and have a taskqueue handle those. 1) is what drivers like iwn(4) do internally. 2) is what I've tinkered with - but we become a slave to the scheduler. Task switching is expensive and unpredictable; doubly so for a non-preemption kernel. We'd have to run the TX taskqueue at some very high priority to get something resembling direct-dispatch behaviour. 3) is what the gige/10ge drivers do. They hold a big TX lock for each TX (from xxx_transmit() to hardware dispatch) and if they can't acquire the TX lock, they defer it to a drbd lockless ring buffer and service that via a taskqueue. I can implement any of the above. architecturally I'd prefer 2) - it massively simplifies and streamlines things, but the scheduling latency is just plain stab-worthy.I'm tempted to just do 1) for now and turn it into 3) if we need to. The main reason against doing 1) (and why 2) is nicer) is recursion - if the TX path wants to call the net80211 TX code for some odd reason, we'll hit lock recursion. I'd rather have the system crash at this point (and then fix the misbehaving driver) but that's just me. So - what do people think? Once this is done I'd like to make sure that the wifi chipset drivers do the same - ie, ensure that the frame order is preserved both between the normal and the raw xmit paths. That should fix all of the odd CCMP out of order crap that I see under heavy, heavy test conditions. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 14 19:50:25 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 850C7560; Thu, 14 Feb 2013 19:50:25 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-we0-x233.google.com (we-in-x0233.1e100.net [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id D5DFB9C5; Thu, 14 Feb 2013 19:50:24 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id p43so491605wea.38 for ; Thu, 14 Feb 2013 11:50:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=iKoeADO4k0xj3LUTaS4l48I1cyr512Jgl2AiUuDN9ew=; b=fkjyhziu6dnoytUG0XjkdeMoA39yCSz6QAbvYPJaD82MALNg/5tAoFj/F8vulHEQob vNKhUSYNsUwiSHiLjVIXm5NyX9jcDoQpsJU3i87LWgwtoFUli9yj9bWZ7dUiAPMmpo/E pZlpY2mQx6061WnwYbfb2Yq0Lx7doYSKdZs8fY51zOgTKhb0DVgDZD/gvq3/R5hVvJ5s 1qe7bQ4ubmK3NoZnGzwSBGTFvqFafGpkdKdIV0RBwmtb1OJ0n28kpPPdicdmt7N5RL2z CqeV/BoL1LXlY2yUoRp6cVI8OMeudU30A2rxRvr0TQ2hIOgLy2Oj/W62ZTMfBPXdv4i8 NJLQ== MIME-Version: 1.0 X-Received: by 10.194.57.206 with SMTP id k14mr48091742wjq.26.1360871423802; Thu, 14 Feb 2013 11:50:23 -0800 (PST) Received: by 10.227.59.19 with HTTP; Thu, 14 Feb 2013 11:50:23 -0800 (PST) In-Reply-To: References: Date: Thu, 14 Feb 2013 20:50:23 +0100 Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 14 Feb 2013 19:50:25 -0000 On Thu, Feb 14, 2013 at 6:14 AM, Adrian Chadd wrote: > Hi, > > I'd like to work on the net80211 TX serialisation now. I'll worry > about driver serialisation and if_transmit methods later. > > The 30 second version - it happens in parallel, which means preemption > and multi-core devices can and will hit lots of subtle and > hard-to-debug races in the TX path. > > We actually need an end-to-end serialisation method - not only for the > 802.11 state (sequence number, correct aggregation handling, etc) but > to line up 802.11 sequence number allocation with the encryption IV/PN > values. Otherwise you end up with lots of crazy subtle out of order > packets occuring. The other is the seqno/CCMP IV race between the raw > transmit path and the normal transmit path. There are other nagging > issues that I'm trying to resolve - but, one thing at a time. > > So there are three current contenders: > > * wrap everything in net80211 TX in a per-vap TX lock; grab it at the > beginning of ieee80211_output() and ieee80211_start(), and don't > release it until the frame is queued to something (a power save queue, > an age queue, the driver.) That guarantees that the driver is called > in lock-step with each frame being processed. > * do deferred transmit- ie, the net80211 entry points simply queue > mbufs to a queue, and a taskqueue runs over the ifnet queue and runs > those frames in-order. There's no need for a lock here as there's only > one sending context (either per-VAP or per-IC). Seems like the best architectural wise, first-in first out. I am just thinking of one can extend this too have like more than one queue, more like the QoS concept, and each packet have a time-stamp assigned to it.Would that help? What I am thinking is more of an optimization maybe. the Wifi can run in different modes BSS (AP/STA), IBSS and MBSS. And for the MBSS mode there is not just data comming from up the stack, or sending beacons. The MBSS also needs to handle data forwarding and management frame propagation. Would it help to have different queues? A mesh path discovery would be delayed too much if the complete system is highly active? Should the path request frames have higher priority to lets say data frames? Would that help for when sending beacons from the stack too. Maybe I am way off :) > * A hybrid setup - use a per-vap TX lock; do a try-acquire on it and > direct dispatch from the queue head if we have it; otherwise defer > frames into a queue and have a taskqueue handle those. That maybe gives the most speed up? > > 1) is what drivers like iwn(4) do internally. > 2) is what I've tinkered with - but we become a slave to the > scheduler. Task switching is expensive and unpredictable; doubly so > for a non-preemption kernel. We'd have to run the TX taskqueue at some > very high priority to get something resembling direct-dispatch > behaviour. > 3) is what the gige/10ge drivers do. They hold a big TX lock for each > TX (from xxx_transmit() to hardware dispatch) and if they can't > acquire the TX lock, they defer it to a drbd lockless ring buffer and > service that via a taskqueue. > > I can implement any of the above. architecturally I'd prefer 2) - it > massively simplifies and streamlines things, but the scheduling > latency is just plain stab-worthy.I'm tempted to just do 1) for now > and turn it into 3) if we need to. > > The main reason against doing 1) (and why 2) is nicer) is recursion - > if the TX path wants to call the net80211 TX code for some odd reason, > we'll hit lock recursion. I'd rather have the system crash at this > point (and then fix the misbehaving driver) but that's just me. > > So - what do people think? > > Once this is done I'd like to make sure that the wifi chipset drivers > do the same - ie, ensure that the frame order is preserved both > between the normal and the raw xmit paths. > That should fix all of the odd CCMP out of order crap that I see under > heavy, heavy test conditions. > > Thanks, > > > Adrian > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" -- Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 01:49:19 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 019D57D1 for ; Fri, 15 Feb 2013 01:49:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22b.google.com (we-in-x022b.1e100.net [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 859ABA27 for ; Fri, 15 Feb 2013 01:49:18 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so2545532wey.16 for ; Thu, 14 Feb 2013 17:49:17 -0800 (PST) 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; bh=CgMwkRXvsL1cYIjCH6AWkVHpSrbPMP5//9PPQp2SusQ=; b=0V7OzJ02ap75NkOVY2cFcytKHinG3kEK1KaQmYHtQNTFvBuXTaaCV4ATFFPMlO92Sh OeqfNcENHJlEGrOCtW1+xsUyp56rOjZYZWlKyuxcBDdbyYPnuVaziqagiW/cqO8y19tj oaMcYy1o9HpVUKcAhUezbVe2cjubTWzKnJIYbNOeji0fhEkMtyk/5B8q9Aqw1sSUteVQ /J0lJH3h+94wYlqk/e38YUcxtF37Qik/BLMboSNVBN7NpsSrxTEn1ZsDJv8zPTIIsP8g P9RnVdD7cRXRkufomxZWMOdR/JvD2PlZ3tSVYVNXawyAzt8g0v5g0DjAxkCl6Rtm9AHR vo+w== MIME-Version: 1.0 X-Received: by 10.180.81.164 with SMTP id b4mr1129081wiy.34.1360892957531; Thu, 14 Feb 2013 17:49:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Thu, 14 Feb 2013 17:49:17 -0800 (PST) In-Reply-To: References: Date: Thu, 14 Feb 2013 17:49:17 -0800 X-Google-Sender-Auth: hWR2SvwkI3YqNWr2Xr5bYe90nqQ Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 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, 15 Feb 2013 01:49:19 -0000 On 14 February 2013 11:50, Monthadar Al Jaberi wrote: > Seems like the best architectural wise, first-in first out. I am just > thinking of one can extend this too have like more than one queue, > more like the QoS concept, and each packet have a time-stamp assigned > to it.Would that help? Well, the queue thing is a bit orthogonal. Yes, we could run multiple queues and multiple kernel threads. But what would multiple kernel threads get us? Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 07:49:48 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 E1AE31C7; Fri, 15 Feb 2013 07:49:48 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wi0-x229.google.com (wi-in-x0229.1e100.net [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id 4C9A1910; Fri, 15 Feb 2013 07:49:48 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id l13so969699wie.2 for ; Thu, 14 Feb 2013 23:49:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qmPCTf9Wxe9PZ3SRCUhQTzW94pgpcn8itSw9neRY9po=; b=A9qi4OI8zrqE+cTYoVGUzX2ngNLfbvjYgQbRo/2kvLhceBnIwB461iZRMEU3lcUBHS y0LJT6uXl7uqWyKQH5zyPPllm8iF0cqq/7FeQ29HLoDLefXw01OXU20d29ymPPoa6uhD amuZpEDkUuCu8kB3qfwRAa8qYElusc1aNGKqFUFr1o6VburBu7YkFKPmaq2TCgR7s118 Gc/B9VU9ouhXZd1HnBf7naDRO3jqOm8zRFRWIJz/dPpBXAIVyALm+GOdMg6z0UCfga6L 8K1KytIjBczRpAVnRmCBtkTmToSIbxwqOyxsaWM0T8VhzjHcYE8Oj9Wf+oDFU3e78XTl xcBw== MIME-Version: 1.0 X-Received: by 10.180.97.166 with SMTP id eb6mr4054848wib.20.1360914586609; Thu, 14 Feb 2013 23:49:46 -0800 (PST) Received: by 10.227.59.19 with HTTP; Thu, 14 Feb 2013 23:49:46 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 08:49:46 +0100 Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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, 15 Feb 2013 07:49:48 -0000 On Fri, Feb 15, 2013 at 2:49 AM, Adrian Chadd wrote: > On 14 February 2013 11:50, Monthadar Al Jaberi wrote: > >> Seems like the best architectural wise, first-in first out. I am just >> thinking of one can extend this too have like more than one queue, >> more like the QoS concept, and each packet have a time-stamp assigned >> to it.Would that help? > > Well, the queue thing is a bit orthogonal. Yes, we could run multiple > queues and multiple kernel threads. But what would multiple kernel > threads get us? I was thinking one kernel thread. This thread have some headroom to take from the higher priority queue if the frame on the other queue is not old "enough". > > > > Adrian -- Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 12:58:42 2013 Return-Path: Delivered-To: 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 6549EA03 for ; Fri, 15 Feb 2013 12:58:42 +0000 (UTC) (envelope-from peter@pean.org) Received: from velox.its.uu.se (velox.its.uu.se [130.238.7.74]) by mx1.freebsd.org (Postfix) with ESMTP id 2AF14A3C for ; Fri, 15 Feb 2013 12:58:41 +0000 (UTC) X-Virus-Scanned: amavisd-new at uu.se Received: from nyx.uppmax.uu.se (nyx.uppmax.uu.se [130.238.137.40]) by velox.its.uu.se (Postfix) with ESMTP id BB65A37A93 for ; Fri, 15 Feb 2013 13:58:39 +0100 (CET) Message-ID: <511E30FF.4050404@pean.org> Date: Fri, 15 Feb 2013 13:58:39 +0100 From: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: wireless@freebsd.org Subject: Support for Mini PCie card WLE300NX( (AR9380) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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, 15 Feb 2013 12:58:42 -0000 Hi! What is the current status for this card in -HEAD? Would it be usable in the near future? FreeBSD gw 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Thu Feb 7 11:31:17 CET 2013 root@gw:/usr/obj/usr/src/sys/SOEKRIS i386 none12@pci0:7:0:0: class=0x028000 card=0x3114168c chip=0x0030168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9300 Wireless LAN adaptor' class = network From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 19:48:34 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 CF6FF902 for ; Fri, 15 Feb 2013 19:48:34 +0000 (UTC) (envelope-from k.s.mail@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id 66CCB124 for ; Fri, 15 Feb 2013 19:48:34 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.4]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M5Jbd-1UpBpW1F2l-00zWU2 for ; Fri, 15 Feb 2013 20:48:33 +0100 Received: (qmail invoked by alias); 15 Feb 2013 19:48:33 -0000 Received: from ip-130-180-70-188.unitymediagroup.de (EHLO [192.168.0.103]) [130.180.70.188] by mail.gmx.net (mp004) with SMTP; 15 Feb 2013 20:48:33 +0100 X-Authenticated: #32709443 X-Provags-ID: V01U2FsdGVkX192rd1l5DR2yc8yHtXleYFe+67A28H8itgeXZXGVw +ex1tvQ8fnilxj Message-ID: <511E910D.1080901@gmx.net> Date: Fri, 15 Feb 2013 20:48:29 +0100 From: Kamil Szczesny User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath0: device timeout on 9.1-RELEASE References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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, 15 Feb 2013 19:48:34 -0000 Adrian, Finally, I managed to get again a 9.1-RELEASE running with a recompiled kernel. gomorrha% uname -v FreeBSD 9.1-RELEASE #0 r246834: Fri Feb 15 18:57:51 CET 2013 root@gomorrha.local:/usr/obj/usr/src/sys/WIFIDEBUG This is the result of athstats: gomorrha% /usr/local/bin/athstats -i ath0 32484 data frames received 5130 data frames transmit 3273 mib overflow interrupts 1M current transmit rate 190 watchdog timeouts 2040 rx failed 'cuz of bad CRC 7 rx failed 'cuz of PHY err 7 CCK restart -0/+0 TDMA slot adjust (usecs, smoothed) 86 avg recv rssi -96 rx noise floor 5130 tx frames through raw api 1 first step level 1 OFDM weak signal detect 12 ANI increased spur immunity 10 ANI decrease spur immunity 990 ANI enabled OFDM weak signal detect 2061 ANI disabled OFDM weak signal detect 3041 ANI disabled CCK weak signal threshold 4 ANI increased first step level 2940667 cumulative OFDM phy error count 5258173 cumulative CCK phy error count 74 bad FCS 105 average rssi (beacons only) 84 average rssi (all rx'd frames) Antenna profile: [1] tx 0 rx 32484 Is it somewhat helpful? regards, Kamil Am 11.02.2013 20:43, schrieb Adrian Chadd: > Ok.. > > On 11 February 2013 11:33, Kamil Szczesny wrote: >> Still with 9.0-RELEASE: >> >> gomorrha% vmstat -i >> interrupt total rate >> irq1: atkbd0 6 0 >> irq16: ath0 ehci0 1367 13 > > .. I can't tell here whether there's any interrupts making it to the > ath0 device or not. > > The driver in -HEAD logs the TX and RX interrupt counts in a ath > sysctl which I can track. > > Can you please compile up athstats and recompile your kernel with: > > ATH_DEBUG > AH_DEBUG > ATH_DIAGAPI > > .. as we will need to establish whether you're actually queuing frames > to the hardware, whether they're going out, whether the hardware is > actually completing them, and whether the interrupt is being > generated. > > Thanks, > > > > Adrian > >> irq23: ehci1 250 2 >> cpu0:timer 8014 77 >> irq256: em0 523 5 >> irq258: ahci0 15444 149 >> cpu1:timer 2797 27 >> cpu2:timer 3743 36 >> cpu3:timer 3053 29 >> Total 35197 341 >> >> >> >> Am 11.02.13 19:59, schrieb Adrian Chadd: >> >>> Hi, >>> >>> Would you please look at the output of vmstat -i, see if the ath0 >>> device is receiving interrupts? >>> >>> Thanks, >>> >>> >>> >>> Adrian >>> >>> >>> On 10 February 2013 23:30, Kamil Szczesny wrote: >>>> >>>> Hi, >>>> >>>> after a downgrade to 9.0-RELEASE the issue remains the same. >>>> /var/log/messages is spamed by equal authentication timeout entries. >>>> >>>> regards, >>>> Kamil >>>> >>>> Am 10.02.13 20:10, schrieb Adrian Chadd: >>>> >>>>> Hi, >>>>> >>>>> Would you please try 9.0-RELEASE too? >>>>> >>>>> >>>>> >>>>> Adrian >>>>> >>>>> >>>>> On 10 February 2013 00:38, Kamil Szczesny wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not >>>>>> existent >>>>>> on 8.x-RELEASE. >>>>>> >>>>>> The issue seems to be the similar to this one: >>>>>> >>>>>> >>>>>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>>>>> >>>>>> I do have the same NIC. pciconf -lv output is equal: >>>>>> >>>>>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>>>>> rev=0x01 >>>>>> hdr=0x00 >>>>>> vendor = 'Atheros Communications Inc.' >>>>>> device = 'AR5008 Wireless Network Adapter' >>>>>> class = network >>>>>> >>>>>> /etc/rc.conf: >>>>>> wlans_ath0="wlan0" >>>>>> ifconfig_wlan0="WPA DHCP" >>>>>> >>>>>> /etc/wpa_supplicant.conf: >>>>>> network={ >>>>>> ssid="home" >>>>>> psk="123" >>>>>> } >>>>>> >>>>>> However, it is not starting to work. >>>>>> >>>>>> I do not have /usr/src/tools/ath so that I can not provide the output. >>>>>> >>>>>> /var/log/messages is spammed with: >>>>>> >>>>>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate with >>>>>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>>>>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>>>>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>>>>> xx:xx:xx:xx:xx:xx timed out. >>>>>> >>>>>> Any idea what might be wrong or how I could fix this? >>>>>> >>>>>> regards, >>>>>> Kamil >>>>>> _______________________________________________ >>>>>> freebsd-wireless@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>> To unsubscribe, send any mail to >>>>>> "freebsd-wireless-unsubscribe@freebsd.org" >>>> >>>> >> > From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 19:55:48 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 A44C4A60 for ; Fri, 15 Feb 2013 19:55:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by mx1.freebsd.org (Postfix) with ESMTP id 41F3C15C for ; Fri, 15 Feb 2013 19:55:47 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id hq4so1601816wib.0 for ; Fri, 15 Feb 2013 11:55:41 -0800 (PST) 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; bh=QbYAjpXY5SZm/3Q7ioVB36Lvlpjsdpt03p+KNqim8V0=; b=p9oCMLM/GrSQhXOMz3eHAuuXCXf3Pqq52BFKnOJkkvV2cLLA4mn5KP+2xkj83IdeIo vCGwPtGHgRsOAsjQlWp+ST1rFOIcZPlddJGGStkvoo8i5GfvbrA371O9b79u+kOaJWoI 1DNJEomzej0CK/mgCs4BYiSq0LhsdAiEc2Bg25sykJKuszB+gF/1m5zWpFfBRx+mK2kD nrgYgJ96BVKmmb/YEIw4sxOERsdt3HflOz20Uf2N7H7DEi7WA3b5yJBwU6x8uoGG0PmF uO5fb7gVdeVCAoXz9eQuN+1GBXBwUXgXcT2b0S2sa0WwZvRgRJB5SPGlbGFV91hCrzg/ A/rA== MIME-Version: 1.0 X-Received: by 10.180.84.165 with SMTP id a5mr8349302wiz.6.1360958141061; Fri, 15 Feb 2013 11:55:41 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 11:55:40 -0800 (PST) In-Reply-To: <511E910D.1080901@gmx.net> References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> <511E910D.1080901@gmx.net> Date: Fri, 15 Feb 2013 11:55:40 -0800 X-Google-Sender-Auth: fTYffMu-f4uVNP0azBT1loRvmys Message-ID: Subject: Re: ath0: device timeout on 9.1-RELEASE From: Adrian Chadd To: Kamil Szczesny Content-Type: text/plain; charset=ISO-8859-1 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, 15 Feb 2013 19:55:48 -0000 Sure, that shows that your environment is quite noisy. :-) But is transmission just plain not happening? Is it just never associating? Or is it sometimes associating and sometimes not? Adrian On 15 February 2013 11:48, Kamil Szczesny wrote: > Adrian, > > Finally, I managed to get again a 9.1-RELEASE running with a recompiled > kernel. > > gomorrha% uname -v > FreeBSD 9.1-RELEASE #0 r246834: Fri Feb 15 18:57:51 CET 2013 > root@gomorrha.local:/usr/obj/usr/src/sys/WIFIDEBUG > > This is the result of athstats: > > gomorrha% /usr/local/bin/athstats -i ath0 > 32484 data frames received > 5130 data frames transmit > 3273 mib overflow interrupts > 1M current transmit rate > 190 watchdog timeouts > 2040 rx failed 'cuz of bad CRC > 7 rx failed 'cuz of PHY err > 7 CCK restart > -0/+0 TDMA slot adjust (usecs, smoothed) > 86 avg recv rssi > -96 rx noise floor > 5130 tx frames through raw api > 1 first step level > 1 OFDM weak signal detect > 12 ANI increased spur immunity > 10 ANI decrease spur immunity > 990 ANI enabled OFDM weak signal detect > 2061 ANI disabled OFDM weak signal detect > 3041 ANI disabled CCK weak signal threshold > 4 ANI increased first step level > 2940667 cumulative OFDM phy error count > 5258173 cumulative CCK phy error count > 74 bad FCS > 105 average rssi (beacons only) > 84 average rssi (all rx'd frames) > Antenna profile: > [1] tx 0 rx 32484 > > Is it somewhat helpful? > > regards, > Kamil > > Am 11.02.2013 20:43, schrieb Adrian Chadd: > >> Ok.. >> >> On 11 February 2013 11:33, Kamil Szczesny wrote: >>> >>> Still with 9.0-RELEASE: >>> >>> gomorrha% vmstat -i >>> interrupt total rate >>> irq1: atkbd0 6 0 >>> irq16: ath0 ehci0 1367 13 >> >> >> .. I can't tell here whether there's any interrupts making it to the >> ath0 device or not. >> >> The driver in -HEAD logs the TX and RX interrupt counts in a ath >> sysctl which I can track. >> >> Can you please compile up athstats and recompile your kernel with: >> >> ATH_DEBUG >> AH_DEBUG >> ATH_DIAGAPI >> >> .. as we will need to establish whether you're actually queuing frames >> to the hardware, whether they're going out, whether the hardware is >> actually completing them, and whether the interrupt is being >> generated. >> >> Thanks, >> >> >> >> Adrian >> >>> irq23: ehci1 250 2 >>> cpu0:timer 8014 77 >>> irq256: em0 523 5 >>> irq258: ahci0 15444 149 >>> cpu1:timer 2797 27 >>> cpu2:timer 3743 36 >>> cpu3:timer 3053 29 >>> Total 35197 341 >>> >>> >>> >>> Am 11.02.13 19:59, schrieb Adrian Chadd: >>> >>>> Hi, >>>> >>>> Would you please look at the output of vmstat -i, see if the ath0 >>>> device is receiving interrupts? >>>> >>>> Thanks, >>>> >>>> >>>> >>>> Adrian >>>> >>>> >>>> On 10 February 2013 23:30, Kamil Szczesny wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> after a downgrade to 9.0-RELEASE the issue remains the same. >>>>> /var/log/messages is spamed by equal authentication timeout entries. >>>>> >>>>> regards, >>>>> Kamil >>>>> >>>>> Am 10.02.13 20:10, schrieb Adrian Chadd: >>>>> >>>>>> Hi, >>>>>> >>>>>> Would you please try 9.0-RELEASE too? >>>>>> >>>>>> >>>>>> >>>>>> Adrian >>>>>> >>>>>> >>>>>> On 10 February 2013 00:38, Kamil Szczesny wrote: >>>>>>> >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not >>>>>>> existent >>>>>>> on 8.x-RELEASE. >>>>>>> >>>>>>> The issue seems to be the similar to this one: >>>>>>> >>>>>>> >>>>>>> >>>>>>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>>>>>> >>>>>>> I do have the same NIC. pciconf -lv output is equal: >>>>>>> >>>>>>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>>>>>> rev=0x01 >>>>>>> hdr=0x00 >>>>>>> vendor = 'Atheros Communications Inc.' >>>>>>> device = 'AR5008 Wireless Network Adapter' >>>>>>> class = network >>>>>>> >>>>>>> /etc/rc.conf: >>>>>>> wlans_ath0="wlan0" >>>>>>> ifconfig_wlan0="WPA DHCP" >>>>>>> >>>>>>> /etc/wpa_supplicant.conf: >>>>>>> network={ >>>>>>> ssid="home" >>>>>>> psk="123" >>>>>>> } >>>>>>> >>>>>>> However, it is not starting to work. >>>>>>> >>>>>>> I do not have /usr/src/tools/ath so that I can not provide the >>>>>>> output. >>>>>>> >>>>>>> /var/log/messages is spammed with: >>>>>>> >>>>>>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate >>>>>>> with >>>>>>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>>>>>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>>>>>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>>>>>> xx:xx:xx:xx:xx:xx timed out. >>>>>>> >>>>>>> Any idea what might be wrong or how I could fix this? >>>>>>> >>>>>>> regards, >>>>>>> Kamil >>>>>>> _______________________________________________ >>>>>>> freebsd-wireless@freebsd.org mailing list >>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>>> To unsubscribe, send any mail to >>>>>>> "freebsd-wireless-unsubscribe@freebsd.org" >>>>> >>>>> >>>>> >>> >> > From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 20:02:20 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 9857EC35 for ; Fri, 15 Feb 2013 20:02:20 +0000 (UTC) (envelope-from k.s.mail@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by mx1.freebsd.org (Postfix) with ESMTP id A69A419B for ; Fri, 15 Feb 2013 20:02:19 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.24]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MY1FO-1USWin3hOC-00UqC1 for ; Fri, 15 Feb 2013 21:02:17 +0100 Received: (qmail invoked by alias); 15 Feb 2013 20:02:17 -0000 Received: from ip-130-180-70-188.unitymediagroup.de (EHLO [192.168.0.103]) [130.180.70.188] by mail.gmx.net (mp024) with SMTP; 15 Feb 2013 21:02:17 +0100 X-Authenticated: #32709443 X-Provags-ID: V01U2FsdGVkX18tMptKfJstXnVjgH5IoJ8NaR7fvG411ZdQ5xNtrT GKEs8DvBUlhlRp Message-ID: <511E9446.4070708@gmx.net> Date: Fri, 15 Feb 2013 21:02:14 +0100 From: Kamil Szczesny User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath0: device timeout on 9.1-RELEASE References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> <511E910D.1080901@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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, 15 Feb 2013 20:02:20 -0000 Am 15.02.2013 20:55, schrieb Adrian Chadd: > Sure, that shows that your environment is quite noisy. :-) > > But is transmission just plain not happening? Is it just never > associating? Or is it sometimes associating and sometimes not? > It's a bit crowded here ; ) Well as far as I have observed, it never associated. regards, Kamil > > > Adrian > > > On 15 February 2013 11:48, Kamil Szczesny wrote: >> Adrian, >> >> Finally, I managed to get again a 9.1-RELEASE running with a recompiled >> kernel. >> >> gomorrha% uname -v >> FreeBSD 9.1-RELEASE #0 r246834: Fri Feb 15 18:57:51 CET 2013 >> root@gomorrha.local:/usr/obj/usr/src/sys/WIFIDEBUG >> >> This is the result of athstats: >> >> gomorrha% /usr/local/bin/athstats -i ath0 >> 32484 data frames received >> 5130 data frames transmit >> 3273 mib overflow interrupts >> 1M current transmit rate >> 190 watchdog timeouts >> 2040 rx failed 'cuz of bad CRC >> 7 rx failed 'cuz of PHY err >> 7 CCK restart >> -0/+0 TDMA slot adjust (usecs, smoothed) >> 86 avg recv rssi >> -96 rx noise floor >> 5130 tx frames through raw api >> 1 first step level >> 1 OFDM weak signal detect >> 12 ANI increased spur immunity >> 10 ANI decrease spur immunity >> 990 ANI enabled OFDM weak signal detect >> 2061 ANI disabled OFDM weak signal detect >> 3041 ANI disabled CCK weak signal threshold >> 4 ANI increased first step level >> 2940667 cumulative OFDM phy error count >> 5258173 cumulative CCK phy error count >> 74 bad FCS >> 105 average rssi (beacons only) >> 84 average rssi (all rx'd frames) >> Antenna profile: >> [1] tx 0 rx 32484 >> >> Is it somewhat helpful? >> >> regards, >> Kamil >> >> Am 11.02.2013 20:43, schrieb Adrian Chadd: >> >>> Ok.. >>> >>> On 11 February 2013 11:33, Kamil Szczesny wrote: >>>> >>>> Still with 9.0-RELEASE: >>>> >>>> gomorrha% vmstat -i >>>> interrupt total rate >>>> irq1: atkbd0 6 0 >>>> irq16: ath0 ehci0 1367 13 >>> >>> >>> .. I can't tell here whether there's any interrupts making it to the >>> ath0 device or not. >>> >>> The driver in -HEAD logs the TX and RX interrupt counts in a ath >>> sysctl which I can track. >>> >>> Can you please compile up athstats and recompile your kernel with: >>> >>> ATH_DEBUG >>> AH_DEBUG >>> ATH_DIAGAPI >>> >>> .. as we will need to establish whether you're actually queuing frames >>> to the hardware, whether they're going out, whether the hardware is >>> actually completing them, and whether the interrupt is being >>> generated. >>> >>> Thanks, >>> >>> >>> >>> Adrian >>> >>>> irq23: ehci1 250 2 >>>> cpu0:timer 8014 77 >>>> irq256: em0 523 5 >>>> irq258: ahci0 15444 149 >>>> cpu1:timer 2797 27 >>>> cpu2:timer 3743 36 >>>> cpu3:timer 3053 29 >>>> Total 35197 341 >>>> >>>> >>>> >>>> Am 11.02.13 19:59, schrieb Adrian Chadd: >>>> >>>>> Hi, >>>>> >>>>> Would you please look at the output of vmstat -i, see if the ath0 >>>>> device is receiving interrupts? >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> >>>>> Adrian >>>>> >>>>> >>>>> On 10 February 2013 23:30, Kamil Szczesny wrote: >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> after a downgrade to 9.0-RELEASE the issue remains the same. >>>>>> /var/log/messages is spamed by equal authentication timeout entries. >>>>>> >>>>>> regards, >>>>>> Kamil >>>>>> >>>>>> Am 10.02.13 20:10, schrieb Adrian Chadd: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Would you please try 9.0-RELEASE too? >>>>>>> >>>>>>> >>>>>>> >>>>>>> Adrian >>>>>>> >>>>>>> >>>>>>> On 10 February 2013 00:38, Kamil Szczesny wrote: >>>>>>>> >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was not >>>>>>>> existent >>>>>>>> on 8.x-RELEASE. >>>>>>>> >>>>>>>> The issue seems to be the similar to this one: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>>>>>>> >>>>>>>> I do have the same NIC. pciconf -lv output is equal: >>>>>>>> >>>>>>>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>>>>>>> rev=0x01 >>>>>>>> hdr=0x00 >>>>>>>> vendor = 'Atheros Communications Inc.' >>>>>>>> device = 'AR5008 Wireless Network Adapter' >>>>>>>> class = network >>>>>>>> >>>>>>>> /etc/rc.conf: >>>>>>>> wlans_ath0="wlan0" >>>>>>>> ifconfig_wlan0="WPA DHCP" >>>>>>>> >>>>>>>> /etc/wpa_supplicant.conf: >>>>>>>> network={ >>>>>>>> ssid="home" >>>>>>>> psk="123" >>>>>>>> } >>>>>>>> >>>>>>>> However, it is not starting to work. >>>>>>>> >>>>>>>> I do not have /usr/src/tools/ath so that I can not provide the >>>>>>>> output. >>>>>>>> >>>>>>>> /var/log/messages is spammed with: >>>>>>>> >>>>>>>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate >>>>>>>> with >>>>>>>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>>>>>>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>>>>>>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>>>>>>> xx:xx:xx:xx:xx:xx timed out. >>>>>>>> >>>>>>>> Any idea what might be wrong or how I could fix this? >>>>>>>> >>>>>>>> regards, >>>>>>>> Kamil >>>>>>>> _______________________________________________ >>>>>>>> freebsd-wireless@freebsd.org mailing list >>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>>>> To unsubscribe, send any mail to >>>>>>>> "freebsd-wireless-unsubscribe@freebsd.org" >>>>>> >>>>>> >>>>>> >>>> >>> >> > From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 20:10:02 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 21C85FCE for ; Fri, 15 Feb 2013 20:10:02 +0000 (UTC) (envelope-from k.s.mail@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id C45B0204 for ; Fri, 15 Feb 2013 20:10:01 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.35]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MCNfL-1UFYQT2GC9-009CcL for ; Fri, 15 Feb 2013 21:10:00 +0100 Received: (qmail invoked by alias); 15 Feb 2013 20:10:00 -0000 Received: from ip-130-180-70-188.unitymediagroup.de (EHLO [192.168.0.103]) [130.180.70.188] by mail.gmx.net (mp035) with SMTP; 15 Feb 2013 21:10:00 +0100 X-Authenticated: #32709443 X-Provags-ID: V01U2FsdGVkX1+ViRsl1+aVwRI60f5145FIi5to6gPMN3DCtwtmkM v9zYCycxpb2Ov1 Message-ID: <511E9615.3020007@gmx.net> Date: Fri, 15 Feb 2013 21:09:57 +0100 From: Kamil Szczesny User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath0: device timeout on 9.1-RELEASE References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> <511E910D.1080901@gmx.net> <511E9446.4070708@gmx.net> In-Reply-To: <511E9446.4070708@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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, 15 Feb 2013 20:10:02 -0000 Am 15.02.2013 21:02, schrieb Kamil Szczesny: > Am 15.02.2013 20:55, schrieb Adrian Chadd: >> Sure, that shows that your environment is quite noisy. :-) >> >> But is transmission just plain not happening? Is it just never >> associating? Or is it sometimes associating and sometimes not? >> > > > It's a bit crowded here ; ) > > Well as far as I have observed, it never associated. ehm, well.. ath0 seems to be, wlan0 however not: ath0: flags=8843 metric 0 mtu 2290 ether 1c:7e:e5:10:61:16 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8c43 metric 0 mtu 1500 ether 1c:7e:e5:10:61:16 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid home channel 3 (2422 MHz 11g) regdomain ETSI indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL > > regards, > Kamil > >> >> >> Adrian >> >> >> On 15 February 2013 11:48, Kamil Szczesny wrote: >>> Adrian, >>> >>> Finally, I managed to get again a 9.1-RELEASE running with a recompiled >>> kernel. >>> >>> gomorrha% uname -v >>> FreeBSD 9.1-RELEASE #0 r246834: Fri Feb 15 18:57:51 CET 2013 >>> root@gomorrha.local:/usr/obj/usr/src/sys/WIFIDEBUG >>> >>> This is the result of athstats: >>> >>> gomorrha% /usr/local/bin/athstats -i ath0 >>> 32484 data frames received >>> 5130 data frames transmit >>> 3273 mib overflow interrupts >>> 1M current transmit rate >>> 190 watchdog timeouts >>> 2040 rx failed 'cuz of bad CRC >>> 7 rx failed 'cuz of PHY err >>> 7 CCK restart >>> -0/+0 TDMA slot adjust (usecs, smoothed) >>> 86 avg recv rssi >>> -96 rx noise floor >>> 5130 tx frames through raw api >>> 1 first step level >>> 1 OFDM weak signal detect >>> 12 ANI increased spur immunity >>> 10 ANI decrease spur immunity >>> 990 ANI enabled OFDM weak signal detect >>> 2061 ANI disabled OFDM weak signal detect >>> 3041 ANI disabled CCK weak signal threshold >>> 4 ANI increased first step level >>> 2940667 cumulative OFDM phy error count >>> 5258173 cumulative CCK phy error count >>> 74 bad FCS >>> 105 average rssi (beacons only) >>> 84 average rssi (all rx'd frames) >>> Antenna profile: >>> [1] tx 0 rx 32484 >>> >>> Is it somewhat helpful? >>> >>> regards, >>> Kamil >>> >>> Am 11.02.2013 20:43, schrieb Adrian Chadd: >>> >>>> Ok.. >>>> >>>> On 11 February 2013 11:33, Kamil Szczesny wrote: >>>>> >>>>> Still with 9.0-RELEASE: >>>>> >>>>> gomorrha% vmstat -i >>>>> interrupt total rate >>>>> irq1: atkbd0 6 0 >>>>> irq16: ath0 ehci0 1367 13 >>>> >>>> >>>> .. I can't tell here whether there's any interrupts making it to the >>>> ath0 device or not. >>>> >>>> The driver in -HEAD logs the TX and RX interrupt counts in a ath >>>> sysctl which I can track. >>>> >>>> Can you please compile up athstats and recompile your kernel with: >>>> >>>> ATH_DEBUG >>>> AH_DEBUG >>>> ATH_DIAGAPI >>>> >>>> .. as we will need to establish whether you're actually queuing frames >>>> to the hardware, whether they're going out, whether the hardware is >>>> actually completing them, and whether the interrupt is being >>>> generated. >>>> >>>> Thanks, >>>> >>>> >>>> >>>> Adrian >>>> >>>>> irq23: ehci1 250 2 >>>>> cpu0:timer 8014 77 >>>>> irq256: em0 523 5 >>>>> irq258: ahci0 15444 149 >>>>> cpu1:timer 2797 27 >>>>> cpu2:timer 3743 36 >>>>> cpu3:timer 3053 29 >>>>> Total 35197 341 >>>>> >>>>> >>>>> >>>>> Am 11.02.13 19:59, schrieb Adrian Chadd: >>>>> >>>>>> Hi, >>>>>> >>>>>> Would you please look at the output of vmstat -i, see if the ath0 >>>>>> device is receiving interrupts? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> >>>>>> Adrian >>>>>> >>>>>> >>>>>> On 10 February 2013 23:30, Kamil Szczesny wrote: >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> after a downgrade to 9.0-RELEASE the issue remains the same. >>>>>>> /var/log/messages is spamed by equal authentication timeout entries. >>>>>>> >>>>>>> regards, >>>>>>> Kamil >>>>>>> >>>>>>> Am 10.02.13 20:10, schrieb Adrian Chadd: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Would you please try 9.0-RELEASE too? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Adrian >>>>>>>> >>>>>>>> >>>>>>>> On 10 February 2013 00:38, Kamil Szczesny wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> I'm facing a problem with ath0 on FreeBSD 9.1-RELEASE, that was >>>>>>>>> not >>>>>>>>> existent >>>>>>>>> on 8.x-RELEASE. >>>>>>>>> >>>>>>>>> The issue seems to be the similar to this one: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065667.html >>>>>>>>> >>>>>>>>> >>>>>>>>> I do have the same NIC. pciconf -lv output is equal: >>>>>>>>> >>>>>>>>> ath0@pci0:2:0:0: class=0x028000 card=0x3a701186 chip=0x0024168c >>>>>>>>> rev=0x01 >>>>>>>>> hdr=0x00 >>>>>>>>> vendor = 'Atheros Communications Inc.' >>>>>>>>> device = 'AR5008 Wireless Network Adapter' >>>>>>>>> class = network >>>>>>>>> >>>>>>>>> /etc/rc.conf: >>>>>>>>> wlans_ath0="wlan0" >>>>>>>>> ifconfig_wlan0="WPA DHCP" >>>>>>>>> >>>>>>>>> /etc/wpa_supplicant.conf: >>>>>>>>> network={ >>>>>>>>> ssid="home" >>>>>>>>> psk="123" >>>>>>>>> } >>>>>>>>> >>>>>>>>> However, it is not starting to work. >>>>>>>>> >>>>>>>>> I do not have /usr/src/tools/ath so that I can not provide the >>>>>>>>> output. >>>>>>>>> >>>>>>>>> /var/log/messages is spammed with: >>>>>>>>> >>>>>>>>> Feb 10 09:08:26 gomorrha wpa_supplicant[1500]: Trying to associate >>>>>>>>> with >>>>>>>>> xx:xx:xx:xx:xx:xx (SSID='home' freq=2422 MHz) >>>>>>>>> Feb 10 09:08:30 gomorrha kernel: ath0: device timeout >>>>>>>>> Feb 10 09:08:36 gomorrha wpa_supplicant[1500]: Authentication with >>>>>>>>> xx:xx:xx:xx:xx:xx timed out. >>>>>>>>> >>>>>>>>> Any idea what might be wrong or how I could fix this? >>>>>>>>> >>>>>>>>> regards, >>>>>>>>> Kamil >>>>>>>>> _______________________________________________ >>>>>>>>> freebsd-wireless@freebsd.org mailing list >>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>>>>> To unsubscribe, send any mail to >>>>>>>>> "freebsd-wireless-unsubscribe@freebsd.org" >>>>>>> >>>>>>> >>>>>>> >>>>> >>>> >>> >> From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 20:15:32 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 ECEC21CA for ; Fri, 15 Feb 2013 20:15:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by mx1.freebsd.org (Postfix) with ESMTP id 88914249 for ; Fri, 15 Feb 2013 20:15:32 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn17so1608156wib.16 for ; Fri, 15 Feb 2013 12:15:31 -0800 (PST) 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; bh=jx9NvdljRdk0ZDZ8N+6wpU9Ho5d1Kg9X3Yg/R0+3boo=; b=EA0+/1rPUwJu/IKV3oYMLZE3PcgA+E+BGfVmu1EObbp3f9t1SmaDjeTO0PP0lcRg6B lvKrowRNaYvtv4owZ+gnZ6ND4uOR9ZbKet7uJUPWl8c3V+TIvhvqvogYue3AFTIEJ+OE +b8bKEZz6Sbur2yeTy8WbnWG4aA+vVnncxgbFvRKI8sOWeTchUrxbXDVMtmcgOeDs1Zn lsUA1TPQupvVwUSTeiLoYy2+NLDjwg6tqTu0InHjzNFpk9y8xgvkTpKwXjyVH+u5jbYH LAZGQRCnmghFAaTN+XkhgkFyXWs5Zz0MMLHnZddxDI5LwEctpEXwOxS5LNb3yEAVIAYe 8buA== MIME-Version: 1.0 X-Received: by 10.194.7.136 with SMTP id j8mr6657006wja.38.1360959331324; Fri, 15 Feb 2013 12:15:31 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 12:15:31 -0800 (PST) In-Reply-To: <511E9615.3020007@gmx.net> References: <51175C69.6050003@gmx.net> <51189E1E.70206@gmx.net> <51194795.5070500@gmx.net> <511E910D.1080901@gmx.net> <511E9446.4070708@gmx.net> <511E9615.3020007@gmx.net> Date: Fri, 15 Feb 2013 12:15:31 -0800 X-Google-Sender-Auth: zYv2cntIN2MmQkWq-PybIQsSANs Message-ID: Subject: Re: ath0: device timeout on 9.1-RELEASE From: Adrian Chadd To: Kamil Szczesny Content-Type: text/plain; charset=ISO-8859-1 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, 15 Feb 2013 20:15:33 -0000 On 15 February 2013 12:09, Kamil Szczesny wrote: > ehm, well.. ath0 seems to be, wlan0 however not: Well, wlan0 is what matters. I'm sorry, I can't be more help at the moment. I'm really busy making other things work. I'd use athstats -z (as root) and then watch your device associate. See if the TX counter values increment. There's also some further descriptor based debugging you can do if you've compiled in ATH_DEBUG, but it gets very noisy very quickly. Look at sys/dev/ath/if_ath_debug.h and enable XMIT (0x01) and XMIT_DESC (0x02) by OR'ing them together (ie, 0x03 :): # sysctl dev.ath.0.debug=0x03. Then let it do some scanning/association and fail a few times, then set it back to 0, and look at /var/log/messages. That will log the descriptor setup and completion for each TX attempt and it'll hopefully tell us whether it's actually being transmitted or not. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 22:51:48 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 BE34A269 for ; Fri, 15 Feb 2013 22:51:48 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm9-vm7.bullet.mail.gq1.yahoo.com (nm9-vm7.bullet.mail.gq1.yahoo.com [98.136.218.246]) by mx1.freebsd.org (Postfix) with SMTP id 85C8FB46 for ; Fri, 15 Feb 2013 22:51:48 +0000 (UTC) Received: from [98.137.12.61] by nm9.bullet.mail.gq1.yahoo.com with NNFMP; 15 Feb 2013 22:51:47 -0000 Received: from [208.71.42.210] by tm6.bullet.mail.gq1.yahoo.com with NNFMP; 15 Feb 2013 22:51:47 -0000 Received: from [127.0.0.1] by smtp221.mail.gq1.yahoo.com with NNFMP; 15 Feb 2013 22:51:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1360968707; bh=LFdKPlZmdooaDlt/ReokrxqwyEJcoCK9ELhu8IwUyzI=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:X-Received:Received:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=hQs7ePF6rrC/ONXwCGQPWOLfStmGrDi6P5spX0qIaCho52UVfEnqunNvJ9/bx3F1cil2er262oDkMTGTlcxnDIrOBk2pF9BODcANV7IMZ8WNb0vjfqwerJkth7/Hz8qvfkwUdb/3mvS9oVq9sMsjgU8WVD7+F/oggSOuQ8ZREzM= X-Yahoo-Newman-Id: 558393.24418.bm@smtp221.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: ILH_FBgVM1nP.gAK1Dy1krPFQBOyA2LjGLuqu3ZEWwncKv4 1dff3OcJnur0uxl0wjkrc7xCw.oEH3Op_YP_ajX1t2_.G17DnuiSFQ9.AJ2W F1whXhHAaYbzXrE9oyjOj.L3w7_xiLm9xokNfdOqGUY2y.0vpA3.a.bwkfqN 9D0IYP.aTXaNyGZ9zrk2ekWN3nNcfhQfmT.N84esLue8qn7WmNcyFUZ0NxjA LeN5ZV18Ool9xM6km2emkgIuWOG.FX1jXqcS4H21eAE8Gjkjs1G7MAOyAHKs SYEBjXbMG3_gUHA6FcmSImFhTnBUb2TSbflWTFrrZ2DRf0_PUdcCVVKlljom ZgiXjnPwhRUYu1AHykbS8xPqbOAcDteyjY7AshcVUouI6LpldjOzqiXRGlgm qQ4U6HnS4qTbWxzphux7145X8zTPQZuVnx30mClQCFkEMKHDh0PH0xjAZQID dgMpoamt.q8q7Bh7i9ik- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-lb0-f174.google.com (moonlightakkiy@209.85.217.174 with plain) by smtp221.mail.gq1.yahoo.com with SMTP; 15 Feb 2013 14:51:47 -0800 PST Received: by mail-lb0-f174.google.com with SMTP id l12so2992885lbo.33 for ; Fri, 15 Feb 2013 14:51:45 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.130.131 with SMTP id oe3mr3698478lab.1.1360968705476; Fri, 15 Feb 2013 14:51:45 -0800 (PST) Received: by 10.112.1.37 with HTTP; Fri, 15 Feb 2013 14:51:45 -0800 (PST) Date: Fri, 15 Feb 2013 15:51:45 -0700 Message-ID: Subject: Re: [RFC] serialising net80211 TX From: PseudoCylon To: Adrian Chadd , Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 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, 15 Feb 2013 22:51:48 -0000 > ------------------------------ > > Message: 2 > Date: Wed, 13 Feb 2013 21:14:53 -0800 > From: Adrian Chadd > To: freebsd-wireless@freebsd.org > Subject: [RFC] serialising net80211 TX > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > I'd like to work on the net80211 TX serialisation now. I'll worry > about driver serialisation and if_transmit methods later. > > The 30 second version - it happens in parallel, which means preemption > and multi-core devices can and will hit lots of subtle and > hard-to-debug races in the TX path. > > We actually need an end-to-end serialisation method - not only for the > 802.11 state (sequence number, correct aggregation handling, etc) but > to line up 802.11 sequence number allocation with the encryption IV/PN > values. Otherwise you end up with lots of crazy subtle out of order > packets occuring. The other is the seqno/CCMP IV race between the raw > transmit path and the normal transmit path. There are other nagging > issues that I'm trying to resolve - but, one thing at a time. > > So there are three current contenders: > > * wrap everything in net80211 TX in a per-vap TX lock; grab it at the > beginning of ieee80211_output() and ieee80211_start(), and don't > release it until the frame is queued to something (a power save queue, > an age queue, the driver.) That guarantees that the driver is called > in lock-step with each frame being processed. Long held locks could be worse. While another thread holding a lock, when one thread try to grab a lock, it will spin a bit then be suspended. This could be more expensive than context switching by the scheduler. If a thread hold a lock longer, there will be more chance this to happen. > * do deferred transmit- ie, the net80211 entry points simply queue > mbufs to a queue, and a taskqueue runs over the ifnet queue and runs > those frames in-order. There's no need for a lock here as there's only > one sending context (either per-VAP or per-IC). I tried taskqueue on run(4), changed it from 1) to 2). Queue with shared thaskqueue, i.e taskqueue_thread, didn't work good, but with own taskqueue works good (60mbp->70+mbp). The catch is I only tested on core2 duo and dual core + ht atom. I saw you patched ath(4) to use taskqueue. How is it working? There are threads other than Tx thread are running on a system, so context switching will happen one way or other. We want to do it smart way, i.e. rather than changing thread on every tx, switch on multiple tx. Currently, tx threads are kept alive until packets are passed to h/w. Instead, if we kill them right after queuing a frame to if_snd and let one thread (would be new ieee80211_tx thread) handle all the packets, there will be fewer threads, so should be less context switching. Anyhow, I don't think we need to queue/dequeue twice, one on vap->iv_ifp->if_snd and one on ic->ic_ifp->if_snd. AK From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 23:03:14 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 BB35C6F2 for ; Fri, 15 Feb 2013 23:03:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id 51B22CB5 for ; Fri, 15 Feb 2013 23:03:13 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm14so1733363wib.3 for ; Fri, 15 Feb 2013 15:03:13 -0800 (PST) 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; bh=pPOsVJTmuFqRYSH7meBa1CZQ2tG66sPDxCFFXc9UBLg=; b=rz4Q75BVBLoV0th6+TYfeKahjwAzFia9Le+lVJ/TcYoUDgAfiWcMYCxoN2mWZ9l/Kh uQT2dlz8zt2NwQsbAvhlT8HCqtElBP43HUCiCytGYEiiOYKKjiS//r9X4DVDnb4KzsrM 4MeZXrRiMKeMARQKyca3P+l5lav//X8OKzRBRdJmJRbJrlt3i4UN0AjhXoUVTIfapn0o LvFy98XxMeh+s+jmtW4KEbhy6nMtnzUXwIUP3Sb22w8GxzSByi0G2dlgMwumEV17zNgh 0wJaZPqRMEwTEuyjGyKlEVXLcvhpbb5+UTDVqHGR23x7HR/shk8oF7T9JytZuv9AW/9F n8lg== MIME-Version: 1.0 X-Received: by 10.194.161.135 with SMTP id xs7mr7192788wjb.41.1360969393065; Fri, 15 Feb 2013 15:03:13 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 15:03:12 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 15:03:12 -0800 X-Google-Sender-Auth: kq9aoKPpte5wbMhJkzKb7xNnKfA Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 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, 15 Feb 2013 23:03:14 -0000 The (many) problems include the two TX paths - one is via _start / _transmit, and one is the raw xmit path. So in the short term it'll be easier (!) to just wrap all TX entry points with a VAP TX lock. Once that's done and we've debugged it, we can look at breaking it into a queue with a taskqueue thread for deferred transmit. How's that sound? Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 01:10:07 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 6A90E7BA for ; Sat, 16 Feb 2013 01:10:07 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm23-vm0.bullet.mail.bf1.yahoo.com (nm23-vm0.bullet.mail.bf1.yahoo.com [98.139.212.191]) by mx1.freebsd.org (Postfix) with ESMTP id D8E19186 for ; Sat, 16 Feb 2013 01:10:06 +0000 (UTC) Received: from [98.139.215.140] by nm23.bullet.mail.bf1.yahoo.com with NNFMP; 16 Feb 2013 01:10:00 -0000 Received: from [98.139.211.205] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 16 Feb 2013 01:10:00 -0000 Received: from [127.0.0.1] by smtp214.mail.bf1.yahoo.com with NNFMP; 16 Feb 2013 01:10:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1360977000; bh=RNkhfFAdSubJKLn4biyLuiqqRMyYSp00ZutRiQhIBIQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:X-Received:Received:Date:Message-ID:Subject:From:To:Content-Type; b=VM27N0tsqpREe8TBp2npjk5rJyP1M55x77P6tqz4OJPoyb9WhMNvfAjf6mIHrQsTJWprOZR8KCWJqvbTuZKKdM/bL3MrmOzMT4/z1gTe18mMHl3Ikri8egfq0AqHkA5/wxDw4GveS76DY46NyIEd7NOK5od+xE3n9iv/JbvCioM= X-Yahoo-Newman-Id: 572159.55604.bm@smtp214.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: J6u82yAVM1nww3BKGARB1ongET_2ocGOZ2t7tJ8ZNCz8C3a gDs0Wh9tnSq.bodFyiFJO6M34AIGjCUFYTwvyerNKE7t0uzoL_iQGjqq7dFy Z2m9cZ0E_6uDRCxB5_cwIP7qTkW19CwlDGogfFOMljvlXRr.I96m8L5kS.Ds zLnpC47vaaSCFofLINa9WawYyK98FwxkwfVOgZOLK8WA1oNJaIqXmb68USbl tS4AnQQM2TMw8qvr2YJzWUL97zhYTHQOMBgNy9B.EiTOxLJP2ZP.P6rYZ45D 78gbs_EDZHsO53En6S27Nkzw_1LaLfmjcO9aF2Auk3YcEhHTJzmxtwvg77ec VHEyoMxx59s3H8_xGirkzfM7LlMcgVpMJvq17vD0cGXuUChHG3ebgQdvWtFh 6jYE5cLpD_g7eNjmvdgR65VSoplubuZqTB1KSjbm_uBOWUFAUtPcf84MyRBV 32aK.bKsDRkWm4nuCQhnebZn07BK_VyYijElCkk8dcfjWPlPSsy3LJJ8Z4u6 NlfsMERVKWoVjDtk2y.NvLpixeAbDToxf6Yj1RAaMEt9Yolv875vljrzuJDv rl4LX6Gk- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-lb0-f181.google.com (moonlightakkiy@209.85.217.181 with plain) by smtp214.mail.bf1.yahoo.com with SMTP; 15 Feb 2013 17:10:00 -0800 PST Received: by mail-lb0-f181.google.com with SMTP id gm6so2977913lbb.26 for ; Fri, 15 Feb 2013 17:09:59 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.24.199 with SMTP id w7mr2829642lbf.102.1360976999343; Fri, 15 Feb 2013 17:09:59 -0800 (PST) Received: by 10.112.1.37 with HTTP; Fri, 15 Feb 2013 17:09:59 -0800 (PST) Date: Fri, 15 Feb 2013 18:09:59 -0700 Message-ID: Subject: negotiating HT params at assoc in sta mode From: PseudoCylon To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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, 16 Feb 2013 01:10:07 -0000 http://fxr.watson.org/fxr/source/net80211/ieee80211_ht.c?#L2656 Shouldn't a sta include iv_ampdu_rxmax and iv_ampdu_density instead when associating? 1) A driver initiates iv_ampdu_rxmax and iv_ampdu_density based on h/w capabilities. 2) When a sta trying to associate, ieee80211_send_mgmt() { case IEEE80211_FC0_SUBTYPE_ASSOC_REQ: ieee80211_add_htcap(); /* the function in question */ } 3) When an ap receives the assoc_req packet, the ap will save ht params to ni_htparam. Then the ap will use those values for Tx packets. 4) The sta will receive packets which size is within the limits if the sta included iv_ampdu_rxmax and iv_ampdu_density. AK From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 01:20:28 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 351F2D96 for ; Sat, 16 Feb 2013 01:20:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id B5A071B8 for ; Sat, 16 Feb 2013 01:20:27 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hi8so1789485wib.13 for ; Fri, 15 Feb 2013 17:20:26 -0800 (PST) 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; bh=WYiuali/W1w04p9CzahKr4o+B8XDnQzVO2Tnj7SMBd4=; b=OHm38pb3H4BeFvksAXAYvk1copOxcP5ukR58ZVq6FHA4E+5n3zzBAUVnBtrSlD57Ac 5lNFR1iNkzNhrq8KSAMWHnUU+yoB5XFPSNLYgzuG9C8vSufQ31+sWeuNairrXVwxvvX/ uUeoEDmt/cGJZQNCZx7Q7LSFH4mMf2S1mlBJ2VDLhKhHWphRslqkrPvIRcwPnecvGmOv tSJeY41CLLgW8+0NCkynhzgnjNA5bQTdaxRnKc6uX2xtKX96k4HCi+HYc+heeyKdcHFZ TasJe40FtF1QQ/SRorsgEznO2zMZNUqCxm2mm4Y0O9fHWLgiJIKtJ2gnJvhZ4uOAGzzB 0ZIg== MIME-Version: 1.0 X-Received: by 10.180.99.227 with SMTP id et3mr7487444wib.6.1360977626576; Fri, 15 Feb 2013 17:20:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 17:20:26 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 17:20:26 -0800 X-Google-Sender-Auth: oBJb6QXKMf5CxNbY403pcOfrVdc Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 01:20:28 -0000 Hm, that sounds right, what's the code doing wrong? Adrian On 15 February 2013 17:09, PseudoCylon wrote: > http://fxr.watson.org/fxr/source/net80211/ieee80211_ht.c?#L2656 > Shouldn't a sta include iv_ampdu_rxmax and iv_ampdu_density instead > when associating? > > 1) A driver initiates iv_ampdu_rxmax and iv_ampdu_density based on h/w > capabilities. > > 2) When a sta trying to associate, > ieee80211_send_mgmt() > { > case IEEE80211_FC0_SUBTYPE_ASSOC_REQ: > ieee80211_add_htcap(); /* the function in question */ > } > > 3) When an ap receives the assoc_req packet, the ap will save ht > params to ni_htparam. Then the ap will use those values for Tx > packets. > > 4) The sta will receive packets which size is within the limits if the > sta included iv_ampdu_rxmax and iv_ampdu_density. > > > AK > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 01:26:40 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 3C474130 for ; Sat, 16 Feb 2013 01:26:40 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm8-vm2.bullet.mail.ne1.yahoo.com (nm8-vm2.bullet.mail.ne1.yahoo.com [98.138.90.156]) by mx1.freebsd.org (Postfix) with ESMTP id AFDD11E8 for ; Sat, 16 Feb 2013 01:26:39 +0000 (UTC) Received: from [98.138.90.53] by nm8.bullet.mail.ne1.yahoo.com with NNFMP; 16 Feb 2013 01:19:50 -0000 Received: from [98.138.84.36] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 16 Feb 2013 01:19:50 -0000 Received: from [127.0.0.1] by smtp104.mail.ne1.yahoo.com with NNFMP; 16 Feb 2013 01:19:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1360977590; bh=zr2ZKAYEHKalhtEyhY68xo18Bsn1gdzUGrRjz5oXp2A=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=y377tqE6kGpG7a+v/XBLRrVw4dgdjb331n0ptGVVqOFaIXzK3n1Z5CAh4tUAWEsYRZka6ndBBSCgBXMcj7NR6c/W4weJBFbuOdX0zfm12sig1wPTTVBDXE2GBbeX/6VyV7tyJWebmqZHjhdMslZpZ/e8FgI+qnDO0On82tvFx0A= X-Yahoo-Newman-Id: 618882.28273.bm@smtp104.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: jqnFFPAVM1l8ARPNJNTmCzm6Wu_tY3J6M.1y6ALWPTHpRPg Z77Wgt7mqYq912cGP9qS__R1KOlIuzaJYGtbfsqBRaI99t7iCi..T_zosQQI xtP76EZezNpAsos45bRgFqIl4tfiT7utQ7pT.4Sc0az9Tlu8.EB_qeGX_eMz nXkAsOwD0K7_w4qiAFXSOP82HMtErTInWJZD1Jfk.GRyhDMfVEqRw8Xalsog kqKsTvHmOELIS7dlzLQcXtlcoXTzj4Ng2PyceaP6rQ1zqyZ7HjbnaKqDJigW xaXzDfjz6ofS85gWEPpqxHMM14hpy9BDfiCoq9kOQa6WCQAN0bY9V2DRcCYC u7P_dVUdxZr1EBQoz8v.GgLqc3YgZ3twp5mFW8fzGUTCWvvtbgwaVhz630HL rTsflMA7.vRWgXsX43JC0tlZ7tS0.MrXwOk6C7otAihdnN80xxx74.6zbMQK jaQ19IFXRbhQbx8giYMDl X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-la0-f52.google.com (moonlightakkiy@209.85.215.52 with plain) by smtp104.mail.ne1.yahoo.com with SMTP; 15 Feb 2013 17:19:50 -0800 PST Received: by mail-la0-f52.google.com with SMTP id fs12so3933027lab.39 for ; Fri, 15 Feb 2013 17:19:48 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.84.130 with SMTP id z2mr2837847lby.65.1360977588907; Fri, 15 Feb 2013 17:19:48 -0800 (PST) Received: by 10.112.1.37 with HTTP; Fri, 15 Feb 2013 17:19:48 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 18:19:48 -0700 Message-ID: Subject: Re: [RFC] serialising net80211 TX From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 01:26:40 -0000 On Fri, Feb 15, 2013 at 4:03 PM, Adrian Chadd wrote: > The (many) problems include the two TX paths - one is via _start / > _transmit, and one is the raw xmit path. > > So in the short term it'll be easier (!) to just wrap all TX entry > points with a VAP TX lock. > Once that's done and we've debugged it, we can look at breaking it > into a queue with a taskqueue thread for deferred transmit. > > How's that sound? I think that's good because if_start/transmit == data packet && if_raw_xmit == mgmt packet is no longer true. http://svnweb.freebsd.org/base?view=revision&revision=222682 And, all-in-one Tx path works with run(4) at least. AK From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 02:27:25 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 5E729C8D for ; Sat, 16 Feb 2013 02:27:25 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm33-vm0.bullet.mail.ne1.yahoo.com (nm33-vm0.bullet.mail.ne1.yahoo.com [98.138.229.64]) by mx1.freebsd.org (Postfix) with ESMTP id E968F38F for ; Sat, 16 Feb 2013 02:27:23 +0000 (UTC) Received: from [98.138.90.55] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 16 Feb 2013 02:21:10 -0000 Received: from [98.138.84.45] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 16 Feb 2013 02:21:10 -0000 Received: from [127.0.0.1] by smtp113.mail.ne1.yahoo.com with NNFMP; 16 Feb 2013 02:21:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1360981270; bh=DymMpHZ3lgSqv+GjPW7tNxwSnBdrC5/CVt6daOxg+zA=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=d1TOQmhrR37GEhtTa58+MKKn+Wj2n9aF2d1SDFeSqjzPBs5dcUGSW9AI8J2QMNxfa0giIKo1yLJFL6Dv296qVqqS7nIhuBpuK35Dwr7N6NbkZzoAHot2vN6czcy48pwTM/H+AUZm2mOz0leK4V/v0FH9m6lbKfh5XAc52qgeuUM= X-Yahoo-Newman-Id: 14479.94593.bm@smtp113.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 96mdUFAVM1kpwrxCuSM.ohMiJeg24g2D3Y7lX.2BFqSqSpY UM1eN6TrJZJYMR20QM4kANLWiGTM0BxvqN8A8zqZ_860_3efK2eZaKKIhryr 7fckDVRg3kqyZSEsq5mM7CJco8cqhyzvC53v.tzR2CxIDD_m6Wq2_4YyOEIJ cY3RrayAlUCnVFJSbMVMAhDsrOa.YUtPWn3SooHkGOUnbxUOcGJxtWVdO4EJ DG2cVJYCWRcagLK0XXsakcmaX2c5mrTNcWKK6iMomiQbWt0ZCx4ow7VltVKB EdbdqsRoram9plld5nivIrkKBxJ4TxRpACPR0EXtHpiwmEj1XogwoeLyedBN yjnUyQra7OphkdvytFJBiV56kqfh0GzWjHm0lPHeTPK2WySLWiJ6LTwPB4k_ wXVBgp5N2qvGR4Szxe.EB7pPqKQH4HkyDglBt0s.vBYakUsfEsnOgVsByjFF WZQrolrBVNhQrXPppdToyT8opkvasCkHJyjtxcQnMnaH3Jn3rob1jVuC3NuO _GKD2G2v6r8uMwROGr2LmnHGMnd7sb4cRdv2JabFFqOhHOKn6hoIfl9AMPhu co12vnw-- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-la0-f51.google.com (moonlightakkiy@209.85.215.51 with plain) by smtp113.mail.ne1.yahoo.com with SMTP; 15 Feb 2013 18:21:09 -0800 PST Received: by mail-la0-f51.google.com with SMTP id fo13so4028885lab.38 for ; Fri, 15 Feb 2013 18:21:08 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.24.199 with SMTP id w7mr2877936lbf.102.1360981268212; Fri, 15 Feb 2013 18:21:08 -0800 (PST) Received: by 10.112.1.37 with HTTP; Fri, 15 Feb 2013 18:21:07 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 19:21:07 -0700 Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 02:27:25 -0000 On Fri, Feb 15, 2013 at 6:20 PM, Adrian Chadd wrote: > Hm, that sounds right, what's the code doing wrong? Currently, it seems the sta sends back ht params the ap included in a PROBE_RESP packet. So, the ap could send ampdu packets bigger (in byte) than the sta can handle or packet gaps are different from the sta wants after ba session is created. (During ba session negotiation, these params are not exchanged, only window sizes (frame count), seq #, and token.) AK > > > > Adrian > > > On 15 February 2013 17:09, PseudoCylon wrote: >> http://fxr.watson.org/fxr/source/net80211/ieee80211_ht.c?#L2656 >> Shouldn't a sta include iv_ampdu_rxmax and iv_ampdu_density instead >> when associating? >> >> 1) A driver initiates iv_ampdu_rxmax and iv_ampdu_density based on h/w >> capabilities. >> >> 2) When a sta trying to associate, >> ieee80211_send_mgmt() >> { >> case IEEE80211_FC0_SUBTYPE_ASSOC_REQ: >> ieee80211_add_htcap(); /* the function in question */ >> } >> >> 3) When an ap receives the assoc_req packet, the ap will save ht >> params to ni_htparam. Then the ap will use those values for Tx >> packets. >> >> 4) The sta will receive packets which size is within the limits if the >> sta included iv_ampdu_rxmax and iv_ampdu_density. >> >> >> AK >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 03:54:52 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 A0944697 for ; Sat, 16 Feb 2013 03:54:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (wg-in-x0229.1e100.net [IPv6:2a00:1450:400c:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id 0DF7A839 for ; Sat, 16 Feb 2013 03:54:51 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id ds1so1400306wgb.0 for ; Fri, 15 Feb 2013 19:54:51 -0800 (PST) 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; bh=XV9m8zRtBCxL90ezXkqz5qF2To5Md4xk+OfmiV6YjmI=; b=ra6sBy2H4TQxcxvSimHuRGwIX35txqoWd5ya+IFFSW61qzO7C/hnTZkUIuR8hKHRIh OeWj/hfuGWUNKtaWiY5FRG5kb6yy+XRVSlYi3f9/bDJo0X1R9Ghh+ulgSD2UiWe3yRPi EnqWwByXuiON39nDstzzB6tYkQsw9kV51N8UDG0ndkZBYYn9Urc7b9fwgC3vAHZVKpVZ 95wzqSiqP5beWIWUCpTc3O4pUFcUGidfkkXQCNhdKQENYbAPuknuF/mIY7VkxLvnF+7N ruml0Sx1YAEuY4Je+bYRh9yIY7qlRBrnYiP2JNb9oc65dXr0Zz6OoesYG0+CBeTSIj+y 4Veg== MIME-Version: 1.0 X-Received: by 10.194.7.136 with SMTP id j8mr8018543wja.38.1360986891231; Fri, 15 Feb 2013 19:54:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 19:54:51 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 19:54:51 -0800 X-Google-Sender-Auth: rSolrXkfKk1oruKhnO8j9vKk89s Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 03:54:52 -0000 On 15 February 2013 18:21, PseudoCylon wrote: > On Fri, Feb 15, 2013 at 6:20 PM, Adrian Chadd wrote: >> Hm, that sounds right, what's the code doing wrong? > > Currently, it seems the sta sends back ht params the ap included in a > PROBE_RESP packet. So, the ap could send ampdu packets bigger (in > byte) than the sta can handle or packet gaps are different from the > sta wants after ba session is created. (During ba session negotiation, > these params are not exchanged, only window sizes (frame count), seq > #, and token.) Right. yes, we should be negotiating the ampdu density to be the maximum of what the AP and STA can associate. Same deal with IBSS peers (and mesh peers too, eventually.) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 04:47:26 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 6818ADDB for ; Sat, 16 Feb 2013 04:47:26 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm1-vm3.bullet.mail.gq1.yahoo.com (nm1-vm3.bullet.mail.gq1.yahoo.com [98.136.218.82]) by mx1.freebsd.org (Postfix) with SMTP id 1A5A19C5 for ; Sat, 16 Feb 2013 04:47:25 +0000 (UTC) Received: from [98.137.12.191] by nm1.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2013 04:40:26 -0000 Received: from [98.136.185.41] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2013 04:40:26 -0000 Received: from [127.0.0.1] by smtp102.mail.gq1.yahoo.com with NNFMP; 16 Feb 2013 04:37:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1360989464; bh=ANlmgbiKy/x7XC17WRDjZ5vVa8qQK3+wIzPVNlPiWog=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=pYWZjBegUYQV6Md38FebrJ6JiIoL0RH6iwtrauh99okZp3tfS9UPpj5ktEKn9VaMvxrDa2p24NoZkYeUAcY7e4iL6UN8yCwB17eZpFImspKwasV83YdJGLaqzVeBJtjH6atnsmR/yoIQiHUKqrd2HvWT8S1uv8cIn6ti5eBzHkQ= X-Yahoo-Newman-Id: 567306.36635.bm@smtp102.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 0r56XT8VM1mqCq914XqtvBl08KTxMba63vOwWOUM.uRPMqe NTe_7RwxiqFI23v_uwzEB1MMf7eVd73L.kCaIIYgPDbXkBoFYRHbzn3L9Drs XGoSPjvIVG.aowY7.HnL._bt.qIbxnj4fgrAkh6KZlZlmXKwmYJn_s2_jWr5 hbhO5md0JrgGpvwtR4oJhogWw0OLD4G5.MwXr3FzB91YOo62hJSsjF749fiI FWLp3ustJXGI5ndVzCEtTF9v0qtPJpAH9TaSzdISgJoaDx9zl_OPkkHw054M 1VZtk26vWY_bX1nq5PRTalqFQ69Mkwu_ZDzHU5gmggQ794DGZiC4NPAy7ArY h_gv32tZkSMiBZ94sQdlbsXTA_4LILLiUgKkaWYrci2gkqTlOyA6Vl_1h2M4 QN67qPVdi4fH4gh.JG8DDAWyQg7w_Puo.JrdZxSYrglBRjP8K58k8QZq7CsF UT5ZyzPcSMPxhOYfhf78Qag1G1o5N3KS4NoeBnV.kgC9CD_29gXYvg3dRw6B SmoIi8ylevykIGvMPQzlRS5P2UIpbQxINQOU5ObjYT7HG7sTUS9Ij_XJSc0. F3R.vAGPBzoK0rgLJp_la.GU- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-la0-f41.google.com (moonlightakkiy@209.85.215.41 with plain) by smtp102.mail.gq1.yahoo.com with SMTP; 16 Feb 2013 04:37:44 +0000 UTC Received: by mail-la0-f41.google.com with SMTP id fo12so4050007lab.28 for ; Fri, 15 Feb 2013 20:40:24 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.130.131 with SMTP id oe3mr4249821lab.1.1360989624056; Fri, 15 Feb 2013 20:40:24 -0800 (PST) Received: by 10.112.1.37 with HTTP; Fri, 15 Feb 2013 20:40:23 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 21:40:23 -0700 Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 04:47:26 -0000 On Fri, Feb 15, 2013 at 8:54 PM, Adrian Chadd wrote: > On 15 February 2013 18:21, PseudoCylon wrote: >> On Fri, Feb 15, 2013 at 6:20 PM, Adrian Chadd wrote: >>> Hm, that sounds right, what's the code doing wrong? >> >> Currently, it seems the sta sends back ht params the ap included in a >> PROBE_RESP packet. So, the ap could send ampdu packets bigger (in >> byte) than the sta can handle or packet gaps are different from the >> sta wants after ba session is created. (During ba session negotiation, >> these params are not exchanged, only window sizes (frame count), seq >> #, and token.) > > Right. yes, we should be negotiating the ampdu density to be the > maximum of what the AP and STA can associate. > > Same deal with IBSS peers (and mesh peers too, eventually.) Yes. But because of this test http://fxr.watson.org/fxr/source/net80211/ieee80211_ht.c#L2649 only nodes in sta mode are affected. AK > > > > Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 05:18:47 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 21BEFF1D for ; Sat, 16 Feb 2013 05:18:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 8DCF2A2B for ; Sat, 16 Feb 2013 05:18:46 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id 12so1424768wgh.3 for ; Fri, 15 Feb 2013 21:18:45 -0800 (PST) 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; bh=NtvccYDPrjiHwqoUrJAdBl1S04W76F19yEVg+im+Q+A=; b=ucRTp4tvkxNTgJ78lO18IixVzNE7ZsZCFkJeLJ18ydj+jJ9fXGrfYt7zvCwM1oKJzk s4rBKI5xMfQ/czqOr+/AOOqxFm4IVTqoQiulNqQk8B4IA4/0tc5AGdTO3p5c7hoy1CVf TpstBdhZ7Eass6TixF0RveL3N7ddVAVFuhKNV256XmBVu1RLpXnh4BM1kZySQgQXwyvI CvIQk6RzUqOFAgUUXaXWnKlB7PonIphHII9k54lpHehH8JRBb5yhRLPc5V45wpAbrzCx +1Qw7l15Gc7MfSJSBYPEcjxi2CO35p1TSesCSPWU8Y6PltmGGslwj4OjYTDjeuzrx6sh qFLg== MIME-Version: 1.0 X-Received: by 10.180.93.234 with SMTP id cx10mr9762944wib.34.1360991925680; Fri, 15 Feb 2013 21:18:45 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Fri, 15 Feb 2013 21:18:45 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 21:18:45 -0800 X-Google-Sender-Auth: YQ9BBMk5rZb-lSNkIchQUNEOXCs Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 05:18:47 -0000 Oh lordie. :-) Please file a PR so we don't forget to fix this? :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 19:34:07 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 02CBC4CC for ; Sat, 16 Feb 2013 19:34:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) by mx1.freebsd.org (Postfix) with ESMTP id 7055B9DD for ; Sat, 16 Feb 2013 19:34:06 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id dr13so3547868wgb.2 for ; Sat, 16 Feb 2013 11:33:59 -0800 (PST) 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; bh=Q8pmCSw8F5x9FPJ2BaL9uJJ48uQCyejlEpnvYWZxLuE=; b=Z92fFtghm8AE/SSDcA4NWHbeu3kyqWd3NrOa5a9+MxE5k6RvYypjvtuN8LchI+cZYn lOmQtHgPLXMUN7Tn53mOFnwYAepj+SPzr2THC0w7fy+YRO5Tgo/PsSwl/bWZB42fHehX 17uP5onqnPbhwzyTT0S7sfzDnE2OriRc5xEmvFkgEyneAtHsqFtdKQcBla7tAZbvIfWH wB/Vq4XrY3dXn9l+UEinV6GiZgkYpJYleIAH0tHfZeCbfMAG5TrvywymQg2x/vArwrqy VXUJRHEadzOfOU+2bUTQ4gbuKm9XSkuT+LhaQlOB336g3epPZ5lA5dD0tHAvFpd0DRyQ EX0w== MIME-Version: 1.0 X-Received: by 10.194.108.101 with SMTP id hj5mr10869283wjb.6.1361043239217; Sat, 16 Feb 2013 11:33:59 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Sat, 16 Feb 2013 11:33:59 -0800 (PST) In-Reply-To: References: <511E30FF.4050404@pean.org> Date: Sat, 16 Feb 2013 11:33:59 -0800 X-Google-Sender-Auth: um4zwDc8To1-vgpal7l7tRF3oX0 Message-ID: Subject: Re: Support for Mini PCie card WLE300NX( (AR9380) From: Adrian Chadd To: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 19:34:07 -0000 Oops, I didn't reply in public! On 15 February 2013 09:03, Adrian Chadd wrote: > Yup! I'm working on open sourcing the HAL side of things soon. I'm going through final code approval now. Then, of course, there's all this extra work required to get it somewhat validated - I have to write a bunch of testing routines to test TX power, TX and RX EVM (to make sure that things aren't distorting), fix up some of the shortcuts I've taken (eg making ANI work right), implement MSI interrupt handling, test whether 3-stream negotiation, TX and RX works correctly, make sure the STA timers are setup right, make sure the hostap timers are setup right, implement CABQ handling for hostap mode... .. yeah, there's still a lot of work to do. :-) But it's almost there. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 23:23:04 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 92CDD190 for ; Sat, 16 Feb 2013 23:23:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mx1.freebsd.org (Postfix) with ESMTP id 2FB01F63 for ; Sat, 16 Feb 2013 23:23:03 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id hm14so2350502wib.10 for ; Sat, 16 Feb 2013 15:22:57 -0800 (PST) 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; bh=wejPdDjZl/5+L+QFkjYjXD/rQzfR6g6r5UHID2Y5Vg8=; b=dCD+K7SGA/YH3D9E3749fku/YDj38TtZFDb8/Hxd0Ah9nV/gaNYAlrKsGPvManSMOH eVCz9xDK3QL6x2VAAPD6okJOtFq0ymV/ZlAcN0TEDaSt70CLotc+PgijK4qUr6UC/p8K CQVDk++d988337f58bXHCX+aGY8le+rZd24buB6rriztwBTlhkSWJtm5DYFfkObzt9r6 RzbM+PCz0UEei46xEbR0Wa939sTOaboWhPjDogiTMJS+ABWM20hqVVJMRwZ37Z/8AF4m 6EYugNFN7Rb4Otjb0SjuJdRKg+jhqG52ZCw7FBNZ5cTodjOoJDIEQz101/ZWTStdvOt3 VdDA== MIME-Version: 1.0 X-Received: by 10.180.81.164 with SMTP id b4mr10943747wiy.34.1361056977541; Sat, 16 Feb 2013 15:22:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Sat, 16 Feb 2013 15:22:57 -0800 (PST) In-Reply-To: References: Date: Sat, 16 Feb 2013 15:22:57 -0800 X-Google-Sender-Auth: a0BBtQTXf9yYSjZq5iwGGoRVMFY Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 23:23:04 -0000 Yeah - gluing TX into a single send queue is going to work, but there's definite queuing / QoS issues. You really want the management frames to be able to go out even if there's a _large_ amount of data frames going out. That's a side-issue though. I have a test patch that just wraps the output, mgmt_output and encapsulation/send routines with a TX lock. I can't wrap the whole TX path in a lock because there's some re-entrant behaviour going on (specifically net80211_start -> ampdu check -> send addba -> mgmt_output -> (re) grab TX lock). Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 16 23:46:59 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 BE951633 for ; Sat, 16 Feb 2013 23:46:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5BB32D1 for ; Sat, 16 Feb 2013 23:46:59 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id es5so3757031wgb.29 for ; Sat, 16 Feb 2013 15:46:51 -0800 (PST) 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; bh=E5Nh0vbv5QPbkRU9WaecuAU+yqcbJ1IMIqSchHvTbfc=; b=OQbhRtmNmlqufpWcq2Bb/SMdyRz7I0pZGYPLFVJ04gDBwBGbSV1xVbsD79IwOemjj6 5NZ6VJ5ji4vzh1jenKDSGZTCLCSE21YNQjJyI0a1s5RuyYqkFMNlfhJHRw3eYLYMk/C0 MCCPWLDQWdSOnEOa74raWIDKZdbCfirbm3zfkR3l4IMyMeWp9uYzDerE0XdnX9cAXA+h DTltdAXbPF+NdPP7y4N/kCoE0/TueYaUf0tx51q3KIukYrz5BPpLwRl3DRjRyT8qAcl7 p4UfJMlti9MhwQd02Vda5tEBKNR3AekiGM0Wm3wi2EoY3J9Ic1D6rdWNOOV++pN5xEER cw6w== MIME-Version: 1.0 X-Received: by 10.194.7.136 with SMTP id j8mr11377143wja.38.1361058411891; Sat, 16 Feb 2013 15:46:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Sat, 16 Feb 2013 15:46:51 -0800 (PST) In-Reply-To: References: Date: Sat, 16 Feb 2013 15:46:51 -0800 X-Google-Sender-Auth: onvk25m0KpF17Oe82m5R8OAGeco Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 16 Feb 2013 23:46:59 -0000 Hi, Here's the patch: * break out the per-packet send code into ieee80211_start_pkt() * introduce a per-vap TX lock * wrap the normal TX path ieee80211_encap(), parent->if_transmit and ic->ic_raw_xmit with the TX lock TODO: * the rest of the encap calls need to be wrapped in the TX lock - wds, superg, mesh. * the TX lock is not re-entrant but the TX path itself is (eg start -> start aggregation -> addba send -> mgmt_send -> (re) grab lock) so a bunch of this stuff needs to be rethought to be "clean" locking wise. I bet wds, superg and mesh is being called from the normal TX path and thus could be called with the TX lock already held. I should investigate this! * the TX aggregation state code should be protected by a lock - do that later? * add some lock / unlock assertion checks (eg assert the TX lock is held in ieee80211_encap()) and debug what code paths are / aren't being engaged. I'm still testing this. I've only tested it in STA mode thus far (iwn and ath.) thanks, Adrian Adrian