From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 02:14:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 92A80F37 for ; Sun, 28 Apr 2013 02:14:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 2D1E513AA for ; Sun, 28 Apr 2013 02:14:57 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id j13so2812809wgh.2 for ; Sat, 27 Apr 2013 19:14:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=8fnLebivgtH0YQov3l0JJCS3gDdjpBpvsxFYRMraQuI=; b=UpeejWndh0vTox80s8fHLqXi/ceRHeM6+qS4+plJmOExRKNqLMCTcW7/LacwCmkNMF 6nXDUA8PMLcMg9MpO13d52o9OepjHwX22yj+dj1XOuE7d/C7247Ec1pEGKBxk+6LjbFO 4/IqPLs0KEW9r7AU1pxqHR7RWffZU5Utu8HsILgIPSW736EGQenyg7IFdjKwl2jBM1Sj fDT/oOBP68CvfI0gqKJxY4vpI2rSNVYSn2Mzuf0YCtaKhOpHZssl7Gs6eh8PdU0HY56o jxrMX5/RZ47PvNwnSqUb0VqpWA0g4T3nE/pO7INtXiVDzW4Ni0CcB3E2CR7S9Pu4Yp3G drzg== MIME-Version: 1.0 X-Received: by 10.180.93.134 with SMTP id cu6mr10933918wib.8.1367115296200; Sat, 27 Apr 2013 19:14:56 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sat, 27 Apr 2013 19:14:56 -0700 (PDT) Date: Sat, 27 Apr 2013 19:14:56 -0700 X-Google-Sender-Auth: L1qvrkDwkYnT0QCvu-waiJa7Slo Message-ID: Subject: notice: ar9300 support is (almost) in head From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2013 02:14:57 -0000 Hi, I've just pushed the vendor code and my freebsd ar9300 work into -head. I haven't yet added the build links into the system so it won't build ar9300 support into the kernel or modules; I'm currently testing that now. Once it passes a 'make universe' I'll commit it to -head. Thanks to everyone who has helped test this stuff out so far! Now, back to working with Lev to get more info about his TX hangs.. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 02:52:19 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 00A2AB75 for ; Sun, 28 Apr 2013 02:52:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 939B11519 for ; Sun, 28 Apr 2013 02:52:18 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id l13so1744636wie.16 for ; Sat, 27 Apr 2013 19:52:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=s27qF/5ee7wQ+uOpDqrlV5FTRU/U21BNrA9QTTuZfKg=; b=MXvtBPFwjvlcQc5zT0wFdsqD3hzs/tVlD0bOQONiUEuyCEMXbABlahsw5KDkML6kb6 /+RpJXKYVGP/2+GMFwQnUceptNK9qN77klnbBEQ6NrDdwvRwstsSmiamLYsNsEBGThya HD7H01s8aSQRCSIoFFue5eTCoXZwYYmiWRN5r63l7zPLROuY3G4Og032GQsR9ZOzhVqb 8wR3beVHKPUtD8fv+utxdEyz9K14sgO2ubft9wYAQkDKm3Va2rrh6GZFM3ob+0pYvhSi q28ka7sCHIOHwx85FuMPiOoq7RKJJXH4OWHpLMB1aDj2vPgLq4JftvbVLWNQBpO2MnDU rc/g== MIME-Version: 1.0 X-Received: by 10.180.20.108 with SMTP id m12mr10992184wie.8.1367117536889; Sat, 27 Apr 2013 19:52:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sat, 27 Apr 2013 19:52:16 -0700 (PDT) Date: Sat, 27 Apr 2013 19:52:16 -0700 X-Google-Sender-Auth: SwEpwYZzzqTx_thywoqupUJ8d58 Message-ID: Subject: net80211 and lock-ordering issues.. From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2013 02:52:19 -0000 Hi, So my recent TX path locking work in net80211 has had time to bake a bit and I've logged all the LORs I've seen in STA/AP modes. Unfortunately there's a lot. I'm going to try and fix the ones I've seen so far. I'm worried though that there's some fundamental design issues here which are going to take a _long_ time to fix up. I'd like some design suggestions please. I'm tempted here to move the ic and vap tx paths over to run out of taskqueues (as I originally planned) and just bite the overhead for now. it just simplifies this locking a lot and will make it much easier to tidy up the rest of the code. Eg, if a buffer can't be sent and it's freed as part of the TX path: Apr 25 01:48:38 lucy kernel: lock order reversal: Apr 25 01:48:38 lucy kernel: 1st 0xcf2096e0 ath0 TX lock (ath0 TX lock) @ sys/dev/ath/if_ath_misc.h:135 Apr 25 01:48:38 lucy kernel: 2nd 0xcf22b6f4 ath0_node_lock (ath0_node_lock) @ /usr/home/adrian/work/freebsd/net80211_tx/head/src/sys/modules/wlan/../../net80211/ieee80211_node.c:1768 Apr 25 01:48:38 lucy kernel: KDB: stack backtrace: Apr 25 01:48:38 lucy kernel: #0 0xc0734d1f at kdb_backtrace+0x4f Apr 25 01:48:38 lucy kernel: #1 0xc074aa85 at _witness_debugger+0x25 Apr 25 01:48:38 lucy kernel: #2 0xc074bd7f at witness_checkorder+0x86f Apr 25 01:48:38 lucy kernel: #3 0xc06e9de4 at _mtx_lock_flags+0xc4 Apr 25 01:48:38 lucy kernel: #4 0xcf19e0d6 at ieee80211_free_node_debug+0xa6 Apr 25 01:48:38 lucy kernel: #5 0xd0b2aadd at ath_start+0x53d Apr 25 01:48:38 lucy kernel: #6 0xd0b299fb at ath_tx_kick+0x3b Apr 25 01:48:38 lucy kernel: #7 0xd0b2a19f at ath_start_queue+0x8f Apr 25 01:48:38 lucy kernel: #8 0xc07b6c42 at if_start+0x12 Apr 25 01:48:38 lucy kernel: #9 0xc07b750f at if_transmit+0x13f Apr 25 01:48:38 lucy kernel: #10 0xcf185d5c at ieee80211_parent_transmit+0x4c Apr 25 01:48:38 lucy kernel: #11 0xcf1a0ffa at ieee80211_start_pkt+0x74a Apr 25 01:48:38 lucy kernel: #12 0xcf1a1515 at ieee80211_start+0x335 Apr 25 01:48:38 lucy kernel: #13 0xc07b6c42 at if_start+0x12 Apr 25 01:48:38 lucy kernel: #14 0xc07b750f at if_transmit+0x13f Apr 25 01:48:38 lucy kernel: #15 0xc1104d41 at bridge_enqueue+0x31 Apr 25 01:48:38 lucy kernel: #16 0xc11079db at bridge_forward+0x2eb Apr 25 01:48:38 lucy kernel: #17 0xc1107f77 at bridge_input+0x527 My power save work also has introduced some. .. if the TIM bit is fiddled with: Apr 25 02:58:44 lucy kernel: lock order reversal: Apr 25 02:58:44 lucy kernel: 1st 0xcf2096e0 ath0 TX lock (ath0 TX lock) @ /usr/home/adrian/work/freebsd/net80211_tx/head/src/sys/modules/ath/../../dev/ath/if_ath.c:3796 Apr 25 02:58:44 lucy kernel: 2nd 0xcf22a014 ath0_com_lock (ath0_com_lock) @ /usr/home/adrian/work/freebsd/net80211_tx/head/src/sys/modules/wlan/../../net80211/ieee80211_power.c:297 Apr 25 02:58:44 lucy kernel: KDB: stack backtrace: Apr 25 02:58:44 lucy kernel: #0 0xc0734d1f at kdb_backtrace+0x4f Apr 25 02:58:44 lucy kernel: #1 0xc074aa85 at _witness_debugger+0x25 Apr 25 02:58:44 lucy kernel: #2 0xc074bd7f at witness_checkorder+0x86f Apr 25 02:58:44 lucy kernel: #3 0xc06e9de4 at _mtx_lock_flags+0xc4 Apr 25 02:58:44 lucy kernel: #4 0xcf1a8e18 at ieee80211_set_tim+0xd8 Apr 25 02:58:44 lucy kernel: #5 0xd0b32b5d at ath_tx_update_tim+0x20d Apr 25 02:58:44 lucy kernel: #6 0xd0b2d0c4 at ath_tx_default_comp+0xe4 Apr 25 02:58:44 lucy kernel: #7 0xd0b430ea at ath_tx_aggr_retry_unaggr+0x25a Apr 25 02:58:44 lucy kernel: #8 0xd0b44b99 at ath_tx_aggr_comp_unaggr+0x519 Apr 25 02:58:44 lucy kernel: #9 0xd0b44d6b at ath_tx_aggr_comp+0x4b Apr 25 02:58:44 lucy kernel: #10 0xd0b2d313 at ath_tx_process_buf_completion+0x123 Apr 25 02:58:44 lucy kernel: #11 0xd0b2d905 at ath_tx_processq+0x5e5 Apr 25 02:58:44 lucy kernel: #12 0xd0b2df20 at ath_tx_proc_q0123+0x170 Apr 25 02:58:44 lucy kernel: #13 0xc07435bb at taskqueue_run_locked+0xeb Apr 25 02:58:44 lucy kernel: #14 0xc0744027 at taskqueue_thread_loop+0x67 Apr 25 02:58:44 lucy kernel: #15 0xc06cb5c2 at fork_exit+0x112 Apr 25 02:58:44 lucy kernel: #16 0xc09715e4 at fork_trampoline+0x8 And some existing ones: Apr 25 03:04:05 lucy kernel: lock order reversal: Apr 25 03:04:05 lucy kernel: 1st 0xcf22b6f4 ath0_node_lock (ath0_node_lock) @ /usr/home/adrian/work/freebsd/net80211_tx/head/src/sys/modules/wlan/../../net80211/ieee80211_ioctl.c:1341 Apr 25 03:04:05 lucy kernel: 2nd 0xcf22a038 ath0_tx_lock (ath0_tx_lock) @ /usr/home/adrian/work/freebsd/net80211_tx/head/src/sys/modules/wlan/../../net80211/ieee80211_output.c:719 Apr 25 03:04:05 lucy kernel: KDB: stack backtrace: Apr 25 03:04:05 lucy kernel: #0 0xc0734d1f at kdb_backtrace+0x4f Apr 25 03:04:05 lucy kernel: #1 0xc074aa85 at _witness_debugger+0x25 Apr 25 03:04:05 lucy kernel: #2 0xc074bd7f at witness_checkorder+0x86f Apr 25 03:04:05 lucy kernel: #3 0xc06e9de4 at _mtx_lock_flags+0xc4 Apr 25 03:04:05 lucy kernel: #4 0xcf1a20be at ieee80211_mgmt_output+0x24e Apr 25 03:04:05 lucy kernel: #5 0xcf1a6043 at ieee80211_send_mgmt+0xd03 Apr 25 03:04:05 lucy kernel: #6 0xcf18c55f at domlme+0x8f Apr 25 03:04:05 lucy kernel: #7 0xcf18c64e at setmlme_dropsta+0xae Apr 25 03:04:05 lucy kernel: #8 0xcf18c7ab at setmlme_common+0xeb Apr 25 03:04:05 lucy kernel: #9 0xcf18cf62 at ieee80211_ioctl_setmlme+0x112 Apr 25 03:04:05 lucy kernel: #10 0xcf18fc14 at ieee80211_ioctl_set80211+0x7f4 Apr 25 03:04:05 lucy kernel: #11 0xcf19130e at ieee80211_ioctl+0x25e Apr 25 03:04:05 lucy kernel: #12 0xc07d66a9 at in_control+0x1e9 Apr 25 03:04:05 lucy kernel: #13 0xc07bd93f at ifioctl+0x1a7f Apr 25 03:04:05 lucy kernel: #14 0xc0754655 at soo_ioctl+0x415 Apr 25 03:04:05 lucy kernel: #15 0xc074e6ad at kern_ioctl+0x21d Apr 25 03:04:05 lucy kernel: #16 0xc074e834 at sys_ioctl+0x134 Apr 25 03:04:05 lucy kernel: #17 0xc0987e80 at syscall+0x380 There's also some LORs with the bridging code: Apr 25 17:31:59 lucy kernel: lock order reversal: Apr 25 17:31:59 lucy kernel: 1st 0xcecb56f4 ath0_node_lock (ath0_node_lock) @ /usr/home/adrian/work/freebsd/net80211_tx/head/src/sys/modules/wlan/../../net80211/ieee80211_node.c:1416 Apr 25 17:31:59 lucy kernel: 2nd 0xcef0460c if_bridge (if_bridge) @ /usr/home/adrian/work/freebsd/stable/9/sys/modules/if_bridge/../../net/if_bridge.c:2211 Apr 25 17:31:59 lucy kernel: KDB: stack backtrace: Apr 25 17:31:59 lucy kernel: #0 0xc0734d1f at kdb_backtrace+0x4f Apr 25 17:31:59 lucy kernel: #1 0xc074aa85 at _witness_debugger+0x25 Apr 25 17:31:59 lucy kernel: #2 0xc074bd7f at witness_checkorder+0x86f Apr 25 17:31:59 lucy kernel: #3 0xc06e9de4 at _mtx_lock_flags+0xc4 Apr 25 17:31:59 lucy kernel: #4 0xc1107ab4 at bridge_input+0x64 Apr 25 17:31:59 lucy kernel: #5 0xc07bff64 at ether_nh_input+0x324 Apr 25 17:31:59 lucy kernel: #6 0xc07c355c at netisr_dispatch_src+0xcc Apr 25 17:31:59 lucy kernel: #7 0xc07c37d0 at netisr_dispatch+0x20 Apr 25 17:31:59 lucy kernel: #8 0xc07bf645 at ether_input+0x35 Apr 25 17:31:59 lucy kernel: #9 0xcf1c2c3d at hostap_deliver_data+0x2cd Apr 25 17:31:59 lucy kernel: #10 0xcf1c38ca at hostap_input+0xc6a Apr 25 17:31:59 lucy kernel: #11 0xcf1b6214 at ampdu_dispatch+0x44 Apr 25 17:31:59 lucy kernel: #12 0xcf1b62a4 at ampdu_rx_flush+0x84 Apr 25 17:31:59 lucy kernel: #13 0xcf1b707b at ieee80211_ht_node_age+0xab Apr 25 17:31:59 lucy kernel: #14 0xcf19c7ef at node_age+0x9f Apr 25 17:31:59 lucy kernel: #15 0xcf19ec8a at ieee80211_timeout_stations+0x21a Apr 25 17:31:59 lucy kernel: #16 0xcf19eff9 at ieee80211_node_timeout+0x39 Apr 25 17:31:59 lucy kernel: #17 0xc0713a59 at softclock+0x369 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 08:11:35 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 235AE14F; Sun, 28 Apr 2013 08:11:35 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id D519E1D0E; Sun, 28 Apr 2013 08:11:34 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 906264AC57; Sun, 28 Apr 2013 12:11:31 +0400 (MSK) Date: Sun, 28 Apr 2013 12:11:22 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1887397692.20130428121122@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 28 Apr 2013 08:11:35 -0000 Hello, Adrian. You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 22:56:30: >> AC> You're not doing something like leaving bgscan enabled, or not >> AC> defining a channel up front? >> Here is my config: > >> ifconfig_wlan0=3D"inet 192.168.135.1 netmask 255.255.255.0 mode 11ng cha= nnel 3:ht/40 -bgscan ssid home.serebryakov.spb.ru country DE regdomain row = txpower 30" AC> Is it a bridge? If so, put an IP address on the bridge, not wlan0. I don't have bridge, it is true router, to have strong separation between WiFi and wired network. AC> thus i do the inet line after _all_ other things are done, and on a AC> separate line. Two lines for one interface? Or just move "inet" part to end of this line? AC> Anyway, leave it how it is for now. Just update to the latest -HEAD AC> ath code and redo the testing. It will now log the whole TX queue AC> contents, not just the completed frames. Hopefully it'll be more AC> obvious. Ok, today later. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 18:50:17 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 85010686; Sun, 28 Apr 2013 18:50:17 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 542741126; Sun, 28 Apr 2013 18:50:15 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id E596C4AC57; Sun, 28 Apr 2013 22:50:06 +0400 (MSK) Date: Sun, 28 Apr 2013 22:50:06 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1467048277.20130428225006@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------05F0631F60EBC40C1" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2013 18:50:17 -0000 ------------05F0631F60EBC40C1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Adrian. You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 22:56:30: AC> Anyway, leave it how it is for now. Just update to the latest -HEAD AC> ath code and redo the testing. It will now log the whole TX queue AC> contents, not just the completed frames. Hopefully it'll be more AC> obvious. Ok, same test: UDP stream from AP to client (with iperf), limited to 300M. Only 11-30M seen by client now, but no beacon stucks. After AP hangs several forced beacon stucks + hostaptd restart allow client to re-associate. Log with dev.ath.0.debug=3D0x900000020 attached ("sudo" messages are left= as "time marks"). -- // Black Lion AKA Lev Serebryakov ------------05F0631F60EBC40C1-- From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 19:32:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3DE777CB; Sun, 28 Apr 2013 19:32:09 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id EE93C1253; Sun, 28 Apr 2013 19:32:08 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 30CFD4AC57; Sun, 28 Apr 2013 23:32:07 +0400 (MSK) Date: Sun, 28 Apr 2013 23:32:05 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1182481344.20130428233205@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1887397692.20130428121122@serebryakov.spb.ru> <27137701.20130428223854@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 28 Apr 2013 19:32:09 -0000 Hello, Adrian. You wrote 28 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 23:15:23: AC> Yeah, can you see why 11n wasn't negotiated and repeat the test? Ok, rebooted both AP and client. Client/Windows says (via connection properties) it is "240Mbit/s", AP/FreeBSD says (via ifconfig list sta): ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG c4:85:08:3f:9e:c2 1 3 270M 22.0 0 14972 4880 EPS AQEHTRM SSID<= home.serebryakov.spb.ru> RATES XRATES<48,72,96,1= 08> RSN HTCAP WME But throughput is no more than 30Mbit again... It is very strange... AC> I'll go over what you gave me but what you did give me has 500 frames AC> in the TX queue. That's a lot of frames to go over. :) When I stop "sending" iperf "receiving" part shows some traffic for about 5 seconds after it :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 19:38:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 355549DC; Sun, 28 Apr 2013 19:38:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by mx1.freebsd.org (Postfix) with ESMTP id 9402A128C; Sun, 28 Apr 2013 19:38:21 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id k13so3210245wgh.7 for ; Sun, 28 Apr 2013 12:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Ekejyixzld1AS0T6d5W7esXg0aza1S5c3EsRHj/Coyk=; b=mqe3N2nXGihV2qBWGn/udojBz3k0MnR8LyYj1ml88H/tgguu/dVWUxOSJe4kdnVljP lD+ixYUYbwglhERLZDRcKt+PuN0vggJMk8EClgFfuA3sSBi9Vt85x1IRPSqOA2QZkMMd 86OO9y5boWvd0XUwBlNTENBkBK9XcXVb9X67Jjwn9ymrR0bJcEn/06mZ4MWijYDOGB/q G0XxNGuJV+tzu35cwLWAyeQ9l42zg5z04bXoJlOIc781rTeQEBhHZhUoAAiH9bU/KUBT UTtG7LfInc6WiClFhMsdqJm36sWUuQPLyoqB34IyVMvoxIjPEjBViHIpDFtIbjQZUQiL eefQ== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr11499468wjb.36.1367177900170; Sun, 28 Apr 2013 12:38:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sun, 28 Apr 2013 12:38:20 -0700 (PDT) In-Reply-To: <1467048277.20130428225006@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> Date: Sun, 28 Apr 2013 12:38:20 -0700 X-Google-Sender-Auth: X8JGHuP_3zAlDmQi8mXWdncp-9g Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2013 19:38:22 -0000 On 28 April 2013 11:50, Lev Serebryakov wrote: > 300M. Only 11-30M seen by client now, but no beacon stucks. > After AP hangs several forced beacon stucks + hostaptd restart > allow client to re-associate. Right. That's likely because 11n aggregation wasn't enabled. I don't know why. > Log with dev.ath.0.debug=0x900000020 attached ("sudo" messages are left as > "time marks"). Cool, thanks. It's odd. The descriptor list(s) look fine - ie, the descriptors aren't out of order or anything. (Ie, the descriptor and link pointers line up with the order that the ath_buf's are in the TXQ.) And the descriptors in your particular setup aren't chained into multi-descriptor lists, they're one descriptor per frame. There used to be bugs with my 11n TX code and which ath_buf to check the status of in a list of ath_bufs, but this last test is with no aggregation. So that's not a problem. The next step is seeing whether the hardware queue is actually just plain stuck, or whether it's idle. If it's idle, it may just be waiting for another call to ath_hal_txstart() or whatever the call is to re-trigger it. The only reason it would be idle like that though is if it hit the end of the descriptor list at about the same time we appended a frame to the list. However, every time we append a frame to the hardware queue, we also call ath_hal_txstart() to re-kick TX. There's some race condition hack that Sam threw in that gets enabled only if you compile things with TDMA support enabled. Would you mind compiling in TDMA support (add options IEEE80211_SUPPORT_TDMA) to your kernel config and rebuild? I'd like to see if that TX queue workaround is effective at helping us out here. Does this happen with tcp iperf? or only udp iperf? adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 19:41:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4ABBEB90; Sun, 28 Apr 2013 19:41:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 0611812A5; Sun, 28 Apr 2013 19:41:38 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id B4EB04AC57; Sun, 28 Apr 2013 23:41:33 +0400 (MSK) Date: Sun, 28 Apr 2013 23:41:33 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <979648529.20130428234133@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.sp b.ru> <1467048277.20130428225006@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 28 Apr 2013 19:41:39 -0000 Hello, Adrian. You wrote 28 =E0=EF=F0=E5=EB=FF 2013 =E3., 23:38:20: AC> There's some race condition hack that Sam threw in that gets enabled AC> only if you compile things with TDMA support enabled. Would you mind AC> compiling in TDMA support (add options IEEE80211_SUPPORT_TDMA) to your AC> kernel config and rebuild? I'd like to see if that TX queue workaround AC> is effective at helping us out here. I'm building it right now. It is good, that only kernel rebuild is fast. AC> Does this happen with tcp iperf? or only udp iperf? First time it was with tcp (some time ago). I could check this too. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 19:49:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DA59ACB9; Sun, 28 Apr 2013 19:49:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by mx1.freebsd.org (Postfix) with ESMTP id 4556712DC; Sun, 28 Apr 2013 19:49:39 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id c10so2143461wiw.8 for ; Sun, 28 Apr 2013 12:49:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=HC0wgzl7tdwq9habT9crrzjr1qLKWRhFyEjvS9mW1Yo=; b=mNClSUyif+SjySHVrpX2nclV8Y6y/0eo1zkIOm1jTgiEp9m1kh+dT/tln9G00vsSIN JwUFmDb1oSK/iFaI4isFgrfWdub9O7bkSAbb9HOgPh7ZTf+1l61VZgGsWDa0YaVvIsI9 x0f8u8yzukhKdMLamwlmnif309x6qEtuN2WtvzHEEExopRAF5DdSdpiCnqXA4Xr4L3fX u7LwAp4F03B9yd89PAGPyUShTcihwd+CGzXP2nhQbe49hFxCaaE602aV/nsbBfLpdUkp Rb5ovNZnVt75o+B1ZSR6vJg07SUywmK8UybLc9uZ8JWOqnqGJ+rbwOwmXpQaPWdg3D8s 5cLA== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr11527606wjb.36.1367178578359; Sun, 28 Apr 2013 12:49:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sun, 28 Apr 2013 12:49:38 -0700 (PDT) In-Reply-To: <15710249844.20130428234801@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <15710249844.20130428234801@serebryakov.spb.ru> Date: Sun, 28 Apr 2013 12:49:38 -0700 X-Google-Sender-Auth: WFvcZD78utCYvvmRSFXWVb6gEj4 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2013 19:49:39 -0000 .. how's this never triggered a clang warning on me before? Just add casts for now or something so it compiles. Adrian On 28 April 2013 12:48, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 28 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 23:38:20: > > AC> There's some race condition hack that Sam threw in that gets enabled > AC> only if you compile things with TDMA support enabled. Would you mind > AC> compiling in TDMA support (add options IEEE80211_SUPPORT_TDMA) to you= r > AC> kernel config and rebuild? I'd like to see if that TX queue workaroun= d > AC> is effective at helping us out here. > Oooopps... And, yes, it is really annoying, that there is no good way > to specify (u_)?int\d\d?_t in printf() :( > > cc -c -O2 -pipe -fno-strict-aliasing -std=3Dc99 -Wall -Wredundant-decls= -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmis= sing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compar= e -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/= data/src/sys -I/data/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HE= ADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcm= odel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchrono= us-unwind-tables -ffreestanding -fstack-protector -Werror /data/src/sys/de= v/ath/if_ath_tdma.c -I/data/src/sys/dev/ath > /data/src/sys/dev/ath/if_ath_tdma.c:442:42: error: format specifies type = 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned l= ong') [-Werror,-Wformat] > (unsigned long long) rs->rs_tstamp, rstamp, tsf, txtime, > ^~~~~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:442:50: error: format specifies type = 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned l= ong') [-Werror,-Wformat] > (unsigned long long) rs->rs_tstamp, rstamp, tsf, txtime, > ^~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:443:6: error: format specifies type '= unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned lo= ng') [-Werror,-Wformat] > nextslot, nextslottu, TSF_TO_TU(nextslot >> 32, nextslot)); > ^~~~~~~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:446:6: error: format specifies type '= unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned lon= g') [-Werror,-Wformat] > le64toh(ni->ni_tstamp.tsf), > ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > /data/src/sys/sys/endian.h:80:20: note: expanded from macro 'le64toh' > #define le64toh(x) ((uint64_t)(x)) > ^ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:447:6: error: format specifies type '= unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned lon= g') [-Werror,-Wformat] > le64toh(ni->ni_tstamp.tsf)); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > /data/src/sys/sys/endian.h:80:20: note: expanded from macro 'le64toh' > #define le64toh(x) ((uint64_t)(x)) > ^ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:451:6: error: format specifies type '= unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned lo= ng') [-Werror,-Wformat] > nexttbtt, > ^~~~~~~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:545:7: error: format specifies type '= unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned lon= g') [-Werror,-Wformat] > tsf, > ^~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DP= RINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > 7 errors generated. > *** [if_ath_tdma.o] Error code 1 > 1 error > *** [buildkernel] Error code 2 > 1 error > *** [buildkernel] Error code 2 > 1 error > > > > -- > // Black Lion AKA Lev Serebryakov > From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 20:14:51 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 435BDD3; Sun, 28 Apr 2013 20:14:51 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 002691360; Sun, 28 Apr 2013 20:14:50 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 0E7D54AC57; Mon, 29 Apr 2013 00:14:48 +0400 (MSK) Date: Mon, 29 Apr 2013 00:14:47 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <576676154.20130429001447@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <15710249844.20130428234801@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 28 Apr 2013 20:14:51 -0000 Hello, Adrian. You wrote 28 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 23:49:38: AC> .. how's this never triggered a clang warning on me before? AC> Just add casts for now or something so it compiles. Testing... One more datapoint: with this option bsnmpd with wlan plugin complains: Apr 29 00:09:46 gateway snmpd[1712]: iface wlan0 - get param: ioctl(201) fa= iled: Operation not supported Apr 29 00:09:46 gateway snmpd[1712]: iface wlan0 - get param: ioctl(202) fa= iled: Operation not supported Apr 29 00:09:46 gateway snmpd[1712]: iface wlan0 - get param: ioctl(203) fa= iled: Operation not supported Apr 29 00:09:46 gateway snmpd[1712]: iface wlan0 - get param: ioctl(204) fa= iled: Operation not supported And bandwidth still low... --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 28 20:44:00 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87B17291; Sun, 28 Apr 2013 20:44:00 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4F1221431; Sun, 28 Apr 2013 20:43:59 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 103F24AC57; Mon, 29 Apr 2013 00:43:52 +0400 (MSK) Date: Mon, 29 Apr 2013 00:43:52 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <725880393.20130429004352@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.sp b.ru> <1467048277.20130428225006@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------0EF021037256C03D5" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 28 Apr 2013 20:44:00 -0000 ------------0EF021037256C03D5 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Hello, Adrian. You wrote 28 =E0=EF=F0=E5=EB=FF 2013 =E3., 23:38:20: AC> There's some race condition hack that Sam threw in that gets enabled AC> only if you compile things with TDMA support enabled. Would you mind AC> compiling in TDMA support (add options IEEE80211_SUPPORT_TDMA) to your AC> kernel config and rebuild? I'd like to see if that TX queue workaround AC> is effective at helping us out here. Two logs for UDP, first time I forgot to stop sender, and second don't, but it doesnt' help :) AC> Does this happen with tcp iperf? or only udp iperf? Same with UDP. Cannot repeat with TCP. --=20 // Black Lion AKA Lev Serebryakov ------------0EF021037256C03D5-- From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 07:29:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CB3CA305; Mon, 29 Apr 2013 07:29:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 3653E1B7F; Mon, 29 Apr 2013 07:29:33 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id x43so4995196wey.39 for ; Mon, 29 Apr 2013 00:29:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0pNFdOtAxlWUAyZdG005qDq4E72vSb7NBS55Y4bXUO8=; b=nFKYgDZG5R02gAXdGSSLhNh58kuzFdXB5K8HLvCmVEaU9FptkpWTJGobl+6OxrkVcm ZgqN8Ofr7Db7iDeHtdodcxBO8Sr4bFxdtdR+YDompnRL3UOA2Rnlr24qgTpuP9UjAb15 3dctrVDi34jj0LWlX0nzdQ5pClxvy4j/bBI6FgsSISkvRbplkKmuCMc1PfaJWaiMZBPq SqG7QM8/IbOGTgkI8izLWFIx6fEQIUxhqpCZXTUURusUh6YLPvH9lEF17i8+NRoh4EEs I4ui8Gv8v+X4UYKvpzXU8bLPLvmWpV4lqNIogbBvSD6fZV0ZQV+M+bHARcj00nmKR0eL 1MXA== MIME-Version: 1.0 X-Received: by 10.180.72.228 with SMTP id g4mr15577940wiv.22.1367220572295; Mon, 29 Apr 2013 00:29:32 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Mon, 29 Apr 2013 00:29:32 -0700 (PDT) In-Reply-To: <725880393.20130429004352@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> Date: Mon, 29 Apr 2013 00:29:32 -0700 X-Google-Sender-Auth: V6APJjB66t2yXyMsQJYdqbB_qcw Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 07:29:33 -0000 Please update to -HEAD first! And erm, run iperf tcp first, before udp. That way aggregation is negotiated. :-) adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 07:30:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5CC2B328; Mon, 29 Apr 2013 07:30:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id B07A81B86; Mon, 29 Apr 2013 07:30:01 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id i48so2015943wef.20 for ; Mon, 29 Apr 2013 00:30:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=P3ImSv3a+4Arv7+mg0JZAGahKhR5jyOksrFPsCfAewU=; b=py2OKBjWePuELtvAy6p5Mvm2VKU0WHJ2ch37R+6iaYYX4qLR6jPh48k0KsWUchwRFq fHpWDW+3uTSwuxOTJ+FdfdPyKrJ47ndeP8Mkky3K+6dPJOws11HRgyL7TceStpDkLsmK kSRDd3wJV4qkbsHSIedPihLnhwxj18D5MEtwaia97sqfDaZ2rRBISNAqsPP7Nne1LdZL GkbgsqI8mO9ZCD1jctxMJ/WEvoO2xMLAk6pAo4gP4ugM7Z6tnkv7F2S9faZsgG7Hrdqh QVFOyJ3+5XInm3O7Yrmm1xoNtPJH8s+LDJJMdRfNyihMFiQiZBShKWIoDfEOojWr6bTG HPDw== MIME-Version: 1.0 X-Received: by 10.180.149.200 with SMTP id uc8mr15645805wib.3.1367220600853; Mon, 29 Apr 2013 00:30:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Mon, 29 Apr 2013 00:30:00 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> Date: Mon, 29 Apr 2013 00:30:00 -0700 X-Google-Sender-Auth: zAcClc5pvBMd4XDqWtCCLwBGgkM Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 07:30:02 -0000 .. well, please update to -HEAD; I've just added some more debugging to the reset path to see what the state of the hardware queue is. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 07:36:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E0BCF3DA; Mon, 29 Apr 2013 07:36:27 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9CA791BC1; Mon, 29 Apr 2013 07:36:27 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 5B9054AC57; Mon, 29 Apr 2013 11:36:24 +0400 (MSK) Date: Mon, 29 Apr 2013 11:36:23 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <187241224.20130429113623@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 29 Apr 2013 07:36:27 -0000 Hello, Adrian. You wrote 29 =E0=EF=F0=E5=EB=FF 2013 =E3., 11:29:32: AC> Please update to -HEAD first! Ok :) These test were on r250017. AC> And erm, run iperf tcp first, before udp. That way aggregation is AC> negotiated. :-) Ok. But on previous revisions it was not needed. But previous tests were done no at Sunday night, and at Sunday night environment is worst here. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 07:49:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6AEB66B8; Mon, 29 Apr 2013 07:49:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by mx1.freebsd.org (Postfix) with ESMTP id CA5F71C37; Mon, 29 Apr 2013 07:49:04 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id e11so3305574wgh.25 for ; Mon, 29 Apr 2013 00:49:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YqI7G+EDM6unqhbN4Rt3UONldjHQ2gVVNB1ldN7x5Gw=; b=wG42edVdPDJ/SdRKC/nEG94BSmUI43dmWmta88bRJzYMqT9EuDmiNLJ5PaFeMpgxAe 9LoKm/+HZ5ubOx7MJA2wCFAwO8vHE9dw5TMkjixyyKU3vwXFBlp/q48TX8MXlYs/Giul sD8ReSQCvBh6MZZdW1pTVDp309idHPyw9ubNErLfNjiq8t7Q78FT9EAV4RTYsKi2wl+A F3tolDsyXSNAulyhUP/kG4m7rzexqm56FV6K0MP6k+3abFF6t3SwqmxV8K2RXFJMorl5 95e8GhSCkmcsFj4DlyNLPzrzWI/uO5Lcrv4AwXWnLdbh8ARKQJ/F1MpB2GPPc+JY/dzi 8plA== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr15698452wib.22.1367221743753; Mon, 29 Apr 2013 00:49:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Mon, 29 Apr 2013 00:49:03 -0700 (PDT) In-Reply-To: <187241224.20130429113623@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> Date: Mon, 29 Apr 2013 00:49:03 -0700 X-Google-Sender-Auth: 1XQFsUmwkeb437SyvQE6jiXH_1s Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 07:49:05 -0000 There's likely some bugs with the AMPDU aggregation negotiating kicking in when all the TX buffers are full. I thought that was fixed, alas. I'll investigate that later. I have to acquire some programmable attenuators to do this. adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 10:14:57 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 647548B7 for ; Mon, 29 Apr 2013 10:14:57 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id B0BE715E1 for ; Mon, 29 Apr 2013 10:14:56 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id r3TAEnP2061317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Apr 2013 12:14:54 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id r3TAEnsD061316 for wireless@freebsd.org; Mon, 29 Apr 2013 12:14:49 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Mon, 29 Apr 2013 12:14:49 +0200 From: Paul Schenkeveld To: wireless@freebsd.org Subject: State os VAP support Message-ID: <20130429101449.GA27298@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 10:14:57 -0000 Hi, I still cannot get VAP's to work, perhaps I'm doing something wrong, perhaps VAP support isn't ready yet. My hardware: Soekris net4826 with Atheros 5212 mini-pci card My FreeBSD: FreeBSD 10.0-CURRENT #0 r249745 My config: wlans_ath0="wlan63 wlan207" create_args_wlan63="wlanmode hostap mode 11g channel 7 country NL" create_args_wlan207="wlanmode hostap mode 11g channel 7 country NL" hostapd_config="/etc/hostapd.conf.testB /etc/hostapd.conf.testO" ==== hostapd.conf.testB: driver=bsd interface=wlan63 ctrl_interface=/var/run/hostapd.wlan63 ctrl_interface_group=wheel ssid=testB wpa=1 wpa_passphrase=******** wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP TKIP ==== hostapd.conf.testO: driver=bsd interface=wlan207 ctrl_interface=/var/run/hostapd.wlan207 ctrl_interface_group=wheel ssid=testO wpa=1 wpa_passphrase=******** wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP TKIP I have tried running a single hostapd with two config files and running two separate hostapd daemons each with a config file. In both cases, I get one wlan working, the other does not work. Running hostapd with -d does not reveal the problem to me either (I see debug output when connecting to the working wlan but not when trying to connect to the other one). Hostapd debug output is below. My questions: Should VAP work at all? Does anyone know of VAP problems with the Atheros 5212? Should I run one hostapd with multiple config files or separate daemons? Anything else I'm doing wrong? Thanks for any help! Paul Schenkeveld ------------------------------------------------------------------------ hostapd -d output: ap1# hostapd -P /var/run/hostapd.pid -d /etc/hostapd.conf.testB /etc/hostapd.conf.testO Configuration file: /etc/hostapd.conf.testB ctrl_interface_group=0 (from group name 'wheel') BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) Completing interface initialization Flushing old station entries Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 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 Using interface wlan63 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testB' Deriving WPA PSK based on passphrase SSID - hexdump_ascii(len=5): 74 65 73 74 42 testB PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: enable WPA= 0x1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 bsd_set_privacy: enabled=1 bsd_set_opt_ie: set WPA+RSN ie (len 28) wlan63: Setup of interface done. Configuration file: /etc/hostapd.conf.testO ctrl_interface_group=0 (from group name 'wheel') BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) Completing interface initialization Flushing old station entries Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 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 Using interface wlan207 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testO' Deriving WPA PSK based on passphrase SSID - hexdump_ascii(len=5): 74 65 73 74 4f testO PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: enable WPA= 0x1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 bsd_set_privacy: enabled=1 bsd_set_opt_ie: set WPA+RSN ie (len 28) wlan207: Setup of interface done. Discard routing message to if#0 (not for us 10) Discard routing message to if#0 (not for us 11) Discard routing message to if#0 (not for us 10) From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 11:06:54 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D4AF2411 for ; Mon, 29 Apr 2013 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C4CDE193B for ; Mon, 29 Apr 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r3TB6swf018335 for ; Mon, 29 Apr 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r3TB6sIZ018333 for freebsd-wireless@FreeBSD.org; Mon, 29 Apr 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Apr 2013 11:06:54 GMT Message-Id: <201304291106.r3TB6sIZ018333@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 11:06:54 -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/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175870 wireless [iwn] /etc/rc.d/netif restart cause system crash o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 158 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 29 16:16:10 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E87B1D19 for ; Mon, 29 Apr 2013 16:16:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by mx1.freebsd.org (Postfix) with ESMTP id 7810A1E62 for ; Mon, 29 Apr 2013 16:16:10 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id m15so3884811wgh.29 for ; Mon, 29 Apr 2013 09:16:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=g4tpaiQdWQZQiPiNnPjpk8upim4X/z0PSnyU5exdqXE=; b=R1MhBFw9qXfjibZsqise5uFT2/za9zxrxuK98AlqCZZRR+dRVsIrGGaAb/fY5ByEbm l4PGDQ8wOZw33U3vLvCTu6oaC+3JFpanEfW698OpHfr7BQqXivOciHasdkTcQdWf5nQp 3cQJXf1mLSUko72LD3EEmzYGfufS0+HvY8YdvplvbiPpt9B0VcInXosoeO9FbgzF7PNs wEFnmezS96z0Erx2jyBzyr4aNTJGGNgybjN/fZ4j+ReVK2sj+YhbIbD+UwL5LJH+3sft 9a3iTr/cvGsusR3hZLYL8i0D1R8hZdjmEV2vatJS5otT4pSqVgjp6YmHKcNOsKNIvg7N 3I0g== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr97956255wjb.56.1367252169565; Mon, 29 Apr 2013 09:16:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Mon, 29 Apr 2013 09:16:09 -0700 (PDT) In-Reply-To: <20130429101449.GA27298@psconsult.nl> References: <20130429101449.GA27298@psconsult.nl> Date: Mon, 29 Apr 2013 09:16:09 -0700 X-Google-Sender-Auth: nq4wfQL_1naAd6VwbGYyLKbfJAc Message-ID: Subject: Re: State os VAP support From: Adrian Chadd To: Paul Schenkeveld Content-Type: text/plain; charset=ISO-8859-1 Cc: wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 16:16:11 -0000 Multiple VAPs should be working. Doubly so on the AR5212 series hardware. adrian On 29 April 2013 03:14, Paul Schenkeveld wrote: > Hi, > > I still cannot get VAP's to work, perhaps I'm doing something wrong, > perhaps VAP support isn't ready yet. > > My hardware: Soekris net4826 with Atheros 5212 mini-pci card > My FreeBSD: FreeBSD 10.0-CURRENT #0 r249745 > My config: > > wlans_ath0="wlan63 wlan207" > create_args_wlan63="wlanmode hostap mode 11g channel 7 country NL" > create_args_wlan207="wlanmode hostap mode 11g channel 7 country NL" > hostapd_config="/etc/hostapd.conf.testB /etc/hostapd.conf.testO" > > ==== hostapd.conf.testB: > driver=bsd > interface=wlan63 > ctrl_interface=/var/run/hostapd.wlan63 > ctrl_interface_group=wheel > ssid=testB > wpa=1 > wpa_passphrase=******** > wpa_key_mgmt=WPA-PSK > wpa_pairwise=CCMP TKIP > > ==== hostapd.conf.testO: > driver=bsd > interface=wlan207 > ctrl_interface=/var/run/hostapd.wlan207 > ctrl_interface_group=wheel > ssid=testO > wpa=1 > wpa_passphrase=******** > wpa_key_mgmt=WPA-PSK > wpa_pairwise=CCMP TKIP > > I have tried running a single hostapd with two config files and running > two separate hostapd daemons each with a config file. In both cases, I > get one wlan working, the other does not work. Running hostapd with -d > does not reveal the problem to me either (I see debug output when > connecting to the working wlan but not when trying to connect to the > other one). Hostapd debug output is below. > > My questions: > > Should VAP work at all? > Does anyone know of VAP problems with the Atheros 5212? > Should I run one hostapd with multiple config files or separate daemons? > Anything else I'm doing wrong? > > Thanks for any help! > > Paul Schenkeveld > > ------------------------------------------------------------------------ > > hostapd -d output: > > ap1# hostapd -P /var/run/hostapd.pid -d /etc/hostapd.conf.testB /etc/hostapd.conf.testO > Configuration file: /etc/hostapd.conf.testB > ctrl_interface_group=0 (from group name 'wheel') > BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) > Completing interface initialization > Flushing old station entries > Deauthenticate all stations > bsd_set_privacy: enabled=0 > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 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 > Using interface wlan63 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testB' > Deriving WPA PSK based on passphrase > SSID - hexdump_ascii(len=5): > 74 65 73 74 42 testB > PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] > PSK (from passphrase) - hexdump(len=32): [REMOVED] > bsd_set_ieee8021x: enabled=1 > bsd_configure_wpa: enable WPA= 0x1 > WPA: group state machine entering state GTK_INIT (VLAN-ID 0) > GMK - hexdump(len=32): [REMOVED] > GTK - hexdump(len=32): [REMOVED] > WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) > bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 > bsd_set_privacy: enabled=1 > bsd_set_opt_ie: set WPA+RSN ie (len 28) > wlan63: Setup of interface done. > Configuration file: /etc/hostapd.conf.testO > ctrl_interface_group=0 (from group name 'wheel') > BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) > Completing interface initialization > Flushing old station entries > Deauthenticate all stations > bsd_set_privacy: enabled=0 > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 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 > Using interface wlan207 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testO' > Deriving WPA PSK based on passphrase > SSID - hexdump_ascii(len=5): > 74 65 73 74 4f testO > PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] > PSK (from passphrase) - hexdump(len=32): [REMOVED] > bsd_set_ieee8021x: enabled=1 > bsd_configure_wpa: enable WPA= 0x1 > WPA: group state machine entering state GTK_INIT (VLAN-ID 0) > GMK - hexdump(len=32): [REMOVED] > GTK - hexdump(len=32): [REMOVED] > WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) > bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 > bsd_set_privacy: enabled=1 > bsd_set_opt_ie: set WPA+RSN ie (len 28) > wlan207: Setup of interface done. > Discard routing message to if#0 (not for us 10) > > Discard routing message to if#0 (not for us 11) > > Discard routing message to if#0 (not for us 10) > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 04:53:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3B619E75; Tue, 30 Apr 2013 04:53:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id 9AD271ABC; Tue, 30 Apr 2013 04:53:01 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id t11so89413wey.9 for ; Mon, 29 Apr 2013 21:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=FlZsxaaj+c6Vh/Q/0WSwWV9VoXDdXcUyMa2+fha/csU=; b=BsVJojS8jR0DHFFFdZSvbQ3bvAaM7XIDtTHBdnvtulYKGzHA4MD8MSO6k4eNqQfCSi O3c5wlAUMKlRfEIPuV8Gxl8nKvvaO9m8naTKxu16715TaOIhRwT49Vnub0klJx5vADYD W1/8in1MZoB4xJOEd+f4kQilnz9xAGO+HOjISb5gDmOJfCQMAqCAm3YWlfcs9jJ+M88E 1gWzGuyZNaRtJ04z7usJUmVf1XdqMUl+Or8zSaFO12k+1kEIH1s8d2d3KLGkucGQn+ne BwjZGKKnrnk1SQtAZT4mUE5tgRca49N+35pEgVTN0wcUn0i9A7+IntYu/JSZ/G3FtoyC Przw== MIME-Version: 1.0 X-Received: by 10.180.212.3 with SMTP id ng3mr1143715wic.22.1367297580700; Mon, 29 Apr 2013 21:53:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Mon, 29 Apr 2013 21:53:00 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> Date: Mon, 29 Apr 2013 21:53:00 -0700 X-Google-Sender-Auth: xC0N91Hn9CtQrk0tjz0Am2UIwjg Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 04:53:02 -0000 Any follow-up with the latest stuff in -HEAD? I'd like to see if the hardware queue is behaving how I think it is. Adrian On 29 April 2013 00:49, Adrian Chadd wrote: > There's likely some bugs with the AMPDU aggregation negotiating > kicking in when all the TX buffers are full. I thought that was fixed, > alas. > > I'll investigate that later. I have to acquire some programmable > attenuators to do this. > > > > adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 08:25:04 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EA36E34F; Tue, 30 Apr 2013 08:25:04 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 77E7B1269; Tue, 30 Apr 2013 08:25:04 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 211694AC57; Tue, 30 Apr 2013 12:25:02 +0400 (MSK) Date: Tue, 30 Apr 2013 12:24:59 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <124956607.20130430122459@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1467048277.20130428225006@serebryakov.s pb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------0121790D21751CE77" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 30 Apr 2013 08:25:05 -0000 ------------0121790D21751CE77 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Hello, Adrian. You wrote 30 =E0=EF=F0=E5=EB=FF 2013 =E3., 8:53:00: AC> Any follow-up with the latest stuff in -HEAD? I'd like to see if the AC> hardware queue is behaving how I think it is. Sorry, was busy yesterday. Sources: r250041, TDMA is enabled in kernel config. Warm-up: 120 seconds of TCP, throughput osculate between 50 and 100Mbit/, several BAR resets, no hangs. Test: 600 seconds of UDP. Throughput is 20Mbit/s. Hang on ~327s. traffic generator stopped, single "forced bstuck" helps. Log attached. Please, note: low throughput for UDP on these revisions. It was not so on older revisions, before all this additional debug stuff was added, latest good I tried was something like r249333, and I don't remember about r249767 (but I could try, firmware image is not removed, and I don't have images between r249333 and r249333). --=20 // Black Lion AKA Lev Serebryakov ------------0121790D21751CE77-- From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 14:26:41 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5C126430 for ; Tue, 30 Apr 2013 14:26:41 +0000 (UTC) (envelope-from purpleritza@gmail.com) Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by mx1.freebsd.org (Postfix) with ESMTP id EE43D1629 for ; Tue, 30 Apr 2013 14:26:40 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id a12so508237wgh.23 for ; Tue, 30 Apr 2013 07:26:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=V7NQryRD7e1NboYRsPWF8tDCIwJqz2+am+PhpSAveUo=; b=fEfHz/1zELOBEaPXwFNRF/wzZiyv1qVFMuRrWa2WZirlzP00H+wMWpCupQL8jRGTwE 7j8JMhUOj8fRdrAIm+B85ZrY+RsjskPefVJBUh9MRAs3zFrDUah01PuHdhcMMqsJE0/T g9t1dc890oqoWFOUehU82mBQ6AW70+mS1A6jYcb11bP5JHSavfU3pyNKcCTxzX+KdICg OPCfnXa+uNfZTP16AzwFMJIy+09uoNtnqv0DTwwdfEWzkurGKYp/bdTKDVnZKOT7PlFT 91o5CELpqDexNum/VDGh33pcIQi2W9s/J7S9QFg/ItW5ys0fanQXUBnNXZfTsnBCg3+8 fFRQ== MIME-Version: 1.0 X-Received: by 10.180.212.3 with SMTP id ng3mr4356285wic.22.1367332000203; Tue, 30 Apr 2013 07:26:40 -0700 (PDT) Received: by 10.194.133.168 with HTTP; Tue, 30 Apr 2013 07:26:40 -0700 (PDT) Received: by 10.194.133.168 with HTTP; Tue, 30 Apr 2013 07:26:40 -0700 (PDT) Date: Tue, 30 Apr 2013 16:26:40 +0200 Message-ID: Subject: Problem with new laptop's ral0 (Ralink 5390) From: Goran Tepshic To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 14:26:41 -0000 Hi, i have a problem with my new laptop Asus X55VD which has Ralink's RT5390 chip. I described the problem here: http://forums.freebsd.org/showthread.php?t=39259 Can someone help or suggest anything, i'd really like to run FreeBSD on this lappy and learn it from scratch. Thanks, p0 From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 15:28:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 09740687 for ; Tue, 30 Apr 2013 15:28:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 9E1B81911 for ; Tue, 30 Apr 2013 15:28:08 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id m6so4063504wiv.7 for ; Tue, 30 Apr 2013 08:28:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xTlF1ndEjsL2zmxVQ1fy8FjnoB1fxtUS1L1T+B5pEzA=; b=gXUF0mY6EgC7eo2TCL/zpfuRnWdCNWup4UYsK+YqQCvdQP3uJpegFPKbQJMzuJuQt2 kxGTZ0jowvJVOLO8zo2ZS4a2HvyB3V+m4Ti8trxU+m3dIUem6Z/F4YyDOEDM3tLYUZIs cefqEXj/3x9j/S6zOIvD5wjk+e0Myt/P51Kl4KUSpuTBAKftnawXR6zj9jIpSIiAMHNf C9+fqyvBJDiRPJMBq92jGU2LhOWhS7nDgqOcPX/kgMRcdchEKhPcJEE+tJLfVozzxJ/z GWAYrfHysvowP3F1o1rGotIzC/nKBnOtRgLtmdgpPen7EylHZnT8iO/ziGABAHS+nkPZ HzYQ== MIME-Version: 1.0 X-Received: by 10.180.149.200 with SMTP id uc8mr25540682wib.3.1367335687880; Tue, 30 Apr 2013 08:28:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 08:28:07 -0700 (PDT) In-Reply-To: References: Date: Tue, 30 Apr 2013 08:28:07 -0700 X-Google-Sender-Auth: Rm2oq5kbPpEAZ6lqE1tUdBZ8_DA Message-ID: Subject: Re: Problem with new laptop's ral0 (Ralink 5390) From: Adrian Chadd To: Goran Tepshic Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 15:28:09 -0000 Try doing 'up' instead of 'up scan'; does it still lock up? Adrian On 30 April 2013 07:26, Goran Tepshic wrote: > Hi, i have a problem with my new laptop Asus X55VD which has Ralink's > RT5390 chip. > > I described the problem here: > > http://forums.freebsd.org/showthread.php?t=39259 > > Can someone help or suggest anything, i'd really like to run FreeBSD on > this lappy and learn it from scratch. > > Thanks, > p0 > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 15:31:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F1494757 for ; Tue, 30 Apr 2013 15:31:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by mx1.freebsd.org (Postfix) with ESMTP id 91B571A3E for ; Tue, 30 Apr 2013 15:31:24 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id m6so680124wiv.3 for ; Tue, 30 Apr 2013 08:31:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sfu22uRF0F010qrbKlSc24uZsv6w62FngLNetzp0pwc=; b=DJfkd1VaxB4l68sd1N937wz+1S4kXT0Et/y3gjI/PsAOeDGC4WQ749+fdW6i29B5FM jOUWKozfa059hpOHPI3C8aVO0A2PaabfAFqRl15j2BtPai8hfHJtIa0RjOTV422lcTNx Dsq8Bgr5fvggdpXnyYTDo5Z75f2/jD4Zd8zd1iyeRkN2EKce6mUUl+CpjknK339KAYHl 7sR+0Y5pjUp3VBiaOq8BAGikMdlqvGwNn3blWcOPM+OtEbpyQNXzEYlJWcUOUcuuCe/b apUmzF9DrX/M45L2z99l9DGgIfSut2yQSsWc16rxDgBN6sknOnLl+1vJ19V23d/BODiQ 8TjA== MIME-Version: 1.0 X-Received: by 10.180.89.140 with SMTP id bo12mr8098523wib.22.1367335883375; Tue, 30 Apr 2013 08:31:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 08:31:23 -0700 (PDT) In-Reply-To: References: Date: Tue, 30 Apr 2013 08:31:23 -0700 X-Google-Sender-Auth: 6a48aaSco-y50BzHDfuBbK7fB7U Message-ID: Subject: Re: Problem with new laptop's ral0 (Ralink 5390) From: Adrian Chadd To: Goran Tepshic Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 15:31:25 -0000 Hi, I've no idea, unfortunately. You'd have to start adding kernel printfs in the driver to see when the driver locks up. I can't be much more help than that at the moment, sorry :( Adrian On 30 April 2013 08:29, Goran Tepshic wrote: > Adrian, yes, exactly. Not sure why. > > On Apr 30, 2013 5:28 PM, "Adrian Chadd" wrote: >> >> Try doing 'up' instead of 'up scan'; does it still lock up? >> >> >> >> Adrian >> >> On 30 April 2013 07:26, Goran Tepshic wrote: >> > Hi, i have a problem with my new laptop Asus X55VD which has Ralink's >> > RT5390 chip. >> > >> > I described the problem here: >> > >> > http://forums.freebsd.org/showthread.php?t=39259 >> > >> > Can someone help or suggest anything, i'd really like to run FreeBSD on >> > this lappy and learn it from scratch. >> > >> > Thanks, >> > p0 >> > _______________________________________________ >> > freebsd-wireless@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> > To unsubscribe, send any mail to >> > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 15:39:22 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DDB21B8E; Tue, 30 Apr 2013 15:39:22 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 4CC251AAD; Tue, 30 Apr 2013 15:39:22 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id r3UFdFN5085445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Apr 2013 17:39:20 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id r3UFdFia085444; Tue, 30 Apr 2013 17:39:15 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Tue, 30 Apr 2013 17:39:15 +0200 From: Paul Schenkeveld To: Adrian Chadd Subject: Re: State os VAP support Message-ID: <20130430153915.GA21457@psconsult.nl> References: <20130429101449.GA27298@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 15:39:22 -0000 On Mon, Apr 29, 2013 at 09:16:09AM -0700, Adrian Chadd wrote: > Multiple VAPs should be working. Doubly so on the AR5212 series hardware. > > adrian Thanks Adrian. When I start two separate hostapd daemons with the config files from my previous post (and separate pidfiles), only the first one works. Starting them in the opposite order, only the other one works so I am (almost) sure that the config files by themselves are correct. Please help! With kind regards, Paul Schenkeveld > On 29 April 2013 03:14, Paul Schenkeveld wrote: > > Hi, > > > > I still cannot get VAP's to work, perhaps I'm doing something wrong, > > perhaps VAP support isn't ready yet. > > > > My hardware: Soekris net4826 with Atheros 5212 mini-pci card > > My FreeBSD: FreeBSD 10.0-CURRENT #0 r249745 > > My config: > > > > wlans_ath0="wlan63 wlan207" > > create_args_wlan63="wlanmode hostap mode 11g channel 7 country NL" > > create_args_wlan207="wlanmode hostap mode 11g channel 7 country NL" > > hostapd_config="/etc/hostapd.conf.testB /etc/hostapd.conf.testO" > > > > ==== hostapd.conf.testB: > > driver=bsd > > interface=wlan63 > > ctrl_interface=/var/run/hostapd.wlan63 > > ctrl_interface_group=wheel > > ssid=testB > > wpa=1 > > wpa_passphrase=******** > > wpa_key_mgmt=WPA-PSK > > wpa_pairwise=CCMP TKIP > > > > ==== hostapd.conf.testO: > > driver=bsd > > interface=wlan207 > > ctrl_interface=/var/run/hostapd.wlan207 > > ctrl_interface_group=wheel > > ssid=testO > > wpa=1 > > wpa_passphrase=******** > > wpa_key_mgmt=WPA-PSK > > wpa_pairwise=CCMP TKIP > > > > I have tried running a single hostapd with two config files and running > > two separate hostapd daemons each with a config file. In both cases, I > > get one wlan working, the other does not work. Running hostapd with -d > > does not reveal the problem to me either (I see debug output when > > connecting to the working wlan but not when trying to connect to the > > other one). Hostapd debug output is below. > > > > My questions: > > > > Should VAP work at all? > > Does anyone know of VAP problems with the Atheros 5212? > > Should I run one hostapd with multiple config files or separate daemons? > > Anything else I'm doing wrong? > > > > Thanks for any help! > > > > Paul Schenkeveld > > > > ------------------------------------------------------------------------ > > > > hostapd -d output: > > > > ap1# hostapd -P /var/run/hostapd.pid -d /etc/hostapd.conf.testB /etc/hostapd.conf.testO > > Configuration file: /etc/hostapd.conf.testB > > ctrl_interface_group=0 (from group name 'wheel') > > BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) > > Completing interface initialization > > Flushing old station entries > > Deauthenticate all stations > > bsd_set_privacy: enabled=0 > > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 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 > > Using interface wlan63 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testB' > > Deriving WPA PSK based on passphrase > > SSID - hexdump_ascii(len=5): > > 74 65 73 74 42 testB > > PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] > > PSK (from passphrase) - hexdump(len=32): [REMOVED] > > bsd_set_ieee8021x: enabled=1 > > bsd_configure_wpa: enable WPA= 0x1 > > WPA: group state machine entering state GTK_INIT (VLAN-ID 0) > > GMK - hexdump(len=32): [REMOVED] > > GTK - hexdump(len=32): [REMOVED] > > WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) > > bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 > > bsd_set_privacy: enabled=1 > > bsd_set_opt_ie: set WPA+RSN ie (len 28) > > wlan63: Setup of interface done. > > Configuration file: /etc/hostapd.conf.testO > > ctrl_interface_group=0 (from group name 'wheel') > > BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) > > Completing interface initialization > > Flushing old station entries > > Deauthenticate all stations > > bsd_set_privacy: enabled=0 > > bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 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 > > Using interface wlan207 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testO' > > Deriving WPA PSK based on passphrase > > SSID - hexdump_ascii(len=5): > > 74 65 73 74 4f testO > > PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] > > PSK (from passphrase) - hexdump(len=32): [REMOVED] > > bsd_set_ieee8021x: enabled=1 > > bsd_configure_wpa: enable WPA= 0x1 > > WPA: group state machine entering state GTK_INIT (VLAN-ID 0) > > GMK - hexdump(len=32): [REMOVED] > > GTK - hexdump(len=32): [REMOVED] > > WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) > > bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 > > bsd_set_privacy: enabled=1 > > bsd_set_opt_ie: set WPA+RSN ie (len 28) > > wlan207: Setup of interface done. > > Discard routing message to if#0 (not for us 10) > > > > Discard routing message to if#0 (not for us 11) > > > > Discard routing message to if#0 (not for us 10) > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 15:41:14 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7A03FBDA; Tue, 30 Apr 2013 15:41:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id DE8561AC3; Tue, 30 Apr 2013 15:41:13 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so4346927wie.3 for ; Tue, 30 Apr 2013 08:41:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=22p+eIyAk+tlrPhVnr5OxKZk6sf3FfmZmX7hilTCfXM=; b=c58gPqGA3CXUcAmVjNNK1fXV0VoO9Q6E0CrLWS6DEffl5xyusGMdNjWNtQ5MP0u+xG BV6feeeULQP6VQiXgAdjpSPuhQPGR95z9xQRfdNWH2e7Y798sv/8m+z7GZQys0l1Ayv4 XTxxSigTSZmehXSoRtVzYIek/2pjTJH7prqqO7hkkdYaYkmm5csl2V8/7ec43fwp7lMS 6UUko07taWMdNSd8NqlXLqrkCpsDL+2ixIhvqbdVOXJtusVNmTKR/B+Rlape8z/nddN+ bUtmWlweocMlqwYPJpU1E6QXkBF6JMJ7Q3AIg7n30JFzT0BvL2T7v2BWpIaksOkyHC41 Cdyg== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr23665300wjb.36.1367336473086; Tue, 30 Apr 2013 08:41:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 08:41:12 -0700 (PDT) In-Reply-To: <124956607.20130430122459@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> Date: Tue, 30 Apr 2013 08:41:12 -0700 X-Google-Sender-Auth: rmSIB_VV2mJrAE5C5a6qfBRmRr0 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 15:41:14 -0000 On 30 April 2013 01:24, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 30 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 8:53:00: > > AC> Any follow-up with the latest stuff in -HEAD? I'd like to see if the > AC> hardware queue is behaving how I think it is. > Sorry, was busy yesterday. > Sources: r250041, TDMA is enabled in kernel config. Ok. > Warm-up: 120 seconds of TCP, throughput osculate between 50 and > 100Mbit/, several BAR resets, no hangs. Ok. But did it negotiate A-MPDU? > Test: 600 seconds of UDP. Throughput is 20Mbit/s. Hang on ~327s. > traffic generator stopped, single "forced bstuck" helps. > > Log attached. > > > Please, note: low throughput for UDP on these revisions. It was not > so on older revisions, before all this additional debug stuff was > added, latest good I tried was something like r249333, and I don't > remember about r249767 (but I could try, firmware image is not > removed, and I don't have images between r249333 and r249333). It's fine. We'll worry about aggregation later. So here we go: Apr 30 12:21:26 gateway kernel: ath0: ath_stoptxdma: tx queue [9] 0xd8c3000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [0] 0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [1] 0xc720ed00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [2] 0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [3] 0xd8bec00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [8] 0xc720d2c0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Notice how the hardware queue isn't active at all. There's frames in the TXQ and the hardware points to the next frame to transmit (but you didn't provide the whole list of frames that were in the TXQ, so I'm going on what it said before.) Hm.. Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 17:13:38 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 019C2200; Tue, 30 Apr 2013 17:13:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id CE7181F3A; Tue, 30 Apr 2013 17:13:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r3UHDbMv088369; Tue, 30 Apr 2013 17:13:37 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r3UHDbTx088368; Tue, 30 Apr 2013 17:13:37 GMT (envelope-from linimon) Date: Tue, 30 Apr 2013 17:13:37 GMT Message-Id: <201304301713.r3UHDbTx088368@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/178263: [ath] review the use of ic_freq / ic_ieee / ic_flags / ichan->channel X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 17:13:38 -0000 Synopsis: [ath] review the use of ic_freq / ic_ieee / ic_flags / ichan->channel Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Tue Apr 30 17:13:29 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178263 From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 17:25:48 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BC75344B; Tue, 30 Apr 2013 17:25:48 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 780A81FBD; Tue, 30 Apr 2013 17:25:48 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id r3UHPgYQ055192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Apr 2013 19:25:47 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id r3UHPgpO055191; Tue, 30 Apr 2013 19:25:42 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Tue, 30 Apr 2013 19:25:42 +0200 From: Paul Schenkeveld To: Adrian Chadd Subject: [SOLVED] Re: State os VAP support Message-ID: <20130430172542.GB21457@psconsult.nl> References: <20130429101449.GA27298@psconsult.nl> <20130430153915.GA21457@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130430153915.GA21457@psconsult.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 17:25:48 -0000 On Tue, Apr 30, 2013 at 05:39:15PM +0200, Paul Schenkeveld wrote: > On Mon, Apr 29, 2013 at 09:16:09AM -0700, Adrian Chadd wrote: > > Multiple VAPs should be working. Doubly so on the AR5212 series hardware. > > > > adrian > > Thanks Adrian. > > When I start two separate hostapd daemons with the config files from my > previous post (and separate pidfiles), only the first one works. > Starting them in the opposite order, only the other one works so I am > (almost) sure that the config files by themselves are correct. > > Please help! I just found a new version of hostapd in /usr/ports/net/hostapd. This one seems to work! I'm running a single daemon and two config files and have clients connected to both SSID's. Thanks! With kind regards, Paul Schenkeveld From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 18:03:21 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 69479B4 for ; Tue, 30 Apr 2013 18:03:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by mx1.freebsd.org (Postfix) with ESMTP id 0A8E3115B for ; Tue, 30 Apr 2013 18:03:20 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id y10so767163wgg.9 for ; Tue, 30 Apr 2013 11:03:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ioRK3L5uf+34FsUJxXJgZTsir6j8Q+oXGwr3UitUhRc=; b=iSos2sgAOmdh9q1io5oAPaWENI0eL1TGv/UJZ1G4P8bTN7xgtMv2AJsCifWAECdasn KPcsEH/o4MUhFI8+VYMX8+3L4gVsrV89O++UcfDfxRWX7Dq6q5rb6w3SlVDTLJg5P/J6 8EQqmOsbIPuEhRBZ7oaPNOI394MnyZI9YIonoxiE/8/RHGFR0wnmFzLnw2q0/9iCh8kS gx33PlHAmjaUFNGetKUere8EHr1IdKarIhOim7IKqKHiZuhDabw3QsD4MaJAlu/Yr211 aPJVaZ2POYBOSSdOzUvMSbvGBkFv2esN6f+jL2hEdJRFH5aLRyZWSD1lEYzVKvQCdINb iGJg== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr24572723wjb.36.1367345000276; Tue, 30 Apr 2013 11:03:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 11:03:20 -0700 (PDT) In-Reply-To: <20130430172542.GB21457@psconsult.nl> References: <20130429101449.GA27298@psconsult.nl> <20130430153915.GA21457@psconsult.nl> <20130430172542.GB21457@psconsult.nl> Date: Tue, 30 Apr 2013 11:03:20 -0700 X-Google-Sender-Auth: Ap5aj593-daRo8InVBpyG4JurmU Message-ID: Subject: Re: [SOLVED] Re: State os VAP support From: Adrian Chadd To: Paul Schenkeveld Content-Type: text/plain; charset=ISO-8859-1 Cc: wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 18:03:21 -0000 Would you please file a PR? The hostapd in the base system should support this with no problems. I've tested this multiple times with no ill effects. Thanks, Adrian On 30 April 2013 10:25, Paul Schenkeveld wrote: > On Tue, Apr 30, 2013 at 05:39:15PM +0200, Paul Schenkeveld wrote: >> On Mon, Apr 29, 2013 at 09:16:09AM -0700, Adrian Chadd wrote: >> > Multiple VAPs should be working. Doubly so on the AR5212 series hardware. >> > >> > adrian >> >> Thanks Adrian. >> >> When I start two separate hostapd daemons with the config files from my >> previous post (and separate pidfiles), only the first one works. >> Starting them in the opposite order, only the other one works so I am >> (almost) sure that the config files by themselves are correct. >> >> Please help! > > I just found a new version of hostapd in /usr/ports/net/hostapd. This > one seems to work! I'm running a single daemon and two config files and > have clients connected to both SSID's. Thanks! > > With kind regards, > > Paul Schenkeveld From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 20:07:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7244FEC2; Tue, 30 Apr 2013 20:07:27 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 2A10615F1; Tue, 30 Apr 2013 20:07:26 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id DFC234AC57; Wed, 1 May 2013 00:07:17 +0400 (MSK) Date: Wed, 1 May 2013 00:07:14 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <146903383.20130501000714@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 30 Apr 2013 20:07:27 -0000 Hello, Adrian. You wrote 30 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 19:41:12: >> Warm-up: 120 seconds of TCP, throughput osculate between 50 and >> 100Mbit/, several BAR resets, no hangs. AC> Ok. But did it negotiate A-MPDU? I'm not sure. Both ends showed typical N speeds (Windows in connection properties, FreeBSD in "list sta"). AC> It's fine. We'll worry about aggregation later. Yep. AC> So here we go: AC> Apr 30 12:21:26 gateway kernel: ath0: ath_stoptxdma: tx queue [9] AC> 0xd8c3000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [0] 0, AC> active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [1] AC> 0xc720ed00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [2] 0, AC> active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [3] AC> 0xd8bec00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [8] AC> 0xc720d2c0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 AC> Notice how the hardware queue isn't active at all. There's frames in AC> the TXQ and the hardware points to the next frame to transmit (but you AC> didn't provide the whole list of frames that were in the TXQ, so I'm AC> going on what it said before.) I've provided everything I've had in log :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 22:17:54 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9DE64F73; Tue, 30 Apr 2013 22:17:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 0744F1C38; Tue, 30 Apr 2013 22:17:53 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id h11so4446675wiv.8 for ; Tue, 30 Apr 2013 15:17:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qthXf9a46Q9uQaC99eW47Iw+T/DZhf/4wpxco6DPH5k=; b=U+Jlj7GedBrJe5noIx9yg3x5DeffLNHFxcLOPJuq6e2kOim1eVwV/j1b5kSyIIfRqA mT6gnd4d7aGpp70gM7MQycUKd5v1TLvwwLc8iCrGjWxa2Uk/ZLAl/VabH6q9w8kdf18V zQKMERqbScE98MfD7LSFiate2yJ8EULvJLm7omddXDnC36hgMFlzuION7xTYePiXUsF6 kyQdkZvhfxnTt4iktRK5poKCN02cKkiwrROzBwlUeIwcDFdYE0fxSwuRt0T8HyrCsQKQ i4/XuQatozDjSJI+gmnI8RanFIBykwjd3+85no7AXLaN6TZ+v7gSZTE11E5USvid8FUV FW1w== MIME-Version: 1.0 X-Received: by 10.194.248.200 with SMTP id yo8mr226287wjc.36.1367360273165; Tue, 30 Apr 2013 15:17:53 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 15:17:52 -0700 (PDT) In-Reply-To: <146903383.20130501000714@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> Date: Tue, 30 Apr 2013 15:17:52 -0700 X-Google-Sender-Auth: 6-gEHvVGewW4UpC7fuJADqQvvzw Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 22:17:54 -0000 Well, right now I'm trying to figure out whether there's a race condition in setting up / enabling the TX queue that I haven't yet seen before, or whether we've hit another one of those corner case bugs in the TX queue handling. I may add in a hack to the completion code that checks if the queue isn't active and if it isn't (but there's frames in the TX queue), it restarts TX. adrian From owner-freebsd-wireless@FreeBSD.ORG Wed May 1 09:32:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0106E8A8; Wed, 1 May 2013 09:32:27 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id B105F142A; Wed, 1 May 2013 09:32:26 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c5e0:df4d:ce7d:bcd9]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 90D234AC57; Wed, 1 May 2013 13:32:24 +0400 (MSK) Date: Wed, 1 May 2013 13:32:20 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <94204652.20130501133220@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.sp b.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org 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, 01 May 2013 09:32:27 -0000 Hello, Adrian. You wrote 1 =EC=E0=FF 2013 =E3., 2:17:52: AC> Well, right now I'm trying to figure out whether there's a race AC> condition in setting up / enabling the TX queue that I haven't yet AC> seen before, or whether we've hit another one of those corner case AC> bugs in the TX queue handling. I could do some additional experiments, if you need more data :) Really, I could add a tons of debug output if you send me a patch, to avoid spamming SVN with code for this particular case. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Wed May 1 15:04:28 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 423BF258; Wed, 1 May 2013 15:04:28 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by mx1.freebsd.org (Postfix) with ESMTP id 185211333; Wed, 1 May 2013 15:04:27 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id g10so851892pdj.6 for ; Wed, 01 May 2013 08:04:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1SECz6P13rBslE6UDmYbtxS8KPrOBixtReUs4A5rdr4=; b=tr0mD2JSUNfZSOceijYuk4kw6flEny/OtNR4J0FjPuYx2KgPSiXcdJgTs01g8kaPWA 2Z60oBKUdIE9HXj1XkXjM9UqMSilxgdjrZwNkliC+juWjzZtqlZlO6tqG0FINqPYiy9c O6UHxle7jze0eIn7Z8sOza8Jr3oy3MEHkj6iDbvWmbNjaT45QQGrMGv+malBQXuLunS3 nfsn1BHcQd9c56KrkXMFO9pYCHRLSDn/HsQbkhQk9bIYQX8VQdtmfDxPC4gPMAqcfM9h MzAlBOv+pIWQQkwinzJc4ZtjN/OSKxPocePyMdWnr+FrlMFNPOrfF+o9E0l2WP2SUJrz fdTw== X-Received: by 10.68.7.70 with SMTP id h6mr4537925pba.77.1367420667444; Wed, 01 May 2013 08:04:27 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPSA id pa2sm4000998pac.9.2013.05.01.08.04.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 May 2013 08:04:26 -0700 (PDT) Message-ID: <51812EEA.80806@gmail.com> Date: Wed, 01 May 2013 08:04:10 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Problem with new laptop's ral0 (Ralink 5390) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, Goran Tepshic X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 May 2013 15:04:28 -0000 On 04/30/13 08:31, Adrian Chadd wrote: > Hi, > > I've no idea, unfortunately. You'd have to start adding kernel printfs > in the driver to see when the driver locks up. I can't be much more > help than that at the moment, sorry :( > > > > Adrian > > > I'm not sure that chip is supported, at least it's news to me...the forum link seems to refer to inserting the pci ids for that chip into the ral driver. I can definitely see how forcing ral to attach to an unsupported device might hang or crash. I think this chip may be similiar to rt2860/rt3060/rt3090, as it looks like it uses the rt2800 driver in Linux. It also looks like they have only recently added support on the Linux side...and it's not that stable. I would look at the sources for any driver that does support this and see if they are having to do special conditionals to handle something specific with this chip, especially with register addresses or chip setup. It might be a good starting point for figuring out why ours doesn't work. My guess would be that invalid data is coming back from the eeprom (since addresses may have changed) and causing havoc. Is the MAC address correct? For what it's worth, the FreeBSD ral seems to be picky about devices...there are a lot of ral variants, but I think only those listed in the manpage are known to work. Adding more is going to be with a lot of printfs and testing, unfortunately. Matt From owner-freebsd-wireless@FreeBSD.ORG Wed May 1 16:07:16 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 79727AE; Wed, 1 May 2013 16:07:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by mx1.freebsd.org (Postfix) with ESMTP id D583F167E; Wed, 1 May 2013 16:07:15 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id l13so1660222wie.12 for ; Wed, 01 May 2013 09:07:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OaA4+A+zXT+/Q6kQbxWlVBZplK7Hc9rU7k4+T7LmhiE=; b=SulrqFOQrpbUpIkpjmEPu+5X9lCpUV3jfwg99+f3DJwr5tDZ4wZcL/0/cKZQjE+9OS DX8qV2l7zv/6vi5t3dAHfuAMBialD70aJHEOadr+1pTS5toKQhBhKRsw9Eyn1fRAKR/a qfMGrS9ts7EIpSR6SjiVKvcmamIAli7uakMzZbE5Y2dpZqwDES2eWngOhg8XEWG5Wu+S 6NVCsmH1WWAQzjj1Nn7P2/kKI+f6VrYfD5pxakLlsD9YaTbWXN8vLqB6nvLnTu0jZE1Y FyTQEnzwTVRuuzRpQ7Bc7d4AzZt9uzM5lpwIr6s7bN84a2NEsWDRctzSFAERTAeegNyM 7rXw== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr3405124wjb.56.1367424434925; Wed, 01 May 2013 09:07:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Wed, 1 May 2013 09:07:14 -0700 (PDT) In-Reply-To: <94204652.20130501133220@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> Date: Wed, 1 May 2013 09:07:14 -0700 X-Google-Sender-Auth: p7C86pXH70i8j8gjELy6b8ODlQo Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 May 2013 16:07:16 -0000 On 1 May 2013 02:32, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 1 =D0=BC=D0=B0=D1=8F 2013 =D0=B3., 2:17:52: > > AC> Well, right now I'm trying to figure out whether there's a race > AC> condition in setting up / enabling the TX queue that I haven't yet > AC> seen before, or whether we've hit another one of those corner case > AC> bugs in the TX queue handling. > I could do some additional experiments, if you need more data :) > Really, I could add a tons of debug output if you send me a patch, > to avoid spamming SVN with code for this particular case. I have enough data for now. :) and I'm all for adding more debuggig to the driver. ADrian From owner-freebsd-wireless@FreeBSD.ORG Wed May 1 16:18:11 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B7C1F5B5; Wed, 1 May 2013 16:18:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by mx1.freebsd.org (Postfix) with ESMTP id 2007F172C; Wed, 1 May 2013 16:18:10 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id m6so1671283wiv.3 for ; Wed, 01 May 2013 09:18:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=r4jVXVYYCQ/mAv7Y9/febe/VqVXOMAsbYwJJ2g2HkyU=; b=z6Bdq98lgOWRJZwu6ku2yP4xAfdK2lAdPMgVuwQTE6yC8DbCL2n9mncu0iCsqbib5O db7+GdvuRiIuT76Hhdxj7RqFAmwfkd2g9UdH+zsVHuUnXbFNyR9x5gXUb2/7R3ai3VvX VZgGlso1tL0N9sztitxWv0qwMi5knpexH2MVA+amCb3VHP5QNmbbPDWPay1RbuDGufUO kozEfwpLbkSfsvGz/lQ2lZr/5/YPWGUMj4s1erKa36MVdSJd+wCjbno0YRsSF7uxUj8r R1mv2cHXILJEKWWUCUlQs9/KZ/kGOuGRAAwT3jV2lg1COOiNzZTsa84IS7BLnu7m00gT 5fSw== MIME-Version: 1.0 X-Received: by 10.180.87.170 with SMTP id az10mr3527937wib.3.1367425090273; Wed, 01 May 2013 09:18:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Wed, 1 May 2013 09:18:10 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> Date: Wed, 1 May 2013 09:18:10 -0700 X-Google-Sender-Auth: QRs-_IZU2H4yeOAgGK1ybyMxM-c Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 May 2013 16:18:11 -0000 I'm trying to plan out how to potentially address this. I don't know whether it'll be enough to just set TXE to 1 for that queue and restart TX that way. I was hoping you'd post some more results with aggregate frames, but it doesn't seem to be happening. I'm hoping I don't have to stop the DMA for that queue and re-start it again. That's going to be relatively error-prone. ath9k and the reference driver have a bunch of workarounds to notice a stalled TX queue and restart things. I'm not really happy doing that; I'd rather try and fix the problem(s) before 10.0. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri May 3 01:54:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B908B3A2; Fri, 3 May 2013 01:54:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 85B2E105C; Fri, 3 May 2013 01:54:55 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id md12so645417pbc.30 for ; Thu, 02 May 2013 18:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=dU/X7cvnaO/Ur+yknFz3eud6ghTCnTTyutTrvqp3rx8=; b=VpQnnFAUv0SkRjuxKStRmwC5dhzC8WH3jsByIOjWfDTvD9NxDeTgkrn8IuQZil0QXS ynz8HRecT/DEVakY8ngrxAsWMM0xKDhMINo0j9ImUxbtIrEE3dSkdWbdQIikR8c0KqVH tTtnp4I4PaxC/NbaykKc1HCQ+3A4QI/nXg+Q6woNOFj/732TWzt4GwGjXKok1jGVNJA1 96UXaOzCQYYjuTUOvlaiqtP/kbgIWOCZIwsPcwS6wwtFwoQ3WToMLpOnEP/X6q3ZoeZb 7VHmtqUTrM2fa4AWRWtkdvAC8n9E6fJbk9ARXq6cXydVrgsoW1JuhAGHQNqM0ATGhLCa KF2g== MIME-Version: 1.0 X-Received: by 10.66.251.202 with SMTP id zm10mr8168231pac.53.1367546095215; Thu, 02 May 2013 18:54:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.46.198 with HTTP; Thu, 2 May 2013 18:54:54 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> Date: Thu, 2 May 2013 18:54:54 -0700 X-Google-Sender-Auth: Fl4bhH5n1JPhLCKbAzZ4Rp8PdHk Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 01:54:55 -0000 .. and I've now (mostly) successfully reproduced this here at home. I'll do some further digging. It may be that I just give in and add the TXQ stall workaround. I'd however like to avoid doing that if possible. :-) Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri May 3 04:22:41 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6C08C2BB; Fri, 3 May 2013 04:22:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-x22f.google.com (mail-da0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 364DC1530; Fri, 3 May 2013 04:22:41 +0000 (UTC) Received: by mail-da0-f47.google.com with SMTP id k13so618131dae.6 for ; Thu, 02 May 2013 21:22:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3JHLpmNIzQ5ur3XxBdFAXeQIKh2uMNVHKA5GA+kA3Jo=; b=zB5kFBbIt8h6LMTujxE8clDIuKCogQkuo9RdEjPuvFS5+IPhhrK5WBrjRn4uJHVTQq zk/v8wV+Ce3Zhm4WGfzZRYX7x+s56LQZJSKd66bQ5oEnLLqahq29tU6QED0tWC951DMt RgdlSNGimBW4s/SNLXwhxFngT5oP+ty86oZJo2WVr2JJWaoj+NG3WJA+Rl845it/oP69 RVPA6kMsqKTbQa49Hhr9bAbQp+NpV5fz7EEaZyJyXE8YcLD1wokblwD9fv9qgHW5LmJB LKKTBhVzIdij2neNwn0TF99CdQNTxEyT75E1cy/Xr5sYqx5CroEFUn7EQCZigRUuierO 097Q== MIME-Version: 1.0 X-Received: by 10.67.5.168 with SMTP id cn8mr13100894pad.119.1367554961037; Thu, 02 May 2013 21:22:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.46.198 with HTTP; Thu, 2 May 2013 21:22:40 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> Date: Thu, 2 May 2013 21:22:40 -0700 X-Google-Sender-Auth: ktC-920ZFS-hUDG9aecxooWsbtw Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 04:22:41 -0000 On 2 May 2013 18:54, Adrian Chadd wrote: > .. and I've now (mostly) successfully reproduced this here at home. > > I'll do some further digging. It may be that I just give in and add > the TXQ stall workaround. I'd however like to avoid doing that if > possible. :-) Hm, I'm reproducing it here and I see some odd descriptor behaviour. I'll tinker with it a bit more locally. There's at least one bug in the TX code to do with descriptor handling, but it didn't fix everything. I'll have to re-review things to make sure everything is handled in the correct order. I'll let you know when I have something to test! Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri May 3 08:28:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5D2A0B56; Fri, 3 May 2013 08:28:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 144B61DEB; Fri, 3 May 2013 08:28:18 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c5e0:df4d:ce7d:bcd9]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id DD2D74AC57; Fri, 3 May 2013 12:28:15 +0400 (MSK) Date: Fri, 3 May 2013 12:28:11 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <94971208.20130503122811@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 08:28:18 -0000 Hello, Adrian. You wrote 3 =EC=E0=FF 2013 =E3., 8:22:40: >> I'll do some further digging. It may be that I just give in and add >> the TXQ stall workaround. I'd however like to avoid doing that if >> possible. :-) AC> Hm, I'm reproducing it here and I see some odd descriptor behaviour. AC> I'll tinker with it a bit more locally. AC> There's at least one bug in the TX code to do with descriptor AC> handling, but it didn't fix everything. I'll have to re-review things AC> to make sure everything is handled in the correct order. AC> I'll let you know when I have something to test! Adrian! I want to thank you for your hard and fantastic work! If I visit USA (when I visit?) and will be near your place of living I want to buy your at least beer :) Or two :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sat May 4 04:06:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DDA893AE; Sat, 4 May 2013 04:06:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id 434AE126C; Sat, 4 May 2013 04:06:02 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id t11so1720282wey.23 for ; Fri, 03 May 2013 21:06:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gYA/KO6YQIigab6nVL5QOk2KoQYNcGGD8f1rdLUZ0HI=; b=xLDozKs1nrvHjsA+uVJRXp7G8mFIixqO0vr+wc4qqGlocLDgFnyKKSZMgarcQar1CB AMzGpheIh10u8Y+lalLnJSVYKoAiP1LKRyVHiDr9b5xSqLijdJkqf6dxLcZe2+zkLdd9 JKNXwxeGRBPc+Txlt5IBOwIPzzvt5GhA+6Jp389LLr20cPNghP8f2CAx2l1V4oyKZ1Sh st2hisi6uWOR2h/x7yEuI3IAKHmQpSVuie6YjEO2HB0T0UQ1NPwPvjtYghpk0k2H/fCH GKx9qbTn2vKTB7Bs9kkS5B4f+EXGOLg/0GwSehLLVL9njUb5MryzUWWAeAsQR89fQLY7 pTWA== MIME-Version: 1.0 X-Received: by 10.180.89.140 with SMTP id bo12mr730217wib.22.1367640361347; Fri, 03 May 2013 21:06:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 3 May 2013 21:06:01 -0700 (PDT) In-Reply-To: <94971208.20130503122811@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> <94971208.20130503122811@serebryakov.spb.ru> Date: Fri, 3 May 2013 21:06:01 -0700 X-Google-Sender-Auth: MjiT5Wl1rj_SSpmCx64ReAWq-Y4 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 04:06:02 -0000 Hi! Please update to the head -HEAD and test! I'm still debugging all of this and trying to understand what the other failure cases. Right now I'm seeing STA disassocications during UDP testing but it doesn't look like a stalled queue. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat May 4 05:09:16 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4D154A83; Sat, 4 May 2013 05:09:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id A4D2014B1; Sat, 4 May 2013 05:09:15 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id x51so1808816wey.14 for ; Fri, 03 May 2013 22:09:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2Q4m+SPzyC9bg3nkHsQkjn09kn9BvMnm9utByP50LPw=; b=EuOJCbxuEnSRkLwYmLfZ6IhYM89fNvWw+RmIRWqQPfY7Ngwk6RHsju9A+0Af3zhl8w nG2FdIDpx/7DLw8qo7HiZgVLKTKnz2TEIXLHB14THKvi2kDtz6L9kQGccRclxlv2QGm5 aE2rJQBuOsmxFT/peRwBDDWDp8x3KxBr2oLEAwco/0t1nnyNeokPz+zRdpwdBdHisrb7 TzIOU3gA5Sx2loTOTuHg0VxKDL8kn3fW0XAp9mWfx7CSiadbX9uRfUZrNwgqm5/d99ia 0mroCQRFhuKtC465WFdeo2vHot50ebGU06De+EfO4h/FLvxT+Ttk+nY+9I5S5dmTl6NJ 9a3w== MIME-Version: 1.0 X-Received: by 10.180.88.162 with SMTP id bh2mr906434wib.3.1367644154867; Fri, 03 May 2013 22:09:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 3 May 2013 22:09:14 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> <94971208.20130503122811@serebryakov.spb.ru> Date: Fri, 3 May 2013 22:09:14 -0700 X-Google-Sender-Auth: Y7vkfr1b1FHNTacFq4Xfze1RWTk Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 05:09:16 -0000 Hi, So doing this testing as a station doing the UDP transmitting (to a FreeBSD AP) is showing some interesting behaviour. No, i don't think it's your bug. The key re-negotiation seems to be failing somewhere; I bet it's out of sequence or out of order crypto frames. I've seen this happen before but I only fixed it for the AP case (by overriding the QOS for said frames so it appeared in a different TID, thus different sequence number space.) Since it's reauthing, it's transitioning the node through disassociate / re-auth / re-associate, but the current code in -HEAD isn't resetting the local state (aggregation, BAR state, filtered frames state, etc.) So things can and do go weird. I'll do some further digging into this and see if I can resolve it. I thought I had fixed it but .. well, obviously not. Once I have resolved this rekey / disconnect issue I'll keep testing things out and see if I've fixed your issue. (And I'll do some testing in parallel in open mode, so I don't bite this bug.) adrian From owner-freebsd-wireless@FreeBSD.ORG Sat May 4 17:14:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A8F21151; Sat, 4 May 2013 17:14:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 20D7C692; Sat, 4 May 2013 17:14:38 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id j13so1581994wgh.1 for ; Sat, 04 May 2013 10:14:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=b/hNn/VPLtoulG4IH3YlOQpAf7KNIAj40GY5nI3vvEE=; b=T9cn0+h6FDjKhLDgeL5RJ6RW/7JYzHuyYJ0HW+4MDm6wfn+prR9qJdoYtEyqTUdkU/ 46IVuhxp5JL4QeDQFOalGG3VTlyDp3JhciZ4QPpD9b4WAaYOFEx8gwYQWSjMmCE2ZpBb pISV4l1qqwsClwf0FyN4pJSDeK0oM4t+Q8FFg7zns4j09WrqTkXrdnGw1pFxSuoOFKJv c3RjSC7dTh8N7lmbXhHbAKgmJHFM5aRMpq+ADMu1eVWF+cgwuxmEpaVWbtQfGHTdpK0G OIXQy1ancPgNgWTQ2NUqHVn45HSE3nt726OKe6o+PWh3Pe8gja4jYvNKJDQN2dasUrgR HMzQ== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr18808161wjb.56.1367687678355; Sat, 04 May 2013 10:14:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sat, 4 May 2013 10:14:38 -0700 (PDT) Date: Sat, 4 May 2013 10:14:38 -0700 X-Google-Sender-Auth: n37umqOy0D6zBJIpHcMAguzyHaU Message-ID: Subject: Note: AR93xx support is now in -HEAD From: Adrian Chadd To: freebsd-wireless@freebsd.org, freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 17:14:39 -0000 Hi, I don't think I've posted this yet, but there's now support for these NICs in -HEAD: * AR9380 * AR9390 * AR9580 * AR9590 * AR9562 * QCA9565 The AR933x / AR934x SoC wifi is in -HEAD but it's not yet tidied up enough to actually work on those SoCs. But it's there. * What have I tested: * hostap mode * sta mode * monitor mode What doesn't work / haven't tested: * bluetooth, bluetooth coexistence * adhoc / ahdemo modes * mesh mode (although this should just work) * TDMA The support is enabled by default on -HEAD; so the next snapshot that we do will include support for all of the above NICs w/ 11n. Adrian