From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 3 10:06:06 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87F9D653; Sun, 3 Aug 2014 10:06:06 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB24B276A; Sun, 3 Aug 2014 10:06:05 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id 10so4498144lbg.12 for ; Sun, 03 Aug 2014 03:06:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=MKBHKxtPj+RgoJPEbBUmveAbpExCSrMgJvC9Y73gyQM=; b=oTpmShT8hFBCFEWjKGgAsMgoI5QsXss7x2Pt7KCpNxi3G6v1RAAovo7BLVSollwNfX HFZg2zNIyoDnQTgpgsCjyXkmDdssrozWJR8py8WRctdrMbw/NQuR+ynV6dbMwq0J0zSM /4oajEFUD641okci9WWVYw5JkUJtHelWNc1dvramVQvYH/A89YY1Awmlv2ytuDxYH353 Mpy+a0IOHX3LFFiJL7qdGnKgo+z4C4l8u1UQlBvJm9ZN0p4gY/0YyGUDLhQ0X4EpQas8 jmtpsF4721ZB5AHyoNeYxmjWWPU4cJAjDLzYVLD/KKa2OVV5sRoSZlruhcna9wIc4CMi DvXw== MIME-Version: 1.0 X-Received: by 10.152.23.197 with SMTP id o5mr1685269laf.60.1407060363809; Sun, 03 Aug 2014 03:06:03 -0700 (PDT) Received: by 10.112.182.38 with HTTP; Sun, 3 Aug 2014 03:06:03 -0700 (PDT) Date: Sun, 3 Aug 2014 12:06:03 +0200 Message-ID: Subject: System crashing after destroying a run iface after coming back from suspend From: Daniel Peyrolon To: adrian@freebsd.org, freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 03 Aug 2014 10:06:06 -0000 Hello everyone, I'm running a relatively CURRENT build on my laptop (Lenovo Thinkpad E530). The problem is adequately described on the subject, except for the fact, that I plugged in the USB WiFi iface *after* coming back from suspension mode (S3). You can see the dmesg and the kernel backtrace at the URLs. Obviously, if there's any information missing, just ask for it. [1]: http://dpaste.com/1RV838H (dmesg) [2]: http://dpaste.com/1T3ASFP (bt) PS: There's a typo at the bt (line 64), since I wrongly entered 'list 0x.*' (I forgot the * before the address, i tried to delete it, but somehow failed to do it properly). -- Daniel From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 3 15:06:03 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FE8DD90 for ; Sun, 3 Aug 2014 15:06:03 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 061122827 for ; Sun, 3 Aug 2014 15:06:01 +0000 (UTC) Received: from srg.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s73F5oS0018812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 3 Aug 2014 23:05:50 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <53DE4FD2.8050309@FreeBSD.org> Date: Sun, 03 Aug 2014 23:05:54 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Miguel Clara , freebsd-wireless@freebsd.org Subject: Re: FreeBSD current RT3071 can't connect to 5G network References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 03 Aug 2014 15:06:03 -0000 On Tue, Jul 29, 2014 at 11:35:00PM +0100, Miguel Clara wrote: > Hi, Hi Miguel, > > I just brought a TP-Link N600 Wireless Dual Band USB Adpater (model > TL-WDN3200) and its correctly recognized in FreeBSD as a ranlink. > > Dmesg shows: > wlan0: Ethernet address: e8:94:f6:12:98:9d > run0: firmware RT3071 ver. 0.33 loaded > > > So the module and firmware seem to be loaded fine and I'm able to connect > to my 2.4g wireless fine. > > However I'm having no luck connecting to the 5G network, I've pasted the > scans and wpa_supplicant log, and I see: > "wlan0: Authentication with 60:a4:4c:28:13:c4 timed out. > Added BSSID 60:a4:4c:28:13:c4 into blacklist" > which I'm guessing means that for some reason the auth time-out, but I > don't really know why, all other 5G devices connect fine! > > (Also if its important the router is a RT-N66U running the latest > Asus-Merlin firmware) > > > First Scan: > > ~% ifconfig wlan0 scan > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > ****** a4:b1:e9:ef:1c:68 1 54M -36:-68 100 EP RSN HTCAP > WPS WPA WME > ****** 9c:97:26:34:b7:cd 11 54M -41:-78 100 EP RSN HTCAP > WPS WPA WME > ****** 24:ec:99:39:4a:12 11 54M -33:-62 100 EP RSN HTCAP > WPS WPA WME > ****** 26:ec:99:39:4a:13 11 54M -31:-60 100 ES HTCAP WME > ****** 10:fe:ed:c3:77:51 7 54M -40:-76 100 EPS RSN HTCAP > WPA WME ATH WPS > Mynetwork5G 60:a4:4c:28:13:c4 44 54M -12:-20 100 EP RSN HTCAP WME > > Second Scan > > % ifconfig wlan0 scan > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > ****** a4:b1:e9:ef:1c:68 1 54M -36:-68 100 EP RSN HTCAP > WPS WPA WME > ****** 9c:97:26:34:b7:cd 11 54M -41:-78 100 EP RSN HTCAP > WPS WPA WME > ****** 24:ec:99:39:4a:12 11 54M -33:-62 100 EP RSN HTCAP > WPS WPA WME > ****** 26:ec:99:39:4a:13 11 54M -31:-60 100 ES HTCAP WME > ****** 10:fe:ed:c3:77:51 7 54M -40:-76 100 EPS RSN HTCAP > WPA WME ATH WPS > Mynetwork5G 60:a4:4c:28:13:c4 44 54M -12:-20 100 EP RSN HTCAP WME > Mynetwork 60:a4:4c:28:13:c0 3 54M -18:-32 100 EP RSN HTCAP WME > > > log from --> wpa_supplicant -i wlano -c /etc/wpa_supplicant.conf -d > NOTE: while doing this in wpa_supplicant.conf I only have my 5g network! I have the same wlan dongle as yours but I have no problems connecting to the TL-WDR4300 on the 5 GHz band. This email is sent over the 5 GHz. I'll investigate further, thanks. # dmesg | grep run0 run0: <1.0> on usbus0 run0: MAC/BBP RT5592 (rev 0x0222), RF RT5592 (MIMO 2T2R), address f8:1a:67:2a:df:3f run0: firmware RT3071 ver. 0.33 loaded # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether f8:1a:67:2a:df:3f inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a status: associated ssid wng_5g channel 149 (5745 MHz 11a) bssid 64:66:b3:c2:3b:d4 country US authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 wme roaming MANUAL > > > wpa_supplicant v2.0 > Successfully initialized wpa_supplicant > Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver > 'default' ctrl_interface 'N/A' bridge 'N/A' > Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' > Reading configuration file '/etc/wpa_supplicant.conf' > ctrl_interface='/var/run/wpa_supplicant' > Priority group 145 > id=0 ssid='PissnLove5G' > wpa_driver_bsd_capa: drivercaps=0x0d85c501,cryptocaps=0x0000001b > wlan0: Own MAC address: e8:94:f6:12:98:9d > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=0 > bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=1 > bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=2 > bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=3 > wpa_driver_bsd_set_countermeasures: enabled=0 > wlan0: RSN: flushing PMKID list in the driver > wlan0: Setting scan request: 0 sec 100000 usec > WPS: Set UUID for interface wlan0 > WPS: UUID based on MAC address - hexdump(len=16): 49 97 f8 d3 b1 d4 56 1d > 94 a4 d0 76 2e 1d 81 b3 > EAPOL: SUPP_PAE entering state DISCONNECTED > EAPOL: Supplicant port status: Unauthorized > EAPOL: KEY_RX entering state NO_KEY_RECEIVE > EAPOL: SUPP_BE entering state INITIALIZE > EAP: EAP entering state DISABLED > EAPOL: Supplicant port status: Unauthorized > EAPOL: Supplicant port status: Unauthorized > wlan0: Added interface wlan0 > wlan0: State: DISCONNECTED -> DISCONNECTED > wlan0: State: DISCONNECTED -> SCANNING > Scan SSID - hexdump_ascii(len=11): > 50 69 73 73 6e 4c 6f 76 65 35 47 PissnLove5G > wlan0: Starting AP scan for wildcard SSID > wpa_driver_bsd_set_wpa: enabled=1 > wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 > EAPOL: disable timer tick > EAPOL: Supplicant port status: Unauthorized > wlan0: Event SCAN_RESULTS (3) received > Received 2464 bytes of scan results (9 BSSes) > wlan0: BSS: Start scan result update 1 > wlan0: BSS: Add new id 0 BSSID 60:a4:4c:28:13:c4 SSID 'PissnLove5G' > wlan0: BSS: Add new id 1 BSSID 60:a4:4c:28:13:c0 SSID 'PissnLove' > wlan0: BSS: Add new id 2 BSSID 24:ec:99:39:4a:12 SSID 'NET' > wlan0: BSS: Add new id 3 BSSID a4:b1:e9:ef:1c:68 SSID 'casabessa' > wlan0: BSS: Add new id 4 BSSID 10:fe:ed:c3:77:51 SSID 'PQTP' > wlan0: BSS: Add new id 5 BSSID 9c:97:26:34:b7:cd SSID 'Vodafone-34B7CD' > wlan0: BSS: Add new id 6 BSSID 00:05:ca:64:7b:e8 SSID 'ZON-7BE0' > wlan0: BSS: Add new id 7 BSSID 26:ec:99:39:4a:13 SSID 'MEO-WiFi' > wlan0: BSS: Add new id 8 BSSID 00:05:ca:64:7b:e9 SSID > 'FON_ZON_FREE_INTERNET' > BSS: last_scan_res_used=9/32 last_scan_full=0 > wlan0: New scan results available > WPS: AP 24:ec:99:39:4a:12 type 0 added > WPS: AP a4:b1:e9:ef:1c:68 type 0 added > WPS: AP 10:fe:ed:c3:77:51 type 0 added > WPS: AP 9c:97:26:34:b7:cd type 0 added > WPS: AP 00:05:ca:64:7b:e8 type 0 added > WPS: AP[0] 24:ec:99:39:4a:12 type=0 tries=0 last_attempt=-1 sec ago > blacklist=0 > WPS: AP[1] a4:b1:e9:ef:1c:68 type=0 tries=0 last_attempt=-1 sec ago > blacklist=0 > WPS: AP[2] 10:fe:ed:c3:77:51 type=0 tries=0 last_attempt=-1 sec ago > blacklist=0 > WPS: AP[3] 9c:97:26:34:b7:cd type=0 tries=0 last_attempt=-1 sec ago > blacklist=0 > WPS: AP[4] 00:05:ca:64:7b:e8 type=0 tries=0 last_attempt=-1 sec ago > blacklist=0 > wlan0: Selecting BSS from priority group 145 > wlan0: 0: 60:a4:4c:28:13:c4 ssid='PissnLove5G' wpa_ie_len=0 rsn_ie_len=20 > caps=0x11 level=-12 > wlan0: selected based on RSN IE > wlan0: selected BSS 60:a4:4c:28:13:c4 ssid='PissnLove5G' > wlan0: Request association: reassociate: 0 selected: 60:a4:4c:28:13:c4 > bssid: 00:00:00:00:00:00 pending: 00:00:00:00:00:00 wpa_state: SCANNING > wlan0: Trying to associate with 60:a4:4c:28:13:c4 (SSID='PissnLove5G' > freq=5220 MHz) > FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0): > wlan0: Cancelling scan request > wlan0: WPA: clearing own WPA/RSN IE > wlan0: Automatic auth_alg selection: 0x1 > RSN: PMKSA cache search - network_ctx=0x0 try_opportunistic=0 > RSN: Search for BSSID 60:a4:4c:28:13:c4 > RSN: No PMKSA cache entry found > wlan0: RSN: using IEEE 802.11i/D9.0 > wlan0: WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2 proto 2 > wlan0: WPA: clearing AP WPA IE > WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f > ac 04 01 00 00 0f ac 02 0c 00 > wlan0: WPA: using GTK CCMP > wlan0: WPA: using PTK CCMP > wlan0: WPA: using KEY_MGMT WPA-PSK > WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 > 00 00 0f ac 04 01 00 00 0f ac 02 00 00 > wlan0: No keys have been configured - skip key clearing > wlan0: State: SCANNING -> ASSOCIATING > Limit connection to BSSID 60:a4:4c:28:13:c4 freq=5220 MHz based on scan > results (bssid_set=0) > wpa_driver_bsd_associate: ssid 'PissnLove5G' wpa ie len 22 pairwise 3 group > 3 key mgmt 1 > wpa_driver_bsd_set_drop_unencrypted: enabled=1 > bsd_set_opt_ie: set WPA+RSN ie (len 22) > wpa_driver_bsd_associate: set PRIVACY 1 > wlan0: Setting authentication timeout: 10 sec 0 usec > EAPOL: External notification - EAP success=0 > EAPOL: Supplicant port status: Unauthorized > EAPOL: External notification - EAP fail=0 > EAPOL: Supplicant port status: Unauthorized > EAPOL: External notification - portControl=Auto > EAPOL: Supplicant port status: Unauthorized > RSN: Ignored PMKID candidate without preauth flag > wlan0: Authentication with 60:a4:4c:28:13:c4 timed out. > Added BSSID 60:a4:4c:28:13:c4 into blacklist > wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 > pending_bssid=60:a4:4c:28:13:c4 reason=3 state=ASSOCIATING > wlan0: Event DEAUTH (12) received > wlan0: Deauthentication notification > wlan0: * reason 3 (locally generated) > Deauthentication frame IE(s) - hexdump(len=0): [NULL] > wlan0: CTRL-EVENT-DISCONNECTED bssid=60:a4:4c:28:13:c4 reason=3 > locally_generated=1 > wlan0: Auto connect enabled: try to reconnect (wps=0 wpa_state=5) > wlan0: Setting scan request: 0 sec 100000 usec > BSSID 60:a4:4c:28:13:c4 blacklist count incremented to 2 > wlan0: Blacklist count 2 --> request scan in 500 ms > wlan0: Not rescheduling scan to ensure that specific SSID scans occur > wlan0: Disconnect event - remove keys > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=0 > bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=1 > bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=2 > bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: key_idx=3 > bsd_set_key: alg=0 addr=0x801c2f4c8 key_idx=0 set_tx=0 seq_len=0 key_len=0 > bsd_del_key: addr=00:00:00:00:00:00 > wlan0: State: ASSOCIATING -> DISCONNECTED > EAPOL: External notification - portEnabled=0 > EAPOL: Supplicant port status: Unauthorized > EAPOL: External notification - portValid=0 > EAPOL: Supplicant port status: Unauthorized > EAPOL: External notification - EAP success=0 > EAPOL: Supplicant port status: Unauthorized > wlan0: No keys have been configured - skip key clearing > wlan0: State: DISCONNECTED -> DISCONNECTED > EAPOL: External notification - portEnabled=0 > EAPOL: Supplicant port status: Unauthorized > EAPOL: External notification - portValid=0 > EAPOL: Supplicant port status: Unauthorized > wlan0: Not rescheduling scan to ensure that specific SSID scans occur > wlan0: State: DISCONNECTED -> SCANNING > Scan SSID - hexdump_ascii(len=11): > 50 69 73 73 6e 4c 6f 76 65 35 47 PissnLove5G > wlan0: Starting AP scan for wildcard SSID > wpa_driver_bsd_set_wpa: enabled=1 > wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 > wlan0: Removing interface wlan0 > wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 > pending_bssid=00:00:00:00:00:00 reason=3 state=SCANNING > wlan0: No keys have been configured - skip key clearing > wlan0: State: SCANNING -> DISCONNECTED > EAPOL: External notification - portEnabled=0 > EAPOL: Supplicant port status: Unauthorized > EAPOL: External notification - portValid=0 > EAPOL: Supplicant port status: Unauthorized > wpa_driver_bsd_set_countermeasures: enabled=0 > wlan0: No keys have been configured - skip key clearing > Removed BSSID 60:a4:4c:28:13:c4 from blacklist (clear) > wlan0: BSS: Remove id 0 BSSID 60:a4:4c:28:13:c4 SSID 'PissnLove5G' due to > wpa_bss_flush > wlan0: BSS: Remove id 1 BSSID 60:a4:4c:28:13:c0 SSID 'PissnLove' due to > wpa_bss_flush > wlan0: BSS: Remove id 2 BSSID 24:ec:99:39:4a:12 SSID 'NET' due to > wpa_bss_flush > wlan0: BSS: Remove id 3 BSSID a4:b1:e9:ef:1c:68 SSID 'casabessa' due to > wpa_bss_flush > wlan0: BSS: Remove id 4 BSSID 10:fe:ed:c3:77:51 SSID 'PQTP' due to > wpa_bss_flush > wlan0: BSS: Remove id 5 BSSID 9c:97:26:34:b7:cd SSID 'Vodafone-34B7CD' due > to wpa_bss_flush > wlan0: BSS: Remove id 6 BSSID 00:05:ca:64:7b:e8 SSID 'ZON-7BE0' due to > wpa_bss_flush > wlan0: BSS: Remove id 7 BSSID 26:ec:99:39:4a:13 SSID 'MEO-WiFi' due to > wpa_bss_flush > wlan0: BSS: Remove id 8 BSSID 00:05:ca:64:7b:e9 SSID > 'FON_ZON_FREE_INTERNET' due to wpa_bss_flush > wlan0: Cancelling scan request > wlan0: Cancelling authentication timeout > wpa_driver_bsd_set_wpa: enabled=0 > wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 > bsd_set_opt_ie: set WPA+RSN ie (len 0) > ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported > wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=0 > wlan0: CTRL-EVENT-TERMINATING Kevin From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 4 08:00:21 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48D12225 for ; Mon, 4 Aug 2014 08:00:21 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B0EF2FED for ; Mon, 4 Aug 2014 08:00:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s7480Ln4097003 for ; Mon, 4 Aug 2014 08:00:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201408040800.s7480Ln4097003@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 04 Aug 2014 08:00:21 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 04 Aug 2014 08:00:21 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 5 03:13:25 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3EF1483 for ; Tue, 5 Aug 2014 03:13:25 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BACFD225F for ; Tue, 5 Aug 2014 03:13:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s753DPCP093158 for ; Tue, 5 Aug 2014 03:13:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 189405] [run] [wlan] hostapd, kernel panic, wlan using run device, run0: RT3071, RF RT3022 Date: Tue, 05 Aug 2014 03:13:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john@feith.com X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2014 03:13:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189405 john@feith.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john@feith.com --- Comment #3 from john@feith.com --- I also ran into this after migrating 9.2 to 10.0 via src build (the wifi was working fine on 9.2). The supplied patch appears to fix the problem on my machine. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 5 09:26:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C2A6ECA for ; Tue, 5 Aug 2014 09:26:47 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B7AEC2A94 for ; Tue, 5 Aug 2014 09:26:46 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s759QaQK041328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 5 Aug 2014 17:26:37 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s759Qa5K041327; Tue, 5 Aug 2014 17:26:36 +0800 (CST) (envelope-from kevlo) Date: Tue, 5 Aug 2014 17:26:36 +0800 From: Kevin Lo To: Miguel Clara Subject: Re: FreeBSD current RT3071 can't connect to 5G network Message-ID: <20140805092636.GA41308@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53DE4FD2.8050309@FreeBSD.org> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2014 09:26:47 -0000 On Sun, Aug 03, 2014 at 11:05:54PM +0800, Kevin Lo wrote: > > On Tue, Jul 29, 2014 at 11:35:00PM +0100, Miguel Clara wrote: > > Hi, > > Hi Miguel, > > > > > I just brought a TP-Link N600 Wireless Dual Band USB Adpater (model > > TL-WDN3200) and its correctly recognized in FreeBSD as a ranlink. > > > > Dmesg shows: > > wlan0: Ethernet address: e8:94:f6:12:98:9d > > run0: firmware RT3071 ver. 0.33 loaded > > > > > > So the module and firmware seem to be loaded fine and I'm able to connect > > to my 2.4g wireless fine. > > > > However I'm having no luck connecting to the 5G network, I've pasted the > > scans and wpa_supplicant log, and I see: > > "wlan0: Authentication with 60:a4:4c:28:13:c4 timed out. > > Added BSSID 60:a4:4c:28:13:c4 into blacklist" > > which I'm guessing means that for some reason the auth time-out, but I > > don't really know why, all other 5G devices connect fine! > > > > (Also if its important the router is a RT-N66U running the latest > > Asus-Merlin firmware) > > > > > > First Scan: > > > > ~% ifconfig wlan0 scan > > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > > ****** a4:b1:e9:ef:1c:68 1 54M -36:-68 100 EP RSN HTCAP > > WPS WPA WME > > ****** 9c:97:26:34:b7:cd 11 54M -41:-78 100 EP RSN HTCAP > > WPS WPA WME > > ****** 24:ec:99:39:4a:12 11 54M -33:-62 100 EP RSN HTCAP > > WPS WPA WME > > ****** 26:ec:99:39:4a:13 11 54M -31:-60 100 ES HTCAP WME > > ****** 10:fe:ed:c3:77:51 7 54M -40:-76 100 EPS RSN HTCAP > > WPA WME ATH WPS > > Mynetwork5G 60:a4:4c:28:13:c4 44 54M -12:-20 100 EP RSN HTCAP WME > > > > Second Scan > > > > % ifconfig wlan0 scan > > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > > ****** a4:b1:e9:ef:1c:68 1 54M -36:-68 100 EP RSN HTCAP > > WPS WPA WME > > ****** 9c:97:26:34:b7:cd 11 54M -41:-78 100 EP RSN HTCAP > > WPS WPA WME > > ****** 24:ec:99:39:4a:12 11 54M -33:-62 100 EP RSN HTCAP > > WPS WPA WME > > ****** 26:ec:99:39:4a:13 11 54M -31:-60 100 ES HTCAP WME > > ****** 10:fe:ed:c3:77:51 7 54M -40:-76 100 EPS RSN HTCAP > > WPA WME ATH WPS > > Mynetwork5G 60:a4:4c:28:13:c4 44 54M -12:-20 100 EP RSN HTCAP WME > > Mynetwork 60:a4:4c:28:13:c0 3 54M -18:-32 100 EP RSN HTCAP WME > > > > > > log from --> wpa_supplicant -i wlano -c /etc/wpa_supplicant.conf -d > > NOTE: while doing this in wpa_supplicant.conf I only have my 5g network! > > I have the same wlan dongle as yours but I have no problems connecting to > the TL-WDR4300 on the 5 GHz band. This email is sent over the 5 GHz. > I'll investigate further, thanks. > > # dmesg | grep run0 > run0: <1.0> on usbus0 > run0: MAC/BBP RT5592 (rev 0x0222), RF RT5592 (MIMO 2T2R), address > f8:1a:67:2a:df:3f > run0: firmware RT3071 ver. 0.33 loaded > > # ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether f8:1a:67:2a:df:3f > inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a > status: associated > ssid wng_5g channel 149 (5745 MHz 11a) bssid 64:66:b3:c2:3b:d4 > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF > TKIP 2:128-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 > scanvalid 60 > wme roaming MANUAL Please try Akinori Furukoshi's patch, thanks. Index: sys/dev/usb/wlan/if_run.c =================================================================== --- sys/dev/usb/wlan/if_run.c (revision 269566) +++ sys/dev/usb/wlan/if_run.c (working copy) @@ -3255,13 +3255,13 @@ run_set_tx_desc(struct run_softc *sc, struct run_t txwi = (struct rt2860_txwi *)(txd + 1); txwi->len = htole16(m->m_pkthdr.len - pad); if (rt2860_rates[ridx].phy == IEEE80211_T_DS) { - txwi->phy = htole16(RT2860_PHY_CCK); + mcs |= RT2860_PHY_CCK; if (ridx != RT2860_RIDX_CCK1 && (ic->ic_flags & IEEE80211_F_SHPREAMBLE)) mcs |= RT2860_PHY_SHPRE; } else - txwi->phy = htole16(RT2860_PHY_OFDM); - txwi->phy |= htole16(mcs); + mcs |= RT2860_PHY_OFDM; + txwi->phy = htole16(mcs); /* check if RTS/CTS or CTS-to-self protection is required */ if (!IEEE80211_IS_MULTICAST(wh->i_addr1) && @@ -3338,7 +3338,7 @@ run_tx(struct run_softc *sc, struct mbuf *m, struc /* pickup a rate index */ if (IEEE80211_IS_MULTICAST(wh->i_addr1) || - type != IEEE80211_FC0_TYPE_DATA) { + type != IEEE80211_FC0_TYPE_DATA || m->m_flags & M_EAPOL) { ridx = (ic->ic_curmode == IEEE80211_MODE_11A) ? RT2860_RIDX_OFDM6 : RT2860_RIDX_CCK1; ctl_ridx = rt2860_rates[ridx].ctl_ridx; @@ -4998,7 +4998,7 @@ run_updateprot_cb(void *arg) tmp = RT2860_RTSTH_EN | RT2860_PROT_NAV_SHORT | RT2860_TXOP_ALLOW_ALL; /* setup protection frame rate (MCS code) */ tmp |= (ic->ic_curmode == IEEE80211_MODE_11A) ? - rt2860_rates[RT2860_RIDX_OFDM6].mcs : + rt2860_rates[RT2860_RIDX_OFDM6].mcs | RT2860_PHY_OFDM : rt2860_rates[RT2860_RIDX_CCK11].mcs; /* CCK frames don't require protection */ From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 01:47:30 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5FA8EFF for ; Wed, 6 Aug 2014 01:47:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CEA082735 for ; Wed, 6 Aug 2014 01:47:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s761lUVa025848 for ; Wed, 6 Aug 2014 01:47:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192415] New: [ath] AR933x power save causes the AR9331 to stop DMA Date: Wed, 06 Aug 2014 01:47:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 01:47:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192415 Bug ID: 192415 Summary: [ath] AR933x power save causes the AR9331 to stop DMA Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: adrian@freebsd.org The current powersave code in the ath(4) driver / HAL is causing issues on the AR9331. Even if powersave is disabled, the chip is put into powersave mode when no VAPs are in use. This seems to lock up the DMA side of things. Symptoms: * lots of "disable rx dma failed" messages * no packets being transmitted/received * TX/RX interrupt counts don't increase * if AH_INTERRUPT_DEBUGGING is defined, then sync interrupts are posted - 0x200 and 0x40. Now, I'm not sure yet what those bits are. I guess it's similar to the AR9340 ones - AR9340_INTR_SYNC_MAC_SLEEP_ACCESS (0x40). That meant that it was configured whilst the MAC was asleep. Ugh. If i disable the power save code in if_ath.c (ie, make all the ath_hal_setpowermode() calls to HAL_PM_AWAKE) then things work fine. So, figure out what is being programmed whilst the MAC is asleep, or what is currently not shut down correctly before the MAC is put to sleep. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 01:52:57 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60A7C103 for ; Wed, 6 Aug 2014 01:52:57 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4994F27F6 for ; Wed, 6 Aug 2014 01:52:57 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s761qv99050284 for ; Wed, 6 Aug 2014 01:52:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192416] New: [ath] TSFOOR interrupt firing on AR9331 Date: Wed, 06 Aug 2014 01:52:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 01:52:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192416 Bug ID: 192416 Summary: [ath] TSFOOR interrupt firing on AR9331 Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: adrian@freebsd.org The TSFOOR interrupt is triggering with the AR9331 in station mode. take a look to see what's going on: * is it not RX'ing beacons; * is the beacon timer programming all fucked up; * is calibration interfering; * something else. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 01:58:19 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3DEA035D for ; Wed, 6 Aug 2014 01:58:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 26A3A2837 for ; Wed, 6 Aug 2014 01:58:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s761wJmm058260 for ; Wed, 6 Aug 2014 01:58:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192416] [ath] TSFOOR interrupt firing on AR9331 Date: Wed, 06 Aug 2014 01:58:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: gjb@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 01:58:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192416 --- Comment #1 from Glen Barber --- Also happens on AR9485, but has not happened for me recently. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:39:11 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 574C9EDA for ; Wed, 6 Aug 2014 08:39:11 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 248492536 for ; Wed, 6 Aug 2014 08:39:11 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768dBQ0041313 for ; Wed, 6 Aug 2014 08:39:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] New: FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Wed, 06 Aug 2014 08:39:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:39:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 Bug ID: 192423 Summary: FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Product: Base System Version: 10.0-STABLE Hardware: i386 OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: ndenev@gmail.com I have a Soekris Net5501 on which I've recently installed an AR9220 based mini-PCI card (MikroTik R52Hn) with both antenna ports used. I'm trying to use it to both connect to an AP, and at the same time setup as a AP. The AP I'm connecting to is 802.11g, while I'm setting up the AP wlan as 802.11n (not sure if this is relevant). And at the moment both wlan0 and wlan1 are enabled the machine slows down, possibly due to excessive kernel printfs like these : ath0: ath_rate_findrate: currates != sc_currates! And eventually reboots (possibly due to watchdog kicking in). rc.conf : wlans_ath0="wlan0 wlan1" ifconfig_ath0="up" ifconfig_wlan0="ssid WISP wepkey 1:0xdeadbeef weptxkey 1 wepmode on deftxkey 1 DHCP" create_args_wlan1="wlanmode hostap" ifconfig_wlan1="mode 11ng channel 9:ht/40" ifconfig_bridge0="addm wlan1 addm vr0" hostapd.conf : interface=wlan1 logger_syslog=-1 logger_syslog_level=0 logger_stdout=-1 logger_stdout_level=0 debug=3 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=my-home-wi-fi macaddr_acl=0 auth_algs=1 ieee8021x=0 wpa=2 wpa_passphrase=******** wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:40:40 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8AB3DFA for ; Wed, 6 Aug 2014 08:40:40 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7188B2550 for ; Wed, 6 Aug 2014 08:40:40 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768eexj043713 for ; Wed, 6 Aug 2014 08:40:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Wed, 06 Aug 2014 08:40:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:40:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 --- Comment #1 from ndenev@gmail.com --- OS is : FreeBSD mars 10.0-STABLE FreeBSD 10.0-STABLE #20 r262664: Mon Mar 3 02:24:37 UTC 2014 root@mars:/usr/obj/usr/src/sys/MARS i386 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:46:19 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B958B1F8 for ; Wed, 6 Aug 2014 08:46:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A0CD02616 for ; Wed, 6 Aug 2014 08:46:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768kJPU049612 for ; Wed, 6 Aug 2014 08:46:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Wed, 06 Aug 2014 08:46:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:46:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org --- Comment #2 from Adrian Chadd --- What channel is it associating on? Typically when that happens it's because the rate control code found that the rate table was changing very frequently from underneath it and a lot of the wifi driver code assumed the rate table wouldn't change that frequently. Is ath0 the AP or STA? So there's two parts: * figure out why your rate table keeps changing; * figure out a better way to handle that in the rate table code. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:48:28 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48EE1275 for ; Wed, 6 Aug 2014 08:48:28 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 30747262F for ; Wed, 6 Aug 2014 08:48:28 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768mSxn050510 for ; Wed, 6 Aug 2014 08:48:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192424] New: [ath] Port over AR9331 fixes from qca-wifi git repository Date: Wed, 06 Aug 2014 08:48:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:48:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192424 Bug ID: 192424 Summary: [ath] Port over AR9331 fixes from qca-wifi git repository Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: adrian@freebsd.org There's a few things that should be ported over from the qca-wifi (public) git repository. I'll add to this ticket as I find things to port. * there's some hornet (AR9331) specific otp initialisation code which I _think_ is setting up various thermal / regulator parameters. * there's a WAR in ar9300_set_reset() for the AR9331 which asks the SoC to get involved if it's a cold reset. Ie, it actually does a full wireless mac/phy/radio reset via the SoC path rather than a straight cold reset via the normal MAC/RTC path. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:49:30 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9AD362D8 for ; Wed, 6 Aug 2014 08:49:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 81B7F2642 for ; Wed, 6 Aug 2014 08:49:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768nUCW051023 for ; Wed, 6 Aug 2014 08:49:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 188576] [ath] traffic hangs in station mode when downgrading from AMPDU TX or reassociating Date: Wed, 06 Aug 2014 08:49:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:49:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188576 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |FIXED --- Comment #2 from Adrian Chadd --- I believe this is fixed in FreeBSD-HEAD. I found and squished these until I had it constantly doing AMPDU upgrade/downgrade due to high packet loss whilst doing constant traffic. I'll re-open this if it pops up again. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:51:51 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 905FB476 for ; Wed, 6 Aug 2014 08:51:51 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 775812690 for ; Wed, 6 Aug 2014 08:51:51 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768pp0L064789 for ; Wed, 6 Aug 2014 08:51:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192423] FreeBSD-10 with AR9220, console spam and reboot with both hostap and client wlan-s on the same ath0 Date: Wed, 06 Aug 2014 08:51:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:51:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192423 --- Comment #3 from ndenev@gmail.com --- Both wlan0 and wlan1 are on the same ath0 device. So, wlan0 is STA, associated on channel 9 (2452 MHz 11g). Currently is at DS/11Mbps, however it fluctuates a lot between DS1/Mbps, 5.5Mbps, sometimes it goes as high as OFDM/48Mbps. wlan1 is the AP wlan, it is now configured on Channel 6, however I've tried to start it also on channel 9 with the same result. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 08:53:42 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 413EA518 for ; Wed, 6 Aug 2014 08:53:42 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 28D2B2746 for ; Wed, 6 Aug 2014 08:53:42 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s768rg27081745 for ; Wed, 6 Aug 2014 08:53:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192415] [ath] AR933x power save causes the AR9331 to stop DMA Date: Wed, 06 Aug 2014 08:53:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 08:53:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192415 --- Comment #1 from Adrian Chadd --- Specifically: root@freebsd-carambola2:/home/adrian # sysctl dev.ath.0.stats.sync_intr | grep -v ': 0$' dev.ath.0.stats.sync_intr.10: 52 dev.ath.0.stats.sync_intr.13: 52 The bits from ar9300reg.h: AR9300_INTR_SYNC_RADM_CPL_TLP_ABORT = 0x00000400, AR9300_INTR_SYNC_LOCAL_TIMEOUT = 0x00002000, .. now, the former is not entirely right - those bits are PCIe host interface specific. The latter bit is likely valid for the AR9331. I'll have to get a hold of the AR9331 host interface description from Atheros to figure out what the sync interrupt bits actually mean here. I do think that a register was programmed whilst the NIC was in network or full sleep. I'll have to figure out why my debugging code isn't picking up on that. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 6 21:23:29 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1B75A4A; Wed, 6 Aug 2014 21:23:29 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A6DF22924; Wed, 6 Aug 2014 21:23:29 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s76LNN4w045518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Aug 2014 14:23:23 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s76LNLBG045517; Wed, 6 Aug 2014 14:23:21 -0700 (PDT) (envelope-from jmg) Date: Wed, 6 Aug 2014 14:23:20 -0700 From: John-Mark Gurney To: John Hay Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140806212320.GU88623@funkthat.com> Mail-Followup-To: John Hay , Adrian Chadd , "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore References: <20140714194932.GA51947@zibbi.meraka.csir.co.za> <20140714200015.GA54311@zibbi.meraka.csir.co.za> <20140714203707.GB54311@zibbi.meraka.csir.co.za> <20140717103430.GA88108@zibbi.meraka.csir.co.za> <20140717192433.GA35445@zibbi.meraka.csir.co.za> <20140717194412.GA37369@zibbi.meraka.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140717194412.GA37369@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 06 Aug 2014 14:23:23 -0700 (PDT) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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, 06 Aug 2014 21:23:30 -0000 John Hay wrote this message on Thu, Jul 17, 2014 at 21:44 +0200: > On Thu, Jul 17, 2014 at 12:30:53PM -0700, Adrian Chadd wrote: > > okay, I think that needs to be fixed first. I can't debug it otherwise. :) > > vmstat -ia output looks the same on an Avila board, so it isn't Cambria > specific. Ok, I tracked this down, and it looks like Ian forgot to add the necessary call to arm_intrnames_init in initarm to setup the names of interrupts properly when he changed how interrupt names were handled... I've fixed this for at least AVILA (and other ixp425 boards) w/ the included patch... Ian will be committing fixes for this issue shortly... He may be using a different method than the attached patch... Index: avila_machdep.c =================================================================== --- avila_machdep.c (revision 269019) +++ avila_machdep.c (working copy) @@ -70,6 +70,7 @@ __FBSDID("$FreeBSD$"); #include #include #include +#include #include #include #include @@ -393,6 +394,7 @@ initarm(struct arm_boot_params *abp) init_proc0(kernelstack.pv_va); + arm_intrnames_init(); arm_vector_init(ARM_VECTORS_HIGH, ARM_VEC_ALL); pmap_curmaxkvaddr = afterkern + PAGE_SIZE; -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."