From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 21 05:05:50 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 74348519 for ; Mon, 21 Oct 2013 05:05:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 37B4D29D8 for ; Mon, 21 Oct 2013 05:05:50 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 8so3482105qea.32 for ; Sun, 20 Oct 2013 22:05:49 -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=nQMFU1oM/2gnzy2McN7zu25Uu9osDsnm+rtkC8dNwNk=; b=Ctu9PwJKGlig4H01Z7QDdfzr/BXWp5qAANB1pwXa7VWiY//f1nCuS42ZtN6IAn8Gb0 0rqpOdT5VbDEcL0n8RU7jeVg3M/oNppLKXhiPoybe6XcF4iogdSF1I05BP8T5Qqj6j54 BtrHeU4RnsulcFfHqMwnHpQcHxpD8axkTasihG4dksgiVIJVFwYpcmbnVsFDaD7z9rJ9 Fga5gHEzSgVY6ffLuL5q8u/Iadaop/BgQJCrm7h2U4szduupA3KU4hK13TltQoBrK9k7 qfQiY//OSTd+qAZv2dlI+QUpnw3KIbgMU6y5/VNEfptgkacr0RgxrnxcVWunBZIh4wqP TEJA== MIME-Version: 1.0 X-Received: by 10.49.130.132 with SMTP id oe4mr6795qeb.86.1382331949436; Sun, 20 Oct 2013 22:05:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sun, 20 Oct 2013 22:05:49 -0700 (PDT) Date: Sun, 20 Oct 2013 22:05:49 -0700 X-Google-Sender-Auth: 2YycKfdca3BOtL75YaxEbnMS81w Message-ID: Subject: implementing multiple BSSID addresses for different VAPs, or 'why was the flag called bssid again?' From: Adrian Chadd To: "freebsd-wireless@freebsd.org" , =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= 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: Mon, 21 Oct 2013 05:05:50 -0000 So, I finally (!) figured out how this address cloning crap works. In if_ath.c, there's assign_address(). It, yes, assigns addresses. If the hardware supports the bssid mask field and the clone flag is set, it sets up multiple addresses. This works great for up to 4 MACs. We have to modify it to support more than 4 MAC addresses per NIC. .. but, how do you set the clone flag? The ifconfig manpage has two entries for 'bssid'. * the first is when you 'create' a VAP. It's passed as an arguement during create, but before wlanmode. It doesn't take an option. * the second is for setting the BSS ID for the VAP. It _does_ take an option (the MAC.) If you try this, it fails: * ifconfig wlan11 create wlandev ath0 wlanmode hostap ssid 'foo_2' bssid If you try this, it works: * ifconfig wlan11 create wlandev ath0 bssid wlanomde hostap ssid 'foo_2' So, if you run multi-VAP, and you want to use WPA on all of the VAPs, please try using 'bssid' as above and ensure you get multiple MAC addresses. This should make things behave much, much better. If it doesn't then we have bigger problems. Thanks, -adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 21 11:06: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 A9A1CA86 for ; Mon, 21 Oct 2013 11:06:57 +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 95C2B2E34 for ; Mon, 21 Oct 2013 11:06:57 +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 r9LB6vAE018834 for ; Mon, 21 Oct 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9LB6v9T018832 for freebsd-wireless@FreeBSD.org; Mon, 21 Oct 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Oct 2013 11:06:57 GMT Message-Id: <201310211106.r9LB6v9T018832@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, 21 Oct 2013 11:06:57 -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 Mon Oct 21 20:03: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 54CF0A40; Mon, 21 Oct 2013 20:03:34 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward16.mail.yandex.net (forward16.mail.yandex.net [IPv6:2a02:6b8:0:1402::1]) by mx1.freebsd.org (Postfix) with ESMTP id 05F662225; Mon, 21 Oct 2013 20:03:34 +0000 (UTC) Received: from smtp16.mail.yandex.net (smtp16.mail.yandex.net [95.108.252.16]) by forward16.mail.yandex.net (Yandex) with ESMTP id 63891D22067; Tue, 22 Oct 2013 00:03:31 +0400 (MSK) Received: from smtp16.mail.yandex.net (localhost [127.0.0.1]) by smtp16.mail.yandex.net (Yandex) with ESMTP id B44576A0754; Tue, 22 Oct 2013 00:03:30 +0400 (MSK) Received: from v3-151-7.yandex.net (v3-151-7.yandex.net [84.201.151.7]) by smtp16.mail.yandex.net (nwsmtp/Yandex) with ESMTP id cS8prTbqQD-3U848Fwd; Tue, 22 Oct 2013 00:03:30 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1382385810; bh=BbQJ1RGNFY5UVp5wFZPZJxeUtqaWILQasz8lK1ScA+s=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=B09Z0qGjBDvz2qKjnYN7DWGgPehJyxbtFNJmoUhrR96dUWizom3o35tVc8wbSkvLu LaV+qLX8WqIyjbthjP3O/ljgifLRpJgWjSkmXpB1Mu6JnGyBZC3k3J4aH4Prf6oeei xpw0Un58xWaIbcGJ0YQXAwjNDsWXiQg/n3/nORNo= Authentication-Results: smtp16.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5265878B.1050809@yandex.ru> Date: Mon, 21 Oct 2013 23:59:07 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: [rfc] removing the NDISulator References: <81.4D.19454.84022625@cdptpa-oedge03> In-Reply-To: <81.4D.19454.84022625@cdptpa-oedge03> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: 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: Mon, 21 Oct 2013 20:03:34 -0000 On 19.10.2013 10:01, Thomas Mueller wrote: > I too would like to see more effort writing new Ethernet and wifi > drivers and porting from other operating systems. > > But I would like to keep the NDISulator/NDISwrapper as a fallback. > > There are still wifi adapters, Ethernet too, where there is no > FreeBSD driver (AR9271 for instance), or the FreeBSD driver is > buggy. I'm agree. While there are still some devices without native drivers, but that work via NDISulator, we should keep it. -- WBR, Andrey V. Elsukov From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 21 20:07:42 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 9D3D7D84; Mon, 21 Oct 2013 20:07:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4C6842266; Mon, 21 Oct 2013 20:07:42 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id j15so2759445qaq.6 for ; Mon, 21 Oct 2013 13:07:41 -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=liBR6BBiCOwhHyD4a4JIH88S7bsve0z35P3dcZn7Zlk=; b=IPFsaUTtJrlKvX/GllNZiufkwB5lAnIiiiiXipcBvuXTcJzDWSGPJcMWliAYJJ/XGr daLQqEnAdSIQ+Jvp/E1qM4qYFr8s1EmpBSLpCROAvRpNFMQQtiYcdwsq0Hg2jWa9dcS9 eDXhawH35Jg1Ma2CZFItfmGmUZ/0BuSEr+AJ0BIamnmaIuFFvNMdTQuMe885j1CbHJEj S+jm62LlM1ENH5ReTm0sfTNLNWSi8ZZkcVhs2WvSggcXlnvQiRcpSDrVCPSSBtkFqer4 z2pLQYaKV3wkI5/VEb0sRLzaT4cQCnvCKjiPWpn+NcUfbUHQ5Jem+MN6JP5rzsPl5hti ZqBg== MIME-Version: 1.0 X-Received: by 10.224.167.206 with SMTP id r14mr25498788qay.4.1382386061003; Mon, 21 Oct 2013 13:07:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 21 Oct 2013 13:07:40 -0700 (PDT) In-Reply-To: <5265878B.1050809@yandex.ru> References: <81.4D.19454.84022625@cdptpa-oedge03> <5265878B.1050809@yandex.ru> Date: Mon, 21 Oct 2013 13:07:40 -0700 X-Google-Sender-Auth: 85ufjsxvpXzP8yAO0zoo3UeF6tY Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: "Andrey V. Elsukov" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 21 Oct 2013 20:07:42 -0000 On 21 October 2013 12:59, Andrey V. Elsukov wrote: > On 19.10.2013 10:01, Thomas Mueller wrote: > > I too would like to see more effort writing new Ethernet and wifi > > drivers and porting from other operating systems. > > > > But I would like to keep the NDISulator/NDISwrapper as a fallback. > > > > There are still wifi adapters, Ethernet too, where there is no > > FreeBSD driver (AR9271 for instance), or the FreeBSD driver is > > buggy. > > I'm agree. While there are still some devices without native drivers, > but that work via NDISulator, we should keep it. > It's honestly about time that these were updated, fixed and/or ported to FreeBSD. So, I'm still going forward with the plan. I won't be killing it during the 10 lifecycle. -adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 21 21:47:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8399D51B; Mon, 21 Oct 2013 21:47:18 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (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 1101E28D9; Mon, 21 Oct 2013 21:47:17 +0000 (UTC) Received: from mart.js.berklix.net (p57BCF4E4.dip0.t-ipconnect.de [87.188.244.228]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r9LLl8OG018137; Mon, 21 Oct 2013 21:47:09 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r9LLl4tH078191; Mon, 21 Oct 2013 23:47:04 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r9LLkqZ1044966; Mon, 21 Oct 2013 23:46:58 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310212146.r9LLkqZ1044966@fire.js.berklix.net> To: "Andrey V. Elsukov" , Adrian Chadd Subject: Re: [rfc] removing the NDISulator From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 21 Oct 2013 23:59:07 +0400." <5265878B.1050809@yandex.ru> Date: Mon, 21 Oct 2013 23:46:52 +0200 Sender: jhs@berklix.com Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 21 Oct 2013 21:47:18 -0000 "Andrey V. Elsukov" wrote: > I'm agree. While there are still some devices without native drivers, > but that work via NDISulator, we should keep it. Yes, best keep it while it helps some people. Adrian Chadd wrote: > It's honestly about time that these were updated, fixed and/or ported to > FreeBSD. > > So, I'm still going forward with the plan. I won't be killing it during the > 10 lifecycle. If ndis is removed while it works, that would be bad for users, some of whom won't even be on lists, but use ndis as their lifeboat. If ndis is later labeled as abandoned & if maintenance ceases, & if it then breaks, only then will pressure increase on others to step forward & help fix things; if a wait then sees no one stepping forward, surely only then would removal seem most appropriate ? Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with "> ". Send plain text, not quoted-printable, HTML, base64, or multipart/alternative. From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 21 22:29: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 D51041A8; Mon, 21 Oct 2013 22:29:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 819F02B3E; Mon, 21 Oct 2013 22:29:25 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id i13so2872695qae.15 for ; Mon, 21 Oct 2013 15:29:24 -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=9S7zz1ir/Ac5ofoWkNKhp1JiqRaN6i/OGX+W/5GBiS4=; b=uA6daoWD7ANOwxMsG6Z7KiBOu0YJdLNUYEfQLFvFNhStrdW8Pks4CAOLI3xUqZbzJ+ X6DWw0Rljud2LWqso501lrogzOexQ9TPX6Arf3xe/JRpkXHH4KciPZFbvMbJHlX7nQa6 Pkc+qW/en6HKmgXT+y84paB839KQJr3U/8JtN2VWNxJxO2503FdigAaNL2NesuNwMlr5 C4LcKbBxyxL6X7VPnWT3VrmhfxUX4md9NOpM3ui/IlBiNkNQvNMdB37kO5sx8Jkmt7F0 4pAwBivhJlbdgy2QdkMHoKsKE9Wm5DdRU1SX8h2u1WAQ7Gu+j2XrQ2QCTE1vsLk75UtJ hq9Q== MIME-Version: 1.0 X-Received: by 10.224.167.206 with SMTP id r14mr26172289qay.4.1382394564591; Mon, 21 Oct 2013 15:29:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 21 Oct 2013 15:29:24 -0700 (PDT) In-Reply-To: <201310212146.r9LLkqZ1044966@fire.js.berklix.net> References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> Date: Mon, 21 Oct 2013 15:29:24 -0700 X-Google-Sender-Auth: ymI1TcBFoob0aaA4zPlKqcFQzwg Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: "Julian H. Stacey" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 21 Oct 2013 22:29:25 -0000 The NDISulator is a crutch from a time when there wasn't _any_ real alternative. There are plenty of alternatives now. What's lacking is desire and person-power. But the datasheets are there, or the vendor code has been released, or there's linux/otherbsd drivers. Leaving it in there is just delaying the inevitable - drivers need to be fixed, ported, or reverse engineered. This is going to upset users in the same way that eliminating any other transition/sideways compatibility layer upsets users. But as I said, the path forward is fixing up the lack of stable drivers, not simply supporting some crutch. If there are drivers that people absolutely need fixed then they should stand up and say "hey, I really would like X to work better!" and then follow it up with some encouraging incentives. Right now the NDISulator lets people work _around_ this by having something that kind of works for them but it doesn't improve our general driver / stack ecosystems. -adrian On 21 October 2013 14:46, Julian H. Stacey wrote: > "Andrey V. Elsukov" wrote: > > > I'm agree. While there are still some devices without native drivers, > > but that work via NDISulator, we should keep it. > > Yes, best keep it while it helps some people. > > > Adrian Chadd wrote: > > > It's honestly about time that these were updated, fixed and/or ported to > > FreeBSD. > > > > So, I'm still going forward with the plan. I won't be killing it during > the > > 10 lifecycle. > > If ndis is removed while it works, that would be bad for users, > some of whom won't even be on lists, but use ndis as their lifeboat. > > If ndis is later labeled as abandoned & if maintenance ceases, & if it > then breaks, only then will pressure increase on others to step > forward & help fix things; if a wait then sees no one stepping forward, > surely only then would removal seem most appropriate ? > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich > http://berklix.com > Interleave replies below like a play script. Indent old text with "> ". > Send plain text, not quoted-printable, HTML, base64, or > multipart/alternative. > From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 22 07:53:43 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 35375157 for ; Tue, 22 Oct 2013 07:53:43 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id F07D025E9 for ; Tue, 22 Oct 2013 07:53:42 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:42385] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 05/BE-02506-FFE26625; Tue, 22 Oct 2013 07:53:36 +0000 Date: Tue, 22 Oct 2013 07:53:35 +0000 Message-ID: <05.BE.02506.FFE26625@cdptpa-oedge01> From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> Subject: Re: [rfc] removing the NDISulator X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 Cc: 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: Tue, 22 Oct 2013 07:53:43 -0000 > The NDISulator is a crutch from a time when there wasn't _any_ real > alternative. > There are plenty of alternatives now. What's lacking is desire and > person-power. But the datasheets are there, or the vendor code has been > released, or there's linux/otherbsd drivers. > Leaving it in there is just delaying the inevitable - drivers need to be > fixed, ported, or reverse engineered. > This is going to upset users in the same way that eliminating any other > transition/sideways compatibility layer upsets users. But as I said, the > path forward is fixing up the lack of stable drivers, not simply supporting > some crutch. > If there are drivers that people absolutely need fixed then they should > stand up and say "hey, I really would like X to work better!" and then > follow it up with some encouraging incentives. Right now the NDISulator > lets people work _around_ this by having something that kind of works for > them but it doesn't improve our general driver / stack ecosystems. > -adrian Sometimes a crutch is needed. But it would be desirable to have a means for using a driver from Linux, NetBSD or OpenBSD. Sometimes the FreeBSD driver is buggy, like re with Realtek 8111E on MSI Z77 MPOWER motherboard. I couldn't checkout FreeBSD 10-current source tree from 9.2 amd64 or 9.1-STABLE i386 USB stick, but was able to checkout and update the source tree to build FreeBSD 10-current (now 11-current and 10.0-BETA1) after updating my NetBSD-HEAD amd64 USB-stick installation and building subversion from pkgsrc. I could checkout the ports tree too but would not be able to make fetch. A driver might work with FreeBSD but fail temporarily in a later source revision due to a new bug. So it's good to use FreeBSD native driver when possible but have ndis for fallback. One problem with NDIS is that now it seems that running "unzip -l" on the Windows driver shows no .inf and .sys files. One can then try from ReactOS or Wine, and even if the installation of Windows driver doesn't work, it might possibly yield .inf and .sys files. I never tried that so am not making any bets. Tom From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 22 16:07:58 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 76718E0E; Tue, 22 Oct 2013 16:07:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2381E24EA; Tue, 22 Oct 2013 16:07:58 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id gc15so4948904qeb.15 for ; Tue, 22 Oct 2013 09:07:57 -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=TZHOiAE8hKZ6ZUK7K6mKLCodxLzm/YBOJu8ZiPZ+REM=; b=cpPPyU0CxWOx+NbkzCmgnMHC6lvIFqg69NdVOs9VxsZxvJ9eZVrD+XFQG05KXtSCII VD3c15osOXxJSifaa3Gi9RklKnijHvLfhyCD8l3/MnAnTQ0c3T6r+6EYXDhX/NX3Oc92 ogcYukQs547mQ1hImmWIMCqtk2eaJl0weLwgh2Fdb+uGRVWYTVpSQHFfQtQBTt7s4Voa GNFq2PclZqtjSbwAPb+QnkX8jwzy68uuT1DPyniPV57qiY+x4xgkTErXtGM3oCgQRVaV k18zcUBlfeqJ++Wgpo76tScAWQ9BGqHjK2hiUhihvln62uIvdjSoL2G1NxlF8aMbgS3g CPlQ== MIME-Version: 1.0 X-Received: by 10.49.127.179 with SMTP id nh19mr29993888qeb.1.1382458077212; Tue, 22 Oct 2013 09:07:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 22 Oct 2013 09:07:57 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Oct 2013 09:07:57 -0700 X-Google-Sender-Auth: zSqfefMoreg7Ukj_65a3ocClEv4 Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: Adrian Chadd To: claudiu vasadi , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@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, 22 Oct 2013 16:07:58 -0000 I know what's causing this! It's because when the management frame completes, there's a callback mbuf tag (M_TXCB) that causes the driver to call the net80211 TX completion callback. Now, because some drivers call the net80211 tx completion callback from within their driver locks, it causes locking issues. So, someone (I don't know or really care who) made it so whenever a TX completion occurs, the net80211 code will schedule a callout to occur. This means the callout occurs outside of the driver locks, solving that issue. This has a bunch of problems. * Firstly, if you have multiple management frames coming in, only the most recent will be acknowledged. Tsk. There's only one callout, and it's per vap. * Secondly, no node reference is taken before scheduling the callout, so if the node is destroyed (eg because the BSS is freed during a channel scan or reset) and the callout still occurs, it'll dereference a bad node. This is the crash cause. * Thirdly, the cancellation occurs in the VAP state change path. It doesn't know about the node(s) that just received TX completions. Since the callback is per vap, there's no way to figure out which node needs dereferencing.. so things blow up. The solution is just to undo this brain damaged solution and require that drivers call the TX completion callback with no driver locks held. That's on my TODO list but it'll take a little more time. Now that 10 has branched I'll be happy to just flip that switch in -HEAD and deal with the locking fallout. Thanks, -adrian On 22 October 2013 07:28, claudiu vasadi wrote: > Hi everyone, > > I have a Lenovo Thinkpad T420s with Intel core i7 @ 2.70GHz, 8GB RAM, Intel > SSD 160GB and iwn0: mem > 0xf4200000-0xf4201fff irq 17 at device 0.0 on pci3 > > Today, while connecting to different AP's, I noticed at one point that I > was not getting an IP although the wifi card was associated. Within > "wifimgr", I did a "Save and Reconnect" and then got a core dump. > > Bellow, the bt: > > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xffffff801e5f7000 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80a10431 > stack pointer = 0x28:0xffffff8000276980 > frame pointer = 0x28:0xffffff8000276a20 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi4: clock) > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff80948a06 at kdb_backtrace+0x66 > #1 0xffffffff8090e50e at panic+0x1ce > #2 0xffffffff80cf3440 at trap_fatal+0x290 > #3 0xffffffff80cf37a1 at trap_pfault+0x211 > #4 0xffffffff80cf3d54 at trap+0x344 > #5 0xffffffff80cdd093 at calltrap+0x8 > #6 0xffffffff808dfddd at intr_event_execute_handlers+0xfd > #7 0xffffffff808e15cd at ithread_loop+0x9d > #8 0xffffffff808dc82f at fork_exit+0x11f > #9 0xffffffff80cdd5be at fork_trampoline+0xe > Uptime: 8h20m28s > Dumping 952 out of 8106 MB:..2% (CTRL-C to abort) (CTRL-C to abort) > (CTRL-C to abort) (CTRL-C to abort) ..11% (CTRL-C to abort) (CTRL-C to > abort) ..21%..31% (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) > (CTRL-C to abort) (CTRL-C to abort) ..41% (CTRL-C to abort) (CTRL-C to > abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to > abort) (CTRL-C to abort) (CTRL-C to abort) ..51% (CTRL-C to abort) > (CTRL-C to abort) ..61% (CTRL-C to abort) ..71% (CTRL-C to abort) > ..81%..91% > > Reading symbols from /boot/kernel/zfs.ko...Reading symbols from > /boot-mount/boot/kernel/zfs.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/zfs.ko > Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from > /boot-mount/boot/kernel/opensolaris.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/opensolaris.ko > Reading symbols from /boot/kernel/geom_eli.ko...Reading symbols from > /boot-mount/boot/kernel/geom_eli.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/geom_eli.ko > Reading symbols from /boot/kernel/crypto.ko...Reading symbols from > /boot-mount/boot/kernel/crypto.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/crypto.ko > Reading symbols from /boot/kernel/linux.ko...Reading symbols from > /boot-mount/boot/kernel/linux.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/linux.ko > Reading symbols from /boot/kernel/drm.ko...Reading symbols from > /boot-mount/boot/kernel/drm.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/drm.ko > Reading symbols from /boot/modules/nvidia.ko...done. > Loaded symbols for /boot/modules/nvidia.ko > Reading symbols from /boot/kernel/mmc.ko...Reading symbols from > /boot-mount/boot/kernel/mmc.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/mmc.ko > Reading symbols from /boot/kernel/mmcsd.ko...Reading symbols from > /boot-mount/boot/kernel/mmcsd.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/mmcsd.ko > Reading symbols from /boot/kernel/acpi_call.ko...done. > Loaded symbols for /boot/kernel/acpi_call.ko > Reading symbols from /boot/kernel/umodem.ko...Reading symbols from > /boot-mount/boot/kernel/umodem.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/umodem.ko > Reading symbols from /boot/modules/vboxnetflt.ko...done. > Loaded symbols for /boot/modules/vboxnetflt.ko > Reading symbols from /boot/modules/vboxdrv.ko...done. > Loaded symbols for /boot/modules/vboxdrv.ko > Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from > /boot-mount/boot/kernel/netgraph.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/netgraph.ko > Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from > /boot-mount/boot/kernel/ng_ether.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/ng_ether.ko > Reading symbols from /boot/modules/vboxnetadp.ko...done. > Loaded symbols for /boot/modules/vboxnetadp.ko > #0 doadump (textdump=) at pcpu.h:234 > 234 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:234 > #1 0xffffffff8090dfe6 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:449 > #2 0xffffffff8090e4e7 in panic (fmt=0x1
) at > /usr/src/sys/kern/kern_shutdown.c:637 > #3 0xffffffff80cf3440 in trap_fatal (frame=0xc, eva=) > at /usr/src/sys/amd64/amd64/trap.c:879 > #4 0xffffffff80cf37a1 in trap_pfault (frame=0xffffff80002768d0, > usermode=0) at /usr/src/sys/amd64/amd64/trap.c:795 > #5 0xffffffff80cf3d54 in trap (frame=0xffffff80002768d0) at > /usr/src/sys/amd64/amd64/trap.c:463 > #6 0xffffffff80cdd093 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:232 > #7 0xffffffff80a10431 in ieee80211_tx_mgt_timeout (arg=0xffffff801e5f7000) > at /usr/src/sys/net80211/ieee80211_output.c:2487 > #8 0xffffffff809246e8 in softclock (arg=) at > /usr/src/sys/kern/kern_timeout.c:518 > #9 0xffffffff808dfddd in intr_event_execute_handlers (p= out>, ie=0xfffffe0007221b00) > at /usr/src/sys/kern/kern_intr.c:1272 > #10 0xffffffff808e15cd in ithread_loop (arg=0xfffffe0007209460) at > /usr/src/sys/kern/kern_intr.c:1285 > #11 0xffffffff808dc82f in fork_exit (callout=0xffffffff808e1530 > , arg=0xfffffe0007209460, > frame=0xffffff8000276b00) at /usr/src/sys/kern/kern_fork.c:990 > #12 0xffffffff80cdd5be in fork_trampoline () at > /usr/src/sys/amd64/amd64/exception.S:606 > #13 0x0000000000000000 in ?? () > > > One thing to keep in mind is that since I started using geli+ZFS (installed > with PC-BSD 9.1 cd), I always got "Cannot reset interface wlan0 - exit > status 1" with "wifimgr" whichever action i did (ex: reconect, rescan, > up/down,etc). > > > I would appreciate some help in debugging this. > > > -- > Best regards, > Claudiu Vasadi > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 22 16:56:52 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 0BF36580; Tue, 22 Oct 2013 16:56:52 +0000 (UTC) (envelope-from claudiu.vasadi@gmail.com) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB5322803; Tue, 22 Oct 2013 16:56:51 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id tp5so2232905ieb.31 for ; Tue, 22 Oct 2013 09:56:51 -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=W3EpCpG3w5RS61hCsJSAmmDzbAnmhMWAQ13xkpyqgYM=; b=ZZKxTqC+sTSLxVrW5hFDjqtFfYGrD+m7BOxhHIr/b3hQnm4YFtx4iUp1EjGpotul35 gl2x3ElbGw29C0TLaWmDRnHcHlOtncYDRlH6e/MoFPcMAZz6hdj5jFPIQsDA7Hv+hVbz 4Ci9xEaT5taKHaJECosjKi9qAh+7uKlzqnT3DJKorWj593V6MebyKyrYHHG0DItcJM6M T0E/Ii6pKhd9m3UwEydJrE7tF2ztmnQ9eJy/7xdvwm9442Vn4kz3ARhgAcmXZHdzrVq3 aCKtrF36vXe1MXtMpNE3Upk2wW8d+TA/26BBjLsU1bE8XPuIeL4RSE2IDn/qoySthXFS VloA== MIME-Version: 1.0 X-Received: by 10.50.122.40 with SMTP id lp8mr14429326igb.24.1382461011070; Tue, 22 Oct 2013 09:56:51 -0700 (PDT) Received: by 10.64.134.169 with HTTP; Tue, 22 Oct 2013 09:56:51 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Oct 2013 18:56:51 +0200 Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: claudiu vasadi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Oct 2013 16:56:52 -0000 For when the time comes, I'm all in for any tests (if needed). On Tue, Oct 22, 2013 at 6:07 PM, Adrian Chadd wrote: > I know what's causing this! > > It's because when the management frame completes, there's a callback mbuf > tag (M_TXCB) that causes the driver to call the net80211 TX completion > callback. > > Now, because some drivers call the net80211 tx completion callback from > within their driver locks, it causes locking issues. So, someone (I don't > know or really care who) made it so whenever a TX completion occurs, the > net80211 code will schedule a callout to occur. This means the callout > occurs outside of the driver locks, solving that issue. > > This has a bunch of problems. > > * Firstly, if you have multiple management frames coming in, only the most > recent will be acknowledged. Tsk. There's only one callout, and it's per > vap. > * Secondly, no node reference is taken before scheduling the callout, so > if the node is destroyed (eg because the BSS is freed during a channel scan > or reset) and the callout still occurs, it'll dereference a bad node. This > is the crash cause. > * Thirdly, the cancellation occurs in the VAP state change path. It > doesn't know about the node(s) that just received TX completions. Since the > callback is per vap, there's no way to figure out which node needs > dereferencing.. so things blow up. > > The solution is just to undo this brain damaged solution and require that > drivers call the TX completion callback with no driver locks held. That's > on my TODO list but it'll take a little more time. Now that 10 has branched > I'll be happy to just flip that switch in -HEAD and deal with the locking > fallout. > > Thanks, > > > > -adrian > > > > On 22 October 2013 07:28, claudiu vasadi wrote: > >> Hi everyone, >> >> I have a Lenovo Thinkpad T420s with Intel core i7 @ 2.70GHz, 8GB RAM, >> Intel >> SSD 160GB and iwn0: mem >> 0xf4200000-0xf4201fff irq 17 at device 0.0 on pci3 >> >> Today, while connecting to different AP's, I noticed at one point that I >> was not getting an IP although the wifi card was associated. Within >> "wifimgr", I did a "Save and Reconnect" and then got a core dump. >> >> Bellow, the bt: >> >> >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you >> are >> welcome to change it and/or distribute copies of it under certain >> conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for >> details. >> This GDB was configured as "amd64-marcel-freebsd"... >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0xffffff801e5f7000 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff80a10431 >> stack pointer = 0x28:0xffffff8000276980 >> frame pointer = 0x28:0xffffff8000276a20 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 12 (swi4: clock) >> trap number = 12 >> panic: page fault >> cpuid = 0 >> KDB: stack backtrace: >> #0 0xffffffff80948a06 at kdb_backtrace+0x66 >> #1 0xffffffff8090e50e at panic+0x1ce >> #2 0xffffffff80cf3440 at trap_fatal+0x290 >> #3 0xffffffff80cf37a1 at trap_pfault+0x211 >> #4 0xffffffff80cf3d54 at trap+0x344 >> #5 0xffffffff80cdd093 at calltrap+0x8 >> #6 0xffffffff808dfddd at intr_event_execute_handlers+0xfd >> #7 0xffffffff808e15cd at ithread_loop+0x9d >> #8 0xffffffff808dc82f at fork_exit+0x11f >> #9 0xffffffff80cdd5be at fork_trampoline+0xe >> Uptime: 8h20m28s >> Dumping 952 out of 8106 MB:..2% (CTRL-C to abort) (CTRL-C to abort) >> (CTRL-C to abort) (CTRL-C to abort) ..11% (CTRL-C to abort) (CTRL-C to >> abort) ..21%..31% (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) >> (CTRL-C to abort) (CTRL-C to abort) ..41% (CTRL-C to abort) (CTRL-C to >> abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C >> to >> abort) (CTRL-C to abort) (CTRL-C to abort) ..51% (CTRL-C to abort) >> (CTRL-C to abort) ..61% (CTRL-C to abort) ..71% (CTRL-C to abort) >> ..81%..91% >> >> Reading symbols from /boot/kernel/zfs.ko...Reading symbols from >> /boot-mount/boot/kernel/zfs.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/zfs.ko >> Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from >> /boot-mount/boot/kernel/opensolaris.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/opensolaris.ko >> Reading symbols from /boot/kernel/geom_eli.ko...Reading symbols from >> /boot-mount/boot/kernel/geom_eli.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/geom_eli.ko >> Reading symbols from /boot/kernel/crypto.ko...Reading symbols from >> /boot-mount/boot/kernel/crypto.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/crypto.ko >> Reading symbols from /boot/kernel/linux.ko...Reading symbols from >> /boot-mount/boot/kernel/linux.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/linux.ko >> Reading symbols from /boot/kernel/drm.ko...Reading symbols from >> /boot-mount/boot/kernel/drm.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/drm.ko >> Reading symbols from /boot/modules/nvidia.ko...done. >> Loaded symbols for /boot/modules/nvidia.ko >> Reading symbols from /boot/kernel/mmc.ko...Reading symbols from >> /boot-mount/boot/kernel/mmc.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/mmc.ko >> Reading symbols from /boot/kernel/mmcsd.ko...Reading symbols from >> /boot-mount/boot/kernel/mmcsd.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/mmcsd.ko >> Reading symbols from /boot/kernel/acpi_call.ko...done. >> Loaded symbols for /boot/kernel/acpi_call.ko >> Reading symbols from /boot/kernel/umodem.ko...Reading symbols from >> /boot-mount/boot/kernel/umodem.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/umodem.ko >> Reading symbols from /boot/modules/vboxnetflt.ko...done. >> Loaded symbols for /boot/modules/vboxnetflt.ko >> Reading symbols from /boot/modules/vboxdrv.ko...done. >> Loaded symbols for /boot/modules/vboxdrv.ko >> Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from >> /boot-mount/boot/kernel/netgraph.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/netgraph.ko >> Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from >> /boot-mount/boot/kernel/ng_ether.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/ng_ether.ko >> Reading symbols from /boot/modules/vboxnetadp.ko...done. >> Loaded symbols for /boot/modules/vboxnetadp.ko >> #0 doadump (textdump=) at pcpu.h:234 >> 234 pcpu.h: No such file or directory. >> in pcpu.h >> (kgdb) bt >> #0 doadump (textdump=) at pcpu.h:234 >> #1 0xffffffff8090dfe6 in kern_reboot (howto=260) at >> /usr/src/sys/kern/kern_shutdown.c:449 >> #2 0xffffffff8090e4e7 in panic (fmt=0x1
) at >> /usr/src/sys/kern/kern_shutdown.c:637 >> #3 0xffffffff80cf3440 in trap_fatal (frame=0xc, eva=> out>) >> at /usr/src/sys/amd64/amd64/trap.c:879 >> #4 0xffffffff80cf37a1 in trap_pfault (frame=0xffffff80002768d0, >> usermode=0) at /usr/src/sys/amd64/amd64/trap.c:795 >> #5 0xffffffff80cf3d54 in trap (frame=0xffffff80002768d0) at >> /usr/src/sys/amd64/amd64/trap.c:463 >> #6 0xffffffff80cdd093 in calltrap () at >> /usr/src/sys/amd64/amd64/exception.S:232 >> #7 0xffffffff80a10431 in ieee80211_tx_mgt_timeout >> (arg=0xffffff801e5f7000) >> at /usr/src/sys/net80211/ieee80211_output.c:2487 >> #8 0xffffffff809246e8 in softclock (arg=) at >> /usr/src/sys/kern/kern_timeout.c:518 >> #9 0xffffffff808dfddd in intr_event_execute_handlers (p=> out>, ie=0xfffffe0007221b00) >> at /usr/src/sys/kern/kern_intr.c:1272 >> #10 0xffffffff808e15cd in ithread_loop (arg=0xfffffe0007209460) at >> /usr/src/sys/kern/kern_intr.c:1285 >> #11 0xffffffff808dc82f in fork_exit (callout=0xffffffff808e1530 >> , arg=0xfffffe0007209460, >> frame=0xffffff8000276b00) at /usr/src/sys/kern/kern_fork.c:990 >> #12 0xffffffff80cdd5be in fork_trampoline () at >> /usr/src/sys/amd64/amd64/exception.S:606 >> #13 0x0000000000000000 in ?? () >> >> >> One thing to keep in mind is that since I started using geli+ZFS >> (installed >> with PC-BSD 9.1 cd), I always got "Cannot reset interface wlan0 - exit >> status 1" with "wifimgr" whichever action i did (ex: reconect, rescan, >> up/down,etc). >> >> >> I would appreciate some help in debugging this. >> >> >> -- >> Best regards, >> Claudiu Vasadi >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >> " >> > > -- Best regards, Claudiu Vasadi From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 01:18: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 3417D5CD; Wed, 23 Oct 2013 01:18:27 +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 D5591268D; Wed, 23 Oct 2013 01:18:26 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id ii20so3849549qab.18 for ; Tue, 22 Oct 2013 18:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=EAaaBS6C0UFYdUKrtFZ0lb+L9Jk1MzO8AMEY3FHr+x8=; b=CCuGf7cWcWyjkmtWWXjca/aX1/fdHgr5HSm/46SW8cYMwJ5Xbk/6CnuXhCSVbvyD11 9dL7T9MyRrpnWGcXNvsGyOu4F/Jf7c/0httrEDPaN2Dk+yOFdpNY/pjBGljF4LSDYyaU l9yr6axv5rZ0ScerJPzzmgdlxGQ9Rt/xGcmPwqpSplM4PXlIcA4hcObwIcxG0Suvoy9t eb5Jq+hvFiZ5MddRNgMFJwh+uBgN94fykhHki7fMwgp/2+OXaNBb2/QD2OtCbFQNGZd1 qJhG9YLmFsFf9vJy4RT8e3dMCERktGYKkH1FcpUplPwjV+aIpzAFlWQKS6rRkArIy+M9 eXFg== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr757200qad.76.1382491106050; Tue, 22 Oct 2013 18:18:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 22 Oct 2013 18:18:25 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Oct 2013 18:18:25 -0700 X-Google-Sender-Auth: DvGJb_WlJ7MkU3exnbX1O1DWZxM Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: Adrian Chadd To: claudiu vasadi Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 01:18:27 -0000 Grr, it's slightly more complicated than that. That whole timer mess is actually used for two things: * if the management transmit succeeds - it acts as a short-interval (a few seconds) timer to ensure that the probe request ends up providing some response that transitions to auth; otherwise it aborts and transitions back to the SCAN state; * if the management transmit fails - it immediately transitions back to SCAN. So, the "correct" fix involves correctly locking things and turning that timer into a "if I fail to transition into a run state, then just go back to scanning" timeout. It sucks and it's going to take an evening of deep thought to figure out the correct solution to. Thanks for reminding me about this mess! -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 14:30:48 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 37920F2B; Wed, 23 Oct 2013 14:30:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0F92F2394; Wed, 23 Oct 2013 14:30:48 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 182E8B93B; Wed, 23 Oct 2013 10:30:47 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: [rfc] removing the NDISulator Date: Wed, 23 Oct 2013 10:23:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201310231023.32351.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 23 Oct 2013 10:30:47 -0400 (EDT) Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 14:30:48 -0000 On Monday, October 21, 2013 6:29:24 pm Adrian Chadd wrote: > The NDISulator is a crutch from a time when there wasn't _any_ real > alternative. > > There are plenty of alternatives now. What's lacking is desire and > person-power. But the datasheets are there, or the vendor code has been > released, or there's linux/otherbsd drivers. > > Leaving it in there is just delaying the inevitable - drivers need to be > fixed, ported, or reverse engineered. > > This is going to upset users in the same way that eliminating any other > transition/sideways compatibility layer upsets users. But as I said, the > path forward is fixing up the lack of stable drivers, not simply supporting > some crutch. > > If there are drivers that people absolutely need fixed then they should > stand up and say "hey, I really would like X to work better!" and then > follow it up with some encouraging incentives. Right now the NDISulator > lets people work _around_ this by having something that kind of works for > them but it doesn't improve our general driver / stack ecosystems. Eh, having taken a stab at porting the bwl blob already, I would strongly oppose removing NDIS. If you do that I will just stop using my netbook with a Broadcom part altogether as I wouldn't be able to use it to try to test bwl changes. The NDIS thing is a bit hackish, but it is quite useful for a lot of folks. -- John Baldwin From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 17:35:41 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 E0E1861E for ; Wed, 23 Oct 2013 17:35:41 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DE812FCA for ; Wed, 23 Oct 2013 17:35:41 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id v1so654426qcw.5 for ; Wed, 23 Oct 2013 10:35:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=V/4IKVIqS/c8Oj3wDhLOT1rW6gmrbdl+/nb0aku4UwE=; b=I2DZXcp2rHW1AM0wqPD2851vu2Xl5bYgCN7PoRxSSxPfSMCMGaXnM2KxG+xlqYFrNY Oq/IYgUn8hBVRnClTS7cEecRre6KdZkkXR15m0AofFMfFQiFPaaafB7Qz32H4EjjfcyP CX9GuZ41Ok8+1NPegQDh1C36nDKX7Tl0jCoTY= 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:from:date :message-id:subject:to:cc:content-type; bh=V/4IKVIqS/c8Oj3wDhLOT1rW6gmrbdl+/nb0aku4UwE=; b=KYlr5Jo9imTr0oHWAY61LGbcqojqlHT99D4aIPRDGuV1jepLpWpSb4FA4LT5gWaQRi AM6dgbJQ1jJL0JliSRv34c2oi6WkybnG9QgEojh1HYbRzlIQ0Rhs7SaSLC66qPiKTgAz 4sTA+OWRvJKBY5D+kDK6joQLHfgVyge4Sd6y3hLYNZNtaOFln0a88y1+mPp3MonQk5zV rOFOZ6/mxllypwwSzXUrhdEIo1eoXApqilzo6474OoJHRFZ9Ws3RjztNMylsj29jsfGR VpykP4gO5GM5UAa+k35Ggou2c28uHEvuWhhGaUdM/vIsbpz0CM2u4mYGAzQG8dj3OWxZ OZYg== X-Gm-Message-State: ALoCoQmDT0CFMXuZbPIxi6VymjQU32ppbUoRmfuK/8mQfRp8rdgcTc3TEFv4cdXcm70RdN5znt71 X-Received: by 10.224.69.132 with SMTP id z4mr5541158qai.78.1382549740530; Wed, 23 Oct 2013 10:35:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.63.101 with HTTP; Wed, 23 Oct 2013 10:35:10 -0700 (PDT) In-Reply-To: References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> From: Eitan Adler Date: Wed, 23 Oct 2013 13:35:10 -0400 Message-ID: Subject: Re: [rfc] removing the NDISulator To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" , freebsd-current 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, 23 Oct 2013 17:35:41 -0000 On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote: > If there are drivers that people absolutely need fixed then they should > stand up and say "hey, I really would like X to work better!" and then > follow it up with some encouraging incentives. Right now the NDISulator > lets people work _around_ this by having something that kind of works for > them but it doesn't improve our general driver / stack ecosystems. I doubt most people prefer to use the ndisulator over a native driver. However, many people don't have the skills, time, or money to provide the incentives you are talking about. At this point ndisulator provides a means to an end: working wireless and it isn't causing significant strain on the project in terms of development effort. Our end users are not always developers and I think removing this feature will hurt more than it will help. -- Eitan Adler From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 18:09:14 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 7D961BEC; Wed, 23 Oct 2013 18:09:14 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 67045223E; Wed, 23 Oct 2013 18:09:14 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 093A61A3CC9; Wed, 23 Oct 2013 11:09:14 -0700 (PDT) Message-ID: <526810DB.20705@mu.org> Date: Wed, 23 Oct 2013 11:09:31 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: John Baldwin , freebsd-current@freebsd.org Subject: Re: [rfc] removing the NDISulator References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <201310231023.32351.jhb@freebsd.org> In-Reply-To: <201310231023.32351.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 18:09:14 -0000 On 10/23/13 7:23 AM, John Baldwin wrote: > On Monday, October 21, 2013 6:29:24 pm Adrian Chadd wrote: >> The NDISulator is a crutch from a time when there wasn't _any_ real >> alternative. >> >> There are plenty of alternatives now. What's lacking is desire and >> person-power. But the datasheets are there, or the vendor code has been >> released, or there's linux/otherbsd drivers. >> >> Leaving it in there is just delaying the inevitable - drivers need to be >> fixed, ported, or reverse engineered. >> >> This is going to upset users in the same way that eliminating any other >> transition/sideways compatibility layer upsets users. But as I said, the >> path forward is fixing up the lack of stable drivers, not simply supporting >> some crutch. >> >> If there are drivers that people absolutely need fixed then they should >> stand up and say "hey, I really would like X to work better!" and then >> follow it up with some encouraging incentives. Right now the NDISulator >> lets people work _around_ this by having something that kind of works for >> them but it doesn't improve our general driver / stack ecosystems. > Eh, having taken a stab at porting the bwl blob already, I would strongly > oppose removing NDIS. If you do that I will just stop using my netbook > with a Broadcom part altogether as I wouldn't be able to use it to try to > test bwl changes. The NDIS thing is a bit hackish, but it is quite useful > for a lot of folks. > I have to agree. Deprecation != motivation. -- Alfred Perlstein From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 18:11:30 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 928BAE3A; Wed, 23 Oct 2013 18:11:30 +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 2E8D622CA; Wed, 23 Oct 2013 18:11:30 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id k4so739368qaq.14 for ; Wed, 23 Oct 2013 11:11:29 -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=X0rrZZpORMURQsjA+sf/oq7jS0rSYdoeq6ADpXAngiM=; b=j1+sF7W3rJGCQScHLYQzZtpiVsq9zhIpdJQ+keFV6PNiZwOCU2XXU/hlHlnWAXJ8WC RwX5ZSMA6ltyvmNFd8/9aHaRWc1ETl4U589+zAZz3Y2SfK6Nd5x6bXif9+e2o3hEjlFV Q9dblnoVDO63WlrmFfa5Dy6r7foxrF2lvp1rdaU4epBY52UJGIybEyNkDNPUESGeKI5d hEzm1JUo0KizW5PaetPOxIDcvQnHWSOajbAeZrxhju13NZ0z9P8LxSL+lGK5hvIJWqu/ xJmjSNqdgKm89T0VSXQouKqdKFfGL9+i8apwuZhC1rwb2WP33kCNZbOQJrUxIvxX5fAD XNUg== MIME-Version: 1.0 X-Received: by 10.49.103.161 with SMTP id fx1mr3997476qeb.68.1382551889396; Wed, 23 Oct 2013 11:11:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 11:11:29 -0700 (PDT) In-Reply-To: <526810DB.20705@mu.org> References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <201310231023.32351.jhb@freebsd.org> <526810DB.20705@mu.org> Date: Wed, 23 Oct 2013 11:11:29 -0700 X-Google-Sender-Auth: N_cGOpzUcpqPZheZ4VnvkpjCHnc Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Julian H. Stacey" , freebsd-current , "freebsd-wireless@freebsd.org" , John Baldwin 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, 23 Oct 2013 18:11:30 -0000 On 23 October 2013 11:09, Alfred Perlstein wrote: > Eh, having taken a stab at porting the bwl blob already, I would strongly >> oppose removing NDIS. If you do that I will just stop using my netbook >> with a Broadcom part altogether as I wouldn't be able to use it to try to >> test bwl changes. The NDIS thing is a bit hackish, but it is quite useful >> for a lot of folks. >> >> I have to agree. Deprecation != motivation. I can pull out examples of this not holding true: * all the giant locking in drivers * all the giant locking in VFS People did pop up and claim ownership of things they cared about. Some stuff died, some stuff didn't. There was enough of a motivation by us to kill giant off in these pathways so things could continue to evolve. We didn't leave the GIANT crutch in forever. -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 18:15: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 B6037FA0; Wed, 23 Oct 2013 18:15:28 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 9F60C22F7; Wed, 23 Oct 2013 18:15:28 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 46F5A1A3C20; Wed, 23 Oct 2013 11:15:26 -0700 (PDT) Message-ID: <5268124E.4040906@mu.org> Date: Wed, 23 Oct 2013 11:15:42 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: [rfc] removing the NDISulator References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <201310231023.32351.jhb@freebsd.org> <526810DB.20705@mu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 18:15:28 -0000 On 10/23/13 11:11 AM, Adrian Chadd wrote: > On 23 October 2013 11:09, Alfred Perlstein wrote: > > >> Eh, having taken a stab at porting the bwl blob already, I would strongly >>> oppose removing NDIS. If you do that I will just stop using my netbook >>> with a Broadcom part altogether as I wouldn't be able to use it to try to >>> test bwl changes. The NDIS thing is a bit hackish, but it is quite useful >>> for a lot of folks. >>> >>> I have to agree. Deprecation != motivation. > > I can pull out examples of this not holding true: > > * all the giant locking in drivers > * all the giant locking in VFS > > People did pop up and claim ownership of things they cared about. Some > stuff died, some stuff didn't. There was enough of a motivation by us to > kill giant off in these pathways so things could continue to evolve. We > didn't leave the GIANT crutch in forever. > > Sure, however those drivers and vfs systems were not sustainable and holding the kernel back. What part of the NDISulator actually holds the system back? I'm saying that it seems as if it was conjecture rather than a need. Is the NDISulator giant locked? Also why the interest in writing drivers so much? Being able to leverage other platform drivers is pretty neat and saves us a ton of work. -- Alfred Perlstein From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 18:28:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1CA1069D; Wed, 23 Oct 2013 18:28:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BD8A123A2; Wed, 23 Oct 2013 18:28:23 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id i13so752624qae.1 for ; Wed, 23 Oct 2013 11:28:22 -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=ThiEjRZ29rm9UddR2Yl63Z3pFUYh97xPpEKArXt4yE8=; b=0yh2npoCvd715zfOckRRp0+zOl8sBInUwN9630uhe6lUa3kS5O5LiOapLXdVJfpxRj BJd+tcZ2bB+ZYmRK/wHM4PnENIypP6j7tePmZRx4iQ2c9DkMvpepfq4e7+wkLx4DbIIm tqWLCEVdFgCVUE+SBijnUmWXrEAxvj+lM75OqUtJruTzLoSqBeusav3HxphGCNc8ijPa 3bGqcebHcEdzk+2fB96uGDfGPOJQSR41gHMA3SY7qdq9RpXSbsT6N3JNjrWXAujAJY5p U4rT74/WkFMJUeWBf0syaCuvbb5bE+e/PvgWlUjRMPjUYDyViiz1rRqssB9cIvjfiUlg KJVA== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr5857845qad.76.1382552902777; Wed, 23 Oct 2013 11:28:22 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 11:28:22 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 11:28:22 -0700 (PDT) In-Reply-To: <5268124E.4040906@mu.org> References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <201310231023.32351.jhb@freebsd.org> <526810DB.20705@mu.org> <5268124E.4040906@mu.org> Date: Wed, 23 Oct 2013 11:28:22 -0700 X-Google-Sender-Auth: PTIL4LuzBqKRWiWHpq_Bbj_LT8w Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Julian H. Stacey" , freebsd-wireless@freebsd.org, freebsd-current 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, 23 Oct 2013 18:28:24 -0000 Because the Linux stuff is mostly very GPL. Adrian On Oct 23, 2013 2:15 PM, "Alfred Perlstein" wrote: > On 10/23/13 11:11 AM, Adrian Chadd wrote: > >> On 23 October 2013 11:09, Alfred Perlstein wrote: >> >> >> Eh, having taken a stab at porting the bwl blob already, I would strongly >>> >>>> oppose removing NDIS. If you do that I will just stop using my netbook >>>> with a Broadcom part altogether as I wouldn't be able to use it to try >>>> to >>>> test bwl changes. The NDIS thing is a bit hackish, but it is quite >>>> useful >>>> for a lot of folks. >>>> >>>> I have to agree. Deprecation != motivation. >>>> >>> >> I can pull out examples of this not holding true: >> >> * all the giant locking in drivers >> * all the giant locking in VFS >> >> People did pop up and claim ownership of things they cared about. Some >> stuff died, some stuff didn't. There was enough of a motivation by us to >> kill giant off in these pathways so things could continue to evolve. We >> didn't leave the GIANT crutch in forever. >> >> >> Sure, however those drivers and vfs systems were not sustainable and > holding the kernel back. > > What part of the NDISulator actually holds the system back? I'm saying > that it seems as if it was conjecture rather than a need. Is the > NDISulator giant locked? > > Also why the interest in writing drivers so much? Being able to leverage > other platform drivers is pretty neat and saves us a ton of work. > > -- > Alfred Perlstein > > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 18:40:59 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 BF80CF37; Wed, 23 Oct 2013 18:40:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 975BC2468; Wed, 23 Oct 2013 18:40:59 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2D18EB93B; Wed, 23 Oct 2013 14:40:56 -0400 (EDT) From: John Baldwin To: Adrian Chadd Subject: Re: [rfc] removing the NDISulator Date: Wed, 23 Oct 2013 14:27:16 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <5265878B.1050809@yandex.ru> <526810DB.20705@mu.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201310231427.16812.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 23 Oct 2013 14:40:56 -0400 (EDT) Cc: "Julian H. Stacey" , Alfred Perlstein , "freebsd-wireless@freebsd.org" , freebsd-current 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, 23 Oct 2013 18:40:59 -0000 On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote: > On 23 October 2013 11:09, Alfred Perlstein wrote: > > > > Eh, having taken a stab at porting the bwl blob already, I would strongly > >> oppose removing NDIS. If you do that I will just stop using my netbook > >> with a Broadcom part altogether as I wouldn't be able to use it to try to > >> test bwl changes. The NDIS thing is a bit hackish, but it is quite useful > >> for a lot of folks. > >> > >> I have to agree. Deprecation != motivation. > > > I can pull out examples of this not holding true: > > * all the giant locking in drivers > * all the giant locking in VFS > > People did pop up and claim ownership of things they cared about. Some > stuff died, some stuff didn't. There was enough of a motivation by us to > kill giant off in these pathways so things could continue to evolve. We > didn't leave the GIANT crutch in forever. Giant isn't dead yet. :) (And I've done a lot of the de-Gianting FWIW.) I don't consider ndis in the same camp. Often times there are vendors where datasheets, etc. are not obtainable, but a foo.sys + foo.inf is. -- John Baldwin From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 18:41: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 72E3A242; Wed, 23 Oct 2013 18:41:58 +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 0E5AC2482; Wed, 23 Oct 2013 18:41:57 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id i13so4477580qae.9 for ; Wed, 23 Oct 2013 11:41:57 -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=AxycB3RJW5Cd4IUIveRtCyoo5g5S1IaTwr61nrDwh20=; b=MSCFQkQn4VwdqUdeCoFjBdjpuMzf1Ofam76MBk+z1wpM43CzjS6gQrwcKNmrPoC5NU aMmoeBzuFnJpNaqQeRFHc/bxLNfu37J8tTDThyOcyqJCF7o029ac3zFl4hxk0wTSKpx/ +2Spb5uvdmB+jkCQ7+B4k5crJhKMBhvh//T/B3rIwADM5yhd8Nhwh0ny+F+pAPAwUZTr rE6ckn2w5+DxHhvDA0vBgCT8FoEBnNe5ghu3khIhE9uLNAa0ub2ikqhiJ7vW5HNxuqxa DlPX9Ir5xPZH7U+DymhMlJ9OvsKrvaYbdOnvhCKxfu+KkKVTs1RadBa/Kjzfw41kwIAf +Ldg== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr5980820qai.74.1382553717092; Wed, 23 Oct 2013 11:41:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 11:41:57 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 11:41:57 -0700 (PDT) In-Reply-To: <201310231427.16812.jhb@freebsd.org> References: <5265878B.1050809@yandex.ru> <526810DB.20705@mu.org> <201310231427.16812.jhb@freebsd.org> Date: Wed, 23 Oct 2013 11:41:57 -0700 X-Google-Sender-Auth: PSUlcbmldlLODHi9w1mecQWBsu0 Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Julian H. Stacey" , Alfred Perlstein , "freebsd-wireless@freebsd.org" , freebsd-current 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, 23 Oct 2013 18:41:58 -0000 And the link momentum is strong now. There's driver source. Adrian On Oct 23, 2013 2:41 PM, "John Baldwin" wrote: > On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote: > > On 23 October 2013 11:09, Alfred Perlstein wrote: > > > > > > > Eh, having taken a stab at porting the bwl blob already, I would > strongly > > >> oppose removing NDIS. If you do that I will just stop using my > netbook > > >> with a Broadcom part altogether as I wouldn't be able to use it to > try to > > >> test bwl changes. The NDIS thing is a bit hackish, but it is quite > useful > > >> for a lot of folks. > > >> > > >> I have to agree. Deprecation != motivation. > > > > > > I can pull out examples of this not holding true: > > > > * all the giant locking in drivers > > * all the giant locking in VFS > > > > People did pop up and claim ownership of things they cared about. Some > > stuff died, some stuff didn't. There was enough of a motivation by us to > > kill giant off in these pathways so things could continue to evolve. We > > didn't leave the GIANT crutch in forever. > > Giant isn't dead yet. :) (And I've done a lot of the de-Gianting FWIW.) > > I don't consider ndis in the same camp. Often times there are vendors > where > datasheets, etc. are not obtainable, but a foo.sys + foo.inf is. > > -- > John Baldwin > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 19:51:25 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 0FC5024D; Wed, 23 Oct 2013 19:51:25 +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 B14AA2BCC; Wed, 23 Oct 2013 19:51:24 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id k18so780774qcv.10 for ; Wed, 23 Oct 2013 12:51:23 -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=UxpzX6vbVBf75B0zRLq+T6Vv58N2D+Fn2+pMrBno7Dk=; b=vmG7RlKJrWhc08VgiXzBsorZxngi/mHR+TVLwoc2Z8BQSVA3XeUulHxIU/cM3zr+I5 HV97boW/+HuEfvh5NwIxQsHFkpHhBfzL/yrRjK30CZ50dudtC9JctyLWvtM5ROMjlaMl zw6bOYI/+q5jbHx97x0VPNRm7/ihTqi3ae+CgtMY8y6eO8fJWk8Pnh8OH2NPC8LZjSjJ odFf9OVNgoaSYBhjfLgwchxUtW4H8YjdzTDvXypalULav3qoEL2uppgRfuJPAd4POJ9t x3jwgh7c5bagc3ZyMh50ZZufN7CLRTqtgf6s/neZNVaVVJpagihhK7o9qo/nm+zya5Hs 4Nng== MIME-Version: 1.0 X-Received: by 10.49.62.3 with SMTP id u3mr4619583qer.6.1382557883752; Wed, 23 Oct 2013 12:51:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 12:51:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Oct 2013 12:51:23 -0700 X-Google-Sender-Auth: OhMTojlssnnIqRfvD4U-PPlbNrs Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: Adrian Chadd To: claudiu vasadi , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@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, 23 Oct 2013 19:51:25 -0000 Hi, Please try this: http://people.freebsd.org/~adrian/ath/20131023-net80211-txmgt-locking-2.diff It implements what I think is the mostly-right fix: * remove the node reference in the callout, it's actually not freaking needed! * grab the ic lock when doing the timeout callout, ensuring consistency * expose ieee80211_new_state_locked(), as a few places will already hold the ic lock when wanting to update state Please try it out and let me know if it fixes your panics. Thanks! -adrian On 22 October 2013 07:28, claudiu vasadi wrote: > Hi everyone, > > I have a Lenovo Thinkpad T420s with Intel core i7 @ 2.70GHz, 8GB RAM, Intel > SSD 160GB and iwn0: mem > 0xf4200000-0xf4201fff irq 17 at device 0.0 on pci3 > > Today, while connecting to different AP's, I noticed at one point that I > was not getting an IP although the wifi card was associated. Within > "wifimgr", I did a "Save and Reconnect" and then got a core dump. > > Bellow, the bt: > > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xffffff801e5f7000 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80a10431 > stack pointer = 0x28:0xffffff8000276980 > frame pointer = 0x28:0xffffff8000276a20 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi4: clock) > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff80948a06 at kdb_backtrace+0x66 > #1 0xffffffff8090e50e at panic+0x1ce > #2 0xffffffff80cf3440 at trap_fatal+0x290 > #3 0xffffffff80cf37a1 at trap_pfault+0x211 > #4 0xffffffff80cf3d54 at trap+0x344 > #5 0xffffffff80cdd093 at calltrap+0x8 > #6 0xffffffff808dfddd at intr_event_execute_handlers+0xfd > #7 0xffffffff808e15cd at ithread_loop+0x9d > #8 0xffffffff808dc82f at fork_exit+0x11f > #9 0xffffffff80cdd5be at fork_trampoline+0xe > Uptime: 8h20m28s > Dumping 952 out of 8106 MB:..2% (CTRL-C to abort) (CTRL-C to abort) > (CTRL-C to abort) (CTRL-C to abort) ..11% (CTRL-C to abort) (CTRL-C to > abort) ..21%..31% (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) > (CTRL-C to abort) (CTRL-C to abort) ..41% (CTRL-C to abort) (CTRL-C to > abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to > abort) (CTRL-C to abort) (CTRL-C to abort) ..51% (CTRL-C to abort) > (CTRL-C to abort) ..61% (CTRL-C to abort) ..71% (CTRL-C to abort) > ..81%..91% > > Reading symbols from /boot/kernel/zfs.ko...Reading symbols from > /boot-mount/boot/kernel/zfs.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/zfs.ko > Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from > /boot-mount/boot/kernel/opensolaris.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/opensolaris.ko > Reading symbols from /boot/kernel/geom_eli.ko...Reading symbols from > /boot-mount/boot/kernel/geom_eli.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/geom_eli.ko > Reading symbols from /boot/kernel/crypto.ko...Reading symbols from > /boot-mount/boot/kernel/crypto.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/crypto.ko > Reading symbols from /boot/kernel/linux.ko...Reading symbols from > /boot-mount/boot/kernel/linux.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/linux.ko > Reading symbols from /boot/kernel/drm.ko...Reading symbols from > /boot-mount/boot/kernel/drm.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/drm.ko > Reading symbols from /boot/modules/nvidia.ko...done. > Loaded symbols for /boot/modules/nvidia.ko > Reading symbols from /boot/kernel/mmc.ko...Reading symbols from > /boot-mount/boot/kernel/mmc.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/mmc.ko > Reading symbols from /boot/kernel/mmcsd.ko...Reading symbols from > /boot-mount/boot/kernel/mmcsd.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/mmcsd.ko > Reading symbols from /boot/kernel/acpi_call.ko...done. > Loaded symbols for /boot/kernel/acpi_call.ko > Reading symbols from /boot/kernel/umodem.ko...Reading symbols from > /boot-mount/boot/kernel/umodem.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/umodem.ko > Reading symbols from /boot/modules/vboxnetflt.ko...done. > Loaded symbols for /boot/modules/vboxnetflt.ko > Reading symbols from /boot/modules/vboxdrv.ko...done. > Loaded symbols for /boot/modules/vboxdrv.ko > Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from > /boot-mount/boot/kernel/netgraph.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/netgraph.ko > Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from > /boot-mount/boot/kernel/ng_ether.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/ng_ether.ko > Reading symbols from /boot/modules/vboxnetadp.ko...done. > Loaded symbols for /boot/modules/vboxnetadp.ko > #0 doadump (textdump=) at pcpu.h:234 > 234 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:234 > #1 0xffffffff8090dfe6 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:449 > #2 0xffffffff8090e4e7 in panic (fmt=0x1
) at > /usr/src/sys/kern/kern_shutdown.c:637 > #3 0xffffffff80cf3440 in trap_fatal (frame=0xc, eva=) > at /usr/src/sys/amd64/amd64/trap.c:879 > #4 0xffffffff80cf37a1 in trap_pfault (frame=0xffffff80002768d0, > usermode=0) at /usr/src/sys/amd64/amd64/trap.c:795 > #5 0xffffffff80cf3d54 in trap (frame=0xffffff80002768d0) at > /usr/src/sys/amd64/amd64/trap.c:463 > #6 0xffffffff80cdd093 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:232 > #7 0xffffffff80a10431 in ieee80211_tx_mgt_timeout (arg=0xffffff801e5f7000) > at /usr/src/sys/net80211/ieee80211_output.c:2487 > #8 0xffffffff809246e8 in softclock (arg=) at > /usr/src/sys/kern/kern_timeout.c:518 > #9 0xffffffff808dfddd in intr_event_execute_handlers (p= out>, ie=0xfffffe0007221b00) > at /usr/src/sys/kern/kern_intr.c:1272 > #10 0xffffffff808e15cd in ithread_loop (arg=0xfffffe0007209460) at > /usr/src/sys/kern/kern_intr.c:1285 > #11 0xffffffff808dc82f in fork_exit (callout=0xffffffff808e1530 > , arg=0xfffffe0007209460, > frame=0xffffff8000276b00) at /usr/src/sys/kern/kern_fork.c:990 > #12 0xffffffff80cdd5be in fork_trampoline () at > /usr/src/sys/amd64/amd64/exception.S:606 > #13 0x0000000000000000 in ?? () > > > One thing to keep in mind is that since I started using geli+ZFS (installed > with PC-BSD 9.1 cd), I always got "Cannot reset interface wlan0 - exit > status 1" with "wifimgr" whichever action i did (ex: reconect, rescan, > up/down,etc). > > > I would appreciate some help in debugging this. > > > -- > Best regards, > Claudiu Vasadi > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 20:10:48 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 0AC119DA; Wed, 23 Oct 2013 20:10:48 +0000 (UTC) (envelope-from claudiu.vasadi@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B9ECE2CF0; Wed, 23 Oct 2013 20:10:47 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id as1so2275731iec.13 for ; Wed, 23 Oct 2013 13:10:47 -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=H64GEOoLUEbLFohtulDjwlTdi+vUPUmL2/2qADFQRjs=; b=jNiSLOuEQNUSvVnz9TfUBcGulSLHag/jG2hQlCt6eT7jPi6fwkyDnBDI6JQ59SYlzO riHAoxQrxDErVNOQtSbeU6flR5/VhkUHYuSn0GZsztHj9JUMfFcwxaVmHgFjHcFYzLta luM//lb8AEikp886Yzd4Xzq/NNRCoDoWIfSNvwbGLpt45XDjc5nuH/P9QLV0R4aIo7i6 ft32GiLSv7S6qWGQnO7oMYdDwkGxUQeE8EIzDCzoaHgxOmsUfG1aG0DkZR1Gr0uka0F5 68ScQWv+yRFA3rpvh813uJoVkuyQ/v5dMjzhAzf4GCcivyayAFHV7cMLV6DneetXSoWB M8MQ== MIME-Version: 1.0 X-Received: by 10.50.122.40 with SMTP id lp8mr1837693igb.24.1382559047120; Wed, 23 Oct 2013 13:10:47 -0700 (PDT) Received: by 10.64.134.169 with HTTP; Wed, 23 Oct 2013 13:10:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Oct 2013 22:10:46 +0200 Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: claudiu vasadi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 20:10:48 -0000 Hi, Still getting the "Cannot reset interface wlan0 - exit status 1" in wifimgr but no crash yet. Will keep trying :D On Wed, Oct 23, 2013 at 9:51 PM, Adrian Chadd wrote: > Hi, > > Please try this: > > > http://people.freebsd.org/~adrian/ath/20131023-net80211-txmgt-locking-2.diff > > It implements what I think is the mostly-right fix: > > * remove the node reference in the callout, it's actually not freaking > needed! > * grab the ic lock when doing the timeout callout, ensuring consistency > * expose ieee80211_new_state_locked(), as a few places will already hold > the ic lock when wanting to update state > > Please try it out and let me know if it fixes your panics. > > Thanks! > > > > -adrian > > > > On 22 October 2013 07:28, claudiu vasadi wrote: > >> Hi everyone, >> >> I have a Lenovo Thinkpad T420s with Intel core i7 @ 2.70GHz, 8GB RAM, >> Intel >> SSD 160GB and iwn0: mem >> 0xf4200000-0xf4201fff irq 17 at device 0.0 on pci3 >> >> Today, while connecting to different AP's, I noticed at one point that I >> was not getting an IP although the wifi card was associated. Within >> "wifimgr", I did a "Save and Reconnect" and then got a core dump. >> >> Bellow, the bt: >> >> >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you >> are >> welcome to change it and/or distribute copies of it under certain >> conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for >> details. >> This GDB was configured as "amd64-marcel-freebsd"... >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0xffffff801e5f7000 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff80a10431 >> stack pointer = 0x28:0xffffff8000276980 >> frame pointer = 0x28:0xffffff8000276a20 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 12 (swi4: clock) >> trap number = 12 >> panic: page fault >> cpuid = 0 >> KDB: stack backtrace: >> #0 0xffffffff80948a06 at kdb_backtrace+0x66 >> #1 0xffffffff8090e50e at panic+0x1ce >> #2 0xffffffff80cf3440 at trap_fatal+0x290 >> #3 0xffffffff80cf37a1 at trap_pfault+0x211 >> #4 0xffffffff80cf3d54 at trap+0x344 >> #5 0xffffffff80cdd093 at calltrap+0x8 >> #6 0xffffffff808dfddd at intr_event_execute_handlers+0xfd >> #7 0xffffffff808e15cd at ithread_loop+0x9d >> #8 0xffffffff808dc82f at fork_exit+0x11f >> #9 0xffffffff80cdd5be at fork_trampoline+0xe >> Uptime: 8h20m28s >> Dumping 952 out of 8106 MB:..2% (CTRL-C to abort) (CTRL-C to abort) >> (CTRL-C to abort) (CTRL-C to abort) ..11% (CTRL-C to abort) (CTRL-C to >> abort) ..21%..31% (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) >> (CTRL-C to abort) (CTRL-C to abort) ..41% (CTRL-C to abort) (CTRL-C to >> abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C >> to >> abort) (CTRL-C to abort) (CTRL-C to abort) ..51% (CTRL-C to abort) >> (CTRL-C to abort) ..61% (CTRL-C to abort) ..71% (CTRL-C to abort) >> ..81%..91% >> >> Reading symbols from /boot/kernel/zfs.ko...Reading symbols from >> /boot-mount/boot/kernel/zfs.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/zfs.ko >> Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from >> /boot-mount/boot/kernel/opensolaris.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/opensolaris.ko >> Reading symbols from /boot/kernel/geom_eli.ko...Reading symbols from >> /boot-mount/boot/kernel/geom_eli.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/geom_eli.ko >> Reading symbols from /boot/kernel/crypto.ko...Reading symbols from >> /boot-mount/boot/kernel/crypto.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/crypto.ko >> Reading symbols from /boot/kernel/linux.ko...Reading symbols from >> /boot-mount/boot/kernel/linux.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/linux.ko >> Reading symbols from /boot/kernel/drm.ko...Reading symbols from >> /boot-mount/boot/kernel/drm.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/drm.ko >> Reading symbols from /boot/modules/nvidia.ko...done. >> Loaded symbols for /boot/modules/nvidia.ko >> Reading symbols from /boot/kernel/mmc.ko...Reading symbols from >> /boot-mount/boot/kernel/mmc.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/mmc.ko >> Reading symbols from /boot/kernel/mmcsd.ko...Reading symbols from >> /boot-mount/boot/kernel/mmcsd.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/mmcsd.ko >> Reading symbols from /boot/kernel/acpi_call.ko...done. >> Loaded symbols for /boot/kernel/acpi_call.ko >> Reading symbols from /boot/kernel/umodem.ko...Reading symbols from >> /boot-mount/boot/kernel/umodem.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/umodem.ko >> Reading symbols from /boot/modules/vboxnetflt.ko...done. >> Loaded symbols for /boot/modules/vboxnetflt.ko >> Reading symbols from /boot/modules/vboxdrv.ko...done. >> Loaded symbols for /boot/modules/vboxdrv.ko >> Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from >> /boot-mount/boot/kernel/netgraph.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/netgraph.ko >> Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from >> /boot-mount/boot/kernel/ng_ether.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/ng_ether.ko >> Reading symbols from /boot/modules/vboxnetadp.ko...done. >> Loaded symbols for /boot/modules/vboxnetadp.ko >> #0 doadump (textdump=) at pcpu.h:234 >> 234 pcpu.h: No such file or directory. >> in pcpu.h >> (kgdb) bt >> #0 doadump (textdump=) at pcpu.h:234 >> #1 0xffffffff8090dfe6 in kern_reboot (howto=260) at >> /usr/src/sys/kern/kern_shutdown.c:449 >> #2 0xffffffff8090e4e7 in panic (fmt=0x1
) at >> /usr/src/sys/kern/kern_shutdown.c:637 >> #3 0xffffffff80cf3440 in trap_fatal (frame=0xc, eva=> out>) >> at /usr/src/sys/amd64/amd64/trap.c:879 >> #4 0xffffffff80cf37a1 in trap_pfault (frame=0xffffff80002768d0, >> usermode=0) at /usr/src/sys/amd64/amd64/trap.c:795 >> #5 0xffffffff80cf3d54 in trap (frame=0xffffff80002768d0) at >> /usr/src/sys/amd64/amd64/trap.c:463 >> #6 0xffffffff80cdd093 in calltrap () at >> /usr/src/sys/amd64/amd64/exception.S:232 >> #7 0xffffffff80a10431 in ieee80211_tx_mgt_timeout >> (arg=0xffffff801e5f7000) >> at /usr/src/sys/net80211/ieee80211_output.c:2487 >> #8 0xffffffff809246e8 in softclock (arg=) at >> /usr/src/sys/kern/kern_timeout.c:518 >> #9 0xffffffff808dfddd in intr_event_execute_handlers (p=> out>, ie=0xfffffe0007221b00) >> at /usr/src/sys/kern/kern_intr.c:1272 >> #10 0xffffffff808e15cd in ithread_loop (arg=0xfffffe0007209460) at >> /usr/src/sys/kern/kern_intr.c:1285 >> #11 0xffffffff808dc82f in fork_exit (callout=0xffffffff808e1530 >> , arg=0xfffffe0007209460, >> frame=0xffffff8000276b00) at /usr/src/sys/kern/kern_fork.c:990 >> #12 0xffffffff80cdd5be in fork_trampoline () at >> /usr/src/sys/amd64/amd64/exception.S:606 >> #13 0x0000000000000000 in ?? () >> >> >> One thing to keep in mind is that since I started using geli+ZFS >> (installed >> with PC-BSD 9.1 cd), I always got "Cannot reset interface wlan0 - exit >> status 1" with "wifimgr" whichever action i did (ex: reconect, rescan, >> up/down,etc). >> >> >> I would appreciate some help in debugging this. >> >> >> -- >> Best regards, >> Claudiu Vasadi >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >> " >> > > -- Best regards, Claudiu Vasadi From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 20:12:06 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 B397FB09; Wed, 23 Oct 2013 20:12:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6176F2D09; Wed, 23 Oct 2013 20:12:06 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id w8so4549751qac.1 for ; Wed, 23 Oct 2013 13:12:05 -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=ptGaPrkKH2ITZuOvN+pDH0mPSk/FVwrhwrS3zW/t/Rk=; b=FXDaZu3o6ewgdKd3nao3CvR7M6GxKnFJBN3l1srVmdGtc7Rqp/+qvqy5vAR6zYwVWg DyglWY43mt+hIf++xUz5fRky8mv7fQJFOUW4pywbRAtBgzWVPxwTVtrLcNIUmBwpUiEn g5xWK5l1yFi5q+bVWMKkQ8/w+KZXa7Bc+pzl2UdISfV4k68rkFT2WkTWAMb8Q9iy/Xt8 5Nlptnj0BPWVoHc8MVSmiYE4tgpDO6voQpmZx8vInYPjgIt9WqeoYO1/VPT+lxloDY9b HUS+o0Ir/97IXSlDugnXhNAC0LjXyvU3FMHXnv5JzmSbT8jL6xTMTOmmtrQ4VhaABTgz SjCg== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr6500239qai.74.1382559125416; Wed, 23 Oct 2013 13:12:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 13:12:05 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Oct 2013 13:12:05 -0700 X-Google-Sender-Auth: 6ZbBgbIeEKK4TEPHC5R0axUaAOc Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: Adrian Chadd To: claudiu vasadi Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 20:12:06 -0000 On 23 October 2013 13:10, claudiu vasadi wrote: > Hi, > > Still getting the "Cannot reset interface wlan0 - exit status 1" in > wifimgr but no crash yet. Will keep trying :D > I have no idea about that. It's likely there's some net80211/iwn bug(s) but I don't use wifimgr so I don't know what it's doing. For that I'd bug the wifimgr people in PCBSD. they can always file bug reports with me :) Thanks, -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 20:14:19 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 DC949D27; Wed, 23 Oct 2013 20:14:18 +0000 (UTC) (envelope-from claudiu.vasadi@gmail.com) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 982312D3A; Wed, 23 Oct 2013 20:14:18 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id tp5so2250648ieb.16 for ; Wed, 23 Oct 2013 13:14:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4SHMoPUlD4awTCckXGIQmib87gYFYIdoXi5b0NzFynQ=; b=o/0zqZYZErvbRaP8ACA9sF86apSA9il4BXxUIbCk2/AQGjipf4+I++yn3X5WUiNz5f w1JulIg7iZNUIee/PhFTf7PfhyN9sTLUUk6thfVe7Jmu70XHH6gXLOvDbiOaYrBH/po/ m2mZGYmtUYNm5Y/OyaOT+yTpcin6rrCk2uOj0MUJhJkxae1k7jmC2Hbj7X8Xq4yZsQPy it2d+jZl93TlOxPQi9PnKXfB86b7NAwzkIVIU2hQhg4wWpGqu3KfzdrT2EBIBnnFFFS6 S/JyI8sucexNGDKSdQgBqPGfds2y2kNfr5+zpLQCVlOuCzRzBvwdanNfsO4dS9QO+QU/ ToTg== MIME-Version: 1.0 X-Received: by 10.43.57.79 with SMTP id wf15mr1595191icb.14.1382559257886; Wed, 23 Oct 2013 13:14:17 -0700 (PDT) Received: by 10.64.134.169 with HTTP; Wed, 23 Oct 2013 13:14:17 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Oct 2013 22:14:17 +0200 Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: claudiu vasadi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 20:14:19 -0000 Understood. Will do so. On Wed, Oct 23, 2013 at 10:12 PM, Adrian Chadd wrote: > > > > On 23 October 2013 13:10, claudiu vasadi wrote: > >> Hi, >> >> Still getting the "Cannot reset interface wlan0 - exit status 1" in >> wifimgr but no crash yet. Will keep trying :D >> > > I have no idea about that. It's likely there's some net80211/iwn bug(s) > but I don't use wifimgr so I don't know what it's doing. > > For that I'd bug the wifimgr people in PCBSD. they can always file bug > reports with me :) > > Thanks, > > > > -adrian > > -- Best regards, Claudiu Vasadi From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 20:39:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E2ED179E; Wed, 23 Oct 2013 20:39:18 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9F92D2EDD; Wed, 23 Oct 2013 20:39:18 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r9NKdCdC095970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Oct 2013 13:39:12 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r9NKdCf7095969; Wed, 23 Oct 2013 13:39:12 -0700 (PDT) (envelope-from jmg) Date: Wed, 23 Oct 2013 13:39:12 -0700 From: John-Mark Gurney To: Adrian Chadd Subject: Re: [rfc] removing the NDISulator Message-ID: <20131023203912.GD94140@funkthat.com> Mail-Followup-To: Adrian Chadd , freebsd-current , "freebsd-wireless@freebsd.org" References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <201310231023.32351.jhb@freebsd.org> <526810DB.20705@mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 23 Oct 2013 13:39:12 -0700 (PDT) Cc: freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 20:39:19 -0000 Adrian Chadd wrote this message on Wed, Oct 23, 2013 at 11:11 -0700: > On 23 October 2013 11:09, Alfred Perlstein wrote: > > > Eh, having taken a stab at porting the bwl blob already, I would strongly > >> oppose removing NDIS. If you do that I will just stop using my netbook > >> with a Broadcom part altogether as I wouldn't be able to use it to try to > >> test bwl changes. The NDIS thing is a bit hackish, but it is quite useful > >> for a lot of folks. > >> > >> I have to agree. Deprecation != motivation. > > > I can pull out examples of this not holding true: > > * all the giant locking in drivers > * all the giant locking in VFS > > People did pop up and claim ownership of things they cared about. Some > stuff died, some stuff didn't. There was enough of a motivation by us to > kill giant off in these pathways so things could continue to evolve. We > didn't leave the GIANT crutch in forever. I'd say that locking a drive is a LOT easier than writing a driver from scratch, esspecially if you don't have the specs.. This of course coming from experience with both... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 21:37:23 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 EEF3E28F for ; Wed, 23 Oct 2013 21:37:23 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id AC53622D9 for ; Wed, 23 Oct 2013 21:37:23 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:32601] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id D7/4B-19454-29148625; Wed, 23 Oct 2013 21:37:22 +0000 Date: Wed, 23 Oct 2013 21:37:22 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: Subject: Re: [rfc] removing the NDISulator X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Cc: freebsd-current@freebsd.org, claudiu vasadi 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, 23 Oct 2013 21:37:24 -0000 > > On 23 October 2013 13:10, claudiu vasadi wrote: > > Hi, > > Still getting the "Cannot reset interface wlan0 - exit status 1" in > > wifimgr but no crash yet. Will keep trying :D > I have no idea about that. It's likely there's some net80211/iwn bug(s) but > I don't use wifimgr so I don't know what it's doing. > For that I'd bug the wifimgr people in PCBSD. they can always file bug > reports with me :) > Thanks, > -adrian I don't have wifimgr either, can't even install it until I get wifi set up. Does wifimgr have more functionality than wpa_cli? Why would some drivers not be ndisulatable/ndiswrappable? Would that be because the resulting driver would fail, or because of the lack of .inf and .sys files in Windows driver? Tom From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 21:43: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 9370A68A; Wed, 23 Oct 2013 21:43:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x231.google.com (mail-qe0-x231.google.com [IPv6:2607:f8b0:400d:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 40EA72358; Wed, 23 Oct 2013 21:43:08 +0000 (UTC) Received: by mail-qe0-f49.google.com with SMTP id a11so898932qen.22 for ; Wed, 23 Oct 2013 14:43:07 -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=z6oPy/nZHiOQwJ81bZAt/T/RJ+5unsxyBXhQ6jHQe/A=; b=fr2uwVKwGMI1nnSVp+MvgNXUJn7zUjiDIMY7hDoV5xaT2/B8L6+P9/LOoYF/iqUu4h YfeOsRuhW4hSJ/LZFVFOK1aZn5UT4hhK07ymaiNwSKN0MgA30KaiBxRmQkgE7Q/rEkVR Jt1mgTgPsbSa8sy96fUKmgxxhr5WJ4LmPE0gMMN6eqv46CbOoVlt9IUDCZ7DXYrfTVRA zZrnAv2Th0E0Vgos03qq675aevLJuo+Ag2cu/WFKVHreRC0nUIBMmN6PfYCkVkpdY1S3 O+etQrxwo0KDAFPpOLVwY+OnEcbCjkIVVv5lVECtYC6aI5OIiHgQDQdpW1IVL+Tzowjd 4ZyA== MIME-Version: 1.0 X-Received: by 10.224.51.131 with SMTP id d3mr15096qag.0.1382564587437; Wed, 23 Oct 2013 14:43:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 14:43:07 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Oct 2013 14:43:07 -0700 X-Google-Sender-Auth: flaPberON1BtbAaDdZBV-Ehg4OI Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" , claudiu vasadi , freebsd-current 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, 23 Oct 2013 21:43:08 -0000 Hi, The later driver model isn't supported by ndisulator. We'd have to implement all the newer NDIS stuff for wifi and ethernet. In the later NDIS layer the Microsoft Wireless Services implement a bunch of stuff that used to be up to the driver. Ie, the driver just exposed an ethernet "device" with some extra bits for wifi. Ie, the whole stack runs in the driver. That has changed. -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 22:31:52 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 E13CC681; Wed, 23 Oct 2013 22:31:52 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) (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 5E5212600; Wed, 23 Oct 2013 22:31:52 +0000 (UTC) Received: from vincemacbook.unsane.co.uk (vincemacbook.unsane.co.uk [10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.7/8.14.6) with ESMTP id r9NMVaTE061865 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 23 Oct 2013 23:31:38 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <52684E48.20709@unsane.co.uk> Date: Wed, 23 Oct 2013 23:31:36 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Eitan Adler , Adrian Chadd Subject: Re: [rfc] removing the NDISulator References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" , freebsd-current 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, 23 Oct 2013 22:31:53 -0000 On 23/10/2013 18:35, Eitan Adler wrote: > On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote: >> If there are drivers that people absolutely need fixed then they should >> stand up and say "hey, I really would like X to work better!" and then >> follow it up with some encouraging incentives. Right now the NDISulator >> lets people work _around_ this by having something that kind of works for >> them but it doesn't improve our general driver / stack ecosystems. > I doubt most people prefer to use the ndisulator over a native driver. > However, many people don't have the skills, time, or money to provide > the incentives you are talking about. At this point ndisulator > provides a means to an end: working wireless and it isn't causing > significant strain on the project in terms of development effort. > > Our end users are not always developers and I think removing this > feature will hurt more than it will help. > > As an end user, the main issue I have is that according to the manpage it supports ndis 5.1 According to http://en.wikipedia.org/wiki/Network_Driver_Interface_Specification this is the version supported by Windows XP , Server 2003 , Windows CE 4.x, 5.0, 6.0 As you might guess most new devices wont be coming with drivers for XP, so does this mean I wont be able to use drivers for a recent windows version (my understanding is that it will but happy to learn differently) If this is the case and there is no active development on it, a gradual depreciation over the 10.x series is probably a good idea. If however its likely to support current drivers/devices it does have a place (I've used it once or twice in a pinch.) Vince ^ From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 23:56:34 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 6565A2D5 for ; Wed, 23 Oct 2013 23:56:34 +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 4C25529CA for ; Wed, 23 Oct 2013 23:56:33 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:content-type:date:message-id:mime-version; b=mWrskoiP+V3IMMaZ8owkTBUepUs5ZvwfEz/uKlU8GahbqdLxd0j/PRjZHrXQtE/9Y0ymJ9jDitnF PBWYxojn3oiGnypuVkdyqq4dtepvwCRge8Vqo2thkBNf3PhPzwXV Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1382572587112640.3276255338359; Wed, 23 Oct 2013 16:56:27 -0700 (PDT) Subject: service netif restart [iface] runs a wpa_supplicant twice From: clutton To: freebsd-wireless@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-CfFQPgS3AuOVS/IrdjFg" Date: Thu, 24 Oct 2013 02:56:23 +0300 Message-ID: <1382572583.1862.39.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 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: Wed, 23 Oct 2013 23:56:34 -0000 --=-CfFQPgS3AuOVS/IrdjFg Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=20 network=3D{ ssid=3D"ssid" psk=3D"psk" } 11.0-CURRENT --=-CfFQPgS3AuOVS/IrdjFg 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) iQIcBAABAgAGBQJSaGInAAoJECNkWbjnbjuiTWoP/3LSabkq4FBEm24tL/0q50Oz acKIBWEb++53vMHeyaAojBBKr6udBsJ8X8FKbNCA1bj+aMg894yn7flv1YAkMDmk JQyvv9QOjsOWUr2hb1z8VHhCMWJc35eNpxyqmGUJxFdADBWvqo6O9iY+F4IZ+2Eo OWq/1j20dT1B0UZUyzd3P3NpKrFlECbXCohYrPa74MS5+S3Pweg1Fwz75A+t8MPH 1dM/16Z2SjNuZnxoG9iCtuX3Y28r/PdGgRbqP0DeBmz6WwSx19LAnREGB/E+RmBw btHKCjTYY+BQ37V5BSWgxKPNzCK3HQ0Wk1lV9NUAOKJawv958E2o+RwjcmBv/Myz E7MlfkweH+MLGad0RBf4wDzDU8Bgl/fLZIJ4YgJZZ4HcyD8sJ+CQlpdqfp64OI3L AgE9TQzos/jrq/XINpl53IjpK07ju+OEFOZ0pQijuwliUee1rMQ4BdfwXwvYyFA9 OlBjpCWIN0WwDuN2ijoE0hju64S0HpZle7UOB1TyLt936q2ZzJfNMybdHs5job6G oJha+xZ0TlI2r7E8YzbFp/rXCCPFtX3ISs8tPhmtotELveEQ6PiX/r8Yjks+b+lO foK6iVrwFoihg8KC4Xtwa3a3K1yPDfvwfE6S3mkKkeoLVavGQgDGvp5moAFYlEJa 06pAUhdtAu4TGgiV+CJ0 =O8Xe -----END PGP SIGNATURE----- --=-CfFQPgS3AuOVS/IrdjFg-- From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 23:57:32 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 11053303 for ; Wed, 23 Oct 2013 23:57:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C776B29CF for ; Wed, 23 Oct 2013 23:57:31 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id i7so951864qcq.30 for ; Wed, 23 Oct 2013 16:57:31 -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=PQl54EkC2HokkJ+I9xQq+FsC6uEQH1k8I4iVcgv0KTk=; b=mfVt1SfJyM0eaY3SmuZAC58NEnQ3Vkb3NHHKHdFZDl9hls+4g2rLuE4Sm2YXprq5Q4 +lMZzqxgklSgPp0g8x5JL42ZM5xGAlTsWywfxwCAt/oLbtEIsruIaDM/fjiczPC9XQ3I dPx5kQgcFGzosKqhOdbe7leAgomcrgOTDht7zL2CnK/aR5W8I1r2/2Sc50u8olzJeCiJ JE/0e5+N3KrtvCCumVykMUJMDlgg02BvYeOhVMsdFwW0OsjN1QaSOjAtcubrsIxzDGvI XJgY4kBcXQOQp0B+d4Svu0Og52mfoCNF16t0qnov6b/Vuyyi5do7yfgzOVlVS4lEv0TX esTA== MIME-Version: 1.0 X-Received: by 10.224.167.206 with SMTP id r14mr590197qay.4.1382572651017; Wed, 23 Oct 2013 16:57:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 16:57:30 -0700 (PDT) In-Reply-To: <1382572583.1862.39.camel@eva02.mbsd> References: <1382572583.1862.39.camel@eva02.mbsd> Date: Wed, 23 Oct 2013 16:57:30 -0700 X-Google-Sender-Auth: 5zIi1xYROTeONEJj_FUUs7gZ5z8 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: Wed, 23 Oct 2013 23:57:32 -0000 .. 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=30067 > [wpa_supplicant] SUPPID=30067 > [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="wlan0" > ifconfig_wlan0="WPA DHCP" > ifconfig_em0="DHCP" > ipsec_enable="YES" > > /etc/wpa_supplicant.conf > network={ > ssid="ssid" > psk="psk" > } > > 11.0-CURRENT > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 00:11: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 96840749; Thu, 24 Oct 2013 00:11:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 432612A96; Thu, 24 Oct 2013 00:11:33 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id w8so4672218qac.15 for ; Wed, 23 Oct 2013 17:11: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=ta0WkFyMY8fZKwqf7Z9o7mHbTrJl10hEZoQadQrD/nI=; b=L+PzGL1M7wvJkYKqH4KbO45/idvWyIKFaUbHm2qyxAaUVgM1dJpqPqZa8xTOU4vADO iRJzh06x5tIHSqnL4AHVjQkib9eY6zZiygpJFPkthcEY8yaTjpZg7JXz1EIbtV/9IQDC G3GGDXYDUCK0T2ybtyW/tiPuA7a/P+p9XiS6L9Y24K1cHzqZYVDu1GY5T9TD/xV9JG/J kxuMKQPmfvreDNFQSpN8GkJg3qG4Q1aXfeQYLpOd9mk45pBPoISNSTzkvBX8YSXzbi7/ sYV6Zy49nO5QWxSsggzhZJVe9iHoPbOMyQCzEYifqb7LFgF0xtph71Q8AUU2vJG4lbqt N5zw== MIME-Version: 1.0 X-Received: by 10.49.59.115 with SMTP id y19mr57797qeq.8.1382573492479; Wed, 23 Oct 2013 17:11:32 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 17:11:32 -0700 (PDT) In-Reply-To: <52684E48.20709@unsane.co.uk> References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <52684E48.20709@unsane.co.uk> Date: Wed, 23 Oct 2013 17:11:32 -0700 X-Google-Sender-Auth: -msC0nmGGIVM6ykizCKovh0r254 Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Vincent Hoffman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" , freebsd-current 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: Thu, 24 Oct 2013 00:11:33 -0000 On 23 October 2013 15:31, Vincent Hoffman wrote: > On 23/10/2013 18:35, Eitan Adler wrote: > > On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote: > > If there are drivers that people absolutely need fixed then they should > stand up and say "hey, I really would like X to work better!" and then > follow it up with some encouraging incentives. Right now the NDISulator > lets people work _around_ this by having something that kind of works for > them but it doesn't improve our general driver / stack ecosystems. > > I doubt most people prefer to use the ndisulator over a native driver. > However, many people don't have the skills, time, or money to provide > the incentives you are talking about. At this point ndisulator > provides a means to an end: working wireless and it isn't causing > significant strain on the project in terms of development effort. > > Our end users are not always developers and I think removing this > feature will hurt more than it will help. > > > > As an end user, the main issue I have is that according to the manpage it > supports ndis 5.1 > According to > http://en.wikipedia.org/wiki/Network_Driver_Interface_Specification this > is the version supported by > Windows XP , Server 2003, > Windows CE 4.x, 5.0, 6.0 > > As you might guess most new devices wont be coming with drivers for XP, so > does this mean I wont be able to use drivers for a recent windows version > (my understanding is that it will but happy to learn differently) > If this is the case and there is no active development on it, a gradual > depreciation over the 10.x series is probably a good idea. If however its > likely to support current drivers/devices it does have a place (I've used > it once or twice in a pinch.) > This is why I'd rather us bite the bullet now and deprecate it, versus have it in there and put in the work to upgrade it to handle NDIS 6.x drivers with the Microsoft wireless extensions stuff. -adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 00:43:31 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 4A38C3E3 for ; Thu, 24 Oct 2013 00:43:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0BB802CE1 for ; Thu, 24 Oct 2013 00:43:30 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id s14so1025360qeb.33 for ; Wed, 23 Oct 2013 17:43: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=eXPg32tCmUA5Qudj/m1H5MG/P7XNCkudauuIsJg4Gb4=; b=uAnQGXfj4kIUuoU6i2bWuV9cK0hkQPnX9eYCtXs+d5xmXbrqnnfNfLx4XZf5ItundF DTEx2IxfsU5q+/bexumFYf1BA+48P9P4bExKjvhPiVdC4WJ2XN3cOm9J3TQIU9JPZRN/ Ws8kNpDBehen4X6IzZwsCe8aNuiTc65SUy2R2wEYq2/KkB2G3NpxCUE8jQlfhXuwaELd jJPQ+gcsb3/4CurflrQsWwsV6Pg7RfWC3hjO2zOw0oTYIyIkZogredMEnhTjAB1S0h/q yG2jDiL5emwJxdEM7dtju9wfmtf7IaSFzU2RU6R3lpGtxCZk2+s7xt+VDdKDnHHIxlui qbbw== MIME-Version: 1.0 X-Received: by 10.49.127.179 with SMTP id nh19mr59524qeb.1.1382575410189; Wed, 23 Oct 2013 17:43:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 17:43:30 -0700 (PDT) In-Reply-To: <002701cebc6f$634c0040$29e400c0$@info> References: <002701cebc6f$634c0040$29e400c0$@info> Date: Wed, 23 Oct 2013 17:43:30 -0700 X-Google-Sender-Auth: gmXeZEutfZTS7IGxZtiAopor73k Message-ID: Subject: Re: [IWN] Review From: Adrian Chadd To: Cedric GROSS 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: Thu, 24 Oct 2013 00:43:31 -0000 Hi, Ok. I've reviewed this stuff in more depth. Split-6 is still way too big to commit as one commit. I was also hoping that we could get the updated hardware support into this without necessarily adding the PAN support. But, you're the one driving this, so it's up to you. :) * There's DPRINTF() and the debug flags that you've moved into if_iwnreg.h, which is the wrong place for it! * .. same as iwn_intr_str() * You still have style(9) issues: + the "if" constructs should be if (), not if(); + you need spaces between things - eg, if (a == b) rather than if(a==b) or if (a==b); + the } else { should be on one line, not separate on multiple lines. * What's the story behind sc->ctx? When is it being set/changed? * And then there's also ivp->ctx; that's the current VAP context, right? If that's the case ,why are we bothering checking unit number? Why don't we consistently check the vap context? So, let's break up split_6 into this: * create if_iwn_debug.h; put the debug macros, enum and such into that; * submit a patch _just_ for the debug work, that's easy to do. * Then, fix up the style(9) issues. * Then, help me figure out what the story is with sc->ctx so I understand what's going on there. I'd like to try and remove that if possible. Thanks, -adrian On 28 September 2013 10:23, Cedric GROSS wrote: > Hello, > > > > I'm get some free time. So I setted up my github for split work. > > > > So on https://github.com/KreizIT/FreeBSD-IWN/ > > > > You will find 2 new branch : split_6 and split_7. > > > > Split_6 is iwn -HEAD with split 6 applied. Patch for that is also available > in this branch. > > Split_7 is iwn -HEAD with split 6 and new split 7 applied. > > > > Split_7 start "parameters task". So no massive change except that it's > manage NIC without BT. > > > > Regards > > Cedric > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 01:05:50 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 60550CC3 for ; Thu, 24 Oct 2013 01:05:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2045B2DED for ; Thu, 24 Oct 2013 01:05:50 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id f11so4716368qae.14 for ; Wed, 23 Oct 2013 18:05:49 -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=bkFN4lsLgBfDs/s0x3cpY0lI57N3LNW5nIuI67QigIw=; b=lRytc/uRERsWjL5RlgyLOl8pZa7YdJGrgnF9hRE5UREjZ7tCkYq1R/YiaBAnCGwE18 KDgND8GZFqOgH6/v2PAyP2C/+Zx5z5r2T+4YbnqFlzK6/9P1ouJ23xVPLrTNrS7VN8l1 1SiFUuMbK1JDLuHtTvahC3uWaeHyWy/WIPtg0Dl6svIb3FGa8o9uCmGNKQS5yzaUHIb/ /vrYxy+dX6TA3S+zhYsTFSvqIkmU/yL//r6EJiVdnOB7UrQpJkX6ht0CtOp2BkqjIjUe CD63CG2+m/dEe2HzwCusA7pWF0LjrU/nCb/WDI26B7QzeFj1y/sAmo5YyImk0+yZE7V3 S0Gg== MIME-Version: 1.0 X-Received: by 10.224.161.83 with SMTP id q19mr759437qax.92.1382576749267; Wed, 23 Oct 2013 18:05:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 18:05:49 -0700 (PDT) In-Reply-To: References: <002701cebc6f$634c0040$29e400c0$@info> Date: Wed, 23 Oct 2013 18:05:49 -0700 X-Google-Sender-Auth: TpzcnLYXs8zj4a5QXa-jh7Q5yM0 Message-ID: Subject: Re: [IWN] Review From: Adrian Chadd To: Cedric GROSS 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: Thu, 24 Oct 2013 01:05:50 -0000 .. and I've just done the if_iwn_debug.h stuff, so you should update your patchset to include that. Thanks, -adrian On 23 October 2013 17:43, Adrian Chadd wrote: > Hi, > > Ok. I've reviewed this stuff in more depth. > > Split-6 is still way too big to commit as one commit. > > I was also hoping that we could get the updated hardware support into this > without necessarily adding the PAN support. But, you're the one driving > this, so it's up to you. :) > > * There's DPRINTF() and the debug flags that you've moved into > if_iwnreg.h, which is the wrong place for it! > * .. same as iwn_intr_str() > * You still have style(9) issues: > + the "if" constructs should be if (), not if(); > + you need spaces between things - eg, if (a == b) rather than if(a==b) > or if (a==b); > + the } else { should be on one line, not separate on multiple lines. > > * What's the story behind sc->ctx? When is it being set/changed? > * And then there's also ivp->ctx; that's the current VAP context, right? > If that's the case ,why are we bothering checking unit number? Why don't we > consistently check the vap context? > > So, let's break up split_6 into this: > > * create if_iwn_debug.h; put the debug macros, enum and such into that; > * submit a patch _just_ for the debug work, that's easy to do. > > * Then, fix up the style(9) issues. > * Then, help me figure out what the story is with sc->ctx so I understand > what's going on there. I'd like to try and remove that if possible. > > Thanks, > > > > -adrian > > > > On 28 September 2013 10:23, Cedric GROSS wrote: > >> Hello, >> >> >> >> I'm get some free time. So I setted up my github for split work. >> >> >> >> So on https://github.com/KreizIT/FreeBSD-IWN/ >> >> >> >> You will find 2 new branch : split_6 and split_7. >> >> >> >> Split_6 is iwn -HEAD with split 6 applied. Patch for that is also >> available >> in this branch. >> >> Split_7 is iwn -HEAD with split 6 and new split 7 applied. >> >> >> >> Split_7 start "parameters task". So no massive change except that it's >> manage NIC without BT. >> >> >> >> Regards >> >> Cedric >> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to " >> freebsd-wireless-unsubscribe@freebsd.org" >> > > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 03:46:19 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 8B48C133 for ; Thu, 24 Oct 2013 03:46:19 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 546A325EF for ; Thu, 24 Oct 2013 03:46:19 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:43072] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id CB/9C-15942-A0898625; Thu, 24 Oct 2013 03:46:18 +0000 Date: Thu, 24 Oct 2013 03:46:18 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <52684E48.20709@unsane.co.uk> Subject: Re: [rfc] removing the NDISulator X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Cc: 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: Thu, 24 Oct 2013 03:46:19 -0000 > The later driver model isn't supported by ndisulator. We'd have to > implement all the newer NDIS stuff for wifi and ethernet. > In the later NDIS layer the Microsoft Wireless Services implement a bunch > of stuff that used to be up to the driver. Ie, the driver just exposed an > ethernet "device" with some extra bits for wifi. Ie, the whole stack runs > in the driver. That has changed. ... > This is why I'd rather us bite the bullet now and deprecate it, versus have > it in there and put in the work to upgrade it to handle NDIS 6.x drivers > with the Microsoft wireless extensions stuff. > -adrian How much extra work would there be to update the ndis(ulator/wrapper)? Would it be more than writing native FreeBSD drivers which might be ported from NetBSD, OpenBSD and Linux? What about cases where specifications might be a trade secret? How difficult is it to port or write a wifi or Ethernet driver for FreeBSD? I have no experience writing device drivers but have some experience with C and C++. I notice NetBSD and OpenBSD have drivers for some chips that FreeBSD lacks. I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) and OpenBSD. Tom From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 04:30:26 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 5ED91B56 for ; Thu, 24 Oct 2013 04:30:26 +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 428F827A3 for ; Thu, 24 Oct 2013 04:30:25 +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=AllV5uMV+X1mP7wZtkRdDR7kWspsi0mi9Ckk/IGi0VDjn990zzzm7V9tXLjis4KL5OL097sY11mz HK3zhdIyVeJ5XUpN/Htr2trMqkgG7pbc1Kf3J32x6P82p+fdh6lq Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1382589023914991.3337685167688; Wed, 23 Oct 2013 21:30: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> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-PWaL94nvI2eFkBhZ/5OV" Date: Thu, 24 Oct 2013 07:30:20 +0300 Message-ID: <1382589020.1846.36.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_17103_262 X-ZohoMail-Owner: <1382589020.1846.36.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: Thu, 24 Oct 2013 04:30:26 -0000 --=-PWaL94nvI2eFkBhZ/5OV Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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! >=20 >=20 >=20 > -adrian >=20 >=20 >=20 > On 23 October 2013 16:56, clutton wrote: >=20 > > What is the best way to restart a wireless stack? > > > > A command "ifconfig wlan0 create wlandev ath0" starts the wpa_supplican= t > > 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/neti= f > > 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.or= g" --=-PWaL94nvI2eFkBhZ/5OV 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) iQIcBAABAgAGBQJSaKJbAAoJECNkWbjnbjuiWGkP/i0MfEd9P+WoZgebKJzFEpFI 0vkjvFrAybtzCzq3ulWjNZIukfXSB2IqrMhQgEwWazlsR5VUTHinQ87YG29kSAtE PpNkhWYCGRot5k3X2kf7aqeRSeLL1RdB5V7PliHGtpkOtsjMy7HgxkafLSedxduE TUpk4ftnBmaoL3O09XsPS1UInS7VcUf3MLUACywhPg7CqfFqx/OzOo+kpnSiLzU5 wPg/6EcXtw5srXhR1LMVDpTNHkWyjtIyQNI97Ukk0BE+/azebT1CrNJQe/H7NumY YyFjp8kUr4RQzcS3mob053JAG0yuZU9D7oA5vPP+gusYl4ssteLSsDBoaA1zuaGz t9RrOsOBr6OVBLZwikgm3Zd6mUahrVQMK93/xIas36VI8Qr3kSeKBlYxl4HwrXJQ JCovv0hG8ZTqAXal7jsYq46Pp6RIBSqCUsZR/XN5WLQMbeiRX3As3DGPf/YKKUN6 i6lN+m6Ce9mIVJoNia54ENNv29xdLEp1anOYoxUQiY4cCn4cbKX7odhmjqO9MbuV rp/derIMZrizoXFI+yh8mQSExx04J4/IaO/503raCBKSr5Ws70AxYTiP6k+QAN4W 4t9mMmjtNObHXntYLWdKAyOhUH5wbnpqERhtH4c1TjfbJ7a84Mn6rBBgxMQbed68 c9HmJ9qex/KR3PJbcQQs =tQf5 -----END PGP SIGNATURE----- --=-PWaL94nvI2eFkBhZ/5OV-- From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 04:43:40 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 B3DA1BC for ; Thu, 24 Oct 2013 04:43:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 74253283D for ; Thu, 24 Oct 2013 04:43:40 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id s14so1107387qeb.5 for ; Wed, 23 Oct 2013 21:43:39 -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=fZdcpPW2/pYFYyt84HaqHYOWkImT2kQ/oDs8eXevrJs=; b=wNIRUZ0SycdEp4QNuP9JxY+XCnrswobpEUZ6JwqQdmXig6smQNww9Q9hE12bGFGPPJ NO9xWvNWzcOhq+Nz3vD6an9Zd3fWLa8DpmRzdS4RHw7dtcH3QJVDlTLiExzDOsBfCCy6 T2tOlWi+LTTP/gYvvrRb8smziYs3t3LCQkb3UmA8V4qnpw6XvLFw+cflZ4vuHUCpIyW/ jKyETycGavVEKL7UjL5fOcHOZnvKIn9yVwcGNHrC2tCiD07cDi4kXpOt3ld6iU6Ko5Zs NM1RZyPNaIxtKUuUpdsN048a2M1tiCJPW4JsdcgnNGPfkt0wkwTLLrAdpny4owuwDu62 qtmQ== MIME-Version: 1.0 X-Received: by 10.49.24.202 with SMTP id w10mr1025925qef.12.1382589819672; Wed, 23 Oct 2013 21:43:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 23 Oct 2013 21:43:39 -0700 (PDT) In-Reply-To: <1382589020.1846.36.camel@eva02.mbsd> References: <1382572583.1862.39.camel@eva02.mbsd> <1382589020.1846.36.camel@eva02.mbsd> Date: Wed, 23 Oct 2013 21:43:39 -0700 X-Google-Sender-Auth: 5FwkgWsqsCKzuI4JcB-6IeXprRw 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: Thu, 24 Oct 2013 04:43:40 -0000 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=30067 > > > [wpa_supplicant] SUPPID=30067 > > > [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="wlan0" > > > ifconfig_wlan0="WPA DHCP" > > > ifconfig_em0="DHCP" > > > ipsec_enable="YES" > > > > > > /etc/wpa_supplicant.conf > > > network={ > > > ssid="ssid" > > > psk="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" > > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 06:17:38 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 AB0A4565; Thu, 24 Oct 2013 06:17:38 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 010762C2A; Thu, 24 Oct 2013 06:17:37 +0000 (UTC) Received: from [127.0.0.1] (mail.kevlo.org [220.135.115.6]) by ns.kevlo.org (8.14.6/8.14.6) with ESMTP id r9O6BWRe008017; Thu, 24 Oct 2013 14:11:33 +0800 (CST) (envelope-from kevlo@kevlo.org) Message-ID: <5268BB16.9@kevlo.org> Date: Thu, 24 Oct 2013 14:15:50 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: [rfc] removing the NDISulator References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <52684E48.20709@unsane.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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: Thu, 24 Oct 2013 06:17:38 -0000 Thomas Mueller wrote: > >> The later driver model isn't supported by ndisulator. We'd have to >> implement all the newer NDIS stuff for wifi and ethernet. > >> In the later NDIS layer the Microsoft Wireless Services implement a bunch >> of stuff that used to be up to the driver. Ie, the driver just exposed an >> ethernet "device" with some extra bits for wifi. Ie, the whole stack runs >> in the driver. That has changed. > > ... > >> This is why I'd rather us bite the bullet now and deprecate it, versus have >> it in there and put in the work to upgrade it to handle NDIS 6.x drivers >> with the Microsoft wireless extensions stuff. > > >> -adrian > How much extra work would there be to update the ndis(ulator/wrapper)? > > Would it be more than writing native FreeBSD drivers which might be ported > from NetBSD, OpenBSD and Linux? > > What about cases where specifications might be a trade secret? > > How difficult is it to port or write a wifi or Ethernet driver for FreeBSD? > > I have no experience writing device drivers but have some experience with C and C++. > > I notice NetBSD and OpenBSD have drivers for some chips that FreeBSD lacks. > > I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to > connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and > Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) > and OpenBSD. No offence, but you have mentioned several times that Realtek 8111E Ethernet and athn(4) do not work on FreeBSD, just wondering why you don't sit down and start coding then all your questions will be answered. > > Tom > > Kevin From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 08:20:01 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 3219B5A2; Thu, 24 Oct 2013 08:20:01 +0000 (UTC) (envelope-from milu@dat.pl) Received: from jab.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id E25B124A3; Thu, 24 Oct 2013 08:20:00 +0000 (UTC) Received: from jab.dat.pl (jsrv.dat.pl [127.0.0.1]) by jab.dat.pl (Postfix) with ESMTP id E390F14E; Thu, 24 Oct 2013 10:09:57 +0200 (CEST) X-Virus-Scanned: amavisd-new at dat.pl Received: from jab.dat.pl ([127.0.0.1]) by jab.dat.pl (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Uwo9eLEziiK0; Thu, 24 Oct 2013 10:09:55 +0200 (CEST) Received: from [10.0.6.80] (unknown [212.69.68.42]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by jab.dat.pl (Postfix) with ESMTPSA id BA6CD51; Thu, 24 Oct 2013 10:09:54 +0200 (CEST) Message-ID: <5268D632.2030506@dat.pl> Date: Thu, 24 Oct 2013 10:11:30 +0200 From: Maciej Milewski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: [rfc] removing the NDISulator References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <52684E48.20709@unsane.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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: Thu, 24 Oct 2013 08:20:01 -0000 On 24.10.2013 05:46, Thomas Mueller wrote: > I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to > connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and > Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) > and OpenBSD. > > Tom For your problems with Realtek 8111E chipset please have alook at http://lists.freebsd.org/pipermail/freebsd-net/2013-October/036935.html Maybe this patch isn't for you but you need to do something similar to add support. Regards, Maciej From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 10:49:40 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 133DA56E; Thu, 24 Oct 2013 10:49:40 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D2B9D2274; Thu, 24 Oct 2013 10:49:39 +0000 (UTC) Received: from pool-71-174-185-176.bstnma.east.verizon.net ([71.174.185.176] helo=homobox.opal.com) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VZITt-000HOM-5w; Thu, 24 Oct 2013 10:49:33 +0000 Received: from shibato (ANice-652-1-319-97.w86-193.abo.wanadoo.fr [86.193.178.97]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r9OAnRvS002537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 24 Oct 2013 06:49:28 -0400 (EDT) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 71.174.185.176 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18Tmh02OKDIdc3TM82D//r9 Date: Thu, 24 Oct 2013 12:49:15 +0200 From: "J.R. Oldroyd" To: Adrian Chadd Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump Message-ID: <20131024124915.315d25c4@shibato> In-Reply-To: References: X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.2) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/ni96b7Sh5/dGHs+xDk3ABl="; protocol="application/pgp-signature" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [71.174.185.176]); Thu, 24 Oct 2013 06:49:30 -0400 (EDT) X-Spam-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_50, FSL_HELO_NON_FQDN_1,HELO_NO_DOMAIN,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC shortcircuit=no autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com Cc: "freebsd-hackers@freebsd.org" , "freebsd-wireless@freebsd.org" , claudiu vasadi 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: Thu, 24 Oct 2013 10:49:40 -0000 --Sig_/ni96b7Sh5/dGHs+xDk3ABl= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 23 Oct 2013 13:12:05 -0700 Adrian Chadd wrote: > > On 23 October 2013 13:10, claudiu vasadi wrote: >=20 > > Hi, > > > > Still getting the "Cannot reset interface wlan0 - exit status 1" in > > wifimgr but no crash yet. Will keep trying :D > > >=20 > I have no idea about that. It's likely there's some net80211/iwn bug(s) b= ut > I don't use wifimgr so I don't know what it's doing. >=20 > For that I'd bug the wifimgr people in PCBSD. they can always file bug > reports with me :) >=20 > Thanks, >=20 >=20 >=20 > -adrian wifimgr isn't a PCBSD tool. wifimgr just a GUI front-end invoking standard FreeBSD command line tools to do what needs to be done. In this case, the command being executed is: /etc/rc.d/netif restart wlan0 Run this command from a shell to make sure there are no errors. Also check that wifimgr's su module is installed properly. It is %%PREFIX%%/libexec/wifimgrsu and should be mode 4511. -jr --Sig_/ni96b7Sh5/dGHs+xDk3ABl= Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlJo+zAACgkQls33urr0k4lPsgCgkkK832hIZHr+cHkXbcGG66qY IuEAnjiRPaUUQcxy4KDoRq11BEKb+vmK =g9Np -----END PGP SIGNATURE----- --Sig_/ni96b7Sh5/dGHs+xDk3ABl=-- From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 10:58:12 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 09815DB0; Thu, 24 Oct 2013 10:58:12 +0000 (UTC) (envelope-from claudiu.vasadi@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B98882334; Thu, 24 Oct 2013 10:58:11 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id e14so3452008iej.22 for ; Thu, 24 Oct 2013 03:58:11 -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=bxjHRdtrJh99pKv9NtlYEnvfuQmeEsOqaxaRZT7MrT4=; b=KxxJYxOPhscCXgDUGPtEVBZ6Sdpa16tbuy5tbLfJxo8RhL7Bkk8I4beMFHRmxlmmq/ 65hDvxtiaL6rj4Pc9ExIVz7LtEIpErUX30dGsA4V/CmBjw5m7a52BESKirvPq0TQSogG 8bX0WXaZySPUDIYbEv8SXN3dv1P1RN7De+GdH0KG2eE1aJDrm46SXY7leS2Frh/vyis2 Aq1HFsbkpkrrfWXE6WQo3wTBnjBbiF7v+FEtOYTnFvOZat1rrnA777xUTbZPdHsYSOny GauikiC8BU5t4KTz1GigfcWPIL24hPVZVTMjR8cRdSQsVU8YlaHXKaFSYJ1fcmGgYcG7 mD3w== MIME-Version: 1.0 X-Received: by 10.50.67.107 with SMTP id m11mr1215787igt.11.1382612291197; Thu, 24 Oct 2013 03:58:11 -0700 (PDT) Received: by 10.64.134.169 with HTTP; Thu, 24 Oct 2013 03:58:11 -0700 (PDT) In-Reply-To: <20131024124915.315d25c4@shibato> References: <20131024124915.315d25c4@shibato> Date: Thu, 24 Oct 2013 12:58:11 +0200 Message-ID: Subject: Re: 9.2-STABLE r255918 with GENERIC and iwn - core dump From: claudiu vasadi To: "J.R. Oldroyd" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" , "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: Thu, 24 Oct 2013 10:58:12 -0000 Hi, No errors and the file with mode 4511 exists. On Thu, Oct 24, 2013 at 12:49 PM, J.R. Oldroyd wrote: > On Wed, 23 Oct 2013 13:12:05 -0700 Adrian Chadd > wrote: > > > > On 23 October 2013 13:10, claudiu vasadi > wrote: > > > > > Hi, > > > > > > Still getting the "Cannot reset interface wlan0 - exit status 1" in > > > wifimgr but no crash yet. Will keep trying :D > > > > > > > I have no idea about that. It's likely there's some net80211/iwn bug(s) > but > > I don't use wifimgr so I don't know what it's doing. > > > > For that I'd bug the wifimgr people in PCBSD. they can always file bug > > reports with me :) > > > > Thanks, > > > > > > > > -adrian > > wifimgr isn't a PCBSD tool. > > wifimgr just a GUI front-end invoking standard FreeBSD command line > tools to do what needs to be done. In this case, the command being > executed is: > > /etc/rc.d/netif restart wlan0 > > Run this command from a shell to make sure there are no errors. > Also check that wifimgr's su module is installed properly. It is > %%PREFIX%%/libexec/wifimgrsu and should be mode 4511. > > -jr > -- Best regards, Claudiu Vasadi From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 24 20:04:26 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 77BDA1A1 for ; Thu, 24 Oct 2013 20:04:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3BCBE278E for ; Thu, 24 Oct 2013 20:04:26 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id x19so1685760qcw.37 for ; Thu, 24 Oct 2013 13:04:25 -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=3gZzKUDLB9iX7nDj8BinRFArKJdT91GwGX51WD16aq8=; b=b1woB4QA8f2FT8M/jA4xw3qRbm8TVT5AR4FQ7LNpYdqFz0o1oJMPX5xtI78jdxjdIp 5JbcPxo3rpJeiuzWfGQxsm3KHa9sGxHxqWE9hvPl41Y+bdjKQksL8F6PMK3Y1jWVVLVh Ajfpvvdz0H8bhZd/J1w3fB1PBkzsPdS7+mVPsng/V0agkbC+l8PLgyM0Zcy+zjYDMi9s pPn9YfrF3UQ8sXBspC0yRxEMdYeRwNtMndMFttznypsVRSozSGerTlzui8vHZqBhCkAI my6iGBjFu4Zucmq6bc2Ndlro7c9zsxpx32NFkCU229+n0viN4QjYexixIa7OtSCMxg+t YlaA== MIME-Version: 1.0 X-Received: by 10.49.62.3 with SMTP id u3mr5976030qer.6.1382645065430; Thu, 24 Oct 2013 13:04:25 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Thu, 24 Oct 2013 13:04:25 -0700 (PDT) Date: Thu, 24 Oct 2013 13:04:25 -0700 Message-ID: Subject: [iwn] request to test: linkq, plcp, txrate fixes From: Adrian Chadd 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: Thu, 24 Oct 2013 20:04:26 -0000 Hi! I have a patch against iwn(4): http://people.freebsd.org/~adrian/ath/20131024-iwn-1-fix-xmit-rate-plcp-linkq.diff This does a few things: * The multi-rate retry ("link quality" stuff) on iwn is a table, and I think I broke it slightly when I implemented 11n rate control. This disables it for now, at least until I / someone implements a replacement table setup and linkq decision. * get rid of the rate index stuff - it was used to decide a few things and it was doing legacy-only rate index lookups. I've just removed it; it's not needed. * Teach the raw transmit path to use the new plcp lookup routine that sets things up. * Correctly implement 11g protection. Right now it was a bit of a hack and it was not correct for 11a or 11n operation. I still get transmit hangs on my 4965 but the "invalid rate" failures have disappeared. But for some odd reason, the transmits completed but weren't being marked as failed. I don't yet know why. I'm also not sure why transmit is hanging; sometimes it looks like DMA stalls somehow. So - maybe this'll help with various 11n issues on iwn(4), maybe it won't. I'm not sure yet. I'm trying to avoid taking ownership of iwn(4) but I rather dislike the occasional 5100/4965 hangs.. Thanks, -adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 25 01:11: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 F3188105 for ; Fri, 25 Oct 2013 01:11:21 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm2-vm1.bullet.mail.bf1.yahoo.com (nm2-vm1.bullet.mail.bf1.yahoo.com [98.139.213.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 825DE2CCB for ; Fri, 25 Oct 2013 01:11:21 +0000 (UTC) Received: from [98.139.212.145] by nm2.bullet.mail.bf1.yahoo.com with NNFMP; 25 Oct 2013 01:11:14 -0000 Received: from [98.139.211.205] by tm2.bullet.mail.bf1.yahoo.com with NNFMP; 25 Oct 2013 01:11:14 -0000 Received: from [127.0.0.1] by smtp214.mail.bf1.yahoo.com with NNFMP; 25 Oct 2013 01:11:14 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382663474; bh=mWwOLG9hrl10+Lk9j3t24E4kQmUYxAJdQ0q0oeiZ1eY=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=6vvPIvVZPzjujzTkq5r4JUriVJjcWX7XH41Gwr/Ra/XHiDtvKtGK/HRnrfueOxSfkvQTCi8yZ4VCImz9e658tJhyp+5YaQ8mQG4Sejx8xwK0w9UM/12Nl6134D+7GD0jxWjx8KDVUdCx9aWSyFNwcxuMYm9lHwQalrnz5dqF2kY= X-Yahoo-Newman-Id: 398663.56385.bm@smtp214.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: EL4ijF0VM1lFxvk7K.VlmHyLoD1bCIVH02r5I9fn8PRxm.4 UqC04F5eIdsRFh1AqS1v6pUGAooVBhPOcdznCqjqtIYXtDhpFVq3IZK4Cqjn J9z.OBuXaUyq.CFcZ3Gt9Bqoc6TVd3.yJ6yRUidxse3jc_pMN8R6wkARsfdt F5hcCUk2ucGwSWGSQVDGwpfdj4RWKlJq89dmzzluJ6zljSHkWuh_9UGHSkgm xc3zN3ke_qpXMHwQ1x1RBXILFEhylSr53wDZVpq8hcWU_PmSGQNPclKylVPb lkvirM84IH7y8wDwW4XwKMgczR_bcHrbVb57rxG3jfu8w7dsPr.psmvOaEKB leBH8RJv91umeG6Is1MqQoiIZWP05x0hXcPmJ9awAYk9jC8kwtdUj2wF7V.i ibHI1.b.umD6j9ejksNjUA6FG09549MLJhLMz2NJKegCd2Ht2z9JWMt1ZGCv GvgpsYrnrboPz_q84X1M9hXgoocqDgv4SnA_ctVKpSW9A.oaCHLHhA272fNF wNhSRx1Gjn11txyJqtHf_K14_7OQQJ.hPxUDZgWRITIJXLM9VZ80dSgvzwa9 K6jcslFnZ140OAePvAwuqfSdRa4u5s290Ziblb9di.IyLaClfXydsqCoZn3I LvBwaCruA4xuqEx6OBu3vp6CpoeqG_xL79V0LKvLP8DiHCGlaHrMDr_UBL34 H1ZqAuwNGEBLknzY- X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [192.168.100.5] (sean_bruno@63.138.121.126 with ) by smtp214.mail.bf1.yahoo.com with SMTP; 24 Oct 2013 18:11:14 -0700 PDT Subject: Re: [iwn] request to test: linkq, plcp, txrate fixes From: Sean Bruno To: Adrian Chadd In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-kutRUkuTFt8Sr5xjNGCZ" Date: Thu, 24 Oct 2013 20:49:56 -0400 Message-ID: <1382662196.2498.1.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2013 01:11:22 -0000 --=-kutRUkuTFt8Sr5xjNGCZ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Thu, 2013-10-24 at 13:04 -0700, Adrian Chadd wrote: > Hi! >=20 > I have a patch against iwn(4): >=20 > http://people.freebsd.org/~adrian/ath/20131024-iwn-1-fix-xmit-rate-plcp-l= inkq.diff >=20 > This does a few things: >=20 > * The multi-rate retry ("link quality" stuff) on iwn is a table, and I > think I broke it slightly when I implemented 11n rate control. This > disables it for now, at least until I / someone implements a replacement > table setup and linkq decision. >=20 > * get rid of the rate index stuff - it was used to decide a few things an= d > it was doing legacy-only rate index lookups. I've just removed it; it's n= ot > needed. >=20 > * Teach the raw transmit path to use the new plcp lookup routine that set= s > things up. >=20 > * Correctly implement 11g protection. Right now it was a bit of a hack an= d > it was not correct for 11a or 11n operation. >=20 > I still get transmit hangs on my 4965 but the "invalid rate" failures hav= e > disappeared. But for some odd reason, the transmits completed but weren't > being marked as failed. I don't yet know why. >=20 > I'm also not sure why transmit is hanging; sometimes it looks like DMA > stalls somehow. >=20 > So - maybe this'll help with various 11n issues on iwn(4), maybe it won't= . > I'm not sure yet. I'm trying to avoid taking ownership of iwn(4) but I > rather dislike the occasional 5100/4965 hangs.. >=20 > Thanks, >=20 >=20 >=20 > -adrian running this now against 11-CURRENT. No issues noted on my adapter (Centrino Advanced-N 6205 [Taylor Peak]). All seems very good. I haven't tried it the office though, and that's the one that's the most interesting I fear. sean --=-kutRUkuTFt8Sr5xjNGCZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iQEcBAABAgAGBQJSacAxAAoJEBkJRdwI6BaHrQIH/RlMGJQi5cCnvKcJz6UdWgj7 rruLond4psLWy2exENV2Yj8+rI8GpFSxfQq2vBKhQHfBwIIPZQ9KcA7opiaIrYR+ oD8cKcAJuBQpB1K/rtzKzu6DHoHevZ/toUkguD46oPsh2cBKaCy4voOIRQm9Lxw8 2b0QeUBe6GhZVy3670aaIKcfuGPsJiQNiZNiBJSUDTjoEEpe5M00104q82pnhqtN iVA6f06smwFSCZxrj1CVxI4fTGN3w3CL7n26UA6qmJZM+9wbZ49Pg9BomRZv8yDl CGaoAox/c5b+S4bOTYICUTVDLNZm51IXIN0cxszN9jnwAx4g1piHjkW4Rhhy0Fo= =neCW -----END PGP SIGNATURE----- --=-kutRUkuTFt8Sr5xjNGCZ-- From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 25 05:30:49 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 5B52E3A7 for ; Fri, 25 Oct 2013 05:30:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1C4872C78 for ; Fri, 25 Oct 2013 05:30:49 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id j15so328880qaq.20 for ; Thu, 24 Oct 2013 22:30:48 -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:content-type; bh=5TlaN9DyNuYdvYjXy4WgdgDmUa/EGZDhlQlDTb/LS9I=; b=rbQzwniEXEO76gXYPhcbB0ZiWd3kErlgtJ220hpNEkpOxhqq97uc9uowgioEz6huw7 xJDU/bUPXYjHiyyeh3lepKCgCx4Z+9i3ytxw65f94netTUxggTtM8kmtbggS6hqTddva mdjaksyYWJ1pic+bnjt6cBDbCkmflrR1xvaDsRZxtrZFGRqYSEuT7eaASm01cMn73h1T nZjMgcMDo0dRD+AtXaza4vpJhyYOao8IZ9foeoDAHgn8gUBWWGZxssLqPUZnXsEMrU6M rhRUWIBi6PlzSWa85VOb8rBlm1HEuaFyRzovkWbahNuJWKPnJ2f79Sc6QPBX8P4TQJoq /5mw== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr8799724qad.76.1382679048299; Thu, 24 Oct 2013 22:30:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 24 Oct 2013 22:30:48 -0700 (PDT) In-Reply-To: <201310250406.r9P46s8A080761@svn.freebsd.org> References: <201310250406.r9P46s8A080761@svn.freebsd.org> Date: Thu, 24 Oct 2013 22:30:48 -0700 X-Google-Sender-Auth: MD_-oRPOA3kJiydtCBUykW4IjfY Message-ID: Subject: Fwd: svn commit: r257094 - head/sys/mips/conf From: Adrian Chadd 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, 25 Oct 2013 05:30:49 -0000 https://code.google.com/p/freebsd-wifi-build/wiki/Alfa_Hornet_UB :) -adrian ---------- Forwarded message ---------- From: Adrian Chadd Date: 24 October 2013 21:06 Subject: svn commit: r257094 - head/sys/mips/conf To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: adrian Date: Fri Oct 25 04:06:54 2013 New Revision: 257094 URL: http://svnweb.freebsd.org/changeset/base/257094 Log: Add a configuration file and hints file for the Alfa Networks Hornet UB board. This is another AR9331 board similar to the Carambola2. It has different ethernet and LED wiring though. They make a variety of boards that mostly differ on the amount of RAM/flash available. Alfa Networks graciously donated a handful of 64MB RAM/16MB flash boards so I can finish off 802.11s support for the AR93xx chips and do up a tech demonstration with it. This is enough to bring up the board. Tested: * Alfa networks UB Hornet board - 64MB ram, 16MB flash version. Thankyou to Alfa Networks for the development boards! Sponsored by: Alfa Networks (hardware only) Added: head/sys/mips/conf/ALFA_HORNET_UB (contents, props changed) head/sys/mips/conf/ALFA_HORNET_UB.hints (contents, props changed) Added: head/sys/mips/conf/ALFA_HORNET_UB ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/mips/conf/ALFA_HORNET_UB Fri Oct 25 04:06:54 2013 (r257094) @@ -0,0 +1,57 @@ +# +# Alfa Networks Hornet UB - an AR933x based SoC wifi device. +# +# http://www.alfa.com.tw/products_show.php?pc=99&ps=50 +# +# This is for the 64MB RAM/16MB flash part. They also +# do various other versions; they have different RAM/flash +# configurations. +# +# * AR9330 SoC +# * 64MB RAM +# * 16MB flash +# * Integrated 1x1 2GHz wifi and 10/100 bridge +# +# $FreeBSD$ +# + +# Include the default AR933x parameters +include "AR933X_BASE" + +ident ALFA_HORNET_UB + +# Override hints with board values +hints "ALFA_HORNET_UB.hints" + +# Board memory - 64MB +options AR71XX_REALMEM=(64*1024*1024) + +# i2c GPIO bus +#device gpioiic +#device iicbb +#device iicbus +#device iic + +# Options required for miiproxy and mdiobus +options ARGE_MDIO # Export an MDIO bus separate from arge +device miiproxy # MDIO bus <-> MII PHY rendezvous + +device etherswitch +device arswitch + +# read MSDOS formatted disks - USB +#options MSDOSFS + +# Enable the uboot environment stuff rather then the +# redboot stuff. +options AR71XX_ENV_UBOOT + +# uzip - to boot natively from flash +device geom_uncompress +options GEOM_UNCOMPRESS + +# Used for the static uboot partition map +device geom_map + +# Boot off of the rootfs, as defined in the geom_map setup. +options ROOTDEVNAME=\"ufs:map/rootfs.uncompress\" Added: head/sys/mips/conf/ALFA_HORNET_UB.hints ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/mips/conf/ALFA_HORNET_UB.hints Fri Oct 25 04:06:54 2013 (r257094) @@ -0,0 +1,105 @@ +# +# This file adds to the values in AR933X_BASE.hints +# +# $FreeBSD$ + +# mdiobus on arge1 +hint.argemdio.0.at="nexus0" +hint.argemdio.0.maddr=0x1a000000 +hint.argemdio.0.msize=0x1000 +hint.argemdio.0.order=0 + +# There's no need to set the ar933x GMAC configuration bits. +# This just creates a switch instance and correctly uses it. + +# Embedded Atheros Switch +hint.arswitch.0.at="mdio0" + +# XXX this should really say it's an AR933x switch, as there +# are some vlan specific differences here! +hint.arswitch.0.is_7240=1 +hint.arswitch.0.numphys=4 +hint.arswitch.0.phy4cpu=1 # phy 4 is a "CPU" separate PHY +hint.arswitch.0.is_rgmii=0 +hint.arswitch.0.is_gmii=1 # arge1 <-> switch PHY is GMII + +# arge0 - MII, autoneg, phy(4) +hint.arge.0.phymask=0x10 # PHY4 +hint.arge.0.mdio=mdioproxy1 # .. off of the switch mdiobus + +# arge1 - GMII, 1000/full +hint.arge.1.phymask=0x0 # No directly mapped PHYs +hint.arge.1.media=1000 +hint.arge.1.fduplex=1 + +# Where the ART is - last 64k in the flash +# 0x9fff1000 ? +hint.ath.0.eepromaddr=0x1fff0000 +hint.ath.0.eepromsize=16384 + +# The board 16MiB flash layout in uboot env: +# +# 256k (uboot), 64k (uboot-env), 14336k (rootfs), 1600k (kernel), 64k (NVRAM), 64k (ART) + +# However, it boots from 0x9f050000, which is the front of the flsah! +# Thus the kernel/rootfs are switched around. + +# 256KB +hint.map.0.at="flash/spi0" +hint.map.0.start=0x00000000 +hint.map.0.end=0x000040000 +hint.map.0.name="uboot" +hint.map.0.readonly=1 + +# 64KB +hint.map.1.at="flash/spi0" +hint.map.1.start=0x00040000 +hint.map.1.end=0x00050000 +hint.map.1.name="uboot-env" +hint.map.1.readonly=0 + +# 1600KB +hint.map.2.at="flash/spi0" +hint.map.2.start=0x00050000 +hint.map.2.end=0x001e0000 +hint.map.2.name="kernel" +hint.map.2.readonly=0 + +# 14336KB +hint.map.3.at="flash/spi0" +hint.map.3.start=0x001e0000 +hint.map.3.end=0x00fe0000 +hint.map.3.name="rootfs" +hint.map.3.readonly=0 + +# NVRAM +hint.map.4.at="flash/spi0" +hint.map.4.start=0x00fe0000 +hint.map.4.end=0x00ff0000 +hint.map.4.name="cfg" +hint.map.4.readonly=0 + +# This is radio calibration section. It is (or should be!) unique +# for each board, to take into account thermal and electrical differences +# as well as the regulatory compliance data. +# +hint.map.5.at="flash/spi0" +hint.map.5.start=0x00ff0000 +hint.map.5.end=0x01000000 +hint.map.5.name="art" +hint.map.5.readonly=1 + +# GPIO specific configuration block + +# Don't flip on anything that isn't already enabled. +# This includes leaving the SPI CS1/CS2 pins as GPIO pins as they're +# not used here. +hint.gpio.0.function_set=0x00000000 +hint.gpio.0.function_clear=0x00000000 + +# These are the GPIO LEDs and buttons which can be software controlled. +#hint.gpio.0.pinmask=0x001c02ae +#hint.gpio.0.pinmask=0x00001803 + +# XXX TODO: the button and LEDs! + From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 25 09:09:20 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 5D931B18 for ; Fri, 25 Oct 2013 09:09:20 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 234C627D3 for ; Fri, 25 Oct 2013 09:09:19 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:59597] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 38/65-02506-F353A625; Fri, 25 Oct 2013 09:09:19 +0000 Date: Fri, 25 Oct 2013 09:09:19 +0000 Message-ID: <38.65.02506.F353A625@cdptpa-oedge01> From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <52684E48.20709@unsane.co.uk> <5268D632.2030506@dat.pl> Subject: Re: [rfc] removing the NDISulator X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 Cc: 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: Fri, 25 Oct 2013 09:09:20 -0000 > On 24.10.2013 05:46, Thomas Mueller wrote: > > I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to > > connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and > > Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) > > and OpenBSD. > > Tom > For your problems with Realtek 8111E chipset please have alook at http://lists.freebsd.org/pipermail/freebsd-net/2013-October/036935.html > Maybe this patch isn't for you but you need to do something similar to > add support. > Regards, > Maciej Where does the patch begin and end? Does it include a and b in apparent path? Is the first line diff -git and the last line just before -- ? Do I save that to a file, go to $SRCDIR and patch ? I would also like to see if I can connect by wifi using Hiro H50191 USB-stick WLAN adapter (RTL8191SU chip) using device rsu. Tom From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 25 12:15: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 0563E489; Fri, 25 Oct 2013 12:15:39 +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 7D2ED21D3; Fri, 25 Oct 2013 12:15:37 +0000 (UTC) Received: from mail.s1.d2ux.org (mail [10.0.0.3]) by mail.s1.d2ux.org (Postfix) with ESMTP id 5530284F25D6; Fri, 25 Oct 2013 14:08:57 +0200 (CEST) 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 JmYx6yjB2Mhn; Fri, 25 Oct 2013 14:08:55 +0200 (CEST) Received: from workstation.local (p5DDA8D2F.dip0.t-ipconnect.de [93.218.141.47]) by mail.s1.d2ux.org (Postfix) with ESMTPSA id 3B16E84F25CC; Fri, 25 Oct 2013 14:08:55 +0200 (CEST) Message-ID: <526A5EBD.0@petermann-it.de> Date: Fri, 25 Oct 2013 14:06:21 +0200 From: Matthias Petermann User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Cedric GROSS Subject: Re: Centrino Wireless N2230 support References: <20130913112427.Horde.Lr2e32AbzvcQIrrWuDh-dg1@d2ux.org> <001e01ceb064$80168220$80438660$@info> In-Reply-To: <001e01ceb064$80168220$80438660$@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: Fri, 25 Oct 2013 12:15:39 -0000 Hi Cedric, Am 13.09.2013 11:34, schrieb Cedric GROSS: > Not against 10-current. But if you wish, you could test with my > version on github https://github.com/KreizIT/FreeBSD-IWN Use LKGV > branch, should be running with 10-current. Cedric finally I had a chance to test the driver. I installed a fresh 9.2 relase and placed the files from https://github.com/KreizIT/FreeBSD-IWN into my /usr/src/sys and tried to make sys/modules/iwn (cd /usr/src/sys/modules/iwn;make) Unfortunality it doesn't build, instead giving this message: Warning: Object directory not changed from original /usr/src/sys/modules/iwn @ -> /usr/src/sys machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h echo "#define IEEE80211_DEBUG 1" > opt_wlan.h :> opt_iwn.h cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c cc1: warnings being treated as errors /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c: In function 'iwn_rate_to_plcp': /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:2254: warning: implicit declaration of function 'ieee80211_legacy_rate_lookup' /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:2254: warning: nested extern declaration of 'ieee80211_legacy_rate_lookup' [-Wnested-externs] /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c: In function 'iwn_rx_compressed_ba': /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:2600: error: 'struct ieee80211_tx_ampdu' has no member named 'txa_tid' /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c: In function 'iwn_ampdu_tx_done': /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3075: error: 'struct ieee80211_tx_ampdu' has no member named 'txa_tid' /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c: In function 'iwn_addba_response': /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:6021: error: 'struct ieee80211_tx_ampdu' has no member named 'txa_tid' /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c: In function 'iwn_ampdu_tx_stop': /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:6084: error: 'struct ieee80211_tx_ampdu' has no member named 'txa_tid' *** [if_iwn.o] Error code 1 The closest issue seems to be "struct ieee80211_tx_ampdu' has no member named 'txa_tid' but I cannot see what's wrong with it. As I get the similiar error when trying to build https://github.com/KreizIT/freebsd-iwl - is there anything wrong with my build process? Kind regards, Matthias From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 25 20:14:40 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 79DF9296; Fri, 25 Oct 2013 20:14:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 287142E98; Fri, 25 Oct 2013 20:14:40 +0000 (UTC) Received: by mail-qe0-f44.google.com with SMTP id 6so2683211qeb.31 for ; Fri, 25 Oct 2013 13:14:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WvCwXmhBqUwILiG33CQkCmVfY7S0OEf/prND3kmo6cM=; b=mfJQA3+ztHpoVhizrzVzU0duMy9aS+CfPj/m9TTYFmy/H6UkDGHBruWc4E91MaKf7e y8YDJ+4RQQaST/8GS55jklE7PAOznTHyQSvNPy2eR5D4nfJK0N78vF0wpCZptlhWlinY DuZVaTHjHZ+02giKqmlMAlSb73JNuX7ZYHxCCdUOFbHRNe5otuFurWYtqHbJ9c66wY/G 3rXkeFcaMrt9u7luXE+Gh0FJtijyhT+GjsCQequHEwUrEIj2kf9jtvRHexnKKHCXUXsl mFMsCWXHKdnw3B14Prl3nWAEHVv3Rgcp2W1i01+iPk34EAbAoEbomN3OUy45FmKseGkn xHng== MIME-Version: 1.0 X-Received: by 10.49.103.161 with SMTP id fx1mr13256052qeb.68.1382732079409; Fri, 25 Oct 2013 13:14:39 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Fri, 25 Oct 2013 13:14:39 -0700 (PDT) In-Reply-To: <1382662196.2498.1.camel@localhost> References: <1382662196.2498.1.camel@localhost> Date: Fri, 25 Oct 2013 13:14:39 -0700 Message-ID: Subject: Re: [iwn] request to test: linkq, plcp, txrate fixes From: Adrian Chadd To: Sean Bruno 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, 25 Oct 2013 20:14:40 -0000 Just committed it to -HEAD. -adrian On 24 October 2013 17:49, Sean Bruno wrote: > On Thu, 2013-10-24 at 13:04 -0700, Adrian Chadd wrote: > > Hi! > > > > I have a patch against iwn(4): > > > > > http://people.freebsd.org/~adrian/ath/20131024-iwn-1-fix-xmit-rate-plcp-linkq.diff > > > > This does a few things: > > > > * The multi-rate retry ("link quality" stuff) on iwn is a table, and I > > think I broke it slightly when I implemented 11n rate control. This > > disables it for now, at least until I / someone implements a replacement > > table setup and linkq decision. > > > > * get rid of the rate index stuff - it was used to decide a few things > and > > it was doing legacy-only rate index lookups. I've just removed it; it's > not > > needed. > > > > * Teach the raw transmit path to use the new plcp lookup routine that > sets > > things up. > > > > * Correctly implement 11g protection. Right now it was a bit of a hack > and > > it was not correct for 11a or 11n operation. > > > > I still get transmit hangs on my 4965 but the "invalid rate" failures > have > > disappeared. But for some odd reason, the transmits completed but weren't > > being marked as failed. I don't yet know why. > > > > I'm also not sure why transmit is hanging; sometimes it looks like DMA > > stalls somehow. > > > > So - maybe this'll help with various 11n issues on iwn(4), maybe it > won't. > > I'm not sure yet. I'm trying to avoid taking ownership of iwn(4) but I > > rather dislike the occasional 5100/4965 hangs.. > > > > Thanks, > > > > > > > > -adrian > > running this now against 11-CURRENT. No issues noted on my adapter > (Centrino Advanced-N 6205 [Taylor Peak]). All seems very good. > > I haven't tried it the office though, and that's the one that's the most > interesting I fear. > > sean > From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 26 08:56:56 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 1031BCCD; Sat, 26 Oct 2013 08:56:56 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id 983832098; Sat, 26 Oct 2013 08:56:55 +0000 (UTC) Received: by alpha.kreiz-it.fr (Postfix, from userid 80) id 6361C820; Sat, 26 Oct 2013 10:56:53 +0200 (CEST) To: Matthias Petermann Subject: Re: Centrino Wireless N2230 support X-PHP-Script: webmail.kreiz-it.fr/index.php for 83.202.109.211 MIME-Version: 1.0 Date: Sat, 26 Oct 2013 10:56:53 +0200 From: cg@cgross.info In-Reply-To: <526A5EBD.0@petermann-it.de> References: <20130913112427.Horde.Lr2e32AbzvcQIrrWuDh-dg1@d2ux.org> <001e01ceb064$80168220$80438660$@info> <526A5EBD.0@petermann-it.de> Message-ID: <3f4c1e2627b7da9b271b55f10ad9f7e5@cgross.info> X-Sender: cg@cgross.info User-Agent: Roundcube Webmail/0.8.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sat, 26 Oct 2013 08:56:56 -0000 Hello Matthias, Le 2013-10-25 14:06, Matthias Petermann a écrit : > Hi Cedric, > > Am 13.09.2013 11:34, schrieb Cedric GROSS: > >> Not against 10-current. But if you wish, you could test with my version on github https://github.com/KreizIT/FreeBSD-IWN [1] Use LKGV branch, should be running with 10-current. Cedric > > finally I had a chance to test the driver. I installed a fresh 9.2 > relase and placed the files from https://github.com/KreizIT/FreeBSD-IWN [1] > into my /usr/src/sys and tried to make sys/modules/iwn (cd > /usr/src/sys/modules/iwn;make) > > Unfortunality it doesn't build, instead giving this message: > > /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:2254: warning: implicit > declaration of function 'ieee80211_legacy_rate_lookup' > [...] > The closest issue seems to be "struct ieee80211_tx_ampdu' has no member > named 'txa_tid' but I cannot see what's wrong with it. > > As I get the similiar error when trying to build > https://github.com/KreizIT/freebsd-iwl [2] - is there anything wrong with my > build process? > > Kind regards, > Matthias You must get and build net80211 from -HEAD also. It's why you have this kind of compile error. Cedric Links: ------ [1] https://github.com/KreizIT/FreeBSD-IWN [2] https://github.com/KreizIT/freebsd-iwl From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 26 14:32:46 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 3E4244DD; Sat, 26 Oct 2013 14:32:46 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EF44420DE; Sat, 26 Oct 2013 14:32:45 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id n10so2061372oag.11 for ; Sat, 26 Oct 2013 07:32:45 -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=Znzb3S0w9j2QULsxjHw1L5QLEC8AkzVVGsQLZWAYTVk=; b=RjM39cgtjVWOXvYjt0XEW5ep31rSU6y9kHLXSNddUZYA7/PYqvqmpIctQ6N/bXWspL 4OmQfNsuoIY3om8PnhdLJI8D+huKzQi/40+kgcXVCpPr9iZm8rvGENt+B9bpV3WAKkmh AVJuuWKcX5e21D8+52BQ7tZbuHMoQ6K0WDm6uJKc7eiK4nM2MdwujCMbgKh7UnB993TY eNlETEj8U2ooXi02Bxz2JuaITtEcB74Z+m0xLp8ggZ3u+h/FQBniRUiT/g9+MdEExRTB NWS5U2OG211LNuGaCXN09HhEK7xHnRMVtLRMhrNEljwFig3iuCXJGXtGUBjc5ND/4aUD dg0w== MIME-Version: 1.0 X-Received: by 10.182.22.18 with SMTP id z18mr7272823obe.42.1382797965169; Sat, 26 Oct 2013 07:32:45 -0700 (PDT) Sender: uspoerlein@gmail.com Received: by 10.76.69.104 with HTTP; Sat, 26 Oct 2013 07:32:45 -0700 (PDT) In-Reply-To: References: Date: Sat, 26 Oct 2013 16:32:45 +0200 X-Google-Sender-Auth: D7KQ2elEPGK_weiqa4M4F7JmBjw Message-ID: Subject: Re: implementing multiple BSSID addresses for different VAPs, or 'why was the flag called bssid again?' From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 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, 26 Oct 2013 14:32:46 -0000 Well, the following in rc.conf wlans_ath0="wlan0 wlan2" create_args_wlan0="bssid wlanmode hostap country DE authmode wpa ssid COYOTE" ifconfig_wlan0="ssid COYOTE mode 11g pureg up" create_args_wlan2="bssid wlanmode hostap country DE authmode wpa ssid COYOTE_GUEST" ifconfig_wlan2="ssid COYOTE_GUEST mode 11g pureg up" Does not quite work, I'm left with: (from dmesg) Setting hostname: coyote.spoerlein.net. bridge0: Ethernet address: 02:ac:6e:56:db:00 Created clone interfaces: bridge0. wlan0: Ethernet address: 68:a3:c4:51:44:99 wlan2: Ethernet address: 6e:a3:c4:51:44:99 ifconfig: SIOCS80211: Device busy ath0: stuck beacon; resetting (bmiss count 4) (not that there's no echo for creating wlan devices, that should maybe be added?) Anyway, I thus get this: ath0: flags=8943 metric 0 mtu 2290 ether 68:a3:c4:51:44:99 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running wlan0: flags=8d43 metric 0 mtu 1500 ether 68:a3:c4:51:44:99 inet6 fe80::6aa3:c4ff:fe51:4499%wlan0 prefixlen 64 tentative scopeid 0xa nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: no carrier ssid COYOTE channel 7 (2442 MHz 11g) regdomain ETSI country DE indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs wlan2: flags=8943 metric 0 mtu 1500 ether 6e:a3:c4:51:44:99 inet6 fe80::6ca3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative scopeid 0xb nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE_GUEST channel 7 (2442 MHz 11g) bssid 6e:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXED deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs root@coyote:~# ifconfig ath0 ath0: flags=8802 metric 0 mtu 2290 ether 68:a3:c4:51:44:99 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: no carrier root@coyote:~# ifconfig wlan0 create wlandev ath0 bssid wlanmode hostap country DE authmode wpa ssid COYOTE root@coyote:~# ifconfig wlan0 wlan0: flags=8943 metric 0 mtu 1500 ether 6a:a3:c4:51:44:99 inet6 fe80::68a3:c4ff:fe51:4499%wlan0 prefixlen 64 tentative scopeid 0xa nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE channel 13 (2472 MHz 11g) bssid 6a:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXED deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs root@coyote:~# ifconfig wlan2 create wlandev ath0 bssid wlanmode hostap country DE authmode wpa ssid COYOTE_GUEST ifconfig: SIOCS80211: Device busy Exit 1 root@coyote:~# ifconfig wlan2 wlan2: flags=8943 metric 0 mtu 1500 ether 6e:a3:c4:51:44:99 inet6 fe80::6ca3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative scopeid 0xb nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE_GUEST channel 13 (2472 MHz 11g) bssid 6e:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXED deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs root@coyote:~# ifconfig wlan0; ifconfig wlan2 wlan0: flags=8943 metric 0 mtu 1500 ether 6a:a3:c4:51:44:99 inet6 fe80::68a3:c4ff:fe51:4499%wlan0 prefixlen 64 tentative scopeid 0xa nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE channel 13 (2472 MHz 11g) bssid 6a:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXED deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs wlan2: flags=8943 metric 0 mtu 1500 ether 6e:a3:c4:51:44:99 inet6 fe80::6ca3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative scopeid 0xb nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE_GUEST channel 13 (2472 MHz 11g) bssid 6e:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXED deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs Then I also had to bounce the hostapd on wlan0 and start the one on wlan2 and it looks very promising currently. Is it possible that there is a timing issue involved and doing it manually works better than when the startup scripts run through this? I've now got this working version that seems to be solid and comes up during boot w/o manual intervention. /etc/rc.conf: wlans_ath0="wlan0 wlan2" create_args_wlan0="bssid wlanmode hostap country DE authmode wpa ssid COYOTE" create_args_wlan2="bssid wlanmode hostap country DE authmode wpa ssid COYOTE_GUEST" (no ifconfig_wlanX settings, I'm using a bridge for these, no hostapd!) /etc/rc.local: #!/bin/sh /etc/rc.d/hostapd start wlan0 sleep 2 /etc/rc.d/hostapd start wlan2 and I get: root@coyote:~# ifconfig wlan0; ifconfig wlan2 wlan0: flags=8943 metric 0 mtu 1500 ether 68:a3:c4:51:44:99 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE channel 13 (2472 MHz 11g) bssid 68:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs wlan2: flags=8943 metric 0 mtu 1500 ether 6e:a3:c4:51:44:99 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE_GUEST channel 13 (2472 MHz 11g) bssid 6e:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs root@coyote:~# pgrep -fl hostapd 3071 /usr/sbin/hostapd -P /var/run/hostapd-wlan2.pid -B /etc/hostapd-wlan2.conf 3061 /usr/sbin/hostapd -P /var/run/hostapd-wlan0.pid -B /etc/hostapd-wlan0.conf Now I need to un-bridge the wlan2, put in a firewalled guest network and tweak pf accordingly. Or maybe I'll use a pf-based filtering bridge. And I still need an USB fob for that 5GHz AP. Thanks! Uli 2013/10/21 Adrian Chadd : > So, I finally (!) figured out how this address cloning crap works. > > In if_ath.c, there's assign_address(). It, yes, assigns addresses. If the > hardware supports the bssid mask field and the clone flag is set, it sets up > multiple addresses. This works great for up to 4 MACs. We have to modify it > to support more than 4 MAC addresses per NIC. > > .. but, how do you set the clone flag? > > The ifconfig manpage has two entries for 'bssid'. > > * the first is when you 'create' a VAP. It's passed as an arguement during > create, but before wlanmode. It doesn't take an option. > * the second is for setting the BSS ID for the VAP. It _does_ take an option > (the MAC.) > > If you try this, it fails: > > * ifconfig wlan11 create wlandev ath0 wlanmode hostap ssid 'foo_2' bssid > > If you try this, it works: > > * ifconfig wlan11 create wlandev ath0 bssid wlanomde hostap ssid 'foo_2' > > So, if you run multi-VAP, and you want to use WPA on all of the VAPs, please > try using 'bssid' as above and ensure you get multiple MAC addresses. This > should make things behave much, much better. If it doesn't then we have > bigger problems. > > Thanks, > > > -adrian > From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 26 16:51:31 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 9291A92 for ; Sat, 26 Oct 2013 16:51:31 +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 519232785 for ; Sat, 26 Oct 2013 16:51:31 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id k18so2900325qcv.24 for ; Sat, 26 Oct 2013 09:51: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=tWKmaAkS3DJ+3jsShKrb+RS+VTNgWPUGJQPHdjj1YLY=; b=w0bt0cE/k8qMQjhqyLZC0JXXvVTA+BstRGK/C07m8fNRRbiNCKEo6S1SUN+DBi+Jzx L7YtPR03MEk/pv36xY+0yGIML/gN2ehuZbrx9PtQ51ry319vkZpXA4RDrvxvABcA4yYo TxpxAKvrrLV/56oXgnisWq/zEkggQqSCNMZ71xT8/oW9LhIID6V61pMnhWTC5kkAPn99 kAYZkpeH8gdHBsh/fp27iwfF0R8zbBA5XdVWJllHxH3DsmuKUn5dbrFtcTbNy5exB7Vl n7FRRO+euVq7Up332alpMUeb1sfR8W0llUi78SE0Bo+fEeak/TBMNKlnZh++ia/ujJTC ak0A== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr19026391qai.74.1382806290262; Sat, 26 Oct 2013 09:51:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sat, 26 Oct 2013 09:51:30 -0700 (PDT) In-Reply-To: References: Date: Sat, 26 Oct 2013 09:51:30 -0700 X-Google-Sender-Auth: yiyOxqCyrSNbDGaqMSHLVYC-2Cc Message-ID: Subject: Re: implementing multiple BSSID addresses for different VAPs, or 'why was the flag called bssid again?' From: Adrian Chadd To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Sat, 26 Oct 2013 16:51:31 -0000 Hi, It doesn't surprise me that the devd and rc.conf scripts seem to be clashing. I'd very much like to see this fixed. Would someone please take a crack at it? Thanks! -a On 26 October 2013 07:32, Ulrich Sp=F6rlein wrote: > Well, the following in rc.conf > > wlans_ath0=3D"wlan0 wlan2" > create_args_wlan0=3D"bssid wlanmode hostap country DE authmode wpa ssid > COYOTE" > ifconfig_wlan0=3D"ssid COYOTE mode 11g pureg up" > create_args_wlan2=3D"bssid wlanmode hostap country DE authmode wpa ssid > COYOTE_GUEST" > ifconfig_wlan2=3D"ssid COYOTE_GUEST mode 11g pureg up" > > Does not quite work, I'm left with: > > (from dmesg) > Setting hostname: coyote.spoerlein.net. > bridge0: Ethernet address: 02:ac:6e:56:db:00 > Created clone interfaces: bridge0. > wlan0: Ethernet address: 68:a3:c4:51:44:99 > wlan2: Ethernet address: 6e:a3:c4:51:44:99 > ifconfig: SIOCS80211: Device busy > ath0: stuck beacon; resetting (bmiss count 4) > > (not that there's no echo for creating wlan devices, that should maybe > be added?) > > Anyway, I thus get this: > > ath0: flags=3D8943 > metric 0 mtu 2290 > ether 68:a3:c4:51:44:99 > nd6 options=3D21 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > wlan0: flags=3D8d43 > metric 0 mtu 1500 > ether 68:a3:c4:51:44:99 > inet6 fe80::6aa3:c4ff:fe51:4499%wlan0 prefixlen 64 tentative > scopeid 0xa > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: no carrier > ssid COYOTE channel 7 (2442 MHz 11g) > regdomain ETSI country DE indoor ecm authmode WPA2/802.11i > privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 6= 0 > pureg protmode CTS wme burst dtimperiod 1 -dfs > wlan2: flags=3D8943 > metric 0 mtu 1500 > ether 6e:a3:c4:51:44:99 > inet6 fe80::6ca3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative > scopeid 0xb > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE_GUEST channel 7 (2442 MHz 11g) bssid 6e:a3:c4:51:44:9= 9 > regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXE= D > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme bur= st > dtimperiod 1 -dfs > > root@coyote:~# ifconfig ath0 > ath0: flags=3D8802 metric 0 mtu 2290 > ether 68:a3:c4:51:44:99 > nd6 options=3D21 > media: IEEE 802.11 Wireless Ethernet autoselect > (autoselect ) > status: no carrier > root@coyote:~# ifconfig wlan0 create wlandev ath0 bssid wlanmode > hostap country DE authmode wpa ssid COYOTE > root@coyote:~# ifconfig wlan0 > wlan0: flags=3D8943 > metric 0 mtu 1500 > ether 6a:a3:c4:51:44:99 > inet6 fe80::68a3:c4ff:fe51:4499%wlan0 prefixlen 64 tentative > scopeid 0xa > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE channel 13 (2472 MHz 11g) bssid 6a:a3:c4:51:44:99 > regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXE= D > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme bur= st > dtimperiod 1 -dfs > root@coyote:~# ifconfig wlan2 create wlandev ath0 bssid wlanmode > hostap country DE authmode wpa ssid COYOTE_GUEST > ifconfig: SIOCS80211: Device busy > Exit 1 > root@coyote:~# ifconfig wlan2 > wlan2: flags=3D8943 > metric 0 mtu 1500 > ether 6e:a3:c4:51:44:99 > inet6 fe80::6ca3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative > scopeid 0xb > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE_GUEST channel 13 (2472 MHz 11g) bssid 6e:a3:c4:51:44:= 99 > regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXE= D > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme bur= st > dtimperiod 1 -dfs > root@coyote:~# ifconfig wlan0; ifconfig wlan2 > wlan0: flags=3D8943 > metric 0 mtu 1500 > ether 6a:a3:c4:51:44:99 > inet6 fe80::68a3:c4ff:fe51:4499%wlan0 prefixlen 64 tentative > scopeid 0xa > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE channel 13 (2472 MHz 11g) bssid 6a:a3:c4:51:44:99 > regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXE= D > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme bur= st > dtimperiod 1 -dfs > wlan2: flags=3D8943 > metric 0 mtu 1500 > ether 6e:a3:c4:51:44:99 > inet6 fe80::6ca3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative > scopeid 0xb > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE_GUEST channel 13 (2472 MHz 11g) bssid 6e:a3:c4:51:44:= 99 > regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXE= D > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme bur= st > dtimperiod 1 -dfs > > > Then I also had to bounce the hostapd on wlan0 and start the one on > wlan2 and it looks very promising currently. Is it possible that there > is a timing issue involved and doing it manually works better than > when the startup scripts run through this? > > > I've now got this working version that seems to be solid and comes up > during boot w/o manual intervention. > > /etc/rc.conf: > wlans_ath0=3D"wlan0 wlan2" > create_args_wlan0=3D"bssid wlanmode hostap country DE authmode wpa ssid > COYOTE" > create_args_wlan2=3D"bssid wlanmode hostap country DE authmode wpa ssid > COYOTE_GUEST" > (no ifconfig_wlanX settings, I'm using a bridge for these, no hostapd!) > > /etc/rc.local: > #!/bin/sh > /etc/rc.d/hostapd start wlan0 > sleep 2 > /etc/rc.d/hostapd start wlan2 > > and I get: > > root@coyote:~# ifconfig wlan0; ifconfig wlan2 > wlan0: flags=3D8943 > metric 0 mtu 1500 > ether 68:a3:c4:51:44:99 > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE channel 13 (2472 MHz 11g) bssid 68:a3:c4:51:44:99 > regdomain ETSI country DE indoor ecm authmode WPA2/802.11i > privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 6= 0 > protmode CTS wme burst dtimperiod 1 -dfs > wlan2: flags=3D8943 > metric 0 mtu 1500 > ether 6e:a3:c4:51:44:99 > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid COYOTE_GUEST channel 13 (2472 MHz 11g) bssid 6e:a3:c4:51:44:= 99 > regdomain ETSI country DE indoor ecm authmode WPA2/802.11i > privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 6= 0 > protmode CTS wme burst dtimperiod 1 -dfs > root@coyote:~# pgrep -fl hostapd > 3071 /usr/sbin/hostapd -P /var/run/hostapd-wlan2.pid -B > /etc/hostapd-wlan2.conf > 3061 /usr/sbin/hostapd -P /var/run/hostapd-wlan0.pid -B > /etc/hostapd-wlan0.conf > > Now I need to un-bridge the wlan2, put in a firewalled guest network > and tweak pf accordingly. Or maybe I'll use a pf-based filtering > bridge. And I still need an USB fob for that 5GHz AP. > > Thanks! > Uli > > > 2013/10/21 Adrian Chadd : > > So, I finally (!) figured out how this address cloning crap works. > > > > In if_ath.c, there's assign_address(). It, yes, assigns addresses. If t= he > > hardware supports the bssid mask field and the clone flag is set, it > sets up > > multiple addresses. This works great for up to 4 MACs. We have to modif= y > it > > to support more than 4 MAC addresses per NIC. > > > > .. but, how do you set the clone flag? > > > > The ifconfig manpage has two entries for 'bssid'. > > > > * the first is when you 'create' a VAP. It's passed as an arguement > during > > create, but before wlanmode. It doesn't take an option. > > * the second is for setting the BSS ID for the VAP. It _does_ take an > option > > (the MAC.) > > > > If you try this, it fails: > > > > * ifconfig wlan11 create wlandev ath0 wlanmode hostap ssid 'foo_2' bssi= d > > > > If you try this, it works: > > > > * ifconfig wlan11 create wlandev ath0 bssid wlanomde hostap ssid 'foo_2= ' > > > > So, if you run multi-VAP, and you want to use WPA on all of the VAPs, > please > > try using 'bssid' as above and ensure you get multiple MAC addresses. > This > > should make things behave much, much better. If it doesn't then we have > > bigger problems. > > > > Thanks, > > > > > > -adrian > > >