From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 01:21:03 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9FBD106566C for ; Sun, 22 Jul 2012 01:21:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8EFA68FC17 for ; Sun, 22 Jul 2012 01:21:03 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so9218079pbb.13 for ; Sat, 21 Jul 2012 18:21:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5d6EbDVbxRxxqBY2NP6VxrtLOaMp5IOdDf/o3Umlzj8=; b=IVCK8fyYJOo8zB4RZzBb/ustePNIEGu9P5D5gLh2kP4o6tBWSlxX0njktixt11u2P5 4PotL0YDqFeaQw1A6fSVpYaTjQBThDbZQXsgaOB6F3/LzoNh1BxqYuvO7Yv8WF4Sl1QE fAvxzzP7JpPdJIt2F4nnBAjnr8aS0L6HRbyiYQEon5pYmGc2lkaVBcRDMpaRCXhXFeXA FqKjo6gkrGahrDQlKOZTJpbCLxkoIG3xJJKYemh5/pqbsogk/3Pu39f/RiYg+QM4kBPK ZO9wUuYp94ncxpYjXbIe5QlySenPEHqqYBBGt4IUlz/2pEkEX8034+OSyasTwIdECwFd iSZQ== MIME-Version: 1.0 Received: by 10.68.201.9 with SMTP id jw9mr24815794pbc.28.1342920063149; Sat, 21 Jul 2012 18:21:03 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sat, 21 Jul 2012 18:21:03 -0700 (PDT) In-Reply-To: References: Date: Sat, 21 Jul 2012 18:21:03 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath lor X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 01:21:03 -0000 This is one of those known LORs in net80211. I'd love to get someone to help fix. :) adiran On 21 July 2012 13:18, Kim Culhan wrote: > Observed some instances of this lor: > > Jul 21 16:09:49 foo kernel: lock order reversal: > Jul 21 16:09:49 foo kernel: 1st 0xffffff8001ad3948 ath0_scan_lock > (ath0_scan_lock) @ /usr/src/sys/net80211/ieee8 > 0211_node.c:2166 > Jul 21 16:09:49 foo kernel: 2nd 0xffffff8001ad2018 ath0_com_lock > (ath0_com_lock) @ /usr/src/sys/net80211/ieee802 > 11_node.c:2518 > Jul 21 16:09:49 foo kernel: KDB: stack backtrace: > Jul 21 16:09:49 foo kernel: db_trace_self_wrapper() at > db_trace_self_wrapper+0x37 > Jul 21 16:09:49 foo kernel: kdb_backtrace() at kdb_backtrace+0x39 > Jul 21 16:09:49 foo kernel: witness_checkorder() at witness_checkorder+0xca1 > Jul 21 16:09:49 foo kernel: _mtx_lock_flags() at _mtx_lock_flags+0x79 > Jul 21 16:09:49 foo kernel: ieee80211_node_leave() at > ieee80211_node_leave+0x97 > Jul 21 16:09:49 foo kernel: ieee80211_iterate_nodes() at > ieee80211_iterate_nodes+0x89 > Jul 21 16:09:49 foo kernel: setmlme_common() at setmlme_common+0x408 > Jul 21 16:09:49 foo kernel: ieee80211_ioctl_setmlme() at > ieee80211_ioctl_setmlme+0x87 > Jul 21 16:09:49 foo kernel: ieee80211_ioctl_set80211() at > ieee80211_ioctl_set80211+0x5b0 > Jul 21 16:09:49 foo kernel: in_control() at in_control+0x234 > Jul 21 16:09:49 foo kernel: ifioctl() at ifioctl+0x148c > Jul 21 16:09:49 foo kernel: kern_ioctl() at kern_ioctl+0x1dc > Jul 21 16:09:49 foo kernel: sys_ioctl() at sys_ioctl+0x12e > Jul 21 16:09:50 foo kernel: amd64_syscall() at amd64_syscall+0x25a > Jul 21 16:09:50 foo kernel: Xfast_syscall() at Xfast_syscall+0xfb > Jul 21 16:09:50 foo kernel: --- syscall (54, FreeBSD ELF64, > sys_ioctl), rip = 0x801210dfc, rsp = 0x7fffffffda78, > rbp = 0x2a --- > Jul 21 16:09:50 foo kernel: ath0: stuck beacon; resetting (bmiss count 4) > > thanks > -kim From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 11:47:35 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 74EB7106566B for ; Sun, 22 Jul 2012 11:47:35 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 324498FC17 for ; Sun, 22 Jul 2012 11:47:35 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3438964qcs.13 for ; Sun, 22 Jul 2012 04:47:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=s+RrTyTMa1LHBqJl4Cx3rJ6RIHfjM8Zybhn/yqWIIWQ=; b=Q6KMcydErGNt3ZVT8uLK7T2hdyg3uivY76FODsARVcws4XIFucO2Grei7Z0OBzn0P5 aH2NZlYYialDNRXg7XBXtDS/PBa1UPKkRQ29Jx6nbHWTlTi6t7Elqh8W+3Y7/alWiHu5 wvMLCKLDrIVVjdBupuJ3q4n95WweUVxUywil2+GFI53dddZrvyhoP4kCCw2hkfoFFwte TQBla4JUdc+N/Rk9xQDHMocnRSTRRqn6bpVvEX9og6AD53QeIRpOSj4QFGujtFQq+/8y K0nYk6fsdWiRMzYKmNglbAAcZOIwqUGhorB1OsaDhy2K3xDyZ7bpMUQ1aBezwgb06Y1y /8JA== MIME-Version: 1.0 Received: by 10.224.189.137 with SMTP id de9mr19372438qab.7.1342957654271; Sun, 22 Jul 2012 04:47:34 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 04:47:34 -0700 (PDT) Date: Sun, 22 Jul 2012 07:47:34 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: net80211 LORs X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 11:47:35 -0000 On Sat, Jul 21, 2012 at 9:21 PM, Adrian Chadd wrote: > This is one of those known LORs in net80211. I'd love to get someone > to help fix. :) Through the many reboots done working on multi-ssid vap there were several hard hangs at reboot, around 1 in 3 reboots would hang this way. On the console when the system would hang would be the several lines associated with the net80211 LOR, followed by a last line referencing pflogd and promiscuous mode. -kim From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 13:11:49 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFBEE106566C for ; Sun, 22 Jul 2012 13:11:49 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 642908FC14 for ; Sun, 22 Jul 2012 13:11:49 +0000 (UTC) Received: by qabg1 with SMTP id g1so810212qab.13 for ; Sun, 22 Jul 2012 06:11:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uYlwitemdwYyU4OR4b2pqG4PaNavKH8SC9zToE8nNoE=; b=JPS8GypYkuEJS4zXM6hf8gxtJdLHy8p3PnpqTpeU8c0uCEjqTKTjdz+dWkef/Ud9vn 7ALLPOfc2Ouzw7Y9+dHAsXRNVy69OSD45l6rvBqylbgvo3a6n2WP3HNtQ/cnZjM5QhF+ ok96tHDpsX3OzK9tz7uw1FgGUtcPebH2dmfmS4z1V/OzRUJJmokLRvgHyHIIVUcnjk8D NxNpJSXR78E1UGDjcf5BBWLsmWGvIzKe1K6M6Zxj53ct1Q3ZbjU3NqN5Wn/rzHis/b/c bclJpnukuqmsXuQr98uXm+KDKsA16H26SSxceSv87osg1Ft74j0STSjBDzY6DnFJ4fF/ rfEg== MIME-Version: 1.0 Received: by 10.224.178.73 with SMTP id bl9mr16181757qab.89.1342962703137; Sun, 22 Jul 2012 06:11:43 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 06:11:43 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 09:11:43 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 13:11:49 -0000 On Sat, Jul 21, 2012 at 5:16 PM, Adrian Chadd wrote: > hi, > > Do you need 'bssid' on the ifconfig line? > > Can you provide the output of ifconfig -a when you create the good and > bad configuration? I'd like to see the bssid's. > > It's quite possible that the beacon timers and beacon slot allocation > is wrong, leading to issues. Here are some observations wrt configurations. 4 vaps, without bssid in config: create_args_wlan0="wlanmode hostap" .. create_args_wlan4="wlanmode hostap" Usually possible to connect with 2 of 4 vaps, the 2 'rotate' among the 4, some ssid's frequently not visible. ifconfig -a ath0: flags=8843 metric 0 mtu 2290 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running em0: flags=8943 metric 0 mtu 1500 options=2098 ether 00:0e:0c:7f:cf:02 inet6 fe80::20e:cff:fe7f:cf02%em0 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active re0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:1b:21:0a:a6:32 inet 1.2.3.4 netmask 0xfffffc00 broadcast 1.2.3.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:1e:8c:01:67:65 nd6 options=29 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.1e.8c.0.0.1.67.65.a.2.ff.fe.0.0.0.0 nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 bridge0: flags=8843 metric 0 mtu 1500 ether 02:f3:8d:7d:04:00 inet 10.0.0.3 netmask 0xff000000 broadcast 10.255.255.255 nd6 options=29 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: em0 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2000000 member: wlan3 flags=143 ifmaxaddr 0 port 11 priority 128 path cost 33333 member: wlan2 flags=143 ifmaxaddr 0 port 10 priority 128 path cost 33333 member: wlan1 flags=143 ifmaxaddr 0 port 9 priority 128 path cost 33333 member: wlan0 flags=143 ifmaxaddr 0 port 8 priority 128 path cost 33333 wlan0: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap1 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode OPEN privacy OFF txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan1: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap2 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan2: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap3 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan3: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap4 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 pflog0: flags=141 metric 0 mtu 33152 nd6 options=21 tap0: flags=8842 metric 0 mtu 1500 options=80000 ether 00:bd:f8:56:00:00 nd6 options=29 media: Ethernet autoselect status: active Opened by PID 2004 Same as above, with bss as: create_args_wlan0="wlanmode hostap bssid" .. create_args_wlan4="wlanmode hostap bssid" ssid's visible, usually possible to connect with 3 of 4 vaps, the 3 'rotate' among the 4 ifconfig -a ath0: flags=8843 metric 0 mtu 2290 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running em0: flags=8943 metric 0 mtu 1500 options=2098 ether 00:0e:0c:7f:cf:02 inet6 fe80::20e:cff:fe7f:cf02%em0 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active re0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:1b:21:0a:a6:32 inet 1.2.3.4 netmask 0xfffffc00 broadcast 1.2.3.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:1e:8c:01:67:65 nd6 options=29 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.1e.8c.0.0.1.67.65.a.2.ff.fe.0.0.0.0 nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 bridge0: flags=8843 metric 0 mtu 1500 ether 02:f3:8d:7d:04:00 inet 10.0.0.3 netmask 0xff000000 broadcast 10.255.255.255 nd6 options=29 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: em0 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2000000 member: wlan3 flags=143 ifmaxaddr 0 port 11 priority 128 path cost 33333 member: wlan2 flags=143 ifmaxaddr 0 port 10 priority 128 path cost 33333 member: wlan1 flags=143 ifmaxaddr 0 port 9 priority 128 path cost 33333 member: wlan0 flags=143 ifmaxaddr 0 port 8 priority 128 path cost 33333 wlan0: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap1 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode OPEN privacy OFF txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan1: flags=8943 metric 0 mtu 1500 ether fe:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap2 channel 6 (2437 MHz 11g ht/40+) bssid fe:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan2: flags=8943 metric 0 mtu 1500 ether fa:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap3 channel 6 (2437 MHz 11g ht/40+) bssid fa:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan3: flags=8943 metric 0 mtu 1500 ether fe:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap4 channel 6 (2437 MHz 11g ht/40+) bssid fe:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 pflog0: flags=141 metric 0 mtu 33152 nd6 options=21 tap0: flags=8842 metric 0 mtu 1500 options=80000 ether 00:bd:f1:5a:00:00 nd6 options=29 media: Ethernet autoselect status: active Opened by PID 2011 3 vaps, with bssid as: create_args_wlan0="wlanmode hostap bssid" .. create_args_wlan4="wlanmode hostap bssid" ssid's visible, usually possible to connect with all 3 vaps ifconfig -a ath0: flags=8843 metric 0 mtu 2290 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running em0: flags=8943 metric 0 mtu 1500 options=2098 ether 00:0e:0c:7f:cf:02 inet6 fe80::20e:cff:fe7f:cf02%em0 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active re0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:1b:21:0a:a6:32 inet 1.2.3.4 netmask 0xfffffc00 broadcast 1.2.3.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:1e:8c:01:67:65 nd6 options=29 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.1e.8c.0.0.1.67.65.a.2.ff.fe.0.0.0.0 nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 bridge0: flags=8843 metric 0 mtu 1500 ether 02:f3:8d:7d:04:00 inet 10.0.0.3 netmask 0xff000000 broadcast 10.255.255.255 nd6 options=29 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: em0 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2000000 member: wlan2 flags=143 ifmaxaddr 0 port 10 priority 128 path cost 33333 member: wlan1 flags=143 ifmaxaddr 0 port 9 priority 128 path cost 33333 member: wlan0 flags=143 ifmaxaddr 0 port 8 priority 128 path cost 33333 wlan0: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap1 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode OPEN privacy OFF txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan1: flags=8943 metric 0 mtu 1500 ether fe:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap2 channel 6 (2437 MHz 11g ht/40+) bssid fe:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan2: flags=8943 metric 0 mtu 1500 ether fa:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap3 channel 6 (2437 MHz 11g ht/40+) bssid fa:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 pflog0: flags=141 metric 0 mtu 33152 nd6 options=21 tap0: flags=8842 metric 0 mtu 1500 options=80000 ether 00:bd:7d:4a:00:00 nd6 options=29 media: Ethernet autoselect status: active Opened by PID 2105 3 vaps, without bssid in config as: create_args_wlan0="wlanmode hostap" .. create_args_wlan2="wlanmode hostap" ssid's visible, possible to connect with 1 vap, ssid ap1 ifconfig -a ath0: flags=8843 metric 0 mtu 2290 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running em0: flags=8943 metric 0 mtu 1500 options=2098 ether 00:0e:0c:7f:cf:02 inet6 fe80::20e:cff:fe7f:cf02%em0 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active re0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:1b:21:0a:a6:32 inet 1.2.3.4 netmask 0xfffffc00 broadcast 1.2.3.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:1e:8c:01:67:65 nd6 options=29 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.1e.8c.0.0.1.67.65.a.2.ff.fe.0.0.0.0 nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 bridge0: flags=8843 metric 0 mtu 1500 ether 02:f3:8d:7d:04:00 inet 10.0.0.3 netmask 0xff000000 broadcast 10.255.255.255 nd6 options=29 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: em0 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2000000 member: wlan2 flags=143 ifmaxaddr 0 port 10 priority 128 path cost 33333 member: wlan1 flags=143 ifmaxaddr 0 port 9 priority 128 path cost 33333 member: wlan0 flags=143 ifmaxaddr 0 port 8 priority 128 path cost 33333 wlan0: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap1 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode OPEN privacy OFF txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan1: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap2 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 wlan2: flags=8943 metric 0 mtu 1500 ether f8:d1:11:38:3c:e5 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid ap3 channel 6 (2437 MHz 11g ht/40+) bssid f8:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 pflog0: flags=141 metric 0 mtu 33152 nd6 options=21 tap0: flags=8842 metric 0 mtu 1500 options=80000 ether 00:bd:81:58:00:00 nd6 options=29 media: Ethernet autoselect status: active Opened by PID 1902 thanks -kim From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 15:22:16 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B11F1065672 for ; Sun, 22 Jul 2012 15:22:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5DB858FC08 for ; Sun, 22 Jul 2012 15:22:16 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so9984684pbb.13 for ; Sun, 22 Jul 2012 08:22:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QM3NAITJd/hSaskckZdcdGn+Xs0gi2PDTVTvXg+E5pQ=; b=lO9kmxImyHe3jYQcghfyu0yRqq8EAXYTD+maWmEks6uJ3niZfSGDH2VIbvhwiMTn4H 8/XhhyhMwy+rzPJINZ9jFpxWs8Akd/8qs+8Wetkip22zYvEkbd+pYG/0dGx7+Jw3S1Ns 9MhIIKU6eLMMmwZ9UcPdf0YgC8SFU80ZgmcAyirxiI5bCJ9B0y5wJ6K3p0ldp11amkq7 kSxsiNiaz5dx9JjZTf9lBry3S+ZAOMvwaACtou7HkRD2MpX8sbQ4J1/eXAPIBT/QLv75 sMNs5KXzjLPsLMtDCGF4k9M08mcQoATOIP/2YwsiW6kKHv0tUt3g5cQII4DiVqpcYEy1 4CMQ== MIME-Version: 1.0 Received: by 10.66.72.163 with SMTP id e3mr24635306pav.42.1342970536156; Sun, 22 Jul 2012 08:22:16 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 08:22:16 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 08:22:16 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 15:22:16 -0000 Hm, ok. So I'd start diagnosing this by setting up another FreeBSD device in monitor mode on that channel and capturing some beacons. Then take a look in wireshark and make sure you're seeing beacons consistently. I bet the beacon timer and beacon slot configuration is all subtly messed up, leading to this mess. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 15:26:25 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CFB8E106566C for ; Sun, 22 Jul 2012 15:26:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id A4B628FC18 for ; Sun, 22 Jul 2012 15:26:25 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so9988870pbb.13 for ; Sun, 22 Jul 2012 08:26:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7cJ6JW7nlnveaJdwCJR7+GME5N7wvTKaY3XtuYAbHVE=; b=xtwQojK/yQG1Ofd6tr3rLq/ksyaapGBWhAUNIy+ZNMPQ0VU8hgnbdfvu7YTx6U5irM O62SgmAgYffoWDtk0uU0AjrCEVDceSfdV/llLwkyp1RfsZMT6japwYSWYKaqo873Xln8 ccBw1/5VypBf+PC2Alp4yTP/k8ERwVPFcaPKQFhb+NK+/WT3Kt/nFiATzmEAs1oCUyEF ICt+zOF1VkTCBDdOpgYsmJChDq3EZBXuBGyVI3rt4DCZqnTVqWwAbrTkn7xFHlGtmEsK /gkTNUzYciTBw9K+Ac5g4l+0/mGXHlLH9bJHgu88OPTOw9Yh03hxslXqwlmPQyUgAkqC FxSQ== MIME-Version: 1.0 Received: by 10.68.222.163 with SMTP id qn3mr28358456pbc.135.1342970785472; Sun, 22 Jul 2012 08:26:25 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 08:26:25 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 08:26:25 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 LORs X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 15:26:25 -0000 On 22 July 2012 04:47, Kim Culhan wrote: > On Sat, Jul 21, 2012 at 9:21 PM, Adrian Chadd wrote: >> This is one of those known LORs in net80211. I'd love to get someone >> to help fix. :) > > Through the many reboots done working on multi-ssid vap there were several > hard hangs at reboot, around 1 in 3 reboots would hang this way. > > On the console when the system would hang would be the several lines > associated with the net80211 LOR, followed by a last line referencing > pflogd and promiscuous mode. Hm, are you able to break to the debugger when things have hung? Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 16:52:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 86EEA1065670 for ; Sun, 22 Jul 2012 16:52:09 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3C57F8FC14 for ; Sun, 22 Jul 2012 16:52:09 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3494499qcs.13 for ; Sun, 22 Jul 2012 09:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YEbI6T6XeO0NaB9xB1eP0Ss7IYUpRoqpM1qRU/EY65k=; b=kzKGbWZGAQH5VvOaQQrlR2l4GDxfHSp4fIlledFRo0XzikFReYGJ0e0sJZjswk+WAE 7y8hc3Sd8IbIQosZF62/L+i0TWe8WFPlg79k73NLWogTjR7G1SYTyOU6gbrUbTmfvjmH PgAm8XVOE2UKTxTT3qqzbOSUGBJ1wC6WG4NoXuXElOO1j4754OZD8/IWtSUf8xFKd+P9 hyGs20c6yGMykgwxD9zRJ0mPxt6FBHdJ+U/IUDheEPWlQNL9ZnvORXxPWS8Z1C3C/lSj YiTDOidIKGl8clVy9Q+H8sKPHcISbRWbBuDP0iXV6WEZ6e/8kE/1fEzWHdbTYCxsSpjh yQPg== MIME-Version: 1.0 Received: by 10.224.59.13 with SMTP id j13mr20387634qah.44.1342975928425; Sun, 22 Jul 2012 09:52:08 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 09:52:08 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 12:52:08 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 16:52:09 -0000 On Sun, Jul 22, 2012 at 11:22 AM, Adrian Chadd wrote: > Hm, ok. > > So I'd start diagnosing this by setting up another FreeBSD device in > monitor mode on that channel and capturing some beacons. > Then take a look in wireshark and make sure you're seeing beacons consistently. > > I bet the beacon timer and beacon slot configuration is all subtly > messed up, leading to this mess. Ah ok.. I'll work on setting up another FreeBSD machine. thanks -kim From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 16:53:28 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66DB9106564A for ; Sun, 22 Jul 2012 16:53:28 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 13A4A8FC08 for ; Sun, 22 Jul 2012 16:53:27 +0000 (UTC) Received: by qaat11 with SMTP id t11so849844qaa.13 for ; Sun, 22 Jul 2012 09:53:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=n6iSDqM6WGRqtUhToQLho0JsX/QjbLE0PJ70MUyTOzo=; b=MXNW6O3yF93ttJJHNNVbMb53aUd0usaKWSfZSXHd+3QvMxmTdEReY0pd75FnsM0BwB KGaI//1C725UpPFwqDC8DMM9LsJr1H1j1BusLVGLutkusDTDGnTG8xL7aXk6katfYCIk Vefe4omJ+Lb1aKr+poglwhG0nHea/Qg/YmxoZBftHan7bqUem2VWT7OtMZanAvzhGpqI +gYNt1bGxnNP81wQ1FOllQygi41+apt5aXg78FfC3zXqh4NHGkC5UgVdb/E29xR6VnUd 1vzJjaizGbU9zQq2mk+Zlcd9PtkEi1x1U0m4536rNm4+xnzbpg4WCU4spu787nfS8RWk oLIA== MIME-Version: 1.0 Received: by 10.224.101.193 with SMTP id d1mr20475517qao.20.1342976007433; Sun, 22 Jul 2012 09:53:27 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 09:53:27 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 12:53:27 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 16:53:28 -0000 On Sun, Jul 22, 2012 at 11:22 AM, Adrian Chadd wrote: > Hm, ok. > > So I'd start diagnosing this by setting up another FreeBSD device in > monitor mode on that channel and capturing some beacons. > Then take a look in wireshark and make sure you're seeing beacons consistently. > > I bet the beacon timer and beacon slot configuration is all subtly > messed up, leading to this mess. Oh and I'll need another 11n-capable card. -kim From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 18:20:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 238C2106566B for ; Sun, 22 Jul 2012 18:20:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E8C478FC0C for ; Sun, 22 Jul 2012 18:20:19 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so10164316pbb.13 for ; Sun, 22 Jul 2012 11:20:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xcZ4SfUON8njfsp6bVUufXSciMleLiMmF5VaOR/G5yQ=; b=Hote2AtUH7CW8WwltX14JlcDRWlR19WLfpOd/0vSWxOtUh/rpeM8kS3/gq+YBpYH2Y oEdAZ/jKPj2B4c2ghF9vh8j+AOdPVsq4yZgVbzuseD7UEi2h33Nz5zHo18M3MOA1R0Hy sCgXp1dpKMaMVuQh92302KX6Dk6I+UVvhazK68bbQmwtBWxv9I7U3C01PkSlxD0kMgNp H8EVNe0FbYhp3Ho82acR9ye8ZpGbhyirCP/z5MBPZklUADZmTJNHYUcwqVGK/FjK/aoI XD9vRSkH1ra1RbdCvc6jfWQJXxkvBU3usNqh8bsjlZzbyvqxYXEPNl2TxPN530mAho4l 3qEA== MIME-Version: 1.0 Received: by 10.66.84.7 with SMTP id u7mr13127148pay.83.1342981219719; Sun, 22 Jul 2012 11:20:19 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 11:20:19 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 11:20:19 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 18:20:20 -0000 You don't need another 11n capable card to just dump beacons. Just any atheros NIC :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 19:28:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83636106566C for ; Sun, 22 Jul 2012 19:28:14 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 37D218FC17 for ; Sun, 22 Jul 2012 19:28:14 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3520870qcs.13 for ; Sun, 22 Jul 2012 12:28:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8ZaAzHH/KJE+3giQ+5yvcaCth7tnDP7NOenXZVOpvbI=; b=tvDjrFmozjE2Z3rhMqA0N6/6iuX627s4Eu1HMSw36/RNbjrnJHXZCyrkrxcyUFcp6d QZwJDTXjJAlupu5kwDVXJNs02uscebA0jt2SaNKna2bJihuXKFlr8YtbV3HGJiSiPsET iK/vqT3z608lxiEHtiOId0//C0AofjACLlK9Gn+xf+VA+c1EYNoAQj+KG7gufNn3K622 quEaMSyaoyrT1GvoywnZFgfdoXy3ISVCMy+07f4H3pXOKG/ejj9XUzetYtcAMG975JRx Vp5gGdA/SyLRuU0CK7B4gxAz+Y9R2h9vU2sLAK4LuT3LvZjRmXI5wE7yhrzY803hhsPW 4j2w== MIME-Version: 1.0 Received: by 10.224.71.11 with SMTP id f11mr2299952qaj.41.1342985293511; Sun, 22 Jul 2012 12:28:13 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 12:28:13 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 15:28:13 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 LORs X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 19:28:14 -0000 On Sun, Jul 22, 2012 at 11:26 AM, Adrian Chadd wrote: > On 22 July 2012 04:47, Kim Culhan wrote: >> On Sat, Jul 21, 2012 at 9:21 PM, Adrian Chadd wrote: >>> This is one of those known LORs in net80211. I'd love to get someone >>> to help fix. :) >> >> Through the many reboots done working on multi-ssid vap there were several >> hard hangs at reboot, around 1 in 3 reboots would hang this way. >> >> On the console when the system would hang would be the several lines >> associated with the net80211 LOR, followed by a last line referencing >> pflogd and promiscuous mode. > > Hm, are you able to break to the debugger when things have hung? Only tried ctrl-c, are there any key combinations? -kim From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 22 19:32:32 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 420E1106566B for ; Sun, 22 Jul 2012 19:32:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1606F8FC16 for ; Sun, 22 Jul 2012 19:32:32 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so10233532pbb.13 for ; Sun, 22 Jul 2012 12:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y2ifvGWm3993PQFkxMkJAcBk5z2ieDbu6CWM1pVc2W0=; b=UJYO6/neoLMtj87l0jZN93HDOpWbsrtvBAWSuIQ7pJyBrlSRakZy6GkRq3lrqyuMw2 P47ZlTaaRfinq7qhfP9tBahHBEM+nek5cKZ19kDZdXw4i3Q/ZTxoMTVU4HmtEsvUgMAq dA/kVVVVIzPC5tysr8gfto/DqkFkI1O5EvZ0ODIMcqObeb2VFjrd9CUpx48S4vMoWBtg v5tz8uXnpmGL1xgeHjY0fZPp1RRTuYQDHMQDvHrSxTRSoYQXwCsAFzxCvKyqb10a5H4P WHWg8fLB0pwzcdiTA5Ef+CwQtdkIttXV2vhCCrsZ3KigRbdvGq2WcEkZtFx4f/GRItuz TH2Q== MIME-Version: 1.0 Received: by 10.68.201.9 with SMTP id jw9mr29687370pbc.28.1342985551713; Sun, 22 Jul 2012 12:32:31 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 12:32:31 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 12:32:31 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 LORs X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 19:32:32 -0000 Yup, it's an escape sequence. Man ddb for more information. There's a way to view locks - "show alllocks" I believe. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 01:06:09 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07C291065674; Mon, 23 Jul 2012 01:06:09 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CCD468FC1F; Mon, 23 Jul 2012 01:06:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6N168Hj097762; Mon, 23 Jul 2012 01:06:08 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6N168Ir097758; Mon, 23 Jul 2012 01:06:08 GMT (envelope-from linimon) Date: Mon, 23 Jul 2012 01:06:08 GMT Message-Id: <201207230106.q6N168Ir097758@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/170066: [ral] ral(4) rt61pci Linksys freezes the machine as soon as wpa_supplicant is started X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 01:06:09 -0000 Old Synopsis: ral(4) rt61pci Linksys freezes the machine as soon as wpa_supplicant is started New Synopsis: [ral] ral(4) rt61pci Linksys freezes the machine as soon as wpa_supplicant is started Responsible-Changed-From-To: freebsd-i386->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 23 01:05:43 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=170066 From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 01:41:49 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C66A106564A for ; Mon, 23 Jul 2012 01:41:49 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id C85298FC0A for ; Mon, 23 Jul 2012 01:41:48 +0000 (UTC) Received: by qabg1 with SMTP id g1so932259qab.13 for ; Sun, 22 Jul 2012 18:41:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qBo77ARfrO6mkIcjMoxgiEmoOwHeWUbIIqzSXZMFz/4=; b=QtBD7PGwrDLgzHvcOTWgi+BZZTNlm57Q1zagThzFKfOX2nIA92yN4OXSjqmC1+epsB ARYd9oTyk5m9AcFPwvLkEEvRhXeibix2j5aG51P75G0SXnaD5oNE5TlheARKFXgQ99a9 dUSNqqym1cQWziEx7NP8f2/GA0Q+rQtkYtyFN7ujPpOpcr75v/d2xZwq935rZag5MoZv e2cCGwyibPBy7/2Pt1Y62kn8eFduOcpJzGTJAVkUcpoxWsKb9Xyt+ho47Ek0rFoAjta4 qlhXmHXBXuMlAw+j4HrqHj5IWWwqzNxQJhh/lGi06Q3OORqJ6gU6TJAwwYEOP3fvWj+E WCkQ== MIME-Version: 1.0 Received: by 10.224.101.193 with SMTP id d1mr22140568qao.20.1343007708121; Sun, 22 Jul 2012 18:41:48 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 18:41:48 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 21:41:48 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 LORs X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 01:41:49 -0000 On Sun, Jul 22, 2012 at 3:32 PM, Adrian Chadd wrote: > Yup, it's an escape sequence. Man ddb for more information. > > There's a way to view locks - "show alllocks" I believe. Had a chance to try to break to the debugger and it was not possible. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:08:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D7BD106564A for ; Mon, 23 Jul 2012 02:08:09 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id B411A8FC0A for ; Mon, 23 Jul 2012 02:08:08 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3593484qcs.13 for ; Sun, 22 Jul 2012 19:08:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QRB4x5kS53zvO9z6UYJ1ywPjHTPoxbu0iVXrsiAxWQ8=; b=iEfpPyGvRjDZX6upDZlF01WqhSFUPNTvDXOUHYo/7a5iMKDFBoRXsgL0E1MUI10rbG yIGtBeEMJK2NfiYz420bNl4n++Vs1NtMxbyxLaG68yqbvP3CXovZ7Y+F7dVyrqC3IpD0 s5cbCVN1v08KfoAQMpTwMVtOxLzricSraranxxg2G3D0o8gZ8EW6jHrwkg/c6RoZcRbn hyjwhCsn4zXTc8HSTTwQAcDHWxPTjQmhSdI3fbNo7uIyXTFRCmMdfS+fhDyD0WIeF8fw 6SAf95eNwWHGRkB/nEwvx7eDshopamzkbQnd1LixT+0X1UYewnJW3Tv5ivUT6paPQtZu 33PA== MIME-Version: 1.0 Received: by 10.224.59.13 with SMTP id j13mr22117131qah.44.1343009282600; Sun, 22 Jul 2012 19:08:02 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 19:08:02 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 22:08:02 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 02:08:09 -0000 On Sun, Jul 22, 2012 at 11:22 AM, Adrian Chadd wrote: > Hm, ok. > > So I'd start diagnosing this by setting up another FreeBSD device in > monitor mode on that channel and capturing some beacons. > Then take a look in wireshark and make sure you're seeing beacons consistently. > > I bet the beacon timer and beacon slot configuration is all subtly > messed up, leading to this mess. I've setup another machine running -current and have it running in monitor mode. Some output looks like: 21:38:55.159960 709697219us tsft 1.0 Mb/s -21dB signal -96dB noise antenna 1 2437 MHz 11g Beacon (ap1) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] ESS CH: 6 21:38:55.211339 709748597us tsft 1.0 Mb/s -14dB signal -96dB noise antenna 1 2437 MHz 11g Beacon (ap2) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] ESS CH: 6, PRIVACY 21:38:55.236939 709774195us tsft 1.0 Mb/s -13dB signal -96dB noise antenna 1 2437 MHz 11g Beacon (ap3) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] ESS CH: 6, PRIVACY 21:38:55.243399 709780617us tsft MCS 7 -55dB signal -96dB noise antenna 1 2437 MHz 11g ht/40+ CF +QoS Data IV:68e Pad 20 KeyID 0 21:38:55.243403 709780661us tsft short preamble 24.0 Mb/s -18dB signal -96dB noise antenna 1 2437 MHz 11g Acknowledgment RA:90:f6:52:75:eb:99 21:38:55.243859 709780972us tsft short preamble 24.0 Mb/s -17dB signal -96dB noise antenna 1 2437 MHz 11g Request-To-Send TA:fe:d1:11:38:3c:e5 21:38:55.243863 709781016us tsft short preamble 24.0 Mb/s -53dB signal -96dB noise antenna 1 2437 MHz 11g Clear-To-Send RA:fe:d1:11:38:3c:e5 Looks like its good to go in monitor mode. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:09:37 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3D2E106564A for ; Mon, 23 Jul 2012 02:09:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 74D538FC14 for ; Mon, 23 Jul 2012 02:09:37 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so10647340pbb.13 for ; Sun, 22 Jul 2012 19:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q+bg853Ps5mVFsd5fe9Ata2WA5tMH5RrTEyQcNQAtko=; b=0ppOVvKoG82K6vMqjn1CHBEU07j/NJONU/Gj8IYLIQDC6Ba5DHUVcDdRbij+49Ysbx bGhkk3R3tcloiARFCoKyK+Z/evKqq5l5+Gd8urLhsh96ljM/id5YAsv+zEIUB2VAJeFL VDMj/HgEgvJZeqZ1TgY5ep2S4kJZK6NlHkOgf/km9hfJ+QnjL23IGzDXjGSzZvtqiQD3 tfsPdbDmHZeoZJsr6snORna3Fu0T3R/58+ZZx00ggS6Iwz/yws9F1Rx0LGarpiqBPtVt 6P+vXJ1I8ArRDTvmmEITxLWdI1M45WvAnRa8pPOWo5JzRkHZsR6CXergunLMF4ZLoiDK ByUA== MIME-Version: 1.0 Received: by 10.66.73.69 with SMTP id j5mr27342435pav.8.1343009377227; Sun, 22 Jul 2012 19:09:37 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 19:09:37 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 19:09:37 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 02:09:37 -0000 Sweet. Let's see if you can establish whether you're seeing reliable beacons and if not, if there's any pattern to it. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:14:31 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07616106564A for ; Mon, 23 Jul 2012 02:14:31 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id AC7E58FC0C for ; Mon, 23 Jul 2012 02:14:30 +0000 (UTC) Received: by qabg1 with SMTP id g1so938988qab.13 for ; Sun, 22 Jul 2012 19:14:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Bp5h7DC37ut0KT1tM9WN1yYvjma8WG7Rj9W7RIJcT+I=; b=JFYTFbmBQo1gtmoNn04HtgbjgGPaTUuP9rZFqWTGEFoFLvLcwEVferkLtg9NOymxQ5 5/+ioIGQzo3yP6kOdbW84XYdLjrdbX7UfZwjTlX01bOt+kbgSaiwC1beqyZC4cKtcJ6w CGwroBVKOgJlNxt6/32ngRSPDJxqXcVawDxY//i6GPswchDhkvqdVxwz/GIaNL+0woZY jRNjWh5RWb9GvYgBmZysbjkxaUavubE7MfQVn06aif3If9/BWVzEguvqxJG+bLC03YTF aVTipJByT12TJAap5CYwuamREZiDfZYHuQA/FfZiEAzS45xmQnkTbxrz0ZCDCsIDtsJ9 70fA== MIME-Version: 1.0 Received: by 10.224.222.147 with SMTP id ig19mr22237924qab.32.1343009670056; Sun, 22 Jul 2012 19:14:30 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 19:14:29 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 22:14:29 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 02:14:31 -0000 On Sun, Jul 22, 2012 at 10:09 PM, Adrian Chadd wrote: > Sweet. Let's see if you can establish whether you're seeing reliable > beacons and if not, if there's any pattern to it. Great, the setup to this point is: ifconfig wlan0 create wlandev ath0 wlanmode monitor ifconfig wlan0 channel 6 ifconfig wlan0 up tcpdump -ni wlan0 -y IEEE802_11_RADIO How should it be setup to look at the beacons? -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:18:21 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCAED106564A for ; Mon, 23 Jul 2012 02:18:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 921458FC08 for ; Mon, 23 Jul 2012 02:18:21 +0000 (UTC) Received: by ghbz22 with SMTP id z22so5873454ghb.13 for ; Sun, 22 Jul 2012 19:18:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9RR1I8lw1UPRkin6VpscuZYmWCf+jsPQ51zRiJg/N1w=; b=M4au4Qt0H+7RiTTYxCHa60FjPRB/o/jzOaV0JD/0lThqxqzuYlUHwX1zqWLI6pWoS2 GDXVtmUGfhfiaciD2Ms56dXTZ2aGZqdJSoLtt878h0BX4k+C3oFGuDifyLDqZ4EgfTcQ MRk/Bs7HsajSMsMkL9MNb/p7RKoYOjvsjoa6S78wz13qvl7wgx+AMahsJmkAj0dwFonk fDaaUutd+sxUgziMYQa1hoPxqBver/gxtFrH8LVRL9kAdfkDMEE/qoDAZ9Tmx8zx9uGm C4Fjy0BoJux6U6hOMYDTZ1Ice4dhWLmNKOUoDETaihT5WdIszucBDITvf60hcY9HN8Xp USvg== MIME-Version: 1.0 Received: by 10.66.72.163 with SMTP id e3mr27236601pav.42.1343009900561; Sun, 22 Jul 2012 19:18:20 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 19:18:20 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 19:18:20 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 02:18:21 -0000 On 22 July 2012 19:14, Kim Culhan wrote: > Great, the setup to this point is: > > ifconfig wlan0 create wlandev ath0 wlanmode monitor > ifconfig wlan0 channel 6 > ifconfig wlan0 up > tcpdump -ni wlan0 -y IEEE802_11_RADIO > > How should it be setup to look at the beacons? Grab a dump and look at it in wireshark. tcpdump -ni wlan0 -y IEEE802_11_RADIO -s0 -l -v -w output.pcap Then open that pcap in wireshark and look at just the beacons.:) From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:55:06 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA595106566C for ; Mon, 23 Jul 2012 02:55:06 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8388B8FC0C for ; Mon, 23 Jul 2012 02:55:06 +0000 (UTC) Received: by qaat11 with SMTP id t11so951111qaa.13 for ; Sun, 22 Jul 2012 19:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Vu4dSGmGCSWMRR9hpXmjuPpeplQvlaQe5Qv8dXpzijk=; b=ljMJbU8o4EPBPmgaYWrrQNHj6QgC6sJVN2+bAe+OqHz0KeLwwwFogim1scv3gdc2ce sMN//eF8/wwsQI3tJ2qJqoFfTggt1tcosggpaO9dK4WfkLYW7dQyNoIP0umzaqlt0ehd p4LtMt/KA5o3n8wr0jjTZSm0CYpQZdzvn/Wgen9oBBd4BkGQRM/2zH8Pov7Dx2SUZQ6W 5rKK/BgVo3fVZMLb5W3dtaItPG0dCQCUqKDpsF3RYrI4W1Zq28JbuGzxamWgZTcDNwRI yqkwzSIad36uU5wULei3gFHMquBmVrcvS3xu5YDp2QxfYYOy6j6ZUP4CyOqa3/fXa512 CkQg== MIME-Version: 1.0 Received: by 10.224.101.193 with SMTP id d1mr22342636qao.20.1343012100566; Sun, 22 Jul 2012 19:55:00 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 19:55:00 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 22:55:00 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 02:55:06 -0000 On Sun, Jul 22, 2012 at 10:18 PM, Adrian Chadd wrote: > On 22 July 2012 19:14, Kim Culhan wrote: > >> Great, the setup to this point is: >> >> ifconfig wlan0 create wlandev ath0 wlanmode monitor >> ifconfig wlan0 channel 6 >> ifconfig wlan0 up >> tcpdump -ni wlan0 -y IEEE802_11_RADIO >> >> How should it be setup to look at the beacons? > > Grab a dump and look at it in wireshark. > > tcpdump -ni wlan0 -y IEEE802_11_RADIO -s0 -l -v -w output.pcap > > Then open that pcap in wireshark and look at just the beacons.:) Looking at a pcap when running the ap with 4 vaps, behaving in the usual way looking at it from a client., cant connect to most of the ssid's. Not finding anything remarkable looking at it with wireshark, would you want to give a look and see what you think? -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 02:58:32 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16A75106566C for ; Mon, 23 Jul 2012 02:58:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id D7A828FC0C for ; Mon, 23 Jul 2012 02:58:31 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so10709210pbb.13 for ; Sun, 22 Jul 2012 19:58:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GmIGo1/Stj9SNZDeiMYlt/DK86crOOg3ofhWFryU7+U=; b=NbMBIOZxH1AYZkegKUrOJRU0uaqhiLxbmHmMgCMbGXFd+QSgJNngVqNd5SDBSLlNQn LW8XHpK4jnRAiWps+lSBjRAEmFeU2KmAriADopXRYxqbupvwl58wo5XI2nq3Q7FHGBc4 aY/Gb4fK6yVYNJvRlhvBfhswSO0T265LkdFvw0efgmEztC1CI4UgjVM2C8Uirp49cSly WXuNT/6Uls5LFewG1yAf1tKe1L5upjXsfYXS8mzesp7peCdFoDR1NqWbaSKh9lwrwKe+ 6xX3uM07wwCfwbtHLVkE8xLUrn8xaVbJA/lhVYyg/Zc151KHXHeQnlWd0ToViWw0k1TG uZTA== MIME-Version: 1.0 Received: by 10.66.83.65 with SMTP id o1mr27506265pay.17.1343012311581; Sun, 22 Jul 2012 19:58:31 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sun, 22 Jul 2012 19:58:31 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 19:58:31 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 02:58:32 -0000 On 22 July 2012 19:55, Kim Culhan wrote: > Looking at a pcap when running the ap with 4 vaps, behaving in the > usual way looking at it from > a client., cant connect to most of the ssid's. Hm, right. > Not finding anything remarkable looking at it with wireshark, would > you want to give a look > and see what you think? I'm knee deep in massaging the driver to be ready for the AR93xx and later series chips. I can give you some pointers, but I don't want to get too distracted by other things. :) What I'd do: * I'd look at the beacon interval (in TU - which is 1024 microseconds) in the beacon frames, for each VAP; * Then I'd look at whether the beacons you're seeing are occuring at regular intervals, at the above beacon intervals. Let's first establish that you're reliably transmitting each beacon correctly with the right interval, then we'll go from there. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 03:03:02 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 55685106564A for ; Mon, 23 Jul 2012 03:03:02 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 01AB98FC14 for ; Mon, 23 Jul 2012 03:03:01 +0000 (UTC) Received: by qaat11 with SMTP id t11so952860qaa.13 for ; Sun, 22 Jul 2012 20:03:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DWjX73TdAgxQ7cSYMPPfmJIxJUZ5BZ0sASs2a7LSfAw=; b=obkSTHNXPstzup4uLcuyoGtGHnHBaYNFzkwOX9Zpcb9PggM/hMit5yNX8M4XxgI86j rBi7BY+FhowaQHafEUxHUbLX6CmqajLD343eg9s9dcDCwuwCu/MQ774/UBWRPDD7dRYX oTD1MTRTiyPMFtJQkI4PiIf7J+hdKVrL+O4kMORoh43xteEGd5CnRhzrwVsqIMt3zD3U l3OjuOaBopufRaOkGeV7/v/4lYjmq/XDx9ezMJfBF9D3WTOdWph/NRaZ7V8badsymrED kv4mnBhLW90Ww5ecYzzeyfIjtauBYX4xFf0ChvrwoQQo6AV+QDD86+51jMi3zwjqmMw/ 0qxQ== MIME-Version: 1.0 Received: by 10.224.71.11 with SMTP id f11mr3657193qaj.41.1343012581494; Sun, 22 Jul 2012 20:03:01 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Sun, 22 Jul 2012 20:03:01 -0700 (PDT) In-Reply-To: References: Date: Sun, 22 Jul 2012 23:03:01 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 03:03:02 -0000 On Sun, Jul 22, 2012 at 10:58 PM, Adrian Chadd wrote: > On 22 July 2012 19:55, Kim Culhan wrote: > >> Looking at a pcap when running the ap with 4 vaps, behaving in the >> usual way looking at it from >> a client., cant connect to most of the ssid's. > > Hm, right. > >> Not finding anything remarkable looking at it with wireshark, would >> you want to give a look >> and see what you think? > > I'm knee deep in massaging the driver to be ready for the AR93xx and > later series chips. I can give you some pointers, but I don't want to > get too distracted by other things. :) > > What I'd do: > > * I'd look at the beacon interval (in TU - which is 1024 microseconds) > in the beacon frames, for each VAP; > * Then I'd look at whether the beacons you're seeing are occuring at > regular intervals, at the above beacon intervals. > > Let's first establish that you're reliably transmitting each beacon > correctly with the right interval, then we'll go from there. Very good, that direction is greatly appreciated and I'll follow up with it. thanks -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 11:07:29 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84CCB1065670 for ; Mon, 23 Jul 2012 11:07:29 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8BF8FC23 for ; Mon, 23 Jul 2012 11:07:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6NB7TQS090206 for ; Mon, 23 Jul 2012 11:07:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6NB7Sqo090204 for freebsd-wireless@FreeBSD.org; Mon, 23 Jul 2012 11:07:28 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Jul 2012 11:07:28 GMT Message-Id: <201207231107.q6NB7Sqo090204@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 11:07:29 -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/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169433 wireless [iwn] iwn(4) doesn't support 6235 chip. o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o 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 116 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 12:06:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 448771065670 for ; Mon, 23 Jul 2012 12:06:14 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id E62B08FC1D for ; Mon, 23 Jul 2012 12:06:13 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3776226qcs.13 for ; Mon, 23 Jul 2012 05:06:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D8amFB7B/QDGiy8C08o0rSRjyXbsRpb2HTY5N7sJ8JY=; b=ZDcY3UVOWsKmbWlWK/XONpSIRfUJSAj6J+Nw/MvSuqRzsMuf8UXGJba7GmyXQWRcfY ItSmlkmLfKEQLUPYsxgsU/jCnzi6Ek8GVE2LHfOc/6MLZquVu+hr9oNP5Y8ehpwir3OA cVgPf4O5ewYVvggiOQ2kpaC6FQ9MLo6xcQMfejAC/4/G/n4PMRlMGnRG3XpaVQhYnUNY LPvn/vrksKN+JjZ0vcQcjQvy7oKo9nReoQX+5im68eCZvyc55Je6j251hOIV7KR5vQVh epUa5SnowH1TXoOnxAqdSPxCuoW+BNx3BqUANY09NXDkg4dKuujxgBDhA5nBiG2IgWCh jOig== MIME-Version: 1.0 Received: by 10.229.137.12 with SMTP id u12mr6999788qct.28.1343045172514; Mon, 23 Jul 2012 05:06:12 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 05:06:12 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 08:06:12 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 12:06:14 -0000 On Sun, Jul 22, 2012 at 10:58 PM, Adrian Chadd wrote: > I'm knee deep in massaging the driver to be ready for the AR93xx and > later series chips. Would an ar9380 be good for testing when you get the driver to that point? -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 12:07:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7DB36106566B for ; Mon, 23 Jul 2012 12:07:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4781D8FC0C for ; Mon, 23 Jul 2012 12:07:14 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so11452322pbb.13 for ; Mon, 23 Jul 2012 05:07:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mE1psBUzotlvLXmgBErFkufQYKx211wvXR3b8EMeDoI=; b=gT1HucwWe7gMvIQ5VEwkRF3YTZBSjQfZWaAzB0+r9tkVuydO7xxVrqJA65CEeVdzPq bPZEJftjLwCxtdQM0T9zzAU3orjqfIM3MwTZCbFWx5tXvQ0ztBelscQVuG1E5Io+ZdWv hnI2idXzCVKfkgFLuluxjHGcONVzuYEaZbPyCvhm7Q2gMLO56D2avlGnHnjI8zmc4TcW 49kjwbEixs0XN+zapoGPBRO7nbTcpytCgEd91WdCkSf1xVFOBNtIPnT3IMk4LFeJaL/B fII4f8otc1Z75p3ETcx6fPeEsVAE7bCBrmuY9KGTunTD4TU2hWrZkh5OeN1swFEkyne1 rz0w== MIME-Version: 1.0 Received: by 10.68.238.166 with SMTP id vl6mr11819998pbc.96.1343045233674; Mon, 23 Jul 2012 05:07:13 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Mon, 23 Jul 2012 05:07:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 05:07:13 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 12:07:14 -0000 On 23 July 2012 05:06, Kim Culhan wrote: > On Sun, Jul 22, 2012 at 10:58 PM, Adrian Chadd wrote: > >> I'm knee deep in massaging the driver to be ready for the AR93xx and >> later series chips. > > Would an ar9380 be good for testing when you get the driver to that point? yup. adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 13:28:15 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 679B21065677 for ; Mon, 23 Jul 2012 13:28:15 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 170B98FC15 for ; Mon, 23 Jul 2012 13:28:15 +0000 (UTC) Received: by qaat11 with SMTP id t11so1145596qaa.13 for ; Mon, 23 Jul 2012 06:28:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QJhXCPFPWEUX5ShhuvRein2y7LwhFCcCqnkf/pQwB5A=; b=d7DTtd7W5rQu03jaBqXMfTc3bt9dV2UhNIgvkh2KcRex2MVhhISfll/ajAUrDOPblI MBxk7n+CHnAi+ommnXyiQoJagh6WzOvMMdhX7pQa+NnrPmJ0aS0obyWjDMby+wRvrOV7 D5h5vL3bx2xfuwuwA90kmdBbtGNSWEJnEeN5TxcXVl45xMQriJV5ga0AImg+xoiksPaI h+0OSKuuh5WSyRiI2vg3ClI5tAhS3mIG2L+zHcwz7GYJi0jRPCv2PWxOZU0cuOq7yVHt JSn9psL5hGdnL2Dk34wdFFtWp8dhvHukfmJzplU3daWMvJbtolqjb7z51kfhAqwDRyO0 bguw== MIME-Version: 1.0 Received: by 10.229.137.12 with SMTP id u12mr7110155qct.28.1343050093399; Mon, 23 Jul 2012 06:28:13 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 06:28:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 09:28:13 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID with ath on FreeBSD 10-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 13:28:15 -0000 Would you rather test with -current built with gcc or clang? -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 13:57:56 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57D02106564A for ; Mon, 23 Jul 2012 13:57:56 +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 C7D548FC0A for ; Mon, 23 Jul 2012 13:57:55 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:a84b:9962:ac85:792c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3B6E84AC2D; Mon, 23 Jul 2012 17:57:47 +0400 (MSK) Date: Mon, 23 Jul 2012 17:57:44 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1468023399.20120723175744@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> <802688919.20120709140808@serebryakov.spb.ru> <1966637204.20120713194935@serebryakov.spb.ru> <5862675.20120713203432@serebryakov.spb.ru> <7750188.20120716011053@serebryakov.spb.ru> <1214412854.20120722020752@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Jul 2012 13:57:56 -0000 Hello, Adrian. You wrote 22 =D0=B8=D1=8E=D0=BB=D1=8F 2012 =D0=B3., 2:10:42: >> AC> Hm. With debuggimg it works, but turning it off causes timeouts? >> I'll turn it off tomorrow and will see AC> Thanks. If that's the case, it's quite likely a timing / race AC> condition bug and even your debugging logs as they are will be very AC> helpful. Again (without debug): ath0: ath_tx_tid_bar_unsuspend: bar_tx=3D0, bar_wait=3D0: ? ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: ath_tx_tid_drain: node 0xc404b000: bf=3D0xc34fda60: addbaw=3D0, dobaw= =3D0, seqno=3D3113, retry=3D0 ath0: ath_tx_tid_drain: node 0xc404b000: bf=3D0xc34fda60: tid txq_depth=3D5= 03 hwq_depth=3D0, bar_wait=3D0 ath0: ath_tx_tid_drain: node 0xc404b000: tid 0: txq_depth=3D1, txq_aggr_dep= th=3D0, sched=3D0, paused=3D-1, hwq_depth=3D0, incomp=3D0, baw_head=3D111, = baw_tail=3D111 txa_start=3D3113, ni_txseqs=3D5107 FRDS 00:0c:42:64:69:92->70:d4:f2:ad:6a:26(00:0c:42:64:69:92) data QoS [TID = 0] WEP [IV 29 0c 00 00 00 00 KID 0] 0M 8862 0000 70d4 f2ad 6a26 000c 4264 6992 000c 4264 6992 90c2 0000 0101 290c= 0020 0000 0000 aaaa 0300 0000 0800 ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 15:11:22 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EAA81065670 for ; Mon, 23 Jul 2012 15:11:22 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 576FF8FC0A for ; Mon, 23 Jul 2012 15:11:22 +0000 (UTC) Received: by qabg1 with SMTP id g1so1267030qab.13 for ; Mon, 23 Jul 2012 08:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=hbOzu0e1fjop0ygvuF7CtdLYrqFo0ZmWUqvV/FW963M=; b=kVsQ4queM4LgVKYRT+2aP45kk7vZhBUHNZJJeCQ6KvIb67zYlBkpeafHnXiNbSBesI Ta72m+t1fvn5ljT9wW6ow8XbcZ+d4HgPNoPm1u28XDvpu6EgKt89KHTac9s+lvYO8xSS UxHd1GwrrE+8Yhxz/5GObj0fSZyeFGWNTetqYhZlnQj6Lq7qYtjLk15BMMDNlWFT+AEu qAuHzEW/RTnJy9jVsDKlY/V69wK53J+dLDpSCCyCsdxg+V/SpPPqU7Nmn6KKLEcM5Tor qwhQ9kKf1vw3RfXXSRFnGw0scJ9rWsbkO8q3QN39+49J+AgqAU/bBiiAFkO2+p/pGu2c EfVw== MIME-Version: 1.0 Received: by 10.224.178.73 with SMTP id bl9mr21387681qab.89.1343056276425; Mon, 23 Jul 2012 08:11:16 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 08:11:16 -0700 (PDT) Date: Mon, 23 Jul 2012 11:11:16 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 15:11:22 -0000 Having each vap with a unique bssid appears to have eliminated a problem with a client not being able to connect to all vap in a 4-vap test setup. The configuration which achieves unique bssid : create_args_wlan0="wlanmode hostap wlanaddr f8:d1:11:38:3c:e5" create_args_wlan1="wlanmode hostap wlanaddr fa:d1:11:38:3c:e5" create_args_wlan2="wlanmode hostap wlanaddr fc:d1:11:38:3c:e5" create_args_wlan3="wlanmode hostap wlanaddr fe:d1:11:38:3c:e5" This has been 'tested' so far in the case of all vap running in OPEN mode and for a config with 1 OPEN mode and 3 WPA2. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 18:53:45 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C7EE106564A for ; Mon, 23 Jul 2012 18:53:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id EDA548FC08 for ; Mon, 23 Jul 2012 18:53:44 +0000 (UTC) Received: by lbon10 with SMTP id n10so10422579lbo.13 for ; Mon, 23 Jul 2012 11:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wYL/TQs25V+F7AOtAttfKKtevyDa5Xx7sgguMfmTPc4=; b=NO6zNnE9WmMdh9TZU8xD2r+W7h3OobJcc0hyxF06vwcWIrhRGRMIfYSuYgqEMfYpkf /Olk7PYa6Nx7osFw602x1u0zZo0vYVR5yq2SKxldcIqP6TBezFwdShUfauLxbVcebTzk vlEMsUTwaiyAvpgfDpVqL6U7YRo3V/i9W3St7bw52Ca+w0hdUwHGPQdMA0Kz/8+b6tOr sbYgJ79BpXdZr3YP+kuXccgwi3k5/lfplnHqA+QTlFWuxeG+QzjbnWQOcWtA6pc2e5nP fzF0CkWtnCfQSeRWNjVs4NBZFIT1l3VqjkTunRWU3b/wSuXlClph9QEBzBFVfSHsdbv5 eT3g== MIME-Version: 1.0 Received: by 10.112.44.163 with SMTP id f3mr8219744lbm.59.1343069623685; Mon, 23 Jul 2012 11:53:43 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 11:53:43 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 11:53:43 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 18:53:45 -0000 .. what changed? Adrian On 23 July 2012 08:11, Kim Culhan wrote: > Having each vap with a unique bssid appears to have eliminated a > problem with a client > not being able to connect to all vap in a 4-vap test setup. > > The configuration which achieves unique bssid : > > create_args_wlan0="wlanmode hostap wlanaddr f8:d1:11:38:3c:e5" > create_args_wlan1="wlanmode hostap wlanaddr fa:d1:11:38:3c:e5" > create_args_wlan2="wlanmode hostap wlanaddr fc:d1:11:38:3c:e5" > create_args_wlan3="wlanmode hostap wlanaddr fe:d1:11:38:3c:e5" > > This has been 'tested' so far in the case of all vap running in OPEN > mode and for > a config with 1 OPEN mode and 3 WPA2. > > -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 19:01:01 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5AFE10656B3; Mon, 23 Jul 2012 19:01:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id DDE4D8FC08; Mon, 23 Jul 2012 19:01:00 +0000 (UTC) Received: by lbon10 with SMTP id n10so10429622lbo.13 for ; Mon, 23 Jul 2012 12:00:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=amJ8ZuuucUjt7c4TqmVroYV2YRQQU6Xvcso/LxWWDB0=; b=BBPD0TCT98guCnekCcTDFV0PFY4Lrx4M2M9VKmaIEIOPbSY/2gOaW/jr+I6I61RHUN AY1se2zCfLAzR8CtMq6RVcLjLXsPi79z7jnSWQ/i/22qWO5P7ih0R863aNR9xv6ynEFb 9/SFNut14fubt09c8+v2cqNOAP3m8JQQ7OBJC4jkVzB1UKAYxh5J1f3ZWB3XjKCRRmrL NXeLN0tbEV9IQG4IERXxypi7T3/CFN0vxJ5fiSzWZljGmfh2jZvbKZjVYS//oEpaxROw /4mU/ILTfeu66jGz2GrTrfgOPtc821MRsdTlRbgeFt2CUWilm0DrErpqXQBULiYq279L BSGQ== MIME-Version: 1.0 Received: by 10.152.148.1 with SMTP id to1mr18056558lab.34.1343070059743; Mon, 23 Jul 2012 12:00:59 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 12:00:59 -0700 (PDT) In-Reply-To: <1468023399.20120723175744@serebryakov.spb.ru> References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> <802688919.20120709140808@serebryakov.spb.ru> <1966637204.20120713194935@serebryakov.spb.ru> <5862675.20120713203432@serebryakov.spb.ru> <7750188.20120716011053@serebryakov.spb.ru> <1214412854.20120722020752@serebryakov.spb.ru> <1468023399.20120723175744@serebryakov.spb.ru> Date: Mon, 23 Jul 2012 12:00:59 -0700 Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 19:01:01 -0000 Ok, it may be timing related and / or a race condition. Turn on debugging and email me a log for a days worth of normal use, the same use that'd cause the session to hang. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 19:04:26 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA65B106564A; Mon, 23 Jul 2012 19:04:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2EF698FC0C; Mon, 23 Jul 2012 19:04:26 +0000 (UTC) Received: by laai10 with SMTP id i10so263278laa.13 for ; Mon, 23 Jul 2012 12:04:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yCmj0EckAWP7ON5EQHSTAWNVKk6oqImoYiWgxm9VBE8=; b=j7UNOEFe6osOSKw+SrazBZPZO058uiU64dAtKmbow0nx6Qoa8hpIS6qZb7Zgf4xWuJ pMsxidJc8/TnlPkJZG3BlFscoTRTkoGlThXF+SRym/iiZteCaufvbFaBmrPbQsmrSG6O DOl8Oeon/HnYZ/AQOI8x6Bj02yuNV4o1oEjAJALvk9u7YQt0v/RcKrp691bkSTJxI+vc lV1/DALzI0AUf2yfp8TAK4f7oRiQygXKIj5CF9WIJWQaro2cNtbdH5C9Hnlsank+Fg23 JgRIsy/y/bS7hiyeOYQwryuh9UV8RgjWeoe+eFi0DKsOpnhizuzdxTAkexeqQO4woOoG +Ekg== MIME-Version: 1.0 Received: by 10.152.105.51 with SMTP id gj19mr18091639lab.38.1343070264728; Mon, 23 Jul 2012 12:04:24 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 12:04:24 -0700 (PDT) In-Reply-To: References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> <802688919.20120709140808@serebryakov.spb.ru> <1966637204.20120713194935@serebryakov.spb.ru> <5862675.20120713203432@serebryakov.spb.ru> <7750188.20120716011053@serebryakov.spb.ru> <1214412854.20120722020752@serebryakov.spb.ru> <1468023399.20120723175744@serebryakov.spb.ru> Date: Mon, 23 Jul 2012 12:04:24 -0700 Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 19:04:27 -0000 .. and please file a PR with all the details to date and let me know the PR number. I'll assign it to freebsd-wireless@ and we'll then just keep tacking debugging information onto that PR. Thanks! Adrian On 23 July 2012 12:00, Adrian Chadd wrote: > Ok, it may be timing related and / or a race condition. > > Turn on debugging and email me a log for a days worth of normal use, > the same use that'd cause the session to hang. > > > > Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 19:24:36 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83898106566C; Mon, 23 Jul 2012 19:24:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id BAA288FC0A; Mon, 23 Jul 2012 19:24:35 +0000 (UTC) Received: by laai10 with SMTP id i10so283274laa.13 for ; Mon, 23 Jul 2012 12:24:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tFnALR2Fpr290zumRhHtJNbaQ3PSeHfHc7m3oIVrfn8=; b=LEZviwr6ucRX3Gvp0JadZXxbHMJqdm2W319o/ypIZAnyoMknez1JrFE7dBAGH4Sp7X Uf0JFChwKk/NkzuNwVi6xm/bjktGvflX+qgSDDi60olndg+0kJxQ0rCEJu8MWyCaU+5S vC1FIxwhfBLxNksNS/JqHbBINtzVffMRRY8Fkvb7Vv3p9Hr3kfn0/Xua2d0xOPu7YAqb 4chVxTcyTVOif8PMnDVTCCcRBJOAC/kbhH7IngsH3L/T5wgX5bjkgMdLgXH3+fTvxHQc iA/EObjO8OQxa1Tx+EDgPhRLwDhumTwYIbkMoNxtDhDTY5Y3plJS8w8tFiNFhTr8GoCK 914w== MIME-Version: 1.0 Received: by 10.152.105.51 with SMTP id gj19mr18167722lab.38.1343071474730; Mon, 23 Jul 2012 12:24:34 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 12:24:34 -0700 (PDT) In-Reply-To: <1468023399.20120723175744@serebryakov.spb.ru> References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> <802688919.20120709140808@serebryakov.spb.ru> <1966637204.20120713194935@serebryakov.spb.ru> <5862675.20120713203432@serebryakov.spb.ru> <7750188.20120716011053@serebryakov.spb.ru> <1214412854.20120722020752@serebryakov.spb.ru> <1468023399.20120723175744@serebryakov.spb.ru> Date: Mon, 23 Jul 2012 12:24:34 -0700 Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 19:24:36 -0000 .. and is that "bar_unsuspend" the first line to appear in your debugging output? Time to braindump what's going on in this aggregation/BAR path: * the TID pause/unpause only occurs for a few things - negotiating aggregation, tearing down aggregation, sending BAR; * and it's refcounted, because it's entirely possible multiple things will occur (eg sending BAR overlapping with tearing down aggregation); * So I need to try and establish whether this is something specific to say, just BAR handling, or whether it's overlapping with a call to ath_addba_stop() which will call ath_tx_tid_cleanup() to "clean" up the aggregation frames in preparation for dropping back to non-aggregation. Now - ath_addba_stop() is called when: * the station re-associates for whatever reason, as the state needs to be torn down and re-established; * the station times out and the state is being freed. So maybe some overlapping traffic and BAR TX is occuring, whilst the station re-associates. Finally, the way the cleanup path works is a bit hokey: * the caller pauses the TID; * it then calls ath_tx_tid_cleanup(); * ath_tx_tid_cleanup() then walks the list of frames that it thinks are in the hardware queue (don't ask why it does this - I stole it from Linux/Atheros code, before I just added a per-TID hardware queue counter) and it marks the TID as "cleanup in progress". * The TID is then only unpaused once all the hardware-queued frames have completed (ie, when incomp is decremented and equal to 0.) * .. that occurs in either ath_tx_comp_cleanup_aggr() and ath_tx_comp_cleanup_unaggr(). Now, incomp is 0, so it's unlikely due to something being stuck in the TX queue or the math calculating the queue depth being wrong. The interesting warning there is the debugging from ath_tx_tid_bar_unsuspend() - that shouldn't be called with both of those flags equal to 0. There's only a few places it's called from. There aren't many places where it could even _be_ set to 0. However, there's no locking in the net80211 stack for handling BAR, so I have to compensate by doing locking and workarounds in the TX / BAR path in the driver. So it's entirely possible I've missed something there. I think I recall one instance where aggregation was being attempted concurrently, multiple times, but only calling the completion routine once. Eek. Anyway, I hope that braindump helps you or someone else in potentially going for a dive through the code. Oh, one last thing - I actually have a local kernel modification to device_printf() in sys/kern/subr_bus.c (I think, just grep for it) which prints out the current thread ID before any device output. It makes concurrent/overlapping/racy behaviour _really_ obvious, as they come from separate thread IDs. You may wish to hack that in to your kernel and see if any of the debug statements are coming from different threads. Oh, and another last thing - you could also turn on association debugging (wlandebug -i wlanX +assoc) to capture whether the station is reassociating constantly. That'll help me out too. Thanks! Adrian On 23 July 2012 06:57, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 22 =D0=B8=D1=8E=D0=BB=D1=8F 2012 =D0=B3., 2:10:42: > >>> AC> Hm. With debuggimg it works, but turning it off causes timeouts? >>> I'll turn it off tomorrow and will see > AC> Thanks. If that's the case, it's quite likely a timing / race > AC> condition bug and even your debugging logs as they are will be very > AC> helpful. > Again (without debug): > > ath0: ath_tx_tid_bar_unsuspend: bar_tx=3D0, bar_wait=3D0: ? > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: ath_tx_tid_drain: node 0xc404b000: bf=3D0xc34fda60: addbaw=3D0, dob= aw=3D0, seqno=3D3113, retry=3D0 > ath0: ath_tx_tid_drain: node 0xc404b000: bf=3D0xc34fda60: tid txq_depth= =3D503 hwq_depth=3D0, bar_wait=3D0 > ath0: ath_tx_tid_drain: node 0xc404b000: tid 0: txq_depth=3D1, txq_aggr_d= epth=3D0, sched=3D0, paused=3D-1, hwq_depth=3D0, incomp=3D0, baw_head=3D111= , baw_tail=3D111 txa_start=3D3113, ni_txseqs=3D5107 > FRDS 00:0c:42:64:69:92->70:d4:f2:ad:6a:26(00:0c:42:64:69:92) data QoS [TI= D 0] WEP [IV 29 0c 00 00 00 00 KID 0] 0M > 8862 0000 70d4 f2ad 6a26 000c 4264 6992 000c 4264 6992 90c2 0000 0101 29= 0c 0020 0000 0000 aaaa 0300 0000 0800 > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 4) > > > -- > // Black Lion AKA Lev Serebryakov > From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 20:03:43 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C849110656D3 for ; Mon, 23 Jul 2012 20:03:43 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 808B88FC15 for ; Mon, 23 Jul 2012 20:03:43 +0000 (UTC) Received: by qcsg15 with SMTP id g15so4199737qcs.13 for ; Mon, 23 Jul 2012 13:03:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AkYPRWUBZvJCcLLPTQ5wlc3oLlc5qtYPAsQ3Eg0dyx4=; b=w5Xn/G9QTe1QoWk1svSNOte1S1PgHY5zK/6H7azbt38dPoc6Pp/MDqmf9afhcqon0a U0/u4zbP7MIboejMsy3pWHJL5MGizqEvqmF4ZctkCyqmIo8so9idZDjU2Pyu8JLFKAKW lmh6TUwMt0dpSGeeThuoFed5mXx00KBWaR5rZCUN56C71TNFvi4atjt5F8uIWjG0XaFO Yd/XflSu+JVLiHb316G//5XgVVHVMhAlmk6ijDJC+2gpR3nSKYa5qWqDzJIygx8KwcN8 EZP+X0umhYwOQKfKL1YPRK32kZKRWPFu1tOxw2Oxy8Z9h6H3Nv5T1sZgA5Fvi2oPHR3K O6Lw== MIME-Version: 1.0 Received: by 10.224.101.193 with SMTP id d1mr26347675qao.20.1343073822789; Mon, 23 Jul 2012 13:03:42 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 13:03:42 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 16:03:42 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 20:03:43 -0000 On Mon, Jul 23, 2012 at 2:53 PM, Adrian Chadd wrote: > .. what changed? Until now I was unable to cause the bssid's to all be unique. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 20:20:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4EE5410657EF for ; Mon, 23 Jul 2012 20:20:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id BAF148FC08 for ; Mon, 23 Jul 2012 20:20:19 +0000 (UTC) Received: by lbon10 with SMTP id n10so10509856lbo.13 for ; Mon, 23 Jul 2012 13:20:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e1KVPy0q/Q8oDEIMNx0JAP7kyJ+VdpcDAY7bb2Bg5vg=; b=FLfO1HBY+Mu4ICu0X58CgKlvsla0HaCClAll0yGCOUibWm9WsFXafBAE194lckNgLK ueLu8Fkn3at4hXR5x0ZnQQyOSZp754hYKinAtUrUCoJGnF8xGo+xfA584gZdVtj40hHR MmpEVMfoUARGkuafN1utAoiLFAUjWEG1+nNFEkY4LfQf5AtCTcy2oz7iN5GOMEPovhFy Qj5BH2xQn2I4vFiBGSDf+Qadf1u8OHtrEYPMGNmM/N12xTViPW199X7161TkVWwCrDOi hdrP42Jg/0VKeRBajVYKvxzrKvZ6hEqH9mKEf6gI3Tu9feAXcFniXB5FKP8OVxMmXHOM XRQg== MIME-Version: 1.0 Received: by 10.112.27.226 with SMTP id w2mr8502865lbg.57.1343074818546; Mon, 23 Jul 2012 13:20:18 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 13:20:18 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 13:20:18 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 20:20:20 -0000 On 23 July 2012 13:03, Kim Culhan wrote: > On Mon, Jul 23, 2012 at 2:53 PM, Adrian Chadd wrote: >> .. what changed? > > Until now I was unable to cause the bssid's to all be unique. Right, but specifically: When you do a tcpdump of the beacons before and after this change, what do they look like? Were the beacons going out correctly in both cases? And all that changed is the MAC address? Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 20:26:15 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DBA1A106566B for ; Mon, 23 Jul 2012 20:26:15 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 8FC7F8FC0A for ; Mon, 23 Jul 2012 20:26:15 +0000 (UTC) Received: by qabg1 with SMTP id g1so1509030qab.13 for ; Mon, 23 Jul 2012 13:26:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1x0sA5CDQfs+wP++y5VDwH2Tj/UaCXzPsXHCVfMzir0=; b=B1M+qJUG1aXVK7A9gt1V7zYRCvt3m2rZgXuhte/pvw1HgquwPOKySVfYcNSZRdrsYx pCLEHdSKx3LRHLi9AzKLp0eRPvrzMj1EOpCi94gyuvxBjCSuv6TteAOULBr1JfCCFKwE dQuWdzgwQT4TjJRhCeNkMiDcCczncmks0zA8JRoXnFdslqDZ0ALSYkbtz9Jp2e1KuWRE Kl6e3GmsOfSbF1YzYhuMBS46r3LM+w39wX8PyO7Z1JrGYnPar5mKhWTlu78Yx0FncX79 Vb37eUSHw8hX4M6JjDiBP1VgUI20DESy0B9ZrLT1/Re/Ys3n1n63Is9JDEi5Kc0iKNem sNaw== MIME-Version: 1.0 Received: by 10.224.71.11 with SMTP id f11mr7759198qaj.41.1343075174731; Mon, 23 Jul 2012 13:26:14 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 13:26:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 16:26:14 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 20:26:16 -0000 On Mon, Jul 23, 2012 at 4:20 PM, Adrian Chadd wrote: > On 23 July 2012 13:03, Kim Culhan wrote: >> On Mon, Jul 23, 2012 at 2:53 PM, Adrian Chadd wrote: >>> .. what changed? >> >> Until now I was unable to cause the bssid's to all be unique. > > Right, but specifically: > > When you do a tcpdump of the beacons before and after this change, > what do they look like? > > Were the beacons going out correctly in both cases? And all that > changed is the MAC address? The beacons appear to be going out correctly in either case and the MAC addresses are the only difference. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 20:31:19 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 418D0106564A for ; Mon, 23 Jul 2012 20:31:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id B41058FC0A for ; Mon, 23 Jul 2012 20:31:18 +0000 (UTC) Received: by lbon10 with SMTP id n10so10520645lbo.13 for ; Mon, 23 Jul 2012 13:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/YRKt81DSUDz1C2PXsbZC90E31JIkOzulyNVarEQiDo=; b=qIuObfwdQ+AfIIprfhmWTFl12pRb3qDEBxXO8mLLkuxgV3B4cRKYy4FLAly8vJzeBT MLVBlI3PDgmQb1xM+0Wke2Pa+uA2iCY0Qle2uFVw5dkqkFu2bvwvmEr2/zOXo0csk7UX RintTKuLFyKl4/+VtYNISjZvbRorYpwNzZapB2DkyPLcTh4L7RrCMUtoQIHP4ChFrOhb PuZk6Xc9tp7Y3Wko8CEGzozCgNWPeqA0662h3SXd9Tg93bvlSoAX36gSKedypJ7dqY4b 7mTM9pXua+/TqcxDNhR/TpZyMaiWGeaAbwiywsmNLCRLycVQ+k4PTbi1p7cXYzPfizPA Cdrg== MIME-Version: 1.0 Received: by 10.152.104.44 with SMTP id gb12mr18531086lab.29.1343075477689; Mon, 23 Jul 2012 13:31:17 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 13:31:17 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 13:31:17 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 20:31:19 -0000 On 23 July 2012 13:26, Kim Culhan wrote: >> Were the beacons going out correctly in both cases? And all that >> changed is the MAC address? > > The beacons appear to be going out correctly in either case and the > MAC addresses > are the only difference. Very cool. Ok, so the default behaviour isn't correctly allocating the different BSSIDs when creating VAPs. Would you please file a PR with all of the debugging/information you've gathered so far? I'd like to fix the default case to work correctly. Thanks again for tracking this down! Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 20:34:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECFAD106566B for ; Mon, 23 Jul 2012 20:34:09 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9F63B8FC18 for ; Mon, 23 Jul 2012 20:34:09 +0000 (UTC) Received: by qabg1 with SMTP id g1so1512690qab.13 for ; Mon, 23 Jul 2012 13:34:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XCeSwg4z5BXxJLxEpcYhmbIo3/H/fjKgza4HXhcCY08=; b=oxKVb04M7K+2fX8kXUeOtzLvksguVbwDU46EmWmJcm6lt6JHHO3jxO4YZ9ORUuTCoi oIu2+13VlI0/DFGNAeshyEoeEZUzJFd70epAI6jU5IAWZs+VtvaqNl9fnp/9wmW+5IBd qIay3mn5QXU27S5l9DFNohTJQ7bBKd/RQpJVq/cTJAC0DpWjEhzY7KLCzDoJrfBZWWuJ am2qVPolm0RmI+TncN5agWGODM79Tvfq/8uLfWdl2I8ZImxMjormHga5o7+NksXqdf6a 66xMlqpZlwmVAv5Xwv72n5Z3Jfh6QJTdZ9ZXZ9GMa5lBxbp7dvjcGP3rWhhbiXG/IOH4 J/qw== MIME-Version: 1.0 Received: by 10.224.59.13 with SMTP id j13mr26373510qah.44.1343075649114; Mon, 23 Jul 2012 13:34:09 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 13:34:09 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 16:34:09 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 20:34:10 -0000 Setting the configuration with ex: create_args_wlan0="wlanmode hostap wlanaddr f8:d1:11:38:3c:e5" Results in the Beacon frame source address and the BSS Id in the Beacon frame both being set the same value. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 20:35:58 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64659106566B for ; Mon, 23 Jul 2012 20:35:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id D0C018FC12 for ; Mon, 23 Jul 2012 20:35:57 +0000 (UTC) Received: by laai10 with SMTP id i10so355684laa.13 for ; Mon, 23 Jul 2012 13:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MlGIBZvtyyfRMc/NHMqYtAwEnow1UVOvQB1lv8lYh9E=; b=bWvthb4Vjec/EfrA9sYGeYuWAGQUKoBCBtRjMCf4VFegkE5cfRNpVtbJi40oPLFyGz ajZ3tzA22r7wYI++9Sc+LWKL1zh463iFjRgtCWdF7Oc4ZrJ4eC7BnBs3jDR3QKE24EQP 2iJUILOOKaYkgbj/MPhSYykQgp3AnMn/RLBSXTzKCgRXt9Ku2IAEpnZnRLzxh8pLworH d9gDTISME4V+LGkQnb0NmckHs+QvHKaCumfob+QkN+GU7mmbCpMN49qw+T9BQYR/QQMR XGiHZ4Kefx6RsEayXBD8u835mykkjAAC1/J6lE5VrnqBf8OADaWtgj7KC42okInUN7Kg VMEA== MIME-Version: 1.0 Received: by 10.112.84.65 with SMTP id w1mr8498783lby.40.1343075756644; Mon, 23 Jul 2012 13:35:56 -0700 (PDT) Received: by 10.112.20.197 with HTTP; Mon, 23 Jul 2012 13:35:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 13:35:56 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 20:35:58 -0000 On 23 July 2012 13:34, Kim Culhan wrote: > Setting the configuration with ex: > > create_args_wlan0="wlanmode hostap wlanaddr f8:d1:11:38:3c:e5" > > Results in the Beacon frame source address and the BSS Id in the Beacon frame > both being set the same value. Right. but you had that same MAC set for all VAPs? So each of your hostap instances has the same MAC? Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 21:09:21 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6B05106567B for ; Mon, 23 Jul 2012 21:09:21 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5D85A8FC14 for ; Mon, 23 Jul 2012 21:09:21 +0000 (UTC) Received: by qcsg15 with SMTP id g15so4241956qcs.13 for ; Mon, 23 Jul 2012 14:09:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=65Nn40ePPgxMahxPoFYA7wtabjGsElJAqoOrjGbZYBY=; b=BYGcXBq98QEGjhjvyX2E6kgDUCHNOIMAwxtdHVp+nTytDuINLyHT0fiSSO7v7+PeN+ tfZG6+u6h8GTcUutuchytSXs33LIa6+3PZBieK9eMCzFEMFlEjqcBg0xidD/7l+ZXAy6 0LnOEFqJPxbKiE3CZVSadkvBpj8YM6bKdnFPsvMUhavC/No4aEbizJjj41awFrhz0UE6 SPx3eZXcZmRtLF7/1JYTymXnNYLPoPYYjMKY0nNTagCtBhea5Gq7daY3ZvygjV130qXd F9nrQDE8fggT6Od9nNS8F+wM9d+KTP6luB/rYOLRRwC2hJm6Dt5tkpv/soQ5e+mXa1Zt 2Enw== MIME-Version: 1.0 Received: by 10.224.101.193 with SMTP id d1mr26646919qao.20.1343077760622; Mon, 23 Jul 2012 14:09:20 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Mon, 23 Jul 2012 14:09:20 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Jul 2012 17:09:20 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: multi vap Multi-SSID unique bssid eliminates client connect failures X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 21:09:22 -0000 On Mon, Jul 23, 2012 at 4:35 PM, Adrian Chadd wrote: > On 23 July 2012 13:34, Kim Culhan wrote: >> Setting the configuration with ex: >> >> create_args_wlan0="wlanmode hostap wlanaddr f8:d1:11:38:3c:e5" >> >> Results in the Beacon frame source address and the BSS Id in the Beacon frame >> both being set the same value. > > Right. but you had that same MAC set for all VAPs? > So each of your hostap instances has the same MAC? At some point they were the same, which worked very poorly, and later in a way where they were supposed be automagically assigned unique numbers. At that point there would be 2 addresses of 4 the same until I arrived at the latest configuration. -kim From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 22:59:58 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E66A2106564A; Mon, 23 Jul 2012 22:59:58 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BA0F98FC0C; Mon, 23 Jul 2012 22:59:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6NMxwPD085819; Mon, 23 Jul 2012 22:59:58 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6NMxwEt085815; Mon, 23 Jul 2012 22:59:58 GMT (envelope-from adrian) Date: Mon, 23 Jul 2012 22:59:58 GMT Message-Id: <201207232259.q6NMxwEt085815@freefall.freebsd.org> To: adrian@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Cc: Subject: Re: kern/170098: [ath] [net80211] VAPs (Virtual access points) with Atheros ath driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 22:59:59 -0000 Old Synopsis: virtual access points with Atheros ath driver New Synopsis: [ath] [net80211] VAPs (Virtual access points) with Atheros ath driver Class-Changed-From-To: doc-bug->sw-bug Class-Changed-By: adrian Class-Changed-When: Mon Jul 23 22:59:09 UTC 2012 Class-Changed-Why: This is partially a docs and partially a kern problem. Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Mon Jul 23 22:59:09 UTC 2012 Responsible-Changed-Why: This is partially a docs and partially a kern problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=170098 From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 24 12:56:08 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74FEA1065687 for ; Tue, 24 Jul 2012 12:56:08 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id F28038FC2F for ; Tue, 24 Jul 2012 12:56:07 +0000 (UTC) Received: by qaat11 with SMTP id t11so1855248qaa.13 for ; Tue, 24 Jul 2012 05:56:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=rP0AhI3KQ7OoUA3fiZ9iJF9+oQwmIgfYIydGCikpUzY=; b=UMFwY8ILmh6sOFJsHk+Ato5oONfbQRmJnp1uw1kjnELjet6GvT1uy/fCWUSVQVjJIF UbDixbxIaHjJfIvaYTPGYEtPYaFte9l7PfESAQlGpYdVF3DP/yBVHbiGg9Lujnh+1DL7 8TFlTNk8mTUwdheQBrHmYtJYwtC01LDRXC4+BhRPCCCd/C94+N9VJza5sGbz41gYKumc 2AuYjYcccpP06m3kxOIdeHgWQ+nRBqsosbnOYxwZ2HjTULuGFtzZgMMdhrJNgAjIZhnk sIxM9bws36LBqKDAjTyXZuwaGnvrLQLlU2FDTRGRhXpZ5UbPZNMbdIL7iXVXQ2IoX3FT 9EiQ== MIME-Version: 1.0 Received: by 10.224.71.11 with SMTP id f11mr11857203qaj.41.1343134567250; Tue, 24 Jul 2012 05:56:07 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Tue, 24 Jul 2012 05:56:07 -0700 (PDT) Date: Tue, 24 Jul 2012 08:56:07 -0400 Message-ID: From: Kim Culhan To: freebsd-wireless@freebsd.org Content-Type: multipart/mixed; boundary=bcaec5196ffdc439c204c592e28f X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: net80211 related LOR hard hang at reboot X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 12:56:08 -0000 --bcaec5196ffdc439c204c592e28f Content-Type: text/plain; charset=ISO-8859-1 Running FreeBSD 10-current r238721M After issuing a reboot command, the machine hangs and must be power-cycled. The details of a net80211 related LOR with KDB backtrace is printed to the console. In most cases the last item printed to the console before the hard hang is: pflog0: promiscuous mode disabled In an unusual case the last line: Waiting (max 60 seconds) for system process 'bufdaemon' to stop... (Hangs here..) Please see attached console pic. thanks -kim --bcaec5196ffdc439c204c592e28f-- From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 24 13:31:58 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 158D71065670 for ; Tue, 24 Jul 2012 13:31:58 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id C3B658FC0C for ; Tue, 24 Jul 2012 13:31:57 +0000 (UTC) Received: by qabg1 with SMTP id g1so1880933qab.13 for ; Tue, 24 Jul 2012 06:31:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=H9p3z9pbV8hO+p2zM2NIUOKjkZL+1CPEGaMxI2kTT74=; b=xSaDlskXxBMyS4tTBnokeC6hwoqYLpf0HDOMHwy+DoBIkfdUj3ry5tPTIPC6Rfu86l hSk7qOmQuPRHSVNRgBf5n34rig3NP2iMc9vd4/7DitNcKs9nVujGwRURmry0lJCwUQKZ +gAzmoangq6xqwlTIQ2lBaD/XoYMDb0xNN73CnimGtk8NsKdsGH2a4iyM9pYlyjiuFE3 7loMr2H0/oDhYx7MNmJHXTHCweuC/1SY0ybHza5raWsZ56Z2lcAybZyij2DrgUkNV7d5 e0UX8ZE6w32he0VqbeexWC5lVrn4f+iK+F/3ea0ue1/BrnqrN5nkhBIfZqNCqxT9BuLL 8Bow== MIME-Version: 1.0 Received: by 10.224.189.137 with SMTP id de9mr30756676qab.7.1343136717030; Tue, 24 Jul 2012 06:31:57 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Tue, 24 Jul 2012 06:31:57 -0700 (PDT) Date: Tue, 24 Jul 2012 09:31:57 -0400 Message-ID: From: Kim Culhan To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: net80211 related LOR hard hang at reboot -link to console pic X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 13:31:58 -0000 The console at the point of hard hang looks like: https://picasaweb.google.com/lh/photo/GLOTsUckjvUk8Jq2iHBBU_vlauO1nZapmUqNnSQpTnM?feat=directlink -kim From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 25 12:30:01 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9677106564A for ; Wed, 25 Jul 2012 12:30:01 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9360C8FC18 for ; Wed, 25 Jul 2012 12:30:01 +0000 (UTC) Received: by qabg1 with SMTP id g1so2650265qab.13 for ; Wed, 25 Jul 2012 05:30:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=xFLaiXQk8zqMnjzHFPISESlYiHUuIqmEGNdbP3w0VP8=; b=uj/4ZuLe2dC8LUU5vwq7J0cBp/754uq6t3b3YoCnOJURREruOydRFAZ3wASyBfV3j5 DJLSW5nSaD3X0z2BH7rDCetM8NwK9kfM0R/ixEOcBNQslg+6opBy4OglzJZSxjnvzcTz 3ABPn6e8Sf9CRqUREENC4lQUEwnFuX0dYrI2USaNLtfWeTyoaeJiwmFvGUdw13cY5PFB UDbkPR8Be/oU3FnmaoF3/1BCJNtaIXAV3RWN/WLTZfVE5haKtUBxnpmf6xYE8jPyHrSE 3SBI40AWndrkqwvtlsxxrIfQcoWrxPggIPUvqIivm6CatJ2hdHoNaGAhWBg6hCWcDYs+ F3+Q== MIME-Version: 1.0 Received: by 10.229.136.8 with SMTP id p8mr10924070qct.150.1343219400865; Wed, 25 Jul 2012 05:30:00 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Wed, 25 Jul 2012 05:30:00 -0700 (PDT) Date: Wed, 25 Jul 2012 08:30:00 -0400 Message-ID: From: Kim Culhan To: freebsd-wireless@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: net80211 related panic -dropped to debugger X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 12:30:01 -0000 On one occasion while rebooting, after apparently hanging for nearly 1 minute, the system dropped into the debugger. The console: https://picasaweb.google.com/lh/photo/ZfBa39nNXej6S-UJCjaPACQOaUjNSQCUhVGtskp5mqc?feat=directlink In an attempt to make some headway finding the cause of the hard hang referred to in an earlier post, the 4 memory sticks were replaced with the memory from another machine. When this had no effect, 2 of the 4 memory modules (2MB) were removed and it was with this setup the system dropped to the debugger on the next reboot. Unfortunately this was the last time it entered the debugger, after several reboots so far, and I plan to keep trying. Any thoughts on this are greatly appreciated. thanks -kim From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 25 14:15:38 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8ABDF106564A for ; Wed, 25 Jul 2012 14:15:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 442228FC0C for ; Wed, 25 Jul 2012 14:15:38 +0000 (UTC) Received: by ghbz22 with SMTP id z22so901001ghb.13 for ; Wed, 25 Jul 2012 07:15:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=uzCHPmT+yFgvVg4WpoWOZn7Jo3KsXmo67etn6iG9sl4=; b=C3un7mmkTXgnbiI6DtzTne8QlGWgLLhVc1ku0DlqkMJybn6TNX9VQyqvIfIJcye04G bvvOi6iWmrwEQe4EVkvcIuXJ65PdK1ZBgyk839/GKTw0LAuOgHP6mfpTkAnpfBykDPiR M8/6zo9SsuEi9iX2HdwdQpON4H97SlZaGdl8wVQlCuVxGufusu+V3ruWhNpMBtVaJoAk 8JnwUeYBO+E9zlcQiKOjcZ4hxB8XIXxtFpKOf5dgTMMfPoOmWqCeO28mmlFL7I92xv9q QeBanQLSra268lh0qLlsxpX3yIMg00eCtvIKt7906mmPq78QoeOwG39nBTCimUMg4tuR DYLQ== MIME-Version: 1.0 Received: by 10.68.222.163 with SMTP id qn3mr53651589pbc.135.1343225737465; Wed, 25 Jul 2012 07:15:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.191.138 with HTTP; Wed, 25 Jul 2012 07:15:37 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Jul 2012 07:15:37 -0700 X-Google-Sender-Auth: m5lepBFCCkXNLVSDl70TtImA8Sg Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 related panic -dropped to debugger X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 14:15:38 -0000 On 25 July 2012 05:30, Kim Culhan wrote: > On one occasion while rebooting, after apparently hanging for nearly 1 > minute, the system > dropped into the debugger. > > The console: > > https://picasaweb.google.com/lh/photo/ZfBa39nNXej6S-UJCjaPACQOaUjNSQCUhVGtskp5mqc?feat=directlink Hm, next time you have this happen, can you please enter 'bt' so we can see the call stack? Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 25 14:24:55 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2858A106566C; Wed, 25 Jul 2012 14:24:55 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) by mx1.freebsd.org (Postfix) with ESMTP id C25268FC08; Wed, 25 Jul 2012 14:24:54 +0000 (UTC) Received: by qcab12 with SMTP id b12so528030qca.18 for ; Wed, 25 Jul 2012 07:24:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=thckTULFV/sGoOQ8N2V53vhC+9V7+PI4rG1m6LXZBX0=; b=fgYlj5GiZ22LclfoUZxKcI1/3+zBMUDldsxQucF5GGc5yj07BJyRdfDpP9USEMIslE GhTEQGysrxh3UclGrPGGsMu4svOqjEtwX/eZH0Z/hc4FCPBRH8JuTLt+WcW4pOyENb3P s4mPrqgrjY+T7O07jfj9/yW4bOv2ipgvrurCyeXTwsU0THBzanPFbEZgP4OUMyGP6n65 J38rRRYmApNfCw2SbTPoT8dcIoo6fnzWFeyQevMDe2MlWUeKttd3Feix8bDZbdQhqvs+ vOT5jly1Xoih+VlJzVewp09zv/KAVvmoq5wcogm6jpRpyJ1Xd0U5isC0xUxqIYgKfFaj 1Csw== MIME-Version: 1.0 Received: by 10.229.137.12 with SMTP id u12mr11311292qct.28.1343226288384; Wed, 25 Jul 2012 07:24:48 -0700 (PDT) Received: by 10.229.39.12 with HTTP; Wed, 25 Jul 2012 07:24:48 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Jul 2012 10:24:48 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 related panic -dropped to debugger X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 14:24:55 -0000 On Wed, Jul 25, 2012 at 10:15 AM, Adrian Chadd wrote: > On 25 July 2012 05:30, Kim Culhan wrote: >> On one occasion while rebooting, after apparently hanging for nearly 1 >> minute, the system >> dropped into the debugger. >> >> The console: >> >> https://picasaweb.google.com/lh/photo/ZfBa39nNXej6S-UJCjaPACQOaUjNSQCUhVGtskp5mqc?feat=directlink > > Hm, next time you have this happen, can you please enter 'bt' so we > can see the call stack? Yes, I really regret not doing that.. -kim From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 26 01:24:27 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5D1DE106564A for ; Thu, 26 Jul 2012 01:24:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 323978FC12 for ; Thu, 26 Jul 2012 01:24:27 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so2498961pbb.13 for ; Wed, 25 Jul 2012 18:24:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6L9wY9y+uiN23AxzWB9OA5GHpCaFqnDMRDCwfjX4DkQ=; b=gxMZr/Xddrlp40daoM7fY5h7PypUKrSRKMUSr3f5NnNySNwIYWmPwmIC38qphmCPUH shf3rSpH1ErvqU9XG5b/4bmFkpePB9jLAElx5kk7ETmeUhp64Dilv8uaCF8r0a4UZHvg zUqg/nUUKlFxHzx8DzlLRwaxw8bNA3J1kprO4Y90MeQF+nuufSeFl0tCmVU+CvTnCh0e W0wP5PzZnJZnaDrATGtpyVlvr3yL1A3Y/mAHWrOYqcU9JQ9csvwgUvyvCJIrcZhLpqDi cUGbMjHKysKEDRrRlPT+RUwQ66OZ/lofnAB+6qW/1JxK8leu3/v6yVXb6+P9PMPA9Ydo LkMg== MIME-Version: 1.0 Received: by 10.68.218.7 with SMTP id pc7mr638436pbc.88.1343265866773; Wed, 25 Jul 2012 18:24:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.66.136 with HTTP; Wed, 25 Jul 2012 18:24:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Jul 2012 18:24:26 -0700 X-Google-Sender-Auth: yGG5S4Ri1fe1tGiBxAiIjxa7suI Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: net80211 related panic -dropped to debugger X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2012 01:24:27 -0000 After Kim took some photos, it looks like the hang is indeed due to that LOR. So, who would like to tackle figuring out how to correctly fix things up so that LOR goes away? I'm still knee deep in fixing up the TX path for AR93xx support, as well as trying to track down these BAR TX failures reported by Rui/Lev. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 27 19:21:39 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72DA7106566B for ; Fri, 27 Jul 2012 19:21:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 46CB28FC0A for ; Fri, 27 Jul 2012 19:21:39 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so5863451pbb.13 for ; Fri, 27 Jul 2012 12:21:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GYcdVfNChWY2aBt3mMOmm3OVnP3SyqlqwNxTd8XGHJM=; b=H3ibI61NEFb8ahe/WoSAltUgmMbcUSgJdD4hfq/nvV5rL4vab+K5uRmz57Uvf8wHg3 GHsn9l+YGi/UFIchAa+v5im/T0pds6572C6xUSVt65lNeviOuJWZH4/Br3OKjEHiwE37 W8dLr2AZ/MxgWuL5j5eQnn6p43iFx6GEW6G+BAg4DC8+6Kf97zgKW6cDHsfTwP2z/Z98 llaWFnRH/NjAGf0ms0A12gE79YXwZVq8tYEeTDjKEkqWk9XOHVwq84cHh7zmf4czeiXc KP2hUcSlpKnLEShKKutGFcUAKf/iPNsAp/W4eGHzKgrT555FQAqXTyfIyYk4LuIJC9W0 4CCA== MIME-Version: 1.0 Received: by 10.68.228.2 with SMTP id se2mr16303447pbc.109.1343416899049; Fri, 27 Jul 2012 12:21:39 -0700 (PDT) Received: by 10.68.66.136 with HTTP; Fri, 27 Jul 2012 12:21:39 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Jul 2012 12:21:39 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath lor X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2012 19:21:39 -0000 Ok, hm. I wonder if the "correct" thing to do here is to ensure the comlock is NOT held when iterating through nodes. I don't know if net80211 ever had the lock hierarchy defined/designed in any detail. So it's either: * ieee80211_iterate_nodes() shouldn't be called with the comlock/nodelock/node iterate lock held; * ieee80211_iterate_nodes() must always be called with the comlock held. I bet it's the former. The latter is too scary. :-) I'll add a lock witness check on a local device and get a backtrace. If you'd like to immediately crash your device, you could do the same. If you're feeling very brave and immediately crash-y, try: Index: sys/net80211/ieee80211_node.c =================================================================== --- sys/net80211/ieee80211_node.c (revision 238389) +++ sys/net80211/ieee80211_node.c (working copy) @@ -2163,6 +2163,12 @@ struct ieee80211_node *ni; u_int gen; + /* + * To avoid LORs, ic must not be held here as the + * called function may acquire ic. + */ + IEEE80211_UNLOCK_ASSERT(nt->nt_ic); + IEEE80211_NODE_ITERATE_LOCK(nt); gen = ++nt->nt_scangen; restart: Index: sys/net80211/ieee80211_freebsd.h =================================================================== --- sys/net80211/ieee80211_freebsd.h (revision 238389) +++ sys/net80211/ieee80211_freebsd.h (working copy) @@ -53,6 +53,8 @@ #define IEEE80211_UNLOCK(_ic) mtx_unlock(IEEE80211_LOCK_OBJ(_ic)) #define IEEE80211_LOCK_ASSERT(_ic) \ mtx_assert(IEEE80211_LOCK_OBJ(_ic), MA_OWNED) +#define IEEE80211_UNLOCK_ASSERT(_ic) \ + mtx_assert(IEEE80211_LOCK_OBJ(_ic), MA_NOTOWNED) /* * Node locking definitions. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 27 19:33:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FAD910657CE for ; Fri, 27 Jul 2012 19:33:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id EC6F48FC0C for ; Fri, 27 Jul 2012 19:33:13 +0000 (UTC) Received: by ghbz22 with SMTP id z22so4243721ghb.13 for ; Fri, 27 Jul 2012 12:33:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=g0f6Rf7dG9c6QHfcziANhkqZBC1qvpltpteWyJlph1w=; b=xrHumGP8U/VdJmdNm2lz+gCBXFzZC8sjQPm6csFRs7+BIMU+4wxD+IVltAve/OXKuy amyqc/iKl2wvSHEsR0zHpTZq9QIuz1eJrfykjH5qU8yi0N71AfX0lRUIiEutIsObQDYN 2m/DDe4g0W0X4uVb8yeTYT2Naq4v1WV+aRatB82pV8JTp4zbeU9GsJH+hpdXeO2gR8Y8 uUIxyksy15PtgGPIJyV8rvyQLVl3cl01JA13ZLvldmlE3UWoHC60SDu9f3/mPB8p/oyh It79GKeaXDcPdl+KEoFKSTVN++19+fdoaKeo57hM7c/xMkPNK5dT6AiWkuKIU2/BHENK FWiQ== MIME-Version: 1.0 Received: by 10.66.73.70 with SMTP id j6mr7847908pav.5.1343417593074; Fri, 27 Jul 2012 12:33:13 -0700 (PDT) Received: by 10.68.66.136 with HTTP; Fri, 27 Jul 2012 12:33:13 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Jul 2012 12:33:13 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath lor X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2012 19:33:14 -0000 .. hm, so. This is quite annoying, really. ieee80211_iterate_nodes() is called from hostap_newstate() to do a bunch of things, including: * calling sta_diassoc() on each STA; * handling CSA for each STA (for DFS channel change) via sta_csa(); * dropping stations when doing a CSA (via sta_drop()); Now, at this point the _newstate() routine has the comlock (IEEE80211_LOCK()) held. So, any function that is passed to ieee80211_iterate_nodes() that also tries to grab the comlock is going to silently fail. It may _be_ that the only sensible thing to do here is to force the comlock is held before calling ieee80211_iterate_nodes(), and then update all the functions that it calls to require the comlock be held. So, that'd currently be (in net80211, ignoring what are in drivers atm): * sta_leave() * load_ucastkey() * sta_disassoc() * sta_csa() * sta_drop() * get_sta_space() * get_sta_info() * domlme() * mesh_vdetach_peers() * mesh_checkid() * get_adhoc_rssi() * get_hostap_rssi() * get_mesh_rssi() .. and that's kind of scary, because a lot of those will call into the driver and do things like transmit frames; and we absolutely can't hold the comlock when doing that or all kinds of bad LORs will occur. Fixing this is going to take a little more time/patience. I'm open to other ideas/suggestions on this. Adrian