From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 27 15:36:28 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 209A6A57; Sun, 27 Oct 2013 15:36:28 +0000 (UTC) (envelope-from matthias@petermann-it.de) Received: from mail.s1.d2ux.org (static.209.96.9.5.clients.your-server.de [5.9.96.209]) by mx1.freebsd.org (Postfix) with ESMTP id CFEDC2D20; Sun, 27 Oct 2013 15:36:27 +0000 (UTC) Received: from mail.s1.d2ux.org (mail [10.0.0.3]) by mail.s1.d2ux.org (Postfix) with ESMTP id 5E30C84F25B2; Sun, 27 Oct 2013 16:36:20 +0100 (CET) Received: from mail.s1.d2ux.org ([10.0.0.3]) by mail.s1.d2ux.org (mail.s1.d2ux.org [10.0.0.3]) (amavisd-new, port 10024) with ESMTP id dGgladJjCm0j; Sun, 27 Oct 2013 16:36:18 +0100 (CET) Received: from workstation.local (p5DDABE5E.dip0.t-ipconnect.de [93.218.190.94]) by mail.s1.d2ux.org (Postfix) with ESMTPSA id 4456C84F2580; Sun, 27 Oct 2013 16:36:18 +0100 (CET) Message-ID: <526D3255.8090109@petermann-it.de> Date: Sun, 27 Oct 2013 16:33:41 +0100 From: Matthias Petermann User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: cg@cgross.info Subject: Re: Centrino Wireless N2230 support References: <20130913112427.Horde.Lr2e32AbzvcQIrrWuDh-dg1@d2ux.org> <001e01ceb064$80168220$80438660$@info> <526A5EBD.0@petermann-it.de> <3f4c1e2627b7da9b271b55f10ad9f7e5@cgross.info> In-Reply-To: <3f4c1e2627b7da9b271b55f10ad9f7e5@cgross.info> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-drivers@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Oct 2013 15:36:28 -0000 Hello Cedric, Am 26.10.2013 10:56, schrieb cg@cgross.info: > You must get and build net80211 from -HEAD also. It's why you have > this kind of compile error. Thanks, this was exactly my miss. With net80211 from -HEAD it built. I first tried IWL (https://github.com/KreizIT/freebsd-iwl) with FreeBSD 9.2-RELEASE. When I try to load the module with kldload if_iwl the kernel panics: Unread portion of the kernel message buffer: iwl0: mem 0xf1500000-0xf1501fff irq 17 at device 0.0 on pci2 iwl0: iwl_read_eeprom_ht40: no entry for channel 1 iwl0: iwl_read_eeprom_ht40: no entry for channel 2 iwl0: iwl_read_eeprom_ht40: no entry for channel 3 iwl0: iwl_read_eeprom_ht40: no entry for channel 4 iwl0: iwl_read_eeprom_ht40: no entry for channel 5 iwl0: iwl_read_eeprom_ht40: no entry for channel 6 iwl0: iwl_read_eeprom_ht40: no entry for channel 7 panic: ieee80211_get_ratetable: no rate table for channel; freq 0 flags 0x0 cpuid = 3 KDB: stack backtrace: #0 0xffffffff80947986 at kdb_backtrace+0x66 #1 0xffffffff8090d9ae at panic+0x1ce #2 0xffffffff80a1399e at ieee80211_get_ratetable+0x10e #3 0xffffffff809eb3a5 at ieee80211_media_init+0x355 #4 0xffffffff809eb69e at ieee80211_ifattach+0xae #5 0xffffffff81864914 at iwl_attach+0xbd4 #6 0xffffffff8186d360 at iwl_pci_attach+0x2f0 #7 0xffffffff809405dc at device_attach+0xcc #8 0xffffffff8064a0ca at pci_driver_added+0xda #9 0xffffffff8093e765 at devclass_driver_added+0x75 #10 0xffffffff8093f2a3 at devclass_add_driver+0x103 #11 0xffffffff808f80c8 at module_register_init+0xa8 #12 0xffffffff808f004e at linker_load_module+0x85e #13 0xffffffff808f0688 at kern_kldload+0xb8 #14 0xffffffff808f08a4 at sys_kldload+0x84 #15 0xffffffff80cf187a at amd64_syscall+0x5ea #16 0xffffffff80cdbff7 at Xfast_syscall+0xf7 Any ideas? Kind regards, Matthias From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 28 04:20:12 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A2613680; Mon, 28 Oct 2013 04:20:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 32B192F91; Mon, 28 Oct 2013 04:20:12 +0000 (UTC) Received: by mail-qe0-f43.google.com with SMTP id nc12so3672947qeb.16 for ; Sun, 27 Oct 2013 21:20:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=Euq6vdT1ejnvaAQVxZKV/ZLl2eTSvTrYEgM5hqMOhf8=; b=UgPEXBDape/F+6gHXqmMK5x2QcpGgRERUDEl22PqYnfK2QZyjbtBM1V+JKLmoNFT1O bR+oJ9e4dR+yz8R9MsDIdc7ra1mWq5jrPgdsrY+0ehStiWaO+04WVHXm4t69ekQxgg3c 8QpHp1rZ+kEm7QH21zXJwKJy1Wt9BdRRYNQPsTwJGB1VmSj0yB/y5hlM3pOGG9fBEip2 fskEMWnAzicOapLXxiemsGVxoYMDXjYbdYnVa+ZO9nbDq8h4nUamckBq9Qz85MtT9y2U xCJ0ZusnPIeBIIZrBtQ/dvUAy8+InzqMUT4SnOpbszQZgOz8SvJgN+fvZo1/+d3qvyQp jnaA== MIME-Version: 1.0 X-Received: by 10.49.88.3 with SMTP id bc3mr26089619qeb.30.1382934011357; Sun, 27 Oct 2013 21:20:11 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sun, 27 Oct 2013 21:20:11 -0700 (PDT) Date: Sun, 27 Oct 2013 21:20:11 -0700 X-Google-Sender-Auth: q2CEbAZ48SUlqQ8J58tPory3QSA Message-ID: Subject: [ath] testing bus write barriers From: Adrian Chadd To: "freebsd-wireless@freebsd.org" , FreeBSD PowerPC ML , freebsd-sparc64 , "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 04:20:12 -0000 Hi all, I'd like to add correct bus write barriers to the ath driver. Here's what I have thus far: http://people.freebsd.org/~adrian/ath/20131028-ath-bus-write-barriers.diff Now, it sucks that I'm doing a bus write barrier on _each_ write but fixing it requires a lot of HAL churn and that would, well, suck. PPC - this was a problem that was fixed by adding implicit write flushes in your bus space. This _should_ let you get rid of that (well, as long as you fix the rest of the drivers.) sparc64 - if you use a PCI or PCIe ath NIC in your sparc machine, please contact me and let me know. This should make it work (better.) MIPS - for mips24k it's not a big problem as register accesses are in the uncached section and are already in-order. But for mips74k and other superscalar architectures, it will need a flush otherwise things don't work (right.) I'd appreciate it if this could get some testing. Thanks, -adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 28 11:06:58 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A13C9B79 for ; Mon, 28 Oct 2013 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8DD9F248A for ; Mon, 28 Oct 2013 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9SB6wUl055284 for ; Mon, 28 Oct 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9SB6w7I055282 for freebsd-wireless@FreeBSD.org; Mon, 28 Oct 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Oct 2013 11:06:58 GMT Message-Id: <201310281106.r9SB6w7I055282@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 11:06:58 -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/181898 wireless [iwn] [patch] Centrino Advanced-N 6235 with latest iwn o kern/181694 wireless [iwn] [patch] Initialize hardware in iwn(4) resume cod o kern/181161 wireless [wl] config a old compaq wl-110 wireless card make ker o kern/181132 wireless [iwn] stream calculation is wrong for the Intel 4965 o kern/181100 wireless [bwi] Turning up bwi0 crashes / deadlocks the kernel o kern/180816 wireless [iwl] Intel Centrino Wireless-N 2200 not supported o kern/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170411 wireless [ath] Uninitialized variables in if_ath.c o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 178 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 29 04:27:32 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6947CBF; Tue, 29 Oct 2013 04:27:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 49C2526C8; Tue, 29 Oct 2013 04:27:31 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id i13so2641598qae.16 for ; Mon, 28 Oct 2013 21:27:30 -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:message-id:subject :from:to:cc:content-type; bh=lTpcHyGPuOHNuQFHIc1qdoXIMEVVjReu5BK7DCcMe1M=; b=d5mDUoJAew2tpjMV5msAxpqYyUBFY752Rl7o7Df4uZaQFBGHXHRIVyCGhQ8ru9LcaG y2EsoZeoWKs+9iAgf09J7wuBg6o/6JRwCnB7dr2uWrC170rK0rpm974KHVfn04PIxzta XqkpB0Kx/ckusDkwdoLtIbR/8hXiNFu5HfUp+u5LH39536kPig2fvN+Gtr8Tdf0gQObO 1lJy9Eqre2zglKePEJ4jh7JNm5btlOKOmKAUgybilFD/RDlayvDXH4YWGh/zDuXf5uMe Cto+xmq9DvRVw6vpujJCQZDLE7adtZyHUVekcr2Ua2bjtNX38OHhhOSBx6aGh3rN6z+t FwWw== MIME-Version: 1.0 X-Received: by 10.224.131.133 with SMTP id x5mr34486421qas.70.1383020850440; Mon, 28 Oct 2013 21:27:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 28 Oct 2013 21:27:30 -0700 (PDT) In-Reply-To: References: <201310251944.r9PJis6q004419@svn.freebsd.org> <20131027101106.GA2843@mole.fafoe.narf.at> <20131028190005.GA1509@mole.fafoe.narf.at> <20131028192731.GA1505@mole.fafoe.narf.at> Date: Mon, 28 Oct 2013 21:27:30 -0700 X-Google-Sender-Auth: 5GuFnQt8ls2U1b44yhwgvWqrONw Message-ID: Subject: Re: svn commit: r257133 - head/sys/dev/iwn From: Adrian Chadd To: Stefan Farfeleder , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 04:27:32 -0000 I've filed a PR. Please update to -HEAD and test. Thanks! -adrian On 28 October 2013 15:05, Adrian Chadd wrote: > Hi! > > Yup! So, the difference is in the rate being selected. > > It looks like the remote end is just plainly not ACKing the 11n > management frame being sent; but it totally ACKs the 11b CCK frame > being sent. > > So, thanks for pointing that out. I'll go and err, "fix" this mistake. > The driver should be doing what the stack says. Bernhard figured out a > couple years ago that doing 11n management frames to 11n devices is > not guaranteed to work, so we "fixed" that. I will go and figure out > why this is now broken for iwn. > > Thanks! > > Would you mind filing a PR with what we've gathered? > > > > -adrian > > > > On 28 October 2013 12:27, Stefan Farfeleder wrote: >> On Mon, Oct 28, 2013 at 12:07:17PM -0700, Adrian Chadd wrote: >>> Yeah: >>> >>> Oct 28 19:43:43 mole kernel: iwn5000_tx_done: qid 3 idx 4 retries 7 >>> nkill 0 rate a902 duration 686 status 83 >>> >>> status 0x83 is LONG_LIMIT, which meant it tried to transmit and it >>> failed to get an ACK each time. >>> >>> The rate control says: >>> >>> 0x02: the rate in question >>> bit 8: MCS >>> bit 11: HT40 >>> bits 14+15: transmit antennas A+B >>> >>> .. and it's an association/management frame, which is odd as they're >>> not supposed to be sent as 11n HT40 frames like this. >>> >>> can you do the same experiment but with the patch reverted? I'd like >>> to see what the selected rate is. >> >> Ok, here's the output with r257155 and r257133 reverted: >> >> http://pastebin.com/CJzsTANv >> >> Stefan From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 29 04:54:40 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4B039394; Tue, 29 Oct 2013 04:54:40 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1DF5E27EA; Tue, 29 Oct 2013 04:54:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9T4sdjW010212; Tue, 29 Oct 2013 04:54:39 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9T4sdtV010211; Tue, 29 Oct 2013 04:54:39 GMT (envelope-from linimon) Date: Tue, 29 Oct 2013 04:54:39 GMT Message-Id: <201310290454.r9T4sdtV010211@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/183428: [net80211] [iwn] Some APs seem to announce HT but no HT rates X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 04:54:40 -0000 Synopsis: [net80211] [iwn] Some APs seem to announce HT but no HT rates Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Tue Oct 29 04:54:27 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=183428 From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 29 04:55:11 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 761BC400; Tue, 29 Oct 2013 04:55:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B59B27F7; Tue, 29 Oct 2013 04:55:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9T4tBtw010296; Tue, 29 Oct 2013 04:55:11 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9T4tBGa010295; Tue, 29 Oct 2013 04:55:11 GMT (envelope-from linimon) Date: Tue, 29 Oct 2013 04:55:11 GMT Message-Id: <201310290455.r9T4tBGa010295@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/183430: [iwn] latest change to the rate code setup uses 11n rates on an 11n channel when 11n rates aren't provided X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 04:55:11 -0000 Synopsis: [iwn] latest change to the rate code setup uses 11n rates on an 11n channel when 11n rates aren't provided Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Tue Oct 29 04:54:52 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=183430 From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 29 09:17:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E19A9C80; Tue, 29 Oct 2013 09:17:33 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from fep17.mx.upcmail.net (fep17.mx.upcmail.net [62.179.121.37]) by mx1.freebsd.org (Postfix) with ESMTP id 8EAAC262B; Tue, 29 Oct 2013 09:17:32 +0000 (UTC) Received: from edge04.upcmail.net ([192.168.13.239]) by viefep22-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20131029091719.GCU23634.viefep22-int.chello.at@edge04.upcmail.net>; Tue, 29 Oct 2013 10:17:19 +0100 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge04.upcmail.net with edge id ixHJ1m0432xdvHc03xHKsd; Tue, 29 Oct 2013 10:17:19 +0100 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id D005B6D47B; Tue, 29 Oct 2013 10:17:18 +0100 (CET) Date: Tue, 29 Oct 2013 10:17:18 +0100 From: Stefan Farfeleder To: Adrian Chadd Subject: Re: svn commit: r257133 - head/sys/dev/iwn Message-ID: <20131029091718.GA1520@mole.fafoe.narf.at> References: <201310251944.r9PJis6q004419@svn.freebsd.org> <20131027101106.GA2843@mole.fafoe.narf.at> <20131028190005.GA1509@mole.fafoe.narf.at> <20131028192731.GA1505@mole.fafoe.narf.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "freebsd-wireless@freebsd.org" , "src-committers@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 09:17:34 -0000 On Mon, Oct 28, 2013 at 09:27:30PM -0700, Adrian Chadd wrote: > I've filed a PR. > > Please update to -HEAD and test. Ok thanks, will do. Probably I won't be able before tomorrow though. Stefan From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 30 19:17:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A5CEDE4; Wed, 30 Oct 2013 19:17:52 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from fep19.mx.upcmail.net (fep19.mx.upcmail.net [62.179.121.39]) by mx1.freebsd.org (Postfix) with ESMTP id 4F8DF2C66; Wed, 30 Oct 2013 19:17:50 +0000 (UTC) Received: from edge02.upcmail.net ([192.168.13.237]) by viefep19-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20131030191749.MDI6747.viefep19-int.chello.at@edge02.upcmail.net>; Wed, 30 Oct 2013 20:17:49 +0100 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge02.upcmail.net with edge id jXHp1m0082xdvHc02XHpfj; Wed, 30 Oct 2013 20:17:49 +0100 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id E10A96D47B; Wed, 30 Oct 2013 20:17:48 +0100 (CET) Date: Wed, 30 Oct 2013 20:17:48 +0100 From: Stefan Farfeleder To: Adrian Chadd Subject: Re: svn commit: r257133 - head/sys/dev/iwn Message-ID: <20131030191748.GA1463@mole.fafoe.narf.at> References: <201310251944.r9PJis6q004419@svn.freebsd.org> <20131027101106.GA2843@mole.fafoe.narf.at> <20131028190005.GA1509@mole.fafoe.narf.at> <20131028192731.GA1505@mole.fafoe.narf.at> <20131029091718.GA1520@mole.fafoe.narf.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131029091718.GA1520@mole.fafoe.narf.at> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "freebsd-wireless@freebsd.org" , "src-committers@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 19:17:52 -0000 On Tue, Oct 29, 2013 at 10:17:18AM +0100, Stefan Farfeleder wrote: > On Mon, Oct 28, 2013 at 09:27:30PM -0700, Adrian Chadd wrote: > > I've filed a PR. > > > > Please update to -HEAD and test. > > Ok thanks, will do. Probably I won't be able before tomorrow though. Seems to work as before, thanks! Stefan From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 30 19:18:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7BBFE241; Wed, 30 Oct 2013 19:18:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E36882C78; Wed, 30 Oct 2013 19:18:38 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id n7so1046284qcx.41 for ; Wed, 30 Oct 2013 12:18:38 -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:message-id:subject :from:to:cc:content-type; bh=7RBMDZoLj4RG7QacXBH7t3yLsiWlWB63FmqrUaXk0Pg=; b=PzpijeuWqTDTqRMHLXs6mtnD8Q/o036M1j9Ws0vJqywYNxSTmjPZdOcpVLdSpaSpXo ttbXY0KuONhvfApz9dnKBAYt6v+bJSo7pW5BfMoSpXsP0b194SnY7lY8r8q9gA2ovUxX WzZJar7oXdTdKq9beDK0HnMrOiOOK4FUd6g3T3Ibwg4J2gW/O5YKcdIz0EXNBZJ/Z/to zAktrRpmtOYYeXgWFaRDpyIMHajSWhBS28tg5MV1vHBrT/K3pFpFPUCh/djGw9zLBAti KXuzkS52rH3+aScU716Vhq06NmBtwyvQtG8lZPtzwSNTqgCnAZ5USXY/K47HTH2KTUMU BVBQ== MIME-Version: 1.0 X-Received: by 10.224.51.131 with SMTP id d3mr182048qag.0.1383160717999; Wed, 30 Oct 2013 12:18:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 30 Oct 2013 12:18:37 -0700 (PDT) In-Reply-To: <20131030191748.GA1463@mole.fafoe.narf.at> References: <201310251944.r9PJis6q004419@svn.freebsd.org> <20131027101106.GA2843@mole.fafoe.narf.at> <20131028190005.GA1509@mole.fafoe.narf.at> <20131028192731.GA1505@mole.fafoe.narf.at> <20131029091718.GA1520@mole.fafoe.narf.at> <20131030191748.GA1463@mole.fafoe.narf.at> Date: Wed, 30 Oct 2013 12:18:37 -0700 X-Google-Sender-Auth: 2r7mjsWStBmdkIviUXOYbPUlLtk Message-ID: Subject: Re: svn commit: r257133 - head/sys/dev/iwn From: Adrian Chadd To: Stefan Farfeleder Content-Type: text/plain; charset=ISO-8859-1 Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "freebsd-wireless@freebsd.org" , "src-committers@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 19:18:39 -0000 Sweet, thankyou! -a On 30 October 2013 12:17, Stefan Farfeleder wrote: > On Tue, Oct 29, 2013 at 10:17:18AM +0100, Stefan Farfeleder wrote: >> On Mon, Oct 28, 2013 at 09:27:30PM -0700, Adrian Chadd wrote: >> > I've filed a PR. >> > >> > Please update to -HEAD and test. >> >> Ok thanks, will do. Probably I won't be able before tomorrow though. > > Seems to work as before, thanks! > > Stefan From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 31 02:10:01 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8CD9F23B for ; Thu, 31 Oct 2013 02:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B2682504 for ; Thu, 31 Oct 2013 02:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9V2A1ae083641 for ; Thu, 31 Oct 2013 02:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9V2A1aX083640; Thu, 31 Oct 2013 02:10:01 GMT (envelope-from gnats) Date: Thu, 31 Oct 2013 02:10:01 GMT Message-Id: <201310310210.r9V2A1aX083640@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: dfilter@FreeBSD.ORG (dfilter service) Subject: Re: kern/183428: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dfilter service 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, 31 Oct 2013 02:10:01 -0000 The following reply was made to PR kern/183428; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/183428: commit references a PR Date: Thu, 31 Oct 2013 02:05:01 +0000 (UTC) Author: adrian Date: Thu Oct 31 02:04:53 2013 New Revision: 257412 URL: http://svnweb.freebsd.org/changeset/base/257412 Log: Don't treat the node as an 11n node if 11n rates are disabled. For now, the AMRR code only knows about _either_ MCS or non-MCS rates. It doesn't know how to downgrade (ie, doing 11b CCK rates if MCS0 isn't reliable.) PR: kern/183428 Modified: head/sys/net80211/ieee80211_amrr.c Modified: head/sys/net80211/ieee80211_amrr.c ============================================================================== --- head/sys/net80211/ieee80211_amrr.c Thu Oct 31 02:03:30 2013 (r257411) +++ head/sys/net80211/ieee80211_amrr.c Thu Oct 31 02:04:53 2013 (r257412) @@ -131,6 +131,12 @@ amrr_deinit(struct ieee80211vap *vap) free(vap->iv_rs, M_80211_RATECTL); } +/* + * Return whether 11n rates are possible. + * + * Some 11n devices may return HT information but no HT rates. + * Thus, we shouldn't treat them as an 11n node. + */ static int amrr_node_is_11n(struct ieee80211_node *ni) { @@ -139,6 +145,8 @@ amrr_node_is_11n(struct ieee80211_node * return (0); if (ni->ni_chan == IEEE80211_CHAN_ANYC) return (0); + if (IEEE80211_IS_CHAN_HT(ni->ni_chan) && ni->ni_htrates.rs_nrates == 0) + return (0); return (IEEE80211_IS_CHAN_HT(ni->ni_chan)); } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 31 02:30:02 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3ACC4110 for ; Thu, 31 Oct 2013 02:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0EBF62632 for ; Thu, 31 Oct 2013 02:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9V2U1Xs089126 for ; Thu, 31 Oct 2013 02:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9V2U1OV089125; Thu, 31 Oct 2013 02:30:01 GMT (envelope-from gnats) Date: Thu, 31 Oct 2013 02:30:01 GMT Message-Id: <201310310230.r9V2U1OV089125@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: dfilter@FreeBSD.ORG (dfilter service) Subject: Re: kern/183428: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dfilter service 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, 31 Oct 2013 02:30:02 -0000 The following reply was made to PR kern/183428; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/183428: commit references a PR Date: Thu, 31 Oct 2013 02:21:56 +0000 (UTC) Author: adrian Date: Thu Oct 31 02:21:48 2013 New Revision: 257415 URL: http://svnweb.freebsd.org/changeset/base/257415 Log: Don't base the rate table selection based on the channel mode; it needs to check whether there are rate entries in there or not. PR: kern/183428 Modified: head/sys/dev/iwn/if_iwn.c Modified: head/sys/dev/iwn/if_iwn.c ============================================================================== --- head/sys/dev/iwn/if_iwn.c Thu Oct 31 02:14:28 2013 (r257414) +++ head/sys/dev/iwn/if_iwn.c Thu Oct 31 02:21:48 2013 (r257415) @@ -4312,6 +4312,7 @@ iwn_set_link_quality(struct iwn_softc *s struct iwn_cmd_link_quality linkq; uint8_t txant; int i, rate, txrate; + int is_11n; DPRINTF(sc, IWN_DEBUG_TRACE, "->%s begin\n", __func__); @@ -4326,15 +4327,25 @@ iwn_set_link_quality(struct iwn_softc *s linkq.ampdu_threshold = 3; linkq.ampdu_limit = htole16(4000); /* 4ms */ + /* + * Are we using 11n rates? Ensure the channel is + * 11n _and_ we have some 11n rates, or don't + * try. + */ + if (IEEE80211_IS_CHAN_HT(ni->ni_chan) && ni->ni_htrates.rs_nrates > 0) + is_11n = 1; + else + is_11n = 0; + /* Start at highest available bit-rate. */ - if (IEEE80211_IS_CHAN_HT(ni->ni_chan)) + if (is_11n) txrate = ni->ni_htrates.rs_nrates - 1; else txrate = rs->rs_nrates - 1; for (i = 0; i < IWN_MAX_TX_RETRIES; i++) { uint32_t plcp; - if (IEEE80211_IS_CHAN_HT(ni->ni_chan)) + if (is_11n) rate = IEEE80211_RATE_MCS | txrate; else rate = RV(rs->rs_rates[txrate]); _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 04:09:03 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 62FB095E for ; Fri, 1 Nov 2013 04:09:03 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E3C95298A for ; Fri, 1 Nov 2013 04:09:02 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id ey11so587375wid.6 for ; Thu, 31 Oct 2013 21:09:01 -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=Ay/LGrxTJnbpDHTgUcWq59+M0oR/b0CVn2usu7uGdk4=; b=ll3KjcXEeRclZuRIpjRIFZ3hRPaY5AsM+yCw+kJxTXcjQZ8TowbTv8tGmea8sn+9kZ UWX8sGuX25q/uCiE1oUmq0jizo7Ts4+V1BDFRj360QlvKnBz+WXVmkVg5lso8QKPhznN CMmp6UCSp4dYGLxQgwQFgYiY+BwAAzKujABMITkkqIKz+++LET588WKyAnVjXhS3erp4 1tfWpKhkGNY2sDBoSvL2B86pCbgdnaAVslP0l5LMVO4who3DtvNzwHYr94fDL6nbkFUQ NvY+6+GA3JT5sAe4Y4ECvxQZ7zByne4ApO7mW64gd9O78vQS3oZlsq9XI5Ra9S4xcuY5 XUcg== MIME-Version: 1.0 X-Received: by 10.194.187.232 with SMTP id fv8mr43634wjc.56.1383278941412; Thu, 31 Oct 2013 21:09:01 -0700 (PDT) Received: by 10.194.151.98 with HTTP; Thu, 31 Oct 2013 21:09:01 -0700 (PDT) Date: Fri, 1 Nov 2013 12:09:01 +0800 Message-ID: Subject: Atheros 9285 "unable to reset channel" From: Ben Woods To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 04:09:03 -0000 Hi, I am trialling FreeBSD10-BETA2 in an attempt to find bugs etc. I am having a problem with my Atheros 9285 wireless driver which I think might have been around for a while (not new in 10), but I know a lot of work has been done on these drivers in 10. The symptom is I lose my wifi connection after the computer has been running for some time and I get the following errors scrolling on my terminal: *ath0: ath_chan_set: unable to reset channel X (24XX MHz, flags 0xXXX), hal status 14* It looks similar to these 2 bug reports: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165543 http://www.freebsd.org/cgi/query-pr.cgi?pr=151198 Has anyone seen this before or have any ideas/suggestions of how I can troubleshoot further? I am using wpa_supplicant and DHCP. If I reboot my wifi works again for a few hours and then stops. # pciconf -lv ath0@pci0:1:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9285 Wireless Network Adapter (PCI-Express)' class = network # uname -a FreeBSD sparticus.home.local 10.0-BETA2 FreeBSD 10.0-BETA2 #0 r257166: Sat Oct 26 19:23:22 UTC 2013 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # cat /etc/rc.conf wpa_supplicant_flags="-sd" wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP" # cat /etc/wpa_supplicant.conf network={ ssid="SSID" psk="PSK" } # cat /var/log/dmesg.today ath0: ath_chan_set: unable to reset channel 8 (2447 MHz, flags 0x480), hal status 14 ath0: ath_chan_set: unable to reset channel 9 (2452 MHz, flags 0x480), hal status 14 ath0: ath_chan_set: unable to reset channel 10 (2457 MHz, flags 0x480), hal status 14 ath0: ath_chan_set: unable to reset channel 12 (2467 MHz, flags 0x680), hal status 14 ath0: ath_chan_set: unable to reset channel 14 (2484 MHz, flags 0x2a0), hal status 14 ath0: ath_reset: unable to reset hardware; hal status 14 pid 53465 (python), uid 972: exited on signal 6 (core dumped) # cat /var/log/debug.log wpa_supplicant[490]: wlan0: Event SCAN_RESULTS (3) received wpa_supplicant[490]: Received 0 bytes of scan results (0 BSSes) wpa_supplicant[490]: wlan0: BSS: Start scan result update 5935 wpa_supplicant[490]: BSS: last_scan_res_used=0/32 last_scan_full=0 wpa_supplicant[490]: wlan0: New scan results available wpa_supplicant[490]: WPS: AP[0] 30:85:a9:e7:e4:10 type=0 tries=0 last_attempt=-1 sec ago blacklist=2 wpa_supplicant[490]: WPS: AP[1] 00:26:44:9a:d5:21 type=0 tries=0 last_attempt=-1 sec ago blacklist=0 wpa_supplicant[490]: WPS: AP[2] a4:b1:e9:9b:de:9e type=0 tries=0 last_attempt=-1 sec ago blacklist=0 wpa_supplicant[490]: wlan0: No suitable network found wpa_supplicant[490]: wlan0: Setting scan request: 5 sec 0 usec wpa_supplicant[490]: wlan0: Starting AP scan for wildcard SSID wpa_supplicant[490]: wpa_driver_bsd_set_wpa: enabled=1 wpa_supplicant[490]: wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 Thanks in advance! -Ben From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 04:35:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 60CDDCAD for ; Fri, 1 Nov 2013 04:35:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 24E182B19 for ; Fri, 1 Nov 2013 04:35:08 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id ii20so384335qab.18 for ; Thu, 31 Oct 2013 21:35:06 -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:message-id:subject :from:to:cc:content-type; bh=JHUPUamKtN+aedbai1OUqX9zz5mOWkoPYN9Iqd0nhys=; b=Pxk7rN0OVvF5LUrhunnXsEOOwWW6AW4eZrp/f8iVzZyFwkZf29JclgFiWHtF1E53vG gJ8V5KrbNzRqynvOrEKR7Rt955PqhmEFZ9XtwY0GvsKK8u0ewuXzYYQpze889Z4oAq64 yG7uXXxLijzYtd5hs6GIkFSRe1ABw4Ap8++2d0ail1FEFaY+G/aBQQc27wI7HNNkrHmR c2N2hrcmUPm78WaauEcDnOI1etL7LrosfQnxQKGSleojYWWbVknO1wubedILFzKPCzA1 cyv7x3j4GQ2miizgzbO+hPQeb7LiriWtv6KM1kzmE7cw4zL2+y3p6195Yml9a3LWGFSp KPYg== MIME-Version: 1.0 X-Received: by 10.49.59.115 with SMTP id y19mr1410659qeq.8.1383280506414; Thu, 31 Oct 2013 21:35:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 31 Oct 2013 21:35:06 -0700 (PDT) In-Reply-To: References: Date: Thu, 31 Oct 2013 21:35:06 -0700 X-Google-Sender-Auth: y2KjWiSbH8xe8rQNshhF6R_SOzg Message-ID: Subject: Re: Atheros 9285 "unable to reset channel" From: Adrian Chadd To: Ben Woods Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 04:35:08 -0000 Hi! HAL status 14 is HAL_ESELFTEST, which generally indicates the initial calibration failed. Now, it could fail in a few places. Have a look at ath_hal/ar5416/ar5416_cal.c : ar5416InitCal(). There's an initial calibration done for each chipset, a power-amplifier calibration for the TX side, then noise floor calibration; then various other calibration bits and pieces get started. So, the question is which calibration is failing. The calibration failures are logged at HAL_DEBUG_ANY, so as long as any debug bit is set, it gets echoed. Pick something like HAL_DEBUG_BT_COEX (sysctl dev.ath.0.debug=0x20000000) and see if the HAL dumps any useful information anything. But first - add these to your kernel config and reboot: options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI Also, compile up the stuff in /usr/src/tools/tools/ath . athstats is really, really great at general debugging. -adrian On 31 October 2013 21:09, Ben Woods wrote: > Hi, > > I am trialling FreeBSD10-BETA2 in an attempt to find bugs etc. I am having > a problem with my Atheros 9285 wireless driver which I think might have > been around for a while (not new in 10), but I know a lot of work has been > done on these drivers in 10. > > The symptom is I lose my wifi connection after the computer has been > running for some time and I get the following errors scrolling on my > terminal: > *ath0: ath_chan_set: unable to reset channel X (24XX MHz, flags 0xXXX), hal > status 14* > > It looks similar to these 2 bug reports: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165543 > http://www.freebsd.org/cgi/query-pr.cgi?pr=151198 > > Has anyone seen this before or have any ideas/suggestions of how I can > troubleshoot further? I am using wpa_supplicant and DHCP. If I reboot my > wifi works again for a few hours and then stops. > > # pciconf -lv > ath0@pci0:1:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 > hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR9285 Wireless Network Adapter (PCI-Express)' > class = network > > # uname -a > FreeBSD sparticus.home.local 10.0-BETA2 FreeBSD 10.0-BETA2 #0 r257166: Sat > Oct 26 19:23:22 UTC 2013 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > # cat /etc/rc.conf > wpa_supplicant_flags="-sd" > wlans_ath0="wlan0" > ifconfig_wlan0="WPA DHCP" > > # cat /etc/wpa_supplicant.conf > network={ > ssid="SSID" > psk="PSK" > } > > # cat /var/log/dmesg.today > ath0: ath_chan_set: unable to reset channel 8 (2447 MHz, flags 0x480), hal > status 14 > ath0: ath_chan_set: unable to reset channel 9 (2452 MHz, flags 0x480), hal > status 14 > ath0: ath_chan_set: unable to reset channel 10 (2457 MHz, flags 0x480), hal > status 14 > ath0: ath_chan_set: unable to reset channel 12 (2467 MHz, flags 0x680), hal > status 14 > ath0: ath_chan_set: unable to reset channel 14 (2484 MHz, flags 0x2a0), hal > status 14 > ath0: ath_reset: unable to reset hardware; hal status 14 > pid 53465 (python), uid 972: exited on signal 6 (core dumped) > > # cat /var/log/debug.log > wpa_supplicant[490]: wlan0: Event SCAN_RESULTS (3) received > wpa_supplicant[490]: Received 0 bytes of scan results (0 BSSes) > wpa_supplicant[490]: wlan0: BSS: Start scan result update 5935 > wpa_supplicant[490]: BSS: last_scan_res_used=0/32 last_scan_full=0 > wpa_supplicant[490]: wlan0: New scan results available > wpa_supplicant[490]: WPS: AP[0] 30:85:a9:e7:e4:10 type=0 tries=0 > last_attempt=-1 sec ago blacklist=2 > wpa_supplicant[490]: WPS: AP[1] 00:26:44:9a:d5:21 type=0 tries=0 > last_attempt=-1 sec ago blacklist=0 > wpa_supplicant[490]: WPS: AP[2] a4:b1:e9:9b:de:9e type=0 tries=0 > last_attempt=-1 sec ago blacklist=0 > wpa_supplicant[490]: wlan0: No suitable network found > wpa_supplicant[490]: wlan0: Setting scan request: 5 sec 0 usec > wpa_supplicant[490]: wlan0: Starting AP scan for wildcard SSID > wpa_supplicant[490]: wpa_driver_bsd_set_wpa: enabled=1 > wpa_supplicant[490]: wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 > > > Thanks in advance! > -Ben > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 19:00:03 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E492FC91 for ; Fri, 1 Nov 2013 19:00:03 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.103]) by mx1.freebsd.org (Postfix) with ESMTP id C6CFB2143 for ; Fri, 1 Nov 2013 19:00:03 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version; b=couh7BA06KLxQrDIjIeZkBWoMueNZtx1YzBsB/0hBdGIojZ3uacey+1OhToA7586WdsFnt982JeK Hp0aB6ETZgVNI7tixiYXGblc/VXR0CjJvcX962K6wfUCao6zdHkq Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1383331211054770.480595994726; Fri, 1 Nov 2013 11:40:11 -0700 (PDT) Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-nutuopRJ+OnH5uQKKcpE" Date: Fri, 01 Nov 2013 20:40:03 +0200 Message-ID: <1383331203.12614.1.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_25103_322 X-ZohoMail-Owner: <1383331203.12614.1.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 19:00:04 -0000 --=-nutuopRJ+OnH5uQKKcpE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2013-10-23 at 21:43 -0700, Adrian Chadd wrote: > IT's not. It's devd doing something dumb. >=20 >=20 > -a >=20 >=20 > On 23 October 2013 21:30, clutton wrote: >=20 > > Indeed. > > > > I have looked at a sys/net80211 and at a sys/dev/ath. > > But I still have no idea which one triggers rc script and how on the > > earth it can be done. > > > > On Wed, 2013-10-23 at 16:57 -0700, Adrian Chadd wrote: > > > . that needs to be fixed. It definitely shouldn't be started twice! > > > > > > > > > > > > -adrian > > > > > > > > > > > > On 23 October 2013 16:56, clutton wrote: > > > > > > > What is the best way to restart a wireless stack? > > > > > > > > A command "ifconfig wlan0 create wlandev ath0" starts the > > wpa_supplicant > > > > by itself. It means that the netif script runs the wpa_supplicant > > twice, > > > > always. Is it ok? > > > > > > > > There is my debug during booting: > > > > > > > > [netif.network_common()] START: > > > > [netif.network_common()] ITERATION: > > > > [wpa_supplicant] SUPPID=3D30067 > > > > [wpa_supplicant] SUPPID=3D30067 > > > > [netif.network_common()] STOP: > > > > > > > > It means that during running a network_common() from the > > /etc/rc.d/netif > > > > the /etc/rc.d/wpa_supplicant was called twice. > > > > > > > > /etc/rc.conf > > > > wlans_ath0=3D"wlan0" > > > > ifconfig_wlan0=3D"WPA DHCP" > > > > ifconfig_em0=3D"DHCP" > > > > ipsec_enable=3D"YES" > > > > > > > > /etc/wpa_supplicant.conf > > > > network=3D{ > > > > ssid=3D"ssid" > > > > psk=3D"psk" > > > > } > > > > > > > > 11.0-CURRENT > > > > > > > _______________________________________________ > > > freebsd-wireless@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > > To unsubscribe, send any mail to " > > freebsd-wireless-unsubscribe@freebsd.org" > > > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" Yes, it's not a bug, just misconfigured devd. Here the patch: =CE=9E ~ =E2=86=92 diff -u /usr/src/etc/devd.conf /etc/devd.conf =20 --- /usr/src/etc/devd.conf 2013-09-29 17:24:16.759250174 +0300 +++ /etc/devd.conf 2013-11-01 10:52:02.731746832 +0200 @@ -38,7 +38,7 @@ # notify 0 { match "system" "IFNET"; - match "subsystem" "!usbus[0-9]+"; + match "subsystem" "!(usbus|wlan)[0-9]+"; match "type" "ATTACH"; action "/etc/pccard_ether $subsystem start"; }; zsh: exit 1 diff -u /usr/src/etc/devd.conf /etc/devd.conf =E2=86=911 ~ =E2=86=92=20 Is it good enough? Should I make an pr? I believe that the wlan iface may be avoided and all cases, am I wrong? --=-nutuopRJ+OnH5uQKKcpE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJSc/WDAAoJECNkWbjnbjuipeoP/RnoiUb+uhIpCw1Qht42MhFS MgYJyIkFMzncEithc2AOpARC1JDnJQ6JOztgTGeDcZC0nkPPc45zjwtZGk5cQpk1 sq1d70SyOhSFN1b/MPeXLM04/D0fiPHmpIasddTkpS2XsGAc0jVUrFXsB7Ewgc8f EYDz6f5oABNmautLOAoavdzAj47wgZY0gSGgS1JSnRUekqftTKUCvfIqEgPGhqCG YUW8SfLm1kG+nh7db5VaqbJI+NewtO5M8UdBwuDVXV8D97hrA23JyC+qIU9H/M+1 7eQP5nldKyYH4J4UXdBg+/Rhb1zeaiBSSo3J90I0s526LKSRjI87m4pm8wWfN9aD bOHsujcphJDPQvMCB5yOVEYk3KEJz3EVsvVfW5P85iodCKGg08KxFG6Y1fx+Pnnd AEj/NNVP8OPRXtNX2VAaDw2jRQ/JRsvnO8HUbx2XxOpXnR6WvJD5zVzRZgSd+jRI GxEGaesjoSh5rRheUqpep9alRDKa1TNhf/8xkETAIXz1zdy13u5YQzdA76tWKMJE ojkRzuS6UUu/GmSZspStax9mdYhCmJZt3+rL4Qafi8CybJXa3wPC233ucY0zfL3o P/AFQ0zSmyZMloGZsTHG6xtW134CAeIBAM6CZ356DQmkzsLCnNIznr3PSvDXr7C5 +hGijWCBZQr8tJcMQCtJ =hAmq -----END PGP SIGNATURE----- --=-nutuopRJ+OnH5uQKKcpE-- From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 19:16:46 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3A432EEC for ; Fri, 1 Nov 2013 19:16:46 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C6F432224 for ; Fri, 1 Nov 2013 19:16:45 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id q58so4420278wes.0 for ; Fri, 01 Nov 2013 12:16:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=n56IYnfHRBAPbhtn+C+6nh3wHZyDlFpqbPgDpCWo9j0=; b=ivU0I0Fq418PMWRiSoKwccrEIQVm0/3XqOjz7V9i01iohZH/KZD7kvQvC1bCJd/Nck 4cd+zY+QKDarY6kyLdqcaPAyVPBL7nHcgrB5PznmhBxZapn81pwj5ikBs+NNWmiJMJyC LrX4RvNy9zFltZQG9N5ga5i1J48uvoxE/r4kEllzRdiOABltDNGfNLprctsN/f2Ia+KT xYRETAvu+XOCO3kwbnkkxCN9SAT8Uua705OO4GJU2B0GNG/YM/02ZyoY84UGIP9TWpk2 Pb4RKpx9OUcLfBuZTip3VgOzW5Ee4Kij60EevyMeLAZIhO1q5DZJI6hezJuejQ9kPWwE foAw== X-Gm-Message-State: ALoCoQl1g4GIpQkbhDskuPx2cwNimWY+VIn2DZC0YRaBqq2FDoUuP38Tr45IpQ1slUHwRg+I6QQx MIME-Version: 1.0 X-Received: by 10.180.12.14 with SMTP id u14mr3364913wib.63.1383333397831; Fri, 01 Nov 2013 12:16:37 -0700 (PDT) Received: by 10.227.226.196 with HTTP; Fri, 1 Nov 2013 12:16:37 -0700 (PDT) X-Originating-IP: [88.65.59.108] In-Reply-To: <1383331203.12614.1.camel@eva02.mbsd> References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> Date: Fri, 1 Nov 2013 20:16:37 +0100 Message-ID: Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: Bernhard Schmidt To: clutton Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 19:16:46 -0000 On Fri, Nov 1, 2013 at 7:40 PM, clutton wrote: > On Wed, 2013-10-23 at 21:43 -0700, Adrian Chadd wrote: >> IT's not. It's devd doing something dumb. >> >> >> -a >> >> >> On 23 October 2013 21:30, clutton wrote: >> >> > Indeed. >> > >> > I have looked at a sys/net80211 and at a sys/dev/ath. >> > But I still have no idea which one triggers rc script and how on the >> > earth it can be done. >> > >> > On Wed, 2013-10-23 at 16:57 -0700, Adrian Chadd wrote: >> > > . that needs to be fixed. It definitely shouldn't be started twice! >> > > >> > > >> > > >> > > -adrian >> > > >> > > >> > > >> > > On 23 October 2013 16:56, clutton wrote: >> > > >> > > > What is the best way to restart a wireless stack? >> > > > >> > > > A command "ifconfig wlan0 create wlandev ath0" starts the >> > wpa_supplicant >> > > > by itself. It means that the netif script runs the wpa_supplicant >> > twice, >> > > > always. Is it ok? >> > > > >> > > > There is my debug during booting: >> > > > >> > > > [netif.network_common()] START: >> > > > [netif.network_common()] ITERATION: >> > > > [wpa_supplicant] SUPPID=3D30067 >> > > > [wpa_supplicant] SUPPID=3D30067 >> > > > [netif.network_common()] STOP: >> > > > >> > > > It means that during running a network_common() from the >> > /etc/rc.d/netif >> > > > the /etc/rc.d/wpa_supplicant was called twice. >> > > > >> > > > /etc/rc.conf >> > > > wlans_ath0=3D"wlan0" >> > > > ifconfig_wlan0=3D"WPA DHCP" >> > > > ifconfig_em0=3D"DHCP" >> > > > ipsec_enable=3D"YES" >> > > > >> > > > /etc/wpa_supplicant.conf >> > > > network=3D{ >> > > > ssid=3D"ssid" >> > > > psk=3D"psk" >> > > > } >> > > > >> > > > 11.0-CURRENT >> > > > >> > > _______________________________________________ >> > > freebsd-wireless@freebsd.org mailing list >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> > > To unsubscribe, send any mail to " >> > freebsd-wireless-unsubscribe@freebsd.org" >> > >> > >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.o= rg" > > Yes, it's not a bug, just misconfigured devd. > Here the patch: > > =CE=9E ~ =E2=86=92 diff -u /usr/src/etc/devd.conf /etc/devd.conf > --- /usr/src/etc/devd.conf 2013-09-29 17:24:16.759250174 +0300 > +++ /etc/devd.conf 2013-11-01 10:52:02.731746832 +0200 > @@ -38,7 +38,7 @@ > # > notify 0 { > match "system" "IFNET"; > - match "subsystem" "!usbus[0-9]+"; > + match "subsystem" "!(usbus|wlan)[0-9]+"; > match "type" "ATTACH"; > action "/etc/pccard_ether $subsystem start"; > }; > zsh: exit 1 diff -u /usr/src/etc/devd.conf /etc/devd.conf > =E2=86=911 ~ =E2=86=92 > > Is it good enough? Should I make an pr? > I believe that the wlan iface may be avoided and all cases, am I wrong? That actually is a design question I once wrapped my head around unsuccessfully. The lines above are responsible for configuring wlan0 if it is created, eg. ifconfig wlan0 destroy ifconfig wlan0 create wlandev ath0 will invoke above code which will then invoke pccard_ether. Changing the code as you intent to will prevent this. Someone should step up an decide what is supposed to happen, should wlan0 in that case be configured as stated in rc.conf, or not? The actual issue though, is in wpa_supplicant itself. It has code to prevent it being started twice, but that doesn't kick in because the instances are started to fast and we loose (have not yet setup enough) information in our net code. --=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 19:33:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5857F7C8 for ; Fri, 1 Nov 2013 19:33:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 181952362 for ; Fri, 1 Nov 2013 19:33:33 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id n9so2707278qcw.15 for ; Fri, 01 Nov 2013 12:33:32 -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:message-id:subject :from:to:cc:content-type; bh=j3R4DwYVT8FjRJfrb3OzmMXIEZWjcfxpvz08MAhSEZs=; b=hhQdkPG7ZuAsxxZjOTAzuLBSX6WM/7pd/QRhhkDBSjUHcxlqAnbk62UzCp8wV3yP/j Gxx/mMpv4uGqFu4QBmkNPD23iHRnQlOtbixQje/XsgyXyFL6Kh6eLaci7gqb9dg+aWnr dnNS1UYWxEfjw2Va6o/4mBGuXb2Z/tdLaqHUlrsZqf6mXiTgvYgok6agth5ueYjalQnm uCDKbnNl5y5PNRTXQFfAn8ht7h2d7hVJVky5zUYZNhixenIUeYFK9rZH/DC/KNISEdts Qjm2RQQkTwf5ZMHLQlaiv8ooDOdubH5oxLndKitvDI76Bg6pNdI/VcSdgj8UWXFR3ZWk tVzQ== MIME-Version: 1.0 X-Received: by 10.49.127.179 with SMTP id nh19mr6105220qeb.1.1383334412323; Fri, 01 Nov 2013 12:33:32 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 1 Nov 2013 12:33:32 -0700 (PDT) In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> Date: Fri, 1 Nov 2013 12:33:32 -0700 X-Google-Sender-Auth: GkoWZ-8P-u6N1yJq06gAPVp-Oys Message-ID: Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: Adrian Chadd To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: clutton , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 19:33:33 -0000 On 1 November 2013 12:16, Bernhard Schmidt wrote: > That actually is a design question I once wrapped my head around > unsuccessfully. The lines above are responsible for configuring wlan0 > if it is created, eg. > ifconfig wlan0 destroy > ifconfig wlan0 create wlandev ath0 > will invoke above code which will then invoke pccard_ether. Changing > the code as you intent to will prevent this. > > Someone should step up an decide what is supposed to happen, should > wlan0 in that case be configured as stated in rc.conf, or not? > > The actual issue though, is in wpa_supplicant itself. It has code to > prevent it being started twice, but that doesn't kick in because the > instances are started to fast and we loose (have not yet setup enough) > information in our net code. Uhm, I'm confused by this. Would you mind explaining it in a bit more detail? -a From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 20:00:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 85C4213B for ; Fri, 1 Nov 2013 20:00:13 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 671A524BE for ; Fri, 1 Nov 2013 20:00:13 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version; b=kYOUiWaFjw0ddF527r6i+g98Nbvv8f8Bhmw7CPkrGyDoUYtkt8rj0dNziMOuSUabNe2mCDgTonQ4 LnaIQZqyR1zS0YK5huUAWrFHKdlC7+lXfxSKGRBl5iKzLymtJNNe Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1383336011049591.6342966721718; Fri, 1 Nov 2013 13:00:11 -0700 (PDT) Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-X1xQAmpEcOdnYv12MzDa" Date: Fri, 01 Nov 2013 22:00:04 +0200 Message-ID: <1383336004.13657.18.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_25103_58 X-ZohoMail-Owner: <1383336004.13657.18.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-ZohoMailClient: External X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 20:00:13 -0000 --=-X1xQAmpEcOdnYv12MzDa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2013-11-01 at 12:33 -0700, Adrian Chadd wrote: > On 1 November 2013 12:16, Bernhard Schmidt wrote= : >=20 > > That actually is a design question I once wrapped my head around > > unsuccessfully. The lines above are responsible for configuring wlan0 > > if it is created, eg. > > ifconfig wlan0 destroy > > ifconfig wlan0 create wlandev ath0 > > will invoke above code which will then invoke pccard_ether. Changing > > the code as you intent to will prevent this. > > > > Someone should step up an decide what is supposed to happen, should > > wlan0 in that case be configured as stated in rc.conf, or not? > > > > The actual issue though, is in wpa_supplicant itself. It has code to > > prevent it being started twice, but that doesn't kick in because the > > instances are started to fast and we loose (have not yet setup enough) > > information in our net code. >=20 > Uhm, I'm confused by this. Would you mind explaining it in a bit more det= ail? >=20 >=20 > -a The devd runs a pccard_ether script when the IFNET interface appears. In some rare cases you can see two copies of the wpa_sopplicant. --=-X1xQAmpEcOdnYv12MzDa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJSdAhEAAoJECNkWbjnbjuifxQP/A9v06ssmQIGYwM72aBRZb+5 s8zYErVMZXN1MkA669Et3N9BVVytez28AbewShMfuqBL+zL3WFoNhPRmqkKTjew4 plAutlGLVyqP5syJx5+af/eWax8m9bIvHU/FyNgP+7d1DbnXmuh0/RI6ECcCBx5k +dEa85liRhp5SM8K4YOEe6FFwCfCQQd2FVOGMM+LAF5G9nNQ/0CKFs0EFjwiv4OP dHCnix4S2qNSP5zYsv5LHaSOkX3RcvcqlnYiN1HXZdXGUtPkuQiBFmS19FbOBREh 6uCMYrdFx+02CC0m2bzhAQ1n3gfn4y2rw8FPhWG4e2SP71GGBzm4AmLw+nFVa/nj 2K3U06u83A05NZjo6UAhgpHsuSK3OgF805H7yovc/zRwFfSpP5aDHJdfAjx5Ji4B 7M0xdPW2zsOEcbHiA4P2xYYiEfuEKMxQrxwwtbgZ+QGfyjw8eRdvxjxYEcd1upsG kFpg9FKY66Ld9zvWcYfvJ0OkPxUBRBlJCiNWESjCUXVdPFV+qRCTRfpAxPjOJCuK evntX3X/f9hKpxtzLBaFbstUsDnQTnLRZ4kywlTAVRH4btmOWHrXCsYDKS+6RQLi OmszcRdcTiqoDaoT9NECtCc8Rx8Q2lkhM6+5Ps/9Et4zOO9oJ6fDBIBP8ziWvTlr fzFD6nwm4uWZfWZRxtBi =4T0U -----END PGP SIGNATURE----- --=-X1xQAmpEcOdnYv12MzDa-- From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 20:02:34 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BF0F2170 for ; Fri, 1 Nov 2013 20:02:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7D04024F7 for ; Fri, 1 Nov 2013 20:02:34 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id k18so2686883qcv.24 for ; Fri, 01 Nov 2013 13:02:33 -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=s03P+6c9CQR9BXP7e+0h2nufTc8JAfak9Xgt5FNzJz0=; b=L80kYWUEUWIVELCb0XMKLLdZcqelRk84cqgupnegrR9YFkosJd+P5w48APDKo1pVDM bSc+xsL2V5lyrHf65Gsh5V4oIbIWPAe3A1URlXN+8wPbp7vPqkEaICxlYQTPe3JvQ+hw /hiNfdlJMmiQcpN/Xo8ypa1EKIf0x/Qy33zT60CJQKOKmHDE+Qx7wm2sKCwfb/aQ0eVL ER6nZ0LOrvRODtY+gTszZyYHVd6aplS+RHnF50MTxwGXX5VrMrcj1eoyVmmZUQKIPOFX AWi7g5q82o8mAJV+9KC3CRWXGFItGPuBk7MgeebNaIq+DA2II5gkDefZs77f+PzktdMJ 7zRg== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr6350870qai.74.1383336153685; Fri, 01 Nov 2013 13:02:33 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Fri, 1 Nov 2013 13:02:33 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Fri, 1 Nov 2013 13:02:33 -0700 (PDT) In-Reply-To: <1383336004.13657.18.camel@eva02.mbsd> References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> Date: Fri, 1 Nov 2013 13:02:33 -0700 Message-ID: Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: Adrian Chadd To: clutton Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 20:02:34 -0000 What's running the other copy? Adrian On Nov 1, 2013 4:00 PM, "clutton" wrote: > On Fri, 2013-11-01 at 12:33 -0700, Adrian Chadd wrote: > > On 1 November 2013 12:16, Bernhard Schmidt > wrote: > > > > > That actually is a design question I once wrapped my head around > > > unsuccessfully. The lines above are responsible for configuring wlan0 > > > if it is created, eg. > > > ifconfig wlan0 destroy > > > ifconfig wlan0 create wlandev ath0 > > > will invoke above code which will then invoke pccard_ether. Changing > > > the code as you intent to will prevent this. > > > > > > Someone should step up an decide what is supposed to happen, should > > > wlan0 in that case be configured as stated in rc.conf, or not? > > > > > > The actual issue though, is in wpa_supplicant itself. It has code to > > > prevent it being started twice, but that doesn't kick in because the > > > instances are started to fast and we loose (have not yet setup enough) > > > information in our net code. > > > > Uhm, I'm confused by this. Would you mind explaining it in a bit more > detail? > > > > > > -a > > The devd runs a pccard_ether script when the IFNET interface appears. > In some rare cases you can see two copies of the wpa_sopplicant. > From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 20:15:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E40F45E1 for ; Fri, 1 Nov 2013 20:15:57 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id C50BB25B8 for ; Fri, 1 Nov 2013 20:15:57 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version; b=rJ2F7wLh4gKwPX2r8hCp/qt8+4gkpba7VRhhICpcW8fGhHjySTNq8GWV2F8EimumYuXe554qKZ7k +GI7mRGp2+pPCReh+EGuWFKX3fg7NbivldsdC39bJuWh2WCU3qbd Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1383336955742413.66200506551456; Fri, 1 Nov 2013 13:15:55 -0700 (PDT) Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-IXDXDJG/3oyLC+sS0HM3" Date: Fri, 01 Nov 2013 22:15:45 +0200 Message-ID: <1383336945.13657.34.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_25103_83 X-ZohoMail-Owner: <1383336945.13657.34.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-ZohoMailClient: External X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 20:15:58 -0000 --=-IXDXDJG/3oyLC+sS0HM3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2013-11-01 at 20:16 +0100, Bernhard Schmidt wrote: > On Fri, Nov 1, 2013 at 7:40 PM, clutton wrote: > > On Wed, 2013-10-23 at 21:43 -0700, Adrian Chadd wrote: > >> IT's not. It's devd doing something dumb. > >> > >> > >> -a > >> > >> > >> On 23 October 2013 21:30, clutton wrote: > >> > >> > Indeed. > >> > > >> > I have looked at a sys/net80211 and at a sys/dev/ath. > >> > But I still have no idea which one triggers rc script and how on the > >> > earth it can be done. > >> > > >> > On Wed, 2013-10-23 at 16:57 -0700, Adrian Chadd wrote: > >> > > . that needs to be fixed. It definitely shouldn't be started twice= ! > >> > > > >> > > > >> > > > >> > > -adrian > >> > > > >> > > > >> > > > >> > > On 23 October 2013 16:56, clutton wrote: > >> > > > >> > > > What is the best way to restart a wireless stack? > >> > > > > >> > > > A command "ifconfig wlan0 create wlandev ath0" starts the > >> > wpa_supplicant > >> > > > by itself. It means that the netif script runs the wpa_supplican= t > >> > twice, > >> > > > always. Is it ok? > >> > > > > >> > > > There is my debug during booting: > >> > > > > >> > > > [netif.network_common()] START: > >> > > > [netif.network_common()] ITERATION: > >> > > > [wpa_supplicant] SUPPID=3D30067 > >> > > > [wpa_supplicant] SUPPID=3D30067 > >> > > > [netif.network_common()] STOP: > >> > > > > >> > > > It means that during running a network_common() from the > >> > /etc/rc.d/netif > >> > > > the /etc/rc.d/wpa_supplicant was called twice. > >> > > > > >> > > > /etc/rc.conf > >> > > > wlans_ath0=3D"wlan0" > >> > > > ifconfig_wlan0=3D"WPA DHCP" > >> > > > ifconfig_em0=3D"DHCP" > >> > > > ipsec_enable=3D"YES" > >> > > > > >> > > > /etc/wpa_supplicant.conf > >> > > > network=3D{ > >> > > > ssid=3D"ssid" > >> > > > psk=3D"psk" > >> > > > } > >> > > > > >> > > > 11.0-CURRENT > >> > > > > >> > > _______________________________________________ > >> > > freebsd-wireless@freebsd.org mailing list > >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> > > To unsubscribe, send any mail to " > >> > freebsd-wireless-unsubscribe@freebsd.org" > >> > > >> > > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd= .org" > > > > Yes, it's not a bug, just misconfigured devd. > > Here the patch: > > > > =CE=9E ~ =E2=86=92 diff -u /usr/src/etc/devd.conf /etc/devd.conf > > --- /usr/src/etc/devd.conf 2013-09-29 17:24:16.759250174 +0300 > > +++ /etc/devd.conf 2013-11-01 10:52:02.731746832 +0200 > > @@ -38,7 +38,7 @@ > > # > > notify 0 { > > match "system" "IFNET"; > > - match "subsystem" "!usbus[0-9]+"; > > + match "subsystem" "!(usbus|wlan)[0-9]+"; > > match "type" "ATTACH"; > > action "/etc/pccard_ether $subsystem start"; > > }; > > zsh: exit 1 diff -u /usr/src/etc/devd.conf /etc/devd.conf > > =E2=86=911 ~ =E2=86=92 > > > > Is it good enough? Should I make an pr? > > I believe that the wlan iface may be avoided and all cases, am I wrong? >=20 > That actually is a design question I once wrapped my head around > unsuccessfully. The lines above are responsible for configuring wlan0 > if it is created, eg. > ifconfig wlan0 destroy > ifconfig wlan0 create wlandev ath0 > will invoke above code which will then invoke pccard_ether. Changing > the code as you intent to will prevent this. >=20 > Someone should step up an decide what is supposed to happen, should > wlan0 in that case be configured as stated in rc.conf, or not? >=20 > The actual issue though, is in wpa_supplicant itself. It has code to > prevent it being started twice, but that doesn't kick in because the > instances are started to fast and we loose (have not yet setup enough) > information in our net code. >=20 > --=20 > Bernhard At least it shouldn't call the pccard_ether. My wifi card is not the pccard nor the ether card :). Here we have an old design + a new implementation of wlan devices. And yes, it occurs that the FreeBSD has some kind of a NetworkManager. In my view it should be optional, because rc.d scripts is mandatory anyway. --=-IXDXDJG/3oyLC+sS0HM3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJSdAvxAAoJECNkWbjnbjui7bcP/i5w1gPqrNuhOOk7/RL/9jGa 4JscmLcMp4AzrgQEj7B+Nt0WzV2a5L8e0LxupmalKgk9Zn9y6EDQeaYx2hLiKWqg nMTqT03V8G1Rl206XCg9DQeW1Lg7JYnJ1QGOQxSIJyBH1jDOZRayE4n5mbw0ehnT nGDrVD4+kOpO7B3WHHJxV+CqiXEfCpN6q6CI0jGnFI10ntsVgg66weud5rLpq+eY gzLQoDs0bNR6l3Mlf2ksDYTwmcCYXeGarz6YUuZoT3GfXEnL+/IktiXvAZMnFqOy 79MCR3WpE75QP6JBT+0OIeZKHdSeSMik99RtgtvRDR+Fgdo7dXwj2d5V3gtJ2Bh0 mfhX9ures+i7yM8Wu4tAmMGer3tCFHRhlJXBzp9dvnRgu8LwVFuDQLmpzUKSGzMo ep7G5+3o5YzPQHzPsX+sJLunkcxNV0EqWshjHPz96vszLolhHxjyqnSoZOPvUC5q eU/aCs2JhO1FAKLP7Xa/NkgOTqKqoHR6imbJOI+dSblhhIYmYEMXKKtu8XPA2GEs aqVRbPMgWubsqdwKIJgNqj4QagDNRE0AgSYXw1wxYNQPZQR7ZQOwVcUhlJiKdzAc jXNGaTpCmJgWjBuCmQiMjqvmNxByEBdYMK0hzndsu6nd9TVEs87MHmbn9ENrGgyJ gWY5wNVAEF3ahjcXuoqM =Z8SO -----END PGP SIGNATURE----- --=-IXDXDJG/3oyLC+sS0HM3-- From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 1 20:35:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6C9BAF59 for ; Fri, 1 Nov 2013 20:35:25 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 4CFEA26D9 for ; Fri, 1 Nov 2013 20:35:25 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version; b=okgLWDWGdY23Ji4BSDdroac0KgAwrRW5RRGzuzTax3pATOw4rR0ZkxdbJ9XR13IN5BZbOLiNDMdn esw2CZvmQ3++Vdo7h/6/eihIs4OIc80u7SHZGIbun7Tnm/hHP+pV Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1383338123828350.2742818311242; Fri, 1 Nov 2013 13:35:23 -0700 (PDT) Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-NQHgN4Pcp74HmTBjL43n" Date: Fri, 01 Nov 2013 22:35:17 +0200 Message-ID: <1383338117.13657.53.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_25103_57 X-ZohoMail-Owner: <1383338117.13657.53.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-ZohoMailClient: External X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 20:35:25 -0000 --=-NQHgN4Pcp74HmTBjL43n Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2013-11-01 at 13:02 -0700, Adrian Chadd wrote: > What's running the other copy? >=20 >=20 >=20 > Adrian >=20 > On Nov 1, 2013 4:00 PM, "clutton" wrote: > On Fri, 2013-11-01 at 12:33 -0700, Adrian Chadd wrote: > > On 1 November 2013 12:16, Bernhard Schmidt > wrote: > > > > > That actually is a design question I once wrapped my head > around > > > unsuccessfully. The lines above are responsible for > configuring wlan0 > > > if it is created, eg. > > > ifconfig wlan0 destroy > > > ifconfig wlan0 create wlandev ath0 > > > will invoke above code which will then invoke > pccard_ether. Changing > > > the code as you intent to will prevent this. > > > > > > Someone should step up an decide what is supposed to > happen, should > > > wlan0 in that case be configured as stated in rc.conf, or > not? > > > > > > The actual issue though, is in wpa_supplicant itself. It > has code to > > > prevent it being started twice, but that doesn't kick in > because the > > > instances are started to fast and we loose (have not yet > setup enough) > > > information in our net code. > > > > Uhm, I'm confused by this. Would you mind explaining it in a > bit more detail? > > > > > > -a > =20 > The devd runs a pccard_ether script when the IFNET interface > appears. > In some rare cases you can see two copies of the > wpa_sopplicant. devd: notify 0 { match "system" "IFNET"; match "subsystem" "!usbus[0-9]+"; match "type" "ATTACH"; action "/etc/pccard_ether $subsystem start"; }; --=-NQHgN4Pcp74HmTBjL43n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJSdBCFAAoJECNkWbjnbjuiJIwP/RBQ24CvGWA+SjWe8qvrNY7J TUWfmZYYEQwJYHFC5p4sZ77ZEgR+9vc95CxaXKQbCp3mN8Hdh5Uz5PqSzrRAX5Lg 1ZzSa95Zhk5+MPYzb2G9SCCdBFFDQrSlQ3r0+gMJnE7zgLmCIcdzoOiVmAWtnUWI CoC5lZERERBenh4oPM6YcAahzLfElu+Wgsn/VYTolkLhcHuFf7Vx4Ja+b3SvE5SZ /czngCEkFBoUFWgf0/pXHzVk6i26Ir3FmaHGoV5bavTAtJm9aBoXpUpzXAshBlVj qh9kioqFyT9BsK20kTMV55Ut2DmsHpQ2fAnP80XgtSjUTbnxuLspQHG2FhQeedFT aiX++hH3r9KJjbRF/hf+7B7GOVdtO1YGUjceA8pzch1cGpvNn/wtRAXXJtDG8/dS H0oUwdBxzCfEtYeDjlOp9FH3o88NnRkaDe3ZuWYKyeOCF740dg9AHswrc4s4/XEe b4yreqCDc6Czxdt2S4UQYq3tA9poKEO9GzeVrGYJAOxS+UosT2H275rKSODN0UXl imeQ+FS/PgmUJWyRNcewOht/B4lY4wGtDmAHBwhKw1fL2YR1uTCvPju01kHqQFGL +aXxUA4VBiLKS15XqyDp6JEfXG+93CIi5Nvq6+13Us8EzpgWyP61nc5R5UAJrj6q 39x/lMApYQ//UdIV45Mq =oOj/ -----END PGP SIGNATURE----- --=-NQHgN4Pcp74HmTBjL43n-- From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 2 06:50:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D19B3945 for ; Sat, 2 Nov 2013 06:50:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 91F8924AE for ; Sat, 2 Nov 2013 06:50:22 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id k4so1083140qaq.14 for ; Fri, 01 Nov 2013 23:50: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=oDxnoCtp/CKWV5zllnHhdE8stNy9UztXr45ByD9G5xA=; b=vk8xTPNpCihMc6NqnzzDT1JlsiNau4UdGDhWdWD+4wc5Q9uzghrJUMK3JJtsgVpx5Z 8eV74EqgECwpgBBGPCwF5cnSZTOKr4wrnfyfPp2t9S3OeW15RY0BjukFLOSRcls/Ul8/ q6LHqoZK5MKBHMUApGSscQ+cfHc16pI9k42Ik+fVoNWtPYY/f3Y2AE5Dq497aU1uQ3Ws rlkeozFM1pnPQDqSos97qpJTJJk8tZJGtpcahSNgn6S3fVGHDBZiAx3RQ1e2ZZScIXKx j54J7E/5Xhz9rLT5wBxMaakxDWz3nF2BBtPgnTnb5CHj3vxTNntR4bg2zUjg3HghRUeV lc2A== MIME-Version: 1.0 X-Received: by 10.49.24.202 with SMTP id w10mr8846650qef.12.1383375021823; Fri, 01 Nov 2013 23:50:21 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Fri, 1 Nov 2013 23:50:21 -0700 (PDT) In-Reply-To: <1383338117.13657.53.camel@eva02.mbsd> References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> <1383338117.13657.53.camel@eva02.mbsd> Date: Fri, 1 Nov 2013 23:50:21 -0700 Message-ID: Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: Adrian Chadd To: clutton Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 06:50:23 -0000 OK, so where's the other path for invoking wpa_supplicant? -a On 1 November 2013 13:35, clutton wrote: > On Fri, 2013-11-01 at 13:02 -0700, Adrian Chadd wrote: >> What's running the other copy? >> >> >> >> Adrian >> >> On Nov 1, 2013 4:00 PM, "clutton" wrote: >> On Fri, 2013-11-01 at 12:33 -0700, Adrian Chadd wrote: >> > On 1 November 2013 12:16, Bernhard Schmidt >> wrote: >> > >> > > That actually is a design question I once wrapped my head >> around >> > > unsuccessfully. The lines above are responsible for >> configuring wlan0 >> > > if it is created, eg. >> > > ifconfig wlan0 destroy >> > > ifconfig wlan0 create wlandev ath0 >> > > will invoke above code which will then invoke >> pccard_ether. Changing >> > > the code as you intent to will prevent this. >> > > >> > > Someone should step up an decide what is supposed to >> happen, should >> > > wlan0 in that case be configured as stated in rc.conf, or >> not? >> > > >> > > The actual issue though, is in wpa_supplicant itself. It >> has code to >> > > prevent it being started twice, but that doesn't kick in >> because the >> > > instances are started to fast and we loose (have not yet >> setup enough) >> > > information in our net code. >> > >> > Uhm, I'm confused by this. Would you mind explaining it in a >> bit more detail? >> > >> > >> > -a >> >> The devd runs a pccard_ether script when the IFNET interface >> appears. >> In some rare cases you can see two copies of the >> wpa_sopplicant. > > devd: > > notify 0 { > match "system" "IFNET"; > match "subsystem" "!usbus[0-9]+"; > match "type" "ATTACH"; > action "/etc/pccard_ether $subsystem start"; > }; > From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 2 09:00:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 23427CF7 for ; Sat, 2 Nov 2013 09:00:27 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 031D029C0 for ; Sat, 2 Nov 2013 09:00:26 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version; b=KzBygMjaMeF+z5BW2kYq5IDdfBFUapu/5ECDeUS5v3QRtZmVomC7Al3r63QtP61XVfN2CeDrdb28 Ol0RFVADqio5479WMaqyLmlzR6dbxSJqzZ58ca1t/NznX4lnU0dQ Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1383382823874327.74719553782086; Sat, 2 Nov 2013 02:00:23 -0700 (PDT) Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> <1383338117.13657.53.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-qx3f4/weV05ByAUrxLbl" Date: Sat, 02 Nov 2013 11:00:15 +0200 Message-ID: <1383382815.31973.1.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_25103_62 X-ZohoMail-Owner: <1383382815.31973.1.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-ZohoMailClient: External X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 09:00:27 -0000 --=-qx3f4/weV05ByAUrxLbl Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2013-11-01 at 23:50 -0700, Adrian Chadd wrote: > OK, so where's the other path for invoking wpa_supplicant? >=20 >=20 > -a >=20 > On 1 November 2013 13:35, clutton wrote: > > On Fri, 2013-11-01 at 13:02 -0700, Adrian Chadd wrote: > >> What's running the other copy? > >> > >> > >> > >> Adrian > >> > >> On Nov 1, 2013 4:00 PM, "clutton" wrote: > >> On Fri, 2013-11-01 at 12:33 -0700, Adrian Chadd wrote: > >> > On 1 November 2013 12:16, Bernhard Schmidt > >> wrote: > >> > > >> > > That actually is a design question I once wrapped my head > >> around > >> > > unsuccessfully. The lines above are responsible for > >> configuring wlan0 > >> > > if it is created, eg. > >> > > ifconfig wlan0 destroy > >> > > ifconfig wlan0 create wlandev ath0 > >> > > will invoke above code which will then invoke > >> pccard_ether. Changing > >> > > the code as you intent to will prevent this. > >> > > > >> > > Someone should step up an decide what is supposed to > >> happen, should > >> > > wlan0 in that case be configured as stated in rc.conf, or > >> not? > >> > > > >> > > The actual issue though, is in wpa_supplicant itself. It > >> has code to > >> > > prevent it being started twice, but that doesn't kick in > >> because the > >> > > instances are started to fast and we loose (have not yet > >> setup enough) > >> > > information in our net code. > >> > > >> > Uhm, I'm confused by this. Would you mind explaining it in a > >> bit more detail? > >> > > >> > > >> > -a > >> > >> The devd runs a pccard_ether script when the IFNET interface > >> appears. > >> In some rare cases you can see two copies of the > >> wpa_sopplicant. > > > > devd: > > > > notify 0 { > > match "system" "IFNET"; > > match "subsystem" "!usbus[0-9]+"; > > match "type" "ATTACH"; > > action "/etc/pccard_ether $subsystem start"; > > }; > > What do you mean? --=-qx3f4/weV05ByAUrxLbl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJSdL8fAAoJECNkWbjnbjuilEUP/0Z1sLs9vsCvspr/zUm1qAxF xpDJEwZ3k8C2xrm2o8D3CnUVSe3A4/xzK9NBEWgZczZcZYRF4Heo1cil3Gch5R9p xeCGfj7gax2wc45Bn0ZnBr8xm+oygN7zmAXW6lYbJ6qQMKvhFzapfsR6wxviti0S smkqLIA3QeseeN4DVWrk83g2mmitynvGqY6tHvcHlokxt70AZXIfcwV5GlvAdk4D o+WAti6hqXwgqSt3YLfOTAaQEzHC1gTB1wmJwXsOA0AYi7JumnDP93tjn168h0Oz W222OcozdQdUnv7krov6t8pbHjVyTcHZnjTBfRUfXzOLYo0/eUElJWXsLioAm2Bo uzyO3xMLwtzoMQSLvAxZMQFOdlLq5ssIlNEowC7/xD4lNVQeCFshHm0DUDjc6I/Z LefRgeHX5jrfDmfraTdwNievHAMKuRE/ko0afpHy7QODaNd/8R+Jbxj1jnileZyt INm+qzGOZ9ok8gGk7yGCyteuWnkuHBktNC9V+Y7poisdGnZUlE1uwf+e7Ra8iekW NsaLxlNn609pADsYVSsZI6Cu6UfXOdtQdoy+gfkHZu9Oyvf0jnY3OGCKSEWmhecg DVwvFS9OuKYROZVPmSTZXBEVWEnwGSqHQKTiW++TN+07uvDstajpm6s2orTzgYB5 i1cNAB598v+eA7ty/ntt =ZX/W -----END PGP SIGNATURE----- --=-qx3f4/weV05ByAUrxLbl-- From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 2 09:44:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B8BB28DA for ; Sat, 2 Nov 2013 09:44:57 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 518C32B7F for ; Sat, 2 Nov 2013 09:44:57 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id ex4so232217wid.1 for ; Sat, 02 Nov 2013 02:44:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=A5nJsac74wD6qv2eRYrF3kjyrinZOeLukN0mjDRgqaY=; b=VBDIw2waeg3CYqk+uUYJRkX8f+y6JMmkbVxCTQQSyvy0/KQ44z/fdvEBo+rUDmHUHV kkvf9RQHjHCEdzAM6AZv6KY7ttIQLb1AzddydabZwsTCE5pZlI70sbP3M4Ogq/ag7AiX xyfu418RlaGLRCGfhCNhsgnbppbJ8P+ZDSNz6M1OdkXHf+iPREaKj0wt4eZEyudQB4xv fvAeDAcxPzH+MpL7K2VbAuGHf8+Og0T54U9EF/uBSPxICTT+5FAKEMWhZGR8wli8dAbe MmmOQm+UA6O1GRINo3INBuTaefQpQXhUuoEbbZcuL4Q/ywlaEyEBNiV0Nv2LRlk5wfvz uQXA== X-Gm-Message-State: ALoCoQntMdtQoKfq+DVV9HUEpqWKB8M51+G8cwGDGabFFzWlKkLnLmfefigyFv/jxpKykvmreJQF MIME-Version: 1.0 X-Received: by 10.180.94.38 with SMTP id cz6mr5338104wib.27.1383385020990; Sat, 02 Nov 2013 02:37:00 -0700 (PDT) Received: by 10.227.226.196 with HTTP; Sat, 2 Nov 2013 02:37:00 -0700 (PDT) X-Originating-IP: [88.65.219.231] In-Reply-To: <1383382815.31973.1.camel@eva02.mbsd> References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> <1383338117.13657.53.camel@eva02.mbsd> <1383382815.31973.1.camel@eva02.mbsd> Date: Sat, 2 Nov 2013 10:37:00 +0100 Message-ID: Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: Bernhard Schmidt To: clutton Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 09:44:57 -0000 On Sat, Nov 2, 2013 at 10:00 AM, clutton wrote: > On Fri, 2013-11-01 at 23:50 -0700, Adrian Chadd wrote: >> OK, so where's the other path for invoking wpa_supplicant? > > What do you mean? kldload if_ath if will create ath0 which is a INET interface which will invoke pccard_ether, which will configure the interface based on what is configured in rc.conf. Point is, down the road wlan0 will be created, with 2 things following 1. start wpa_supplicant if it is configured in rc.conf 2. create an event for devd which will again invoke pccard_ether for wlan0 So basically we have 2 instances of pccard_ether started, one for ath0 and one for wlan0. create ath0 -> devd (new interface ath0) -> pccard_ether -> create wlan0 (*) -> start wpa_supplicant (*) devd (new interface wlan0) -> pccard_ether -> start wpa_supplicant Hope that makes it a bit clearer. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 2 17:00:54 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AF08AD33 for ; Sat, 2 Nov 2013 17:00:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6BC2E2E5C for ; Sat, 2 Nov 2013 17:00:54 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id n9so3127573qcw.15 for ; Sat, 02 Nov 2013 10:00:53 -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:message-id:subject :from:to:cc:content-type; bh=H6wOC4SxCkHWLgae1OWfy5GBHUIrh58KyBSdxj5WSDM=; b=L3PGi/EqR4yM5g3qYWIhmidS/tUDnTtg7q4M+r+EO/7lV5n/6xbker5x24Os3cst95 l+UGBNlqw6qniJQjETOI4azZoQiMJfvkaMfACkcu2MbGoh24Ni+O6r26mjUVTQx0iyoO it711umv/g+roHpKKL9sXjQ58IHW4I3sRlNMxcvYifD0GqIZM90gPqgDHPVwPhCvsumD BNGO/iWLYbzeip/5Q43RAIC9JXLcZ65tRIlR9bCGHBZEzDFRmXzf1EwPw1TK4LN7sS6D 4oyS/LKh8qsSVlop25mNzV5QSPTHUzLaqAzSJOeEBVLsQY1HPpYFscEGW9IhcgVwWhet GbqQ== MIME-Version: 1.0 X-Received: by 10.49.127.179 with SMTP id nh19mr11373529qeb.1.1383411653547; Sat, 02 Nov 2013 10:00:53 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sat, 2 Nov 2013 10:00:53 -0700 (PDT) In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> <1383338117.13657.53.camel@eva02.mbsd> <1383382815.31973.1.camel@eva02.mbsd> Date: Sat, 2 Nov 2013 10:00:53 -0700 X-Google-Sender-Auth: sptb0hqmjX7E5JdMXxgTbVkBjjQ Message-ID: Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: Adrian Chadd To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: clutton , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 17:00:54 -0000 right, this makes it clearer. What about: * the wpa_supplicant rc script only starts/stops one wpa_supplicant instance * upon ethernet / wlan clone creation, use interface_add to add the interface to wpa_supplicant * upon ethernet / wlan clone destruction, use interface_remove how's that sound? -adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 2 19:13:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6FB4FB72 for ; Sat, 2 Nov 2013 19:13:33 +0000 (UTC) (envelope-from clutton@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 4CBC423F7 for ; Sat, 2 Nov 2013 19:13:33 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version; b=bVtnquAakUMHUq0+83oLJOwaFaN1aZeeyOtv1XAeGWZsoLEkfs2aDp5ZZee4awtnpIL5iQd3WWI0 VWuw90+LnncGDWdnWZTV4YVHe8+P8MwXgD7DaZbGi38npgERHgbe Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1383419606653341.2057659007768; Sat, 2 Nov 2013 12:13:26 -0700 (PDT) Subject: Re: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org In-Reply-To: References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> <1383331203.12614.1.camel@eva02.mbsd> <1383336004.13657.18.camel@eva02.mbsd> <1383338117.13657.53.camel@eva02.mbsd> <1383382815.31973.1.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-n+s/DsaiIaKH72GPhAGc" Date: Sat, 02 Nov 2013 21:13:16 +0200 Message-ID: <1383419596.3253.42.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_25103_328 X-ZohoMail-Owner: <1383419596.3253.42.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-ZohoMailClient: External X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 19:13:33 -0000 --=-n+s/DsaiIaKH72GPhAGc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, 2013-11-02 at 10:00 -0700, Adrian Chadd wrote: > right, this makes it clearer. >=20 > What about: >=20 > * the wpa_supplicant rc script only starts/stops one wpa_supplicant insta= nce > * upon ethernet / wlan clone creation, use interface_add to add the > interface to wpa_supplicant > * upon ethernet / wlan clone destruction, use interface_remove >=20 > how's that sound? >=20 >=20 > -adrian Sounds nice, but firstly we need to figure out this case, and then we can do adding/removing/whatever Without fixing that, it would be possible to see adding/removing/whatever twice. How to reproduce: 1) put debug info into rc.d/wpa_supplicant, a =C2=ABtoto=C2=BB looks very informative! =E2=86=911 ~ =E2=86=92 diff -u /usr/src/etc/rc.d/wpa_supplicant /etc/rc.d/w= pa_supplicant --- /usr/src/etc/rc.d/wpa_supplicant 2013-06-19 01:06:53.911196741 +0300 +++ /etc/rc.d/wpa_supplicant 2013-11-02 20:42:02.556222618 +0200 @@ -34,6 +34,8 @@ driver=3D"bsd" fi =20 +echo toto >> /tmp/toto + load_rc_config $name =20 command=3D${wpa_supplicant_program} zsh: exit 1 diff -u /usr/src/etc/rc.d/wpa_supplicant /etc/rc.d/wpa_supplicant =E2=86=911 ~ =E2=86=92=20 2) then: service netif restart 3) then: cat /tmp/toto, how many totos do you see? 4) if you are lucky like I am, you can even observe something like this: root 15038 0.0 0.1 21596 6100 - Ss 8:42pm 0:00.16 /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant.conf -D bsd -P /var/run/wpa_supplicant/wlan0.pid root 15077 0.0 0.1 21596 6112 - Ss 8:42pm 0:00.12 /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant.conf -D bsd -P /var/run/wpa_supplicant/wlan0.pid What was happened? netif tries to setup wlan0 (clone, wpa, dhcp, etc), when wlan0 interface occurs, devd runs another copy of netif. --=-n+s/DsaiIaKH72GPhAGc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJSdU7MAAoJECNkWbjnbjui98sQAIYwzxdGjOMUFcSctjUcYrT0 2oMtA7/q2s6gCKlmNvamd76v5onat2Exw8RKkRbaFWNltJgEx/N5N3im8LGyGzg8 Xdps6Tm5+nUBKcRPe70p/e4UQCcl1smWXbT2wrtVtTE4PJ2IE6SiVKiqcucyzYD+ 8xnyVgDiWDsytQob89E4Fpj6/0YtzEca8Z7SwycOAFjvO6cQ+rOKEqkHdyK7hN1r o4fsVWGqP1jP59Qm3eofyZWpGqj2ZOZnJXSvfsCPHH7EqPexULWc9TclueFmveWJ Hdw93ro5YR4E6GcUfMZuOpGPHszom3alHpi7dnNpBqr2ZCFC+DNPawQoYJRpQIP9 rX7hophzacx4vS+VcxwHupS1YSC5uYAlnqTTtUZfyBi0CwcjY1ce9rnyXF8Nx4c9 +i8tCeqLHHE0Ql9A1UqTWESNyX8UHYK7Gm4PzSh38c0O6nmJ5Dn/Gr5Nui0hiWgz b0Y+WaJcUmm9rOCapkbBWO6wsVZ0zy7alQkgkk+T2y8pQIjpdRfL4YQeGfBmlPFW mXHtl2Q3YcFkEbNht8TDwxxe83Cg7U+w0ZFBhmEVgpnNBtkoLFzI7C3JeRYm3xaM p3T2qlCixKZogXSTLmLDZTzaCAAoFu3jnCEnT1/xo2KWFNZ5yMctMlVX8AJXXYWz uGw7RwhUvhghIkKITPJR =9ubh -----END PGP SIGNATURE----- --=-n+s/DsaiIaKH72GPhAGc--