From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 22 04:19:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D1341065676 for ; Sun, 22 Jan 2012 04:19:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BBDA68FC0C for ; Sun, 22 Jan 2012 04:19:13 +0000 (UTC) Received: by vbbey12 with SMTP id ey12so1892164vbb.13 for ; Sat, 21 Jan 2012 20:19:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=5Hcz6bSOI5t8qgfznHoTgc5phNO+IERj8ykIX1yrKA8=; b=q1Hmt6Top5jjPald1JABxs26cM74zZq9bLEvucj0HNDfscrD1PRm25F6Ru3xKhylJT F/zRFSMZ+DRZURud3KW97dBFUKwvk54IbqKW4TjqEp/ZIGexjbojBUWXIqMwax4pu0O9 SV7hlt3+5l1KinZ7+gBBBD4fvElBv4AJJHNtE= MIME-Version: 1.0 Received: by 10.52.30.81 with SMTP id q17mr1587304vdh.115.1327205952995; Sat, 21 Jan 2012 20:19:12 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Sat, 21 Jan 2012 20:19:12 -0800 (PST) In-Reply-To: <20120121214434.GA2494@tinyCurrent> References: <20120121214434.GA2494@tinyCurrent> Date: Sat, 21 Jan 2012 20:19:12 -0800 X-Google-Sender-Auth: KPoQerRac1zrKRGX2TTianmynyQ Message-ID: From: Adrian Chadd To: Matthias Apitz Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwi0: UP/DOWN in WPA-PSK mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 04:19:14 -0000 Hi, Please file a bug report. I've no idea what is causing this but we can hopefully start enabling some debugging to figure it out. Adrian On 21 January 2012 13:44, Matthias Apitz wrote: > > Hello, > > I've changed my AP at home from WEP to WPA2 and since this one of my > stations facing after some while (~90 minutes) the problem of UP and > DOWN; in /var/log/messages it looks like this: > > Jan 21 22:00:09 Perlach wpa_supplicant[485]: CTRL-EVENT-DISCONNECTED - > Disconnect event - remove keys > Jan 21 22:00:09 Perlach kernel: wlan0: link state changed to DOWN > Jan 21 22:00:09 Perlach wpa_supplicant[485]: Trying to associate with > 00:13:f7:0d:08:48 (SSID='tarara' freq=2442 MHz) > Jan 21 22:00:09 Perlach wpa_supplicant[485]: Associated with > 00:13:f7:0d:08:48 > Jan 21 22:00:09 Perlach kernel: wlan0: link state changed to UP > Jan 21 22:00:12 Perlach wpa_supplicant[485]: WPA: Key negotiation > completed with 00:13:f7:0d:08:48 [PTK=CCMP GTK=CCMP] > Jan 21 22:00:12 Perlach wpa_supplicant[485]: CTRL-EVENT-CONNECTED - > Connection to 00:13:f7:0d:08:48 completed (reauth) [id=0 id_str=] > Jan 21 22:00:18 Perlach wpa_supplicant[485]: CTRL-EVENT-DISCONNECTED - > Disconnect event - remove keys > Jan 21 22:00:18 Perlach kernel: wlan0: link state changed to DOWN > Jan 21 22:00:18 Perlach wpa_supplicant[485]: Trying to associate with > 00:13:f7:0d:08:48 (SSID='tarara' freq=2442 MHz) > > The system runs 9-CURRENT from October 2010 (r214444) and did not show > this problem in WEP mode; wpa_supplicant lines are simple: > > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > eapol_version=1 > ap_scan=1 > fast_reauth=1 > > network={ > ssid="tarara" > key_mgmt=WPA-PSK > psk="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" > } > > Killing the dhclient(8) processes and restart > > # dhclient wlan0 > > helps to get out of this loop of UP/DOWN. > > Any ideas or should I file a bug report? > > Thanks > > matthias > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 > _______________________________________________ > 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 Sun Jan 22 05:40:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 373AC1065677 for ; Sun, 22 Jan 2012 05:40:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E56C38FC15 for ; Sun, 22 Jan 2012 05:40:12 +0000 (UTC) Received: by vcbfl17 with SMTP id fl17so1923161vcb.13 for ; Sat, 21 Jan 2012 21:40:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=BRF+V4bSprcPJktwr/zXf/4XLH54kp1aG8ZO0eGIk4o=; b=LqJ27SUeKrkf1wZo5ypLuPgjc8QY4+Ia9H+aG/fltfDJzCnNsZ1ErsDGx81I9ZNFgm dJa5xQqC5lptR3cDUkzxdUHCouxYMnBkR7ofViUvQi4KK56h7sGHZW6FSVL+Cyg5Cikb qzagvIf0TcYmHDytaKiSagNU6eeI0HkGmwVXw= MIME-Version: 1.0 Received: by 10.220.149.212 with SMTP id u20mr2025483vcv.7.1327210812061; Sat, 21 Jan 2012 21:40:12 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Sat, 21 Jan 2012 21:40:12 -0800 (PST) Date: Sat, 21 Jan 2012 21:40:12 -0800 X-Google-Sender-Auth: Uygml6ye8AgX74LgOE2hebI9-8k Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 05:40:13 -0000 Hi, I've noticed some kernel panics in net80211/ath in -HEAD. It in all instances boils down to a now-invalid ieee80211_node - either it's partially allocated/copied, or it's been recently freed. This became increasingly obvious when doing DFS CAC, as the kernel was now changing the channel quite frequently on me whilst simulating/processing radar events. I've since found I can mostly reproduce it in the lab (when surrounded by ridiculous levels of RX intereference traffic, triggering all kinds of events) whilst creating/destroying VAPs. Now that I have debugging code in place (which as a side effect makes it very difficult now to cause a crash, let alone tickle the race condition) it's glaringly obvious what's going on. There's five contexts stuff can occur, at least in the net80211/ath case: * the swi (ie ath_intr(), ath_beacon_proc) * the ath taskqueue; * the net80211 taskqueue; * the ioctl() context, coming up from a userland process; * a callout running in the clock thread. Now, callouts should _hopefully_ be grabbing and releasing locks correctly. We've found a few spots where they weren't (leading to quite silly state races and crashes.) I'm going to ignore the obvious possible problems with multiple concurrent processes doing ioctl()s. l'm simply going to operate on the principle that the multiple-ioctl() path is fine. It seems that -obtaining- references to vap->iv_bss aren't locked. So in (say) ieee80211_sta_join1() the iv_bss node can be dereferenced and freed. If this is going on concurrently with (say) something going on in the net80211 taskqueue (eg a newstate call) then I _think_ it's possible for the ath_newstate() code to get a reference to vap->iv_bss simultaneously with it being freed in ieee80211_sta_join1() (or similar.) So the ath_newstate() code will be assigned a 'ni' that has just been freed. I've seen another crash in the net80211_ht code where it _looks_ like the bss node wasn't entirely setup - bsschan was 0xffff - so the kernel paniced hard there. This likely explains a lot of the "weird stuff" people have been reporting. I also think the bgscan race is related to this - I can't help but wonder if the bgscan callout/event is also coinciding with wpa_supplicant doing stuff, and a race condition ends up leaving the vap w/ the sta power save flag set. I don't yet have a solution to all of this - I just wanted to brain dump what I've seen thus far. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 22 06:27:37 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C0E81065674; Sun, 22 Jan 2012 06:27:37 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 525528FC12; Sun, 22 Jan 2012 06:27:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0M6RbvC093651; Sun, 22 Jan 2012 06:27:37 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0M6RbNd093647; Sun, 22 Jan 2012 06:27:37 GMT (envelope-from linimon) Date: Sun, 22 Jan 2012 06:27:37 GMT Message-Id: <201201220627.q0M6RbNd093647@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/164365: [iwi] iwi0: UP/DOWN in WPA-PSK mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 06:27:37 -0000 Old Synopsis: iwi0: UP/DOWN in WPA-PSK mode New Synopsis: [iwi] iwi0: UP/DOWN in WPA-PSK mode Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 22 06:27:21 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=164365 From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 22 17:00:31 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FB611065777 for ; Sun, 22 Jan 2012 17:00:30 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 534AA8FC12 for ; Sun, 22 Jan 2012 17:00:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0MH0NWU044103 for ; Sun, 22 Jan 2012 17:00:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0MH0Ngm044102; Sun, 22 Jan 2012 17:00:23 GMT (envelope-from gnats) Date: Sun, 22 Jan 2012 17:00:23 GMT Message-Id: <201201221700.q0MH0Ngm044102@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Matthias Apitz Cc: Subject: Re: kern/164365: iwi0: UP/DOWN in WPA-PSK mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz 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, 22 Jan 2012 17:00:31 -0000 The following reply was made to PR kern/164365; it has been noted by GNATS. From: Matthias Apitz To: bug-followup@FreeBSD.org, Matthias Apitz Cc: Subject: Re: kern/164365: iwi0: UP/DOWN in WPA-PSK mode Date: Sun, 22 Jan 2012 17:17:47 +0100 Today I faced another incident and while this UP/DOWN loop occurs I see in the messages of the other laptop connected to the same AP: Jan 22 14:32:20 tinyCurrent wpa_supplicant[1612]: WPA: Group rekeying completed with 00:13:f7:0d:08:48 [GTK=CCMP] Jan 22 14:32:52 tinyCurrent last message repeated 10 times Jan 22 14:34:55 tinyCurrent last message repeated 39 times Jan 22 14:36:16 tinyCurrent last message repeated 19 times Jan 22 14:36:18 tinyCurrent wpa_supplicant[1612]: WPA: AES unwrap failed - could not decrypt EAPOL-Key key data Jan 22 14:36:25 tinyCurrent wpa_supplicant[1612]: WPA: Group rekeying completed with 00:13:f7:0d:08:48 [GTK=CCMP] Jan 22 14:36:40 tinyCurrent last message repeated 4 times In the AP the interval of "Group Key Re_Keying" is disabled; I will change this now to 12 hours .... matthias From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 22 22:26:15 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF2CF106566C; Sun, 22 Jan 2012 22:26:15 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 911D88FC14; Sun, 22 Jan 2012 22:26:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0MMQFUw046002; Sun, 22 Jan 2012 22:26:15 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0MMQF7T045998; Sun, 22 Jan 2012 22:26:15 GMT (envelope-from linimon) Date: Sun, 22 Jan 2012 22:26:15 GMT Message-Id: <201201222226.q0MMQF7T045998@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/164382: [ath] crash when down/deleting a vap - inside ieee80211_input_mimo_all() X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 22:26:15 -0000 Synopsis: [ath] crash when down/deleting a vap - inside ieee80211_input_mimo_all() Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 22 22:26:05 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=164382 From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 23 11:07:17 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7208E106566B for ; Mon, 23 Jan 2012 11:07:17 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5552A8FC08 for ; Mon, 23 Jan 2012 11:07:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0NB7HXb081136 for ; Mon, 23 Jan 2012 11:07:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0NB7G0k081134 for freebsd-wireless@FreeBSD.org; Mon, 23 Jan 2012 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Jan 2012 11:07:16 GMT Message-Id: <201201231107.q0NB7G0k081134@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 Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2012 11:07:17 -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/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 o kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath 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/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/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using 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 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 66 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 03:22:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A253C106566B for ; Wed, 25 Jan 2012 03:22:20 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1EF148FC08 for ; Wed, 25 Jan 2012 03:22:19 +0000 (UTC) Received: by yenq3 with SMTP id q3so2330638yen.13 for ; Tue, 24 Jan 2012 19:22:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:from:to:content-type:mime-version:subject:date :x-mailer; bh=kgG4d0j8jBpFpQ/AldmnIX3hYpmUWCnf4jFiLBHnbMc=; b=ljrfNv+WGPWeqRMcxJMXrKUIsEFVhAQFiJohKmGmW1fyhuQZ40JfbcJuVV0LO9mrOw miiHE/Vn6QcNGnLYdyujJeLa1YcLB2JeEypwESC29r/0eldcq5fRBWkHeEdW9lEsweqF FjMn4CG3XuKJXqnXIPJIUR9XJ3nCk7i5kuZ/c= Received: by 10.236.155.234 with SMTP id j70mr21690681yhk.123.1327460433299; Tue, 24 Jan 2012 19:00:33 -0800 (PST) Received: from triad.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com. [216.15.41.8]) by mx.google.com with ESMTPS id j16sm50561677anm.9.2012.01.24.19.00.31 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 Jan 2012 19:00:32 -0800 (PST) Sender: Justin Hibbits Message-Id: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> From: Justin Hibbits To: freebsd-wireless@freebsd.org Content-Type: multipart/mixed; boundary=Apple-Mail-2--886735953 Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 24 Jan 2012 21:58:18 -0500 X-Mailer: Apple Mail (2.936) Subject: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 03:22:20 -0000 --Apple-Mail-2--886735953 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Can someone test this patch on x86? The patch is needed to work properly on big-endian architectures (tested on ppc with my if_wi macio attachment, to be committed after wider testing). Taken from the OpenBSD driver. - Justin --Apple-Mail-2--886735953 Content-Disposition: attachment; filename=wi.diff Content-Type: application/octet-stream; x-unix-mode=0644; name="wi.diff" Content-Transfer-Encoding: 7bit Index: sys/dev/wi/if_wi.c =================================================================== --- sys/dev/wi/if_wi.c (revision 230483) +++ sys/dev/wi/if_wi.c (working copy) @@ -1898,8 +1898,7 @@ static int wi_read_bap(struct wi_softc *sc, int id, int off, void *buf, int buflen) { - u_int16_t *ptr; - int i, error, cnt; + int error, cnt; if (buflen == 0) return 0; @@ -1908,9 +1907,7 @@ return error; } cnt = (buflen + 1) / 2; - ptr = (u_int16_t *)buf; - for (i = 0; i < cnt; i++) - *ptr++ = CSR_READ_2(sc, WI_DATA0); + CSR_READ_MULTI_STREAM_2(sc, WI_DATA0, (u_int16_t *)buf, cnt); sc->sc_bap_off += cnt * 2; return 0; } @@ -1918,8 +1915,7 @@ static int wi_write_bap(struct wi_softc *sc, int id, int off, void *buf, int buflen) { - u_int16_t *ptr; - int i, error, cnt; + int error, cnt; if (buflen == 0) return 0; @@ -1929,9 +1925,7 @@ return error; } cnt = (buflen + 1) / 2; - ptr = (u_int16_t *)buf; - for (i = 0; i < cnt; i++) - CSR_WRITE_2(sc, WI_DATA0, ptr[i]); + CSR_WRITE_MULTI_STREAM_2(sc, WI_DATA0, (u_int16_t *)buf, cnt); sc->sc_bap_off += cnt * 2; return 0; --Apple-Mail-2--886735953 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit --Apple-Mail-2--886735953-- From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 03:32:50 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18A19106566B for ; Wed, 25 Jan 2012 03:32:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AF0D48FC14 for ; Wed, 25 Jan 2012 03:32:49 +0000 (UTC) Received: by vcbfl17 with SMTP id fl17so4974351vcb.13 for ; Tue, 24 Jan 2012 19:32:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fBBlWuFPyuC8Clbcblff3nU5WTm0gnMaOPaHdILCoQg=; b=OELfuEk0hQP60wUk85grbpYIXn/U87H8Bg7W8mmA9I/RDva3x0+HeFRzozflqUYTP+ tqn1c3SdWIccA3HbW5bSy5CMCaaE3CI7SWjc0tA0aK+bWlTH+yPW8SpF2MbHjL9o2AGS 2G476fGM05C1RF3pe+NG+B58SSGyPHu5uf4hQ= MIME-Version: 1.0 Received: by 10.52.29.75 with SMTP id i11mr7777959vdh.23.1327462368445; Tue, 24 Jan 2012 19:32:48 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.71.241 with HTTP; Tue, 24 Jan 2012 19:32:48 -0800 (PST) In-Reply-To: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> Date: Tue, 24 Jan 2012 19:32:48 -0800 X-Google-Sender-Auth: jt3sjjANCZfZTrj2LvTckgzOWTc Message-ID: From: Adrian Chadd To: Justin Hibbits Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 03:32:50 -0000 You fixed it? :-) Yay! I actually have acquired a couple of if_wi NICs. Can you please create a PR and I'll try to get to it in the next couple weeks? Thanks, Adrian On 24 January 2012 18:58, Justin Hibbits wrote: > Can someone test this patch on x86? The patch is needed to work properly > on big-endian architectures (tested on ppc with my if_wi macio attachment, > to be committed after wider testing). Taken from the OpenBSD driver. > > - Justin > > > > _______________________________________________ > 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 Wed Jan 25 03:46:31 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02E42106566C; Wed, 25 Jan 2012 03:46:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 91C368FC08; Wed, 25 Jan 2012 03:46:30 +0000 (UTC) Received: by vcbfl17 with SMTP id fl17so4983413vcb.13 for ; Tue, 24 Jan 2012 19:46:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=WwjT6FY0UdnX7xm0mMYO283zZ/MU2l/0duZcoI/naQs=; b=pDNR1qysUJbNy0tmdH8rtucJXVDLW8K2hQSV42J30N77WIV2nnTqie7XDPVia2smm/ cM7Nhovxg7lcx3aNVRjj7ei804eRzmFwhIWFn98AXdD0g7jNbHNQsF4dCCHxgmOmh9Bo sMCnjdNWsrZWRMP3xVBLXwhXeb8bkpRjrCTDg= MIME-Version: 1.0 Received: by 10.52.94.73 with SMTP id da9mr7816459vdb.6.1327463189616; Tue, 24 Jan 2012 19:46:29 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.71.241 with HTTP; Tue, 24 Jan 2012 19:46:29 -0800 (PST) In-Reply-To: <43606099-9A1E-4B56-87FB-FB1CD23E9A8F@di-vision.sk> References: <43606099-9A1E-4B56-87FB-FB1CD23E9A8F@di-vision.sk> Date: Tue, 24 Jan 2012 19:46:29 -0800 X-Google-Sender-Auth: kK2TUytS7eHt2HSl-wbTxV0PepM Message-ID: From: Adrian Chadd To: =?UTF-8?Q?Michal_Van=C4=8Do?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ath0: device timeout on 9.0-STABLE X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 03:46:31 -0000 Sure, can you please: * compile with the following options: options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI * compile /usr/src/sys/tools/tools/ath/athstats/ * run athstats -i ath0 and email them to me + freebsd-wireless@freebsd.org Thanks! Adrian On 24 January 2012 04:01, Michal Van=C4=8Do wrote: > Hi there, > > I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad T60 > and I'm not able to use WiFi. Kernel is GENERIC. > > pciconf -lv: > ath0@pci0:3:0:0: class=3D0x028000 card=3D0x0033168c chip=3D0x00241= 68c > rev=3D0x01 hdr=3D0x00 > vendor =3D 'Atheros Communications Inc.' > device =3D 'AR5008 Wireless Network Adapter' > class =3D network > > relevant part of rc.conf: > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"country SK" > ifconfig_wlan0=3D"WPA DHCP" > > and wpa_supplicant.conf: > ctrl_interface=3D/var/run/wpa_supplicant > > network=3D{ > ssid=3D"XXX" > psk=3D"XXX" > } > > dmesg just fills with "ath0: device timeout" messages and wifi just > doesn't work. > > any clue? > > regards > michal > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 07:52:34 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3FB11065672; Wed, 25 Jan 2012 07:52:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 946298FC1E; Wed, 25 Jan 2012 07:52:33 +0000 (UTC) Received: by vcmm1 with SMTP id m1so56581vcm.13 for ; Tue, 24 Jan 2012 23:52:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=TEdCHY0NvY7/K5MBXkG6lEl1zvenSDYE4h7xb2pdobI=; b=SSKlFFkWSH+gqyAi7p05R21HQMzKi29Uh/6mpfE9OoGRgchwRc3PVZteEwUCZnO0Sg HDpIQGdnEA5LstgdCJsLDoCdHAVCQqZcq6XMqsHF5FLSikxAgJHOD9U6fmMK+1rgFAcw aUEsRrESIma7vd0I+50lvFa7TrNb65nt5a9TQ= MIME-Version: 1.0 Received: by 10.52.29.228 with SMTP id n4mr8183345vdh.57.1327477952000; Tue, 24 Jan 2012 23:52:32 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.71.241 with HTTP; Tue, 24 Jan 2012 23:52:31 -0800 (PST) In-Reply-To: References: <43606099-9A1E-4B56-87FB-FB1CD23E9A8F@di-vision.sk> Date: Tue, 24 Jan 2012 23:52:31 -0800 X-Google-Sender-Auth: _agOZIxUeisULXyZOlZv4Liljc0 Message-ID: From: Adrian Chadd To: =?UTF-8?Q?Michal_Van=C4=8Do?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ath0: device timeout on 9.0-STABLE X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 07:52:34 -0000 Hi, The LED stuff may be a bit broken for 9.0. I'll try to fix it up and backport the GPIO and LED fixes. Adrian On 24 January 2012 23:51, Michal Van=C4=8Do wrote: > Adrian, > > believe or not =E2=80=A6 it simply started to work. I just left my thinkp= ad turned > off during the night and now when I booted, almost everything works as > expected: > > # ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > ether 00:19:7e:52:1c:c4 > inet 192.168.0.17 netmask 0xffffff00 broadcast 192.168.0.255 > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g > status: associated > ssid XXX channel 9 (2452 MHz 11g) bssid 10:9a:dd:88:2a:5d > regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i > privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7 > scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 > roam:rate 5 protmode CTS wme burst roaming MANUAL > > # /usr/src/tools/tools/ath/athstats/athstats -i ath0 > 4228 data frames received > 818 data frames transmit > 3 tx frames with an alternate rate > 126 long on-chip tx retries > 29480 mib overflow interrupts > 24M current transmit rate > 730 tx frames with short preamble > 210 rx failed 'cuz of bad CRC > 18 rx failed 'cuz of PHY err > 18 CCK restart > 10 periodic calibrations > -0/+0 TDMA slot adjust (usecs, smoothed) > 37 rssi of last ack > 37 avg recv rssi > -96 rx noise floor > 90 tx frames through raw api > 1 spur immunity level > 1 first step level > 9 ANI increased spur immunity > 2 ANI decrease spur immunity > 103 ANI enabled OFDM weak signal detect > 4 ANI disabled OFDM weak signal detect > 102 ANI disabled CCK weak signal threshold > 3 ANI increased first step level > 7392282 cumulative OFDM phy error count > 34526 cumulative CCK phy error count > 20 ANI forced listen time to zero > 126 missing ACK's > 291 bad FCS > 2928 beacons received > 39 average rssi (beacons only) > 37 average rssi (all rx'd frames) > 37 average rssi (ACKs only) > Antenna profile: > [0] tx 817 rx 65 > [1] tx 0 rx 4163 > > I say "almost" because that small WiFi-LED doesn't blink as it should. Is > there any way to fix this? I see these sysctls: > > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > > but I'm lost with them :) > > regards > michal > > On 25.1.2012, at 4:46, Adrian Chadd wrote: > > > Sure, can you please: > > > > * compile with the following options: > > > > options ATH_DEBUG > > options AH_DEBUG > > options ATH_DIAGAPI > > > > * compile /usr/src/sys/tools/tools/ath/athstats/ > > > > * run athstats -i ath0 and email them to me + > freebsd-wireless@freebsd.org > > > > Thanks! > > > > > > > > Adrian > > > > > > On 24 January 2012 04:01, Michal Van=C4=8Do wrote= : > > Hi there, > > > > I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad T6= 0 > and I'm not able to use WiFi. Kernel is GENERIC. > > > > pciconf -lv: > > ath0@pci0:3:0:0: class=3D0x028000 card=3D0x0033168c chip=3D0x002= 4168c > rev=3D0x01 hdr=3D0x00 > > vendor =3D 'Atheros Communications Inc.' > > device =3D 'AR5008 Wireless Network Adapter' > > class =3D network > > > > relevant part of rc.conf: > > wlans_ath0=3D"wlan0" > > create_args_wlan0=3D"country SK" > > ifconfig_wlan0=3D"WPA DHCP" > > > > and wpa_supplicant.conf: > > ctrl_interface=3D/var/run/wpa_supplicant > > > > network=3D{ > > ssid=3D"XXX" > > psk=3D"XXX" > > } > > > > dmesg just fills with "ath0: device timeout" messages and wifi just > doesn't work. > > > > any clue? > > > > regards > > michal > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g > " > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 08:07:50 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3004106564A; Wed, 25 Jan 2012 08:07:50 +0000 (UTC) (envelope-from mvanco@di-vision.sk) Received: from mail.forza.sk (mail.forza.sk [92.240.234.106]) by mx1.freebsd.org (Postfix) with ESMTP id 707058FC08; Wed, 25 Jan 2012 08:07:48 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.forza.sk (Postfix) with ESMTP id A07A38031C; Wed, 25 Jan 2012 08:51:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=di-vision.sk; h= x-mailer:references:message-id:content-transfer-encoding:date :date:in-reply-to:from:from:content-type:content-type :mime-version:subject:subject:received:received; s=mail; t= 1327477861; bh=cOn2vtXNj7vh/t98VBwsAEmcxGLGMQVQe0eFMSfrwLA=; b=d +U0drXNMTRirPOt5aJ75g9Y7zlXH7EF/uLg2lf3UQJQJTICABTNFJ2GGshoCc4EB JBxYypwFYe0krqp3a7ntcZwLml8ICJMRTB/jkkvWCmSqWwRuDyPfkDHnwIkoboYS 9CWsDMJZS9l/sls7y90uELbNfTJR1ppw3GFfSwpIHU= X-Virus-Scanned: amavisd-new at forza.sk Received: from mail.forza.sk ([127.0.0.1]) by localhost (mail.forza.sk [127.0.0.1]) (amavisd-new, port 10026) with LMTP id Q2iyj1GpmPqT; Wed, 25 Jan 2012 08:51:01 +0100 (CET) Received: from [192.168.0.11] (unknown [178.143.101.64]) by mail.forza.sk (Postfix) with ESMTPSA id 993C480317; Wed, 25 Jan 2012 08:51:00 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=utf-8 From: =?utf-8?Q?Michal_Van=C4=8Do?= In-Reply-To: Date: Wed, 25 Jan 2012 08:51:00 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <43606099-9A1E-4B56-87FB-FB1CD23E9A8F@di-vision.sk> To: Adrian Chadd X-Mailer: Apple Mail (2.1251.1) Cc: freebsd-wireless@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ath0: device timeout on 9.0-STABLE X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 08:07:50 -0000 Adrian, believe or not =E2=80=A6 it simply started to work. I just left my = thinkpad turned off during the night and now when I booted, almost = everything works as expected: # ifconfig wlan0 wlan0: flags=3D8843 metric 0 mtu = 1500 ether 00:19:7e:52:1c:c4 inet 192.168.0.17 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g status: associated ssid XXX channel 9 (2452 MHz 11g) bssid 10:9a:dd:88:2a:5d regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL # /usr/src/tools/tools/ath/athstats/athstats -i ath0 4228 data frames received 818 data frames transmit 3 tx frames with an alternate rate 126 long on-chip tx retries 29480 mib overflow interrupts 24M current transmit rate 730 tx frames with short preamble 210 rx failed 'cuz of bad CRC 18 rx failed 'cuz of PHY err 18 CCK restart 10 periodic calibrations -0/+0 TDMA slot adjust (usecs, smoothed) 37 rssi of last ack 37 avg recv rssi -96 rx noise floor 90 tx frames through raw api 1 spur immunity level 1 first step level 9 ANI increased spur immunity 2 ANI decrease spur immunity 103 ANI enabled OFDM weak signal detect 4 ANI disabled OFDM weak signal detect 102 ANI disabled CCK weak signal threshold 3 ANI increased first step level 7392282 cumulative OFDM phy error count 34526 cumulative CCK phy error count 20 ANI forced listen time to zero 126 missing ACK's 291 bad FCS 2928 beacons received 39 average rssi (beacons only) 37 average rssi (all rx'd frames) 37 average rssi (ACKs only) Antenna profile: [0] tx 817 rx 65 [1] tx 0 rx 4163 I say "almost" because that small WiFi-LED doesn't blink as it should. = Is there any way to fix this? I see these sysctls: dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 but I'm lost with them :) regards michal On 25.1.2012, at 4:46, Adrian Chadd wrote: > Sure, can you please: >=20 > * compile with the following options: >=20 > options ATH_DEBUG > options AH_DEBUG > options ATH_DIAGAPI >=20 > * compile /usr/src/sys/tools/tools/ath/athstats/ >=20 > * run athstats -i ath0 and email them to me + = freebsd-wireless@freebsd.org >=20 > Thanks! >=20 >=20 >=20 > Adrian >=20 >=20 > On 24 January 2012 04:01, Michal Van=C4=8Do = wrote: > Hi there, >=20 > I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad = T60 and I'm not able to use WiFi. Kernel is GENERIC. >=20 > pciconf -lv: > ath0@pci0:3:0:0: class=3D0x028000 card=3D0x0033168c = chip=3D0x0024168c rev=3D0x01 hdr=3D0x00 > vendor =3D 'Atheros Communications Inc.' > device =3D 'AR5008 Wireless Network Adapter' > class =3D network >=20 > relevant part of rc.conf: > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"country SK" > ifconfig_wlan0=3D"WPA DHCP" >=20 > and wpa_supplicant.conf: > ctrl_interface=3D/var/run/wpa_supplicant >=20 > network=3D{ > ssid=3D"XXX" > psk=3D"XXX" > } >=20 > dmesg just fills with "ath0: device timeout" messages and wifi just = doesn't work. >=20 > any clue? >=20 > regards > michal >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 08:13:29 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6339E1065670; Wed, 25 Jan 2012 08:13:29 +0000 (UTC) (envelope-from mvanco@di-vision.sk) Received: from mail.forza.sk (mail.forza.sk [92.240.234.106]) by mx1.freebsd.org (Postfix) with ESMTP id F23048FC08; Wed, 25 Jan 2012 08:13:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.forza.sk (Postfix) with ESMTP id A4B6A8031C; Wed, 25 Jan 2012 09:13:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=di-vision.sk; h= x-mailer:references:message-id:content-transfer-encoding:date :date:in-reply-to:from:from:content-type:content-type :mime-version:subject:subject:received:received; s=mail; t= 1327479207; bh=69zYYVa3NT5euIyJsYT7ZW5tvalVXaiT8L+iGKHfR+4=; b=d ihE1LjswTeZtVcDwNL81E1pYWnowtlmNeVgrG8CcZwU+0Uy1+rQbwW9p9I7ZVaVK j4GxSMmp6Swv9tJbZ/jWwQNLdUiiBGMOM3ZXcXwuF/skU2HTElCWOHZtCiqrrJPH VNKqGRWwRRk2Acs19We2p9hxtGg26etMlVWs4eLXY4= X-Virus-Scanned: amavisd-new at forza.sk Received: from mail.forza.sk ([127.0.0.1]) by localhost (mail.forza.sk [127.0.0.1]) (amavisd-new, port 10026) with LMTP id WDN0KT6Nalgn; Wed, 25 Jan 2012 09:13:27 +0100 (CET) Received: from [192.168.0.11] (unknown [178.143.101.64]) by mail.forza.sk (Postfix) with ESMTPSA id 2028B802F2; Wed, 25 Jan 2012 09:13:26 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=utf-8 From: =?utf-8?Q?Michal_Van=C4=8Do?= In-Reply-To: Date: Wed, 25 Jan 2012 09:13:26 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <2FBABAB8-A464-4A66-9753-20D72C6A7CB0@di-vision.sk> References: <43606099-9A1E-4B56-87FB-FB1CD23E9A8F@di-vision.sk> To: Adrian Chadd X-Mailer: Apple Mail (2.1251.1) Cc: freebsd-wireless@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ath0: device timeout on 9.0-STABLE X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 08:13:29 -0000 Hi, thanks for your response. Though there is one more thing. Is my adapter supposed to work in 5GHz = band? I'm sure it works in windows and linux. Trying to switch to a = different SSID (5GHz one) on the same AP, wlan0 stay unassociated = (status: no carrier): # ifconfig wlan0 wlan0: flags=3D8843 metric 0 mtu = 1500 ether 00:19:7e:52:1c:c4 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "XXX (5 GHz)" channel 36 (5180 MHz 11a) regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 17 bmiss 7 mcastrate 6 = mgmtrate 6 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 12 wme burst roaming MANUAL =09 # /usr/src/tools/tools/ath/athstats/athstats -i ath0 3245 data frames received 1102 data frames transmit 652 mib overflow interrupts 6M current transmit rate 116 rx failed 'cuz of bad CRC 46 rx failed 'cuz of PHY err 46 CCK restart -0/+0 TDMA slot adjust (usecs, smoothed) 23 rssi of last ack 25 avg recv rssi -96 rx noise floor 1102 tx frames through raw api 1 spur immunity level 1 first step level 14 ANI increased spur immunity 889 ANI enabled OFDM weak signal detect 889 ANI disabled CCK weak signal threshold 10 ANI increased first step level 180060 cumulative OFDM phy error count 1709 cumulative CCK phy error count 113 bad FCS 25 average rssi (beacons only) 32 average rssi (all rx'd frames) 23 average rssi (ACKs only) Antenna profile: [0] tx 1056 rx 200 [1] tx 0 rx 3045 With these messages in dmesg: ar5212StopDmaReceive: dma failed to stop in 10ms AR_CR=3D0x00000024 AR_DIAG_SW=3D0x42000020 ar5212StopDmaReceive: dma failed to stop in 10ms AR_CR=3D0x00000024 AR_DIAG_SW=3D0x42000020 Michal On 25.1.2012, at 8:52, Adrian Chadd wrote: > Hi, >=20 > The LED stuff may be a bit broken for 9.0. I'll try to fix it up and = backport the GPIO and LED fixes. >=20 >=20 > Adrian >=20 > On 24 January 2012 23:51, Michal Van=C4=8Do = wrote: > Adrian, >=20 > believe or not =E2=80=A6 it simply started to work. I just left my = thinkpad turned off during the night and now when I booted, almost = everything works as expected: >=20 > # ifconfig wlan0 > wlan0: flags=3D8843 metric 0 = mtu 1500 > ether 00:19:7e:52:1c:c4 > inet 192.168.0.17 netmask 0xffffff00 broadcast 192.168.0.255 > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g > status: associated > ssid XXX channel 9 (2452 MHz 11g) bssid 10:9a:dd:88:2a:5d > regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i > privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7 > scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 > roam:rate 5 protmode CTS wme burst roaming MANUAL >=20 > # /usr/src/tools/tools/ath/athstats/athstats -i ath0 > 4228 data frames received > 818 data frames transmit > 3 tx frames with an alternate rate > 126 long on-chip tx retries > 29480 mib overflow interrupts > 24M current transmit rate > 730 tx frames with short preamble > 210 rx failed 'cuz of bad CRC > 18 rx failed 'cuz of PHY err > 18 CCK restart > 10 periodic calibrations > -0/+0 TDMA slot adjust (usecs, smoothed) > 37 rssi of last ack > 37 avg recv rssi > -96 rx noise floor > 90 tx frames through raw api > 1 spur immunity level > 1 first step level > 9 ANI increased spur immunity > 2 ANI decrease spur immunity > 103 ANI enabled OFDM weak signal detect > 4 ANI disabled OFDM weak signal detect > 102 ANI disabled CCK weak signal threshold > 3 ANI increased first step level > 7392282 cumulative OFDM phy error count > 34526 cumulative CCK phy error count > 20 ANI forced listen time to zero > 126 missing ACK's > 291 bad FCS > 2928 beacons received > 39 average rssi (beacons only) > 37 average rssi (all rx'd frames) > 37 average rssi (ACKs only) > Antenna profile: > [0] tx 817 rx 65 > [1] tx 0 rx 4163 >=20 > I say "almost" because that small WiFi-LED doesn't blink as it should. = Is there any way to fix this? I see these sysctls: >=20 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 >=20 > but I'm lost with them :) >=20 > regards > michal >=20 > On 25.1.2012, at 4:46, Adrian Chadd wrote: >=20 > > Sure, can you please: > > > > * compile with the following options: > > > > options ATH_DEBUG > > options AH_DEBUG > > options ATH_DIAGAPI > > > > * compile /usr/src/sys/tools/tools/ath/athstats/ > > > > * run athstats -i ath0 and email them to me + = freebsd-wireless@freebsd.org > > > > Thanks! > > > > > > > > Adrian > > > > > > On 24 January 2012 04:01, Michal Van=C4=8Do = wrote: > > Hi there, > > > > I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad = T60 and I'm not able to use WiFi. Kernel is GENERIC. > > > > pciconf -lv: > > ath0@pci0:3:0:0: class=3D0x028000 card=3D0x0033168c = chip=3D0x0024168c rev=3D0x01 hdr=3D0x00 > > vendor =3D 'Atheros Communications Inc.' > > device =3D 'AR5008 Wireless Network Adapter' > > class =3D network > > > > relevant part of rc.conf: > > wlans_ath0=3D"wlan0" > > create_args_wlan0=3D"country SK" > > ifconfig_wlan0=3D"WPA DHCP" > > > > and wpa_supplicant.conf: > > ctrl_interface=3D/var/run/wpa_supplicant > > > > network=3D{ > > ssid=3D"XXX" > > psk=3D"XXX" > > } > > > > dmesg just fills with "ath0: device timeout" messages and wifi just = doesn't work. > > > > any clue? > > > > regards > > michal > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" > > >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 10:40:29 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 001A8106564A; Wed, 25 Jan 2012 10:40:28 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id AD10F8FC15; Wed, 25 Jan 2012 10:40:28 +0000 (UTC) Received: from terran.dlink.ua (unknown [192.168.10.90]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 7F2F6C495C; Wed, 25 Jan 2012 12:21:36 +0200 (EET) Date: Wed, 25 Jan 2012 12:21:39 +0200 From: Aleksandr Rybalko To: Justin Hibbits Message-Id: <20120125122139.b0745a11.ray@dlink.ua> In-Reply-To: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 10:40:29 -0000 On Tue, 24 Jan 2012 21:58:18 -0500 Justin Hibbits wrote: >> Can someone test this patch on x86? The patch is needed to work >> properly on big-endian architectures (tested on ppc with my if_wi >> macio attachment, to be committed after wider testing). Taken from >> the OpenBSD driver. >> >> - Justin Cool! Justin, any plans to make it support FW loading? Then I will able to bring up WiFi on my old Palm Tungsten C :) Anyway, thank you! WBW -- Alexandr Rybalko aka Alex RAY From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 10:44:46 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C4381065673 for ; Wed, 25 Jan 2012 10:44:46 +0000 (UTC) (envelope-from milu@dat.pl) Received: from jab.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id 0131F8FC19 for ; Wed, 25 Jan 2012 10:44:45 +0000 (UTC) Received: from jab.dat.pl (jsrv.dat.pl [127.0.0.1]) by jab.dat.pl (Postfix) with ESMTP id 9C253A2 for ; Wed, 25 Jan 2012 11:26:56 +0100 (CET) X-Virus-Scanned: amavisd-new at dat.pl Received: from jab.dat.pl ([127.0.0.1]) by jab.dat.pl (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AC5GqJdtLbkr for ; Wed, 25 Jan 2012 11:26:54 +0100 (CET) Received: from snifi.localnet (unknown [212.69.68.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jab.dat.pl (Postfix) with ESMTPSA id D02A593 for ; Wed, 25 Jan 2012 11:26:54 +0100 (CET) From: Maciej Milewski To: freebsd-wireless@freebsd.org Date: Wed, 25 Jan 2012 11:27:06 +0100 Message-ID: <1952213.pSGpNs2iPC@snifi> User-Agent: KMail/4.7.4 (Linux/3.2.1-2-ARCH; KDE/4.7.4; x86_64; ; ) In-Reply-To: <2FBABAB8-A464-4A66-9753-20D72C6A7CB0@di-vision.sk> References: <43606099-9A1E-4B56-87FB-FB1CD23E9A8F@di-vision.sk> <2FBABAB8-A464-4A66-9753-20D72C6A7CB0@di-vision.sk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Subject: Re: ath0: device timeout on 9.0-STABLE X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 10:44:46 -0000 Dnia =C5=9Broda, 25 stycznia 2012 09:13:26 Michal Van=C4=8Do pisze: > Hi, >=20 > thanks for your response. >=20 > Though there is one more thing. Is my adapter supposed to work in 5GH= z band? > I'm sure it works in windows and linux. Trying to switch to a differe= nt > SSID (5GHz one) on the same AP, wlan0 stay unassociated (status: no > carrier): >=20 > # ifconfig wlan0 > wlan0: flags=3D8843 metric 0 = mtu 1500 > =09ether 00:19:7e:52:1c:c4 > =09nd6 options=3D29 > =09media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > =09status: no carrier > =09ssid "XXX (5 GHz)" channel 36 (5180 MHz 11a) > =09regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i > =09privacy ON deftxkey UNDEF txpower 17 bmiss 7 mcastrate 6 mgmtrate = 6 > =09scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 > =09roam:rate 12 wme burst roaming MANUAL >=20 It allowed you to set the 5GHz channel so it supports that if it wasn't= be=20 supporting it would complain: #ifconfig wlan0 mode 11a ifconfig: SIOCSIFMEDIA (media): Device not configured try if ifconfig wlan0 scan or ifconfig wlan0 list scan shows you some=20= networks. --=20 Pozdrawiam, Maciej Milewski From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 11:41:02 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB5F31065675 for ; Wed, 25 Jan 2012 11:41:01 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 81A4E8FC14 for ; Wed, 25 Jan 2012 11:41:01 +0000 (UTC) Received: by yenq3 with SMTP id q3so2462713yen.13 for ; Wed, 25 Jan 2012 03:41:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bBkInftIFuNYVjqB8Er4uyBFccwVymNZPLjqyAqnanA=; b=f82NvTzJHYiGDu45znJJKTdIjimLlOC6hAZRiYDk/pLEQJOqRkW07yL2ia3Errh1Oh ycGhjURFx+Kg58+cT++3tsCk6FeNbPKQITbIH0ut0MkFeIRLXag5XIfp6hGoVX9Hod5s MmHT5Q1Z8pYpD7eOZDdNr8K1CyEs2fmTPG1Vo= MIME-Version: 1.0 Received: by 10.236.155.226 with SMTP id j62mr23840582yhk.49.1327491660806; Wed, 25 Jan 2012 03:41:00 -0800 (PST) Sender: chmeeedalf@gmail.com Received: by 10.147.125.2 with HTTP; Wed, 25 Jan 2012 03:41:00 -0800 (PST) In-Reply-To: References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> Date: Wed, 25 Jan 2012 06:41:00 -0500 X-Google-Sender-Auth: gdrcUSmKigS2zGHk1QcsxpRIYVA Message-ID: From: Justin Hibbits To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 11:41:02 -0000 This was part of the patch I posted back in October, I haven't tested my Airport card in a couple months, just going through patches I've made so I can make some more commits. When I first posted, you had mentioned needing to regression test on i386 before committing, I'm just pushing it along now :) I'll file a PR later today. - Justin On Tue, Jan 24, 2012 at 10:32 PM, Adrian Chadd wrote: > You fixed it? :-) > > Yay! > > I actually have acquired a couple of if_wi NICs. Can you please create a > PR and I'll try to get to it in the next couple weeks? > > Thanks, > > > Adrian > > > On 24 January 2012 18:58, Justin Hibbits wrote: > >> Can someone test this patch on x86? The patch is needed to work properly >> on big-endian architectures (tested on ppc with my if_wi macio attachment, >> to be committed after wider testing). Taken from the OpenBSD driver. >> >> - Justin >> >> >> >> _______________________________________________ >> 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 Wed Jan 25 11:42:29 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E403F106564A for ; Wed, 25 Jan 2012 11:42:29 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9E76D8FC13 for ; Wed, 25 Jan 2012 11:42:29 +0000 (UTC) Received: by yenq3 with SMTP id q3so2463225yen.13 for ; Wed, 25 Jan 2012 03:42:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=5oS113O/qHUEZ9OiOP1eJZYR97A+Ukw2nTbi08HMj1I=; b=DKwS35sBtdD9wwdOLpwiFswdzEKFk4Ujic4lEVfzujNF/VEcfK5FyUBwKSxSqu2DhZ WFs+iQUvJyG0Rplup7gHEexGJv4w2Is5pKfLpFnzJ9oBjdGUkhfo9AAfhA3JJOlD26AX 61zMHY5NoxxLpYJ8nYaXV9Dwfi1oRfKpDmy9E= MIME-Version: 1.0 Received: by 10.236.173.40 with SMTP id u28mr23886308yhl.15.1327491749128; Wed, 25 Jan 2012 03:42:29 -0800 (PST) Sender: chmeeedalf@gmail.com Received: by 10.147.125.2 with HTTP; Wed, 25 Jan 2012 03:42:29 -0800 (PST) In-Reply-To: <20120125122139.b0745a11.ray@dlink.ua> References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> <20120125122139.b0745a11.ray@dlink.ua> Date: Wed, 25 Jan 2012 06:42:29 -0500 X-Google-Sender-Auth: WCvyci2A_fzsUekGdVKoVsUAvFM Message-ID: From: Justin Hibbits To: Aleksandr Rybalko Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 11:42:30 -0000 On Wed, Jan 25, 2012 at 5:21 AM, Aleksandr Rybalko wrote: > On Tue, 24 Jan 2012 21:58:18 -0500 > Justin Hibbits wrote: > > >> Can someone test this patch on x86? The patch is needed to work > >> properly on big-endian architectures (tested on ppc with my if_wi > >> macio attachment, to be committed after wider testing). Taken from > >> the OpenBSD driver. > >> > >> - Justin > > Cool! > > Justin, any plans to make it support FW loading? Then I will able to > bring up WiFi on my old Palm Tungsten C :) > > Anyway, thank you! > > WBW I don't know anything about firmware loading, I'm just trying to get my PowerBook on wifi :) - Justin From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 14:47:15 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15991106566C; Wed, 25 Jan 2012 14:47:15 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id C61C68FC15; Wed, 25 Jan 2012 14:47:14 +0000 (UTC) Received: from terran.dlink.ua (unknown [192.168.10.90]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 9D48CC495B; Wed, 25 Jan 2012 16:47:13 +0200 (EET) Date: Wed, 25 Jan 2012 16:47:17 +0200 From: Aleksandr Rybalko To: Justin Hibbits Message-Id: <20120125164717.fa1d132a.ray@dlink.ua> In-Reply-To: References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> <20120125122139.b0745a11.ray@dlink.ua> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 14:47:15 -0000 On Wed, 25 Jan 2012 06:42:29 -0500 Justin Hibbits wrote: >> On Wed, Jan 25, 2012 at 5:21 AM, Aleksandr Rybalko >> wrote: >> >> > On Tue, 24 Jan 2012 21:58:18 -0500 >> > Justin Hibbits wrote: >> > >> > >> Can someone test this patch on x86? The patch is needed to work >> > >> properly on big-endian architectures (tested on ppc with my >> > >> if_wi macio attachment, to be committed after wider testing). >> > >> Taken from the OpenBSD driver. >> > >> >> > >> - Justin >> > >> > Cool! >> > >> > Justin, any plans to make it support FW loading? Then I will able >> > to bring up WiFi on my old Palm Tungsten C :) >> > >> > Anyway, thank you! >> > >> > WBW >> >> >> I don't know anything about firmware loading, I'm just trying to get >> my PowerBook on wifi :) Will explain a bit (hope nobody beat me) : embedded devices like Palm TC and some Asus have if_wi, but w/o firmware flash, so driver need to load FW before enable device. Do you have doc for it? because linux code with FW loading to much inconsistent with my head :) >> >> - Justin >> _______________________________________________ >> 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" -- Рыбалко Александр Консультант D-Link Украина From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 14:56:03 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE95B106566B for ; Wed, 25 Jan 2012 14:56:03 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm21-vm2.bullet.mail.ne1.yahoo.com (nm21-vm2.bullet.mail.ne1.yahoo.com [98.138.91.209]) by mx1.freebsd.org (Postfix) with SMTP id 72EFC8FC12 for ; Wed, 25 Jan 2012 14:56:03 +0000 (UTC) Received: from [98.138.90.50] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 25 Jan 2012 14:43:33 -0000 Received: from [98.138.226.61] by tm3.bullet.mail.ne1.yahoo.com with NNFMP; 25 Jan 2012 14:43:33 -0000 Received: from [127.0.0.1] by smtp212.mail.ne1.yahoo.com with NNFMP; 25 Jan 2012 14:43:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1327502613; bh=yySdmhTmBTzxWOMDUHH37QqkbPPjrSyLca4668ITP8k=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:Date:Message-ID:Subject:From:To:Content-Type:Content-Transfer-Encoding; b=0nVUDG/j03xx4LePBv2g8vA9UsfhocJ+5BLxxj1QVQfciCcNJv7r8x1Sa0xhOYYCxu8CP/ybNg1BpmZ06pjkbqL41w9MnABW1P1pqLRUdH9j4M57BEVSig5oFE5X0w4lt9/ZsYwRNbPMAUO/u/R/cenwLMcKQLhM3q4LKOCVAjg= X-Yahoo-Newman-Id: 769013.82562.bm@smtp212.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: CCufYGUVM1nO0r_XvI7pZ7dWnCYSV5tBRViHSf01tPwLl3K PM8eZukMIqyeuweBS4GHyMr42mKxEE3Em0nEqqq3344cDOF8VrCpRr0fIw9X XbI..2cqLuUOFaDMYLn2U_lJaOUjjbZZwYnpZ7_psLUSD0esPqU6hInuxR4u UnavG2IMWkxeIcSIsRBkPxEGsXqiyUnj5dMIV3E9xfiUNHZzeCVC0XoTPoII vR1lK9lyAlWux7DcMAU4XBnF5Re1flnPSTR7vUaiywBbdmT9Mt50V0kf1nkN xKdwrCgZ4wHK_zuLK5NnnpbwzYnzvHS3NK2kcC0Zrka.iLiL4MoWmSi1gKKH xYcozeUbMqG2W6oFXgqm8nnggcsV7mpzHgAmyqddw6pq9lDsmeBEzlY3.kZN Yitg_FI7XT0vbUlrZ0MddqUMlkjIUuQ4_n4jImWH7bmjN7SE- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-iy0-f182.google.com (moonlightakkiy@209.85.210.182 with plain) by smtp212.mail.ne1.yahoo.com with SMTP; 25 Jan 2012 06:43:33 -0800 PST Received: by iaeo4 with SMTP id o4so1840680iae.13 for ; Wed, 25 Jan 2012 06:43:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.131.136 with SMTP id z8mr15667909ics.5.1327502613199; Wed, 25 Jan 2012 06:43:33 -0800 (PST) Received: by 10.231.37.2 with HTTP; Wed, 25 Jan 2012 06:43:33 -0800 (PST) Date: Wed, 25 Jan 2012 07:43:33 -0700 Message-ID: From: PseudoCylon To: Adrian Chadd , freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 14:56:03 -0000 > ------------------------------ > > Message: 14 > Date: Sat, 21 Jan 2012 21:40:12 -0800 > From: Adrian Chadd > Subject: net80211 race conditions seen in -HEAD > To: freebsd-wireless@freebsd.org > Message-ID: > =A0 =A0 =A0 =A0 > Content-Type: text/plain; charset=3DISO-8859-1 > > Hi, > > I've noticed some kernel panics in net80211/ath in -HEAD. It in all > instances boils down to a now-invalid ieee80211_node - either it's > partially allocated/copied, or it's been recently freed. > > > > This became increasingly obvious when doing DFS CAC, as the kernel was no= w > changing the channel quite frequently on me whilst simulating/processing > radar events. I've since found I can mostly reproduce it in the lab (when > surrounded by ridiculous levels of RX intereference traffic, triggering a= ll > kinds of events) whilst creating/destroying VAPs. > > Now that I have debugging code in place (which as a side effect makes it > very difficult now to cause a crash, let alone tickle the race condition) > it's glaringly obvious what's going on. > > There's five contexts stuff can occur, at least in the net80211/ath case: > > * the swi (ie ath_intr(), ath_beacon_proc) > * the ath taskqueue; > * the net80211 taskqueue; > * the ioctl() context, coming up from a userland process; > * a callout running in the clock thread. > > Now, callouts should _hopefully_ be grabbing and releasing locks correctl= y. > We've found a few spots where they weren't (leading to quite silly state > races and crashes.) > > I'm going to ignore the obvious possible problems with multiple concurren= t > processes doing ioctl()s. l'm simply going to operate on the principle th= at > the multiple-ioctl() path is fine. > > It seems that -obtaining- references to vap->iv_bss aren't locked. So in > (say) ieee80211_sta_join1() the iv_bss node can be dereferenced and freed= . > If this is going on concurrently with (say) something going on in the > net80211 taskqueue (eg a newstate call) then I _think_ it's possible for > the ath_newstate() code to get a reference to vap->iv_bss simultaneously > with it being freed in ieee80211_sta_join1() (or similar.) So the > ath_newstate() code will be assigned a 'ni' that has just been freed. > > I've seen another crash in the net80211_ht code where it _looks_ like the > bss node wasn't entirely setup - bsschan was 0xffff - so the kernel panic= ed > hard there. > > This likely explains a lot of the "weird stuff" people have been reportin= g. > I also think the bgscan race is related to this - I can't help but wonder > if the bgscan callout/event is also coinciding with wpa_supplicant doing > stuff, and a race condition ends up leaving the vap w/ the sta power save > flag set. > > I don't yet have a solution to all of this - I just wanted to brain dump > what I've seen thus far. > Here is my brain dump. While ago usb wifi drivers had the slimier issue (race in 80211 stack). It's worth checking this rev. http://svnweb.freebsd.org/base?view=3Drevision&revision=3D212127 AK From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 21:47:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE4CC106566C for ; Wed, 25 Jan 2012 21:47:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 989A68FC19 for ; Wed, 25 Jan 2012 21:47:09 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so2750297vbb.13 for ; Wed, 25 Jan 2012 13:47:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ARYmlZuBViFFiVRAYZqK0SQTgo8trRO59FQvAqcAfWc=; b=Kk6mPNtFCnshcBpVWpwjiGCPWhkGlEo7M2gQHTvxuiMxLIhu1X5fdbru3TJ0HnOq+C bHIoK5ftUFPXr2lTBDWlhcAURBjJYkRQsUT6bDkJqNSJ7XeVLR0H40MDboV+Rwf/SdHD +6YV7XMVWLCcy+/OB3zBljQx5kbyZSsfi2F1M= MIME-Version: 1.0 Received: by 10.52.94.73 with SMTP id da9mr10211598vdb.6.1327528028869; Wed, 25 Jan 2012 13:47:08 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.71.241 with HTTP; Wed, 25 Jan 2012 13:47:08 -0800 (PST) In-Reply-To: References: Date: Wed, 25 Jan 2012 13:47:08 -0800 X-Google-Sender-Auth: VH7Gz4IM9R4qzqUhduPgQ3fCHTk Message-ID: From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 21:47:09 -0000 On 25 January 2012 06:43, PseudoCylon wrote: > Here is my brain dump. > > While ago usb wifi drivers had the slimier issue (race in 80211 > stack). It's worth checking this rev. > http://svnweb.freebsd.org/base?view=revision&revision=212127 > > AK > Hi, right, but that isn't at all completely _atomic_. It's quite possible that the underlying node gets ripped out by thread B whilst the assignment is happening in thread A. Once you have that reference you're fine, but I can't see where the guarantee is that vap->iv_bss is actually going to stay referenced for the lifecycle of the call _to_ ieee80211_ref_node() (rather than the atomic increment itself.) The fundamental trouble there is that the assignment can and does occur whilst the refcount i Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 25 21:47:38 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FCD11065708 for ; Wed, 25 Jan 2012 21:47:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 39CC68FC0A for ; Wed, 25 Jan 2012 21:47:38 +0000 (UTC) Received: by mail-vw0-f54.google.com with SMTP id fa15so2750297vbb.13 for ; Wed, 25 Jan 2012 13:47:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=g7SCyQV7OqjT7XB7XLdPkXH1En9ZBTme7PZkdOSDzJ8=; b=RueHxFraakuc8mw8YjHsWot90zue1l43LRAmU8dhLOjS8h8GuBja7kwzbo0rP+LnjI sLQZ6hMiEO+EoLQpcFvAITX4JCaXjCfNrQBb6p4dEuEj/lJYjGfbBCtrqYSy2rIC7jfw ttKvjeUCC2A5A2XHrL7r0P5l8btLlg8WLf8Y4= MIME-Version: 1.0 Received: by 10.52.94.73 with SMTP id da9mr10212181vdb.6.1327528058053; Wed, 25 Jan 2012 13:47:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.71.241 with HTTP; Wed, 25 Jan 2012 13:47:38 -0800 (PST) In-Reply-To: References: Date: Wed, 25 Jan 2012 13:47:38 -0800 X-Google-Sender-Auth: 5cky8dAInPxCDq1FXQp4TZASgHA Message-ID: From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 21:47:38 -0000 .. whilst the refcount is 1, so ieee80211_ref_node() may not increment the counter before it's freed by another thread. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 01:56:51 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 677EF106564A for ; Thu, 26 Jan 2012 01:56:51 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 216638FC16 for ; Thu, 26 Jan 2012 01:56:50 +0000 (UTC) Received: by yenq3 with SMTP id q3so39626yen.13 for ; Wed, 25 Jan 2012 17:56:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; bh=Yen79+9ziO3z6U8Zi1P03RSF1uMaTM/RpT6hAioHIrs=; b=Y8Fb6Abm2xW8w5xyoy8gVIJ/ekkzk+ZZ5LGk3VsVO014u9JIwfujjiPwFIP2bw36Be D46+Xa1P8kkhmjCQOULYTkbdGmB2CpXrpCGbmzG6i2FUjDmpuykFkRXwJ5KlOvIAAgRk 3ekZF2P/x/eT/PvWn5D35O/eVLEUFyD4G6nSA= Received: by 10.236.201.201 with SMTP id b49mr148604yho.18.1327543010412; Wed, 25 Jan 2012 17:56:50 -0800 (PST) Received: from triad.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com. [216.15.41.8]) by mx.google.com with ESMTPS id 9sm6436240ans.15.2012.01.25.17.56.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Jan 2012 17:56:49 -0800 (PST) Sender: Justin Hibbits Message-Id: <94FD5531-98B4-40A9-8599-676673F88560@freebsd.org> From: Justin Hibbits To: Aleksandr Rybalko In-Reply-To: <20120125164717.fa1d132a.ray@dlink.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Wed, 25 Jan 2012 20:54:33 -0500 References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> <20120125122139.b0745a11.ray@dlink.ua> <20120125164717.fa1d132a.ray@dlink.ua> X-Mailer: Apple Mail (2.936) Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 01:56:51 -0000 On Jan 25, 2012, at 9:47 AM, Aleksandr Rybalko wrote: > On Wed, 25 Jan 2012 06:42:29 -0500 > Justin Hibbits wrote: > >>> On Wed, Jan 25, 2012 at 5:21 AM, Aleksandr Rybalko >>> wrote: >>> >>>> On Tue, 24 Jan 2012 21:58:18 -0500 >>>> Justin Hibbits wrote: >>>> >>>>>> Can someone test this patch on x86? The patch is needed to work >>>>>> properly on big-endian architectures (tested on ppc with my >>>>>> if_wi macio attachment, to be committed after wider testing). >>>>>> Taken from the OpenBSD driver. >>>>>> >>>>>> - Justin >>>> >>>> Cool! >>>> >>>> Justin, any plans to make it support FW loading? Then I will able >>>> to bring up WiFi on my old Palm Tungsten C :) >>>> >>>> Anyway, thank you! >>>> >>>> WBW >>> >>> >>> I don't know anything about firmware loading, I'm just trying to get >>> my PowerBook on wifi :) > > Will explain a bit (hope nobody beat me) : > embedded devices like Palm TC and some Asus have if_wi, but w/o > firmware flash, so driver need to load FW before enable device. > > Do you have doc for it? because linux code with FW loading to much > inconsistent with my head :) Nope, sorry. I don't even know what I'm doing, really :) Adrian knows a lot more, he helped me with what I've done. You can look at firmware(4) for help with loading firmware, that's all I can say. - Justin From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 02:22:51 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FF1E106564A; Thu, 26 Jan 2012 02:22:51 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 565E38FC12; Thu, 26 Jan 2012 02:22:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0Q2Mpi7011176; Thu, 26 Jan 2012 02:22:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0Q2MpID011172; Thu, 26 Jan 2012 02:22:51 GMT (envelope-from linimon) Date: Thu, 26 Jan 2012 02:22:51 GMT Message-Id: <201201260222.q0Q2MpID011172@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/164499: [wi] [patch] if_wi needs fix for big endian architectures. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 02:22:51 -0000 Old Synopsis: if_wi needs fix for big endian architectures. New Synopsis: [wi] [patch] if_wi needs fix for big endian architectures. Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 26 02:22:27 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=164499 From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 02:34:48 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F333106564A; Thu, 26 Jan 2012 02:34:48 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 371078FC14; Thu, 26 Jan 2012 02:34:47 +0000 (UTC) Received: by yhfs35 with SMTP id s35so49840yhf.13 for ; Wed, 25 Jan 2012 18:34:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:cc:message-id:from:to:in-reply-to:content-type:mime-version :subject:date:references:x-mailer; bh=bpiZ4hgehigCv+a2H+FwwOC/4ccc63pCv5Li8NQuFh0=; b=V21y6lHYAA7FY7qmKAo8rIz8O0aj3KPz+FrxmtuOtwfaezK3VqLetbJI0rtxWsXNf9 t+jMb28wsz3GZrOVQS/dfyFI8HpofGMUC2uqO9jPsIvRaN7keY2ygcAA6ibnnwgYpR+5 M7H147vFUjNMTE9cb0xPAxYRFYNdmQYDwCDMY= Received: by 10.236.139.130 with SMTP id c2mr160322yhj.103.1327545287536; Wed, 25 Jan 2012 18:34:47 -0800 (PST) Received: from triad.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com. [216.15.41.8]) by mx.google.com with ESMTPS id v7sm3505232yhi.1.2012.01.25.18.34.46 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Jan 2012 18:34:46 -0800 (PST) Sender: Justin Hibbits Message-Id: From: Justin Hibbits To: Adrian Chadd In-Reply-To: Mime-Version: 1.0 (Apple Message framework v936) Date: Wed, 25 Jan 2012 21:32:31 -0500 References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> X-Mailer: Apple Mail (2.936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 02:34:48 -0000 PR filed as kern/164499 - Justin On Jan 24, 2012, at 10:32 PM, Adrian Chadd wrote: > You fixed it? :-) > > Yay! > > I actually have acquired a couple of if_wi NICs. Can you please > create a PR and I'll try to get to it in the next couple weeks? > > Thanks, > > > Adrian > > > On 24 January 2012 18:58, Justin Hibbits wrote: > Can someone test this patch on x86? The patch is needed to work > properly on big-endian architectures (tested on ppc with my if_wi > macio attachment, to be committed after wider testing). Taken from > the OpenBSD driver. > > - Justin > > > > _______________________________________________ > 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 Thu Jan 26 05:25:44 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D2E0106564A; Thu, 26 Jan 2012 05:25:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C9B9E8FC08; Thu, 26 Jan 2012 05:25:43 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so253569vbb.13 for ; Wed, 25 Jan 2012 21:25:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6dbfL2y3OqTAW4Quxf1UmQqQDoPMcOevbTTdTV9sQ5M=; b=w/gdv1y0sclrZzD8PsSp0uw3kkQr9vfwddwOgir1lnjWhN8wRIA5R4ZeNGZweCoP3S 8gs1ZVTUHuo8HdfOM2HkCInXrMYURgbDc7vrNEidS6mfLKNlD0FdhwI3K/iu4kMKMZGB hRnGiQCC7XkUB8l+3wS3CJ/6Cm7XQdvLo6jps= MIME-Version: 1.0 Received: by 10.52.29.75 with SMTP id i11mr284206vdh.23.1327555543174; Wed, 25 Jan 2012 21:25:43 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.110.104 with HTTP; Wed, 25 Jan 2012 21:25:43 -0800 (PST) In-Reply-To: <94FD5531-98B4-40A9-8599-676673F88560@freebsd.org> References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> <20120125122139.b0745a11.ray@dlink.ua> <20120125164717.fa1d132a.ray@dlink.ua> <94FD5531-98B4-40A9-8599-676673F88560@freebsd.org> Date: Wed, 25 Jan 2012 21:25:43 -0800 X-Google-Sender-Auth: 6im39LBi45iRinNSa3MXl6AH-hg Message-ID: From: Adrian Chadd To: Justin Hibbits Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Aleksandr Rybalko , freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 05:25:44 -0000 Hi, It turns out that my lucent gold wavelan cards have very early firmware on them, not supported by if_wi. I'm not sure why. .. guess if I'm going to be any help, someone's going to have to help me figure out whether I can actually load newer firmware onto this card. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 07:22:53 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0009106566C for ; Thu, 26 Jan 2012 07:22:52 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm28.bullet.mail.sp2.yahoo.com (nm28.bullet.mail.sp2.yahoo.com [98.139.91.98]) by mx1.freebsd.org (Postfix) with SMTP id AC4798FC18 for ; Thu, 26 Jan 2012 07:22:52 +0000 (UTC) Received: from [98.139.91.67] by nm28.bullet.mail.sp2.yahoo.com with NNFMP; 26 Jan 2012 07:09:27 -0000 Received: from [208.71.42.202] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 26 Jan 2012 07:08:27 -0000 Received: from [127.0.0.1] by smtp213.mail.gq1.yahoo.com with NNFMP; 26 Jan 2012 07:08:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1327561707; bh=W6T+NrF05Ar9mRDylkk5HHTDiLaXZPMes32lNgzoYJg=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=dyDTI7nAJvVWnOoyu31VJJaaHAtaBlckYlR4CwHUOj4abx1DbFKkGvHByx0s3cKlm885L95OQyeGSWp+lgkgZsG2zN37Iy+V9Yi3GnmrUYoFYn4VqEA6h2X3cUa7azAUqpyBgvQ1Nf6bs56eRn9V+Kxot3p6+sFgAsc7xT0w4Fc= X-Yahoo-Newman-Id: 177578.60162.bm@smtp213.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: le2ePckVM1nAQA5OZj83l2cgXywLsE6EEvjU3YYsB9Gv1lT Mq76BWyZ.HC4bfp3qEq5G.OqKscKoXer9rNhQ0evwrl9C7yMFvSGre48yzid IKU7J8.DVBXIsnmLLz7oCwDSPJ6McEzR9_fwoLMFu5wMAiqfcHsiPTaT8xkb yqlwotzEv1lZOYzDUNZ_Bwa2wEBkXXL82sVK7NTAJflL8y47OZwOd0VMPele ZGOZCy_CI0gs8aFuR0szCnTMvAXZmWKpYwtLXb8IAZdLezbKkJ7cHgOf.kG1 .ah.g7_Dq3Rsi.s6FMKDQEaz8RrRugumszTBfg8Xo0i8PLOvR2RD.nrE9nNg wnC.zLNbtm8NH8ZJcyT_aZ.3IKkLn.0bpVxPMXBkRXFwptUw.uQXBkfP3Cty gWhNciHHXC1iVKL0a3eCMu53uLa1sZc3XGF6KuPWldu8DIO61PFx_U1_M3Es ENDUEuhS_BIkulwcN2OKzBJDcp.yBGt0F6WWa73Dixdn_Df9tbcXrQgCORWX p2Dj1bwFa7yDZnFZQg3W07vyrtQHMoL0WzD_CuA7BPqK46N9.GcMf1QrkqGU z57bmeos- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-iy0-f182.google.com (moonlightakkiy@209.85.210.182 with plain) by smtp213.mail.gq1.yahoo.com with SMTP; 25 Jan 2012 23:08:26 -0800 PST Received: by iaeo4 with SMTP id o4so650092iae.13 for ; Wed, 25 Jan 2012 23:08:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.153.234 with SMTP id vj10mr903192igb.16.1327561706372; Wed, 25 Jan 2012 23:08:26 -0800 (PST) Received: by 10.231.37.2 with HTTP; Wed, 25 Jan 2012 23:08:26 -0800 (PST) In-Reply-To: References: Date: Thu, 26 Jan 2012 00:08:26 -0700 Message-ID: From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 07:22:53 -0000 On Wed, Jan 25, 2012 at 2:47 PM, Adrian Chadd wrote: > .. whilst the refcount is 1, so ieee80211_ref_node() may not increment the > counter before it's freed by another thread. > Further browsing the codes, I'd say here is the point of no return. http://fxr.watson.org/fxr/source/net80211/ieee80211_freebsd.c?im=bigexcerpts#L310 After atomic_cmpset_int() returned 1, increment ref cont won't stop freeing node no matter how we handle the ref count. It will continue freeing node, anyway. If we cannot stop freeing node, we should stop the thread using the node once freeing node process has started. How about make ieee80211_ref_node() return NULL when ni_refcnt == 0 and caller of ieee80211_ref_node() to exit? ieee80211_ref_node(ni) { #ifdef NO_LOCK /* * This loop simulates atomic_cmp_and_add() as commented at http://fxr.watson.org/fxr/source/net80211/ieee80211_freebsd.c?im=bigexcerpts#L308 * The current code work most of the time, so this will loop very rarely */ for (;;) { if ((cnt = atomic_load_int(&ni_refcnt)) == 0) return (NULL); /* caller should abort process */ if (atomic_cmp_set(&ni_refcnt, cnt, cnt + 1)) return (ni); } #else /* you may receive complimentary barrage of LOR */ LOCK(); if (ni_refcnt == 0) ni = NULL; else ni_refcnt++: UNLOCK(); return (ni); #endif } ieee80211_node_dectestref(ni) { #ifdef NO_LOCK for (;;) { if ((cnt = atomic_load_int(&ni_refcnt)) == 0) return (1); /* free node */ if (atomic_cmp_set(&ni_refcnt, cnt, cnt -1)) return (cnt <= 1); /* cnt - 1 == 0 free node */ } #else LOCK(); cnt = ni_refcnt > 0 ? cnt - 1 : 0; UNLOCK(); return (cnt); #endif } AK From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 09:41:15 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C0B5106564A; Thu, 26 Jan 2012 09:41:15 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 0E9EE8FC15; Thu, 26 Jan 2012 09:41:14 +0000 (UTC) Received: from terran.dlink.ua (unknown [192.168.10.90]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 0BA98C492D; Thu, 26 Jan 2012 11:41:13 +0200 (EET) Date: Thu, 26 Jan 2012 11:41:20 +0200 From: Aleksandr Rybalko To: Adrian Chadd Message-Id: <20120126114120.1903425c.ray@dlink.ua> In-Reply-To: References: <81F29D74-1AA1-4DA8-81A1-951DDFB22F2B@freebsd.org> <20120125122139.b0745a11.ray@dlink.ua> <20120125164717.fa1d132a.ray@dlink.ua> <94FD5531-98B4-40A9-8599-676673F88560@freebsd.org> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Justin Hibbits , freebsd-wireless@freebsd.org Subject: Re: if_wi patch X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 09:41:15 -0000 On Wed, 25 Jan 2012 21:25:43 -0800 Adrian Chadd wrote: >> Hi, >> >> It turns out that my lucent gold wavelan cards have very early >> firmware on them, not supported by if_wi. >> >> I'm not sure why. >> >> .. guess if I'm going to be any help, someone's going to have to >> help me figure out whether I can actually load newer firmware onto >> this card. >> Or it is firmware-less item, like my :) >> >> >> Adrian -- Alexandr Rybalko aka Alex RAY From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 16:35:23 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15E9A106564A; Thu, 26 Jan 2012 16:35:23 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 62D8C8FC14; Thu, 26 Jan 2012 16:35:21 +0000 (UTC) Received: by lahj13 with SMTP id j13so597786lah.13 for ; Thu, 26 Jan 2012 08:35:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.38.227 with SMTP id j3mr759957lbk.88.1327595720933; Thu, 26 Jan 2012 08:35:20 -0800 (PST) Received: by 10.152.3.161 with HTTP; Thu, 26 Jan 2012 08:35:20 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Thu, 26 Jan 2012 17:35:20 +0100 Message-ID: From: Bernhard Schmidt To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: PseudoCylon , freebsd-wireless@freebsd.org Subject: Re: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 16:35:23 -0000 On Wed, Jan 25, 2012 at 22:47, Adrian Chadd wrote: > .. whilst the refcount is 1, so ieee80211_ref_node() may not increment the > counter before it's freed by another thread. You know, that is an inline function, what "lifetime" are we taking about? iv_bss has other issues, being overwritten while some task is using it no matter how high the refcount is is once of those. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 26 18:56:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA7991065677 for ; Thu, 26 Jan 2012 18:56:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5EDE78FC18 for ; Thu, 26 Jan 2012 18:56:12 +0000 (UTC) Received: by vcmm1 with SMTP id m1so1040501vcm.13 for ; Thu, 26 Jan 2012 10:56:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4sWh5zx79JO/qqbowiFFW/YMwDMxrxXGUaTsgHV7g1s=; b=yCQ3U58kBf1Zc5J8QoVuKtv+nzdN15LWSbiFiF4C8BOFbmUJLclGtAKdmEj/EUhAZ+ mx4frJf+wsGnlM9rd+vv0DtqmH1EEejBPtj4SOTum70OIT2LGxABvq5EC/fYIW27Wh9n eFxgwK7cZRIRjjufGmcmgRPnVwXVukucCT2Os= MIME-Version: 1.0 Received: by 10.220.231.129 with SMTP id jq1mr1827512vcb.59.1327604171596; Thu, 26 Jan 2012 10:56:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.73.228 with HTTP; Thu, 26 Jan 2012 10:56:11 -0800 (PST) In-Reply-To: References: Date: Thu, 26 Jan 2012 10:56:11 -0800 X-Google-Sender-Auth: UxKzGN_2nOHFaWFJ0fMs2gz08wA Message-ID: From: Adrian Chadd To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: PseudoCylon , freebsd-wireless@freebsd.org Subject: Re: net80211 race conditions seen in -HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 18:56:12 -0000 On 26 January 2012 08:35, Bernhard Schmidt wrote: > On Wed, Jan 25, 2012 at 22:47, Adrian Chadd wrote: > > .. whilst the refcount is 1, so ieee80211_ref_node() may not increment > the > > counter before it's freed by another thread. > > You know, that is an inline function, what "lifetime" are we taking about? > > Although the 4 byte pointer assignment _should_ be atomic on i386 architectures, I haven't gone and verified that there are no places where inconsistencies can occur. Except that they are occuring. I wonder if it's the debugging.. > iv_bss has other issues, being overwritten while some task is using it > no matter how high the refcount is is once of those. Yeah. Ew. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 28 05:23:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AA40106566B for ; Sat, 28 Jan 2012 05:23:52 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id F13C38FC0A for ; Sat, 28 Jan 2012 05:23:51 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q0S4ioUC048217 for ; Fri, 27 Jan 2012 20:44:50 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q0S4ioFH048216; Fri, 27 Jan 2012 20:44:50 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: FreeBSD Wireless Cc: Message-Id: <1327725890.48211@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.480 Date: Fri, 27 Jan 2012 20:44:50 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1327725890" Subject: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 05:23:52 -0000 This is a multi-part message in MIME format. --bound1327725890 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hi, I'm new to this group. I have an AR9280 on FreeBSD 9.0-RELEASE and I'd like to see 802.11n working. I believe I understand that this is a project in development, so I suppose I'd like to try out the code on https://gitorious.org/~adrianchadd/freebsd/adrianchadd-freebsd-work - it seems like this is the latest available (?) Are there any pointers or maybe a how-to page to get me started? Thank you for your help. -- Waitman Gobble San Jose California USA --bound1327725890-- From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 28 05:24:54 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB7E6106566B for ; Sat, 28 Jan 2012 05:24:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 974208FC13 for ; Sat, 28 Jan 2012 05:24:53 +0000 (UTC) Received: by vcmm1 with SMTP id m1so2756915vcm.13 for ; Fri, 27 Jan 2012 21:24:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/OaAxUbZj5YqJZMu3uyxd+BO7sb+RlNkxxpb9j41DT4=; b=iQ3FmVmBCRV6gv09lCayVNorzXlHDQxurKKxbOn3k+bQ9s85qxsFzbpjEH/0jj6Hrh 5V+G8W8RNjJmOoOFxt0a9/y6XVzn8QlEyXfd2sD2cS6CuWP3FBp0FYB+UP6kN3svOK9D 8xHmari31701VJhkpnf9e6fIBIOSTSZW4/PVA= MIME-Version: 1.0 Received: by 10.52.26.199 with SMTP id n7mr4788447vdg.17.1327728292933; Fri, 27 Jan 2012 21:24:52 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Fri, 27 Jan 2012 21:24:52 -0800 (PST) In-Reply-To: <1327725890.48211@da3m0n8t3r.com> References: <1327725890.48211@da3m0n8t3r.com> Date: Fri, 27 Jan 2012 21:24:52 -0800 X-Google-Sender-Auth: POBjSu2B54aC2Ej95faUR9sMx88 Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Wireless Subject: Re: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 05:24:54 -0000 Hi, FreeBSD-HEAD contains all of that work. I don't have any plans to backport it to 9.x until it's totally stable and debugged.. and I have no idea when that will be. :-) Adrian On 27 January 2012 20:44, Waitman Gobble wrote: > Hi, > > I'm new to this group. I have an AR9280 on FreeBSD 9.0-RELEASE and I'd > like to see 802.11n working. I believe I understand that this is a project > in development, so I suppose I'd like to try out the code on > https://gitorious.org/~adrianchadd/freebsd/adrianchadd-freebsd-work - it > seems like this is the latest available (?) > > Are there any pointers or maybe a how-to page to get me started? > > Thank you for your help. > > -- > Waitman Gobble > San Jose California USA > > _______________________________________________ > 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 Jan 28 05:53:47 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 189F3106566C for ; Sat, 28 Jan 2012 05:53:47 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id DC44A8FC15 for ; Sat, 28 Jan 2012 05:53:46 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q0S5rkCA014451 for ; Fri, 27 Jan 2012 21:53:46 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q0S5rk4t014449; Fri, 27 Jan 2012 21:53:46 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: FreeBSD Wireless Cc: Message-Id: <1327730026.14444@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.480 In-Reply-To: Date: Fri, 27 Jan 2012 21:53:46 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1327730026" Subject: Re: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 05:53:47 -0000 This is a multi-part message in MIME format. --bound1327730026 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > Hi, > > FreeBSD-HEAD contains all of that work. I don't have any plans to backport > it to 9.x until it's totally stable and debugged.. and I have no idea when > that will be. :-) > > > > > Adrian > > On 27 January 2012 20:44, Waitman Gobble wrote: > > > Hi, > > > > I'm new to this group. I have an AR9280 on FreeBSD 9.0-RELEASE and I'd > > like to see 802.11n working. I believe I understand that this is a project > > in development, so I suppose I'd like to try out the code on > > https://gitorious.org/~adrianchadd/freebsd/adrianchadd-freebsd-work - it > > seems like this is the latest available (?) > > > > Are there any pointers or maybe a how-to page to get me started? > > > > Thank you for your help. > > > > -- > > Waitman Gobble > > San Jose California USA > > > > _______________________________________________ > > 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 > > " > > > > Thank you for the quick reply. Is it possible to get this device on the 5.0 GHz/n network without running FreeBSD-HEAD? Running FreeBSD-HEAD might be an option for me, but I don't know if this is the right machine for that sort of tinkering. :) Might be prudent to upgrade the rest of the everything else of the guts that's connected to the AR9280 first.. but I'll think about it. -- Waitman Gobble San Jose California USA --bound1327730026-- From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 28 05:55:51 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40566106564A for ; Sat, 28 Jan 2012 05:55:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id EB62B8FC0C for ; Sat, 28 Jan 2012 05:55:50 +0000 (UTC) Received: by vcmm1 with SMTP id m1so2769298vcm.13 for ; Fri, 27 Jan 2012 21:55:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=+YLQWtiCGcACCIIaUppOQtPIJ0lmwEOIPq6rzkeVWD8=; b=Nd/4KCnh/2PQmUM0AVh829U/jXuNKFBJFfa7nGYVONMzeMJ0+9GP3KYl6wZXk1m9l8 BE5Pto0x4f8cz85FkmilY0vhsTmSDOWSa4qi7TYANEbHlRJkv9BmjAaM5qet3V6Nux+Y XM8/Edr4ZrChf/y8lVkqC0tF/88ErJLdlP5N4= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr5575619vcw.22.1327730150179; Fri, 27 Jan 2012 21:55:50 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Fri, 27 Jan 2012 21:55:50 -0800 (PST) In-Reply-To: <1327730026.14444@da3m0n8t3r.com> References: <1327730026.14444@da3m0n8t3r.com> Date: Fri, 27 Jan 2012 21:55:50 -0800 X-Google-Sender-Auth: LLKQ9DKNM27KM_FCoJf0GgAFb6Y Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Wireless Subject: Re: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 05:55:51 -0000 On 27 January 2012 21:53, Waitman Gobble wrote: > Is it possible to get this device on the 5.0 GHz/n network without running > FreeBSD-HEAD? > > Running FreeBSD-HEAD might be an option for me, but I don't know if this > is the right machine for that sort of tinkering. :) Might be prudent to > upgrade the rest of the everything else of the guts that's connected to the > AR9280 first.. but I'll think about it. > > Hi, Sure, you can flip on 11n for RX only (where you won't TX aggregate 11n frames) but unfortunately there are a lot of corner cases in theath driver which I need to fix. They show up as TX hanging and this can ruin your wireless day. .. you should show up to the Hacker Dojo in Mountain view sometime btw, since I do drop by here from time to time and bring wifi equipment to hack on. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 28 06:34:07 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01CB41065672 for ; Sat, 28 Jan 2012 06:34:07 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id C6D278FC15 for ; Sat, 28 Jan 2012 06:34:06 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q0S6Y6Pk016665; Fri, 27 Jan 2012 22:34:06 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q0S6Y6Bi016664; Fri, 27 Jan 2012 22:34:06 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1327732446.16659@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.480 In-Reply-To: Date: Fri, 27 Jan 2012 22:34:06 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1327732446" Cc: FreeBSD Wireless Subject: Re: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 06:34:07 -0000 This is a multi-part message in MIME format. --bound1327732446 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > On 27 January 2012 21:53, Waitman Gobble wrote: > > > > Is it possible to get this device on the 5.0 GHz/n network without running > > FreeBSD-HEAD? > > > > Running FreeBSD-HEAD might be an option for me, but I don't know if this > > is the right machine for that sort of tinkering. :) Might be prudent to > > upgrade the rest of the everything else of the guts that's connected to the > > AR9280 first.. but I'll think about it. > > > > > Hi, > > Sure, you can flip on 11n for RX only (where you won't TX aggregate 11n > frames) but unfortunately there are a lot of corner cases in theath driver > which I need to fix. They show up as TX hanging and this can ruin your > wireless day. > > .. you should show up to the Hacker Dojo in Mountain view sometime btw, > since I do drop by here from time to time and bring wifi equipment to hack > on. > > > Adrian Thanks. I'll give it a try. Reading through the previous posts now. OK I'll check out Hacker Dojo, looks cool. And it's a short drive. -- Waitman Gobble San Jose California USA --bound1327732446--