From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 03:13:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA3987FF for ; Mon, 24 Feb 2014 03:13:18 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 68C4416A3 for ; Mon, 24 Feb 2014 03:13:18 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id j15so5648836qaq.39 for ; Sun, 23 Feb 2014 19:13:17 -0800 (PST) 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=j0TDtwdrosF7q6IbVa2SebQw4WykBR/0xXoHm2zvJxI=; b=vEUO/926WWmJx39OWk9+gaTDbw+ioR43FOWtFNYp5RwPepLRDuWTCpY4puF1MknMfw fWthmGJUUEPCpJKUlE9wgtfXbumpnn81Q2i0k8ht2xuTahWpznDZ8dcLmtBpZOjVQhI2 0jZ+nmpDiMqiIryYXehgvuJD6Sg4WRebX73T3jkpsRCa9MosXtFNSbiaqlS/Sgn60wmt dIdnZHtmoQY/tr0XhZXYxwI3Lf/7DjnfraBhQRg7Eum60wZA1DFfVeUQY9chxNhVXdWA kruMGbb3GR2QU3p3BiL87rXIqUKNZL+WqfWL1UlEEAi+xsGe59PQyBk5rOAqlrK6Atne oV7w== MIME-Version: 1.0 X-Received: by 10.140.50.131 with SMTP id s3mr25559218qga.12.1393211597005; Sun, 23 Feb 2014 19:13:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Sun, 23 Feb 2014 19:13:16 -0800 (PST) Date: Sun, 23 Feb 2014 19:13:16 -0800 X-Google-Sender-Auth: s3YFsH9M57HFVlubtCzv-tcv8g0 Message-ID: Subject: iwnstats and iwn debugging From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 03:13:18 -0000 hi, I've just added code to iwn on -HEAD to expose statistics via ioctl(). I then added a very barnjacked iwnstats in tools/iwn/ which will dump out the statistics from the firmware every 1/10th of a second. Now, I have no idea what most of the fields mean, so don't even start with questions like "what's X mean?" If it's not documented in the linux iwlwifi driver, I have no idea. I highly recommend people do some digging in Linux to help me figure out what each statistics field means. but, hopefully it'll help us figure out why things are busted. For example, I know now that my 6205 (with no bluetooth) is actually stomping frames due to bluetooth when there isn't actually any bluetooth - and that needs to be fixed. Gragh. Enjoy, -a From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 06:03:40 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 553EF92C; Mon, 24 Feb 2014 06:03:40 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 008301645; Mon, 24 Feb 2014 06:03:39 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id e16so1512010qcx.20 for ; Sun, 23 Feb 2014 22:03:39 -0800 (PST) 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=/iU3rVM1dwOuB3i2y8LBskaQk8fjnOQIp9Yzi+f3RNw=; b=WIkIB1ST8ccyAwHBZcF2zIksemJjHv7HKhNCD3OFFGUgjI9NG3O2EwMGCb0G4ZZb04 ZCon8xIR5iE6suNHILmeY31v1RFMHvaYU6p+lFKIICf1GAZFV+ikMxqs+Sp1cCUVkBy5 YgiidfEyndQaiWowGYFiRA8NvIk3CeCW1V6N6utHgMyVpk/zkOqXYGY1Zc/n2fGLhsFs viHsj5ccgvYFWQwYOrTscUmqGOvQXM8TByejrKYixrV6YEEw23Qz3Ja/o01UgDqW7WPy zw7+O0xkyp6a3wsBUNkastwQzFt3mkjIK0pLqlN2s/PuycQIJcqjDk7xiHsl7Wvf+FuY jFpQ== MIME-Version: 1.0 X-Received: by 10.140.93.130 with SMTP id d2mr25651457qge.41.1393221819204; Sun, 23 Feb 2014 22:03:39 -0800 (PST) Received: by 10.229.154.82 with HTTP; Sun, 23 Feb 2014 22:03:39 -0800 (PST) Date: Mon, 24 Feb 2014 10:03:39 +0400 Message-ID: Subject: WiFi configuration From: Michael BlackHeart To: freebsd-wireless@freebsd.org, freebsd-stable Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 06:03:40 -0000 Hello, I've got a question about configuring WiFi bridged networking in FreeBSD 10 Stable. The config info: *Ethernet and WiFi transparent bridged network *WiFi is protected via WPA2 *802.11n/ht WiFi FreeBSD Configuration: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" cloned_interfaces="bridge0" ifconfig_lo0="inet 127.0.0.1/8 mtu 9000" ifconfig_bridge0="inet 192.168.1.1/24 addm re1 addm wlan0 description LAN" ifconfig_re0="rxcsum txcsum tso -vlanhwtag -vlanmtu -vlanhwcsum description ToISP up" ifconfig_re1="description LAN_Ethernet" ifconfig_wlan0="ht channel 6:ht/20 country RU regdomain etsi -bgscan bintval 500" Hostapd from ports: In rc.conf hostapd_enable="YES" hostapd_program="/usr/local/sbin/hostapd" In /etc/hostapd.conf there's some stuff configured interface=wlan0 driver=bsd logger_syslog=-1 logger_syslog_level=4 logger_stdout=-1 logger_stdout_level=4 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=MIEKOFF.LOCAL country_code=RU ieee80211d=1 beacon_int=100 dtim_period=2 max_num_sta=10 rts_threshold=2347 fragm_threshold=2346 preamble=1 macaddr_acl=0 auth_algs=2 ignore_broadcast_ssid=0 wmm_enabled=1 wmm_ac_bk_cwmin=4 wmm_ac_bk_cwmax=10 wmm_ac_bk_aifs=7 wmm_ac_bk_txop_limit=0 wmm_ac_bk_acm=0 wmm_ac_be_aifs=3 wmm_ac_be_cwmin=4 wmm_ac_be_cwmax=10 wmm_ac_be_txop_limit=0 wmm_ac_be_acm=0 wmm_ac_vi_aifs=2 wmm_ac_vi_cwmin=3 wmm_ac_vi_cwmax=4 wmm_ac_vi_txop_limit=94 wmm_ac_vi_acm=0 wmm_ac_vo_aifs=2 wmm_ac_vo_cwmin=2 wmm_ac_vo_cwmax=3 wmm_ac_vo_txop_limit=47 wmm_ac_vo_acm=0 ap_max_inactivity=600 disassoc_low_ack=1 max_listen_interval=600 ap_isolate=0 ieee8021x=0 eap_server=0 wpa=2 wpa_psk=da55ab74e575db9fcfa6dca52dbe9c1d29cc8a216627b0360e91c4ff3a50b6f9 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP CCMP wpa_group_rekey=600 wpa_gmk_rekey=86400 rsn_preauth=1 disable_pmksa_caching=0 ap_table_max_size=255 ap_table_expiration_time=3600 time_advertisement=0 Question 1: Should I use hostapd from world or ports? Does it matter? Question 2: It seems than order of lines in rc.conf is important, e.g. if I place wifi before bridge there wolud be an error. Question 3: how should I configure WiFi device to be 802.11n/ht capable? When I place some args in "wlan_create" line they do not work or produce errors. e.g. if I place this: create_args_wlan0="wlanmode hostap ht channel 6:ht/20 country RU regdomain etsi mtu 2290" WiFi device would be not condigured due to unknown reason while system boots up. Question 4: I'd like to have increased MTU (2290), but when I try to add some MTU stuff to configuration, the bridge0 starts first, adds re1 with increased MTU and says that it cannot attach wlan0 with MTU 1500. Question 5: something happens with ht/40+. I just figure out how to configure wlan0 with ht/40+ at the boot time. When I add it to wlan_create nothing happens or error happens. Of couse each try breaks bridge0 and cuts me off so I have to log in directly - that's pain. Question 6: what sould I configure in hostapd.conf? Or what can I configure if I'd like to without disturbing wireless networking. -- amd_miek Think different. Just superior. From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 06:35:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E54ED8D; Mon, 24 Feb 2014 06:35:31 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BE5C518A6; Mon, 24 Feb 2014 06:35:30 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id f51so13804227qge.2 for ; Sun, 23 Feb 2014 22:35:29 -0800 (PST) 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=FYNZvs8LFSkmMvaxo60XS4hYOvbGFDnb9F5+7VZfZbw=; b=wt7pDsn9DL8gAACnrlM5weHsMLXQC2n7v25LEBVemzANWZShqo2bXoxAiXcjD7trL5 8eaaUVDgb0ASY0K0JO4nZDs2rBX8yvAFY7ufP31lyr5p+by0fg6PnCbRvNnO3xqqXbKQ HYpxQxNaaFv5eAPTCdfxnAiPHdEWGW4nMaFi6S93SXeC48sHLvrW+cfJl7sL98MensnJ Wfl89qxM49kIajJGR3nyXHQWGjFFVhyxTpLi4tKLbqOKMVFXPA6WNvW7qAJpeOhWs5Tp JNZ7CjMQX0MUYWovM+8q5U4T6XlSqGx3YqLFxwOJvmvK+8ZVTrdh5+gvAg8315rPTAQm CChw== MIME-Version: 1.0 X-Received: by 10.140.42.138 with SMTP id c10mr26275541qga.24.1393223729925; Sun, 23 Feb 2014 22:35:29 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Sun, 23 Feb 2014 22:35:29 -0800 (PST) In-Reply-To: References: Date: Sun, 23 Feb 2014 22:35:29 -0800 X-Google-Sender-Auth: JRDHndj8JT2aF4RxJG1yyDJ8V0M Message-ID: Subject: Re: WiFi configuration From: Adrian Chadd To: Michael BlackHeart Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , freebsd-stable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 06:35:31 -0000 Hi all you need is: interface=wlan0 driver=bsd ssid=CACHEBOY_11N_1 wpa=3 wpa_key_mgmt=WPA-PSK wpa_passphrase=PasswordGoesHere wpa_pairwise=CCMP ctrl_interface=/var/run/hostapd I haven't tried running the wifi with an mtu greater than the default (1500). Why are you trying to do this? you also don't need to say ht, it'll automatically do ht for you. -a From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 08:43:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 717D2AC1 for ; Mon, 24 Feb 2014 08:43:04 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 232FB1833 for ; Mon, 24 Feb 2014 08:43:03 +0000 (UTC) Received: from srg.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s1O8gcvq082991 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 24 Feb 2014 16:42:39 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <530B060F.8030204@FreeBSD.org> Date: Mon, 24 Feb 2014 16:42:55 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Alex Deiter Subject: Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode References: <63a130f264cbfb29dc3fd34ab3170447.squirrel@mx.waitman.net> <53041318.6090303@FreeBSD.org> In-Reply-To: <53041318.6090303@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------070708040301060900090202" Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 08:43:04 -0000 This is a multi-part message in MIME format. --------------070708040301060900090202 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2014/02/19 10:12, Kevin Lo wrote: > On 2014/02/18 14:17, Alex Deiter wrote: >> Hello, > > Hi Alex, > >> >> Thank you for your advice! >> I found a workaround: >> >> # ifconfig wlan0 create wlandev run0 >> >> then wait 5 minutes ;-) >> >> and only thereafter: >> >> # ifconfig wlan0 up >> >> run0: <1.0> on usbus1 >> run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address >> 30:85:a9:f4:52:bd >> uhid0: on >> usbus1 >> wlan0: Ethernet address: 30:85:a9:f4:52:bd >> run0: firmware RT3071 ver. 0.33 loaded >> >> But found another issue: ifconfig wlan0 list scan command does not >> show any >> results: >> >> root@test:~ # ifconfig wlan0 list scan >> root@test:~ # >> >> root@test:~ # wlandebug -i wlan0 scan >> net.wlan.0.debug: 0x0 => 0x200000 >> >> wlan0: sta_pick_bss: no scan candidate >> wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend >> 2147963261] >> wlan0: scan_task: chan 140a -> 1g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 1g -> 6g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 6g -> 11g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 11g -> 7g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 7g -> 52a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 52a -> 56a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 56a -> 60a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 60a -> 64a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 64a -> 36a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 36a -> 40a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 40a -> 44a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 44a -> 48a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 48a -> 2g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 2g -> 3g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 3g -> 4g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 4g -> 5g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 5g -> 8g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 8g -> 9g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 9g -> 10g [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 10g -> 149a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms] >> wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms] >> wlan0: sta_pick_bss: no scan candidate > > I have an ZyxXEL NWD2705 working fine. It has the exact same chipset as > the ASUS USB-N66. So far I haven't been able to come up with a good > solution to your problem. I purchased the ASUS USB-N66 and will arrive > in the next couple of days. Hope I could find a new interesting bug :-) After r258363, I forgot to add a flag to run's device list which uses a standard scsi eject. The ASUS USB-N66 has been tested to work on my laptop. The attached patch should fix your problem :-) Please test it, thanks. Kevin --------------070708040301060900090202 Content-Type: text/plain; charset=UTF-8; name="patch-if_run" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch-if_run" Index: sys/dev/usb/wlan/if_run.c =================================================================== --- sys/dev/usb/wlan/if_run.c (revision 262433) +++ sys/dev/usb/wlan/if_run.c (working copy) @@ -100,7 +100,8 @@ SYSCTL_INT(_hw_usb_run, OID_AUTO, debug, CTLFLAG_R static const STRUCT_USB_HOST_ID run_devs[] = { #define RUN_DEV(v,p) { USB_VP(USB_VENDOR_##v, USB_PRODUCT_##v##_##p) } #define RUN_DEV_EJECT(v,p) \ - { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, 0) } + { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, RUN_EJECT) } +#define RUN_EJECT 1 RUN_DEV(ABOCOM, RT2770), RUN_DEV(ABOCOM, RT2870), RUN_DEV(ABOCOM, RT3070), @@ -315,7 +316,7 @@ static const STRUCT_USB_HOST_ID run_devs[] = { RUN_DEV(ZINWELL, RT3072_2), RUN_DEV(ZYXEL, RT2870_1), RUN_DEV(ZYXEL, RT2870_2), - RUN_DEV(ZYXEL, NWD2705), + RUN_DEV_EJECT(ZYXEL, NWD2705), RUN_DEV_EJECT(RALINK, RT_STOR), #undef RUN_DEV_EJECT #undef RUN_DEV @@ -707,6 +708,8 @@ run_attach(device_t self) device_set_usb_desc(self); sc->sc_udev = uaa->device; sc->sc_dev = self; + if (USB_GET_DRIVER_INFO(uaa) != RUN_EJECT) + sc->sc_flags |= RUN_FLAG_FWLOAD_NEEDED; mtx_init(&sc->sc_mtx, device_get_nameunit(sc->sc_dev), MTX_NETWORK_LOCK, MTX_DEF); @@ -1151,7 +1154,7 @@ run_load_microcode(struct run_softc *sc) } /* write microcode image */ - if (sc->mac_ver != 0x3593) { + if (sc->sc_flags & RUN_FLAG_FWLOAD_NEEDED) { run_write_region_1(sc, RT2870_FW_BASE, base, 4096); run_write(sc, RT2860_H2M_MAILBOX_CID, 0xffffffff); run_write(sc, RT2860_H2M_MAILBOX_STATUS, 0xffffffff); Index: sys/dev/usb/wlan/if_runvar.h =================================================================== --- sys/dev/usb/wlan/if_runvar.h (revision 262433) +++ sys/dev/usb/wlan/if_runvar.h (working copy) @@ -154,6 +154,11 @@ struct run_softc { device_t sc_dev; struct usb_device *sc_udev; struct ifnet *sc_ifp; + int sc_need_fwload; + + int sc_flags; +#define RUN_FLAG_FWLOAD_NEEDED 0x01 + uint16_t wcid_stats[RT2870_WCID_MAX + 1][3]; #define RUN_TXCNT 0 #define RUN_SUCCESS 1 --------------070708040301060900090202-- From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 08:56:40 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A109A7; Mon, 24 Feb 2014 08:56:40 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 06B4B192B; Mon, 24 Feb 2014 08:56:39 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id c9so8581100qcz.1 for ; Mon, 24 Feb 2014 00:56:39 -0800 (PST) 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=/HR5kVXJ2BBb6dsE4ynQORZ4xzOvqSqoQOJaSazB8Jk=; b=iAmr7PU8L9xiKNMwZRZuJ9OeU1EBBd0iNmW5mvX/OE5kl1K8cZmRjjAIgOF68OGCfN gQUXM6aVCcB9UXubpDHXvPCI3+wAm0feiDsmBAGLv6PpQwuPDQ1oobmMXlgCQUsh3OTP RP9Q/s7jQcbPrdJQ78dpBjb9H/jg7rZNJRY2DwPuKRC8gmvpgLWQOJpTUIv05MKWA+Jt U7ZzXZOc45ocjZ6Jw2HBPXTvKoZUqixphor854MiydwX+qFecP+86gfu5mjA2MzRSkSM W38+7mbZfwKuPwJ5oRz4hWV5TiaSwCtASWc9LaJjA3QrUkiQruZRhE1TbWYvyxHr4kyM Wwhg== MIME-Version: 1.0 X-Received: by 10.140.50.46 with SMTP id r43mr26531577qga.22.1393232199195; Mon, 24 Feb 2014 00:56:39 -0800 (PST) Received: by 10.229.154.82 with HTTP; Mon, 24 Feb 2014 00:56:39 -0800 (PST) In-Reply-To: References: Date: Mon, 24 Feb 2014 12:56:39 +0400 Message-ID: Subject: Re: WiFi configuration From: Michael BlackHeart To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-wireless@freebsd.org" , freebsd-stable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 08:56:40 -0000 2014-02-24 10:35 GMT+04:00 Adrian Chadd : > Hi > > all you need is: > > interface=wlan0 > driver=bsd > ssid=CACHEBOY_11N_1 > wpa=3 > wpa_key_mgmt=WPA-PSK > wpa_passphrase=PasswordGoesHere > wpa_pairwise=CCMP > ctrl_interface=/var/run/hostapd > > > I haven't tried running the wifi with an mtu greater than the default > (1500). Why are you trying to do this? > > As far I understand MTU 2290 is native to wireless/ath/freebsd driver. Look at this ath0: flags=8843 metric 0 mtu 2290 ether cc:b2:55:00:68:1f media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running But when freebsd creates wlan0 it's lowered to 1500. I tried with another ath WiFi card this way - worked fine with 2290 MTU in a bridge. BTW 2290 is max value, but it seems than noone looked into wifi MTU under freebsd, theoretically it could be about 7k to 9k - normal jumbo frame. 2290 is some kinda way of baby jumbo frames - they're slightly bigger than 1.5k. So next is the bridge. By default bridge uses the MTU of a first member, so if it will be a stock ethernet i-face so it'll be again 1500. If you're asking me why am I to use increased MTU - I see it reasonable. > you also don't need to say ht, it'll automatically do ht for you. > > -a > -- amd_miek Think different. Just superior. From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 11:07:00 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE089B71 for ; Mon, 24 Feb 2014 11:07:00 +0000 (UTC) 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 8B7D21638 for ; Mon, 24 Feb 2014 11:07:00 +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 s1OB70Sd027749 for ; Mon, 24 Feb 2014 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1OB6xd7027744 for freebsd-wireless@FreeBSD.org; Mon, 24 Feb 2014 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Feb 2014 11:06:59 GMT Message-Id: <201402241106.s1OB6xd7027744@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.17 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, 24 Feb 2014 11:07:00 -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/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 192 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 15:53:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 54B234F2; Mon, 24 Feb 2014 15:53:49 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 004BC166B; Mon, 24 Feb 2014 15:53:48 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id e16so2158939qcx.6 for ; Mon, 24 Feb 2014 07:53:48 -0800 (PST) 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=6Py68FAz+5na1XPGLabNRnu3MnZFfT5S0Ndy8DxGTek=; b=KLVyd+QwHPO+M+h4vJcP94s/scgd7tyMoLohKz+jAIA5Dawd6y3F24JBxgQNiiZijy y9WqNlSM2DcCXm4LatHKh/XTpbPvcDEDBuNEObLO7K3PM375DrbZYfauVpVQCHgWecPJ K3cTmXEUme6rR6UuInDkRe1yAh+rFsmCJP+kPbVOaLHwaB7NaKize2TkIJBZEyTkwFJR gQ/VLXYVOauaR9txhyCb/lI92EahNURRsbbsnyfdVl7oiBrEjZnTy0DuhxtDaJSbVNkY gjZvYS8gz/tZLpPhX2PQvDyH2Ndsg4L/D6nnZTnwWDyM2ANYs/rdaGgcC6gVXq9un46T S/wg== MIME-Version: 1.0 X-Received: by 10.224.121.137 with SMTP id h9mr31083234qar.55.1393257228239; Mon, 24 Feb 2014 07:53:48 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Mon, 24 Feb 2014 07:53:48 -0800 (PST) In-Reply-To: References: Date: Mon, 24 Feb 2014 07:53:48 -0800 X-Google-Sender-Auth: b-W2tfpKyivbrrhoH_Mzgt70jUQ Message-ID: Subject: Re: WiFi configuration From: Adrian Chadd To: Michael BlackHeart Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , freebsd-stable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 15:53:49 -0000 Hi, It's a hold-over from what wifi will let you get away with. Just stick to 1500 and let the 802.11n A-MPDU aggregate things as appropriate. -a On 24 February 2014 00:56, Michael BlackHeart wrote: > > > > 2014-02-24 10:35 GMT+04:00 Adrian Chadd : > >> Hi >> >> all you need is: >> >> interface=wlan0 >> driver=bsd >> ssid=CACHEBOY_11N_1 >> wpa=3 >> wpa_key_mgmt=WPA-PSK >> wpa_passphrase=PasswordGoesHere >> wpa_pairwise=CCMP >> ctrl_interface=/var/run/hostapd >> >> >> I haven't tried running the wifi with an mtu greater than the default >> (1500). Why are you trying to do this? >> > > As far I understand MTU 2290 is native to wireless/ath/freebsd driver. > > Look at this > ath0: flags=8843 metric 0 mtu 2290 > ether cc:b2:55:00:68:1f > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running > > But when freebsd creates wlan0 it's lowered to 1500. I tried with another > ath WiFi card this way - worked fine with 2290 MTU in a bridge. BTW 2290 is > max value, but it seems than noone looked into wifi MTU under freebsd, > theoretically it could be about 7k to 9k - normal jumbo frame. 2290 is some > kinda way of baby jumbo frames - they're slightly bigger than 1.5k. > > So next is the bridge. By default bridge uses the MTU of a first member, so > if it will be a stock ethernet i-face so it'll be again 1500. > > If you're asking me why am I to use increased MTU - I see it reasonable. > >> >> you also don't need to say ht, it'll automatically do ht for you. >> >> -a > > > > > -- > amd_miek > Think different. > Just superior. From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 24 16:58:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F05B174C; Mon, 24 Feb 2014 16:58:09 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 588071C72; Mon, 24 Feb 2014 16:58:09 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id f8so3339992wiw.7 for ; Mon, 24 Feb 2014 08:58:07 -0800 (PST) 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=Vvcu/n24ddQfSuG8RJIifmGyzmaEtmQEeCank9+0ufo=; b=AJhwWOh1HCf0DAamrX9ZJoIV4Daf818wvauhhRiZz8RKrSwwucBj7G0kLqhU/1/5ZP LWC1XR+cnet5X7S2U40VdguVtYt7rBu77bfh3ZL0UaYLJ5CmBZHctRCOiBfBykjWrmUy X1aMJNn8UDBOkaJHcQpedye8NAx+zPOp8DDhn+RiJiNIBE3qObmmCTvyk4HVcTSiO5tc UaDTCVMCElrriTwfuCzmGb5ntz2VnFiutiZv2ybeVevxmzTyglAW+9Hul8MhOuuiE4IR Gb40k0/SgLyoB35ayz9Gz5Vx7vnPedIr1f8N5fiDa61O66HUWq7CZ1A3C1Tfd2u/NO1Y usjw== MIME-Version: 1.0 X-Received: by 10.180.96.102 with SMTP id dr6mr15406902wib.19.1393261087585; Mon, 24 Feb 2014 08:58:07 -0800 (PST) Received: by 10.217.119.132 with HTTP; Mon, 24 Feb 2014 08:58:07 -0800 (PST) In-Reply-To: <530B060F.8030204@FreeBSD.org> References: <63a130f264cbfb29dc3fd34ab3170447.squirrel@mx.waitman.net> <53041318.6090303@FreeBSD.org> <530B060F.8030204@FreeBSD.org> Date: Mon, 24 Feb 2014 20:58:07 +0400 Message-ID: Subject: Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode From: Alex Deiter To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 24 Feb 2014 16:58:10 -0000 Hello Kevin, Thank you very much! Successfully tested! 2014-02-24 12:42 GMT+04:00 Kevin Lo : > On 2014/02/19 10:12, Kevin Lo wrote: > >> On 2014/02/18 14:17, Alex Deiter wrote: >> >>> Hello, >>> >> >> Hi Alex, >> >> >>> Thank you for your advice! >>> I found a workaround: >>> >>> # ifconfig wlan0 create wlandev run0 >>> >>> then wait 5 minutes ;-) >>> >>> and only thereafter: >>> >>> # ifconfig wlan0 up >>> >>> run0: <1.0> on usbus1 >>> run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address >>> 30:85:a9:f4:52:bd >>> uhid0: on >>> usbus1 >>> wlan0: Ethernet address: 30:85:a9:f4:52:bd >>> run0: firmware RT3071 ver. 0.33 loaded >>> >>> But found another issue: ifconfig wlan0 list scan command does not show >>> any >>> results: >>> >>> root@test:~ # ifconfig wlan0 list scan >>> root@test:~ # >>> >>> root@test:~ # wlandebug -i wlan0 scan >>> net.wlan.0.debug: 0x0 => 0x200000 >>> >>> wlan0: sta_pick_bss: no scan candidate >>> wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend >>> 2147963261] >>> wlan0: scan_task: chan 140a -> 1g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 1g -> 6g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 6g -> 11g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 11g -> 7g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 7g -> 52a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 52a -> 56a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 56a -> 60a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 60a -> 64a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 64a -> 36a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 36a -> 40a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 40a -> 44a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 44a -> 48a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 48a -> 2g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 2g -> 3g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 3g -> 4g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 4g -> 5g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 5g -> 8g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 8g -> 9g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 9g -> 10g [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 10g -> 149a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms] >>> wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms] >>> wlan0: sta_pick_bss: no scan candidate >>> >> >> I have an ZyxXEL NWD2705 working fine. It has the exact same chipset as >> the ASUS USB-N66. So far I haven't been able to come up with a good >> solution to your problem. I purchased the ASUS USB-N66 and will arrive >> in the next couple of days. Hope I could find a new interesting bug :-) >> > > After r258363, I forgot to add a flag to run's device list which uses a > standard scsi eject. The ASUS USB-N66 has been tested to work on my > laptop. > The attached patch should fix your problem :-) Please test it, thanks. > > Kevin > -- Alex Deiter From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 25 01:43:28 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64288D50 for ; Tue, 25 Feb 2014 01:43:28 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F083E1FD7 for ; Tue, 25 Feb 2014 01:43:27 +0000 (UTC) Received: from srg.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s1P1h57A090787 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 25 Feb 2014 09:43:06 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <530BF53C.7050607@FreeBSD.org> Date: Tue, 25 Feb 2014 09:43:24 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Alex Deiter Subject: Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode References: <63a130f264cbfb29dc3fd34ab3170447.squirrel@mx.waitman.net> <53041318.6090303@FreeBSD.org> <530B060F.8030204@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 25 Feb 2014 01:43:28 -0000 Cool! I committed a fix in r262465, thanks. Kevin On 2014/02/25 00:58, Alex Deiter wrote: > Hello Kevin, > > Thank you very much! > Successfully tested! > > > 2014-02-24 12:42 GMT+04:00 Kevin Lo : > >> On 2014/02/19 10:12, Kevin Lo wrote: >> >>> On 2014/02/18 14:17, Alex Deiter wrote: >>> >>>> Hello, >>>> >>> Hi Alex, >>> >>> >>>> Thank you for your advice! >>>> I found a workaround: >>>> >>>> # ifconfig wlan0 create wlandev run0 >>>> >>>> then wait 5 minutes ;-) >>>> >>>> and only thereafter: >>>> >>>> # ifconfig wlan0 up >>>> >>>> run0: <1.0> on usbus1 >>>> run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address >>>> 30:85:a9:f4:52:bd >>>> uhid0: on >>>> usbus1 >>>> wlan0: Ethernet address: 30:85:a9:f4:52:bd >>>> run0: firmware RT3071 ver. 0.33 loaded >>>> >>>> But found another issue: ifconfig wlan0 list scan command does not show >>>> any >>>> results: >>>> >>>> root@test:~ # ifconfig wlan0 list scan >>>> root@test:~ # >>>> >>>> root@test:~ # wlandebug -i wlan0 scan >>>> net.wlan.0.debug: 0x0 => 0x200000 >>>> >>>> wlan0: sta_pick_bss: no scan candidate >>>> wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend >>>> 2147963261] >>>> wlan0: scan_task: chan 140a -> 1g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 1g -> 6g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 6g -> 11g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 11g -> 7g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 7g -> 52a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 52a -> 56a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 56a -> 60a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 60a -> 64a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 64a -> 36a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 36a -> 40a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 40a -> 44a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 44a -> 48a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 48a -> 2g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 2g -> 3g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 3g -> 4g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 4g -> 5g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 5g -> 8g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 8g -> 9g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 9g -> 10g [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 10g -> 149a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms] >>>> wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms] >>>> wlan0: sta_pick_bss: no scan candidate >>>> >>> I have an ZyxXEL NWD2705 working fine. It has the exact same chipset as >>> the ASUS USB-N66. So far I haven't been able to come up with a good >>> solution to your problem. I purchased the ASUS USB-N66 and will arrive >>> in the next couple of days. Hope I could find a new interesting bug :-) >>> >> After r258363, I forgot to add a flag to run's device list which uses a >> standard scsi eject. The ASUS USB-N66 has been tested to work on my >> laptop. >> The attached patch should fix your problem :-) Please test it, thanks. >> >> Kevin >> > > From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 27 20:13:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BD26BEC; Thu, 27 Feb 2014 20:13:53 +0000 (UTC) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EA1B31143; Thu, 27 Feb 2014 20:13:52 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id w7so154543qcr.36 for ; Thu, 27 Feb 2014 12:13:52 -0800 (PST) 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=/Jl5oDU0+tgNvbyhjw9VxrUbJCbLvm+UcDCvNt6klDY=; b=PQqOuZ6eDYK2enkv2iYFCd5Gn1cb47k8NvlvzBEihWZWrn8t6FM6TnCBBzcebOKgm7 3KHCf+mr69fLym+Pyrke5xUNDtgmhkVU9M7MqfdK5sfi2wo+xFCbUpt5CT5nAdnn99G4 coPK2GQgnvSPz/rgKDGlHQnAgUrC8wR2ht+3siOjAtKKUgHOe6tcG/g6BHvFqZKuUERA 5OEKiLKZm1ew3MXGPpEjkZz/WBHfsT+iyI2qom7r4k8bk60YIqFMn+2bmLaI9EJlfU7R icAbJvwULWJt6/HGd4gSWGHlpNoK7K9fT7o/5/6YAdIgyHT++A/TpmLQKvlw6v4mMf7l 6JqA== MIME-Version: 1.0 X-Received: by 10.140.96.180 with SMTP id k49mr10139603qge.4.1393532031993; Thu, 27 Feb 2014 12:13:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Thu, 27 Feb 2014 12:13:51 -0800 (PST) In-Reply-To: <530EEEA5.4090306@shurik.kiev.ua> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> Date: Thu, 27 Feb 2014 12:13:51 -0800 X-Google-Sender-Auth: PfxPw9hInH-Tz3HKtxKagH1FS2I Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Alexandr Content-Type: text/plain; charset=ISO-8859-1 Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 27 Feb 2014 20:13:53 -0000 On 26 February 2014 23:52, Alexandr wrote: > Tom, could you: > > 1. compile kernel WITH_IWNDEBUG > 2. sysctl dev.iwn.0.debug=0x1 > 3. wlandebug -i wlan0 auth+assoc > 4. Associate with AP in 11n mode > 5. Send us appropriate /var/log/messages > > Then I try to compare it with my log. Please do. I've been trying to track down the source of this "ht just doesn't work!" but it works fine with all of the Intel NICs I have here. Can someone see if they can find a mtaching NIC online (amazon,ebay?) Owning one that I can whack in a laptop is likely going ot help things a lot. Thanks, -a From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 28 03:40:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1ED9600; Fri, 28 Feb 2014 03:40:27 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A72218C5; Fri, 28 Feb 2014 03:40:27 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id m5so147897qaj.39 for ; Thu, 27 Feb 2014 19:40:26 -0800 (PST) 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=Zc6VSu0iTK+2QYJGb3sMBI33vt4Xgq4YsfwBQdxBI5I=; b=uWiZf7ZuwjSAhcOqL2WJKJT3iC7BJyhjtiH1naNwAHnLxYopaErRFvGrCbe/YmGpCR VXj0zTjz9bz6s3Ol76RIg/Fb0k6zQLEVutLKffoB8ExHlfPbnuyZa6hA4zLDOa0DKguc VxuX8DH9GDfz0SLW76XuTy2JPBWuznZ5aVNDjk1Inxaj8cLv3OA2iVy2myShXQJG1GgF K7CsZXKMuuKvXHvu8zXVc2yrhHSvsi/bAinC8nWEvozADKHEJLNRIZb+gaN1j6BZPyA/ /Xg7MzLDH0LHmzUlgcNaLVojnr4OUjlzFVeXeURoYehxzkv1xeCbdiZC27e8H74XN8Dh 8xxA== MIME-Version: 1.0 X-Received: by 10.224.173.1 with SMTP id n1mr705436qaz.48.1393558826727; Thu, 27 Feb 2014 19:40:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Thu, 27 Feb 2014 19:40:26 -0800 (PST) In-Reply-To: <24791.1393550277@elam.kais.kyoto-u.ac.jp> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> Date: Thu, 27 Feb 2014 19:40:26 -0800 X-Google-Sender-Auth: WFLDZuChT64EyGT6XqxDEtHipxU Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 28 Feb 2014 03:40:28 -0000 Hi, Yes there are issues; I'm too busy to try and chase them down. I'd appreciate some help in chasing down why things are unhappy. Thanks, -a On 27 February 2014 17:17, Kaho Toshikazu wrote: > Hello, -current members > > I have a similar problem with Centrino Wireless-N 1000. > It operated until r257951 and have a trouble after r258030. > I use r262433 kernel with sys/dev/iwn reverted to r257951 > and changed from IEEE80211_FC1_WEP to EEE80211_FC1_PROTECTED. > > r262422 if_iwn module with IWN_DEBUG in opt_iwn.h and dev.iwn.0.debug=1 says: > > -- output of `dmesg -a` -- > iwn0: mem 0xd2500000-0xd2501fff irq 19 at device 0.0 on pci2 > wlan0: Ethernet address: 00:1e:64:45:f5:64 > iwn0: iwn_setregdomain: invalid channel 8 freq 2447/0x20480 > iwn_notif_intr: scanning channel 1 status 1 > iwn_notif_intr: scanning channel 6 status 1 > iwn_notif_intr: scanning channel 11 status 1 > iwn_notif_intr: scanning channel 7 status 1 > iwn_notif_intr: scanning channel 13 status 1 > iwn_notif_intr: scanning channel 2 status 1 > iwn_notif_intr: scanning channel 3 status 1 > iwn_notif_intr: scanning channel 4 status 1 > iwn_notif_intr: scanning channel 5 status 1 > iwn_notif_intr: scanning channel 8 status 1 > iwn_notif_intr: scanning channel 9 status 1 > iwn_notif_intr: scanning channel 10 status 1 > iwn_notif_intr: scanning channel 12 status 1 > iwn_tx_data_raw: qid 3 idx 0 len 6 nsegs 1 > iwn5000_tx_done: qid 3 idx 0 retries 0 nkill 0 rate 420a duration 778 status 201 > iwn_tx_data_raw: qid 3 idx 1 len 86 nsegs 1 > iwn5000_tx_done: qid 3 idx 1 retries 0 nkill 0 rate 420a duration 1418 status 201 > iwn_set_link_quality: 1stream antenna=0x01, 2stream antenna=0x03, ntxstreams=1 > iwn_set_link_quality: i=0, txrate=7, rate=0x87 > iwn_set_link_quality: i=1, txrate=6, rate=0x86 > iwn_set_link_quality: i=2, txrate=5, rate=0x85 > iwn_set_link_quality: i=3, txrate=4, rate=0x84 > iwn_set_link_quality: i=4, txrate=3, rate=0x83 > iwn_set_link_quality: i=5, txrate=2, rate=0x82 > iwn_set_link_quality: i=6, txrate=1, rate=0x81 > iwn_set_link_quality: i=7, txrate=0, rate=0x80 > iwn_set_link_quality: i=8, txrate=0, rate=0x80 > iwn_set_link_quality: i=9, txrate=0, rate=0x80 > iwn_set_link_quality: i=10, txrate=0, rate=0x80 > iwn_set_link_quality: i=11, txrate=0, rate=0x80 > iwn_set_link_quality: i=12, txrate=0, rate=0x80 > iwn_set_link_quality: i=13, txrate=0, rate=0x80 > iwn_set_link_quality: i=14, txrate=0, rate=0x80 > iwn_set_link_quality: i=15, txrate=0, rate=0x80 > wlan0: link state changed to UP > iwn0: iwn_intr: fatal firmware error > firmware error log: > error type = "SYSASSERT" (0x00000005) > program counter = 0x00018DBC > source line = 0x00000032 > error data = 0x0000000100000000 > branch link = 0x00018D6E00018D6E > interrupt link = 0x0000082600000000 > time = 1043083265 > driver status: > tx ring 0: qid=0 cur=0 queued=0 > tx ring 1: qid=1 cur=0 queued=0 > tx ring 2: qid=2 cur=0 queued=0 > tx ring 3: qid=3 cur=2 queued=0 > tx ring 4: qid=4 cur=57 queued=0 > tx ring 5: qid=5 cur=0 queued=0 > tx ring 6: qid=6 cur=0 queued=0 > tx ring 7: qid=7 cur=0 queued=0 > tx ring 8: qid=8 cur=0 queued=0 > tx ring 9: qid=9 cur=0 queued=0 > tx ring 10: qid=10 cur=0 queued=0 > tx ring 11: qid=11 cur=0 queued=0 > tx ring 12: qid=12 cur=0 queued=0 > tx ring 13: qid=13 cur=0 queued=0 > tx ring 14: qid=14 cur=0 queued=0 > tx ring 15: qid=15 cur=0 queued=0 > tx ring 16: qid=16 cur=0 queued=0 > tx ring 17: qid=17 cur=0 queued=0 > tx ring 18: qid=18 cur=0 queued=0 > tx ring 19: qid=19 cur=0 queued=0 > rx ring: cur=55 > > -- output of `pciconf -lvcb` -- > iwn0@pci0:2:0:0: class=0x028000 card=0x13058086 chip=0x00838086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Centrino Wireless-N 1000 [Condor Peak]' > class = network > bar [10] = type Memory, range 64, base 0xd2500000, size 8192, enabled > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR link x1(x1) > speed 2.5(2.5) ASPM L1(L0s/L1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 3 corrected > ecap 0003[140] = Serial 1 001e64ffff45f564 > > -- > Kaho Toshikazu > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 28 23:07:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB2BEFE7; Fri, 28 Feb 2014 23:07:19 +0000 (UTC) Received: from mx1.pertho.net (87-194-102-137.bethere.co.uk [87.194.102.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 780A612EF; Fri, 28 Feb 2014 23:07:16 +0000 (UTC) Received: from syn.pertho.net (syn [10.0.29.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tom) by syn.pertho.net (Postfix) with ESMTPSA id 5501D1D449D; Fri, 28 Feb 2014 23:07:07 +0000 (GMT) Date: Fri, 28 Feb 2014 23:07:05 +0000 From: Tom Murphy To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140228230705.GA28290@syn.pertho.net> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: Cc: freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 28 Feb 2014 23:07:20 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I've attached my iwn debug messages to this email starting with the point I tried to associate to the Wifi. Thanks again for looking at this! Kind regards, Tom On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote: > On 26 February 2014 23:52, Alexandr wrote: > > Tom, could you: > > > > 1. compile kernel WITH_IWNDEBUG > > 2. sysctl dev.iwn.0.debug=0x1 > > 3. wlandebug -i wlan0 auth+assoc > > 4. Associate with AP in 11n mode > > 5. Send us appropriate /var/log/messages > > > > Then I try to compare it with my log. > > Please do. I've been trying to track down the source of this "ht just > doesn't work!" but it works fine with all of the Intel NICs I have > here. > > Can someone see if they can find a mtaching NIC online (amazon,ebay?) > Owning one that I can whack in a laptop is likely going ot help things > a lot. > > Thanks, > > > -a --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="iwn_debug_messages.txt" Feb 28 22:55:20 kernel: wlan0: Ethernet address: 0c:d2:92:0e:aa:e2 Feb 28 22:55:20 wpa_supplicant[2424]: Successfully initialized wpa_supplicant Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:55:20 wpa_supplicant[2423]: Successfully initialized wpa_supplicant Feb 28 22:55:20 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Device not configured Feb 28 22:55:20 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:55:20 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:55:20 wpa_supplicant[2426]: wlan0: Trying to associate with a0:f3:c1:35:a3:6c (SSID='pertho' freq=2462 MHz) Feb 28 22:55:20 wpa_supplicant[2425]: wlan0: Trying to associate with a0:f3:c1:35:a3:6c (SSID='pertho' freq=2462 MHz) Feb 28 22:55:21 kernel: iwn_tx_data_raw: qid 3 idx 0 len 6 nsegs 1 Feb 28 22:55:21 kernel: iwn_tx_data_raw: qid 3 idx 1 len 6 nsegs 1 Feb 28 22:55:21 kernel: iwn5000_tx_done: qid 3 idx 0 retries 0 nkill 0 rate 420a duration 778 status 201 Feb 28 22:55:21 kernel: iwn5000_tx_done: qid 3 idx 1 retries 0 nkill 0 rate 420a duration 778 status 201 Feb 28 22:55:21 kernel: iwn_tx_data_raw: qid 3 idx 2 len 87 nsegs 1 Feb 28 22:55:21 kernel: iwn5000_tx_done: qid 3 idx 2 retries 0 nkill 0 rate 420a duration 1426 status 201 Feb 28 22:55:21 kernel: iwn_set_link_quality: 1stream antenna=0x01, 2stream antenna=0x03, ntxstreams=1 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=0, txrate=7, rate=0x87 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=1, txrate=6, rate=0x86 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=2, txrate=5, rate=0x85 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=3, txrate=4, rate=0x84 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=4, txrate=3, rate=0x83 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=5, txrate=2, rate=0x82 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=6, txrate=1, rate=0x81 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=7, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=8, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=9, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=10, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=11, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=12, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=13, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=14, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: iwn_set_link_quality: i=15, txrate=0, rate=0x80 Feb 28 22:55:21 kernel: wlan0: link state changed to UP Feb 28 22:55:21 wpa_supplicant[2425]: wlan0: Associated with a0:f3:c1:35:a3:6c Feb 28 22:55:21 wpa_supplicant[2426]: wlan0: Associated with a0:f3:c1:35:a3:6c Feb 28 22:55:21 dhclient[2746]: send_packet: No buffer space available Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 3 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 4 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 3 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 4 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 5 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 6 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 5 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 6 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 7 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 8 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 7 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 8 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:27 dhclient[2746]: send_packet: No buffer space available Feb 28 22:55:32 wpa_supplicant[2425]: wlan0: Authentication with a0:f3:c1:35:a3:6c timed out. Feb 28 22:55:32 kernel: iwn_tx_data_raw: qid 3 idx 9 len 2 nsegs 1 Feb 28 22:55:32 wpa_supplicant[2425]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:35:a3:6c reason=3 locally_generated=1 Feb 28 22:55:32 wpa_supplicant[2425]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Feb 28 22:55:32 wpa_supplicant[2425]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pertho" auth_failures=1 duration=10 Feb 28 22:55:32 kernel: wlan0: link state changed to DOWN Feb 28 22:55:32 wpa_supplicant[2426]: wlan0: Authentication with a0:f3:c1:35:a3:6c timed out. Feb 28 22:55:32 wpa_supplicant[2426]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:35:a3:6c reason=3 locally_generated=1 Feb 28 22:55:32 wpa_supplicant[2426]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Feb 28 22:55:32 wpa_supplicant[2426]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pertho" auth_failures=1 duration=10 Feb 28 22:55:32 wpa_supplicant[2426]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Feb 28 22:55:32 kernel: iwn5000_tx_done: qid 3 idx 9 retries 7 nkill 0 rate 420a duration 3024 status 83 Feb 28 22:55:33 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:55:33 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:55:33 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:55:33 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:55:33 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:55:33 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:55:33 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:55:35 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:55:38 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:55:38 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:55:38 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:55:38 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:55:38 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:55:38 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:55:38 dhclient[2746]: send_packet: Invalid argument Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:55:39 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:55:43 dhclient[2746]: send_packet: Network is down Feb 28 22:55:44 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:55:44 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:55:44 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:55:45 wpa_supplicant[2426]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="pertho" Feb 28 22:55:45 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:55:45 wpa_supplicant[2426]: wlan0: Trying to associate with a0:f3:c1:35:a3:6c (SSID='pertho' freq=2462 MHz) Feb 28 22:55:45 wpa_supplicant[2425]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="pertho" Feb 28 22:55:45 wpa_supplicant[2425]: wlan0: Trying to associate with a0:f3:c1:35:a3:6c (SSID='pertho' freq=2462 MHz) Feb 28 22:55:45 kernel: iwn_tx_data_raw: qid 3 idx 10 len 6 nsegs 1 Feb 28 22:55:45 kernel: iwn_tx_data_raw: qid 3 idx 11 len 6 nsegs 1 Feb 28 22:55:45 kernel: iwn5000_tx_done: qid 3 idx 10 retries 0 nkill 0 rate 420a duration 778 status 201 Feb 28 22:55:45 kernel: iwn5000_tx_done: qid 3 idx 11 retries 0 nkill 0 rate 420a duration 778 status 201 Feb 28 22:55:45 kernel: iwn_tx_data_raw: qid 3 idx 12 len 87 nsegs 1 Feb 28 22:55:45 wpa_supplicant[2426]: wlan0: Associated with a0:f3:c1:35:a3:6c Feb 28 22:55:45 kernel: iwn5000_tx_done: qid 3 idx 12 retries 0 nkill 0 rate 420a duration 1426 status 201 Feb 28 22:55:45 kernel: iwn_set_link_quality: 1stream antenna=0x01, 2stream antenna=0x03, ntxstreams=1 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=0, txrate=7, rate=0x87 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=1, txrate=6, rate=0x86 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=2, txrate=5, rate=0x85 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=3, txrate=4, rate=0x84 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=4, txrate=3, rate=0x83 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=5, txrate=2, rate=0x82 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=6, txrate=1, rate=0x81 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=7, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=8, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=9, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=10, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=11, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=12, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=13, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=14, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: iwn_set_link_quality: i=15, txrate=0, rate=0x80 Feb 28 22:55:45 kernel: received statistics without RSSI Feb 28 22:55:45 kernel: wlan0: link state changed to UP Feb 28 22:55:45 wpa_supplicant[2425]: wlan0: Associated with a0:f3:c1:35:a3:6c Feb 28 22:55:45 dhclient[2746]: send_packet: No buffer space available Feb 28 22:55:45 dhclient[2746]: send_packet: No buffer space available Feb 28 22:55:46 kernel: iwn_tx_data: qid 3 idx 13 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:46 kernel: iwn_tx_data: qid 3 idx 14 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:46 kernel: iwn5000_tx_done: qid 3 idx 13 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:46 kernel: iwn5000_tx_done: qid 3 idx 14 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:47 kernel: iwn_tx_data: qid 3 idx 15 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:47 kernel: iwn_tx_data: qid 3 idx 16 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:47 kernel: iwn5000_tx_done: qid 3 idx 15 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:47 kernel: iwn5000_tx_done: qid 3 idx 16 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:48 kernel: iwn_tx_data: qid 3 idx 17 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:48 kernel: iwn_tx_data: qid 3 idx 18 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:48 kernel: iwn5000_tx_done: qid 3 idx 17 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:48 kernel: iwn5000_tx_done: qid 3 idx 18 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:49 kernel: iwn_check_rx_recovery: PLCP error threshold raw (134) comparison (13400) over limit (10250); retune! Feb 28 22:55:49 dhclient[2746]: send_packet: No buffer space available Feb 28 22:55:53 dhclient[2746]: send_packet: No buffer space available Feb 28 22:55:55 kernel: iwn_check_rx_recovery: PLCP error threshold raw (61) comparison (6100) over limit (5450); retune! Feb 28 22:55:56 wpa_supplicant[2426]: wlan0: Authentication with a0:f3:c1:35:a3:6c timed out. Feb 28 22:55:56 kernel: iwn_tx_data_raw: qid 3 idx 19 len 2 nsegs 1 Feb 28 22:55:56 wpa_supplicant[2426]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:35:a3:6c reason=3 locally_generated=1 Feb 28 22:55:56 wpa_supplicant[2426]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Feb 28 22:55:56 wpa_supplicant[2426]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pertho" auth_failures=2 duration=20 Feb 28 22:55:56 kernel: wlan0: link state changed to DOWN Feb 28 22:55:56 wpa_supplicant[2425]: wlan0: Authentication with a0:f3:c1:35:a3:6c timed out. Feb 28 22:55:56 wpa_supplicant[2425]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:35:a3:6c reason=3 locally_generated=1 Feb 28 22:55:56 wpa_supplicant[2425]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Feb 28 22:55:56 wpa_supplicant[2425]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pertho" auth_failures=2 duration=20 Feb 28 22:55:56 wpa_supplicant[2425]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Feb 28 22:55:56 kernel: iwn5000_tx_done: qid 3 idx 19 retries 6 nkill 0 rate 420a duration 3338 status 201 Feb 28 22:55:57 wpa_supplicant[2425]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:55:57 wpa_supplicant[2425]: wlan0: Failed to initiate AP scan Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:55:57 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:56:00 dhclient[2746]: send_packet: Invalid argument Feb 28 22:56:02 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:56:02 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:56:02 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:56:02 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:56:02 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:56:03 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:56:08 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:56:08 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:56:08 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:56:09 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:56:09 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:56:09 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:56:09 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:56:10 dhclient[2746]: send_packet: Network is down Feb 28 22:56:10 login: ROOT LOGIN (root) ON ttyv1 Feb 28 22:56:14 wpa_supplicant[2426]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:56:14 wpa_supplicant[2426]: wlan0: Failed to initiate AP scan Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:56:14 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:56:17 dhclient[2746]: send_packet: Network is down Feb 28 22:56:19 wpa_supplicant[2425]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Feb 28 22:56:19 wpa_supplicant[2425]: wlan0: Failed to initiate AP scan Feb 28 22:56:19 kernel: iwn_notif_intr: scanning channel 1 status 1 Feb 28 22:56:19 kernel: iwn_notif_intr: scanning channel 6 status 1 Feb 28 22:56:19 kernel: iwn_notif_intr: scanning channel 11 status 1 Feb 28 22:56:19 kernel: iwn_notif_intr: scanning channel 7 status 1 Feb 28 22:56:19 kernel: iwn_notif_intr: scanning channel 13 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 2 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 3 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 4 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 5 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 8 status 1 Feb 28 22:56:20 wpa_supplicant[2426]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="pertho" Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 9 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 10 status 1 Feb 28 22:56:20 kernel: iwn_notif_intr: scanning channel 12 status 1 Feb 28 22:56:20 wpa_supplicant[2426]: wlan0: Trying to associate with a0:f3:c1:35:a3:6c (SSID='pertho' freq=2462 MHz) Feb 28 22:56:20 kernel: iwn_tx_data_raw: qid 3 idx 20 len 6 nsegs 1 Feb 28 22:56:20 kernel: iwn_tx_data_raw: qid 3 idx 21 len 6 nsegs 1 Feb 28 22:56:20 wpa_supplicant[2425]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="pertho" Feb 28 22:56:20 wpa_supplicant[2425]: wlan0: Trying to associate with a0:f3:c1:35:a3:6c (SSID='pertho' freq=2462 MHz) Feb 28 22:56:20 kernel: iwn5000_tx_done: qid 3 idx 20 retries 0 nkill 0 rate 420a duration 778 status 201 Feb 28 22:56:20 kernel: iwn5000_tx_done: qid 3 idx 21 retries 0 nkill 0 rate 420a duration 778 status 201 Feb 28 22:56:20 kernel: iwn_tx_data_raw: qid 3 idx 22 len 87 nsegs 1 Feb 28 22:56:20 kernel: iwn5000_tx_done: qid 3 idx 22 retries 1 nkill 0 rate 420a duration 2538 status 201 Feb 28 22:56:20 kernel: iwn_set_link_quality: 1stream antenna=0x01, 2stream antenna=0x03, ntxstreams=1 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=0, txrate=7, rate=0x87 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=1, txrate=6, rate=0x86 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=2, txrate=5, rate=0x85 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=3, txrate=4, rate=0x84 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=4, txrate=3, rate=0x83 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=5, txrate=2, rate=0x82 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=6, txrate=1, rate=0x81 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=7, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=8, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=9, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=10, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=11, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=12, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=13, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=14, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: iwn_set_link_quality: i=15, txrate=0, rate=0x80 Feb 28 22:56:20 kernel: wlan0: link state changed to UP Feb 28 22:56:20 kernel: received statistics without RSSI Feb 28 22:56:20 wpa_supplicant[2425]: wlan0: Associated with a0:f3:c1:35:a3:6c Feb 28 22:56:20 dhclient[2746]: send_packet: No buffer space available Feb 28 22:56:20 wpa_supplicant[2426]: wlan0: Associated with a0:f3:c1:35:a3:6c Feb 28 22:56:21 kernel: iwn_tx_data: qid 3 idx 23 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:56:21 kernel: iwn_tx_data: qid 3 idx 24 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:56:21 kernel: iwn5000_tx_done: qid 3 idx 23 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:56:21 kernel: iwn5000_tx_done: qid 3 idx 24 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:56:22 kernel: iwn_tx_data: qid 3 idx 25 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:56:22 kernel: iwn_tx_data: qid 3 idx 26 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:56:22 dhclient[2746]: send_packet: No buffer space available Feb 28 22:56:22 kernel: iwn5000_tx_done: qid 3 idx 25 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:56:22 kernel: iwn5000_tx_done: qid 3 idx 26 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:56:23 kernel: iwn_tx_data: qid 3 idx 27 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:56:23 kernel: iwn_tx_data: qid 3 idx 28 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:56:23 kernel: iwn5000_tx_done: qid 3 idx 27 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:56:23 kernel: iwn5000_tx_done: qid 3 idx 28 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:56:27 kernel: iwn_check_rx_recovery: PLCP error threshold raw (117) comparison (11700) over limit (4950); retune! Feb 28 22:56:27 dhclient[2746]: send_packet: No buffer space available Feb 28 22:56:31 wpa_supplicant[2426]: wlan0: Authentication with a0:f3:c1:35:a3:6c timed out. Feb 28 22:56:31 kernel: iwn_tx_data_raw: qid 3 idx 29 len 2 nsegs 1 Feb 28 22:56:31 kernel: wlan0: link state changed to DOWN Feb 28 22:56:31 wpa_supplicant[2425]: wlan0: Authentication with a0:f3:c1:35:a3:6c timed out. Feb 28 22:56:31 wpa_supplicant[2426]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:35:a3:6c reason=3 locally_generated=1 Feb 28 22:56:31 wpa_supplicant[2426]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Feb 28 22:56:31 wpa_supplicant[2426]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pertho" auth_failures=3 duration=20 Feb 28 22:56:31 wpa_supplicant[2426]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Feb 28 22:56:31 wpa_supplicant[2425]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:35:a3:6c reason=3 locally_generated=1 Feb 28 22:56:31 wpa_supplicant[2425]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Feb 28 22:56:31 wpa_supplicant[2425]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pertho" auth_failures=3 duration=20 Feb 28 22:56:31 wpa_supplicant[2425]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Feb 28 22:56:31 kernel: iwn5000_tx_done: qid 3 idx 29 retries 3 nkill 0 rate 420a duration 2042 status 201 Feb 28 22:56:31 wpa_supplicant[2425]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Feb 28 22:56:31 wpa_supplicant[2426]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Feb 28 22:56:31 wpa_supplicant[2426]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Feb 28 22:56:31 dhclient[2743]: Interface wlan0 is down, dhclient exiting Feb 28 22:56:31 wpa_supplicant[2426]: wlan0: CTRL-EVENT-TERMINATING Feb 28 22:56:31 wpa_supplicant[2425]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Feb 28 22:56:31 wpa_supplicant[2425]: wlan0: CTRL-EVENT-TERMINATING Feb 28 22:56:31 dhclient[2746]: connection closed Feb 28 22:56:31 dhclient[2746]: exiting. Feb 28 22:56:31 root: /etc/rc.d/dhclient: WARNING: failed to start dhclient Feb 28 22:56:43 root: /etc/rc.d/dhclient: WARNING: failed to start dhclient Feb 28 22:56:51 root: /etc/rc.d/netif: WARNING: wlan0 does not exist. Skipped. Feb 28 22:56:51 dhclient[2815]: wlan0: not found Feb 28 22:56:51 dhclient[2815]: exiting. Feb 28 22:56:51 root: /etc/rc.d/dhclient: WARNING: failed to start dhclient --C7zPtVaVf+AK4Oqc-- From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 28 23:14:56 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9C885C7; Fri, 28 Feb 2014 23:14:56 +0000 (UTC) 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 5152713C7; Fri, 28 Feb 2014 23:14:56 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id m5so738838qaj.35 for ; Fri, 28 Feb 2014 15:14:55 -0800 (PST) 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=P2ulU9PrhDeTlRy8wWsmFVmDoKOe4n2hnCWeQLihHV0=; b=wK8SIStJ8YE9/gTz2b+8sYWvV8jL5vVVZj3w+TTVbCn0cQSn593Kqhe4cYRB2MCk9R 68hLUoEDAd5fvuDTBvoK4/zMBvLDnHOD2sbxnucAKCpz6ZAA+ydaJZyLXCQ60N1Xm7Tu PJXDWD0hgK13iBKMCdUHALN+kyWr3ONkm3ExO09jx383wsXYjb2WQTbaldQzBPGvIQ/U 1/0L6PXhbqCKKKhzBfiEk38kVVFKw/saaFNN278ZSbf7qd945q3ee6dc2OuxdnTc6raW 26T+XaCWfcde/kqjxckZMMTWJgb5mqjyQIRUvuv0YF1/JZMHl8IR0hUY4zVYVaORwwSj HI6A== MIME-Version: 1.0 X-Received: by 10.229.13.195 with SMTP id d3mr7543585qca.4.1393629295517; Fri, 28 Feb 2014 15:14:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Fri, 28 Feb 2014 15:14:55 -0800 (PST) In-Reply-To: <20140228230705.GA28290@syn.pertho.net> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> Date: Fri, 28 Feb 2014 15:14:55 -0800 X-Google-Sender-Auth: Yk2DTjbHmef1OD4P9xqx8ieJ36k Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Tom Murphy Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 28 Feb 2014 23:14:56 -0000 Hi, the interesting bits: Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 3 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 4 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 3 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 4 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 5 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 6 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 5 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 6 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 7 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 8 len 129 nsegs 2 rate 0002 plcp 0x0000420a Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 7 retries 16 nkill 0 rate 80006902 duration 2815 status 83 Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 8 retries 16 nkill 0 rate 80006902 duration 2815 status 83 .. so it's failing to transmit the management frames after association - they're being transmitted at MCS0 and the AP is just plain not ACKing them. Now, I don't know why this is. It's trying to transmit the initial frame at non-MCS rates, but I have a feeling the multi-rate retry table thing is confusing it and it's trying to send it as MCS. So maybe the AP doesn't like management frames at MCS rates. I'll have to think about this a little. -a On 28 February 2014 15:07, Tom Murphy wrote: > I've attached my iwn debug messages to this email starting > with the point I tried to associate to the Wifi. > > Thanks again for looking at this! > > Kind regards, > Tom > > On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote: >> On 26 February 2014 23:52, Alexandr wrote: >> > Tom, could you: >> > >> > 1. compile kernel WITH_IWNDEBUG >> > 2. sysctl dev.iwn.0.debug=0x1 >> > 3. wlandebug -i wlan0 auth+assoc >> > 4. Associate with AP in 11n mode >> > 5. Send us appropriate /var/log/messages >> > >> > Then I try to compare it with my log. >> >> Please do. I've been trying to track down the source of this "ht just >> doesn't work!" but it works fine with all of the Intel NICs I have >> here. >> >> Can someone see if they can find a mtaching NIC online (amazon,ebay?) >> Owning one that I can whack in a laptop is likely going ot help things >> a lot. >> >> Thanks, >> >> >> -a From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 1 17:11:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2554969 for ; Sat, 1 Mar 2014 17:11:27 +0000 (UTC) Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5880E1B91 for ; Sat, 1 Mar 2014 17:11:27 +0000 (UTC) Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s21HBOaI024270; Sat, 1 Mar 2014 12:11:24 -0500 (EST) (envelope-from curtis@ipv6.occnc.com) Message-Id: <201403011711.s21HBOaI024270@maildrop2.v6ds.occnc.com> To: freebsd-wireless@freebsd.org Subject: iwn rtsol on stable/10 with merge from head From: Curtis Villamizar Date: Sat, 01 Mar 2014 12:11:24 -0500 Cc: curtis@ipv6.occnc.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: curtis@ipv6.occnc.com 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, 01 Mar 2014 17:11:27 -0000 rtsol is not working for my kernel build with iwn but everything else works. I'm running a very recent stable/10 (kernel is 262621) upgraded to pick up iwn stuff from head: svn merge \ https://svn0.us-east.freebsd.org/base/head/sys/dev/iwn \ dev/iwn svn merge \ https://svn0.us-east.freebsd.org/base/head/sys/modules/iwnfw \ modules/iwnfw svn merge https://svn0.us-east.freebsd.org/base/head/sys/contrib/dev/iwn \ contrib/dev/iwn That was to get the Centrino 2000 support from the head branch. That works. iwn0: mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci3 Everything works as far as I can tell except rtsol. # rtsold -f -d -D wlan0 checking if wlan0 is ready... wlan0 does not accept Router Advertisement. set timer for wlan0 to 1s New timer is 1s timer expiration on wlan0, state = 3 checking if wlan0 is ready... wlan0 does not accept Router Advertisement. set timer for wlan0 to 1s New timer is 1s timer expiration on wlan0, state = 3 checking if wlan0 is ready... wlan0 does not accept Router Advertisement. set timer for wlan0 to 1s New timer is 1s [ ... etc ... ] If I use rtsold -a it sees wlan0 as not ready and doesn't try to use it but then it receives occasional RA anyway but ignores them because it sees wlan0 as not ready. If I ifconfig inet6 ... alias I get an IPv6 address configured and manually add a default route, then everything is fine. This workaround is OK for home but is not practical for roaming about (like going to IETF) if I want IPv6 to work. Does anyone know why rtsold isn't seeing wlan0 as ready? Is there any info I could provide? How likely is it that will a kernel built from head this would just go away and rtsold would just work. btw- headed for IETF so I'll have a chance to test iwn in a very busy environment and would be willing to help if anyone wants to do that sort of debugging. [I have a usb wlan (run0) as a fallback] Curtis From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 1 17:37:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7787D726 for ; Sat, 1 Mar 2014 17:37:58 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 353451D1B for ; Sat, 1 Mar 2014 17:37:58 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so6205810qgd.1 for ; Sat, 01 Mar 2014 09:37:57 -0800 (PST) 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=VPpxRtxIAiR8qgBmOY2ltIr2Xw2W7Ja0V0D1VxFZ2MQ=; b=UWuSzoLHNasugEHT/nnsxWN43NAoFsJk/DvAneNoCVLYRLAbSIUSfTLoOCTGuHW9zL FaltKsRGdH2VR0PK9OPc6lpEQCPh8zP38CK6+NOe8BM6oqlHxRh0rrzlr733zmRdxYyY hWSm3c+Ov9uNIv3BtSz9hNrPu2m1bbVTb6Kn7gTALRuZcDMqH2YMk9lHEDL/qdk+JD7V WeQZA5rp8NLJdpAwdM/tgAJo2OZkTGPHPs3pAclAPVCS74OuY5UVTlB6oVqqGrvEWRTw MWmbUf/E5EAWSG4SMD1e4G3Rkr/5cC9AVjDMt8h7TlMDDI6A1kX89RAXy0XFhuLjBpzk 4q3g== MIME-Version: 1.0 X-Received: by 10.140.42.54 with SMTP id b51mr11581420qga.87.1393695477369; Sat, 01 Mar 2014 09:37:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Sat, 1 Mar 2014 09:37:57 -0800 (PST) In-Reply-To: <201403011711.s21HBOaI024270@maildrop2.v6ds.occnc.com> References: <201403011711.s21HBOaI024270@maildrop2.v6ds.occnc.com> Date: Sat, 1 Mar 2014 09:37:57 -0800 X-Google-Sender-Auth: WrxUYA1-1P1AziCSO9yIaUsUL6I Message-ID: Subject: Re: iwn rtsol on stable/10 with merge from head From: Adrian Chadd To: curtis@ipv6.occnc.com Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 01 Mar 2014 17:37:58 -0000 Hi, Please grab and try 'iwnstats' from head - tools/tools/iwn/iwnstats - it'll be interesting to see what stats are logged when you're in busy air. I have no idea about rtsold, sorry. :( -a On 1 March 2014 09:11, Curtis Villamizar wrote: > > rtsol is not working for my kernel build with iwn but everything else > works. > > I'm running a very recent stable/10 (kernel is 262621) upgraded to > pick up iwn stuff from head: > > svn merge \ > https://svn0.us-east.freebsd.org/base/head/sys/dev/iwn \ > dev/iwn > svn merge \ > https://svn0.us-east.freebsd.org/base/head/sys/modules/iwnfw \ > modules/iwnfw > svn merge > https://svn0.us-east.freebsd.org/base/head/sys/contrib/dev/iwn \ > contrib/dev/iwn > > That was to get the Centrino 2000 support from the head branch. > > That works. > > iwn0: > mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci3 > > Everything works as far as I can tell except rtsol. > > # rtsold -f -d -D wlan0 > checking if wlan0 is ready... > wlan0 does not accept Router Advertisement. > set timer for wlan0 to 1s > New timer is 1s > timer expiration on wlan0, state = 3 > checking if wlan0 is ready... > wlan0 does not accept Router Advertisement. > set timer for wlan0 to 1s > New timer is 1s > timer expiration on wlan0, state = 3 > checking if wlan0 is ready... > wlan0 does not accept Router Advertisement. > set timer for wlan0 to 1s > New timer is 1s > [ ... etc ... ] > > If I use rtsold -a it sees wlan0 as not ready and doesn't try to use > it but then it receives occasional RA anyway but ignores them because > it sees wlan0 as not ready. > > If I ifconfig inet6 ... alias I get an IPv6 address configured and > manually add a default route, then everything is fine. This > workaround is OK for home but is not practical for roaming about (like > going to IETF) if I want IPv6 to work. > > Does anyone know why rtsold isn't seeing wlan0 as ready? Is there any > info I could provide? How likely is it that will a kernel built from > head this would just go away and rtsold would just work. > > btw- headed for IETF so I'll have a chance to test iwn in a very busy > environment and would be willing to help if anyone wants to do that > sort of debugging. [I have a usb wlan (run0) as a fallback] > > Curtis > _______________________________________________ > 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 Sun Mar 2 00:02:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47C7046C; Sun, 2 Mar 2014 00:02:05 +0000 (UTC) Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EDD0F1F58; Sun, 2 Mar 2014 00:02:04 +0000 (UTC) Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s22021xF031216; Sat, 1 Mar 2014 19:02:02 -0500 (EST) (envelope-from curtis@ipv6.occnc.com) Message-Id: <201403020002.s22021xF031216@maildrop2.v6ds.occnc.com> To: Adrian Chadd From: Curtis Villamizar Subject: Re: iwn rtsol on stable/10 with merge from head In-reply-to: Your message of "Sat, 01 Mar 2014 09:37:57 -0800." Date: Sat, 01 Mar 2014 19:02:01 -0500 Cc: "freebsd-wireless@freebsd.org" , curtis@ipv6.occnc.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: curtis@ipv6.occnc.com List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2014 00:02:05 -0000 In message Adrian Chadd writes: > Hi, > > Please grab and try 'iwnstats' from head - tools/tools/iwn/iwnstats - > it'll be interesting to see what stats are logged when you're in busy > air. Typical WG sessions have 50-200 people. The technical plenary (Monday evening) and the administrative plenary (Thursday evening) typically have around 1,000. That's mostly geeks with wifi in their phones plus their laptops. I'll try to get stats in WG sessions and both plenaries. > I have no idea about rtsold, sorry. :( I'm not sure the cause but the cure has something to do with this: A little RTFC on rtsold/if.c reveals that ND6_IFF_ACCEPT_RTADV is not set in nd.ndi.flags which comes from the lines: if (ioctl(s, SIOCGIFINFO_IN6, (caddr_t)&nd) < 0) { [...] } if (!(nd.ndi.flags & ND6_IFF_ACCEPT_RTADV)) { A man ifconfig reveals: accept_rtadv Set a flag to enable accepting ICMPv6 Router Advertisement messages. The sysctl(8) variable net.inet6.ip6.accept_rtadv controls whether this flag is set by default or not. So the workaround is to add net.inet6.ip6.accept_rtadv=1 to /etc/sysctl.conf. A one time test using "ifconfig wlan0 inet6 accept_rtadv" and restarting rtsold also confirms this is the problem. The mystery is really why this doesn't affect em0 and run0 on the same machine. I'll have to check and make sure they don't all behave the same with the same kernel. None of these driveres have the string rtadv. In sys/dev "grep -il rtadv */*.[hc]" yields nothing. The string ND6_IFF_ACCEPT_RTADV only appears in sys files in the netinet6 directory. Reading the code, iwn seems to do what is right with net.inet6.ip6.accept_rtadv clear and the others (em0, run0, plus msk0 on another machine, em0 on other machines) have ND6_IFF_ACCEPT_RTADV set even though net.inet6.ip6.accept_rtadv is not set. The entire src/sys tree is from head but the rest of src is stable/10. > -a I'll try to get the stats next week but it looks like I'll need to build the src distribution from head to get that done, pulling just iwnstats from head. Merging tools/tools/iwn/iwnstats into the stable/10 tree didn't compile. Not a big deal but pressed for time between now and then. Curtis > On 1 March 2014 09:11, Curtis Villamizar wrote: > > > > rtsol is not working for my kernel build with iwn but everything else > > works. > > > > I'm running a very recent stable/10 (kernel is 262621) upgraded to > > pick up iwn stuff from head: > > > > svn merge \ > > https://svn0.us-east.freebsd.org/base/head/sys/dev/iwn \ > > dev/iwn > > svn merge \ > > https://svn0.us-east.freebsd.org/base/head/sys/modules/iwnfw \ > > modules/iwnfw > > svn merge > > https://svn0.us-east.freebsd.org/base/head/sys/contrib/dev/iwn \ > > contrib/dev/iwn > > > > That was to get the Centrino 2000 support from the head branch. > > > > That works. > > > > iwn0: > > mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci3 > > > > Everything works as far as I can tell except rtsol. > > > > # rtsold -f -d -D wlan0 > > checking if wlan0 is ready... > > wlan0 does not accept Router Advertisement. > > set timer for wlan0 to 1s > > New timer is 1s > > timer expiration on wlan0, state = 3 > > checking if wlan0 is ready... > > wlan0 does not accept Router Advertisement. > > set timer for wlan0 to 1s > > New timer is 1s > > timer expiration on wlan0, state = 3 > > checking if wlan0 is ready... > > wlan0 does not accept Router Advertisement. > > set timer for wlan0 to 1s > > New timer is 1s > > [ ... etc ... ] > > > > If I use rtsold -a it sees wlan0 as not ready and doesn't try to use > > it but then it receives occasional RA anyway but ignores them because > > it sees wlan0 as not ready. > > > > If I ifconfig inet6 ... alias I get an IPv6 address configured and > > manually add a default route, then everything is fine. This > > workaround is OK for home but is not practical for roaming about (like > > going to IETF) if I want IPv6 to work. > > > > Does anyone know why rtsold isn't seeing wlan0 as ready? Is there any > > info I could provide? How likely is it that will a kernel built from > > head this would just go away and rtsold would just work. > > > > btw- headed for IETF so I'll have a chance to test iwn in a very busy > > environment and would be willing to help if anyone wants to do that > > sort of debugging. [I have a usb wlan (run0) as a fallback] > > > > Curtis From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 2 00:35:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D1849A1 for ; Sun, 2 Mar 2014 00:35:37 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BEA9411A0 for ; Sun, 2 Mar 2014 00:35:36 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id f51so7011217qge.2 for ; Sat, 01 Mar 2014 16:35:35 -0800 (PST) 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=0ObMrT+8juUfXSyPfBPsNKgOlyLqKZ5p+fH9txAGPNk=; b=od/8CP1W8WOSONizNW7cWK9w32e0D70cIhhNWI6V+QpAma/Wa8K7futEiWHRW/AQdv bA+85CvrSHbGE8rRUmjEELwKRBDuOiNNJa262g7hBfeQM/Idz68lUUNyW+a6lG8fO2h2 ShlJRGfm1NNOHUCFYINjvkiHXEFn/KfBHKO4R9bF9rFaleupqGe/xAJ0N/k+DDFpizyE JJC1dn0lrmxtQI9SoXOwaXW2+YrjSVlTlwcOaXm+MM1R87IBDTD3EOaOo8kwV+uDlvvX o0aJOSgnjKQhy0F5ahypWl2bmafi+58cY7H/BX1ICx+mcIrFjTykYvnQt4KgfjK0oG1X ymdQ== MIME-Version: 1.0 X-Received: by 10.224.30.16 with SMTP id s16mr14099723qac.74.1393720535887; Sat, 01 Mar 2014 16:35:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Sat, 1 Mar 2014 16:35:35 -0800 (PST) In-Reply-To: <201403020002.s22021xF031216@maildrop2.v6ds.occnc.com> References: <201403020002.s22021xF031216@maildrop2.v6ds.occnc.com> Date: Sat, 1 Mar 2014 16:35:35 -0800 X-Google-Sender-Auth: -tup2i8dzF4OpacUgxbAzIYuxEc Message-ID: Subject: Re: iwn rtsol on stable/10 with merge from head From: Adrian Chadd To: curtis@ipv6.occnc.com Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2014 00:35:37 -0000 Maybe the whole cloned interfaces path isn't setting up the ipv6 flags correctly? -a On 1 March 2014 16:02, Curtis Villamizar wrote: > > In message > Adrian Chadd writes: > >> Hi, >> >> Please grab and try 'iwnstats' from head - tools/tools/iwn/iwnstats - >> it'll be interesting to see what stats are logged when you're in busy >> air. > > Typical WG sessions have 50-200 people. The technical plenary (Monday > evening) and the administrative plenary (Thursday evening) typically > have around 1,000. That's mostly geeks with wifi in their phones plus > their laptops. I'll try to get stats in WG sessions and both plenaries. > >> I have no idea about rtsold, sorry. :( > > I'm not sure the cause but the cure has something to do with this: > > A little RTFC on rtsold/if.c reveals that ND6_IFF_ACCEPT_RTADV is not > set in nd.ndi.flags which comes from the lines: > > if (ioctl(s, SIOCGIFINFO_IN6, (caddr_t)&nd) < 0) { > [...] > } > if (!(nd.ndi.flags & ND6_IFF_ACCEPT_RTADV)) { > > A man ifconfig reveals: > > accept_rtadv > Set a flag to enable accepting ICMPv6 Router > Advertisement messages. The sysctl(8) variable > net.inet6.ip6.accept_rtadv controls whether this flag is > set by default or not. > > So the workaround is to add net.inet6.ip6.accept_rtadv=1 to > /etc/sysctl.conf. A one time test using "ifconfig wlan0 inet6 > accept_rtadv" and restarting rtsold also confirms this is the > problem. > > The mystery is really why this doesn't affect em0 and run0 on the same > machine. I'll have to check and make sure they don't all behave the > same with the same kernel. None of these driveres have the string > rtadv. In sys/dev "grep -il rtadv */*.[hc]" yields nothing. The > string ND6_IFF_ACCEPT_RTADV only appears in sys files in the netinet6 > directory. Reading the code, iwn seems to do what is right with > net.inet6.ip6.accept_rtadv clear and the others (em0, run0, plus msk0 > on another machine, em0 on other machines) have ND6_IFF_ACCEPT_RTADV > set even though net.inet6.ip6.accept_rtadv is not set. > > The entire src/sys tree is from head but the rest of src is stable/10. > >> -a > > I'll try to get the stats next week but it looks like I'll need to > build the src distribution from head to get that done, pulling just > iwnstats from head. Merging tools/tools/iwn/iwnstats into the > stable/10 tree didn't compile. Not a big deal but pressed for time > between now and then. > > Curtis > > >> On 1 March 2014 09:11, Curtis Villamizar wrote: >> > >> > rtsol is not working for my kernel build with iwn but everything else >> > works. >> > >> > I'm running a very recent stable/10 (kernel is 262621) upgraded to >> > pick up iwn stuff from head: >> > >> > svn merge \ >> > https://svn0.us-east.freebsd.org/base/head/sys/dev/iwn \ >> > dev/iwn >> > svn merge \ >> > https://svn0.us-east.freebsd.org/base/head/sys/modules/iwnfw \ >> > modules/iwnfw >> > svn merge >> > https://svn0.us-east.freebsd.org/base/head/sys/contrib/dev/iwn \ >> > contrib/dev/iwn >> > >> > That was to get the Centrino 2000 support from the head branch. >> > >> > That works. >> > >> > iwn0: >> > mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci3 >> > >> > Everything works as far as I can tell except rtsol. >> > >> > # rtsold -f -d -D wlan0 >> > checking if wlan0 is ready... >> > wlan0 does not accept Router Advertisement. >> > set timer for wlan0 to 1s >> > New timer is 1s >> > timer expiration on wlan0, state = 3 >> > checking if wlan0 is ready... >> > wlan0 does not accept Router Advertisement. >> > set timer for wlan0 to 1s >> > New timer is 1s >> > timer expiration on wlan0, state = 3 >> > checking if wlan0 is ready... >> > wlan0 does not accept Router Advertisement. >> > set timer for wlan0 to 1s >> > New timer is 1s >> > [ ... etc ... ] >> > >> > If I use rtsold -a it sees wlan0 as not ready and doesn't try to use >> > it but then it receives occasional RA anyway but ignores them because >> > it sees wlan0 as not ready. >> > >> > If I ifconfig inet6 ... alias I get an IPv6 address configured and >> > manually add a default route, then everything is fine. This >> > workaround is OK for home but is not practical for roaming about (like >> > going to IETF) if I want IPv6 to work. >> > >> > Does anyone know why rtsold isn't seeing wlan0 as ready? Is there any >> > info I could provide? How likely is it that will a kernel built from >> > head this would just go away and rtsold would just work. >> > >> > btw- headed for IETF so I'll have a chance to test iwn in a very busy >> > environment and would be willing to help if anyone wants to do that >> > sort of debugging. [I have a usb wlan (run0) as a fallback] >> > >> > Curtis From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 3 11:06:55 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92B35F4E for ; Mon, 3 Mar 2014 11:06:55 +0000 (UTC) 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 6538495D for ; Mon, 3 Mar 2014 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s23B6tOi008714 for ; Mon, 3 Mar 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s23B6s3X008712 for freebsd-wireless@FreeBSD.org; Mon, 3 Mar 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Mar 2014 11:06:54 GMT Message-Id: <201403031106.s23B6s3X008712@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.17 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, 03 Mar 2014 11:06:55 -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/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 192 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 4 02:23:56 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0F46AFA; Tue, 4 Mar 2014 02:23:56 +0000 (UTC) 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 B66AE7D; Tue, 4 Mar 2014 02:23:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s242Nu6w011308; Tue, 4 Mar 2014 02:23:56 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s242Nu1n011307; Tue, 4 Mar 2014 02:23:56 GMT (envelope-from linimon) Date: Tue, 4 Mar 2014 02:23:56 GMT Message-Id: <201403040223.s242Nu1n011307@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/186733: [iwn] iwn device (5100) periodically times out killing network connectivity X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 04 Mar 2014 02:23:57 -0000 Old Synopsis: iwn device (5100) periodically times out killing network connectivity New Synopsis: [iwn] iwn device (5100) periodically times out killing network connectivity Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Tue Mar 4 02:23:41 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=186733 From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 4 08:09:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F754E56 for ; Tue, 4 Mar 2014 08:09:32 +0000 (UTC) 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 4F473F48 for ; Tue, 4 Mar 2014 08:09:32 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id i8so5110508qcq.9 for ; Tue, 04 Mar 2014 00:09:31 -0800 (PST) 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=bg8SLwcKG5C+6Ay88gF9ROC+8ahylC9RIC7ED7ahUZY=; b=N/TrcBAOTC8GDsuBlfnCzhlnLyvy7cb2+I0qX/0k9z4df0Hp5NueJy78o/EArgRi4y rr/0EPzY1vxtcNm257rykToRSB3Fh3uc5tqOvzvYGFrYl8Fwe8TCYZBbw8ql1YXzvAvV 5Len3wKeeGA61jPnTrrUuGj/7+iEKaGHSsybDZ5cKSaXOj3fdNF3n0Dij3EK9WN+9u+O q7SbK8fZPy2cq0HHMzBHj/nG4eo8bOUJFoEHcDdVQ7AI4dJLW1q4252HZRIkCdyz1yhR H01owCvpuq1/VR2nlQHiUZ9sY0+J2A/DpvzbG3LltenxDnDBaC6mU1t9mn32ookfMDIz mOlA== MIME-Version: 1.0 X-Received: by 10.224.136.195 with SMTP id s3mr8140547qat.95.1393920571492; Tue, 04 Mar 2014 00:09:31 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.16.10 with HTTP; Tue, 4 Mar 2014 00:09:31 -0800 (PST) In-Reply-To: <201403040801.s2481uAc088743@svn.freebsd.org> References: <201403040801.s2481uAc088743@svn.freebsd.org> Date: Tue, 4 Mar 2014 00:09:31 -0800 X-Google-Sender-Auth: W67A3AqXoPQeyj9jnbuEVsztzIg Message-ID: Subject: Fwd: svn commit: r262729 - head/sys/dev/iwn From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 04 Mar 2014 08:09:32 -0000 If you have a Centrino 100, 2200, 2230, then please update to the latest -HEAD. This may fix some calibration issues. -a ---------- Forwarded message ---------- From: Adrian Chadd Date: 4 March 2014 00:01 Subject: svn commit: r262729 - head/sys/dev/iwn To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: adrian Date: Tue Mar 4 08:01:56 2014 New Revision: 262729 URL: http://svnweb.freebsd.org/changeset/base/262729 Log: Handle the newer-style bluetooth message format from the (at least) Centrino 2230 firmware. This fixes the general statistics block to be actually valid. I've verified this by contrasting the output of iwnstats before and after the change. The general block is now correct. Tested: * Intel 5100 (old format stats message) * Intel 2230 (new format stats message) Modified: head/sys/dev/iwn/if_iwn.c Modified: head/sys/dev/iwn/if_iwn.c ============================================================================== --- head/sys/dev/iwn/if_iwn.c Tue Mar 4 06:55:54 2014 (r262728) +++ head/sys/dev/iwn/if_iwn.c Tue Mar 4 08:01:56 2014 (r262729) @@ -685,6 +685,13 @@ iwn_attach(device_t dev) goto fail; } +#if 0 + device_printf(sc->sc_dev, "%s: rx_stats=%d, rx_stats_bt=%d\n", + __func__, + sizeof(struct iwn_stats), + sizeof(struct iwn_stats_bt)); +#endif + if (bootverbose) ieee80211_announce(ic); DPRINTF(sc, IWN_DEBUG_TRACE, "->%s: end\n",__func__); @@ -3143,11 +3150,62 @@ iwn5000_rx_calib_results(struct iwn_soft static void iwn_stats_update(struct iwn_softc *sc, struct iwn_calib_state *calib, - struct iwn_stats *stats) + struct iwn_stats *stats, int len) { + struct iwn_stats_bt *stats_bt; + struct iwn_stats *lstats; + + /* + * First - check whether the length is the bluetooth or normal. + * + * If it's normal - just copy it and bump out. + * Otherwise we have to convert things. + */ + + if (len == sizeof(struct iwn_stats) + 4) { + memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); + sc->last_stat_valid = 1; + return; + } - /* XXX lock assert */ - memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); + /* + * If it's not the bluetooth size - log, then just copy. + */ + if (len != sizeof(struct iwn_stats_bt) + 4) { + DPRINTF(sc, IWN_DEBUG_STATS, + "%s: size of rx statistics (%d) not an expected size!\n", + __func__, + len); + memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); + sc->last_stat_valid = 1; + return; + } + + /* + * Ok. Time to copy. + */ + stats_bt = (struct iwn_stats_bt *) stats; + lstats = &sc->last_stat; + + /* flags */ + lstats->flags = stats_bt->flags; + /* rx_bt */ + memcpy(&lstats->rx.ofdm, &stats_bt->rx_bt.ofdm, + sizeof(struct iwn_rx_phy_stats)); + memcpy(&lstats->rx.cck, &stats_bt->rx_bt.cck, + sizeof(struct iwn_rx_phy_stats)); + memcpy(&lstats->rx.general, &stats_bt->rx_bt.general_bt.common, + sizeof(struct iwn_rx_general_stats)); + memcpy(&lstats->rx.ht, &stats_bt->rx_bt.ht, + sizeof(struct iwn_rx_ht_phy_stats)); + /* tx */ + memcpy(&lstats->tx, &stats_bt->tx, + sizeof(struct iwn_tx_stats)); + /* general */ + memcpy(&lstats->general, &stats_bt->general, + sizeof(struct iwn_general_stats)); + + /* XXX TODO: Squirrel away the extra bluetooth stats somewhere */ sc->last_stat_valid = 1; } @@ -3165,6 +3223,7 @@ iwn_rx_statistics(struct iwn_softc *sc, struct ieee80211vap *vap = TAILQ_FIRST(&ic->ic_vaps); struct iwn_calib_state *calib = &sc->calib; struct iwn_stats *stats = (struct iwn_stats *)(desc + 1); + struct iwn_stats *lstats; int temp; DPRINTF(sc, IWN_DEBUG_TRACE, "->%s begin\n", __func__); @@ -3179,15 +3238,26 @@ iwn_rx_statistics(struct iwn_softc *sc, bus_dmamap_sync(sc->rxq.data_dmat, data->map, BUS_DMASYNC_POSTREAD); - DPRINTF(sc, IWN_DEBUG_CALIBRATE, "%s: received statistics, cmd %d\n", - __func__, desc->type); + DPRINTF(sc, IWN_DEBUG_CALIBRATE | IWN_DEBUG_STATS, + "%s: received statistics, cmd %d, len %d\n", + __func__, desc->type, le16toh(desc->len)); sc->calib_cnt = 0; /* Reset TX power calibration timeout. */ - /* Collect/track general statistics for reporting */ - iwn_stats_update(sc, calib, stats); + /* + * Collect/track general statistics for reporting. + * + * This takes care of ensuring that the bluetooth sized message + * will be correctly converted to the legacy sized message. + */ + iwn_stats_update(sc, calib, stats, le16toh(desc->len)); + + /* + * And now, let's take a reference of it to use! + */ + lstats = &sc->last_stat; /* Test if temperature has changed. */ - if (stats->general.temp != sc->rawtemp) { + if (lstats->general.temp != sc->rawtemp) { /* Convert "raw" temperature to degC. */ sc->rawtemp = stats->general.temp; temp = ops->get_temperature(sc); @@ -3202,25 +3272,25 @@ iwn_rx_statistics(struct iwn_softc *sc, if (desc->type != IWN_BEACON_STATISTICS) return; /* Reply to a statistics request. */ - sc->noise = iwn_get_noise(&stats->rx.general); + sc->noise = iwn_get_noise(&lstats->rx.general); DPRINTF(sc, IWN_DEBUG_CALIBRATE, "%s: noise %d\n", __func__, sc->noise); /* Test that RSSI and noise are present in stats report. */ - if (le32toh(stats->rx.general.flags) != 1) { + if (le32toh(lstats->rx.general.flags) != 1) { DPRINTF(sc, IWN_DEBUG_ANY, "%s\n", "received statistics without RSSI"); return; } if (calib->state == IWN_CALIB_STATE_ASSOC) - iwn_collect_noise(sc, &stats->rx.general); + iwn_collect_noise(sc, &lstats->rx.general); else if (calib->state == IWN_CALIB_STATE_RUN) { - iwn_tune_sensitivity(sc, &stats->rx); + iwn_tune_sensitivity(sc, &lstats->rx); /* * XXX TODO: Only run the RX recovery if we're associated! */ - iwn_check_rx_recovery(sc, stats); - iwn_save_stats_counters(sc, stats); + iwn_check_rx_recovery(sc, lstats); + iwn_save_stats_counters(sc, lstats); } DPRINTF(sc, IWN_DEBUG_TRACE, "->%s: end\n",__func__); From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 6 07:40:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD752787 for ; Thu, 6 Mar 2014 07:40:04 +0000 (UTC) Received: from graal.it-profi.org.ua (graal.shurik.kiev.ua [193.239.74.7]) (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 6878DA55 for ; Thu, 6 Mar 2014 07:40:03 +0000 (UTC) Received: from [217.76.201.82] (helo=thinkpad.it-profi.org.ua) by graal.it-profi.org.ua with esmtpa (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WLSuJ-000LlV-PX for freebsd-wireless@freebsd.org; Thu, 06 Mar 2014 09:39:55 +0200 Message-ID: <53182646.3010004@shurik.kiev.ua> Date: Thu, 06 Mar 2014 09:39:50 +0200 From: Alexandr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: Fwd: svn commit: r262729 - head/sys/dev/iwn References: <201403040801.s2481uAc088743@svn.freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 217.76.201.82 X-SA-Exim-Mail-From: shuriku@shurik.kiev.ua X-SA-Exim-Scanned: No (on graal.it-profi.org.ua); SAEximRunCond expanded to false X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Mar 2014 07:40:04 -0000 My 2230 still not working in 11n 04.03.2014 10:09, Adrian Chadd пишет: > If you have a Centrino 100, 2200, 2230, then please update to the > latest -HEAD. This may fix some calibration issues. > > > -a > > > > ---------- Forwarded message ---------- > From: Adrian Chadd > Date: 4 March 2014 00:01 > Subject: svn commit: r262729 - head/sys/dev/iwn > To: src-committers@freebsd.org, svn-src-all@freebsd.org, > svn-src-head@freebsd.org > > > Author: adrian > Date: Tue Mar 4 08:01:56 2014 > New Revision: 262729 > URL: http://svnweb.freebsd.org/changeset/base/262729 > > Log: > Handle the newer-style bluetooth message format from the (at least) > Centrino 2230 firmware. > > This fixes the general statistics block to be actually valid. > > I've verified this by contrasting the output of iwnstats before and > after the change. The general block is now correct. > > Tested: > > * Intel 5100 (old format stats message) > * Intel 2230 (new format stats message) > > Modified: > head/sys/dev/iwn/if_iwn.c > > Modified: head/sys/dev/iwn/if_iwn.c > ============================================================================== > --- head/sys/dev/iwn/if_iwn.c Tue Mar 4 06:55:54 2014 (r262728) > +++ head/sys/dev/iwn/if_iwn.c Tue Mar 4 08:01:56 2014 (r262729) > @@ -685,6 +685,13 @@ iwn_attach(device_t dev) > goto fail; > } > > +#if 0 > + device_printf(sc->sc_dev, "%s: rx_stats=%d, rx_stats_bt=%d\n", > + __func__, > + sizeof(struct iwn_stats), > + sizeof(struct iwn_stats_bt)); > +#endif > + > if (bootverbose) > ieee80211_announce(ic); > DPRINTF(sc, IWN_DEBUG_TRACE, "->%s: end\n",__func__); > @@ -3143,11 +3150,62 @@ iwn5000_rx_calib_results(struct iwn_soft > > static void > iwn_stats_update(struct iwn_softc *sc, struct iwn_calib_state *calib, > - struct iwn_stats *stats) > + struct iwn_stats *stats, int len) > { > + struct iwn_stats_bt *stats_bt; > + struct iwn_stats *lstats; > + > + /* > + * First - check whether the length is the bluetooth or normal. > + * > + * If it's normal - just copy it and bump out. > + * Otherwise we have to convert things. > + */ > + > + if (len == sizeof(struct iwn_stats) + 4) { > + memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); > + sc->last_stat_valid = 1; > + return; > + } > > - /* XXX lock assert */ > - memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); > + /* > + * If it's not the bluetooth size - log, then just copy. > + */ > + if (len != sizeof(struct iwn_stats_bt) + 4) { > + DPRINTF(sc, IWN_DEBUG_STATS, > + "%s: size of rx statistics (%d) not an expected size!\n", > + __func__, > + len); > + memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); > + sc->last_stat_valid = 1; > + return; > + } > + > + /* > + * Ok. Time to copy. > + */ > + stats_bt = (struct iwn_stats_bt *) stats; > + lstats = &sc->last_stat; > + > + /* flags */ > + lstats->flags = stats_bt->flags; > + /* rx_bt */ > + memcpy(&lstats->rx.ofdm, &stats_bt->rx_bt.ofdm, > + sizeof(struct iwn_rx_phy_stats)); > + memcpy(&lstats->rx.cck, &stats_bt->rx_bt.cck, > + sizeof(struct iwn_rx_phy_stats)); > + memcpy(&lstats->rx.general, &stats_bt->rx_bt.general_bt.common, > + sizeof(struct iwn_rx_general_stats)); > + memcpy(&lstats->rx.ht, &stats_bt->rx_bt.ht, > + sizeof(struct iwn_rx_ht_phy_stats)); > + /* tx */ > + memcpy(&lstats->tx, &stats_bt->tx, > + sizeof(struct iwn_tx_stats)); > + /* general */ > + memcpy(&lstats->general, &stats_bt->general, > + sizeof(struct iwn_general_stats)); > + > + /* XXX TODO: Squirrel away the extra bluetooth stats somewhere */ > sc->last_stat_valid = 1; > } > > @@ -3165,6 +3223,7 @@ iwn_rx_statistics(struct iwn_softc *sc, > struct ieee80211vap *vap = TAILQ_FIRST(&ic->ic_vaps); > struct iwn_calib_state *calib = &sc->calib; > struct iwn_stats *stats = (struct iwn_stats *)(desc + 1); > + struct iwn_stats *lstats; > int temp; > > DPRINTF(sc, IWN_DEBUG_TRACE, "->%s begin\n", __func__); > @@ -3179,15 +3238,26 @@ iwn_rx_statistics(struct iwn_softc *sc, > > bus_dmamap_sync(sc->rxq.data_dmat, data->map, BUS_DMASYNC_POSTREAD); > > - DPRINTF(sc, IWN_DEBUG_CALIBRATE, "%s: received statistics, cmd %d\n", > - __func__, desc->type); > + DPRINTF(sc, IWN_DEBUG_CALIBRATE | IWN_DEBUG_STATS, > + "%s: received statistics, cmd %d, len %d\n", > + __func__, desc->type, le16toh(desc->len)); > sc->calib_cnt = 0; /* Reset TX power calibration timeout. */ > > - /* Collect/track general statistics for reporting */ > - iwn_stats_update(sc, calib, stats); > + /* > + * Collect/track general statistics for reporting. > + * > + * This takes care of ensuring that the bluetooth sized message > + * will be correctly converted to the legacy sized message. > + */ > + iwn_stats_update(sc, calib, stats, le16toh(desc->len)); > + > + /* > + * And now, let's take a reference of it to use! > + */ > + lstats = &sc->last_stat; > > /* Test if temperature has changed. */ > - if (stats->general.temp != sc->rawtemp) { > + if (lstats->general.temp != sc->rawtemp) { > /* Convert "raw" temperature to degC. */ > sc->rawtemp = stats->general.temp; > temp = ops->get_temperature(sc); > @@ -3202,25 +3272,25 @@ iwn_rx_statistics(struct iwn_softc *sc, > if (desc->type != IWN_BEACON_STATISTICS) > return; /* Reply to a statistics request. */ > > - sc->noise = iwn_get_noise(&stats->rx.general); > + sc->noise = iwn_get_noise(&lstats->rx.general); > DPRINTF(sc, IWN_DEBUG_CALIBRATE, "%s: noise %d\n", __func__, sc->noise); > > /* Test that RSSI and noise are present in stats report. */ > - if (le32toh(stats->rx.general.flags) != 1) { > + if (le32toh(lstats->rx.general.flags) != 1) { > DPRINTF(sc, IWN_DEBUG_ANY, "%s\n", > "received statistics without RSSI"); > return; > } > > if (calib->state == IWN_CALIB_STATE_ASSOC) > - iwn_collect_noise(sc, &stats->rx.general); > + iwn_collect_noise(sc, &lstats->rx.general); > else if (calib->state == IWN_CALIB_STATE_RUN) { > - iwn_tune_sensitivity(sc, &stats->rx); > + iwn_tune_sensitivity(sc, &lstats->rx); > /* > * XXX TODO: Only run the RX recovery if we're associated! > */ > - iwn_check_rx_recovery(sc, stats); > - iwn_save_stats_counters(sc, stats); > + iwn_check_rx_recovery(sc, lstats); > + iwn_save_stats_counters(sc, lstats); > } > > DPRINTF(sc, IWN_DEBUG_TRACE, "->%s: end\n",__func__); > _______________________________________________ > 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 Mar 6 07:41:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59C537B0 for ; Thu, 6 Mar 2014 07:41:55 +0000 (UTC) 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 1772CA60 for ; Thu, 6 Mar 2014 07:41:55 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id i8so2434260qcq.23 for ; Wed, 05 Mar 2014 23:41:54 -0800 (PST) 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:content-transfer-encoding; bh=ldyWLXzqkkzA7UL1/4jF2pgJsdPtct9ZUuGe9dlHFpk=; b=alu8/dCtutz0wAK5XQxH2rCoofgXIhWDEz1CNaREXULZP3gmrGbLIV7YdUBOXiv63E yvsV3qUgtDD6Pb2a+pdqTcE9KWL/MmKpMymEhoO/OnVKKIrjEeAFKNVKj4V2ePWym05Q LYNPH8gJU2Z4lpYwrsEWCW9nDHCnfWBLHNGlrCQHB00kXmx7u4l8myYWqCPZkqVi0LqM DO1gvMJYZjtyam7anNpSsesfkNaCQ539IQPePwgWnt8hxR1enu5sJSOTfyUuY+cIr1Cw 2zNgckETRE492Gkc3M+TbYM3ojCzIk9tkHZiEtsFuW9c4nqYdWAvJHiDdM7baFOgYH5y ppig== MIME-Version: 1.0 X-Received: by 10.140.42.138 with SMTP id c10mr11652447qga.24.1394091714210; Wed, 05 Mar 2014 23:41:54 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Wed, 5 Mar 2014 23:41:54 -0800 (PST) In-Reply-To: <53182646.3010004@shurik.kiev.ua> References: <201403040801.s2481uAc088743@svn.freebsd.org> <53182646.3010004@shurik.kiev.ua> Date: Wed, 5 Mar 2014 23:41:54 -0800 X-Google-Sender-Auth: sl0tyreFPJR57j_rIa50E7XiLVQ Message-ID: Subject: Re: Fwd: svn commit: r262729 - head/sys/dev/iwn From: Adrian Chadd To: Alexandr Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Mar 2014 07:41:55 -0000 Your intel 2230 problems aren't calibration related. My intel 2230 and intel 2200 both work fine everywhere I use them, but I don't have a laptop with it in there all the time. -a On 5 March 2014 23:39, Alexandr wrote: > My 2230 still not working in 11n > > 04.03.2014 10:09, Adrian Chadd =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> If you have a Centrino 100, 2200, 2230, then please update to the >> latest -HEAD. This may fix some calibration issues. >> >> >> -a >> >> >> >> ---------- Forwarded message ---------- >> From: Adrian Chadd >> Date: 4 March 2014 00:01 >> Subject: svn commit: r262729 - head/sys/dev/iwn >> To: src-committers@freebsd.org, svn-src-all@freebsd.org, >> svn-src-head@freebsd.org >> >> >> Author: adrian >> Date: Tue Mar 4 08:01:56 2014 >> New Revision: 262729 >> URL: http://svnweb.freebsd.org/changeset/base/262729 >> >> Log: >> Handle the newer-style bluetooth message format from the (at least) >> Centrino 2230 firmware. >> >> This fixes the general statistics block to be actually valid. >> >> I've verified this by contrasting the output of iwnstats before and >> after the change. The general block is now correct. >> >> Tested: >> >> * Intel 5100 (old format stats message) >> * Intel 2230 (new format stats message) >> >> Modified: >> head/sys/dev/iwn/if_iwn.c >> >> Modified: head/sys/dev/iwn/if_iwn.c >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >> --- head/sys/dev/iwn/if_iwn.c Tue Mar 4 06:55:54 2014 (r262728= ) >> +++ head/sys/dev/iwn/if_iwn.c Tue Mar 4 08:01:56 2014 (r262729= ) >> @@ -685,6 +685,13 @@ iwn_attach(device_t dev) >> goto fail; >> } >> >> +#if 0 >> + device_printf(sc->sc_dev, "%s: rx_stats=3D%d, rx_stats_bt=3D%d\n= ", >> + __func__, >> + sizeof(struct iwn_stats), >> + sizeof(struct iwn_stats_bt)); >> +#endif >> + >> if (bootverbose) >> ieee80211_announce(ic); >> DPRINTF(sc, IWN_DEBUG_TRACE, "->%s: end\n",__func__); >> @@ -3143,11 +3150,62 @@ iwn5000_rx_calib_results(struct iwn_soft >> >> static void >> iwn_stats_update(struct iwn_softc *sc, struct iwn_calib_state *calib, >> - struct iwn_stats *stats) >> + struct iwn_stats *stats, int len) >> { >> + struct iwn_stats_bt *stats_bt; >> + struct iwn_stats *lstats; >> + >> + /* >> + * First - check whether the length is the bluetooth or normal. >> + * >> + * If it's normal - just copy it and bump out. >> + * Otherwise we have to convert things. >> + */ >> + >> + if (len =3D=3D sizeof(struct iwn_stats) + 4) { >> + memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); >> + sc->last_stat_valid =3D 1; >> + return; >> + } >> >> - /* XXX lock assert */ >> - memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); >> + /* >> + * If it's not the bluetooth size - log, then just copy. >> + */ >> + if (len !=3D sizeof(struct iwn_stats_bt) + 4) { >> + DPRINTF(sc, IWN_DEBUG_STATS, >> + "%s: size of rx statistics (%d) not an expected size= !\n", >> + __func__, >> + len); >> + memcpy(&sc->last_stat, stats, sizeof(struct iwn_stats)); >> + sc->last_stat_valid =3D 1; >> + return; >> + } >> + >> + /* >> + * Ok. Time to copy. >> + */ >> + stats_bt =3D (struct iwn_stats_bt *) stats; >> + lstats =3D &sc->last_stat; >> + >> + /* flags */ >> + lstats->flags =3D stats_bt->flags; >> + /* rx_bt */ >> + memcpy(&lstats->rx.ofdm, &stats_bt->rx_bt.ofdm, >> + sizeof(struct iwn_rx_phy_stats)); >> + memcpy(&lstats->rx.cck, &stats_bt->rx_bt.cck, >> + sizeof(struct iwn_rx_phy_stats)); >> + memcpy(&lstats->rx.general, &stats_bt->rx_bt.general_bt.common, >> + sizeof(struct iwn_rx_general_stats)); >> + memcpy(&lstats->rx.ht, &stats_bt->rx_bt.ht, >> + sizeof(struct iwn_rx_ht_phy_stats)); >> + /* tx */ >> + memcpy(&lstats->tx, &stats_bt->tx, >> + sizeof(struct iwn_tx_stats)); >> + /* general */ >> + memcpy(&lstats->general, &stats_bt->general, >> + sizeof(struct iwn_general_stats)); >> + >> + /* XXX TODO: Squirrel away the extra bluetooth stats somewhere *= / >> sc->last_stat_valid =3D 1; >> } >> >> @@ -3165,6 +3223,7 @@ iwn_rx_statistics(struct iwn_softc *sc, >> struct ieee80211vap *vap =3D TAILQ_FIRST(&ic->ic_vaps); >> struct iwn_calib_state *calib =3D &sc->calib; >> struct iwn_stats *stats =3D (struct iwn_stats *)(desc + 1); >> + struct iwn_stats *lstats; >> int temp; >> >> DPRINTF(sc, IWN_DEBUG_TRACE, "->%s begin\n", __func__); >> @@ -3179,15 +3238,26 @@ iwn_rx_statistics(struct iwn_softc *sc, >> >> bus_dmamap_sync(sc->rxq.data_dmat, data->map, BUS_DMASYNC_POSTRE= AD); >> >> - DPRINTF(sc, IWN_DEBUG_CALIBRATE, "%s: received statistics, cmd %= d\n", >> - __func__, desc->type); >> + DPRINTF(sc, IWN_DEBUG_CALIBRATE | IWN_DEBUG_STATS, >> + "%s: received statistics, cmd %d, len %d\n", >> + __func__, desc->type, le16toh(desc->len)); >> sc->calib_cnt =3D 0; /* Reset TX power calibration timeout.= */ >> >> - /* Collect/track general statistics for reporting */ >> - iwn_stats_update(sc, calib, stats); >> + /* >> + * Collect/track general statistics for reporting. >> + * >> + * This takes care of ensuring that the bluetooth sized message >> + * will be correctly converted to the legacy sized message. >> + */ >> + iwn_stats_update(sc, calib, stats, le16toh(desc->len)); >> + >> + /* >> + * And now, let's take a reference of it to use! >> + */ >> + lstats =3D &sc->last_stat; >> >> /* Test if temperature has changed. */ >> - if (stats->general.temp !=3D sc->rawtemp) { >> + if (lstats->general.temp !=3D sc->rawtemp) { >> /* Convert "raw" temperature to degC. */ >> sc->rawtemp =3D stats->general.temp; >> temp =3D ops->get_temperature(sc); >> @@ -3202,25 +3272,25 @@ iwn_rx_statistics(struct iwn_softc *sc, >> if (desc->type !=3D IWN_BEACON_STATISTICS) >> return; /* Reply to a statistics request. */ >> >> - sc->noise =3D iwn_get_noise(&stats->rx.general); >> + sc->noise =3D iwn_get_noise(&lstats->rx.general); >> DPRINTF(sc, IWN_DEBUG_CALIBRATE, "%s: noise %d\n", __func__, sc-= >noise); >> >> /* Test that RSSI and noise are present in stats report. */ >> - if (le32toh(stats->rx.general.flags) !=3D 1) { >> + if (le32toh(lstats->rx.general.flags) !=3D 1) { >> DPRINTF(sc, IWN_DEBUG_ANY, "%s\n", >> "received statistics without RSSI"); >> return; >> } >> >> if (calib->state =3D=3D IWN_CALIB_STATE_ASSOC) >> - iwn_collect_noise(sc, &stats->rx.general); >> + iwn_collect_noise(sc, &lstats->rx.general); >> else if (calib->state =3D=3D IWN_CALIB_STATE_RUN) { >> - iwn_tune_sensitivity(sc, &stats->rx); >> + iwn_tune_sensitivity(sc, &lstats->rx); >> /* >> * XXX TODO: Only run the RX recovery if we're associate= d! >> */ >> - iwn_check_rx_recovery(sc, stats); >> - iwn_save_stats_counters(sc, stats); >> + iwn_check_rx_recovery(sc, lstats); >> + iwn_save_stats_counters(sc, lstats); >> } >> >> DPRINTF(sc, IWN_DEBUG_TRACE, "->%s: end\n",__func__); >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.o= rg" > > _______________________________________________ > 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" From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 6 14:11:01 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F1561F2; Thu, 6 Mar 2014 14:11:01 +0000 (UTC) Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3710E98C; Thu, 6 Mar 2014 14:11:00 +0000 (UTC) Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s26EAwlI024994; Thu, 6 Mar 2014 09:10:58 -0500 (EST) (envelope-from curtis@ipv6.occnc.com) Message-Id: <201403061410.s26EAwlI024994@maildrop2.v6ds.occnc.com> To: Adrian Chadd From: Curtis Villamizar Subject: Re: iwn rtsol on stable/10 with merge from head In-reply-to: Your message of "Sat, 01 Mar 2014 16:35:35 -0800." Date: Thu, 06 Mar 2014 09:10:58 -0500 Cc: "freebsd-wireless@freebsd.org" , curtis@ipv6.occnc.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: curtis@ipv6.occnc.com 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, 06 Mar 2014 14:11:01 -0000 Adrian, I compiled all of src from head and the problems went away except that occasionally I get a long (or semi-permanent) lack of connectivity after a switch in APs. Often restarting dhclient fixes this, even though I'm using IPv6. Its possible that something is missing from the RA messages, like DNS or default route. I put a set of iwstats output on http://www.occnc.com/iwn/ . The last plenary session dump may be the best. I have ifconfig iwn0 and ifconfig iwn0 scan data to go along with it. Everything worked fine for most of the time, then a switch of AP happenned. Curtis In message Adrian Chadd writes: > > Maybe the whole cloned interfaces path isn't setting up the ipv6 flags > correctly? > > > -a > > > On 1 March 2014 16:02, Curtis Villamizar wrote: > > > > In message > > Adrian Chadd writes: > > > >> Hi, > >> > >> Please grab and try 'iwnstats' from head - tools/tools/iwn/iwnstats - > >> it'll be interesting to see what stats are logged when you're in busy > >> air. > > > > Typical WG sessions have 50-200 people. The technical plenary (Monday > > evening) and the administrative plenary (Thursday evening) typically > > have around 1,000. That's mostly geeks with wifi in their phones plus > > their laptops. I'll try to get stats in WG sessions and both plenaries. > > > >> I have no idea about rtsold, sorry. :( > > > > I'm not sure the cause but the cure has something to do with this: > > > > A little RTFC on rtsold/if.c reveals that ND6_IFF_ACCEPT_RTADV is not > > set in nd.ndi.flags which comes from the lines: > > > > if (ioctl(s, SIOCGIFINFO_IN6, (caddr_t)&nd) < 0) { > > [...] > > } > > if (!(nd.ndi.flags & ND6_IFF_ACCEPT_RTADV)) { > > > > A man ifconfig reveals: > > > > accept_rtadv > > Set a flag to enable accepting ICMPv6 Router > > Advertisement messages. The sysctl(8) variable > > net.inet6.ip6.accept_rtadv controls whether this flag is > > set by default or not. > > > > So the workaround is to add net.inet6.ip6.accept_rtadv=1 to > > /etc/sysctl.conf. A one time test using "ifconfig wlan0 inet6 > > accept_rtadv" and restarting rtsold also confirms this is the > > problem. > > > > The mystery is really why this doesn't affect em0 and run0 on the same > > machine. I'll have to check and make sure they don't all behave the > > same with the same kernel. None of these driveres have the string > > rtadv. In sys/dev "grep -il rtadv */*.[hc]" yields nothing. The > > string ND6_IFF_ACCEPT_RTADV only appears in sys files in the netinet6 > > directory. Reading the code, iwn seems to do what is right with > > net.inet6.ip6.accept_rtadv clear and the others (em0, run0, plus msk0 > > on another machine, em0 on other machines) have ND6_IFF_ACCEPT_RTADV > > set even though net.inet6.ip6.accept_rtadv is not set. > > > > The entire src/sys tree is from head but the rest of src is stable/10. > > > >> -a > > > > I'll try to get the stats next week but it looks like I'll need to > > build the src distribution from head to get that done, pulling just > > iwnstats from head. Merging tools/tools/iwn/iwnstats into the > > stable/10 tree didn't compile. Not a big deal but pressed for time > > between now and then. > > > > Curtis > > > > > >> On 1 March 2014 09:11, Curtis Villamizar wrote: > >> > > >> > rtsol is not working for my kernel build with iwn but everything else > >> > works. > >> > > >> > I'm running a very recent stable/10 (kernel is 262621) upgraded to > >> > pick up iwn stuff from head: > >> > > >> > svn merge \ > >> > https://svn0.us-east.freebsd.org/base/head/sys/dev/iwn \ > >> > dev/iwn > >> > svn merge \ > >> > https://svn0.us-east.freebsd.org/base/head/sys/modules/iwnfw \ > >> > modules/iwnfw > >> > svn merge > >> > https://svn0.us-east.freebsd.org/base/head/sys/contrib/dev/iwn \ > >> > contrib/dev/iwn > >> > > >> > That was to get the Centrino 2000 support from the head branch. > >> > > >> > That works. > >> > > >> > iwn0: > >> > mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci3 > >> > > >> > Everything works as far as I can tell except rtsol. > >> > > >> > # rtsold -f -d -D wlan0 > >> > checking if wlan0 is ready... > >> > wlan0 does not accept Router Advertisement. > >> > set timer for wlan0 to 1s > >> > New timer is 1s > >> > timer expiration on wlan0, state = 3 > >> > checking if wlan0 is ready... > >> > wlan0 does not accept Router Advertisement. > >> > set timer for wlan0 to 1s > >> > New timer is 1s > >> > timer expiration on wlan0, state = 3 > >> > checking if wlan0 is ready... > >> > wlan0 does not accept Router Advertisement. > >> > set timer for wlan0 to 1s > >> > New timer is 1s > >> > [ ... etc ... ] > >> > > >> > If I use rtsold -a it sees wlan0 as not ready and doesn't try to use > >> > it but then it receives occasional RA anyway but ignores them because > >> > it sees wlan0 as not ready. > >> > > >> > If I ifconfig inet6 ... alias I get an IPv6 address configured and > >> > manually add a default route, then everything is fine. This > >> > workaround is OK for home but is not practical for roaming about (like > >> > going to IETF) if I want IPv6 to work. > >> > > >> > Does anyone know why rtsold isn't seeing wlan0 as ready? Is there any > >> > info I could provide? How likely is it that will a kernel built from > >> > head this would just go away and rtsold would just work. > >> > > >> > btw- headed for IETF so I'll have a chance to test iwn in a very busy > >> > environment and would be willing to help if anyone wants to do that > >> > sort of debugging. [I have a usb wlan (run0) as a fallback] > >> > > >> > Curtis From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 6 14:41:16 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09CF87D7; Thu, 6 Mar 2014 14:41:16 +0000 (UTC) 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 D416ED42; Thu, 6 Mar 2014 14:41:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s26EfF3W008243; Thu, 6 Mar 2014 14:41:15 GMT (envelope-from gjb@freefall.freebsd.org) Received: (from gjb@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s26EfFk9008242; Thu, 6 Mar 2014 14:41:15 GMT (envelope-from gjb) Date: Thu, 6 Mar 2014 14:41:15 GMT Message-Id: <201403061441.s26EfFk9008242@freefall.freebsd.org> To: matthieu.volat@gmail.com, gjb@FreeBSD.org, freebsd-wireless@FreeBSD.org From: gjb@FreeBSD.org Subject: Re: kern/163719: [ath] ath interface do not receive multicast X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Mar 2014 14:41:16 -0000 Synopsis: [ath] ath interface do not receive multicast State-Changed-From-To: open->closed State-Changed-By: gjb State-Changed-When: Thu Mar 6 14:40:52 UTC 2014 State-Changed-Why: Closed at submitter's request, AP was the problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=163719 From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 8 22:51:45 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47645303 for ; Sat, 8 Mar 2014 22:51:45 +0000 (UTC) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13E7A316 for ; Sat, 8 Mar 2014 22:51:44 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n16so5690954oag.13 for ; Sat, 08 Mar 2014 14:51:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=DjVRqxM5UBKtCJFbvnpjo4oY73SuU11GtfUdeuEuigk=; b=OeFBrI0lfNgOGy8bNlyItoPExC5xEXAhu1SE+eMzgMV6Bj5+xTMjXtNFi7MtusR4f3 OvWzg1sIXeEV0kM5j8ZrU3oy8JoZBFmE18EJbOnKtcCxbFAwFI/4YSO64xozhboiShKy 2c2YSARfin4Mneg+pTrA1NpsaR+JvSZJosXFASJmBA5mAMYkc+OBYqEd0Sp0mhYKMbn8 QJdfcq01BY+wNVWMR6oZZeCVTnNSBsxLWq7LB5aMvAKQP46dtKMUzWdlFeXjjmGGZmNu RRra2i/Ebugz1SGuQtbYVgYPcIk90LmCsZP58oob43HyEdgVpvujy3OklSoCWItPpogJ pqIQ== X-Gm-Message-State: ALoCoQkITVJdJK6aw5ejsJhgjkNUTOOuUEyvIiD/uwy7NMBWMYDvtRq6NNqOMSMpLK50lCJXNhse MIME-Version: 1.0 X-Received: by 10.60.116.35 with SMTP id jt3mr17629014oeb.41.1394319103952; Sat, 08 Mar 2014 14:51:43 -0800 (PST) Received: by 10.182.104.169 with HTTP; Sat, 8 Mar 2014 14:51:43 -0800 (PST) Date: Sat, 8 Mar 2014 15:51:43 -0700 Message-ID: Subject: trouble with urtwn From: Tom Everett To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Mar 2014 22:51:45 -0000 Good afternoon. I've got a urtwn device and this in my /boot/loader.conf console="comconsole" legal.realtek.license_ack=1 if_urtwn_load="YES" However when I issue a scan request like this ifconfig wlan0 create wlandev urtwn0 ifconfig wlan0 up scan I get this on the console. urtwn-rtl8192cfwT: You need to read the LICENSE file in /usr/share/doc/legal/realtek/. urtwn-rtl8192cfwT: If you agree with the license, set legal.realtek.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (urtwn_rtl8192cfwT_fw, 0xc76fc4f0, 0) error 1 urtwn-rtl8192cfwT: could not load firmware image, error 8 urtwn0: failed loadfirmware of file urtwn-rtl8192cfwT Have I missed a step? -- A better world shall emerge based on faith and understanding - Douglas MacArthur From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 9 19:21:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 415DD898 for ; Sun, 9 Mar 2014 19:21:17 +0000 (UTC) Received: from felyko.com (felyko.com [IPv6:2607:f2f8:a528::3:1337:ca7]) by mx1.freebsd.org (Postfix) with ESMTP id 2C2FAB5F for ; Sun, 9 Mar 2014 19:21:17 +0000 (UTC) Received: from [10.0.1.3] (c-24-6-115-18.hsd1.ca.comcast.net [24.6.115.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id DBE213983D; Sun, 9 Mar 2014 12:21:15 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: trouble with urtwn From: Rui Paulo In-Reply-To: Date: Sun, 9 Mar 2014 12:21:15 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Tom Everett X-Mailer: Apple Mail (2.1874) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 19:21:17 -0000 On 8 Mar 2014, at 14:51, Tom Everett wrote: > Good afternoon. >=20 > I've got a urtwn device and this in my /boot/loader.conf >=20 > console=3D"comconsole" >=20 > legal.realtek.license_ack=3D1 >=20 > if_urtwn_load=3D"YES" >=20 > However when I issue a scan request like this >=20 > ifconfig wlan0 create wlandev urtwn0 >=20 > ifconfig wlan0 up scan >=20 > I get this on the console. >=20 > urtwn-rtl8192cfwT: You need to read the LICENSE file in > /usr/share/doc/legal/realtek/. > urtwn-rtl8192cfwT: If you agree with the license, set > legal.realtek.license_ack=3D1 in /boot/loader.conf. > module_register_init: MOD_LOAD (urtwn_rtl8192cfwT_fw, 0xc76fc4f0, 0) = error 1 > urtwn-rtl8192cfwT: could not load firmware image, error 8 > urtwn0: failed loadfirmware of file urtwn-rtl8192cfwT >=20 > Have I missed a step? You either need to reboot after changing /boot/loader.conf or you need = to do "kenv legal.realtek.license_ack=3D1". -- Rui Paulo From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 9 19:26:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0CEB7B40 for ; Sun, 9 Mar 2014 19:26:13 +0000 (UTC) Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C9EB7C07 for ; Sun, 9 Mar 2014 19:26:12 +0000 (UTC) Received: by mail-ob0-f169.google.com with SMTP id va2so6151295obc.28 for ; Sun, 09 Mar 2014 12:26:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=RwJhu60yvsvHx34JDv9ifkjCuWwNRF49uoXUXCOotDU=; b=AHGIS0BsHtVUGIv8R0PmFHyzwUa2KRo4xbdr8JDletuBFScif6VSewHz31f8HhUN5f r019UlAigSWx/FiUKzDfYx4KqkBTwVL9UiNR3unDpmLnpwnDBipvJx2kVUUqv61lXiI+ /WhFL8pCt6uZcKc/DNPsD9FiNKZRsRip6nrUXtRKncagb13eRny2zr2WabEDYlBveydB KrmSBIg+vIQb3Eogvg/TrJXKh4yCcSmUPzMC4IGpt1piVcAy1f+gyrxJ1aphQ8zxtUBa hBbmAkpbQtrBE4RXu8csrhJJWNOntlI5cWShKIcDMdi88NdAtHHYsjEDsFLgj2V7BltY 0GGA== X-Gm-Message-State: ALoCoQkgY7OdR2Hcw7C6OX1GH/nj3tW4pHCqJqST67329EkRgfX0bWNfGfLNQmbnH0GwlS1pGJUe MIME-Version: 1.0 X-Received: by 10.60.94.52 with SMTP id cz20mr3199772oeb.43.1394393166754; Sun, 09 Mar 2014 12:26:06 -0700 (PDT) Received: by 10.182.104.169 with HTTP; Sun, 9 Mar 2014 12:26:06 -0700 (PDT) In-Reply-To: References: Date: Sun, 9 Mar 2014 13:26:06 -0600 Message-ID: Subject: Re: trouble with urtwn From: Tom Everett To: Rui Paulo Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 19:26:13 -0000 Just to close the loop, the bug was mine. In the Crochet-FreeBSD configuration I had /boot/loader.conf, and it was properly configured. Unfortunately I didn't have a /boot/loader.rc, so loader.conf was never loaded. On Sun, Mar 9, 2014 at 1:21 PM, Rui Paulo wrote: > On 8 Mar 2014, at 14:51, Tom Everett wrote: > > > Good afternoon. > > > > I've got a urtwn device and this in my /boot/loader.conf > > > > console="comconsole" > > > > legal.realtek.license_ack=1 > > > > if_urtwn_load="YES" > > > > However when I issue a scan request like this > > > > ifconfig wlan0 create wlandev urtwn0 > > > > ifconfig wlan0 up scan > > > > I get this on the console. > > > > urtwn-rtl8192cfwT: You need to read the LICENSE file in > > /usr/share/doc/legal/realtek/. > > urtwn-rtl8192cfwT: If you agree with the license, set > > legal.realtek.license_ack=1 in /boot/loader.conf. > > module_register_init: MOD_LOAD (urtwn_rtl8192cfwT_fw, 0xc76fc4f0, 0) > error 1 > > urtwn-rtl8192cfwT: could not load firmware image, error 8 > > urtwn0: failed loadfirmware of file urtwn-rtl8192cfwT > > > > Have I missed a step? > > You either need to reboot after changing /boot/loader.conf or you need to > do "kenv legal.realtek.license_ack=1". > > -- > Rui Paulo > > > > -- A better world shall emerge based on faith and understanding - Douglas MacArthur From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 9 19:27:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ABAFFB66 for ; Sun, 9 Mar 2014 19:27:10 +0000 (UTC) Received: from felyko.com (felyko.com [IPv6:2607:f2f8:a528::3:1337:ca7]) by mx1.freebsd.org (Postfix) with ESMTP id 93C2FC12 for ; Sun, 9 Mar 2014 19:27:10 +0000 (UTC) Received: from [IPv6:2601:9:8280:603:6116:d4d3:8f52:22c9] (unknown [IPv6:2601:9:8280:603:6116:d4d3:8f52:22c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id E547F3983D; Sun, 9 Mar 2014 12:27:09 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: trouble with urtwn From: Rui Paulo In-Reply-To: Date: Sun, 9 Mar 2014 12:27:08 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <4E5D5035-E0F6-4AFC-8F6D-F1641577BAF3@FreeBSD.org> References: To: Tom Everett X-Mailer: Apple Mail (2.1874) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 19:27:10 -0000 On 9 Mar 2014, at 12:26, Tom Everett wrote: > Just to close the loop, the bug was mine. In the Crochet-FreeBSD = configuration I had /boot/loader.conf, and it was properly configured. = Unfortunately I didn't have a /boot/loader.rc, so loader.conf was never = loaded. Which platform is this? /boot/loader.rc was added to several ARM = platforms last year. -- Rui Paulo From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 9 20:15:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59F43905 for ; Sun, 9 Mar 2014 20:15:55 +0000 (UTC) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20ED9FD5 for ; Sun, 9 Mar 2014 20:15:54 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id i4so6142595oah.24 for ; Sun, 09 Mar 2014 13:15:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9lUJxfskUJ9vVkegBxKwBfpkuWVo4RhGOuuvj6dpNk0=; b=IkeBOT4jNshKOZWxyeKU9uynGxyyeNMG6cS89XnexU5GhkbV6e6DCla3wkbC2keuEd lIOGI9NIzDH7gCfncVE2atH7CKbLM3opmyBhpCUht97PU6BiihiH+vYpZ5RLFsJMnBqy hjsCswcvKHkIoTgjl+tbp5xfx4UNUIC3YyVuAMpJbGfoHJYH9kM0mHP3uu+RcRWPzgJS ED3vE2BCxhPmTDvAUt2qVz7hii2w++SwofzkgRwnlBo4ciEM1Qk1N/ctzfTT/wxBqGwP L+2GF6cRP0NVAgMfcgCge9DHrBtvyTIgOPdL/2Xqdb+LPFPM6SuaD8y9lqoOfMiOiyt3 BItA== X-Gm-Message-State: ALoCoQlEXfJVZHvxpFT7BiCa0uvmQ4cLAQRULolh1nKdsm1sxvzZPj4MFnFyISJExrzTpME44EJe MIME-Version: 1.0 X-Received: by 10.182.22.18 with SMTP id z18mr3035255obe.42.1394396154202; Sun, 09 Mar 2014 13:15:54 -0700 (PDT) Received: by 10.182.104.169 with HTTP; Sun, 9 Mar 2014 13:15:54 -0700 (PDT) In-Reply-To: <4E5D5035-E0F6-4AFC-8F6D-F1641577BAF3@FreeBSD.org> References: <4E5D5035-E0F6-4AFC-8F6D-F1641577BAF3@FreeBSD.org> Date: Sun, 9 Mar 2014 14:15:54 -0600 Message-ID: Subject: Re: trouble with urtwn From: Tom Everett To: Rui Paulo Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 20:15:55 -0000 Wandboard. Here: https://github.com/teverett/crochet-freebsd/tree/master/board/Wandboard On Sun, Mar 9, 2014 at 1:27 PM, Rui Paulo wrote: > On 9 Mar 2014, at 12:26, Tom Everett wrote: > > > Just to close the loop, the bug was mine. In the Crochet-FreeBSD > configuration I had /boot/loader.conf, and it was properly configured. > Unfortunately I didn't have a /boot/loader.rc, so loader.conf was never > loaded. > > Which platform is this? /boot/loader.rc was added to several ARM > platforms last year. > > -- > Rui Paulo > > > > -- A better world shall emerge based on faith and understanding - Douglas MacArthur From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 9 21:05:35 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1C26639 for ; Sun, 9 Mar 2014 21:05:35 +0000 (UTC) Received: from felyko.com (felyko.com [174.136.100.2]) by mx1.freebsd.org (Postfix) with ESMTP id 99D60633 for ; Sun, 9 Mar 2014 21:05:35 +0000 (UTC) Received: from [10.0.1.3] (c-24-6-115-18.hsd1.ca.comcast.net [24.6.115.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id D3F6D39841; Sun, 9 Mar 2014 14:05:25 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: trouble with urtwn From: Rui Paulo In-Reply-To: Date: Sun, 9 Mar 2014 14:05:26 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <0F222A34-DE35-4108-924B-C27A4C47308D@FreeBSD.org> References: <4E5D5035-E0F6-4AFC-8F6D-F1641577BAF3@FreeBSD.org> To: Tom Everett X-Mailer: Apple Mail (2.1874) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 21:05:35 -0000 On 9 Mar 2014, at 13:15, Tom Everett wrote: > Wandboard. =20 >=20 > Here: = https://github.com/teverett/crochet-freebsd/tree/master/board/Wandboard OK, nevermind. I suppose you have a loader.rc.sample. -- Rui Paulo From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 10 11:06:56 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69ECD1E9 for ; Mon, 10 Mar 2014 11:06:56 +0000 (UTC) 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 3CBA0827 for ; Mon, 10 Mar 2014 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2AB6ubp043413 for ; Mon, 10 Mar 2014 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2AB6tTc043411 for freebsd-wireless@FreeBSD.org; Mon, 10 Mar 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Mar 2014 11:06:55 GMT Message-Id: <201403101106.s2AB6tTc043411@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.17 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, 10 Mar 2014 11:06:56 -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/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 192 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 11 17:54:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F56D2F4 for ; Tue, 11 Mar 2014 17:54:48 +0000 (UTC) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E08C2628 for ; Tue, 11 Mar 2014 17:54:47 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id e16so10062293qcx.13 for ; Tue, 11 Mar 2014 10:54:47 -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=Pgmgp5fLUem0c1fC3N57/B/ZwrwPNW4/anPhEjdVKbs=; b=TlzvUjgdfkXfMD4AEZgfUNEnSWnPuDDrgftj9J2r5gxms3u53NDkMD//9eB/hGBkVL Vx3GPjATC5nqpy04K0HIbH7/0BU+CVSeoZP1V+6ZRLj7BzxuNa5NWE8ZBI6ieooNnJkb svxRrFeMAnC/RrPQV0iMHGLVLVTMkWkfl+GIXJ3c2JpwIzj8zgvcbaxHQB1sbsoJ/n6a j7AWVEM2ohTrwJD4Ft+iuKff7qTkpK/iQVk1gvyCOYs+I5IPiQIYQ2mwEwJSREOXQ2kO RNWraAufg5Socii3nQrhxizay3tY6QLW+pcQZQw748yK3Ye+bYArFIpx7Vx/z6PCNpa3 /uOA== MIME-Version: 1.0 X-Received: by 10.140.42.21 with SMTP id b21mr4121527qga.87.1394560486989; Tue, 11 Mar 2014 10:54:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Tue, 11 Mar 2014 10:54:46 -0700 (PDT) In-Reply-To: <201403111653.s2BGrN13026531@maildrop2.v6ds.occnc.com> References: <201403111653.s2BGrN13026531@maildrop2.v6ds.occnc.com> Date: Tue, 11 Mar 2014 10:54:46 -0700 X-Google-Sender-Auth: UJvkDJgxbdOFSeAxWhuzi-RAZ6g Message-ID: Subject: Re: iwn rtsol on stable/10 with merge from head From: Adrian Chadd To: curtis@ipv6.occnc.com, "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Mar 2014 17:54:48 -0000 Hm. If the noise values start fluctuating wildly before it starts missing beacons, this could tell me that the receiver is getting confused. I should finish the "retune by doing a single channel scan" hack that iwlwifi does; maybe it'll help quieten things down a bit. Thanks, -a On 11 March 2014 09:53, Curtis Villamizar wrote: > > In message > Adrian Chadd writes: > >> Hi! >> >> Thanks, >> >> Is it switching APs in the same BSS (ie, same SSID, different AP) or >> different BSS (different SSID) ? >> >> -a > > > I didn't check but it should be same SSID since my wpa_supplicant.conf > prefered the "ietf" SSID in part of the week and the "ietf-v6ONLY" > SSID later in the week. There were plenty of APs with the "ietf" SSID > and "ietf-v6ONLY" SSID. If jumping to a new AP it might have been due > to congestion, not signal strength. > > I also found that when using the "ietf-v6ONLY" SSID that no DNS server > or default route were provided in the IPv6 RA but the M bit was set. > IPv6 only would only work if the client saw the M bit and ran DHCPv6 > (or edited /etc/resolv.conf and added a default route by hand). > > Note that in http://www.occnc.com/iwn/iwn.scan.0306-13:59.plenary > there is a jump from bssid 00:17:df:aa:57:51 to status: no carrier > (despite many viable APs) at 13:54:53 then at 13:55:03 associated with > bssid 00:17:df:a9:c5:e1 . The scan entries are: > > ietf 00:17:df:aa:57:51 6 54M -76:-95 102 ES HTCAP WME > ietf 00:17:df:a9:c5:e1 1 54M -79:-95 102 ES HTCAP WME > > Both channel 1 and channel 6 are very crowded with 16 APs (2 with ietf > SSID) and 12 APs (1 with ietf SSID). There may be a hint in > http://www.occnc.com/iwn/iwnstats.0306-13:59.plenary as to why the > change in SSID but without timestamps it may be hard (for me) to find. > A hint might be that missed+beacons=0 up to a point where it starts > rising, then goes to zero, then rises and goes to zero a few times. > At the first transition to non-zero, there is also a big jump in > moise. Not much else I see in there. > > Perhaps useful things to add to the iwnstats would be timestamp, > channel, ssid, bssid and record a reason for most recent AP change. > Maybe the place to look for this is in the wpa_supplicant debug output > which I did not collect. btw- wpa_supplicant -f file doesn't work. > > On some related topics: > > Is there any detectable change that devd might notice associated > to/from no-carrier transitions or on switch to another AP? If so that > would help a lot in that we could put dhclient and rtsold entries in > devd.conf in case the AP changed and the subnet, dns, and default > route also chnage with the new AP. If not a hook in wpa_supplicant > would be needed to handle this. > > It would also help if rtsold had a hook that could be used to run > dhclient -6 when the M bit was set in the RA (and dhclient -6 -x > when/if M gets cleared, though it might kill both the -4 and -6 > instances or the wrong one). > > Curtis > > >> On 6 March 2014 06:10, Curtis Villamizar wrote: >> > >> > Adrian, >> > >> > I compiled all of src from head and the problems went away except that >> > occasionally I get a long (or semi-permanent) lack of connectivity >> > after a switch in APs. Often restarting dhclient fixes this, even >> > though I'm using IPv6. Its possible that something is missing from >> > the RA messages, like DNS or default route. >> > >> > I put a set of iwstats output on http://www.occnc.com/iwn/ . >> > The last plenary session dump may be the best. I have ifconfig iwn0 >> > and ifconfig iwn0 scan data to go along with it. Everything worked >> > fine for most of the time, then a switch of AP happenned. >> > >> > Curtis >> > >> > >> > In message >> > Adrian Chadd writes: >> >> >> >> Maybe the whole cloned interfaces path isn't setting up the ipv6 flags >> >> correctly? >> >> >> >> >> >> -a >> >> >> >> >> >> On 1 March 2014 16:02, Curtis Villamizar wrote: >> >> > >> >> > In message >> >> > Adrian Chadd writes: >> >> > >> >> >> Hi, >> >> >> >> >> >> Please grab and try 'iwnstats' from head - tools/tools/iwn/iwnstats - >> >> >> it'll be interesting to see what stats are logged when you're in busy >> >> >> air. >> >> > >> >> > Typical WG sessions have 50-200 people. The technical plenary (Monday >> >> > evening) and the administrative plenary (Thursday evening) typically >> >> > have around 1,000. That's mostly geeks with wifi in their phones plus >> >> > their laptops. I'll try to get stats in WG sessions and both plenaries. >> >> > >> >> >> I have no idea about rtsold, sorry. :( >> >> > >> >> > I'm not sure the cause but the cure has something to do with this: >> >> > >> >> > A little RTFC on rtsold/if.c reveals that ND6_IFF_ACCEPT_RTADV is not >> >> > set in nd.ndi.flags which comes from the lines: >> >> > >> >> > if (ioctl(s, SIOCGIFINFO_IN6, (caddr_t)&nd) < 0) { >> >> > [...] >> >> > } >> >> > if (!(nd.ndi.flags & ND6_IFF_ACCEPT_RTADV)) { >> >> > >> >> > A man ifconfig reveals: >> >> > >> >> > accept_rtadv >> >> > Set a flag to enable accepting ICMPv6 Router >> >> > Advertisement messages. The sysctl(8) variable >> >> > net.inet6.ip6.accept_rtadv controls whether this flag is >> >> > set by default or not. >> >> > >> >> > So the workaround is to add net.inet6.ip6.accept_rtadv=1 to >> >> > /etc/sysctl.conf. A one time test using "ifconfig wlan0 inet6 >> >> > accept_rtadv" and restarting rtsold also confirms this is the >> >> > problem. >> >> > >> >> > The mystery is really why this doesn't affect em0 and run0 on the same >> >> > machine. I'll have to check and make sure they don't all behave the >> >> > same with the same kernel. None of these driveres have the string >> >> > rtadv. In sys/dev "grep -il rtadv */*.[hc]" yields nothing. The >> >> > string ND6_IFF_ACCEPT_RTADV only appears in sys files in the netinet6 >> >> > directory. Reading the code, iwn seems to do what is right with >> >> > net.inet6.ip6.accept_rtadv clear and the others (em0, run0, plus msk0 >> >> > on another machine, em0 on other machines) have ND6_IFF_ACCEPT_RTADV >> >> > set even though net.inet6.ip6.accept_rtadv is not set. >> >> > >> >> > The entire src/sys tree is from head but the rest of src is stable/10. >> >> > >> >> >> -a >> >> > >> >> > I'll try to get the stats next week but it looks like I'll need to >> >> > build the src distribution from head to get that done, pulling just >> >> > iwnstats from head. Merging tools/tools/iwn/iwnstats into the >> >> > stable/10 tree didn't compile. Not a big deal but pressed for time >> >> > between now and then. >> >> > >> >> > Curtis >> >> > >> >> > >> >> >> On 1 March 2014 09:11, Curtis Villamizar wrote: >> >> >> > >> >> >> > rtsol is not working for my kernel build with iwn but everything else >> >> >> > works. >> >> >> > >> >> >> > I'm running a very recent stable/10 (kernel is 262621) upgraded to >> >> >> > pick up iwn stuff from head: >> >> >> > >> >> >> > svn merge \ >> >> >> > https://svn0.us-east.freebsd.org/base/head/sys/dev/iwn \ >> >> >> > dev/iwn >> >> >> > svn merge \ >> >> >> > https://svn0.us-east.freebsd.org/base/head/sys/modules/iwnfw \ >> >> >> > modules/iwnfw >> >> >> > svn merge >> >> >> > https://svn0.us-east.freebsd.org/base/head/sys/contrib/dev/iwn \ >> >> >> > contrib/dev/iwn >> >> >> > >> >> >> > That was to get the Centrino 2000 support from the head branch. >> >> >> > >> >> >> > That works. >> >> >> > >> >> >> > iwn0: >> >> >> > mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci3 >> >> >> > >> >> >> > Everything works as far as I can tell except rtsol. >> >> >> > >> >> >> > # rtsold -f -d -D wlan0 >> >> >> > checking if wlan0 is ready... >> >> >> > wlan0 does not accept Router Advertisement. >> >> >> > set timer for wlan0 to 1s >> >> >> > New timer is 1s >> >> >> > timer expiration on wlan0, state = 3 >> >> >> > checking if wlan0 is ready... >> >> >> > wlan0 does not accept Router Advertisement. >> >> >> > set timer for wlan0 to 1s >> >> >> > New timer is 1s >> >> >> > timer expiration on wlan0, state = 3 >> >> >> > checking if wlan0 is ready... >> >> >> > wlan0 does not accept Router Advertisement. >> >> >> > set timer for wlan0 to 1s >> >> >> > New timer is 1s >> >> >> > [ ... etc ... ] >> >> >> > >> >> >> > If I use rtsold -a it sees wlan0 as not ready and doesn't try to use >> >> >> > it but then it receives occasional RA anyway but ignores them because >> >> >> > it sees wlan0 as not ready. >> >> >> > >> >> >> > If I ifconfig inet6 ... alias I get an IPv6 address configured and >> >> >> > manually add a default route, then everything is fine. This >> >> >> > workaround is OK for home but is not practical for roaming about (like >> >> >> > going to IETF) if I want IPv6 to work. >> >> >> > >> >> >> > Does anyone know why rtsold isn't seeing wlan0 as ready? Is there any >> >> >> > info I could provide? How likely is it that will a kernel built from >> >> >> > head this would just go away and rtsold would just work. >> >> >> > >> >> >> > btw- headed for IETF so I'll have a chance to test iwn in a very busy >> >> >> > environment and would be willing to help if anyone wants to do that >> >> >> > sort of debugging. [I have a usb wlan (run0) as a fallback] >> >> >> > >> >> >> > Curtis From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 11 18:03:22 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B0BA89A; Tue, 11 Mar 2014 18:03:22 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B7372789; Tue, 11 Mar 2014 18:03:21 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id f51so9716536qge.2 for ; Tue, 11 Mar 2014 11:03:21 -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=i4+XfluFzo/cAwSVfvf/cMrxRv8j/gmhoi6SqtKHL74=; b=GZBKTrKHflKuanah+F6lP5T7R3Df3jyTdvbcgeW/932PtyTQqfvoOksbGOjPb//sQM TmO6F5Bk9atWYNHH9ooRgDbzNpXnSzKEbJaJ/Ze9FybgTV4Q9joZ00CN9Vobphm1rju3 mGqwwAgs+pKcSKYgudmLwGLuUYP58uuhaOpWzjzAiaa35td7/5QNapQovUlE0kaRi3+t l0ez2kr25ZdXwKq2EZI7j/tMweDOFgWiDOQqZR94pvXtBvkvxMpWvvYAmmzTXo+Y/ZW1 OVAdsFIuWA/pXZaLMPS9jd+hAPjEmsZ/qskd6X/jgHxCE8t4QlRuP5J+BHaoQfLPv/sj +BTw== MIME-Version: 1.0 X-Received: by 10.224.13.142 with SMTP id c14mr4803647qaa.76.1394561000942; Tue, 11 Mar 2014 11:03:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Tue, 11 Mar 2014 11:03:20 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> Date: Tue, 11 Mar 2014 11:03:20 -0700 X-Google-Sender-Auth: h0wlVnLcz7Wn7hfZsadDYtyx9kA Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Tom Murphy Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Mar 2014 18:03:22 -0000 I still don't have any ideas here. I do however want to try hacking the driver to transmit EAPOL frames at the management rate, and then ensure the management rate is non-MCS. -a On 28 February 2014 15:14, Adrian Chadd wrote: > Hi, > > the interesting bits: > > > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 3 len 129 nsegs 2 rate > 0002 plcp 0x0000420a > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 4 len 129 nsegs 2 rate > 0002 plcp 0x0000420a > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 3 retries 16 nkill > 0 rate 80006902 duration 2815 status 83 > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 4 retries 16 nkill > 0 rate 80006902 duration 2815 status 83 > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 5 len 129 nsegs 2 rate > 0002 plcp 0x0000420a > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 6 len 129 nsegs 2 rate > 0002 plcp 0x0000420a > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 5 retries 16 nkill > 0 rate 80006902 duration 2815 status 83 > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 6 retries 16 nkill > 0 rate 80006902 duration 2815 status 83 > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 7 len 129 nsegs 2 rate > 0002 plcp 0x0000420a > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 8 len 129 nsegs 2 rate > 0002 plcp 0x0000420a > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 7 retries 16 nkill > 0 rate 80006902 duration 2815 status 83 > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 8 retries 16 nkill > 0 rate 80006902 duration 2815 status 83 > > .. so it's failing to transmit the management frames after association > - they're being transmitted at MCS0 and the AP is just plain not > ACKing them. > > Now, I don't know why this is. It's trying to transmit the initial > frame at non-MCS rates, but I have a feeling the multi-rate retry > table thing is confusing it and it's trying to send it as MCS. So > maybe the AP doesn't like management frames at MCS rates. > > I'll have to think about this a little. > > -a > > > On 28 February 2014 15:07, Tom Murphy wrote: >> I've attached my iwn debug messages to this email starting >> with the point I tried to associate to the Wifi. >> >> Thanks again for looking at this! >> >> Kind regards, >> Tom >> >> On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote: >>> On 26 February 2014 23:52, Alexandr wrote: >>> > Tom, could you: >>> > >>> > 1. compile kernel WITH_IWNDEBUG >>> > 2. sysctl dev.iwn.0.debug=0x1 >>> > 3. wlandebug -i wlan0 auth+assoc >>> > 4. Associate with AP in 11n mode >>> > 5. Send us appropriate /var/log/messages >>> > >>> > Then I try to compare it with my log. >>> >>> Please do. I've been trying to track down the source of this "ht just >>> doesn't work!" but it works fine with all of the Intel NICs I have >>> here. >>> >>> Can someone see if they can find a mtaching NIC online (amazon,ebay?) >>> Owning one that I can whack in a laptop is likely going ot help things >>> a lot. >>> >>> Thanks, >>> >>> >>> -a From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 11 23:22:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D7256AA; Tue, 11 Mar 2014 23:22:37 +0000 (UTC) Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BDCAC146; Tue, 11 Mar 2014 23:22:36 +0000 (UTC) Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s2BNMXHt031385; Tue, 11 Mar 2014 19:22:33 -0400 (EDT) (envelope-from curtis@ipv6.occnc.com) Message-Id: <201403112322.s2BNMXHt031385@maildrop2.v6ds.occnc.com> To: Adrian Chadd From: Curtis Villamizar Subject: Re: iwn rtsol on stable/10 with merge from head In-reply-to: Your message of "Tue, 11 Mar 2014 10:54:46 -0700." Date: Tue, 11 Mar 2014 19:22:32 -0400 Cc: "freebsd-wireless@freebsd.org" , curtis@ipv6.occnc.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: curtis@ipv6.occnc.com 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, 11 Mar 2014 23:22:37 -0000 In message Adrian Chadd writes: > > Hm. If the noise values start fluctuating wildly before it starts > missing beacons, this could tell me that the receiver is getting > confused. > > I should finish the "retune by doing a single channel scan" hack that > iwlwifi does; maybe it'll help quieten things down a bit. > > Thanks, > > -a Adrian, Some of the problem may be due to AP close by on the same channel and nearly the same signal strength, many with same SSID. On the first drop there were 30 AP on channel 6 (the channel being used) all at 54M and 6 with SSID "ietf". Its definitely a demanding environment. btw- I can't get you any more data in super busy air until next IETF in July. I'd be willing to work more closely with you to collect any data that you need if that helps. Curtis From owner-freebsd-wireless@FreeBSD.ORG Fri Mar 14 23:13:36 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22E83695 for ; Fri, 14 Mar 2014 23:13:36 +0000 (UTC) Received: from ns.umpquanet.com (ns.umpquanet.com [98.158.10.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E5AD1B4A for ; Fri, 14 Mar 2014 23:13:35 +0000 (UTC) Received: from ns.umpquanet.com (localhost [127.0.0.1]) by ns.umpquanet.com (8.14.5/8.14.5) with ESMTP id s2EN0EAV076089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 14 Mar 2014 16:00:14 -0700 (PDT) (envelope-from james@museum.rain.com) Received: (from james@localhost) by ns.umpquanet.com (8.14.5/8.14.5/Submit) id s2EN0EaZ076088 for freebsd-wireless@freebsd.org; Fri, 14 Mar 2014 16:00:14 -0700 (PDT) (envelope-from james@museum.rain.com) Date: Fri, 14 Mar 2014 16:00:14 -0700 From: Jim Long To: freebsd-wireless@freebsd.org Subject: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 Message-ID: <20140314230013.GA25473@ns.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 14 Mar 2014 23:13:36 -0000 I have a long-standing problem that involves the iwi interface on my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. Some wifi connections I make show good signal strength, but poor latency and/or packet loss to the WAP IP. I can't find other wifi users who perceive the wifi performance as poor, so I am assuming the problem is local to me. I will say this is generally repeatable by location: good locations are usually good, bad locations are usually bad. My theory is that the 2200BG likes some WAPs that I use more than it likes others. I'd like to find out what I can do to either fix the problem, or at least be able to accurately tell the WAP owner what their problem is. I'm ignorant about how to troubleshoot problems like this, so please suggest some diagnostic information I can provide to guide either of us toward a solution. Thank you, Jim from dmesg: iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 wlan0: Ethernet address: 00:12:f0:ca:5c:85 I get this a lot, but don't know if it's relevant. It seems to appear during both good and bad connections: iwi0: need multicast update callback Here's 61db of S/N ratio, resulting in almost 50% packet loss: $ wlanstats ; ping -c20 wap2 36 rx frame too short 5 rx from wrong bssid 374 rx discard 'cuz dup 5 rx discard 'cuz mcast echo 3 rx discard mgt frames 1347 rx beacon frames 4151 rx element unknown 42 rx frame chan mismatch 7 rx disassociation 7 beacon miss events handled 6 active scans started 1446 rx management frames 2 tx failed 'cuz vap not in RUN state 28752 total data frames received 8679 unicast data frames received 20073 multicast data frames received 12186 total data frames transmit 12186 unicast data frames sent 54M current transmit rate 61 current rssi -95 current noise floor (dBm) -34 current signal (dBm) PING wap2 (192.168.2.1): 56 data bytes 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms --- wap2 ping statistics --- 20 packets transmitted, 11 packets received, 45.0% packet loss round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms To my knowledge the OS is using the latest 3.1 firmware for the interface: $ cd /usr/src/sys/contrib/dev/iwi $ grep ^FW Makefile; md5 * FW_VERSION=3.1 MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 00:18:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E959D8F for ; Sat, 15 Mar 2014 00:18:43 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20DD6FC3 for ; Sat, 15 Mar 2014 00:18:43 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id m20so3723378qcx.7 for ; Fri, 14 Mar 2014 17:18:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JvUFRU5zqRoDrSp/Oxh+pjAae8dcntSuNjJojLbjPRM=; b=NgWUqapPI2IrztQodfGkRW9KF/Zr2N3EEyWG+EbfmZV9uBCey5J2/NISMmKL18lnHn YbdyMb9GxtRH4DGg1nynrGsYpg/hWQfkGrEhRbpEl4uvjDHUiWtsdGTgbcwRqK82yR78 2kTK8wimiAGPQ9+2wNdbV4/4Zvrl+HfjZbpuBnllHumfaqm7lHq2d50gIboH82souXMu AqIZu2C8eE51/IfgOAO4oWe50iDW6Axl6G61hbeWNNGLYsT8fhA9mO9rgNZe5nguUstQ yex5FMEAxhtBZkM5p8xJ2AaTzZDtuIxCDBEZqOYJlQwui5R1ZO+mavnoXYy4Tobyf8Su hkBg== MIME-Version: 1.0 X-Received: by 10.140.101.244 with SMTP id u107mr54422qge.107.1394842722397; Fri, 14 Mar 2014 17:18:42 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 17:18:42 -0700 (PDT) In-Reply-To: <20140314230013.GA25473@ns.umpquanet.com> References: <20140314230013.GA25473@ns.umpquanet.com> Date: Fri, 14 Mar 2014 17:18:42 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 00:18:43 -0000 Hi, I'm not sure what kind of statistics or diagnostics iwi spits out. It's likely worth reviewing the linux and freebsd drivers to see if it does spit out any kind of statistics messages. That's a good starting point. Thanks! -a On 14 March 2014 16:00, Jim Long wrote: > I have a long-standing problem that involves the iwi interface on > my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. > > Some wifi connections I make show good signal strength, but poor > latency and/or packet loss to the WAP IP. I can't find other > wifi users who perceive the wifi performance as poor, so I am > assuming the problem is local to me. > > I will say this is generally repeatable by location: good > locations are usually good, bad locations are usually bad. My > theory is that the 2200BG likes some WAPs that I use more than it > likes others. I'd like to find out what I can do to either fix > the problem, or at least be able to accurately tell the WAP owner > what their problem is. > > I'm ignorant about how to troubleshoot problems like this, so > please suggest some diagnostic information I can provide to guide > either of us toward a solution. > > Thank you, > > Jim > > from dmesg: > > iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 > wlan0: Ethernet address: 00:12:f0:ca:5c:85 > > I get this a lot, but don't know if it's relevant. It seems > to appear during both good and bad connections: > > iwi0: need multicast update callback > > > Here's 61db of S/N ratio, resulting in almost 50% packet loss: > > $ wlanstats ; ping -c20 wap2 > 36 rx frame too short > 5 rx from wrong bssid > 374 rx discard 'cuz dup > 5 rx discard 'cuz mcast echo > 3 rx discard mgt frames > 1347 rx beacon frames > 4151 rx element unknown > 42 rx frame chan mismatch > 7 rx disassociation > 7 beacon miss events handled > 6 active scans started > 1446 rx management frames > 2 tx failed 'cuz vap not in RUN state > 28752 total data frames received > 8679 unicast data frames received > 20073 multicast data frames received > 12186 total data frames transmit > 12186 unicast data frames sent > 54M current transmit rate > 61 current rssi > -95 current noise floor (dBm) > -34 current signal (dBm) > PING wap2 (192.168.2.1): 56 data bytes > 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms > 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms > 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms > 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms > 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms > 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms > 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms > 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms > 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms > 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms > 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms > > --- wap2 ping statistics --- > 20 packets transmitted, 11 packets received, 45.0% packet loss > round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms > > To my knowledge the OS is using the latest 3.1 firmware for the > interface: > > $ cd /usr/src/sys/contrib/dev/iwi > $ grep ^FW Makefile; md5 * > FW_VERSION=3.1 > MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a > MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 > MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b > MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 > MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 > > _______________________________________________ > 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 Sat Mar 15 00:50:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8468831A for ; Sat, 15 Mar 2014 00:50:13 +0000 (UTC) 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 43DFD295 for ; Sat, 15 Mar 2014 00:50:13 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id k15so3326469qaq.29 for ; Fri, 14 Mar 2014 17:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zSPa8k5NfnqCHiikNCwVlcja9AONLn3vayI4xXmYCQA=; b=WObEEBVp/P5+i6rPQaDAviElCpP6Qx8sRFipgCdS9lWgvbjgk0axrR2CKCKslxB7lB IVmGLEcM1K3y5/cHW5uYcgR6bdFWXPLzDyl14jWVTyyzuO30an/iadSRoDPbcJKgneNs pNLWhaXhv5VTk51T3nTSD79uPz7QGw8l0z+WmSeh55LqrO0vUTYfopLEtlvJsUPpAdVg 7MUf5IExroaWRmaRgMndKn01EDR/UBtpK+sjyjLGLhKBAw/3m6JpW9EzkV/IG9P9UFD1 9mSFXs99tAUa9r6Zuo8k+1TNcif8AuUfSnLJOoqxZ++XgyKBMjaW3OMPsd6cUA7/VOMg looQ== MIME-Version: 1.0 X-Received: by 10.224.127.129 with SMTP id g1mr13429195qas.22.1394844612427; Fri, 14 Mar 2014 17:50:12 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 17:50:12 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> Date: Fri, 14 Mar 2014 17:50:12 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 00:50:13 -0000 It'd be stuff like this: case IWI_NOTIF_TYPE_CALIBRATION: case IWI_NOTIF_TYPE_NOISE: case IWI_NOTIF_TYPE_LINK_QUALITY: DPRINTFN(5, ("Notification (%u)\n", notif->type)); break; -a On 14 March 2014 17:18, Adrian Chadd wrote: > Hi, > > I'm not sure what kind of statistics or diagnostics iwi spits out. > It's likely worth reviewing the linux and freebsd drivers to see if it > does spit out any kind of statistics messages. That's a good starting > point. > > Thanks! > > > -a > > > On 14 March 2014 16:00, Jim Long wrote: >> I have a long-standing problem that involves the iwi interface on >> my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. >> >> Some wifi connections I make show good signal strength, but poor >> latency and/or packet loss to the WAP IP. I can't find other >> wifi users who perceive the wifi performance as poor, so I am >> assuming the problem is local to me. >> >> I will say this is generally repeatable by location: good >> locations are usually good, bad locations are usually bad. My >> theory is that the 2200BG likes some WAPs that I use more than it >> likes others. I'd like to find out what I can do to either fix >> the problem, or at least be able to accurately tell the WAP owner >> what their problem is. >> >> I'm ignorant about how to troubleshoot problems like this, so >> please suggest some diagnostic information I can provide to guide >> either of us toward a solution. >> >> Thank you, >> >> Jim >> >> from dmesg: >> >> iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 >> wlan0: Ethernet address: 00:12:f0:ca:5c:85 >> >> I get this a lot, but don't know if it's relevant. It seems >> to appear during both good and bad connections: >> >> iwi0: need multicast update callback >> >> >> Here's 61db of S/N ratio, resulting in almost 50% packet loss: >> >> $ wlanstats ; ping -c20 wap2 >> 36 rx frame too short >> 5 rx from wrong bssid >> 374 rx discard 'cuz dup >> 5 rx discard 'cuz mcast echo >> 3 rx discard mgt frames >> 1347 rx beacon frames >> 4151 rx element unknown >> 42 rx frame chan mismatch >> 7 rx disassociation >> 7 beacon miss events handled >> 6 active scans started >> 1446 rx management frames >> 2 tx failed 'cuz vap not in RUN state >> 28752 total data frames received >> 8679 unicast data frames received >> 20073 multicast data frames received >> 12186 total data frames transmit >> 12186 unicast data frames sent >> 54M current transmit rate >> 61 current rssi >> -95 current noise floor (dBm) >> -34 current signal (dBm) >> PING wap2 (192.168.2.1): 56 data bytes >> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms >> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms >> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms >> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms >> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms >> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms >> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms >> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms >> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms >> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms >> 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms >> >> --- wap2 ping statistics --- >> 20 packets transmitted, 11 packets received, 45.0% packet loss >> round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms >> >> To my knowledge the OS is using the latest 3.1 firmware for the >> interface: >> >> $ cd /usr/src/sys/contrib/dev/iwi >> $ grep ^FW Makefile; md5 * >> FW_VERSION=3.1 >> MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a >> MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 >> MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b >> MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 >> MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 >> >> _______________________________________________ >> 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 Sat Mar 15 00:52:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 139A24E9 for ; Sat, 15 Mar 2014 00:52:09 +0000 (UTC) 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 C7E21310 for ; Sat, 15 Mar 2014 00:52:08 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id x13so3697728qcv.5 for ; Fri, 14 Mar 2014 17:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ovPjgQLDmHToGnhzBxvpUcV6ZMEFc5b9ofShR8hV0HE=; b=O4a4pF5TkM2OlTWPdEkyRvx9McUTOJb5+hr/XHrQd2kV8nG7TA/MX27MzmqDr3MRpN /7gd77pu1vKs6hEZTr5fRY8Mld6NJS2ia4vCkBkB6z0EoC4NBv+BEACtFkdD3aDTgi0U gfGHdEPCAJLHuPVpizYHTsouV7iX1leO5ytoXGQa25E8gsCSwMw1FWI656LtGKarVq8s UApNdojGgOLZta2+EF37suc04IBTn5IbFogDUUWSaUShhTJ8laKIj5chffoxat5PoCCG esnrnOqJf5uP7oxXXljEsFRlZLx7zUSPY9P/iTYX9FWNSxwsDf8e5siQwjjtbP61NBi/ HrJw== MIME-Version: 1.0 X-Received: by 10.140.95.172 with SMTP id i41mr845598qge.70.1394844728052; Fri, 14 Mar 2014 17:52:08 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 17:52:07 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> Date: Fri, 14 Mar 2014 17:52:07 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 00:52:09 -0000 Hi, right. The linux driver (ipw2x00) has a bunch more quality related stuff that I don't think the iwi driver is decoding. But i bet a little bit of C coding would get the statistics out into a useful format that we can log and analyse. -a On 14 March 2014 17:50, Adrian Chadd wrote: > It'd be stuff like this: > > case IWI_NOTIF_TYPE_CALIBRATION: > case IWI_NOTIF_TYPE_NOISE: > case IWI_NOTIF_TYPE_LINK_QUALITY: > DPRINTFN(5, ("Notification (%u)\n", notif->type)); > break; > > > > -a > > > On 14 March 2014 17:18, Adrian Chadd wrote: >> Hi, >> >> I'm not sure what kind of statistics or diagnostics iwi spits out. >> It's likely worth reviewing the linux and freebsd drivers to see if it >> does spit out any kind of statistics messages. That's a good starting >> point. >> >> Thanks! >> >> >> -a >> >> >> On 14 March 2014 16:00, Jim Long wrote: >>> I have a long-standing problem that involves the iwi interface on >>> my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. >>> >>> Some wifi connections I make show good signal strength, but poor >>> latency and/or packet loss to the WAP IP. I can't find other >>> wifi users who perceive the wifi performance as poor, so I am >>> assuming the problem is local to me. >>> >>> I will say this is generally repeatable by location: good >>> locations are usually good, bad locations are usually bad. My >>> theory is that the 2200BG likes some WAPs that I use more than it >>> likes others. I'd like to find out what I can do to either fix >>> the problem, or at least be able to accurately tell the WAP owner >>> what their problem is. >>> >>> I'm ignorant about how to troubleshoot problems like this, so >>> please suggest some diagnostic information I can provide to guide >>> either of us toward a solution. >>> >>> Thank you, >>> >>> Jim >>> >>> from dmesg: >>> >>> iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 >>> wlan0: Ethernet address: 00:12:f0:ca:5c:85 >>> >>> I get this a lot, but don't know if it's relevant. It seems >>> to appear during both good and bad connections: >>> >>> iwi0: need multicast update callback >>> >>> >>> Here's 61db of S/N ratio, resulting in almost 50% packet loss: >>> >>> $ wlanstats ; ping -c20 wap2 >>> 36 rx frame too short >>> 5 rx from wrong bssid >>> 374 rx discard 'cuz dup >>> 5 rx discard 'cuz mcast echo >>> 3 rx discard mgt frames >>> 1347 rx beacon frames >>> 4151 rx element unknown >>> 42 rx frame chan mismatch >>> 7 rx disassociation >>> 7 beacon miss events handled >>> 6 active scans started >>> 1446 rx management frames >>> 2 tx failed 'cuz vap not in RUN state >>> 28752 total data frames received >>> 8679 unicast data frames received >>> 20073 multicast data frames received >>> 12186 total data frames transmit >>> 12186 unicast data frames sent >>> 54M current transmit rate >>> 61 current rssi >>> -95 current noise floor (dBm) >>> -34 current signal (dBm) >>> PING wap2 (192.168.2.1): 56 data bytes >>> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms >>> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms >>> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms >>> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms >>> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms >>> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms >>> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms >>> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms >>> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms >>> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms >>> 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms >>> >>> --- wap2 ping statistics --- >>> 20 packets transmitted, 11 packets received, 45.0% packet loss >>> round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms >>> >>> To my knowledge the OS is using the latest 3.1 firmware for the >>> interface: >>> >>> $ cd /usr/src/sys/contrib/dev/iwi >>> $ grep ^FW Makefile; md5 * >>> FW_VERSION=3.1 >>> MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a >>> MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 >>> MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b >>> MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 >>> MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 >>> >>> _______________________________________________ >>> 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 Sat Mar 15 01:06:42 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F125ABA for ; Sat, 15 Mar 2014 01:06:42 +0000 (UTC) Received: from ns.umpquanet.com (ns.umpquanet.com [98.158.10.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 08A2B5F0 for ; Sat, 15 Mar 2014 01:06:41 +0000 (UTC) Received: from ns.umpquanet.com (localhost [127.0.0.1]) by ns.umpquanet.com (8.14.5/8.14.5) with ESMTP id s2F16ehF077729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2014 18:06:40 -0700 (PDT) (envelope-from james@museum.rain.com) Received: (from james@localhost) by ns.umpquanet.com (8.14.5/8.14.5/Submit) id s2F16ejd077728; Fri, 14 Mar 2014 18:06:40 -0700 (PDT) (envelope-from james@museum.rain.com) Date: Fri, 14 Mar 2014 18:06:40 -0700 From: Jim Long To: Adrian Chadd Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 Message-ID: <20140315010640.GB65392@ns.umpquanet.com> References: <20140314230013.GA25473@ns.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 01:06:42 -0000 Thank you for your reply. This would be via syslog in /var/log/messages? Nothing that I see: $ zgrep -il notification /var/log/messages* $ On Fri, Mar 14, 2014 at 05:50:12PM -0700, Adrian Chadd wrote: > It'd be stuff like this: > > case IWI_NOTIF_TYPE_CALIBRATION: > case IWI_NOTIF_TYPE_NOISE: > case IWI_NOTIF_TYPE_LINK_QUALITY: > DPRINTFN(5, ("Notification (%u)\n", notif->type)); > break; > > > > -a > > > On 14 March 2014 17:18, Adrian Chadd wrote: > > Hi, > > > > I'm not sure what kind of statistics or diagnostics iwi spits out. > > It's likely worth reviewing the linux and freebsd drivers to see if it > > does spit out any kind of statistics messages. That's a good starting > > point. > > > > Thanks! > > > > > > -a > > > > > > On 14 March 2014 16:00, Jim Long wrote: > >> I have a long-standing problem that involves the iwi interface on > >> my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. > >> > >> Some wifi connections I make show good signal strength, but poor > >> latency and/or packet loss to the WAP IP. I can't find other > >> wifi users who perceive the wifi performance as poor, so I am > >> assuming the problem is local to me. > >> > >> I will say this is generally repeatable by location: good > >> locations are usually good, bad locations are usually bad. My > >> theory is that the 2200BG likes some WAPs that I use more than it > >> likes others. I'd like to find out what I can do to either fix > >> the problem, or at least be able to accurately tell the WAP owner > >> what their problem is. > >> > >> I'm ignorant about how to troubleshoot problems like this, so > >> please suggest some diagnostic information I can provide to guide > >> either of us toward a solution. > >> > >> Thank you, > >> > >> Jim > >> > >> from dmesg: > >> > >> iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 > >> wlan0: Ethernet address: 00:12:f0:ca:5c:85 > >> > >> I get this a lot, but don't know if it's relevant. It seems > >> to appear during both good and bad connections: > >> > >> iwi0: need multicast update callback > >> > >> > >> Here's 61db of S/N ratio, resulting in almost 50% packet loss: > >> > >> $ wlanstats ; ping -c20 wap2 > >> 36 rx frame too short > >> 5 rx from wrong bssid > >> 374 rx discard 'cuz dup > >> 5 rx discard 'cuz mcast echo > >> 3 rx discard mgt frames > >> 1347 rx beacon frames > >> 4151 rx element unknown > >> 42 rx frame chan mismatch > >> 7 rx disassociation > >> 7 beacon miss events handled > >> 6 active scans started > >> 1446 rx management frames > >> 2 tx failed 'cuz vap not in RUN state > >> 28752 total data frames received > >> 8679 unicast data frames received > >> 20073 multicast data frames received > >> 12186 total data frames transmit > >> 12186 unicast data frames sent > >> 54M current transmit rate > >> 61 current rssi > >> -95 current noise floor (dBm) > >> -34 current signal (dBm) > >> PING wap2 (192.168.2.1): 56 data bytes > >> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms > >> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms > >> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms > >> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms > >> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms > >> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms > >> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms > >> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms > >> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms > >> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms > >> 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms > >> > >> --- wap2 ping statistics --- > >> 20 packets transmitted, 11 packets received, 45.0% packet loss > >> round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms > >> > >> To my knowledge the OS is using the latest 3.1 firmware for the > >> interface: > >> > >> $ cd /usr/src/sys/contrib/dev/iwi > >> $ grep ^FW Makefile; md5 * > >> FW_VERSION=3.1 > >> MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a > >> MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 > >> MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b > >> MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 > >> MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 > >> > >> _______________________________________________ > >> 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 Sat Mar 15 01:55:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E04CA930 for ; Sat, 15 Mar 2014 01:55:16 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 89202A9B for ; Sat, 15 Mar 2014 01:55:16 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id a108so9720440qge.3 for ; Fri, 14 Mar 2014 18:55:15 -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=hLiJVwowsPuHLRMwmb3ORBZsIOl7B7n6hSpaxhipP/w=; b=lpcZSz0+VIXd9u1A1ysKyqCqiob7SLA1cqJ8a8qj2aIKeRUsRGYgc4qpXRuqMopcVH Z2zIL3/+K4ekQl3YlshFG161GBPY71yHwC5VUVuNgIDewu+Im7m7fmJMw/1E+Sc8ufoT QOWtyPvWbJfWl2bsWjMA3WG2BD9juU92hurTAx+o8pOuXVmpZtSBz7FiCc0RWs8rMMh2 5qyk8Wey14XIIhstkGMN39u4TCNA3GFFm1CkkF2yBARhQ2t+ZnCHr87CgkxO/aNyV8hE m0RvCCyLLcmnC3sgQQdWkM+czgCSYX24U7Ltk1vzf+RQ2fiNREQ6HidZ8zPM8e/T4vWQ kCcw== MIME-Version: 1.0 X-Received: by 10.140.48.165 with SMTP id o34mr13104177qga.16.1394848515716; Fri, 14 Mar 2014 18:55:15 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 18:55:15 -0700 (PDT) In-Reply-To: <20140315010640.GB65392@ns.umpquanet.com> References: <20140314230013.GA25473@ns.umpquanet.com> <20140315010640.GB65392@ns.umpquanet.com> Date: Fri, 14 Mar 2014 18:55:15 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 01:55:17 -0000 Nope; there's no code for handling the messages yet. I'll dig around to see if I can find a 2200 series NIC in a laptop here or in my collection. I know I have 3945 NICs, but not the 2200.. -a On 14 March 2014 18:06, Jim Long wrote: > Thank you for your reply. > > This would be via syslog in /var/log/messages? Nothing that I see: > > $ zgrep -il notification /var/log/messages* > $ > > > > On Fri, Mar 14, 2014 at 05:50:12PM -0700, Adrian Chadd wrote: >> It'd be stuff like this: >> >> case IWI_NOTIF_TYPE_CALIBRATION: >> case IWI_NOTIF_TYPE_NOISE: >> case IWI_NOTIF_TYPE_LINK_QUALITY: >> DPRINTFN(5, ("Notification (%u)\n", notif->type)); >> break; >> >> >> >> -a >> >> >> On 14 March 2014 17:18, Adrian Chadd wrote: >> > Hi, >> > >> > I'm not sure what kind of statistics or diagnostics iwi spits out. >> > It's likely worth reviewing the linux and freebsd drivers to see if it >> > does spit out any kind of statistics messages. That's a good starting >> > point. >> > >> > Thanks! >> > >> > >> > -a >> > >> > >> > On 14 March 2014 16:00, Jim Long wrote: >> >> I have a long-standing problem that involves the iwi interface on >> >> my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. >> >> >> >> Some wifi connections I make show good signal strength, but poor >> >> latency and/or packet loss to the WAP IP. I can't find other >> >> wifi users who perceive the wifi performance as poor, so I am >> >> assuming the problem is local to me. >> >> >> >> I will say this is generally repeatable by location: good >> >> locations are usually good, bad locations are usually bad. My >> >> theory is that the 2200BG likes some WAPs that I use more than it >> >> likes others. I'd like to find out what I can do to either fix >> >> the problem, or at least be able to accurately tell the WAP owner >> >> what their problem is. >> >> >> >> I'm ignorant about how to troubleshoot problems like this, so >> >> please suggest some diagnostic information I can provide to guide >> >> either of us toward a solution. >> >> >> >> Thank you, >> >> >> >> Jim >> >> >> >> from dmesg: >> >> >> >> iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 >> >> wlan0: Ethernet address: 00:12:f0:ca:5c:85 >> >> >> >> I get this a lot, but don't know if it's relevant. It seems >> >> to appear during both good and bad connections: >> >> >> >> iwi0: need multicast update callback >> >> >> >> >> >> Here's 61db of S/N ratio, resulting in almost 50% packet loss: >> >> >> >> $ wlanstats ; ping -c20 wap2 >> >> 36 rx frame too short >> >> 5 rx from wrong bssid >> >> 374 rx discard 'cuz dup >> >> 5 rx discard 'cuz mcast echo >> >> 3 rx discard mgt frames >> >> 1347 rx beacon frames >> >> 4151 rx element unknown >> >> 42 rx frame chan mismatch >> >> 7 rx disassociation >> >> 7 beacon miss events handled >> >> 6 active scans started >> >> 1446 rx management frames >> >> 2 tx failed 'cuz vap not in RUN state >> >> 28752 total data frames received >> >> 8679 unicast data frames received >> >> 20073 multicast data frames received >> >> 12186 total data frames transmit >> >> 12186 unicast data frames sent >> >> 54M current transmit rate >> >> 61 current rssi >> >> -95 current noise floor (dBm) >> >> -34 current signal (dBm) >> >> PING wap2 (192.168.2.1): 56 data bytes >> >> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms >> >> 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms >> >> >> >> --- wap2 ping statistics --- >> >> 20 packets transmitted, 11 packets received, 45.0% packet loss >> >> round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms >> >> >> >> To my knowledge the OS is using the latest 3.1 firmware for the >> >> interface: >> >> >> >> $ cd /usr/src/sys/contrib/dev/iwi >> >> $ grep ^FW Makefile; md5 * >> >> FW_VERSION=3.1 >> >> MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a >> >> MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 >> >> MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b >> >> MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 >> >> MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 >> >> >> >> _______________________________________________ >> >> 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 Sat Mar 15 02:52:16 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E264825 for ; Sat, 15 Mar 2014 02:52:16 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3D97DF78 for ; Sat, 15 Mar 2014 02:52:15 +0000 (UTC) Received: from [192.168.43.170] (45.sub-174-236-66.myvzw.com [174.236.66.45]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 7AD61192ACD; Sat, 15 Mar 2014 03:17:56 +0000 (UTC) Subject: iwn(4) and WEP From: Sean Bruno To: freebsd-wireless@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-iIN/kLmVWWmZyinJ3JQy" Date: Sat, 15 Mar 2014 11:52:02 +0900 Message-ID: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Sat, 15 Mar 2014 02:52:16 -0000 --=-iIN/kLmVWWmZyinJ3JQy Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable It looks like the wpa_supplicant 2.0 import now checks the cryptocapability mask when trying to validate WEP usage. iwn(4) does not populate the mask with any values so wpa_supplicant sees a value of 0. I added the capabilites and can associate, but dhclient cannot get an IP from the AP. I assume then, that once again, I don't know what I'm doing. More or less, this is what I tried: Index: if_iwn.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- if_iwn.c (revision 263173) +++ if_iwn.c (working copy) @@ -564,6 +564,8 @@ | IEEE80211_C_PMGT /* Station-side power mgmt */ ; =20 + ic->ic_cryptocaps =3D IEEE80211_CRYPTO_WEP; + /* Read MAC address, channels, etc from EEPROM. */ if ((error =3D iwn_read_eeprom(sc, macaddr)) !=3D 0) { device_printf(dev, "could not read EEPROM, error %d\n", sean p.s. Allan Jude came up with a hack for wpa_supplicant that seems to work, so I've bcc'd him here to get a patch out of him. --=-iIN/kLmVWWmZyinJ3JQy Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTI8BOAAoJEBkJRdwI6BaHzd0H/1YOd9h9upfKvfKlF/fma4KN I1CkMI/RrPLQu2VfhXVucR+A1uCJdoTv8AGxR4686vswcMh3yOhaZTmg4/cuB0v7 18KJb06ejnRDj0OtmqUgWf2VHqxpK2dB9uyuRANAy18OtaADc3ZZVGI8JbgFirHx Q6me0B1F8F/tQC/O8weLrBGm0KBIbdfipR4Xu/iJJXnvcDhNsF4FbBWZaiUV3k7m otWgcky6kikZXa+qYP+SKL8OqM2F9zaScIH+d2m/TFhIXxEdb7gjLE8COlVdPIT/ AYaKOQ/nbbNTsSdElG4yJivoscLqM4gz08xtDZ2Zi7xgxzGrTlZPEjoELWomgR4= =pOYs -----END PGP SIGNATURE----- --=-iIN/kLmVWWmZyinJ3JQy-- From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:31:52 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21FEBDD2; Sat, 15 Mar 2014 04:31:52 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C0947B05; Sat, 15 Mar 2014 04:31:51 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id i8so3859119qcq.17 for ; Fri, 14 Mar 2014 21:31:51 -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=Ejsh7xsxBFvjL4vuoScHaBn97WgvJYy3w2rubKRebHI=; b=MWjEtPkB1GrAnuqI6gFWYZsNIx4zDEO/aPIpXCoojnu8LHoIfT6u60uPl6tfGOVPFI 2kGbDy4QEDm7EACK1HEYpe8Qy8typ3U6cYczqwNm6qFp32iKlW2VCZYwa5bLOtI/1BOE Pi2qH47PNaOqanPQx1wtHHNwSvdookSyFEwfHomkSO/u7K3nlGBfTCcpBp4XTIDM4x5Y 0skYrRCVqJ0DRDVsdBIDBOQgSDj7p61Mvpmo2FOGgp6Wf4VyFzzltGnUG+jGZMmfOZg2 Hq0f/zKIVkLcsk3UlLyykdyCYhtETK/7cwMD5M7a8w18VEabAp5BZuI5KCRI+9oZ6ezg GQzA== MIME-Version: 1.0 X-Received: by 10.229.118.4 with SMTP id t4mr14357767qcq.9.1394857910933; Fri, 14 Mar 2014 21:31:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:31:50 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:31:50 -0700 (PDT) In-Reply-To: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> Date: Fri, 14 Mar 2014 21:31:50 -0700 X-Google-Sender-Auth: 9CIkpdE1bPXB4688gkiX54irfek Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 04:31:52 -0000 What other drivers are missing this? Adrian On Mar 14, 2014 7:52 PM, "Sean Bruno" wrote: > It looks like the wpa_supplicant 2.0 import now checks the > cryptocapability mask when trying to validate WEP usage. > > iwn(4) does not populate the mask with any values so wpa_supplicant sees > a value of 0. > > I added the capabilites and can associate, but dhclient cannot get an IP > from the AP. I assume then, that once again, I don't know what I'm > doing. > > More or less, this is what I tried: > > Index: if_iwn.c > =================================================================== > --- if_iwn.c (revision 263173) > +++ if_iwn.c (working copy) > @@ -564,6 +564,8 @@ > | IEEE80211_C_PMGT /* Station-side power mgmt > */ > ; > > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; > + > /* Read MAC address, channels, etc from EEPROM. */ > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { > device_printf(dev, "could not read EEPROM, error %d\n", > > > sean > > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to > work, so I've bcc'd him here to get a patch out of him. > From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:41:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F5ABEC6; Sat, 15 Mar 2014 04:41:02 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 1A2E3BA3; Sat, 15 Mar 2014 04:41:01 +0000 (UTC) Received: from [192.168.11.120] (unknown [180.42.49.96]) (Authenticated sender: roleaccount@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 5962345699; Sat, 15 Mar 2014 04:40:57 +0000 (UTC) Message-ID: <5323D9D4.6090204@allanjude.com> Date: Sat, 15 Mar 2014 00:40:52 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: sbruno@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: iwn(4) and WEP References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> In-Reply-To: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/mixed; boundary="------------070508070906060507080700" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 04:41:02 -0000 This is a multi-part message in MIME format. --------------070508070906060507080700 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 03/14/2014 22:52, Sean Bruno wrote: > It looks like the wpa_supplicant 2.0 import now checks the > cryptocapability mask when trying to validate WEP usage. > > iwn(4) does not populate the mask with any values so wpa_supplicant sees > a value of 0. > > I added the capabilites and can associate, but dhclient cannot get an IP > from the AP. I assume then, that once again, I don't know what I'm > doing. > > More or less, this is what I tried: > > Index: if_iwn.c > =================================================================== > --- if_iwn.c (revision 263173) > +++ if_iwn.c (working copy) > @@ -564,6 +564,8 @@ > | IEEE80211_C_PMGT /* Station-side power mgmt */ > ; > > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; > + > /* Read MAC address, channels, etc from EEPROM. */ > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { > device_printf(dev, "could not read EEPROM, error %d\n", > > > sean > > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to > work, so I've bcc'd him here to get a patch out of him. Attached is my (horrible) patch that no one should use. But it is available for those of us at the conference who just need something that will work for the rest of the weekend. --------------070508070906060507080700 Content-Type: text/x-patch; name="wpa_supplicant.wep.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="wpa_supplicant.wep.patch" Index: contrib/wpa/wpa_supplicant/wpa_supplicant.c =================================================================== --- contrib/wpa/wpa_supplicant/wpa_supplicant.c (revision 261605) +++ contrib/wpa/wpa_supplicant/wpa_supplicant.c (working copy) @@ -3654,6 +3654,11 @@ size_t len = ssid->wep_key_len[i]; if (len == 0) continue; + if (len == 5 && !(drv_enc & WPA_DRIVER_CAPA_ENC_WEP40)) { + wpa_dbg(wpa_s, MSG_DEBUG, "DEBUG: Your Wireless driver claims not to support WEP, " + "Ignoring that and doing it anyway"); + return 0; + } if (len == 5 && (drv_enc & WPA_DRIVER_CAPA_ENC_WEP40)) continue; if (len == 13 && (drv_enc & WPA_DRIVER_CAPA_ENC_WEP104)) --------------070508070906060507080700-- From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:43:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66DE2F50; Sat, 15 Mar 2014 04:43:10 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 43A84BB1; Sat, 15 Mar 2014 04:43:09 +0000 (UTC) Received: from [192.168.11.100] (unknown [180.42.49.96]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id E2E08192ACD; Sat, 15 Mar 2014 05:08:58 +0000 (UTC) Subject: Re: iwn(4) and WEP From: Sean Bruno To: Adrian Chadd In-Reply-To: References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-cfC5AGKMLFrKqfq+QaMX" Date: Sat, 15 Mar 2014 13:43:01 +0900 Message-ID: <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> 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.17 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: Sat, 15 Mar 2014 04:43:10 -0000 --=-cfC5AGKMLFrKqfq+QaMX Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Fri, 2014-03-14 at 21:31 -0700, Adrian Chadd wrote: > What other drivers are missing this? >=20 >=20 > Adrian >=20 =46rom my quick search, many of the older ones. The list is quicker if we talk about the ones that *do* have it: ath(4) run(4) mwl(4) ndis(4) wi(4) It looks like the capabilities struct defines that the driver/hardware will provide to wpa_supplicant. Using the pre-2.0 wpa_supplicant seems to work with iwn(4) as well. sean >=20 > On Mar 14, 2014 7:52 PM, "Sean Bruno" wrote: > It looks like the wpa_supplicant 2.0 import now checks the > cryptocapability mask when trying to validate WEP usage. > =20 > iwn(4) does not populate the mask with any values so > wpa_supplicant sees > a value of 0. > =20 > I added the capabilites and can associate, but dhclient cannot > get an IP > from the AP. I assume then, that once again, I don't know > what I'm > doing. > =20 > More or less, this is what I tried: > =20 > Index: if_iwn.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- if_iwn.c (revision 263173) > +++ if_iwn.c (working copy) > @@ -564,6 +564,8 @@ > | IEEE80211_C_PMGT /* > Station-side power mgmt */ > ; > =20 > + ic->ic_cryptocaps =3D IEEE80211_CRYPTO_WEP; > + > /* Read MAC address, channels, etc from EEPROM. */ > if ((error =3D iwn_read_eeprom(sc, macaddr)) !=3D 0) { > device_printf(dev, "could not read EEPROM, > error %d\n", > =20 > =20 > sean > =20 > p.s. Allan Jude came up with a hack for wpa_supplicant that > seems to > work, so I've bcc'd him here to get a patch out of him. --=-cfC5AGKMLFrKqfq+QaMX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTI9pRAAoJEBkJRdwI6BaHJM4IAIehOWj0XtZDtrtT3A0s4Hr3 uFFdr7xyEYc5bBgbu7GHaR4eH+S4LUqP7KTXu/7Kya26V+0cxaLFQ1ewzp727wDj ful48NvLa2ZWs+3xhl6ClNadGAzB3jzF/qFnveJKxvWPNJzOQnsnrv6iLJumVn8J MiWpFpOg3rGAP0ts79twthNh2oGiMEsO6yGV/vnGRfU7rUwN9KIt5er7kfOfo6aO +xiq2OjO33fQtQZ9BCmfqsG3l4x+4BrY2djSBOE037OZpQ9+P9H1gm5jvQJedAa7 Hv9dDJB53bM8Ch5XW/T5yFA5IT8IDeG7xloyAJX908UMq0Cx0RLMflKTax2bFs4= =ftmC -----END PGP SIGNATURE----- --=-cfC5AGKMLFrKqfq+QaMX-- From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:44:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CF13FA7; Sat, 15 Mar 2014 04:44:58 +0000 (UTC) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 47727BC1; Sat, 15 Mar 2014 04:44:58 +0000 (UTC) Received: by mail-qg0-f41.google.com with SMTP id i50so10013993qgf.0 for ; Fri, 14 Mar 2014 21:44:56 -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=bKNMIZC3ruiUmcXf+ZEi9Wyc85qnAT6OzvGJoEOY1j0=; b=sOONlL7whaJ8mbPKgqjJAu6jzVt0q5AL+vGSGXZEcH6IR6amXEcKgsDJn7D3v4PbqO LQNNNUqn/S21Ayqc/rLhM1Se9QnmaAFXohPqq6dKxyQKf3cXWCtWk2di4snl6QehrCKO fy4Lh9Cvh4uroNEvZ3DRMa8I9dS2Cpy8STAZ4A1ZU3GTNAW83ADld22AJid0LK/RoU0A SJIsjcVBEHuxLNY9f92UStjWoQPpFMYgoHBMoO2cjj5nRBRJgcdn1izQLGgPCxMamNZ6 M19GwlX9L9wRKmhH8RIlSNVivKKfRvZS9MiLV89hoJJTtkbrpBU7+Uyts9lXGhM8BGKO NcfQ== MIME-Version: 1.0 X-Received: by 10.224.11.10 with SMTP id r10mr8188071qar.8.1394858696458; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) In-Reply-To: <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> Date: Fri, 14 Mar 2014 21:44:56 -0700 X-Google-Sender-Auth: aGwUjeloGDHEv--S5UJTAk2xcD4 Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 04:44:58 -0000 Ok. Please file prs for this. I'm glad you all have debugged this! Adrian On Mar 14, 2014 9:43 PM, "Sean Bruno" wrote: > On Fri, 2014-03-14 at 21:31 -0700, Adrian Chadd wrote: > > What other drivers are missing this? > > > > > > Adrian > > > > From my quick search, many of the older ones. > > The list is quicker if we talk about the ones that *do* have it: > > ath(4) > run(4) > mwl(4) > ndis(4) > wi(4) > > It looks like the capabilities struct defines that the driver/hardware > will provide to wpa_supplicant. > > Using the pre-2.0 wpa_supplicant seems to work with iwn(4) as well. > > sean > > > > > > > > On Mar 14, 2014 7:52 PM, "Sean Bruno" wrote: > > It looks like the wpa_supplicant 2.0 import now checks the > > cryptocapability mask when trying to validate WEP usage. > > > > iwn(4) does not populate the mask with any values so > > wpa_supplicant sees > > a value of 0. > > > > I added the capabilites and can associate, but dhclient cannot > > get an IP > > from the AP. I assume then, that once again, I don't know > > what I'm > > doing. > > > > More or less, this is what I tried: > > > > Index: if_iwn.c > > > =================================================================== > > --- if_iwn.c (revision 263173) > > +++ if_iwn.c (working copy) > > @@ -564,6 +564,8 @@ > > | IEEE80211_C_PMGT /* > > Station-side power mgmt */ > > ; > > > > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; > > + > > /* Read MAC address, channels, etc from EEPROM. */ > > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { > > device_printf(dev, "could not read EEPROM, > > error %d\n", > > > > > > sean > > > > p.s. Allan Jude came up with a hack for wpa_supplicant that > > seems to > > work, so I've bcc'd him here to get a patch out of him. > > From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:46:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9AD4FDE; Sat, 15 Mar 2014 04:46:30 +0000 (UTC) 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 53C86BCB; Sat, 15 Mar 2014 04:46:30 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id j5so3420159qaq.28 for ; Fri, 14 Mar 2014 21:46:29 -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=KGTe+fwNpwAmTEDXFlKVspCcrRDp8jJmhNq4AS/HH58=; b=Cde0+BmlYjhFORDXKxy/OLWn3pv6Q6tcS4xn5O+v97e2tk6gO7/VGLiMzF6ZNZxWeN ilgovipVBL+iYDx+M9x57U7PQbrYZnqxD6vx4ZKuZWZDZuSaLkPokIkmGyb200yAV2Mx FBLdKY+vmusiUdEovp1YbSVr/KzOoRo7VfF+0pPKhp6wvxU2xBiYxl8Ut8iix+mR8ZRh ISY5ziH017B9mFoO3HEs6mhMndkOMUM82K+s9elH+YTJQI3gn7daHS2dqFB3F4/Bb6ev PjOTKNGXC/2BQkpqWce02TJ+IxXAsaGS9WQ8O96OZUh0tjzUBS44hMgABpDrYIJi+/zY 2/Lg== MIME-Version: 1.0 X-Received: by 10.224.56.5 with SMTP id w5mr14336949qag.60.1394858789480; Fri, 14 Mar 2014 21:46:29 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:46:29 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:46:29 -0700 (PDT) In-Reply-To: <5323D9D4.6090204@allanjude.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <5323D9D4.6090204@allanjude.com> Date: Fri, 14 Mar 2014 21:46:29 -0700 Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 04:46:30 -0000 Can you put this up on http or attach as .txt so I can read it in this here phone mail app? Adrian On Mar 14, 2014 9:41 PM, "Allan Jude" wrote: > On 03/14/2014 22:52, Sean Bruno wrote: > > It looks like the wpa_supplicant 2.0 import now checks the > > cryptocapability mask when trying to validate WEP usage. > > > > iwn(4) does not populate the mask with any values so wpa_supplicant sees > > a value of 0. > > > > I added the capabilites and can associate, but dhclient cannot get an IP > > from the AP. I assume then, that once again, I don't know what I'm > > doing. > > > > More or less, this is what I tried: > > > > Index: if_iwn.c > > =================================================================== > > --- if_iwn.c (revision 263173) > > +++ if_iwn.c (working copy) > > @@ -564,6 +564,8 @@ > > | IEEE80211_C_PMGT /* Station-side power mgmt > */ > > ; > > > > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; > > + > > /* Read MAC address, channels, etc from EEPROM. */ > > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { > > device_printf(dev, "could not read EEPROM, error %d\n", > > > > > > sean > > > > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to > > work, so I've bcc'd him here to get a patch out of him. > > Attached is my (horrible) patch that no one should use. But it is > available for those of us at the conference who just need something that > will work for the rest of the weekend. > > > > _______________________________________________ > 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 Sat Mar 15 04:49:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6B18228; Sat, 15 Mar 2014 04:49:41 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7D3F1BD7; Sat, 15 Mar 2014 04:49:40 +0000 (UTC) Received: from [192.168.11.100] (unknown [180.42.49.96]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 8B346192ACD; Sat, 15 Mar 2014 05:15:30 +0000 (UTC) Subject: Re: iwn(4) and WEP From: Sean Bruno To: Adrian Chadd In-Reply-To: References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-9O4H1Kb1Y/k746Ri6S3/" Date: Sat, 15 Mar 2014 13:49:36 +0900 Message-ID: <1394858976.2454.5.camel@powernoodle.corp.yahoo.com> 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.17 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: Sat, 15 Mar 2014 04:49:41 -0000 --=-9O4H1Kb1Y/k746Ri6S3/ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Fri, 2014-03-14 at 21:44 -0700, Adrian Chadd wrote: > Ok. Please file prs for this. >=20 > I'm glad you all have debugged this! >=20 >=20 > Adrian >=20 Well, there's the rub. Allan's patch works, mine will associate, but passes no traffic. :-) sean >=20 > On Mar 14, 2014 9:43 PM, "Sean Bruno" wrote: > On Fri, 2014-03-14 at 21:31 -0700, Adrian Chadd wrote: > > What other drivers are missing this? > > > > > > Adrian > > > =20 > >From my quick search, many of the older ones. > =20 > The list is quicker if we talk about the ones that *do* have > it: > =20 > ath(4) > run(4) > mwl(4) > ndis(4) > wi(4) > =20 > It looks like the capabilities struct defines that the > driver/hardware > will provide to wpa_supplicant. > =20 > Using the pre-2.0 wpa_supplicant seems to work with iwn(4) as > well. > =20 > sean > =20 > =20 > =20 > =20 > > > > On Mar 14, 2014 7:52 PM, "Sean Bruno" > wrote: > > It looks like the wpa_supplicant 2.0 import now > checks the > > cryptocapability mask when trying to validate WEP > usage. > > > > iwn(4) does not populate the mask with any values so > > wpa_supplicant sees > > a value of 0. > > > > I added the capabilites and can associate, but > dhclient cannot > > get an IP > > from the AP. I assume then, that once again, I > don't know > > what I'm > > doing. > > > > More or less, this is what I tried: > > > > Index: if_iwn.c > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > --- if_iwn.c (revision 263173) > > +++ if_iwn.c (working copy) > > @@ -564,6 +564,8 @@ > > | IEEE80211_C_PMGT /* > > Station-side power mgmt */ > > ; > > > > + ic->ic_cryptocaps =3D IEEE80211_CRYPTO_WEP; > > + > > /* Read MAC address, channels, etc from > EEPROM. */ > > if ((error =3D iwn_read_eeprom(sc, macaddr)) ! > =3D 0) { > > device_printf(dev, "could not read > EEPROM, > > error %d\n", > > > > > > sean > > > > p.s. Allan Jude came up with a hack for > wpa_supplicant that > > seems to > > work, so I've bcc'd him here to get a patch out of > him. > =20 --=-9O4H1Kb1Y/k746Ri6S3/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTI9vgAAoJEBkJRdwI6BaH0eQIAI+tC+zLDEzzpYn75Vyxl9HM qg32rvC8HbxsCyi9Rhg2m/Y4R7dcAf9TTdBsmPN/1MybUwWCoefx3zxNtcsQ1Fmw /TdH22uhxsRgQh88JxxZcJEL2eftJtmLjxcKLtZz59X0yorc4sM039y2XnV6DKKT NeyNlh5Xza2p5M21z86ZdooLn1lcuzoVJgk2dSHrtXAp5Y+zrNjoCX6R13g5lJ5H 0SYOmaiqhvCaIZqMYhg8q/75jQUF9pcIIv1RQOdqpagQOEifFLgDunNUnCdMyRPD TqIM1ClXf0sBscYngxpnpomin9lkIBrfODaM1ZjXTaAUozlYJep8oMmkCxOqWM8= =L2Kq -----END PGP SIGNATURE----- --=-9O4H1Kb1Y/k746Ri6S3/-- From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 22:43:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C29BF2A; Sat, 15 Mar 2014 22:43:57 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 431AED81; Sat, 15 Mar 2014 22:43:56 +0000 (UTC) Received: from [172.16.1.106] (s224.GtokyoFL6.vectant.ne.jp [222.228.90.224]) (Authenticated sender: roleaccount@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 65C284913B; Sat, 15 Mar 2014 22:43:49 +0000 (UTC) Message-ID: <532420D4.3020800@allanjude.com> Date: Sat, 15 Mar 2014 18:43:48 +0900 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: iwn(4) and WEP References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <5323D9D4.6090204@allanjude.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 22:43:57 -0000 On 2014-03-15 13:46, Adrian Chadd wrote: > > Can you put this up on http or attach as .txt so I can read it in this > here phone mail app? > > Adrian > > On Mar 14, 2014 9:41 PM, "Allan Jude" > wrote: > > On 03/14/2014 22:52, Sean Bruno wrote: > > It looks like the wpa_supplicant 2.0 import now checks the > > cryptocapability mask when trying to validate WEP usage. > > > > iwn(4) does not populate the mask with any values so > wpa_supplicant sees > > a value of 0. > > > > I added the capabilites and can associate, but dhclient cannot > get an IP > > from the AP. I assume then, that once again, I don't know what I'm > > doing. > > > > More or less, this is what I tried: > > > > Index: if_iwn.c > > =================================================================== > > --- if_iwn.c (revision 263173) > > +++ if_iwn.c (working copy) > > @@ -564,6 +564,8 @@ > > | IEEE80211_C_PMGT /* Station-side > power mgmt */ > > ; > > > > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; > > + > > /* Read MAC address, channels, etc from EEPROM. */ > > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { > > device_printf(dev, "could not read EEPROM, error > %d\n", > > > > > > sean > > > > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to > > work, so I've bcc'd him here to get a patch out of him. > > Attached is my (horrible) patch that no one should use. But it is > available for those of us at the conference who just need > something that > will work for the rest of the weekend. > > > > _______________________________________________ > 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 > " > Here is the web url for my patch (which no one should use): http://www.allanjude.com/bsd/wpa_supplicant.wep.patch Here is the patch rpaulo sent us on IRC: http://people.freebsd.org/~rpaulo/wpa.patch From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 23:18:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C834B7D1; Sat, 15 Mar 2014 23:18:41 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7231DFC6; Sat, 15 Mar 2014 23:18:41 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id e16so4440513qcx.6 for ; Sat, 15 Mar 2014 16:18:40 -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=wdlwu5D89CUkwPiI2QnNFSvtcuarbnp9+LSN6dpoXUY=; b=1A/HvQmHfTAIsUdpzLOeAuhDj/23IJ5GFvUr6q1tZDXqUYpL0xc7MVjzTY8f1h5ks6 f6twHpJ1furS/Iq9bxNq0ZZGvXD9Fvm33wvz6xRvuajhjncZqJ+DPLOa9Md/m6e3SyKt XV8lVxuAhfaqvC1FyF6s9Sk9egtMSIYR+PSuOG2i6DhKkGKkcjTXk31i2euHSiNTrj4J RHtJ79Z/wBvba9iiO41vFUnnWGvHaJ8hTu3IbpqqfwbCqhNlM6lpwUlk/z8Co8NZs3uG SS5caZqNFXvSypWaAXIDGrzmW+hJgnvkEpChMtEPT9/EYCp/zRAVuPuWqTqZXSFRos2S Ac/Q== MIME-Version: 1.0 X-Received: by 10.229.134.198 with SMTP id k6mr18488484qct.13.1394925520590; Sat, 15 Mar 2014 16:18:40 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Sat, 15 Mar 2014 16:18:40 -0700 (PDT) In-Reply-To: <532420D4.3020800@allanjude.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <5323D9D4.6090204@allanjude.com> <532420D4.3020800@allanjude.com> Date: Sat, 15 Mar 2014 16:18:40 -0700 Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 23:18:41 -0000 Please commit the wpa patch! -a On 15 March 2014 02:43, Allan Jude wrote: > On 2014-03-15 13:46, Adrian Chadd wrote: > > Can you put this up on http or attach as .txt so I can read it in this here > phone mail app? > > Adrian > > On Mar 14, 2014 9:41 PM, "Allan Jude" wrote: >> >> On 03/14/2014 22:52, Sean Bruno wrote: >> > It looks like the wpa_supplicant 2.0 import now checks the >> > cryptocapability mask when trying to validate WEP usage. >> > >> > iwn(4) does not populate the mask with any values so wpa_supplicant sees >> > a value of 0. >> > >> > I added the capabilites and can associate, but dhclient cannot get an IP >> > from the AP. I assume then, that once again, I don't know what I'm >> > doing. >> > >> > More or less, this is what I tried: >> > >> > Index: if_iwn.c >> > =================================================================== >> > --- if_iwn.c (revision 263173) >> > +++ if_iwn.c (working copy) >> > @@ -564,6 +564,8 @@ >> > | IEEE80211_C_PMGT /* Station-side power mgmt >> > */ >> > ; >> > >> > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; >> > + >> > /* Read MAC address, channels, etc from EEPROM. */ >> > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { >> > device_printf(dev, "could not read EEPROM, error %d\n", >> > >> > >> > sean >> > >> > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to >> > work, so I've bcc'd him here to get a patch out of him. >> >> Attached is my (horrible) patch that no one should use. But it is >> available for those of us at the conference who just need something that >> will work for the rest of the weekend. >> >> >> >> _______________________________________________ >> 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" > > > Here is the web url for my patch (which no one should use): > http://www.allanjude.com/bsd/wpa_supplicant.wep.patch > > Here is the patch rpaulo sent us on IRC: > http://people.freebsd.org/~rpaulo/wpa.patch > > From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 23:27:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83C64918; Sat, 15 Mar 2014 23:27:05 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 61616118; Sat, 15 Mar 2014 23:27:04 +0000 (UTC) Received: from [10.247.155.101] (191.sub-174-236-72.myvzw.com [174.236.72.191]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id D35E1192ACD; Sat, 15 Mar 2014 23:52:53 +0000 (UTC) Date: Sun, 16 Mar 2014 08:26:59 +0900 Subject: Re: iwn(4) and WEP Message-ID: Importance: normal From: sean bruno To: Adrian Chadd , Allan Jude MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 23:27:05 -0000 V2lsbCBkby4gUnVpIGdlbmVyYXRlZCB0aGlzLCBidXQgaXQgbWF5IGJlIG1hc2tpbmcgc29tZXRo aW5nIGVsc2UuCgpodHRwOi8vcGVvcGxlLmZyZWVic2Qub3JnL35ycGF1bG8vd3BhLnBhdGNoCgot LS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tCkZyb206IEFkcmlhbiBDaGFkZCA8YWRy aWFuLmNoYWRkQGdtYWlsLmNvbT4gCkRhdGU6MDMvMTYvMjAxNCAgODoxOCBBTSAgKEdNVCswOTow MCkgClRvOiBBbGxhbiBKdWRlIDxmcmVlYnNkQGFsbGFuanVkZS5jb20+IApDYzogZnJlZWJzZC13 aXJlbGVzc0BmcmVlYnNkLm9yZyxTZWFuIEJydW5vIDxzYnJ1bm9AZnJlZWJzZC5vcmc+IApTdWJq ZWN0OiBSZTogaXduKDQpIGFuZCBXRVAgCgpQbGVhc2UgY29tbWl0IHRoZSB3cGEgcGF0Y2ghCgoK LWEKCgpPbiAxNSBNYXJjaCAyMDE0IDAyOjQzLCBBbGxhbiBKdWRlIDxmcmVlYnNkQGFsbGFuanVk ZS5jb20+IHdyb3RlOgo+IE9uIDIwMTQtMDMtMTUgMTM6NDYsIEFkcmlhbiBDaGFkZCB3cm90ZToK Pgo+IENhbiB5b3UgcHV0IHRoaXMgdXAgb24gaHR0cCBvciBhdHRhY2ggYXMgLnR4dCBzbyBJIGNh biByZWFkIGl0IGluIHRoaXMgaGVyZQo+IHBob25lIG1haWwgYXBwPwo+Cj4gQWRyaWFuCj4KPiBP biBNYXIgMTQsIDIwMTQgOTo0MSBQTSwgIkFsbGFuIEp1ZGUiIDxmcmVlYnNkQGFsbGFuanVkZS5j b20+IHdyb3RlOgo+Pgo+PiBPbiAwMy8xNC8yMDE0IDIyOjUyLCBTZWFuIEJydW5vIHdyb3RlOgo+ PiA+IEl0IGxvb2tzIGxpa2UgdGhlIHdwYV9zdXBwbGljYW50IDIuMCBpbXBvcnQgbm93IGNoZWNr cyB0aGUKPj4gPiBjcnlwdG9jYXBhYmlsaXR5IG1hc2sgd2hlbiB0cnlpbmcgdG8gdmFsaWRhdGUg V0VQIHVzYWdlLgo+PiA+Cj4+ID4gaXduKDQpIGRvZXMgbm90IHBvcHVsYXRlIHRoZSBtYXNrIHdp dGggYW55IHZhbHVlcyBzbyB3cGFfc3VwcGxpY2FudCBzZWVzCj4+ID4gYSB2YWx1ZSBvZiAwLgo+ PiA+Cj4+ID4gSSBhZGRlZCB0aGUgY2FwYWJpbGl0ZXMgYW5kIGNhbiBhc3NvY2lhdGUsIGJ1dCBk aGNsaWVudCBjYW5ub3QgZ2V0IGFuIElQCj4+ID4gZnJvbSB0aGUgQVAuwqAgSSBhc3N1bWUgdGhl biwgdGhhdCBvbmNlIGFnYWluLCBJIGRvbid0IGtub3cgd2hhdCBJJ20KPj4gPiBkb2luZy4KPj4g Pgo+PiA+IE1vcmUgb3IgbGVzcywgdGhpcyBpcyB3aGF0IEkgdHJpZWQ6Cj4+ID4KPj4gPiBJbmRl eDogaWZfaXduLmMKPj4gPiA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09Cj4+ID4gLS0tIGlmX2l3bi5jwqAgKHJldmlzaW9u IDI2MzE3MykKPj4gPiArKysgaWZfaXduLmPCoCAod29ya2luZyBjb3B5KQo+PiA+IEBAIC01NjQs NiArNTY0LDggQEAKPj4gPsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgfCBJRUVFODAyMTFf Q19QTUdUwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgLyogU3RhdGlvbi1zaWRlIHBvd2VyIG1n bXQKPj4gPiAqLwo+PiA+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA7Cj4+ID4KPj4gPiAr wqDCoMKgwqDCoMKgwqAgaWMtPmljX2NyeXB0b2NhcHMgPSBJRUVFODAyMTFfQ1JZUFRPX1dFUDsK Pj4gPiArCj4+ID7CoMKgwqDCoMKgwqAgLyogUmVhZCBNQUMgYWRkcmVzcywgY2hhbm5lbHMsIGV0 YyBmcm9tIEVFUFJPTS4gKi8KPj4gPsKgwqDCoMKgwqDCoCBpZiAoKGVycm9yID0gaXduX3JlYWRf ZWVwcm9tKHNjLCBtYWNhZGRyKSkgIT0gMCkgewo+PiA+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoCBkZXZpY2VfcHJpbnRmKGRldiwgImNvdWxkIG5vdCByZWFkIEVFUFJPTSwgZXJyb3IgJWRc biIsCj4+ID4KPj4gPgo+PiA+IHNlYW4KPj4gPgo+PiA+IHAucy4gQWxsYW4gSnVkZSBjYW1lIHVw IHdpdGggYSBoYWNrIGZvciB3cGFfc3VwcGxpY2FudCB0aGF0IHNlZW1zIHRvCj4+ID4gd29yaywg c28gSSd2ZSBiY2MnZCBoaW0gaGVyZSB0byBnZXQgYSBwYXRjaCBvdXQgb2YgaGltLgo+Pgo+PiBB dHRhY2hlZCBpcyBteSAoaG9ycmlibGUpIHBhdGNoIHRoYXQgbm8gb25lIHNob3VsZCB1c2UuIEJ1 dCBpdCBpcwo+PiBhdmFpbGFibGUgZm9yIHRob3NlIG9mIHVzIGF0IHRoZSBjb25mZXJlbmNlIHdo byBqdXN0IG5lZWQgc29tZXRoaW5nIHRoYXQKPj4gd2lsbCB3b3JrIGZvciB0aGUgcmVzdCBvZiB0 aGUgd2Vla2VuZC4KPj4KPj4KPj4KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18KPj4gZnJlZWJzZC13aXJlbGVzc0BmcmVlYnNkLm9yZyBtYWlsaW5nIGxp c3QKPj4gaHR0cDovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC13 aXJlbGVzcwo+PiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0bwo+PiAiZnJlZWJzZC13 aXJlbGVzcy11bnN1YnNjcmliZUBmcmVlYnNkLm9yZyIKPgo+Cj4gSGVyZSBpcyB0aGUgd2ViIHVy bCBmb3IgbXkgcGF0Y2ggKHdoaWNoIG5vIG9uZSBzaG91bGQgdXNlKToKPiBodHRwOi8vd3d3LmFs bGFuanVkZS5jb20vYnNkL3dwYV9zdXBwbGljYW50LndlcC5wYXRjaAo+Cj4gSGVyZSBpcyB0aGUg cGF0Y2ggcnBhdWxvIHNlbnQgdXMgb24gSVJDOgo+IGh0dHA6Ly9wZW9wbGUuZnJlZWJzZC5vcmcv fnJwYXVsby93cGEucGF0Y2gKPgo+Cg== From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 23:31:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3B6C2951; Sat, 15 Mar 2014 23:31:37 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C86BC19F; Sat, 15 Mar 2014 23:31:36 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id a108so12162959qge.3 for ; Sat, 15 Mar 2014 16:31:36 -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=rYy3ypZdxP6j6iMdx+nQctgZX9WWoz/710lEMuHTXFI=; b=FVbvtk8oIcz5cHt/GudGkBuCQ/HP0BqqsuJU2j0k6Alh02n4Rj198bt4r6UJ60tC+F ob/RoiAhGgYqEwbOyn7I+PSDFoGrggJGd4t0YuDyoK3nC9987zuIlfinJ+50t8tMzzWt Hr9PeHovDvGOkOM9U7upsgzBssXNmz3J+LbfC/b4qFIt+iFGYoYSSN94edil9dCGDGPT qMYkdYizMZFDrGGatjskqMcrPda/O7ugkZDQOFi+Pr8C7BD4rKYkbNa2mx1WfSXaRWLk VkN1GQTXDMLgh25UN6IQpFcjuW5ovcyP5hSnIpNlU0jVsKNc8DuwEGK2CexPTDL+37gm zuFw== MIME-Version: 1.0 X-Received: by 10.224.93.10 with SMTP id t10mr88488qam.82.1394926295963; Sat, 15 Mar 2014 16:31:35 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Sat, 15 Mar 2014 16:31:35 -0700 (PDT) In-Reply-To: References: Date: Sat, 15 Mar 2014 16:31:35 -0700 Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: sean bruno Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , Allan Jude X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 23:31:37 -0000 Hm, from my understanding, the problem is this: * a bunch of drivers don't advertise that they do crypto stuff natively; * net80211 however supports software encryption for other things; * and what we're doing is somehow passing those caps all the way down to the supplicant; * .. that believes that it's not supported. Now, I _think_ that maybe we should be teaching net80211 to fill in the capabilities for what it supports before kicking them up to the supplicant layer, since it knows if there's hardware or softwrae support for things. So, ok. i'll talk with jouni/rui and see if we can come up with a better fix. Thanks! -a On 15 March 2014 16:26, sean bruno wrote: > Will do. Rui generated this, but it may be masking something else. > > http://people.freebsd.org/~rpaulo/wpa.patch > > > -------- Original message -------- > From: Adrian Chadd > Date:03/16/2014 8:18 AM (GMT+09:00) > To: Allan Jude > Cc: freebsd-wireless@freebsd.org,Sean Bruno > Subject: Re: iwn(4) and WEP > > Please commit the wpa patch! > > > -a > > > On 15 March 2014 02:43, Allan Jude wrote: >> On 2014-03-15 13:46, Adrian Chadd wrote: >> >> Can you put this up on http or attach as .txt so I can read it in this >> here >> phone mail app? >> >> Adrian >> >> On Mar 14, 2014 9:41 PM, "Allan Jude" wrote: >>> >>> On 03/14/2014 22:52, Sean Bruno wrote: >>> > It looks like the wpa_supplicant 2.0 import now checks the >>> > cryptocapability mask when trying to validate WEP usage. >>> > >>> > iwn(4) does not populate the mask with any values so wpa_supplicant >>> > sees >>> > a value of 0. >>> > >>> > I added the capabilites and can associate, but dhclient cannot get an >>> > IP >>> > from the AP. I assume then, that once again, I don't know what I'm >>> > doing. >>> > >>> > More or less, this is what I tried: >>> > >>> > Index: if_iwn.c >>> > =================================================================== >>> > --- if_iwn.c (revision 263173) >>> > +++ if_iwn.c (working copy) >>> > @@ -564,6 +564,8 @@ >>> > | IEEE80211_C_PMGT /* Station-side power >>> > mgmt >>> > */ >>> > ; >>> > >>> > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; >>> > + >>> > /* Read MAC address, channels, etc from EEPROM. */ >>> > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { >>> > device_printf(dev, "could not read EEPROM, error %d\n", >>> > >>> > >>> > sean >>> > >>> > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to >>> > work, so I've bcc'd him here to get a patch out of him. >>> >>> Attached is my (horrible) patch that no one should use. But it is >>> available for those of us at the conference who just need something that >>> will work for the rest of the weekend. >>> >>> >>> >>> _______________________________________________ >>> 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" >> >> >> Here is the web url for my patch (which no one should use): >> http://www.allanjude.com/bsd/wpa_supplicant.wep.patch >> >> Here is the patch rpaulo sent us on IRC: >> http://people.freebsd.org/~rpaulo/wpa.patch >> >> From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 23:31:45 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BBF80968; Sat, 15 Mar 2014 23:31:45 +0000 (UTC) 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 53B2C1A1; Sat, 15 Mar 2014 23:31:45 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id x13so4420619qcv.5 for ; Sat, 15 Mar 2014 16:31:44 -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=2P8LPp0Z8Luy6lDYYVSpOczt/e+mmxCSxbKoGkaix5I=; b=Dcadoq29xIF2lGMCuoeJ5QzIxNMI2uLNKC/h1h1rkcfgQHYx9VmvFfrBw6qXAgm6zB FzzVZx4w9aqE/PiDPbJDPsMMJPgCu3+aJF0YJQogDcHk5ToyFpURz2lfhhvnBQJAUmUX sX5vspFLOZFy/DnNiAWUXKnRIohcxWVJo0QHemHYtsLJi80rupHJm143BijwSBfHOyvS wffhFQDPciiznRW6IDgdGeZqCeRp1s/3iKOKt3NfJPb/Lq9reS6121UHtER1SJLHbq+m PU6GjJqRiUcvweErdfDV3QVID8KPwTv+aZHylXnh9Ms5mUwKvWmWRYoHQPMNALK6ox2b jIVw== MIME-Version: 1.0 X-Received: by 10.229.89.65 with SMTP id d1mr19139193qcm.14.1394926304491; Sat, 15 Mar 2014 16:31:44 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Sat, 15 Mar 2014 16:31:44 -0700 (PDT) In-Reply-To: References: Date: Sat, 15 Mar 2014 16:31:44 -0700 Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: sean bruno Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , Allan Jude X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 23:31:45 -0000 ... and can someone please file a bloody PR? :) -a On 15 March 2014 16:31, Adrian Chadd wrote: > Hm, from my understanding, the problem is this: > > * a bunch of drivers don't advertise that they do crypto stuff natively; > * net80211 however supports software encryption for other things; > * and what we're doing is somehow passing those caps all the way down > to the supplicant; > * .. that believes that it's not supported. > > Now, I _think_ that maybe we should be teaching net80211 to fill in > the capabilities for what it supports before kicking them up to the > supplicant layer, since it knows if there's hardware or softwrae > support for things. > > So, ok. i'll talk with jouni/rui and see if we can come up with a better fix. > > Thanks! > > > -a > > > On 15 March 2014 16:26, sean bruno wrote: >> Will do. Rui generated this, but it may be masking something else. >> >> http://people.freebsd.org/~rpaulo/wpa.patch >> >> >> -------- Original message -------- >> From: Adrian Chadd >> Date:03/16/2014 8:18 AM (GMT+09:00) >> To: Allan Jude >> Cc: freebsd-wireless@freebsd.org,Sean Bruno >> Subject: Re: iwn(4) and WEP >> >> Please commit the wpa patch! >> >> >> -a >> >> >> On 15 March 2014 02:43, Allan Jude wrote: >>> On 2014-03-15 13:46, Adrian Chadd wrote: >>> >>> Can you put this up on http or attach as .txt so I can read it in this >>> here >>> phone mail app? >>> >>> Adrian >>> >>> On Mar 14, 2014 9:41 PM, "Allan Jude" wrote: >>>> >>>> On 03/14/2014 22:52, Sean Bruno wrote: >>>> > It looks like the wpa_supplicant 2.0 import now checks the >>>> > cryptocapability mask when trying to validate WEP usage. >>>> > >>>> > iwn(4) does not populate the mask with any values so wpa_supplicant >>>> > sees >>>> > a value of 0. >>>> > >>>> > I added the capabilites and can associate, but dhclient cannot get an >>>> > IP >>>> > from the AP. I assume then, that once again, I don't know what I'm >>>> > doing. >>>> > >>>> > More or less, this is what I tried: >>>> > >>>> > Index: if_iwn.c >>>> > =================================================================== >>>> > --- if_iwn.c (revision 263173) >>>> > +++ if_iwn.c (working copy) >>>> > @@ -564,6 +564,8 @@ >>>> > | IEEE80211_C_PMGT /* Station-side power >>>> > mgmt >>>> > */ >>>> > ; >>>> > >>>> > + ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP; >>>> > + >>>> > /* Read MAC address, channels, etc from EEPROM. */ >>>> > if ((error = iwn_read_eeprom(sc, macaddr)) != 0) { >>>> > device_printf(dev, "could not read EEPROM, error %d\n", >>>> > >>>> > >>>> > sean >>>> > >>>> > p.s. Allan Jude came up with a hack for wpa_supplicant that seems to >>>> > work, so I've bcc'd him here to get a patch out of him. >>>> >>>> Attached is my (horrible) patch that no one should use. But it is >>>> available for those of us at the conference who just need something that >>>> will work for the rest of the weekend. >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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" >>> >>> >>> Here is the web url for my patch (which no one should use): >>> http://www.allanjude.com/bsd/wpa_supplicant.wep.patch >>> >>> Here is the patch rpaulo sent us on IRC: >>> http://people.freebsd.org/~rpaulo/wpa.patch >>> >>> From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 23:34:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87CBA996; Sat, 15 Mar 2014 23:34:43 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 652351AD; Sat, 15 Mar 2014 23:34:43 +0000 (UTC) Received: from [10.247.155.101] (191.sub-174-236-72.myvzw.com [174.236.72.191]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id D9F0D192ACD; Sun, 16 Mar 2014 00:00:31 +0000 (UTC) Date: Sun, 16 Mar 2014 08:34:37 +0900 Subject: Re: iwn(4) and WEP Message-ID: Importance: normal From: sean bruno To: Adrian Chadd MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-wireless@freebsd.org" , Allan Jude X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Mar 2014 23:34:43 -0000 SSB3b3VsZCAsIGlmIGl0IHdvcmtlZCBmcm9tIG15IGNlbGwgcGhvbmUuIFlvdSBrbm93LCBsaWtl IGJ1Z3ppbGxhIG9yIHNvbWV0aGluZyBjcmF6eSBsaWtlIHRoYXQuIDxUUk9MTD4KCklsbCBoZWFk IG92ZXIgdG8gdGhlIGNvbmZlcmVuY2UgaW4gYSBiaXQgYW5kIGZpbGUub25lLgoKLS0tLS0tLS0g T3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLQpGcm9tOiBBZHJpYW4gQ2hhZGQgPGFkcmlhbi5jaGFk ZEBnbWFpbC5jb20+IApEYXRlOjAzLzE2LzIwMTQgIDg6MzEgQU0gIChHTVQrMDk6MDApIApUbzog c2VhbiBicnVubyA8c2JydW5vQGlnbm9yYW50aGFjay5tZT4gCkNjOiBBbGxhbiBKdWRlIDxmcmVl YnNkQGFsbGFuanVkZS5jb20+LGZyZWVic2Qtd2lyZWxlc3NAZnJlZWJzZC5vcmcsU2VhbiBCcnVu byA8c2JydW5vQGZyZWVic2Qub3JnPixSdWkgUGF1bG8gPHJwYXVsb0BmcmVlYnNkLm9yZz4gClN1 YmplY3Q6IFJlOiBpd24oNCkgYW5kIFdFUCAKCi4uLiBhbmQgY2FuIHNvbWVvbmUgcGxlYXNlIGZp bGUgYSBibG9vZHkgUFI/IDopCgoKLWEKCgpPbiAxNSBNYXJjaCAyMDE0IDE2OjMxLCBBZHJpYW4g Q2hhZGQgPGFkcmlhbi5jaGFkZEBnbWFpbC5jb20+IHdyb3RlOgo+IEhtLCBmcm9tIG15IHVuZGVy c3RhbmRpbmcsIHRoZSBwcm9ibGVtIGlzIHRoaXM6Cj4KPiAqIGEgYnVuY2ggb2YgZHJpdmVycyBk b24ndCBhZHZlcnRpc2UgdGhhdCB0aGV5IGRvIGNyeXB0byBzdHVmZiBuYXRpdmVseTsKPiAqIG5l dDgwMjExIGhvd2V2ZXIgc3VwcG9ydHMgc29mdHdhcmUgZW5jcnlwdGlvbiBmb3Igb3RoZXIgdGhp bmdzOwo+ICogYW5kIHdoYXQgd2UncmUgZG9pbmcgaXMgc29tZWhvdyBwYXNzaW5nIHRob3NlIGNh cHMgYWxsIHRoZSB3YXkgZG93bgo+IHRvIHRoZSBzdXBwbGljYW50Owo+ICogLi4gdGhhdCBiZWxp ZXZlcyB0aGF0IGl0J3Mgbm90IHN1cHBvcnRlZC4KPgo+IE5vdywgSSBfdGhpbmtfIHRoYXQgbWF5 YmUgd2Ugc2hvdWxkIGJlIHRlYWNoaW5nIG5ldDgwMjExIHRvIGZpbGwgaW4KPiB0aGUgY2FwYWJp bGl0aWVzIGZvciB3aGF0IGl0IHN1cHBvcnRzIGJlZm9yZSBraWNraW5nIHRoZW0gdXAgdG8gdGhl Cj4gc3VwcGxpY2FudCBsYXllciwgc2luY2UgaXQga25vd3MgaWYgdGhlcmUncyBoYXJkd2FyZSBv ciBzb2Z0d3JhZQo+IHN1cHBvcnQgZm9yIHRoaW5ncy4KPgo+IFNvLCBvay4gaSdsbCB0YWxrIHdp dGggam91bmkvcnVpIGFuZCBzZWUgaWYgd2UgY2FuIGNvbWUgdXAgd2l0aCBhIGJldHRlciBmaXgu Cj4KPiBUaGFua3MhCj4KPgo+IC1hCj4KPgo+IE9uIDE1IE1hcmNoIDIwMTQgMTY6MjYsIHNlYW4g YnJ1bm8gPHNicnVub0BpZ25vcmFudGhhY2subWU+IHdyb3RlOgo+PiBXaWxsIGRvLiBSdWkgZ2Vu ZXJhdGVkIHRoaXMsIGJ1dCBpdCBtYXkgYmUgbWFza2luZyBzb21ldGhpbmcgZWxzZS4KPj4KPj4g aHR0cDovL3Blb3BsZS5mcmVlYnNkLm9yZy9+cnBhdWxvL3dwYS5wYXRjaAo+Pgo+Pgo+PiAtLS0t LS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tCj4+IEZyb206IEFkcmlhbiBDaGFkZAo+PiBE YXRlOjAzLzE2LzIwMTQgODoxOCBBTSAoR01UKzA5OjAwKQo+PiBUbzogQWxsYW4gSnVkZQo+PiBD YzogZnJlZWJzZC13aXJlbGVzc0BmcmVlYnNkLm9yZyxTZWFuIEJydW5vCj4+IFN1YmplY3Q6IFJl OiBpd24oNCkgYW5kIFdFUAo+Pgo+PiBQbGVhc2UgY29tbWl0IHRoZSB3cGEgcGF0Y2ghCj4+Cj4+ Cj4+IC1hCj4+Cj4+Cj4+IE9uIDE1IE1hcmNoIDIwMTQgMDI6NDMsIEFsbGFuIEp1ZGUgPGZyZWVi c2RAYWxsYW5qdWRlLmNvbT4gd3JvdGU6Cj4+PiBPbiAyMDE0LTAzLTE1IDEzOjQ2LCBBZHJpYW4g Q2hhZGQgd3JvdGU6Cj4+Pgo+Pj4gQ2FuIHlvdSBwdXQgdGhpcyB1cCBvbiBodHRwIG9yIGF0dGFj aCBhcyAudHh0IHNvIEkgY2FuIHJlYWQgaXQgaW4gdGhpcwo+Pj4gaGVyZQo+Pj4gcGhvbmUgbWFp bCBhcHA/Cj4+Pgo+Pj4gQWRyaWFuCj4+Pgo+Pj4gT24gTWFyIDE0LCAyMDE0IDk6NDEgUE0sICJB bGxhbiBKdWRlIiA8ZnJlZWJzZEBhbGxhbmp1ZGUuY29tPiB3cm90ZToKPj4+Pgo+Pj4+IE9uIDAz LzE0LzIwMTQgMjI6NTIsIFNlYW4gQnJ1bm8gd3JvdGU6Cj4+Pj4gPiBJdCBsb29rcyBsaWtlIHRo ZSB3cGFfc3VwcGxpY2FudCAyLjAgaW1wb3J0IG5vdyBjaGVja3MgdGhlCj4+Pj4gPiBjcnlwdG9j YXBhYmlsaXR5IG1hc2sgd2hlbiB0cnlpbmcgdG8gdmFsaWRhdGUgV0VQIHVzYWdlLgo+Pj4+ID4K Pj4+PiA+IGl3big0KSBkb2VzIG5vdCBwb3B1bGF0ZSB0aGUgbWFzayB3aXRoIGFueSB2YWx1ZXMg c28gd3BhX3N1cHBsaWNhbnQKPj4+PiA+IHNlZXMKPj4+PiA+IGEgdmFsdWUgb2YgMC4KPj4+PiA+ Cj4+Pj4gPiBJIGFkZGVkIHRoZSBjYXBhYmlsaXRlcyBhbmQgY2FuIGFzc29jaWF0ZSwgYnV0IGRo Y2xpZW50IGNhbm5vdCBnZXQgYW4KPj4+PiA+IElQCj4+Pj4gPiBmcm9tIHRoZSBBUC7CoCBJIGFz c3VtZSB0aGVuLCB0aGF0IG9uY2UgYWdhaW4sIEkgZG9uJ3Qga25vdyB3aGF0IEknbQo+Pj4+ID4g ZG9pbmcuCj4+Pj4gPgo+Pj4+ID4gTW9yZSBvciBsZXNzLCB0aGlzIGlzIHdoYXQgSSB0cmllZDoK Pj4+PiA+Cj4+Pj4gPiBJbmRleDogaWZfaXduLmMKPj4+PiA+ID09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KPj4+PiA+IC0t LSBpZl9pd24uY8KgIChyZXZpc2lvbiAyNjMxNzMpCj4+Pj4gPiArKysgaWZfaXduLmPCoCAod29y a2luZyBjb3B5KQo+Pj4+ID4gQEAgLTU2NCw2ICs1NjQsOCBAQAo+Pj4+ID7CoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgIHwgSUVFRTgwMjExX0NfUE1HVMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgIC8qIFN0YXRpb24tc2lkZSBwb3dlcgo+Pj4+ID4gbWdtdAo+Pj4+ID4gKi8KPj4+PiA+wqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA7Cj4+Pj4gPgo+Pj4+ID4gK8KgwqDCoMKgwqDCoMKg IGljLT5pY19jcnlwdG9jYXBzID0gSUVFRTgwMjExX0NSWVBUT19XRVA7Cj4+Pj4gPiArCj4+Pj4g PsKgwqDCoMKgwqDCoCAvKiBSZWFkIE1BQyBhZGRyZXNzLCBjaGFubmVscywgZXRjIGZyb20gRUVQ Uk9NLiAqLwo+Pj4+ID7CoMKgwqDCoMKgwqAgaWYgKChlcnJvciA9IGl3bl9yZWFkX2VlcHJvbShz YywgbWFjYWRkcikpICE9IDApIHsKPj4+PiA+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBk ZXZpY2VfcHJpbnRmKGRldiwgImNvdWxkIG5vdCByZWFkIEVFUFJPTSwgZXJyb3IgJWRcbiIsCj4+ Pj4gPgo+Pj4+ID4KPj4+PiA+IHNlYW4KPj4+PiA+Cj4+Pj4gPiBwLnMuIEFsbGFuIEp1ZGUgY2Ft ZSB1cCB3aXRoIGEgaGFjayBmb3Igd3BhX3N1cHBsaWNhbnQgdGhhdCBzZWVtcyB0bwo+Pj4+ID4g d29yaywgc28gSSd2ZSBiY2MnZCBoaW0gaGVyZSB0byBnZXQgYSBwYXRjaCBvdXQgb2YgaGltLgo+ Pj4+Cj4+Pj4gQXR0YWNoZWQgaXMgbXkgKGhvcnJpYmxlKSBwYXRjaCB0aGF0IG5vIG9uZSBzaG91 bGQgdXNlLiBCdXQgaXQgaXMKPj4+PiBhdmFpbGFibGUgZm9yIHRob3NlIG9mIHVzIGF0IHRoZSBj b25mZXJlbmNlIHdobyBqdXN0IG5lZWQgc29tZXRoaW5nIHRoYXQKPj4+PiB3aWxsIHdvcmsgZm9y IHRoZSByZXN0IG9mIHRoZSB3ZWVrZW5kLgo+Pj4+Cj4+Pj4KPj4+Pgo+Pj4+IF9fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4+Pj4gZnJlZWJzZC13aXJlbGVz c0BmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QKPj4+PiBodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcv bWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXdpcmVsZXNzCj4+Pj4gVG8gdW5zdWJzY3JpYmUsIHNl bmQgYW55IG1haWwgdG8KPj4+PiAiZnJlZWJzZC13aXJlbGVzcy11bnN1YnNjcmliZUBmcmVlYnNk Lm9yZyIKPj4+Cj4+Pgo+Pj4gSGVyZSBpcyB0aGUgd2ViIHVybCBmb3IgbXkgcGF0Y2ggKHdoaWNo IG5vIG9uZSBzaG91bGQgdXNlKToKPj4+IGh0dHA6Ly93d3cuYWxsYW5qdWRlLmNvbS9ic2Qvd3Bh X3N1cHBsaWNhbnQud2VwLnBhdGNoCj4+Pgo+Pj4gSGVyZSBpcyB0aGUgcGF0Y2ggcnBhdWxvIHNl bnQgdXMgb24gSVJDOgo+Pj4gaHR0cDovL3Blb3BsZS5mcmVlYnNkLm9yZy9+cnBhdWxvL3dwYS5w YXRjaAo+Pj4KPj4+Cg== From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 17 11:06:56 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43E92BC9 for ; Mon, 17 Mar 2014 11:06:56 +0000 (UTC) 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 15D2E2B1 for ; Mon, 17 Mar 2014 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2HB6tac011458 for ; Mon, 17 Mar 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2HB6tcD011456 for freebsd-wireless@FreeBSD.org; Mon, 17 Mar 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Mar 2014 11:06:55 GMT Message-Id: <201403171106.s2HB6tcD011456@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.17 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, 17 Mar 2014 11:06:56 -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/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 192 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 18 01:47:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22B3CCB0 for ; Tue, 18 Mar 2014 01:47:00 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D5D767D9 for ; Tue, 18 Mar 2014 01:46:59 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id e9so7153762qcy.1 for ; Mon, 17 Mar 2014 18:46:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ax8X1nPi1UWccScJTretUhfqftvaIs/zoYv2qWAQ2JM=; b=JVuqSSwxjcqgplo3FUwFqjOuXzAlp9afa/zh3xl4mJaJUbmz4CnJ1FyeSfGqZDEFTW 8Wl21ok59qfMKArrH/FEgvEL5D7babD/6l61HvM0Ki6i3FOAuBUefD2/0UqDnQtRnjZR Imu9cQ+RRHuiJQaLJ6rHtMT9+Ui0z+t13dDZzzAQnNUsLsOWc1L8mHHdwoySwyq6+SyL fwNj4T6dUeSgg2w7/rwq2Kr3rRG3b4xRyfznNyNQaZ0aZDjvHWLnQm/qqjza0C377p+X wMbJhcq50a1VTC2asJfS2kmgIpdJHU2uiRjhCGmiJUfe6L7kTQNb2Svw2bMWpyggAN4C 6eSQ== MIME-Version: 1.0 X-Received: by 10.140.40.5 with SMTP id w5mr30186947qgw.65.1395107219050; Mon, 17 Mar 2014 18:46:59 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Mon, 17 Mar 2014 18:46:58 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> <20140315010640.GB65392@ns.umpquanet.com> Date: Mon, 17 Mar 2014 18:46:58 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 18 Mar 2014 01:47:00 -0000 Yup, I found a 2100 and 2200. And yes it does dump out a bunch of statistics stuff when the NIC is running. I'll see about exposing the statistics messages via some API soon. -a On 14 March 2014 18:55, Adrian Chadd wrote: > Nope; there's no code for handling the messages yet. > > I'll dig around to see if I can find a 2200 series NIC in a laptop > here or in my collection. I know I have 3945 NICs, but not the 2200.. > > -a > > > On 14 March 2014 18:06, Jim Long wrote: >> Thank you for your reply. >> >> This would be via syslog in /var/log/messages? Nothing that I see: >> >> $ zgrep -il notification /var/log/messages* >> $ >> >> >> >> On Fri, Mar 14, 2014 at 05:50:12PM -0700, Adrian Chadd wrote: >>> It'd be stuff like this: >>> >>> case IWI_NOTIF_TYPE_CALIBRATION: >>> case IWI_NOTIF_TYPE_NOISE: >>> case IWI_NOTIF_TYPE_LINK_QUALITY: >>> DPRINTFN(5, ("Notification (%u)\n", notif->type)); >>> break; >>> >>> >>> >>> -a >>> >>> >>> On 14 March 2014 17:18, Adrian Chadd wrote: >>> > Hi, >>> > >>> > I'm not sure what kind of statistics or diagnostics iwi spits out. >>> > It's likely worth reviewing the linux and freebsd drivers to see if it >>> > does spit out any kind of statistics messages. That's a good starting >>> > point. >>> > >>> > Thanks! >>> > >>> > >>> > -a >>> > >>> > >>> > On 14 March 2014 16:00, Jim Long wrote: >>> >> I have a long-standing problem that involves the iwi interface on >>> >> my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. >>> >> >>> >> Some wifi connections I make show good signal strength, but poor >>> >> latency and/or packet loss to the WAP IP. I can't find other >>> >> wifi users who perceive the wifi performance as poor, so I am >>> >> assuming the problem is local to me. >>> >> >>> >> I will say this is generally repeatable by location: good >>> >> locations are usually good, bad locations are usually bad. My >>> >> theory is that the 2200BG likes some WAPs that I use more than it >>> >> likes others. I'd like to find out what I can do to either fix >>> >> the problem, or at least be able to accurately tell the WAP owner >>> >> what their problem is. >>> >> >>> >> I'm ignorant about how to troubleshoot problems like this, so >>> >> please suggest some diagnostic information I can provide to guide >>> >> either of us toward a solution. >>> >> >>> >> Thank you, >>> >> >>> >> Jim >>> >> >>> >> from dmesg: >>> >> >>> >> iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 >>> >> wlan0: Ethernet address: 00:12:f0:ca:5c:85 >>> >> >>> >> I get this a lot, but don't know if it's relevant. It seems >>> >> to appear during both good and bad connections: >>> >> >>> >> iwi0: need multicast update callback >>> >> >>> >> >>> >> Here's 61db of S/N ratio, resulting in almost 50% packet loss: >>> >> >>> >> $ wlanstats ; ping -c20 wap2 >>> >> 36 rx frame too short >>> >> 5 rx from wrong bssid >>> >> 374 rx discard 'cuz dup >>> >> 5 rx discard 'cuz mcast echo >>> >> 3 rx discard mgt frames >>> >> 1347 rx beacon frames >>> >> 4151 rx element unknown >>> >> 42 rx frame chan mismatch >>> >> 7 rx disassociation >>> >> 7 beacon miss events handled >>> >> 6 active scans started >>> >> 1446 rx management frames >>> >> 2 tx failed 'cuz vap not in RUN state >>> >> 28752 total data frames received >>> >> 8679 unicast data frames received >>> >> 20073 multicast data frames received >>> >> 12186 total data frames transmit >>> >> 12186 unicast data frames sent >>> >> 54M current transmit rate >>> >> 61 current rssi >>> >> -95 current noise floor (dBm) >>> >> -34 current signal (dBm) >>> >> PING wap2 (192.168.2.1): 56 data bytes >>> >> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms >>> >> 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms >>> >> >>> >> --- wap2 ping statistics --- >>> >> 20 packets transmitted, 11 packets received, 45.0% packet loss >>> >> round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms >>> >> >>> >> To my knowledge the OS is using the latest 3.1 firmware for the >>> >> interface: >>> >> >>> >> $ cd /usr/src/sys/contrib/dev/iwi >>> >> $ grep ^FW Makefile; md5 * >>> >> FW_VERSION=3.1 >>> >> MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a >>> >> MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 >>> >> MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b >>> >> MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 >>> >> MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 >>> >> >>> >> _______________________________________________ >>> >> 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 Mar 20 19:41:29 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89AD3E39; Thu, 20 Mar 2014 19:41:29 +0000 (UTC) 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 5E6798F9; Thu, 20 Mar 2014 19:41:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2KJfTfv090479; Thu, 20 Mar 2014 19:41:29 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2KJfTRJ090478; Thu, 20 Mar 2014 19:41:29 GMT (envelope-from adrian) Date: Thu, 20 Mar 2014 19:41:29 GMT Message-Id: <201403201941.s2KJfTRJ090478@freefall.freebsd.org> To: adrian@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Subject: Re: kern/187624: WEP and other ciphers do not work if h/w driver does not declare support X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 20 Mar 2014 19:41:29 -0000 Synopsis: WEP and other ciphers do not work if h/w driver does not declare support Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Thu Mar 20 19:41:22 UTC 2014 Responsible-Changed-Why: bounce to owne.r http://www.freebsd.org/cgi/query-pr.cgi?pr=187624 From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 24 11:06:55 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 51A482C1 for ; Mon, 24 Mar 2014 11:06:55 +0000 (UTC) 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 2311718F for ; Mon, 24 Mar 2014 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2OB6sw1014044 for ; Mon, 24 Mar 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2OB6sCl014042 for freebsd-wireless@FreeBSD.org; Mon, 24 Mar 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Mar 2014 11:06:54 GMT Message-Id: <201403241106.s2OB6sCl014042@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.17 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, 24 Mar 2014 11:06:55 -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/187624 wireless WEP and other ciphers do not work if h/w driver does n o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 193 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed Mar 26 14:48:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C097A05 for ; Wed, 26 Mar 2014 14:48:43 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F6FE8E9 for ; Wed, 26 Mar 2014 14:48:43 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id r5so2616539qcx.4 for ; Wed, 26 Mar 2014 07:48:42 -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=zc3qj9KUTD5t4k7CXlMpc6HAzV62Nxo9cDUrVrR9n7A=; b=Md5ACj3ezySUMBIhtHOAm9nwnlcE2N98zytxiGbCs+MBBjNaqP/NX3odW9z9kHdmRy IHouzjOxmwHXEj/9YbXl8qBpQxEt+gazzTZer881j/zCIoQHYeLoXQ5LPlXH0j02v8Ly ETq+i8qLwM99LpEvJQgWf0I8dogeYMBzsPNuKicTDyPUgyOFtu2JNmfajGD9DxzeZXY3 K9EhIa+4XJm1IJUjWxNvJ29S4ewiVNh1QmEnNZJMommWLR2xIxrjgl1is9jzVgtH25kG kyiyAZ5Hlok+Dg1s7gadRC6qB3m8qhMf8oJS5YOv4KqAQkFbi3w14Uun333m1OalA0Je xwZg== MIME-Version: 1.0 X-Received: by 10.224.151.82 with SMTP id b18mr2737567qaw.98.1395845322533; Wed, 26 Mar 2014 07:48:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.125.1 with HTTP; Wed, 26 Mar 2014 07:48:42 -0700 (PDT) Date: Wed, 26 Mar 2014 07:48:42 -0700 X-Google-Sender-Auth: ByBBHnYfovy4mc_SLLyDR0w2bEM Message-ID: Subject: [ath] debugging (another) 11n TX hang.. From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 26 Mar 2014 14:48:43 -0000 Hi, This is mostly a "I should really document this for others to follow" post. Hiren and I are seeing situations where ath(4) in hostap mode will hang. It'll hang, but only to one station (ie, the NIC and driver isn't TX hung; it's something busted in the software queue handling.) Rui changed the debugging so you don't get packet printing unless the netif "debug" flag is enabled and silenced the flood of packet printf's that go on when a client disassociates with frames in the software queue. I erm, put that debugging back, under ATH_DEBUG_RESET (sysctl dev.ath.X.debug=0x20). So, with that in mind, I turned it on, started some traffic, and waited for it to hang. What I saw was. Annoying. The log is on another laptop; I'll post it here. But the summarised output is: ath1: ath_tx_tid_drain_print: norm: : ... seqno=3764, retry=0 ath1: ath_tx_tid_drain_print: norm: : txq[1] axq_depth=0 axq_aggr_depth=0 ath1: ath_tx_tid_drain_print: norm: : tid txq_depth=129 hwq_depth=0 bar_wait=0 isfiltered=0 ath1: ath_tx_tid_drain_print: norm: : tid 0: sched=1, paused=0, incomp=0, baw_head=125, baw_tail=61, txa_start=3700, ni_txseqs=3893 There's 128 more of them, for each of the packets in the software queue. Now, the basics: * seqno = assigned sequence number for this frame * txq[1] = this TID maps to the hardware txq[1] * the axq_depth / axq_aggr_depth shows that no hardware frames are queued to the device. One thing that used to happen is that a frame would get "stuck" in the MAC (mostly because of long standing DMA setup bugs) and if axq_depth or axq_aggr_depth > 2, the software queue code won't queue anything further. * the tid txq_depth=129, so there's 129 frames in the queue * hwq_depth=0, there's no frames from this TID queued to the hardware * bar_wait=0, so the TID isn't waiting for a BAR frame to complete before the queue is unpaused * isfiltered=0, so there's no filtered traffic waiting to complete before we can continue (eg power save handling) Now the fun bits: * sched=1 - the software scheduler is actually trying to send frames * paused=0, incomp=0 - the TID isn't paused (eg wiating for BAR to complete, ADDBA negotiation, etc) * incomp=0 - ie, there's no frames that need to complete before the queue is unpaused (see above) So, ok. it all looks fine. Next, I waited until the thing again hung, and this time I logged in via a different laptop and set up software TX debugging: # sysctl dev.ath.1.debug=0x1fc000020 And this is what I got: ath1: ath_txq_sched: tid=1, paused=0 ath1: ath_tx_tid_hw_queue_aggr: tid=1 ath1: ath_tx_rate_fill_rcflags: i=0, rate=0x8b, flags=0x19, max4ms=25708 ath1: ath_tx_rate_fill_rcflags: i=1, rate=0x8a, flags=0x19, max4ms=19280 ath1: ath_tx_rate_fill_rcflags: i=2, rate=0x89, flags=0x19, max4ms=12852 ath1: ath_get_aggr_limit: max frame len= 12852 ath1: ath_tx_tid_hw_queue_aggr: ath_tx_form_aggr() status=1 .. so, the software scheduler was running, it tried queuing something out, and ath_tx_form_aggr() returned 1 which is ATH_AGGR_BAW_CLOSED. _that_ happens in this condition: /* * If the packet has a sequence number, do not * step outside of the block-ack window. */ if (! BAW_WITHIN(tap->txa_start, tap->txa_wnd, SEQNO(bf->bf_state.bfs_seqno))) { status = ATH_AGGR_BAW_CLOSED; break; } .. now, let's look at what's going on. the first frame seqno here is (say) 3764. The window is 64 frames. txa_start is 3700. So, the first frame is definitely outside the sequence window and ath_tx_form_aggr() is quite rightly saying "nope, we can't schedule this yet." Now, I have no idea right now why this is happening. It may be some off-by-one in some comparison somewhere. The check here isn't an off-by-one as the seqno in question is plainly out of sequence. It _could_ be that there was a hole in the sequence numbers being assigned; that would certainly mess things up. I'll go and review the various places where sequence numbers are assigned and whether all the locking is correct. Unfortunately (!) I made a point of using the net80211 per-TID sequence number field which in the case of net80211 didn't use to be locked at all. I may have to just ditch that and have the driver set its own sequence numbers if aggregation is used. (Maybe for debugging I can track it privately too in the ath driver and complain if they drift out of sync.) I'll file a PR with this so it's being tracked. Anyway - this wifi stuff is mystical but there's plenty of logging and debugging going on right now. What I do note however is that I really wish the MAC addresses of the nodes were logged, as it's a pain to figure out which logging entries match up with which node. As a side note - if anyone would like a smallish project - it'd be nice to introduce a DPRINTF() for the ath driver code that took a node parameter too - so I can do per-node debugging as well as global driver debugging. That way I can do things like turn on debugging only for a given node and still use the VAP for other devices. -a From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 29 19:40:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AC44CE26 for ; Sat, 29 Mar 2014 19:40:31 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6933138E for ; Sat, 29 Mar 2014 19:40:31 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id i8so7476172qcq.31 for ; Sat, 29 Mar 2014 12:40:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FyqMhyl1QDskk0z0QYxqWpGs7QMC3+Q1Vpz4QfPwoec=; b=pJQ0E8mEIgB96C6ybH2p1yq0+toLRt6Wa0/hEl8myI5P8hp9arsBZxC/RlRwFGMMFh p/Lv24OiG9Yuh3hYkRbWJg0LWeKqr7JEOeeasmKpvPAY2M1yCMxqW3Up2tHDwcwRkR8u KT2uuJkdHWa/lWC16xPD2N4Ot6lbEB0GaSUH3grY1GYVDBz8HVLVquAY/t2C17USu7Ai 6OlPEp6RP7hj4eTfxAHX5wMbDA4fvYY2l5dUfgreYMmcsQFkLYz6Z7eKHcW0/D+X7+az JZROtj4nDKGWjCbZJrvKx59+Y4crDCLluzQFQkMc84bZnEPKlF06++VbY9igMSXjmnZ7 C6bg== MIME-Version: 1.0 X-Received: by 10.224.164.199 with SMTP id f7mr2442105qay.83.1396122030550; Sat, 29 Mar 2014 12:40:30 -0700 (PDT) Received: by 10.224.50.143 with HTTP; Sat, 29 Mar 2014 12:40:30 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> <20140315010640.GB65392@ns.umpquanet.com> Date: Sat, 29 Mar 2014 12:40:30 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 29 Mar 2014 19:40:31 -0000 So I exposed the iwi statistics messages but for some odd reason I actually get garbage statistics. The linux driver only looks at two fields (which are correctly filled out) but the rest of the fields aren't filled out. I'm not yet sure why. -a On 17 March 2014 18:46, Adrian Chadd wrote: > Yup, I found a 2100 and 2200. And yes it does dump out a bunch of > statistics stuff when the NIC is running. > > I'll see about exposing the statistics messages via some API soon. > > -a > > > On 14 March 2014 18:55, Adrian Chadd wrote: >> Nope; there's no code for handling the messages yet. >> >> I'll dig around to see if I can find a 2200 series NIC in a laptop >> here or in my collection. I know I have 3945 NICs, but not the 2200.. >> >> -a >> >> >> On 14 March 2014 18:06, Jim Long wrote: >>> Thank you for your reply. >>> >>> This would be via syslog in /var/log/messages? Nothing that I see: >>> >>> $ zgrep -il notification /var/log/messages* >>> $ >>> >>> >>> >>> On Fri, Mar 14, 2014 at 05:50:12PM -0700, Adrian Chadd wrote: >>>> It'd be stuff like this: >>>> >>>> case IWI_NOTIF_TYPE_CALIBRATION: >>>> case IWI_NOTIF_TYPE_NOISE: >>>> case IWI_NOTIF_TYPE_LINK_QUALITY: >>>> DPRINTFN(5, ("Notification (%u)\n", notif->type)); >>>> break; >>>> >>>> >>>> >>>> -a >>>> >>>> >>>> On 14 March 2014 17:18, Adrian Chadd wrote: >>>> > Hi, >>>> > >>>> > I'm not sure what kind of statistics or diagnostics iwi spits out. >>>> > It's likely worth reviewing the linux and freebsd drivers to see if it >>>> > does spit out any kind of statistics messages. That's a good starting >>>> > point. >>>> > >>>> > Thanks! >>>> > >>>> > >>>> > -a >>>> > >>>> > >>>> > On 14 March 2014 16:00, Jim Long wrote: >>>> >> I have a long-standing problem that involves the iwi interface on >>>> >> my Thinkpad T42 running 9.2-PRERELEASE circa 28 Aug 2013. >>>> >> >>>> >> Some wifi connections I make show good signal strength, but poor >>>> >> latency and/or packet loss to the WAP IP. I can't find other >>>> >> wifi users who perceive the wifi performance as poor, so I am >>>> >> assuming the problem is local to me. >>>> >> >>>> >> I will say this is generally repeatable by location: good >>>> >> locations are usually good, bad locations are usually bad. My >>>> >> theory is that the 2200BG likes some WAPs that I use more than it >>>> >> likes others. I'd like to find out what I can do to either fix >>>> >> the problem, or at least be able to accurately tell the WAP owner >>>> >> what their problem is. >>>> >> >>>> >> I'm ignorant about how to troubleshoot problems like this, so >>>> >> please suggest some diagnostic information I can provide to guide >>>> >> either of us toward a solution. >>>> >> >>>> >> Thank you, >>>> >> >>>> >> Jim >>>> >> >>>> >> from dmesg: >>>> >> >>>> >> iwi0: mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2 >>>> >> wlan0: Ethernet address: 00:12:f0:ca:5c:85 >>>> >> >>>> >> I get this a lot, but don't know if it's relevant. It seems >>>> >> to appear during both good and bad connections: >>>> >> >>>> >> iwi0: need multicast update callback >>>> >> >>>> >> >>>> >> Here's 61db of S/N ratio, resulting in almost 50% packet loss: >>>> >> >>>> >> $ wlanstats ; ping -c20 wap2 >>>> >> 36 rx frame too short >>>> >> 5 rx from wrong bssid >>>> >> 374 rx discard 'cuz dup >>>> >> 5 rx discard 'cuz mcast echo >>>> >> 3 rx discard mgt frames >>>> >> 1347 rx beacon frames >>>> >> 4151 rx element unknown >>>> >> 42 rx frame chan mismatch >>>> >> 7 rx disassociation >>>> >> 7 beacon miss events handled >>>> >> 6 active scans started >>>> >> 1446 rx management frames >>>> >> 2 tx failed 'cuz vap not in RUN state >>>> >> 28752 total data frames received >>>> >> 8679 unicast data frames received >>>> >> 20073 multicast data frames received >>>> >> 12186 total data frames transmit >>>> >> 12186 unicast data frames sent >>>> >> 54M current transmit rate >>>> >> 61 current rssi >>>> >> -95 current noise floor (dBm) >>>> >> -34 current signal (dBm) >>>> >> PING wap2 (192.168.2.1): 56 data bytes >>>> >> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=20.726 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.974 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.278 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.942 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.008 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.921 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=1.755 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=0.934 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.803 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.698 ms >>>> >> 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=2.382 ms >>>> >> >>>> >> --- wap2 ping statistics --- >>>> >> 20 packets transmitted, 11 packets received, 45.0% packet loss >>>> >> round-trip min/avg/max/stddev = 0.921/3.311/20.726/5.540 ms >>>> >> >>>> >> To my knowledge the OS is using the latest 3.1 firmware for the >>>> >> interface: >>>> >> >>>> >> $ cd /usr/src/sys/contrib/dev/iwi >>>> >> $ grep ^FW Makefile; md5 * >>>> >> FW_VERSION=3.1 >>>> >> MD5 (LICENSE) = 11963afae1fb1117b86fde8187152b9a >>>> >> MD5 (Makefile) = 2e4c774520e878e5cf8f3be7373fec02 >>>> >> MD5 (ipw2200-bss.fw.uu) = 7c15a60e1ccf28c332d3d795af99012b >>>> >> MD5 (ipw2200-ibss.fw.uu) = b529089d6eee6c12a918f361ee2c8347 >>>> >> MD5 (ipw2200-sniffer.fw.uu) = 9e6c7a76cb528cb1d9f1996189d9c699 >>>> >> >>>> >> _______________________________________________ >>>> >> 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 Sat Mar 29 20:04:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB8A76BD for ; Sat, 29 Mar 2014 20:04:24 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6847E7CE for ; Sat, 29 Mar 2014 20:04:24 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id q108so2309617qgd.38 for ; Sat, 29 Mar 2014 13:04:23 -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=I6BelgVD/rxjZmOVh+CfhytPfYn0vLqTA90v0LcV0gY=; b=B/QRe8iSb+LMQW3jYYhk6brrzF38pHP3+OFvzLTc4xFxdHcWl1QyZ+igGYmUDqeUqm Sydys9m9UcE44YivVnFsBn7rcV2Jrof1KQBO+Njf55p0CCqWLHW10RmzTRk3gjGsEU3b 7bevI+uIxxNgt8sl6QoVKB8mMDVm1bo7kZHHLWklDiNR8Ylqg2k2a3yLe68cht7DsWic xjUoxVHXGEwW5/IHKtYOXchSlJNO+VkDvBj+sZfUuY9M4e45dd5rVOLcf5HZxT/8SQs0 9mJVPuLjt/5pQudpodAjFdQU7zO2CvGC5XidhJSaVVs1hdpUyN9x3c9TaZ1mEOuFxMWN ABzA== MIME-Version: 1.0 X-Received: by 10.224.127.200 with SMTP id h8mr17596905qas.13.1396123463424; Sat, 29 Mar 2014 13:04:23 -0700 (PDT) Received: by 10.224.50.143 with HTTP; Sat, 29 Mar 2014 13:04:23 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> <20140315010640.GB65392@ns.umpquanet.com> Date: Sat, 29 Mar 2014 13:04:23 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 29 Mar 2014 20:04:24 -0000 On 29 March 2014 12:40, Adrian Chadd wrote: > So I exposed the iwi statistics messages but for some odd reason I > actually get garbage statistics. The linux driver only looks at two > fields (which are correctly filled out) but the rest of the fields > aren't filled out. > > I'm not yet sure why. Yeah, I don't quite yet know why I'm getting a firmware notification that is big enough to have all the right statistics fields but doesn't actually fill them out. But it's intel hardware; I have no firmware source, no firmware documentation and no real help from Intel. :-) Sorry! -a From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 29 20:06:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE5C96E5 for ; Sat, 29 Mar 2014 20:06:59 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA1FF7DB for ; Sat, 29 Mar 2014 20:06:59 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id z60so322794qgd.36 for ; Sat, 29 Mar 2014 13:06:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NHcvWf44fVT73vkAfkH1haQmqLH5NJxrhPakqpsfcFs=; b=O6AF8eonwDaakazfpRuPI3oNnQKLYgrlYdThEyZ/+HAzcun8vAg79bLfVL4JNucaq/ zJjDquLx5AVaubs7ngfGLyRT0D0b9C9PEy+K9BLkO5bo/SqWMG2k0XFdiaA74Buyd1Iw Qbvwc0l0GlMt703KiaStEfCvukpGHxfkZ1y4w3yuBbwoIz+mseldGee6CWmu98rxjU9G cioQw6tEbshsax6iQRJT0I5qjvT043egENCgGaeBSCntJOAsha8A+gRYwFUFJ7sx2o/B FcbaQ1BntEHOwy4EvZ+NlwllOYFTlQ4LnSee7sLd7O/oMo3TZtu7fXb9lQSK2jyAf2TT 82DA== MIME-Version: 1.0 X-Received: by 10.224.66.74 with SMTP id m10mr17512273qai.14.1396123618877; Sat, 29 Mar 2014 13:06:58 -0700 (PDT) Received: by 10.224.50.143 with HTTP; Sat, 29 Mar 2014 13:06:58 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> <20140315010640.GB65392@ns.umpquanet.com> Date: Sat, 29 Mar 2014 13:06:58 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 29 Mar 2014 20:07:00 -0000 .. actually, this is even more screwed up. here's what I get in the RX notification messages: time=3D1396123498.839215 g 9 % =EF=BF=BD =02 =EF=BF=BD =EF=BF=BD =EF=BF=BD =EF=BF=BD =EF=BF=BD =EF=BF=BD $ =EF=BF=BD = =EF=BF=BD =16 D =EF=BF=BD =EF=BF=BD =EF=BF=BD =EF=BF=BD =EF=BF=BD P =EF=BF=BD =EF=BF=BD =EF=BF=BD =03 E U =EF=BF=BD @ =11 =EF=BF=BD =01 =EF=BF=BD =01 =EF=BF=BD D \ D \ z =EF=BF=BD d { " h o s t _ i n t " : 7 4 0 7 6 9 6 2 7 , " v e r s i o n " : [ 1 , 8 ] , " d i s p l a y n a m e " : " " , " p o r t " : =02 -- .. it is actually looking like this is 'old' data in the receive buffer and I'm not actually seeing valid data. I'll go and check further. Thanks! -a From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 29 21:16:51 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F3C4379 for ; Sat, 29 Mar 2014 21:16:51 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A9C0CC8 for ; Sat, 29 Mar 2014 21:16:50 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id r5so7504769qcx.32 for ; Sat, 29 Mar 2014 14:16:50 -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=7RuIfg2BJ64z4ivc9ssJSPTr3gQQzhTohDlf1YbzBKU=; b=F+5pvA4mPlXfsB6EPSDeG/OYjJ/V6B1I4c0kCYszAgO73BI3WWJFHdD5sTvrdTl62A WFKv4xnPqXLsicnXFnJKAKkEXJFq2i2sy6/HkgRm6ksmFjS2sUEGuWxS+Im20mlVmUyQ oQWY6PZUzzN5m4DU8yY3rxjSWzky6wxDX+u1LRbSIWWRtL8z41F7g+XlcUXv8NoZHLTz v97zJzOc6NMm2OVh6pn3VEsLnAnRWow/y1STDPierVDRGx/6kUke4I8mNJ6er4KSpvhY JN+Ifm7PwpVE9DZrgvuUzqWzGVhXD2Wx9AI53qP924Kpe1K6zSFZcxu5BOzIhBsYuuVZ dGXw== MIME-Version: 1.0 X-Received: by 10.224.93.10 with SMTP id t10mr2881075qam.82.1396127810149; Sat, 29 Mar 2014 14:16:50 -0700 (PDT) Received: by 10.224.50.143 with HTTP; Sat, 29 Mar 2014 14:16:50 -0700 (PDT) In-Reply-To: References: <20140314230013.GA25473@ns.umpquanet.com> <20140315010640.GB65392@ns.umpquanet.com> Date: Sat, 29 Mar 2014 14:16:50 -0700 Message-ID: Subject: Re: Poor performance w/Intel 2200BG (iwi) on FreeBSD 9.2 From: Adrian Chadd To: Jim Long Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 29 Mar 2014 21:16:51 -0000 .. so, even if i blank the receive buffer, the NIC is copying some old RX data into it, then the only information that's valid is actually the link quality (ie, how much time the link has been silent or not.) Which I guess is what the LINK_DETERIORIATION notification is. I wish I knew how to tell the NIC to send me actual statistics from the NIC. I've emailed the Linux ipw maintainer to see if he has any ideas. If not then I'm afraid I'm done, sorry. :( -a From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 30 08:31:26 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5266755 for ; Sun, 30 Mar 2014 08:31:26 +0000 (UTC) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88368174 for ; Sun, 30 Mar 2014 08:31:26 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id 63so6169758qgz.34 for ; Sun, 30 Mar 2014 01:31:25 -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=LUVGkXhhunU+iUWzmOJ2HdQGkWqkKK2CJc9YYzcXwcI=; b=vkbRHT2Ci1DObsYzu5SLqJw13T5pXbwG4USSQZ4LNRxYz+xbrF5YXsc2st8Tdc5YlZ LJb1z/TPuugEkjRsZcrbxU8hS4t1Y2xYOdoGTPaBCdZsaqt3sVAOB3/5q8+5khQDL1vT 4Jrn+oglixLGmy1r/7EK8taCyGwoy/pDhJ0KIILNHqORKRbF85q9USbjYZqkee3CekTk t4La1JnYWbCbX8TTLfe4QWfE8dmVVFW4qh7PpUiRa2OwYJ6TIsP49MViB2XOqSOBIpkO ZhHzc4FFtWvB6ipEx7ol7eKGuYOHpBzDasKZcBTk+v9cdFc2MwexbiMFEYK99qdb2lcS 6wbQ== MIME-Version: 1.0 X-Received: by 10.224.119.141 with SMTP id z13mr20044685qaq.48.1396168285687; Sun, 30 Mar 2014 01:31:25 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Sun, 30 Mar 2014 01:31:25 -0700 (PDT) Date: Sun, 30 Mar 2014 01:31:25 -0700 X-Google-Sender-Auth: 9-I9TsN02AmKLWkykMrdHY3qKVs Message-ID: Subject: [rft] ath(4) and preparations for power save support in STA mode From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2014 08:31:26 -0000 Hi, I've been working towards supporting basic power save support in ath(4). Now, this patch implements the basic driver hooks required to attempt to do this. It's only been lightly tested on the AR5416. I haven't tested it on any other hardware so if you do try this, it may just blow up in your face. http://people.freebsd.org/~adrian/ath/20140330-ath-powersave-1.diff However, it's also supposed to be a no-op during normal driver use. So what's it do? Firstly, the hardware has three main states. "full sleep" is the lowest power mode. "force awake" is "being forced fully awake, regardless of whether we need to be." Finally, and the most interesting one, is "network sleep." This is where the MAC powers down bits and pieces of things until each beacon interval when it wakes up to receive the beacon, check if the station AID is set in the TIM (or ATIM for later hardware, if in IBSS mode) and if so, stays awake long enough to receive further frames before going to sleep. Now for the gruesome details. * The hardware has to be woken up for things like calibration and DMA work. * The hardware can go into network sleep until each beacon interval (but, see below.) * Only some registers can be read - for the AR5416 family, it's the RTC (clock programming and power mode), the host interface (GPIO, LED and PCI/PCIe interface, including SYNC interrupts), and the EEPROM interface. So in order to ensure everything else is valid, one must force the device awake if the pending-interrupts check shows there's something to handle. * .. and it should also be forced awake for the TX, RX and TX completion path * .. as well as reset, channel programming, etc. * The hardware may decide to go to sleep once the reason(s) for it to be awake are gone, so it's best to force it awake to do whatever's needed and then put it back to network sleep once it's done. * The AR5416 at least will stay awake if you start a transmit and then let it go back to network sleep. Ie, you don't have to keep the hardware set as "force awake" when doing a transmit - which greatly simplifies the transmit logic. However, I've no idea if this holds true for all the other various chips out there. So, the patch as posted actually seems to work well enough if I force the hardware to network sleep - I'm not programming the TX or RX registers inappropriately or trying to do calibration whilst the NIC is asleep. However, it won't stay associated because, and this is totally expected - none of the net80211 station powersave framework is hooked in. Specifically: * The frames being transmitted whilst the NIC is asleep don't have the FC1 PWR_MGT bit set to 1, so the AP doesn't try buffering things, and * There's nothing comprehensive to hook into the receive path to tell the AP that we're now awake. It turns out there's a powersave state (IEEE80211_S_SLEEP) which is mostly implemented. There's also the STA powersave stuff that's used by the bgscan code that also is useful for exactly this. It will correctly buffer outbound frames until we come out of powersave and it'll send NULL frames appropriately to the AP to bring it in and out of powersave. What's however missing is: * if a beacon is received with the TIM bit for us set to 1, we need to either kick off a ps-poll (which we have no support for transmitting yet) or wake the VAP up. Otherwise we'll just stay asleep until we force ourselves back to RUN. * There's no actual sleep management code for station mode operation. Ie, nothing tracks ic_lastdata or anything else and decides to transition the VAP to SLEEP, neither does it have any logic to transition it back to RUN after a timeout (ie, being asleep too long.) I'm going to take a crack at sorting out the missing power-save hooks in net80211 so we can do explicit power save if the NIC requires it. iwn(4) doesn't, so the IEEE80211_S_SLEEP stuff just plain won't be used there. Given all of this, I'd appreciate it if people would try the above patch out with AH_DEBUG and ATH_DEBUG compiled in. Let me know if it complains about anything. Thanks, -a From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 30 08:32:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74E10774 for ; Sun, 30 Mar 2014 08:32:38 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34C6F1E7 for ; Sun, 30 Mar 2014 08:32:38 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so6292445qgd.1 for ; Sun, 30 Mar 2014 01:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=6wMt7EN96wPVQLdXCLsqjwDnBv9WL3c6i5MlfOkkWNk=; b=m3LnSSijwJ8CD18sw98gj7x13C1njOVe8jTPMjwEdShoUH0n6/MPX19zaEk+i8Qubo //6pRTXAwweHQD5/C7knoAwK2Lp7ivdEltlxR4pR5FPUl+KfcjEBnaA9WFvxIgdG+9k8 iDx8u0wpxUfnniIsvQebDvughHT3g9//gys5HBYomwf/oIBTX3wyfWGjp0fV8ynz/rCb fLudhJRF4poRPHaaV+7xR7M8SyhqNPeia4YFMsHvHmjeRQoYMKs4HlD0iLqNeerHcExP aospQVg2ZOKwwhYWy2Yg5sHhZh3XTx2PU/JxbLtplAO2RJm0kTTAqNUoXQULsAkmA2hu 5lVQ== MIME-Version: 1.0 X-Received: by 10.224.161.140 with SMTP id r12mr20451236qax.24.1396168357354; Sun, 30 Mar 2014 01:32:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Sun, 30 Mar 2014 01:32:37 -0700 (PDT) In-Reply-To: References: Date: Sun, 30 Mar 2014 01:32:37 -0700 X-Google-Sender-Auth: C5-LzeHGNwYyj0jQ54Z6wGiZhTw Message-ID: Subject: Re: [rft] ath(4) and preparations for power save support in STA mode From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2014 08:32:38 -0000 .. and I should say that the one thing it currently _does_ do that's not a no-op is that once the final VAP is destroyed or marked down, the NIC is actually put into full-sleep mode. Right now this only happens on detach. So if you'd like to do some power consumption tests, you can certainly test power draw before and after you bring the interface down. The difference between awake and full-sleep is quite noticable. -a On 30 March 2014 01:31, Adrian Chadd wrote: > Hi, > > I've been working towards supporting basic power save support in ath(4). > > Now, this patch implements the basic driver hooks required to attempt > to do this. It's only been lightly tested on the AR5416. I haven't > tested it on any other hardware so if you do try this, it may just > blow up in your face. > > http://people.freebsd.org/~adrian/ath/20140330-ath-powersave-1.diff > > However, it's also supposed to be a no-op during normal driver use. > > So what's it do? > > Firstly, the hardware has three main states. "full sleep" is the > lowest power mode. "force awake" is "being forced fully awake, > regardless of whether we need to be." Finally, and the most > interesting one, is "network sleep." This is where the MAC powers down > bits and pieces of things until each beacon interval when it wakes up > to receive the beacon, check if the station AID is set in the TIM (or > ATIM for later hardware, if in IBSS mode) and if so, stays awake long > enough to receive further frames before going to sleep. > > Now for the gruesome details. > > * The hardware has to be woken up for things like calibration and DMA work. > * The hardware can go into network sleep until each beacon interval > (but, see below.) > * Only some registers can be read - for the AR5416 family, it's the > RTC (clock programming and power mode), the host interface (GPIO, LED > and PCI/PCIe interface, including SYNC interrupts), and the EEPROM > interface. So in order to ensure everything else is valid, one must > force the device awake if the pending-interrupts check shows there's > something to handle. > * .. and it should also be forced awake for the TX, RX and TX completion path > * .. as well as reset, channel programming, etc. > * The hardware may decide to go to sleep once the reason(s) for it to > be awake are gone, so it's best to force it awake to do whatever's > needed and then put it back to network sleep once it's done. > * The AR5416 at least will stay awake if you start a transmit and then > let it go back to network sleep. Ie, you don't have to keep the > hardware set as "force awake" when doing a transmit - which greatly > simplifies the transmit logic. However, I've no idea if this holds > true for all the other various chips out there. > > So, the patch as posted actually seems to work well enough if I force > the hardware to network sleep - I'm not programming the TX or RX > registers inappropriately or trying to do calibration whilst the NIC > is asleep. However, it won't stay associated because, and this is > totally expected - none of the net80211 station powersave framework is > hooked in. Specifically: > > * The frames being transmitted whilst the NIC is asleep don't have the > FC1 PWR_MGT bit set to 1, so the AP doesn't try buffering things, and > * There's nothing comprehensive to hook into the receive path to tell > the AP that we're now awake. > > It turns out there's a powersave state (IEEE80211_S_SLEEP) which is > mostly implemented. There's also the STA powersave stuff that's used > by the bgscan code that also is useful for exactly this. It will > correctly buffer outbound frames until we come out of powersave and > it'll send NULL frames appropriately to the AP to bring it in and out > of powersave. > > What's however missing is: > > * if a beacon is received with the TIM bit for us set to 1, we need to > either kick off a ps-poll (which we have no support for transmitting > yet) or wake the VAP up. Otherwise we'll just stay asleep until we > force ourselves back to RUN. > * There's no actual sleep management code for station mode operation. > Ie, nothing tracks ic_lastdata or anything else and decides to > transition the VAP to SLEEP, neither does it have any logic to > transition it back to RUN after a timeout (ie, being asleep too long.) > > I'm going to take a crack at sorting out the missing power-save hooks > in net80211 so we can do explicit power save if the NIC requires it. > iwn(4) doesn't, so the IEEE80211_S_SLEEP stuff just plain won't be > used there. > > Given all of this, I'd appreciate it if people would try the above > patch out with AH_DEBUG and ATH_DEBUG compiled in. Let me know if it > complains about anything. > > Thanks, > > > -a From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 31 00:43:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 963ED86B for ; Mon, 31 Mar 2014 00:43:58 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F1A7EE8 for ; Mon, 31 Mar 2014 00:43:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=0gw6hYNi3IdI+AY5x9ckv/dsFnE2A9G6Pigs2hg4dPY=; b=yE8ymdNx1poFI62fii65ZdogOctha5jUjNGonQbq9yRfYmmB1i4Z6eFuqi8X4hdvoYASc+W0zs6ofFKYzUx89UGbw1vvgrjG6YfetXdI/nfGEP9zbMZQL//8Hoa3bzv6r6fnUU90K08esXjKoU/N/J6Bs1zhG2TbLR+cI41738o=; Received: from [182.55.101.96] (port=41603 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WUPBq-003FlT-1g for freebsd-wireless@freebsd.org; Sun, 30 Mar 2014 17:30:58 -0600 Date: Mon, 31 Mar 2014 07:30:54 +0800 From: Erich Dollansky To: "freebsd-wireless@freebsd.org" Subject: iwn0 hangs randomly when starting the machine Message-ID: <20140331073054.5d7642d6@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 31 Mar 2014 00:43:58 -0000 Hi, since I upgraded to r263767, I have the following problem: Wireless does not start all the while. When it does not start, it hangs then forever. wpa_supplicant's state in top is then '-'. If I start wpa_supplicant by hand, it will hang and it cannot be stopped by control C. The light indicating that wireless is up is never on in this case. Rebooting the machine solves the problem. I did not find any other way to solve as the wireless related commands will hang. When the wireless network comes up, I can work just normal. Erich PS: The hardware: iwn0: mem 0xf2500000-0xf2501fff irq 17 at device 0.0 on pci3 From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 31 09:38:51 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 259C8C68 for ; Mon, 31 Mar 2014 09:38:51 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9A261B5 for ; Mon, 31 Mar 2014 09:38:50 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id q108so7160262qgd.9 for ; Mon, 31 Mar 2014 02:38:50 -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=csOvFwgYzCXke4L1ADE6drayn2UxmMlGxKtUcSMO69M=; b=E6FhHQsvE0KwAbuJfBXtacoXeiUlT7RoKAv7LVNm5LWJhzWTw2PHopVHPhu3XEE/hr u4IKq7lsDJX/i2yy2SARMzBN0usoKhV10tHdFFyEdMWuE/bxnKai3gJ9q+oj7rXO3h0G sgZ9R/dhp/wGpepPEM7HnoJlMvduTlu5SbhlmIwslpMLSfssyRnLwc468AUhS/1IzgEi l3po68p7WUOZzGgHx5Cyl/X+IgqOiLCIsRUECGGs4z6oVo+xpaNOofEJlRQcg3aWm+PM VzM08DPCyZdVXurohrD+B+y72Mvhwl2m1JNW1c/pciX5RzwxfHq5695NId/BuiHyQHSQ vOgg== MIME-Version: 1.0 X-Received: by 10.229.17.69 with SMTP id r5mr26297290qca.7.1396258730042; Mon, 31 Mar 2014 02:38:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Mon, 31 Mar 2014 02:38:49 -0700 (PDT) In-Reply-To: <20140331073054.5d7642d6@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> Date: Mon, 31 Mar 2014 02:38:49 -0700 X-Google-Sender-Auth: bekaGHrwAYQwMfYAEiZibDzYoAo Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 31 Mar 2014 09:38:51 -0000 Hi, What were you running before and did the NIC work? -a On 30 March 2014 16:30, Erich Dollansky wrote: > Hi, > > since I upgraded to r263767, I have the following problem: > > Wireless does not start all the while. When it does not start, it hangs > then forever. wpa_supplicant's state in top is then '-'. If I start > wpa_supplicant by hand, it will hang and it cannot be stopped by > control C. The light indicating that wireless is up is never on in this > case. Rebooting the machine solves the problem. I did not find any > other way to solve as the wireless related commands will hang. > > When the wireless network comes up, I can work just normal. > > Erich > > PS: > > The hardware: > > iwn0: mem 0xf2500000-0xf2501fff irq 17 > at device 0.0 on pci3 > _______________________________________________ > 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 Mon Mar 31 11:06:54 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 725FBC1D for ; Mon, 31 Mar 2014 11:06:54 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 462E0BB6 for ; Mon, 31 Mar 2014 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2VB6swm058882 for ; Mon, 31 Mar 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2VB6rNV058880 for freebsd-wireless@FreeBSD.org; Mon, 31 Mar 2014 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 31 Mar 2014 11:06:53 GMT Message-Id: <201403311106.s2VB6rNV058880@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.17 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, 31 Mar 2014 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/187624 wireless WEP and other ciphers do not work if h/w driver does n o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 193 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 2 09:11:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B69CCC53 for ; Wed, 2 Apr 2014 09:11:53 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D9D3E57 for ; Wed, 2 Apr 2014 09:11:52 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s329BhTE054230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 2 Apr 2014 09:11:45 GMT (envelope-from theraven@FreeBSD.org) From: David Chisnall Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: WDS with a FreeBSD access point Message-Id: Date: Wed, 2 Apr 2014 10:11:38 +0100 To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Apr 2014 09:11:53 -0000 Hello the wireless people, I have a machine that runs FreeBSD (10) as my AP, which works nicely but = unfortunately doesn't quite have the range to reach one of the rooms in = my flat. I would like to use a cheap off-the-shelf AP to extend the = range, but apparently using WDS requires all of the APs to know about = it. Does anyone know what I need to do to the FreeBSD box to make it talk to = the WDS relay / remote? David From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 2 09:19:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0ECEFDDE; Wed, 2 Apr 2014 09:19:31 +0000 (UTC) Received: from mail.koukaam.se (mail.koukaam.se [193.86.201.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.koukaam.se", Issuer "KOUKAAM Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7594CEFF; Wed, 2 Apr 2014 09:19:29 +0000 (UTC) Received: from [192.168.1.41] (unassigned-81-90-254-125.ujezd.net [81.90.254.125] (may be forged)) (authenticated bits=0) by mail.koukaam.se (8.14.5/8.14.5) with ESMTP id s329JF7o057709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 2 Apr 2014 11:19:20 +0200 (CEST) (envelope-from knezour@weboutsourcing.cz) Message-ID: <533BD60D.9050701@weboutsourcing.cz> Date: Wed, 02 Apr 2014 11:19:09 +0200 From: Ondra Knezour User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: David Chisnall , freebsd-wireless@freebsd.org Subject: Re: WDS with a FreeBSD access point References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Apr 2014 09:19:31 -0000 Dne 2.4.2014 11:11, David Chisnall napsal(a): > Does anyone know what I need to do to the FreeBSD box to make it talk to the WDS relay / remote? See ifconfig(8) - section wlanmode wds -- Ondra Knezour From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 2 21:33:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CAF3A7CE; Wed, 2 Apr 2014 21:33:54 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57959ECF; Wed, 2 Apr 2014 21:33:54 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id m5so782330qaj.7 for ; Wed, 02 Apr 2014 14:33:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=V45vfrcxW19wUWhXUBHkwtfMmqmXOLMknJFb7D5ZMiw=; b=UxaFU2ZNFSkRmOMnAWnt1cQSG47O9M/bOO5eK/FStf1QAFExYsCNOexbAwGxWC6kLF WCe8EuY1zarTp1Og6cKxvk4u4sHojoCTPoCKLBYhTc2+k49yT5nhykLHEe80wiaV5aBG igz82kMZDYzd8u7mozEZlpMJyC7edhMiZUXf0YijGYSH/UnOkY2KGnniZIcKY+YHnhF5 iAJKmxff61E7HSPaGdnI4mJgBVAd+dgX2cUSW+pvImvO44SgqQPjG7LPZx9lZ2CRVRqc ndpqNv3Nv3v6i5tTCVfoNwyAN8ldhWp/5zWFS77rXtq2HjPfMolsaWzvRuE1J8fYlPN7 qQIw== MIME-Version: 1.0 X-Received: by 10.224.96.138 with SMTP id h10mr128874qan.26.1396474432996; Wed, 02 Apr 2014 14:33:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Wed, 2 Apr 2014 14:33:52 -0700 (PDT) In-Reply-To: <533BD60D.9050701@weboutsourcing.cz> References: <533BD60D.9050701@weboutsourcing.cz> Date: Wed, 2 Apr 2014 14:33:52 -0700 X-Google-Sender-Auth: o0eAaTlsIfjpfx79djReMwfde6A Message-ID: Subject: Re: WDS with a FreeBSD access point From: Adrian Chadd To: Ondra Knezour Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Apr 2014 21:33:54 -0000 Right, but has someone done it and has some instructions / horror stories? I'm busy trying to figure out power save support and fix some 1n AP mode traffic hangs, so I can't really also document/diagnose/debug WDS. I'm happy to do the debug bit, but I need some help in general there. Thanks, -a On 2 April 2014 02:19, Ondra Knezour wrote: > Dne 2.4.2014 11:11, David Chisnall napsal(a): > >> Does anyone know what I need to do to the FreeBSD box to make it talk to >> the WDS relay / remote? > > > See ifconfig(8) - section wlanmode wds > > -- > Ondra Knezour > > _______________________________________________ > 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 Apr 3 03:20:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A17663B; Thu, 3 Apr 2014 03:20:54 +0000 (UTC) Received: from mail.koukaam.se (mail.koukaam.se [193.86.201.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.koukaam.se", Issuer "KOUKAAM Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B53ECE6F; Thu, 3 Apr 2014 03:20:53 +0000 (UTC) Received: from [192.168.1.41] (unassigned-81-90-254-125.ujezd.net [81.90.254.125] (may be forged)) (authenticated bits=0) by mail.koukaam.se (8.14.5/8.14.5) with ESMTP id s333KkOU072667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 3 Apr 2014 05:20:51 +0200 (CEST) (envelope-from knezour@weboutsourcing.cz) Message-ID: <533CD386.80906@weboutsourcing.cz> Date: Thu, 03 Apr 2014 05:20:38 +0200 From: Ondra Knezour User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: WDS with a FreeBSD access point References: <533BD60D.9050701@weboutsourcing.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 03:20:54 -0000 Dne 2.4.2014 23:33, Adrian Chadd napsal(a): > Right, but has someone done it and has some instructions / horror stories? There are some scripts in /usr/src/tools/tools/net80211/scripts - related are setup.wds setup.wdsmain and setup.wdsrelay. Also following message can bring in little more info http://lists.freebsd.org/pipermail/freebsd-net/2009-March/021559.html However I probably don't have any hardware to check it out right now :/ -- Ondra Knezour From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 06:39:20 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1855E95; Thu, 3 Apr 2014 06:39:20 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A380F36; Thu, 3 Apr 2014 06:39:20 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s336dC4u062216 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Apr 2014 06:39:18 GMT (envelope-from theraven@theravensnest.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: WDS with a FreeBSD access point From: David Chisnall In-Reply-To: <533CD386.80906@weboutsourcing.cz> Date: Thu, 3 Apr 2014 07:39:07 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> To: Ondra Knezour X-Mailer: Apple Mail (2.1874) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 06:39:20 -0000 On 3 Apr 2014, at 04:20, Ondra Knezour = wrote: > There are some scripts in /usr/src/tools/tools/net80211/scripts - = related are setup.wds setup.wdsmain and setup.wdsrelay. Also following = message can bring in little more info = http://lists.freebsd.org/pipermail/freebsd-net/2009-March/021559.html I found setup.wdsmain, which looks a bit like what I need. It creates = an extra bridging interface (not sure why I need this - some docs would = be nice - or even if I need it, as I'm using pf to move traffic between = my wired and wireless networks and I definitely don't want to do simple = bridging from the WAN to the WLAN), but then runs /usr/local/bin/wlanwds = - I've no idea which port this comes from... David From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 06:57:22 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 391F317E for ; Thu, 3 Apr 2014 06:57:22 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E75A2118 for ; Thu, 3 Apr 2014 06:57:21 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id hw13so1218701qab.4 for ; Wed, 02 Apr 2014 23:57:21 -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:content-transfer-encoding; bh=cvVM49awU1lfXvmcQwaRp1TWfYROnl0TYiDqYQ/hs9o=; b=GF8z4rIYMWN1UIPvQ5MKmDenSSjJCN5sWfx0MHs7evmI8JB8m2qoz16MQL3hR9Dkx/ T8120hm69lLKplAd0+vDDtfFJhVEDXkqtVm8bvvSiOm2LRsHViFSAjOadEFjsgAGIE1i dAErAh31PiUEqTsg3Mnf/UORrkFCgpncxOGdrttO7cJtglKHHdzZEbxBYAtyGNASjV3k 0UAQNP4FJPA3zZoyjRl2BBp81N6uZ1Pt9+Cu+/ALHWq6AP6ZvdHGxGn6iZlc5KpTWWKQ lsve+6Vr/NuDsYJAmNjua4h9mPO3QeZor7XwQdLaGEj5I5BceCnwSNhdjP+udhRtJlMp OQnQ== MIME-Version: 1.0 X-Received: by 10.140.48.199 with SMTP id o65mr5379707qga.16.1396508241068; Wed, 02 Apr 2014 23:57:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Wed, 2 Apr 2014 23:57:21 -0700 (PDT) In-Reply-To: References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> Date: Wed, 2 Apr 2014 23:57:21 -0700 X-Google-Sender-Auth: P_D0F-6gtnMdYbkcfcbQXjr0tcQ Message-ID: Subject: Re: WDS with a FreeBSD access point From: Adrian Chadd To: David Chisnall Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 06:57:22 -0000 Hi, Are both freebsd APs? It looks reasonably straightfoward. I really should just give this a go at home on an extender AP and test the hell out of it. So, for wifi traffic, you absolutely want the wifi VAPs in a bridge group as the traffic between stations and APs is all layer-2. There's no routing involved. If you want to route between the bridge0 interface and the rest of the system then please do so but do put the STA and AP VAPs into the same bridge group. (Those scripts do exactly that.) Thanks, and good luck! -a On 2 April 2014 23:39, David Chisnall wrote: > On 3 Apr 2014, at 04:20, Ondra Knezour wrote: > >> There are some scripts in /usr/src/tools/tools/net80211/scripts - relate= d are setup.wds setup.wdsmain and setup.wdsrelay. Also following message ca= n bring in little more info http://lists.freebsd.org/pipermail/freebsd-net/= 2009-March/021559.html > > I found setup.wdsmain, which looks a bit like what I need. It creates an= extra bridging interface (not sure why I need this - some docs would be ni= ce - or even if I need it, as I'm using pf to move traffic between my wired= and wireless networks and I definitely don't want to do simple bridging fr= om the WAN to the WLAN), but then runs /usr/local/bin/wlanwds - I've no ide= a which port this comes from... > > David > From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 07:05:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBAA5207; Thu, 3 Apr 2014 07:05:58 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 928F81C5; Thu, 3 Apr 2014 07:05:58 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s3375rN3062400 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Apr 2014 07:05:56 GMT (envelope-from theraven@theravensnest.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: WDS with a FreeBSD access point From: David Chisnall In-Reply-To: Date: Thu, 3 Apr 2014 08:05:48 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> To: Adrian Chadd X-Mailer: Apple Mail (2.1874) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 07:05:58 -0000 On 3 Apr 2014, at 07:57, Adrian Chadd wrote: > Are both freebsd APs? Nope, the main station is a FreeBSD box, the remote is a cheap commodity = AP (there are a lot that claim to do WDS for under =A310 - I have two = different models for testing). > It looks reasonably straightfoward. I really should just give this a > go at home on an extender AP and test the hell out of it. Let me know how it goes... > So, for wifi traffic, you absolutely want the wifi VAPs in a bridge > group as the traffic between stations and APs is all layer-2. I think I'm missing something here. The script created a bridge between = the wireless and wired interfaces. I don't think I want that, so what = do I want the bridge between? > There's > no routing involved. If you want to route between the bridge0 > interface and the rest of the system then please do so but do put the > STA and AP VAPs into the same bridge group. 'STA and AP VAPs'? Can we go back to assuming that I don't know = anything please? David From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 07:23:35 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8EAA0419; Thu, 3 Apr 2014 07:23:35 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 544C935A; Thu, 3 Apr 2014 07:23:35 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s337NVgh062512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Apr 2014 07:23:33 GMT (envelope-from theraven@theravensnest.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: WDS with a FreeBSD access point From: David Chisnall In-Reply-To: <533D0C02.9010303@weboutsourcing.cz> Date: Thu, 3 Apr 2014 08:23:25 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> <533D0C02.9010303@weboutsourcing.cz> To: Ondra Knezour X-Mailer: Apple Mail (2.1874) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 07:23:35 -0000 On 3 Apr 2014, at 08:21, Ondra Knezour = wrote: > Dne 3.4.2014 9:05, David Chisnall napsal(a): >> 'STA and AP VAPs'? Can we go back to assuming that I don't know = anything please? >=20 > STA - station, basically a client connecting to the access point > AP - access point > VAP - virtual AP, on one hardware device can be multiple virtual > APs/networks running My confusion is from the fact that I'm not sure why I have a VAP - I was = assuming my configuration would have a single wlan device that would = talk to stations and WDS remotes. Is this not the case? David From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 07:31:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D8545C8; Thu, 3 Apr 2014 07:31:41 +0000 (UTC) Received: from mx.weboutsourcing.cz (mx.weboutsourcing.cz [109.205.73.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37E7B5EB; Thu, 3 Apr 2014 07:31:40 +0000 (UTC) Received: from [192.168.46.157] ([193.86.201.140]) (authenticated bits=0) by mx.weboutsourcing.cz (8.14.4/8.14.4) with ESMTP id s337VbZc098339; Thu, 3 Apr 2014 09:31:38 +0200 (CEST) (envelope-from knezour@weboutsourcing.cz) Message-ID: <533D0E53.9020401@weboutsourcing.cz> Date: Thu, 03 Apr 2014 09:31:31 +0200 From: Ondra Knezour User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: David Chisnall Subject: Re: WDS with a FreeBSD access point References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 07:31:41 -0000 Dne 3.4.2014 8:39, David Chisnall napsal(a): > I found setup.wdsmain, which looks a bit like what I need. It > creates an extra bridging interface (not sure why I need this - some > docs would be nice - or even if I need it, as I'm using pf to move > traffic between my wired and wireless networks and I definitely don't > want to do simple bridging from the WAN to the WLAN), but then runs > /usr/local/bin/wlanwds - I've no idea which port this comes from... Found something in /head/tools/tools/net80211/wlanwds, check it out. -- Ondra Knezour From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 07:34:07 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D32B626; Thu, 3 Apr 2014 07:34:07 +0000 (UTC) Received: from mx.weboutsourcing.cz (mx.weboutsourcing.cz [109.205.73.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 24FC65FF; Thu, 3 Apr 2014 07:34:06 +0000 (UTC) Received: from [192.168.46.157] ([193.86.201.140]) (authenticated bits=0) by mx.weboutsourcing.cz (8.14.4/8.14.4) with ESMTP id s337LisE098213; Thu, 3 Apr 2014 09:21:44 +0200 (CEST) (envelope-from knezour@weboutsourcing.cz) Message-ID: <533D0C02.9010303@weboutsourcing.cz> Date: Thu, 03 Apr 2014 09:21:38 +0200 From: Ondra Knezour User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: David Chisnall , Adrian Chadd Subject: Re: WDS with a FreeBSD access point References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 07:34:07 -0000 Dne 3.4.2014 9:05, David Chisnall napsal(a): > 'STA and AP VAPs'? Can we go back to assuming that I don't know anything please? STA - station, basically a client connecting to the access point AP - access point VAP - virtual AP, on one hardware device can be multiple virtual APs/networks running -- Ondra Knezour From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 07:36:36 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB05865C; Thu, 3 Apr 2014 07:36:36 +0000 (UTC) Received: from mx.weboutsourcing.cz (mx.weboutsourcing.cz [109.205.73.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 27F6F611; Thu, 3 Apr 2014 07:36:35 +0000 (UTC) Received: from [192.168.46.157] ([193.86.201.140]) (authenticated bits=0) by mx.weboutsourcing.cz (8.14.4/8.14.4) with ESMTP id s337aXVl098448; Thu, 3 Apr 2014 09:36:33 +0200 (CEST) (envelope-from knezour@weboutsourcing.cz) Message-ID: <533D0F7B.1000602@weboutsourcing.cz> Date: Thu, 03 Apr 2014 09:36:27 +0200 From: Ondra Knezour User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: David Chisnall Subject: Re: WDS with a FreeBSD access point References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> <533D0C02.9010303@weboutsourcing.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 07:36:36 -0000 Dne 3.4.2014 9:23, David Chisnall napsal(a): > On 3 Apr 2014, at 08:21, Ondra Knezour > wrote: > >> Dne 3.4.2014 9:05, David Chisnall napsal(a): >>> 'STA and AP VAPs'? Can we go back to assuming that I don't know >>> anything please? >> >> STA - station, basically a client connecting to the access point AP >> - access point VAP - virtual AP, on one hardware device can be >> multiple virtual APs/networks running > > My confusion is from the fact that I'm not sure why I have a VAP - I > was assuming my configuration would have a single wlan device that > would talk to stations and WDS remotes. Is this not the case? As I can recall (it is long time ago I was experimenting with the WiFi on little larger scale), you always create at least one VAP, the ifconfig xxx create wlandev yyy does just that - creates one virtual device xxx on the top of the hw device yyy. So if you want for example several diferent SSIDs, you will create multiple VAPs for them and bridge them together. I am unable to try it in near future to explain it better but hopefully you got the point. -- Ondra Knezour From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 09:23:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 61FA8B4C for ; Thu, 3 Apr 2014 09:23:48 +0000 (UTC) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D4F4FE6 for ; Thu, 3 Apr 2014 09:23:48 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id x3so1513910qcv.26 for ; Thu, 03 Apr 2014 02:23:47 -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=AT7b9kegN80qF5E/941cgjk39Hwz14cs9ml35TDUM/c=; b=pZrchxCBoBpxw4uN/zOHLiaO8BsZ5Z+IH+j/oNtmznds+oyXnFukfjTac2VkwISuwA 9lP6VSs5Xw/ON3k0wV7Zc0OesyM7xks2jQLY5DU0imA5I7DArvDt3G+SKjb8q9/yWbMt 7CwiTXw9cGZK+c9OmocNA0HnyIxvbhhjP92weHHP88OwXkII65sGEPNW+DzmMGDVM8r1 jEzrAJJDWEu9swI3vOxIx6llI+RCfKvcj6b/b/zpLVpehX73XTcxekR+A37xqJTpG4tE JqXxpHC27LOM4oHniePMjAqC1UnpboS75BX/d00Sn7YoUWjjBJ67jpB2BFX1DPlBJxL4 Rd5A== MIME-Version: 1.0 X-Received: by 10.140.42.9 with SMTP id b9mr5654887qga.87.1396517027303; Thu, 03 Apr 2014 02:23:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Thu, 3 Apr 2014 02:23:47 -0700 (PDT) In-Reply-To: References: <533BD60D.9050701@weboutsourcing.cz> <533CD386.80906@weboutsourcing.cz> <533D0C02.9010303@weboutsourcing.cz> Date: Thu, 3 Apr 2014 02:23:47 -0700 X-Google-Sender-Auth: 0N3unBc1Ildgw8ytIhd1zyhVvIc Message-ID: Subject: Re: WDS with a FreeBSD access point From: Adrian Chadd To: David Chisnall Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 09:23:48 -0000 Hi, Ok. It's erm, slightly more and less complicated than that. here goes. (Background reading: http://www.studioreti.it/slide/802-11-Frame_E_C.pdf) Normal traffic between an AP and STA is classified as "three-address" traffic - it has source MAC, destination MAC (ie, the station) and BSSID (ie, the AP.) This is why you can't have multiple MAC addresses on a single station - because there's no separate destination station and destination MAC. They're the same thing. Same as the source (from a STA) - there's no separate addresses. So, in a normal scenario you'll have an AP with a single VAP (virtual access point) interface, in hostap mode. When doing WDS, the traffic going to a repeater AP is not just going to have the destination station, it also needs to know which AP to relay it to. It's called a "four address" frame. So when a master AP -> repeater AP transmission goes on, it sets: * addr1 - destination AP * addr2 - local address * addr3 - destination ethernet address * addr4 - source ethernet address WDS doesn't care if the destination MAC address is a wireless station or a wired station, it's still the same "destination ethernet address" idea. net80211 has special case code that says if the given VAP is configured as a WDS peer or forced to use the 4addr format, it does the above. Now, why are there two (or more) VAPs? Put simply, it's an abstraction thing. net80211 treats the WDS session between a master AP and any slave APs as an associated WDS "station", and it gets a VAP created just for that particular connection. It doesn't _need_ to, but having it create dynamic VAPs (and thus netif entries) has its advantages - it can reuse all of the same machinery as normal associations for doing authentication and association handling; it can be force removed by just ifconfig wlanX destroy; you can get per slave statistics via the normal netstat interface. Ok, so to sam's scripts. They're all assuming "open" (ie, no encryption.) I know this isn't ideal, but please give "open" a go to begin with to establish if it's working or not. I don't know whether one wants to run hostapd on each of the cloned VAPs or not. It _should_ work. But as I said, I've never tried WDS and I have no idea whether wpa_supplicant and hostapd work on creating the association links between devices. Good luck! -a On 3 April 2014 00:23, David Chisnall wrote: > On 3 Apr 2014, at 08:21, Ondra Knezour wrote: > >> Dne 3.4.2014 9:05, David Chisnall napsal(a): >>> 'STA and AP VAPs'? Can we go back to assuming that I don't know anything please? >> >> STA - station, basically a client connecting to the access point >> AP - access point >> VAP - virtual AP, on one hardware device can be multiple virtual >> APs/networks running > > My confusion is from the fact that I'm not sure why I have a VAP - I was assuming my configuration would have a single wlan device that would talk to stations and WDS remotes. Is this not the case? > > David > From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 10:07:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C44FF96A; Thu, 3 Apr 2014 10:07:43 +0000 (UTC) Received: from mx1.pertho.net (87-194-102-137.bethere.co.uk [87.194.102.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "pertho.net", Issuer "pertho.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EDFD69F; Thu, 3 Apr 2014 10:07:42 +0000 (UTC) Received: from syn.pertho.net (syn.pertho.lan [10.0.29.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tom) by syn.pertho.net (Postfix) with ESMTPSA id 69B5C1D449F; Thu, 3 Apr 2014 11:02:09 +0100 (BST) Date: Thu, 3 Apr 2014 11:02:07 +0100 From: Tom Murphy To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140403100207.GA23640@syn.pertho.net> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 10:07:43 -0000 Hi, I'm just wondering if you had any time to look at this? I'm happy to test any patches or diffs. Regards, Tom On Tue, Mar 11, 2014 at 11:03:20AM -0700, Adrian Chadd wrote: > I still don't have any ideas here. I do however want to try hacking > the driver to transmit EAPOL frames at the management rate, and then > ensure the management rate is non-MCS. > > > -a > > > On 28 February 2014 15:14, Adrian Chadd wrote: > > Hi, > > > > the interesting bits: > > > > > > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 3 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 4 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 3 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 4 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 5 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 6 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 5 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 6 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 7 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 8 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 7 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 8 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > > > .. so it's failing to transmit the management frames after association > > - they're being transmitted at MCS0 and the AP is just plain not > > ACKing them. > > > > Now, I don't know why this is. It's trying to transmit the initial > > frame at non-MCS rates, but I have a feeling the multi-rate retry > > table thing is confusing it and it's trying to send it as MCS. So > > maybe the AP doesn't like management frames at MCS rates. > > > > I'll have to think about this a little. > > > > -a > > > > > > On 28 February 2014 15:07, Tom Murphy wrote: > >> I've attached my iwn debug messages to this email starting > >> with the point I tried to associate to the Wifi. > >> > >> Thanks again for looking at this! > >> > >> Kind regards, > >> Tom > >> > >> On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote: > >>> On 26 February 2014 23:52, Alexandr wrote: > >>> > Tom, could you: > >>> > > >>> > 1. compile kernel WITH_IWNDEBUG > >>> > 2. sysctl dev.iwn.0.debug=0x1 > >>> > 3. wlandebug -i wlan0 auth+assoc > >>> > 4. Associate with AP in 11n mode > >>> > 5. Send us appropriate /var/log/messages > >>> > > >>> > Then I try to compare it with my log. > >>> > >>> Please do. I've been trying to track down the source of this "ht just > >>> doesn't work!" but it works fine with all of the Intel NICs I have > >>> here. > >>> > >>> Can someone see if they can find a mtaching NIC online (amazon,ebay?) > >>> Owning one that I can whack in a laptop is likely going ot help things > >>> a lot. > >>> > >>> Thanks, > >>> > >>> > >>> -a From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 23:42:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4094D4E5; Thu, 3 Apr 2014 23:42:09 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE555D44; Thu, 3 Apr 2014 23:42:08 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id a108so2620381qge.3 for ; Thu, 03 Apr 2014 16:42: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=K6DZ7FVrnzgAjpjW+wmwKiNT79YcOT+4dXseFMN/6gM=; b=ZONh1WGJWvTzCrzy1GVkuCH91JlNHBrZINqLc7aXZ4JAcCn7SXRSUz9x+TdRNUkNP5 VQSBuyIwkB3EaDZFhpOIhzSm6mwul/3lqcL5hp1Obly231TTA6IJXxKaTLn+WYlI8m2V sVXpXXT+LLp//pF8luOzlcbDzAwTwSlR0ByZvNWOJTBhb9moIhCSj1NOoAzqubXrW6gv rW5VhjprTFG5LZDnNh7Z7msADAkluYLDPnkQYxf9AfBfnUEtPfIL4qeLYcZtX8CseoNL mQoIsVCpwdqdV06+7G+6uO0npNFLg1y+AS9Tu7pDvQ8QeirpphZCl0lDcQ4L9XRLhsFu epjA== MIME-Version: 1.0 X-Received: by 10.224.25.2 with SMTP id x2mr10785646qab.37.1396568527385; Thu, 03 Apr 2014 16:42:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.143 with HTTP; Thu, 3 Apr 2014 16:42:07 -0700 (PDT) In-Reply-To: <20140403100207.GA23640@syn.pertho.net> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> Date: Thu, 3 Apr 2014 16:42:07 -0700 X-Google-Sender-Auth: b6mDQvQ1DrPqY0ntwG7MZ_680_Q Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Tom Murphy Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Apr 2014 23:42:09 -0000 I've had no time to continue looking at this, I'm sorry. I'm very overworked and I'm not able to be both the net80211, ath and iwn maintainer given how much actual attention they all require. Someone has to step up and take command of the iwn code. -a On 3 April 2014 03:02, Tom Murphy wrote: > Hi, > > I'm just wondering if you had any time to look at this? I'm happy to test > any patches or diffs. > > Regards, > Tom > > On Tue, Mar 11, 2014 at 11:03:20AM -0700, Adrian Chadd wrote: >> I still don't have any ideas here. I do however want to try hacking >> the driver to transmit EAPOL frames at the management rate, and then >> ensure the management rate is non-MCS. >> >> >> -a >> >> >> On 28 February 2014 15:14, Adrian Chadd wrote: >> > Hi, >> > >> > the interesting bits: >> > >> > >> > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 3 len 129 nsegs 2 rate >> > 0002 plcp 0x0000420a >> > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 4 len 129 nsegs 2 rate >> > 0002 plcp 0x0000420a >> > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 3 retries 16 nkill >> > 0 rate 80006902 duration 2815 status 83 >> > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 4 retries 16 nkill >> > 0 rate 80006902 duration 2815 status 83 >> > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 5 len 129 nsegs 2 rate >> > 0002 plcp 0x0000420a >> > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 6 len 129 nsegs 2 rate >> > 0002 plcp 0x0000420a >> > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 5 retries 16 nkill >> > 0 rate 80006902 duration 2815 status 83 >> > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 6 retries 16 nkill >> > 0 rate 80006902 duration 2815 status 83 >> > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 7 len 129 nsegs 2 rate >> > 0002 plcp 0x0000420a >> > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 8 len 129 nsegs 2 rate >> > 0002 plcp 0x0000420a >> > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 7 retries 16 nkill >> > 0 rate 80006902 duration 2815 status 83 >> > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 8 retries 16 nkill >> > 0 rate 80006902 duration 2815 status 83 >> > >> > .. so it's failing to transmit the management frames after association >> > - they're being transmitted at MCS0 and the AP is just plain not >> > ACKing them. >> > >> > Now, I don't know why this is. It's trying to transmit the initial >> > frame at non-MCS rates, but I have a feeling the multi-rate retry >> > table thing is confusing it and it's trying to send it as MCS. So >> > maybe the AP doesn't like management frames at MCS rates. >> > >> > I'll have to think about this a little. >> > >> > -a >> > >> > >> > On 28 February 2014 15:07, Tom Murphy wrote: >> >> I've attached my iwn debug messages to this email starting >> >> with the point I tried to associate to the Wifi. >> >> >> >> Thanks again for looking at this! >> >> >> >> Kind regards, >> >> Tom >> >> >> >> On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote: >> >>> On 26 February 2014 23:52, Alexandr wrote: >> >>> > Tom, could you: >> >>> > >> >>> > 1. compile kernel WITH_IWNDEBUG >> >>> > 2. sysctl dev.iwn.0.debug=0x1 >> >>> > 3. wlandebug -i wlan0 auth+assoc >> >>> > 4. Associate with AP in 11n mode >> >>> > 5. Send us appropriate /var/log/messages >> >>> > >> >>> > Then I try to compare it with my log. >> >>> >> >>> Please do. I've been trying to track down the source of this "ht just >> >>> doesn't work!" but it works fine with all of the Intel NICs I have >> >>> here. >> >>> >> >>> Can someone see if they can find a mtaching NIC online (amazon,ebay?) >> >>> Owning one that I can whack in a laptop is likely going ot help things >> >>> a lot. >> >>> >> >>> Thanks, >> >>> >> >>> >> >>> -a From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 7 11:06:54 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 666ADC5D for ; Mon, 7 Apr 2014 11:06:54 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3577CC19 for ; Mon, 7 Apr 2014 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s37B6sF7071257 for ; Mon, 7 Apr 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s37B6rSi071255 for freebsd-wireless@FreeBSD.org; Mon, 7 Apr 2014 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Apr 2014 11:06:53 GMT Message-Id: <201404071106.s37B6rSi071255@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.17 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, 07 Apr 2014 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/187624 wireless WEP and other ciphers do not work if h/w driver does n o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 193 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 07:17:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2318F16A for ; Tue, 8 Apr 2014 07:17:14 +0000 (UTC) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB3861CF3 for ; Tue, 8 Apr 2014 07:17:13 +0000 (UTC) Received: by mail-qg0-f41.google.com with SMTP id z60so516423qgd.28 for ; Tue, 08 Apr 2014 00:17:13 -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=4QIrPmnOkmqD21dgL6jYZb35zql2yGji4ESnYatK+cQ=; b=yrJSYJHZGIJ4gi4HJf0bviz2bRk6ytE0pul1tzEJ8OTD96OS0GH06ziK+57NJEEEGn 1UD2UE5fBCopGo+rSYG5+85wcJCrZ6WZccE5E364Zm/AjXZktpLHtu8yhJjgFMVGXA/f B98ODsE+FeTkQi0mPnV0/F/y1VaKtr6xhzzBGjXkZJJuTGjxBBfg7iwwDWYPufnqLUx9 qfSGKa99gTjFULniNDCxjoZdnK7Tgy02J4QcpMpZIUy5hhCKehPoohwO5HlF8pJYm485 sePpwmAv83FOCDamiJFY60TWF/FOFkX3OtgoIpAiyox+WnjKmg7V7v3yJrK9MlYSIiYh 0eSw== MIME-Version: 1.0 X-Received: by 10.140.22.197 with SMTP id 63mr2244227qgn.4.1396941433073; Tue, 08 Apr 2014 00:17:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 00:17:13 -0700 (PDT) Date: Tue, 8 Apr 2014 00:17:13 -0700 X-Google-Sender-Auth: ARu8AzoBZHdyud8FCy7HQlHf1S0 Message-ID: Subject: You should totally update to -HEAD to fix some ath(4) hangs From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 07:17:14 -0000 Hi, I've just committed a bunch of things to -HEAD that fix ath(4) hangs in 11n A-MPDU transmission. If you're doing 11n AP stuff then please update and re-test. I'd like someone else to MFC the commits to stable/10 so people there can benefit from it. Thanks, -a From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 10:47:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A74564F7; Tue, 8 Apr 2014 10:47:18 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 270641160; Tue, 8 Apr 2014 10:47:17 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.8/8.14.8) with ESMTP id s38AkoRc033330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 8 Apr 2014 14:46:50 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.8/8.14.8/Submit) id s38AkoVo033329; Tue, 8 Apr 2014 14:46:50 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 8 Apr 2014 14:46:50 +0400 From: Gleb Smirnoff To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140408104650.GN44326@FreeBSD.org> References: <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 10:47:18 -0000 Adrian, On Thu, Apr 03, 2014 at 04:42:07PM -0700, Adrian Chadd wrote: A> I've had no time to continue looking at this, I'm sorry. A> A> I'm very overworked and I'm not able to be both the net80211, ath and A> iwn maintainer given how much actual attention they all require. A> Someone has to step up and take command of the iwn code. I must admit that right now iwn(4) is in much worse shape than it was a year ago. :( And the fact you abandon it in current shape is very unpleasant. I started to use laptops with iwn(4) about 3 years ago, and I always track head on my laptop. My connectivity was perfect for the first two years. But for the last year the situation is getting worse and worse. Since you were actively hacking on iwn(4), I decided to keep calm an wait for you to achieve your goals, only then complain. Now you abandon it. What hurts me right now: - The overall network performance is extremely bad. Doing an scp(1) from/to a box, that is on the same LAN I am achieving 30 Kb/s with long stalls. For the last couple of months I am moving larger files to my laptop with help of a USB memstick. - When I actually do run bulk upload/download via iwn(4), the entire office WiFi goes almost dead. My colleagues can't skype while I am copying a kernel file from my laptop to other close box, and copying lasts more than a minute (see above). Actually, not only WiFi is deafened by current iwn(4), it looks like entire 2.4GHz band is noised, because my wireless mouse gets very laggy and lossy during any bulk activity via iwn(4). - Even tiny traffic volume experiences packet loss. Right now I'm typing this via ssh, and sometimes I feel packet loss in the session. Note that my hardware haven't changed at all during last year. Only version of FreeBSD. Right now I have strong desire to update my sources of dev/iwn to early 2013, get it compilable and work with that. -- Totus tuus, Glebius. From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 16:12:50 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95732295 for ; Tue, 8 Apr 2014 16:12:50 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55B3D1395 for ; Tue, 8 Apr 2014 16:12:50 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id j7so1145163qaq.22 for ; Tue, 08 Apr 2014 09:12:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=kiRMQOXRwaWXf9h6YExvI/nUvRkHKLApMTGe/E5LksM=; b=KcMD9QFvP3Gj7ol7pEagzbSoSr3bJJ7tQJm791zGzcvQM1p/lW789VYZw2eF8WlWE2 eapzDxOPtkK32KgkOnKv9MZrU0r5oNrBhkZ8u/nUNnc3pcO+SMiPr98p6KxDH1LBRI3d zkYnYFblxNYHE82YfHhUu6ZTbWt+dLnZ75A40ILpwmrxkqnzkndW2g+GeZ249ZK5G2C+ QZZ+KFilGKAvNbD2EGupDRh3wrtLEYQs6QMCJus2wJ858goblixn0clil8h/Wc67stDW Bc+goFXoT3BJ4WNSoMRw6r9TM6MprHwX4QgsYSspZmhy0AHt8P+Dcy7VVXlpwYy49iaS JCuQ== X-Received: by 10.140.34.46 with SMTP id k43mr5344257qgk.63.1396973569370; Tue, 08 Apr 2014 09:12:49 -0700 (PDT) Received: from lpnix002.local ([66.55.134.195]) by mx.google.com with ESMTPSA id u59sm3277742qga.8.2014.04.08.09.12.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 09:12:48 -0700 (PDT) Message-ID: <53441FFF.3090308@gmail.com> Date: Tue, 08 Apr 2014 12:12:47 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Atheros AR9565 X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 16:12:50 -0000 I have a Toshiba Satellite S55-A5169 This specific one: http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For it to work I have to change the SATA Controller Mode in the BIOS from "AHCI" to "Compatibility". I don't know if this information helps, and it's the only AHCI setting I can tweak. Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 16:37:23 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 39AE38EC; Tue, 8 Apr 2014 16:37:23 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C58FA15EE; Tue, 8 Apr 2014 16:37:22 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id k15so1232978qaq.29 for ; Tue, 08 Apr 2014 09:37: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=A5O8APOrrncwkDyWbbtEIrq87wF2VJ/GPlq+0kaHyJ4=; b=MR2O8BKFPawNbHtzI0MiVgZ2jtzIEsU8UiRjQqsSgRInSHO1IvRGCW6ZW6zpsRQdyX PToHarg71VfUittyb0g3E7TIze3nTILOmR7DF1iGg0gkcRZP4dbas9kQcTHc3UhISdTD hes0xOVwGnVwcTM0ge/qTBwfD/6JQy9WxUunB5LB5NxhbECBqCvh+kam20J5zUQ0yT6i MpMXQvc1AsQxFZJCRdW+ECn2j40KHNYKNIMMPE2bv35Hz+HKhNnY3rn2qjvuomXsYG2S B6MYgnQc+BtBY6tGQDA9/7j3PKoxqynNyDT47KPC167Q4Gg9ZN1zsnlFcA4UrRp+KqwL sReg== MIME-Version: 1.0 X-Received: by 10.140.41.200 with SMTP id z66mr2153691qgz.102.1396975041962; Tue, 08 Apr 2014 09:37:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 09:37:21 -0700 (PDT) In-Reply-To: <20140408104650.GN44326@FreeBSD.org> References: <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> <20140408104650.GN44326@FreeBSD.org> Date: Tue, 8 Apr 2014 09:37:21 -0700 X-Google-Sender-Auth: hwVurPO87c43x09vfpERllJlg7I Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Gleb Smirnoff Content-Type: text/plain; charset=ISO-8859-1 Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 16:37:23 -0000 Hi, Which hardware is it? The driver hasn't changed _that_ much since 2013. I'd really like some help in figuring out which commit(s) broke the driver for you. Would you mind bisecting the driver from HEAD from 2013 to now and tell me when the first break was? I'm happy to fix bugs, but I can only work on making it better for me. I've not had very much feedback from people (except "yay it works better" and "it's the same") so this is news to me. -a From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 18:23:01 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F7E9692 for ; Tue, 8 Apr 2014 18:23:01 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01805121F for ; Tue, 8 Apr 2014 18:23:00 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id q108so1162440qgd.38 for ; Tue, 08 Apr 2014 11:23:00 -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=ZNLEjNQkCQ/8WoVaApgThC1HgCOzjxiOCTgr8QW+Rj0=; b=K9CbRFAGpHHhD8E375wkQs1yfUpDa14flnigUUalwPiLCqBpHx+97gyCwcwbrKdrqy Nw2MhsMUvEz/PTcCv7JXUvV9pR299bzhRPQ3wxbYha7z6hINnvgWf9QBrVFUdm6sj6Y2 7A7YmymK+WcdgOn76tiyTeHYGstt1ZY/+3i2lbNpGs3F28RfO1YRSsbcBQneIrktOG96 62uiKmYvNjrLnCuef1tuZlQpjxNDB+6cYsETTwdpbNggVdCzRNpzT8DR8O2Bd2qe8QL7 KSWK/Objb6A0wL65Q2jGK2SEWvjL/0fWe3KTCkPiXU0KW10V09OwMlx3oCQ6Cn8sqM1B a8Cg== MIME-Version: 1.0 X-Received: by 10.140.41.200 with SMTP id z66mr2873135qgz.102.1396981380183; Tue, 08 Apr 2014 11:23:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 11:23:00 -0700 (PDT) In-Reply-To: <53441FFF.3090308@gmail.com> References: <53441FFF.3090308@gmail.com> Date: Tue, 8 Apr 2014 11:23:00 -0700 X-Google-Sender-Auth: kytEx1LZgsZmqjD71Jh650luQ4E Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 18:23:01 -0000 It should work fine on -10 and HEAD. Is it not working fine? -a On 8 April 2014 09:12, tzoi516 wrote: > I have a Toshiba Satellite S55-A5169 > This specific one: > http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) > > It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For > it to work I have to change the SATA Controller Mode in the BIOS from > "AHCI" to "Compatibility". I don't know if this information helps, and > it's the only AHCI setting I can tweak. > > Mike > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 18:37:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 726ACCE9; Tue, 8 Apr 2014 18:37:19 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EF401333; Tue, 8 Apr 2014 18:37:19 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id q108so1211606qgd.10 for ; Tue, 08 Apr 2014 11:37:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=vnR4zywhXqjjIoF63rCDZBFPFpApVjexkkfIp+sC61I=; b=OUQhqqcmt5nlur+0eY+WEQGFYce5L3/HZUGdEjK/y9ShfF3X+wHyOWrtTgnIXBaUV9 3TnU7mwGlbHGOq3IVBLYy7hKwwJ0eWbuGQJ9pi/2VbMkrYvUjMiau7+EYZL6iBmOHGeM eumXKFdUkY/bbBhwHdSc06xkUddn7q86fxRYOdClvkHDGkfcxSqrrQwdXOkp2onqnjOk ervP0riLJmIQ7f89RR3aiBDY3LQ7yGmFHpSXpVzCHIKz/kcHTiKA6EjSmNA2+QSz2fky oOFmfbvihxiYNXz+ia+naBZLB+u3QfAmz018RSqSRV1VXzbTHWr1d+aPvUXuWpPsQMV+ MoSQ== X-Received: by 10.224.36.194 with SMTP id u2mr6492616qad.73.1396982238220; Tue, 08 Apr 2014 11:37:18 -0700 (PDT) Received: from lpnix002.local ([209.222.7.234]) by mx.google.com with ESMTPSA id b46sm3746785qge.7.2014.04.08.11.37.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 11:37:17 -0700 (PDT) Message-ID: <534441DC.7050800@gmail.com> Date: Tue, 08 Apr 2014 14:37:16 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53441FFF.3090308@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 18:37:19 -0000 On 04/08/14 14:23, Adrian Chadd wrote: > It should work fine on -10 and HEAD. Is it not working fine? > > > -a > > > On 8 April 2014 09:12, tzoi516 wrote: >> I have a Toshiba Satellite S55-A5169 >> This specific one: >> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >> >> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >> it to work I have to change the SATA Controller Mode in the BIOS from >> "AHCI" to "Compatibility". I don't know if this information helps, and >> it's the only AHCI setting I can tweak. >> >> Mike >> _______________________________________________ >> 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" With SATA controller mode set to Compatibility then it works, but a little wonky at startup - sometimes I'll have to run wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. With SATA controller mode set to AHCI then I can ifconfig wlan0 list scan and see available networks but I can't connect to any except for unprotected networks. I'm currently running FreeBSD 10.0-STABLE Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 18:38:07 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 948CCDDE for ; Tue, 8 Apr 2014 18:38:07 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55AA0133A for ; Tue, 8 Apr 2014 18:38:07 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id i8so1571082qcq.3 for ; Tue, 08 Apr 2014 11:38:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=noeMlHB0VbXLFQVYBjT3azSElifKcajvLVQ4R6GCO3Y=; b=qiYYmbZsICbmJInaqyyFCDpM7hfvgxE+sMkefpUcS+o2t6y4ghCO+VECVZgrV4dkYV UZUnt5NR8QQ5Fg5gpVFSilb3OCpkR89NEK5IW2HQjDGh+IcbQZdbnxET5LD+Cfa/0l9W IGQv6ibo8lcjh852I0bXkv2wz77S96edRATdcsP+5LaoMtERsEguaH4jtm3aOA+3uIOD V0Jo1/Q4i/0wvd93sbyLwplI0HaGNnoNEqNI5HAB8rrYDbnAuaShqcns1Y2xGofFYGYA vjOVi+Z0lwSG+INYcPrccZe9L1X1q56Z4AwElElkNNpciR9zvnp4nAyLRG8ot3j5vQ7b oPeQ== MIME-Version: 1.0 X-Received: by 10.140.109.100 with SMTP id k91mr6529522qgf.12.1396982286275; Tue, 08 Apr 2014 11:38:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 11:38:06 -0700 (PDT) In-Reply-To: <534441DC.7050800@gmail.com> References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> Date: Tue, 8 Apr 2014 11:38:06 -0700 X-Google-Sender-Auth: YzmnTMhbi3V77lVjfhW45OOZB-k Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 18:38:07 -0000 Ah. Can you post the buffer errors you're seeing? -a On 8 April 2014 11:37, tzoi516 wrote: > On 04/08/14 14:23, Adrian Chadd wrote: >> It should work fine on -10 and HEAD. Is it not working fine? >> >> >> -a >> >> >> On 8 April 2014 09:12, tzoi516 wrote: >>> I have a Toshiba Satellite S55-A5169 >>> This specific one: >>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>> >>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>> it to work I have to change the SATA Controller Mode in the BIOS from >>> "AHCI" to "Compatibility". I don't know if this information helps, and >>> it's the only AHCI setting I can tweak. >>> >>> Mike >>> _______________________________________________ >>> 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" > With SATA controller mode set to Compatibility then it works, but a > little wonky at startup - sometimes I'll have to run wpa_supplicant -i > wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. > With SATA controller mode set to AHCI then I can ifconfig wlan0 list > scan and see available networks but I can't connect to any except for > unprotected networks. > > I'm currently running FreeBSD 10.0-STABLE > > Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 18:54:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5D3B964; Tue, 8 Apr 2014 18:54:30 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8265715CA; Tue, 8 Apr 2014 18:54:30 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id i8so1567131qcq.37 for ; Tue, 08 Apr 2014 11:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ixKyo+pm37AGc2ToAQG9ncd8cpNmNZfwvB2C7jvW5xc=; b=CfRawfbLjFARjkeTtUSm2WGJwgYqSSeUbApR7C5SvySzjNPNuFpASMe57emnZC7ERz wrGm8HRCxU/50zei/+y0Fw4brRoPtJdPwqEWhzcaer5jSXRYcgVhoZCS8BOO4Cf8eeNP zZC2HdIQeV1I6si3GgHkBzUEEBMKY0gVr2RUV3terWU/TYAcfDDkHRQqYtoyLpG+XJIn eyTwHewwNuzaUsOFRhYTYFqech8eGsOiGTvNJN2P8/wCbVxtXFDQX/I6jfaVwmEK54k7 xgY4ZHGmLqYo4uHpNL52/F9lqpBnIvz/cdXKQQE5Qs0M9weUgyVk2En9Tmosb1Dt7T4k h3pw== X-Received: by 10.229.54.201 with SMTP id r9mr6985080qcg.6.1396983269686; Tue, 08 Apr 2014 11:54:29 -0700 (PDT) Received: from lpnix002.local ([209.222.7.234]) by mx.google.com with ESMTPSA id s111sm3791009qge.19.2014.04.08.11.54.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 11:54:29 -0700 (PDT) Message-ID: <534445E3.6040600@gmail.com> Date: Tue, 08 Apr 2014 14:54:27 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 18:54:31 -0000 dhclient[1014]: send_packet: No buffer space available - is one of them, the other has occurred during portmaster installs. I have two FreeBSD laptops side-by-side with the same settings to the same router and the Intel (iwn0, with FreeBSD 10.0-RELEASE) isn't giving me any errors. Mike On 04/08/14 14:38, Adrian Chadd wrote: > Ah. Can you post the buffer errors you're seeing? > > > -a > > > On 8 April 2014 11:37, tzoi516 wrote: >> On 04/08/14 14:23, Adrian Chadd wrote: >>> It should work fine on -10 and HEAD. Is it not working fine? >>> >>> >>> -a >>> >>> >>> On 8 April 2014 09:12, tzoi516 wrote: >>>> I have a Toshiba Satellite S55-A5169 >>>> This specific one: >>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>> >>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>> it's the only AHCI setting I can tweak. >>>> >>>> Mike >>>> _______________________________________________ >>>> 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" >> With SATA controller mode set to Compatibility then it works, but a >> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >> scan and see available networks but I can't connect to any except for >> unprotected networks. >> >> I'm currently running FreeBSD 10.0-STABLE >> >> Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 19:21:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B22CB8F6; Tue, 8 Apr 2014 19:21:27 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E0A318E6; Tue, 8 Apr 2014 19:21:27 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id i8so1640103qcq.3 for ; Tue, 08 Apr 2014 12:21:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=J6w5DfEgfG/svknFrBvjM+hmAV4LxU2Nh4cgRbZKPhQ=; b=wc1sA7AQXwziVgguH4ej6Wx9FL+MZPRGPqX5GJLibc9og0JVT/61y1HW1aqNNlD/7m ubYPquyBvrNHECWYKBtz+pDU0wLpgMrHGLp9+TPY3W9PcqXU6+oYGj8f/0dvXgJyMnHi ECPWlHmrd9wNPCGvIQ7wSdzBM4iuc36So9VgXGYbQlmJLWUmMzXYTxadHUVSFnLFPm9g uN6tj/60Xpu+cmmQR+X2b672t+uP301NfNOXVyhcdOXk7MW6Un/Ubv3eKb7VyXbRO/u3 MSN25RhBwVvlxmYfJRSYMrF8C6Kb0b+qrb+bzlGt6OldV3d+7aUgxN+ESApUaM38ILVC lNDA== X-Received: by 10.140.80.112 with SMTP id b103mr6689012qgd.98.1396984886404; Tue, 08 Apr 2014 12:21:26 -0700 (PDT) Received: from lpnix002.local ([209.222.7.234]) by mx.google.com with ESMTPSA id c61sm3886520qgf.15.2014.04.08.12.21.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 12:21:25 -0700 (PDT) Message-ID: <53444C34.5060709@gmail.com> Date: Tue, 08 Apr 2014 15:21:24 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 19:21:27 -0000 Sorry for another email, the errors are sporadic. I'm trying to find the ioctl errors that I get on shutdown. These are after logging in: ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping dhclient[1001]: send_packet: Invalid argument dhclient[1001]: send_packet: No buffer space available ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping dhclient[1001]: send_packet: No buffer space available dhclient[1001]: send_packet: Invalid argument dhclient[1001]: send_packet: Network is down Mike On 04/08/14 14:38, Adrian Chadd wrote: > Ah. Can you post the buffer errors you're seeing? > > > -a > > > On 8 April 2014 11:37, tzoi516 wrote: >> On 04/08/14 14:23, Adrian Chadd wrote: >>> It should work fine on -10 and HEAD. Is it not working fine? >>> >>> >>> -a >>> >>> >>> On 8 April 2014 09:12, tzoi516 wrote: >>>> I have a Toshiba Satellite S55-A5169 >>>> This specific one: >>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>> >>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>> it's the only AHCI setting I can tweak. >>>> >>>> Mike >>>> _______________________________________________ >>>> 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" >> With SATA controller mode set to Compatibility then it works, but a >> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >> scan and see available networks but I can't connect to any except for >> unprotected networks. >> >> I'm currently running FreeBSD 10.0-STABLE >> >> Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 20:03:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF77C533 for ; Tue, 8 Apr 2014 20:03:13 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FB3E1CEB for ; Tue, 8 Apr 2014 20:03:13 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id r5so1691119qcx.18 for ; Tue, 08 Apr 2014 13:03:12 -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=fwGuBd/hcNv68wnHgFa/Nu0FgKSdONJk9cPgKOnht/8=; b=AXxrtwyPXp8A5F6umT4ZPBbLTUozUlhrkdnHXy+luOkSY4fbo9Wjqa5IY4ECCEH4Da njoF6sBVe0c+GVDul7BZ0dd98dykKXoRKYZFYxs2uz6LmqM2IC8xaXEypYsSqyCWUL7a 1cElCCMU5sVBTcpNk29UTw94tzPFzhpumqZDam4Pj4XqpRNm7pW4YqdkG0XB8uJ3+98Y GQw1C3pWzTspWVIzspTL5kOeqxpcoJEdQ518N32YUmoSumf20xK6qqGpbpy0sIl2Tj3x 1odru8WENaLEJKej+//IGj7vTx9W5AuHHoLp/ikrAyPce191+N4kmVEja2/0zkxvLLTx xsIg== MIME-Version: 1.0 X-Received: by 10.140.38.149 with SMTP id t21mr6993235qgt.24.1396987392686; Tue, 08 Apr 2014 13:03:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 13:03:12 -0700 (PDT) In-Reply-To: <53444C34.5060709@gmail.com> References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> <53444C34.5060709@gmail.com> Date: Tue, 8 Apr 2014 13:03:12 -0700 X-Google-Sender-Auth: PpcH1Jlcc9X38qya2GZK_z8zc9c Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 20:03:13 -0000 Right. It sounds like it's not associated. Try wlandebug +assoc and then run wpa_supplicant -a On 8 April 2014 12:21, tzoi516 wrote: > Sorry for another email, the errors are sporadic. I'm trying to find the > ioctl errors that I get on shutdown. > These are after logging in: > > ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping > dhclient[1001]: send_packet: Invalid argument > dhclient[1001]: send_packet: No buffer space available > ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping > dhclient[1001]: send_packet: No buffer space available > dhclient[1001]: send_packet: Invalid argument > dhclient[1001]: send_packet: Network is down > > Mike > > On 04/08/14 14:38, Adrian Chadd wrote: >> Ah. Can you post the buffer errors you're seeing? >> >> >> -a >> >> >> On 8 April 2014 11:37, tzoi516 wrote: >>> On 04/08/14 14:23, Adrian Chadd wrote: >>>> It should work fine on -10 and HEAD. Is it not working fine? >>>> >>>> >>>> -a >>>> >>>> >>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>> I have a Toshiba Satellite S55-A5169 >>>>> This specific one: >>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>> >>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>> it's the only AHCI setting I can tweak. >>>>> >>>>> Mike >>>>> _______________________________________________ >>>>> 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" >>> With SATA controller mode set to Compatibility then it works, but a >>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>> scan and see available networks but I can't connect to any except for >>> unprotected networks. >>> >>> I'm currently running FreeBSD 10.0-STABLE >>> >>> Mike > From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 20:08:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 635B15A6; Tue, 8 Apr 2014 20:08:18 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E2E61D1C; Tue, 8 Apr 2014 20:08:17 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id 63so1199533qgz.19 for ; Tue, 08 Apr 2014 13:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=bVOa7BS0o9WVl7aVy2gamH451kTb+9AatS5BUR4X1lg=; b=ZYSeZtO7MU0nfQ/6uBOm2LhwaN68eX8Vw3hyDEAT5kVi9UASXwkTotOi50JlxDvQvj QP4GqFYKhufAGuc3zUoJKWb+R+O+6UjVudods1VB29XgdqgyhpW8pmmsVAVhxHudvBAc xPw8xAZyr6bWmxo4QcXnprowojDkG2yn8oKBzThK9x+BoXRXqXv2q+exS5xyj56r2csp tnR7MPkX65+i3+O9/4KWnW9LYH/jxP6V6xeEpK2pMGhoJlHwYgpF2k35PnnaccWwE4et GM36ummkxB28EqsvgjFD4vh4a3AxbP6/hHQS3tRhr68/E6t0RdxKkzwP9AuhTaIUoc5P LW9g== X-Received: by 10.224.167.12 with SMTP id o12mr7290159qay.77.1396987697176; Tue, 08 Apr 2014 13:08:17 -0700 (PDT) Received: from lpnix002.local ([209.222.7.234]) by mx.google.com with ESMTPSA id w2sm5917089qar.21.2014.04.08.13.08.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 13:08:16 -0700 (PDT) Message-ID: <5344572F.3060604@gmail.com> Date: Tue, 08 Apr 2014 16:08:15 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> <53444C34.5060709@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 20:08:18 -0000 OK. The odd part is after I received those errors I did ifconfig and saw the network was up. ping google.com with 75% packet loss. Pings now are around 35.585 ms with 50.0% packet loss. FreeBSD 10.0-RELEASE system with Intel (iwn0) approximately 80.833 ms with 0% packet loss. Mike On 04/08/14 16:03, Adrian Chadd wrote: > Right. It sounds like it's not associated. > > Try wlandebug +assoc and then run wpa_supplicant > > > -a > > > On 8 April 2014 12:21, tzoi516 wrote: >> Sorry for another email, the errors are sporadic. I'm trying to find the >> ioctl errors that I get on shutdown. >> These are after logging in: >> >> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >> dhclient[1001]: send_packet: Invalid argument >> dhclient[1001]: send_packet: No buffer space available >> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >> dhclient[1001]: send_packet: No buffer space available >> dhclient[1001]: send_packet: Invalid argument >> dhclient[1001]: send_packet: Network is down >> >> Mike >> >> On 04/08/14 14:38, Adrian Chadd wrote: >>> Ah. Can you post the buffer errors you're seeing? >>> >>> >>> -a >>> >>> >>> On 8 April 2014 11:37, tzoi516 wrote: >>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>> I have a Toshiba Satellite S55-A5169 >>>>>> This specific one: >>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>> >>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>> it's the only AHCI setting I can tweak. >>>>>> >>>>>> Mike >>>>>> _______________________________________________ >>>>>> 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" >>>> With SATA controller mode set to Compatibility then it works, but a >>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>> scan and see available networks but I can't connect to any except for >>>> unprotected networks. >>>> >>>> I'm currently running FreeBSD 10.0-STABLE >>>> >>>> Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 20:33:11 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4D3E129; Tue, 8 Apr 2014 20:33:11 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F9FD1102; Tue, 8 Apr 2014 20:33:11 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id m20so1747177qcx.35 for ; Tue, 08 Apr 2014 13:33:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=0LNYRAbnyN7ZfQC1TC/IlHe3S8giN536ivA2gL+kXOA=; b=xsKFabcayMk7Phl5u4Vigt+rANCpXfmV/wQziZPTAhh4WTTonQmxpic77wYAeQpbut cLU301t1io8iYFwsuguYmTYrJbur6uLAPOAm4XHrXBMPYvOzQ10Zu/LffN8ZfH83WbQi wOHtuZev6H9XGy8m9Z1L2BKpUsYl7PS1PzERVekzs4uCRiwGoO535zlKC4r/VMLx5EKQ G1nCLaBrXnyLWERZOSak5MTT00J6PWimtj6dB3OsBtFzj/YjpB+o2PoGBDSe90phnS57 fOLw5akhOgJCrxe3+n7Dc6nFdTvwp1hzHjoZOkwHKjdrgUUW4PmFTDQeWo2YVzXn+Y39 5aQA== X-Received: by 10.224.79.12 with SMTP id n12mr7527480qak.13.1396989190680; Tue, 08 Apr 2014 13:33:10 -0700 (PDT) Received: from lpnix002.local ([209.222.7.234]) by mx.google.com with ESMTPSA id b4sm6028186qaw.26.2014.04.08.13.33.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 13:33:10 -0700 (PDT) Message-ID: <53445D04.5040706@gmail.com> Date: Tue, 08 Apr 2014 16:33:08 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> <53444C34.5060709@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 20:33:11 -0000 This is what I have now, after 5 attempts, and at 41.2% packet loss: ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping wlan0: Trying to associate with (hardware ID) (SSID='Base SSID' freq=1234 MHz wlan0: [hardware ID] station assoc via MLME wlan0: [hardware ID] assoc success at aid 3: long preamble, short slot time, protection wlan0: Associated with (hardware ID) dhclient[3172]: send_packet: No buffer space available wlan0: WPA: Key negotiation completed with (hardware ID) [PTK=TKIP GTK=TKIP] Previous attempts had the following errors constantly cycling (having to type all of it right now): wlan0: link state changed to UP dhclient[1170]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 dhclient[1170]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 dhclient[1170]: wlan0 link state up -> down wlan0: link state changed to DOWN wlan0: [hardware ID] station assoc via MLME wlan0: [hardware ID] assoc success at aid 3: long preamble, short slot time, protection wlan0: link state changed to UP On 04/08/14 16:03, Adrian Chadd wrote: > Right. It sounds like it's not associated. > > Try wlandebug +assoc and then run wpa_supplicant > > > -a > > > On 8 April 2014 12:21, tzoi516 wrote: >> Sorry for another email, the errors are sporadic. I'm trying to find the >> ioctl errors that I get on shutdown. >> These are after logging in: >> >> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >> dhclient[1001]: send_packet: Invalid argument >> dhclient[1001]: send_packet: No buffer space available >> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >> dhclient[1001]: send_packet: No buffer space available >> dhclient[1001]: send_packet: Invalid argument >> dhclient[1001]: send_packet: Network is down >> >> Mike >> >> On 04/08/14 14:38, Adrian Chadd wrote: >>> Ah. Can you post the buffer errors you're seeing? >>> >>> >>> -a >>> >>> >>> On 8 April 2014 11:37, tzoi516 wrote: >>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>> I have a Toshiba Satellite S55-A5169 >>>>>> This specific one: >>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>> >>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>> it's the only AHCI setting I can tweak. >>>>>> >>>>>> Mike >>>>>> _______________________________________________ >>>>>> 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" >>>> With SATA controller mode set to Compatibility then it works, but a >>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>> scan and see available networks but I can't connect to any except for >>>> unprotected networks. >>>> >>>> I'm currently running FreeBSD 10.0-STABLE >>>> >>>> Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 20:38:20 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7739929F; Tue, 8 Apr 2014 20:38:20 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EA131157; Tue, 8 Apr 2014 20:38:20 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so1392646qgd.29 for ; Tue, 08 Apr 2014 13:38:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=MTHDQEy7BaOp+7nqKmZc+IHo/Mk1gIo/rPpfRVi4mBo=; b=EBgK17HJuawR37gznvVuPVcmlS3ccBzxU1Pt72iTjaj/nwjQO+zUXy3yrXMV3gkwBk Q10QQyvjMuiXz3zD0NdoFHkc7nlHDf4kVItL0LB/PsgASw9LqW7YIE6nsFK7FG2zPUtY zlLxNBDkoB7laMR5RtQCz0TLtjkZ3hH+mAcBlUBk3XTXbY+kpM7zpPwa4dk8P4N5FBRv 0ck+CxDs42PPwuQhYOqBa5pNed1U5wOd0KT1c0iLhVYgI+Q3H0wqxH2bqNNfYOVcRphD uNEpYWwbWH1XgaQkszCvzbI/p46Oo3sRL3IB7baX7y+r3gpocO4ADxkmjNYb170Xa2rQ VzhA== X-Received: by 10.224.11.132 with SMTP id t4mr7759045qat.4.1396989499242; Tue, 08 Apr 2014 13:38:19 -0700 (PDT) Received: from lpnix002.local ([209.222.7.234]) by mx.google.com with ESMTPSA id d30sm4150404qga.9.2014.04.08.13.38.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 13:38:18 -0700 (PDT) Message-ID: <53445E39.7080706@gmail.com> Date: Tue, 08 Apr 2014 16:38:17 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> <53444C34.5060709@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 20:38:20 -0000 OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 up I received a ton of these: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? received those about 20 times then this: ath0: ath_edma_recv_proc_queue: Q1: NULL bf? And now the top 2 are slowly scrolling. Mike On 04/08/14 16:03, Adrian Chadd wrote: > Right. It sounds like it's not associated. > > Try wlandebug +assoc and then run wpa_supplicant > > > -a > > > On 8 April 2014 12:21, tzoi516 wrote: >> Sorry for another email, the errors are sporadic. I'm trying to find the >> ioctl errors that I get on shutdown. >> These are after logging in: >> >> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >> dhclient[1001]: send_packet: Invalid argument >> dhclient[1001]: send_packet: No buffer space available >> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >> dhclient[1001]: send_packet: No buffer space available >> dhclient[1001]: send_packet: Invalid argument >> dhclient[1001]: send_packet: Network is down >> >> Mike >> >> On 04/08/14 14:38, Adrian Chadd wrote: >>> Ah. Can you post the buffer errors you're seeing? >>> >>> >>> -a >>> >>> >>> On 8 April 2014 11:37, tzoi516 wrote: >>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>> I have a Toshiba Satellite S55-A5169 >>>>>> This specific one: >>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>> >>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>> it's the only AHCI setting I can tweak. >>>>>> >>>>>> Mike >>>>>> _______________________________________________ >>>>>> 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" >>>> With SATA controller mode set to Compatibility then it works, but a >>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>> scan and see available networks but I can't connect to any except for >>>> unprotected networks. >>>> >>>> I'm currently running FreeBSD 10.0-STABLE >>>> >>>> Mike From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 8 22:29:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D061467E for ; Tue, 8 Apr 2014 22:29:12 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F5461CD5 for ; Tue, 8 Apr 2014 22:29:12 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id i8so1910949qcq.31 for ; Tue, 08 Apr 2014 15:29:11 -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=xnkGbdRV9rPfoDSupyT+9biA7mPFeAnFTOuk9N52jVU=; b=G+rY0E5eDj6crI9k20XN2+rZP2QQfdsbfVN03ZQtlQzBsIcZEVSZPdL5z000XHnmjr MNjibataXoi96XOXR4iMMJoikfSQS5RSsUJpR4KxXqK13skGjQ3Nin/ePsL90ihHczDq JY9acCSTO0TzMJWFVBBliv2oYvfNh0+qG+xEGJRiaLRvk33RR8aZu7OBiviMtenTzKyy XIw8YxLFjvuFEEv4m+REL4N624fsIcqym/oQiD5Vm2m08qeWMyHC1fv3isI3b8J1rCv8 Z3j+aLsxtkX9E/DiI1jaNz+La1xAblLr79I8pOAWYV78m9DTUOE7xh1P6udoLH6zYkXj RH4Q== MIME-Version: 1.0 X-Received: by 10.140.41.200 with SMTP id z66mr4270189qgz.102.1396996151752; Tue, 08 Apr 2014 15:29:11 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 15:29:11 -0700 (PDT) In-Reply-To: <53445E39.7080706@gmail.com> References: <53441FFF.3090308@gmail.com> <534441DC.7050800@gmail.com> <53444C34.5060709@gmail.com> <53445E39.7080706@gmail.com> Date: Tue, 8 Apr 2014 15:29:11 -0700 X-Google-Sender-Auth: j-BE70DJTF4ftFS1zJBityKFELU Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Apr 2014 22:29:13 -0000 hi, ok. Can you please do a pciconf -lv and attach it here? Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. -a On 8 April 2014 13:38, tzoi516 wrote: > OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 > up I received a ton of these: > > ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? > > received those about 20 times then this: > > ath0: ath_edma_recv_proc_queue: Q1: NULL bf? > > And now the top 2 are slowly scrolling. > > Mike > > > On 04/08/14 16:03, Adrian Chadd wrote: >> Right. It sounds like it's not associated. >> >> Try wlandebug +assoc and then run wpa_supplicant >> >> >> -a >> >> >> On 8 April 2014 12:21, tzoi516 wrote: >>> Sorry for another email, the errors are sporadic. I'm trying to find the >>> ioctl errors that I get on shutdown. >>> These are after logging in: >>> >>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>> dhclient[1001]: send_packet: Invalid argument >>> dhclient[1001]: send_packet: No buffer space available >>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>> dhclient[1001]: send_packet: No buffer space available >>> dhclient[1001]: send_packet: Invalid argument >>> dhclient[1001]: send_packet: Network is down >>> >>> Mike >>> >>> On 04/08/14 14:38, Adrian Chadd wrote: >>>> Ah. Can you post the buffer errors you're seeing? >>>> >>>> >>>> -a >>>> >>>> >>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>> This specific one: >>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>> >>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>> it's the only AHCI setting I can tweak. >>>>>>> >>>>>>> Mike >>>>>>> _______________________________________________ >>>>>>> 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" >>>>> With SATA controller mode set to Compatibility then it works, but a >>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>> scan and see available networks but I can't connect to any except for >>>>> unprotected networks. >>>>> >>>>> I'm currently running FreeBSD 10.0-STABLE >>>>> >>>>> Mike > From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 01:18:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4921855 for ; Wed, 9 Apr 2014 01:18:48 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFC4E12E4 for ; Wed, 9 Apr 2014 01:18:48 +0000 (UTC) Received: from [192.168.1.101] (c-24-6-177-88.hsd1.ca.comcast.net [24.6.177.88]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 251AC1929A9; Wed, 9 Apr 2014 01:18:41 +0000 (UTC) Subject: Re: iwn0 hangs randomly when starting the machine From: Sean Bruno To: Erich Dollansky In-Reply-To: <20140331073054.5d7642d6@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-/w1DVPFumOmXG8PLLwvi" Date: Tue, 08 Apr 2014 18:18:40 -0700 Message-ID: <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> 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.17 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: Wed, 09 Apr 2014 01:18:49 -0000 --=-/w1DVPFumOmXG8PLLwvi Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2014-03-31 at 07:30 +0800, Erich Dollansky wrote: > Hi, >=20 > since I upgraded to r263767, I have the following problem: >=20 > Wireless does not start all the while. When it does not start, it hangs > then forever. wpa_supplicant's state in top is then '-'. If I start > wpa_supplicant by hand, it will hang and it cannot be stopped by > control C. The light indicating that wireless is up is never on in this > case. Rebooting the machine solves the problem. I did not find any > other way to solve as the wireless related commands will hang. >=20 > When the wireless network comes up, I can work just normal. >=20 > Erich >=20 > PS: >=20 > The hardware: >=20 > iwn0: mem 0xf2500000-0xf2501fff irq 17 > at device 0.0 on pci3 Hrm ... so I have this one in my T520. I've been experimenting with routers and such ... and I found something *interesting* with iwn(4). On my dlink dir825-C1 I have a channel option "HT20/40 Coexistence". If I disable this, I cannot associate in the 2.4G hz channel at all. I don't know if this is clueful, but it seems to mirror my problems at work. Associates for a moment and then drops. Since I don't know what this really means, I thought I'd chuck it over here and see if its meaningful. sean --=-/w1DVPFumOmXG8PLLwvi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTRJ/mAAoJEBkJRdwI6BaHevEH/2BSkdq2+pUdLTo3IXeEgJVc 4efw/g4nWBWl0EC2617S7eGJeUFPBWiD+MuYI4AsIb7RB6Zcep7c4zc76/85Bwkh 1HTxcooQvIL082J1J12+jg7xTjh0tyqCDjZUawhTnMr0pm5+IrZ5Rr+yQUJUhO4k lc/cDnb3tYykUvoxa00nU6EyVdvfzDFzpwYkcy8S7RYizLlrynKJcoZkwxHyD9xz xIwfYIGFJWeEJA0I5HNI/QOhjQKGCejZS3zfvv0hyodnBKYcGH7iimos15gj9ZE5 ItYdbbnQ86R9r+OscLctYr9u6YnSlJNonZN2s2O8EnuJkkPdj5s6X6oQQteLJRI= =2P2D -----END PGP SIGNATURE----- --=-/w1DVPFumOmXG8PLLwvi-- From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 01:21:20 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31351A76; Wed, 9 Apr 2014 01:21:20 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D573C1314; Wed, 9 Apr 2014 01:21:19 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id i17so2063900qcy.0 for ; Tue, 08 Apr 2014 18:21:19 -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=EzaCpH5BD8lwqEpQI/Gs5Vy/hwaHmWC3SqZckWfuBvc=; b=NuoeFVyYMw98MD2NKIXAyIJjcfeh4qW4Xy0BbPkjau1WX3S3ghb6aiRQeTW+1mc3pV QoZxcOys0i09+zAlwnZMMXWLx579QQDru5QxFKOB2pL7IeUAALtBH60VFKqwq7P95+gz /6fLAotEXCOI1S7ELZNraLB9WwrL9q6pl2EFZ+UGVI6/9brxMvsGXaP1MgnMPSdfafjr GGwF/kXWFh1InG6T/cT93n7lrDJbJqF4xElBJ0oYxZg+/9OcawpZ9xLBHKikHc81BgRw hgvbPdkrBG96g1jKoMYWnGYPtn2sKGdjyDQ2eVEHNc2CkWB6Qd3v3/Plc5x3x6SAcY5l owlg== MIME-Version: 1.0 X-Received: by 10.224.151.210 with SMTP id d18mr8453130qaw.98.1397006478929; Tue, 08 Apr 2014 18:21:18 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 18:21:18 -0700 (PDT) In-Reply-To: <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> Date: Tue, 8 Apr 2014 18:21:18 -0700 X-Google-Sender-Auth: buylJA1go-Stxd9Ftjko9iX2jOY Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 01:21:20 -0000 Hi, 20/40 coex is supposed to be some corner of the spec that notices whether there's a 20mhz only AP on the extension channel and if so, flip everyone over to 20MHz. Is your DIR825 2GHz channel set to 20mhz or 40mhz? -a On 8 April 2014 18:18, Sean Bruno wrote: > On Mon, 2014-03-31 at 07:30 +0800, Erich Dollansky wrote: >> Hi, >> >> since I upgraded to r263767, I have the following problem: >> >> Wireless does not start all the while. When it does not start, it hangs >> then forever. wpa_supplicant's state in top is then '-'. If I start >> wpa_supplicant by hand, it will hang and it cannot be stopped by >> control C. The light indicating that wireless is up is never on in this >> case. Rebooting the machine solves the problem. I did not find any >> other way to solve as the wireless related commands will hang. >> >> When the wireless network comes up, I can work just normal. >> >> Erich >> >> PS: >> >> The hardware: >> >> iwn0: mem 0xf2500000-0xf2501fff irq 17 >> at device 0.0 on pci3 > > Hrm ... so I have this one in my T520. > > I've been experimenting with routers and such ... and I found something > *interesting* with iwn(4). > > On my dlink dir825-C1 I have a channel option "HT20/40 Coexistence". If > I disable this, I cannot associate in the 2.4G hz channel at all. I > don't know if this is clueful, but it seems to mirror my problems at > work. Associates for a moment and then drops. > > Since I don't know what this really means, I thought I'd chuck it over > here and see if its meaningful. > > sean From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 01:31:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A0574BB; Wed, 9 Apr 2014 01:31:57 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7285A150F; Wed, 9 Apr 2014 01:31:57 +0000 (UTC) Received: from [192.168.1.101] (c-24-6-177-88.hsd1.ca.comcast.net [24.6.177.88]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 16CA71929A9; Wed, 9 Apr 2014 01:31:56 +0000 (UTC) Subject: Re: iwn0 hangs randomly when starting the machine From: Sean Bruno To: Adrian Chadd In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-cMX9dq9auwirODEPmfTj" Date: Tue, 08 Apr 2014 18:31:55 -0700 Message-ID: <1397007115.5173.4.camel@powernoodle.corp.yahoo.com> 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.17 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: Wed, 09 Apr 2014 01:31:57 -0000 --=-cMX9dq9auwirODEPmfTj Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2014-04-08 at 18:21 -0700, Adrian Chadd wrote: > Hi, >=20 > 20/40 coex is supposed to be some corner of the spec that notices > whether there's a 20mhz only AP on the extension channel and if so, > flip everyone over to 20MHz. >=20 > Is your DIR825 2GHz channel set to 20mhz or 40mhz? >=20 >=20 > -a=20 Well ... this goofy DLink firmware doesn't let you toggle the 20/40 coexistence radio button if you set the channel width to 20mhz only, so its still on "auto 20/40" in order to toggle the 20/40 coexistence off. Does that make sense at all? sean --=-cMX9dq9auwirODEPmfTj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTRKMLAAoJEBkJRdwI6BaHZHAH/jn3YKPEFDqzNIkP4XWgxX71 GT7EuWrXVoZP65L65S7fPatlnD4OX42kGMqWByEMaFb+EUY4s8F+VssM6KTV8Pdn XVXufCbUaljzM9tXGKATeM5qdcuSwrM86p257j0Ttj8E/1H3BYo0q9nVhOyUZQgH 2dZrX8zW0En4pA/COgzVjYgXjglaVnmICoXbUDkrEhe7gO8to+y+67BFk0qtwGyL 0zMWdkoeWSzmWfy6nVN6IVgleshypkvPqvrwo48sLhfSVwGSTM1Isy1rZIKefh7M zo2nQ1wUEUcgbW/mUV2Y3DO/a+ABGy804OyaO6FZVwM/8tUx+Ms+BBW2xtqCgiU= =rFQn -----END PGP SIGNATURE----- --=-cMX9dq9auwirODEPmfTj-- From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 01:36:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33204519; Wed, 9 Apr 2014 01:36:46 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C47C153C; Wed, 9 Apr 2014 01:36:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=VbkgkhBrBoVXx4UyJCJy0yulsxMjZeA7OCKvtox5WGM=; b=if9H+RNUZ6LWCfGORh74Aq2FNFK9xFWvoatwNbCZaqIZaROyrnLR4cINX+T275uLI8TeXLkKYffYve8PoQckSeNIgLJKg6oMGyFwEo1LS/GLRcgnBfXQagmraEJmMHSwmCTFnmU3d/yppm0lytAG/aPt/1Dqlo3dAo0ywGErmoQ=; Received: from [182.55.101.96] (port=31651 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WXhRV-002fw6-5i; Tue, 08 Apr 2014 19:36:45 -0600 Date: Wed, 9 Apr 2014 09:36:42 +0800 From: Erich Dollansky To: sbruno@freebsd.org Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140409093642.19c2f5cb@X220.alogt.com> In-Reply-To: <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: sbruno@ignoranthack.me, "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 01:36:46 -0000 Hi, On Tue, 08 Apr 2014 18:18:40 -0700 Sean Bruno wrote: > On Mon, 2014-03-31 at 07:30 +0800, Erich Dollansky wrote: > > > > since I upgraded to r263767, I have the following problem: > > > > Wireless does not start all the while. When it does not start, it > > > > iwn0: mem 0xf2500000-0xf2501fff > > irq 17 at device 0.0 on pci3 > > Hrm ... so I have this one in my T520. > > I've been experimenting with routers and such ... and I found > something *interesting* with iwn(4). > > On my dlink dir825-C1 I have a channel option "HT20/40 Coexistence". the router I experience the problem is a D-Link too. But it is not mine. > If I disable this, I cannot associate in the 2.4G hz channel at all. > I don't know if this is clueful, but it seems to mirror my problems at > work. Associates for a moment and then drops. > > Since I don't know what this really means, I thought I'd chuck it over > here and see if its meaningful. On my own router, a ProLink if I remember right, I can only switch between 20 and 40 MHz channel with but I cannot have both. I wonder why the router needs the coexistence. Is it to communicate with other routers to find free channels? Erich From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:07:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0AFC5AFA; Wed, 9 Apr 2014 03:07:41 +0000 (UTC) Received: from mail-ve0-x236.google.com (mail-ve0-x236.google.com [IPv6:2607:f8b0:400c:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8B4E1CC3; Wed, 9 Apr 2014 03:07:40 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id jw12so1547693veb.41 for ; Tue, 08 Apr 2014 20:07: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=s/Xd/HTGMH/eCrrgGvQLLkiVoB5v7XEhP5qIp+dTxXQ=; b=jWpNLyiA2X9KfONiXpP8ouvluL1GTvMfmZbe/wJWbJzct3zvH6YRBaDN5anaqILAWV d0w1UkamQSCn+7NfkQSUNyGzby+0MLRSsILz48ddyt0NvFfXWeDJYY83q0gEoM5V1aFp JC1LN6+BlDlnOczwCp50zGgR5akkZQHNUIHbnTcR6Vq21q42xtiQuBU6EmD3yvHDJjVz R8aMI3QcI0sHzX5gufmEzgFTHJUwN14moS7OoEK8UsZt0+VokSwPC31xwJK/nOeO6u6e gRpYMPwi8XnPS1GxLMIaWy6F1qMXFH+SkKJjWKwHJWaXltXK5u73d6+c1sI6wz8KvXzu K1Bg== MIME-Version: 1.0 X-Received: by 10.58.185.145 with SMTP id fc17mr6663559vec.14.1397012859810; Tue, 08 Apr 2014 20:07:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.220.113.199 with HTTP; Tue, 8 Apr 2014 20:07:39 -0700 (PDT) In-Reply-To: <20140409093642.19c2f5cb@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> Date: Tue, 8 Apr 2014 20:07:39 -0700 X-Google-Sender-Auth: mPhUhv3gIw8k-iXcJuVpk6af85Y Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 03:07:41 -0000 Coexistence is to deal with the fact that a 40MHz channel may overlap a 20MHz-only AP in the extension channel. If the AP finds a 20MHz AP in the extension channel (ie, the other half of its 40MHz) channel then it'll flip itself to 20MHz. If it determines it isn't there any more, it'll flip the BSS to the 40MHz channel. Now, why the hell it's causing the connection to fail? I have no idea. can someone file a PR that says it's all busted with 40MHz coxistence enabled? We can then start debugging from that position. -a From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:32:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFFA2261; Wed, 9 Apr 2014 03:32:59 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C69391062; Wed, 9 Apr 2014 03:32:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=oh6JtMe2D9oruCanTmo+ubTp37Q3DhneI4fCPEu5lNg=; b=vmCbvbS8ChahK4K3ix8aAnffRTUEqlKjphyo4giYW7T3iiKw3oMh/ANu2eDLq3KS36mHFVts9QfXdqfZqUmi9m9hleUNw/xMC2hNWF0yzCSC++iFxY42+VFPHjiRIlHxW2hvC0KQ27DaoGXjw+kPRAAEZfSx3mtF/dM3wLWe/Gk=; Received: from [182.55.101.96] (port=21624 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WXjFy-003w4e-9T; Tue, 08 Apr 2014 21:32:58 -0600 Date: Wed, 9 Apr 2014 11:32:54 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140409113254.3a3277a3@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 03:33:00 -0000 Hi, On Tue, 8 Apr 2014 20:07:39 -0700 Adrian Chadd wrote: > Coexistence is to deal with the fact that a 40MHz channel may overlap > a 20MHz-only AP in the extension channel. > > If the AP finds a 20MHz AP in the extension channel (ie, the other > half of its 40MHz) channel then it'll flip itself to 20MHz. If it > determines it isn't there any more, it'll flip the BSS to the 40MHz > channel. > > Now, why the hell it's causing the connection to fail? I have no idea. > > can someone file a PR that says it's all busted with 40MHz coxistence > enabled? We can then start debugging from that position. > I am not so sure if it is a general problem or just a DLink problem. I just activated my own access point and it worked there. The only problem is that it also works with DLink but only randomly. So, it still could have been that I was just always lucky when connecting to the ProLink access point I have. As the DLink is not mine, I am not even able to access its administration interface. Can I suggest to wait a bit to get more feedback to see if it is a general problem or a problem only linked to one manufacturer? Erich From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:40:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50F6B66D; Wed, 9 Apr 2014 03:40:02 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3C9510E1; Wed, 9 Apr 2014 03:40:01 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id q108so1734122qgd.37 for ; Tue, 08 Apr 2014 20:40:01 -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=+Yk+tA25x5/wnEbTVFjr+2+zCn1yIxr3BIKBg/sYgkM=; b=rY808hYbmM+q2N5A/eb8y+bAQqHmtVIchzrqSz1N6C7yzdQOprydGgqnq24skXP7x0 9jdaC6wSHaD0aZ6MKFo4aH5iU66pafMXgoEsDLGsFnoMXr1W82FgonDxOqKMpMxsnOYk eQPgI4UTuguAhdMUoNXocjeNvn7EA2YPI9qMcCG4ivfbOL/WEa5xv6+2+d24zLmqQQ5m KI8jle5A0Oz7Qzo7OBe9GSeWVKjG+WkEuNS6fbPvXZzh52tahrb3ItFiCNHebTavl9Pc ruobUby6v939Gsx8entf7OUS1+4WVPpqqdb+9Bol8jpap/Vuk0yDZr3X1iZmQK4/9Igv st7Q== MIME-Version: 1.0 X-Received: by 10.140.39.103 with SMTP id u94mr9018039qgu.46.1397014801155; Tue, 08 Apr 2014 20:40:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Tue, 8 Apr 2014 20:40:01 -0700 (PDT) In-Reply-To: <20140409113254.3a3277a3@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> Date: Tue, 8 Apr 2014 20:40:01 -0700 X-Google-Sender-Auth: gyHfuBRiYsOJQGSJEY7C6_jFoMw Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 03:40:02 -0000 I'm not sure. I'd really like to see what the story is with coexistence somehow. -a On 8 April 2014 20:32, Erich Dollansky wrote: > Hi, > > On Tue, 8 Apr 2014 20:07:39 -0700 > Adrian Chadd wrote: > >> Coexistence is to deal with the fact that a 40MHz channel may overlap >> a 20MHz-only AP in the extension channel. >> >> If the AP finds a 20MHz AP in the extension channel (ie, the other >> half of its 40MHz) channel then it'll flip itself to 20MHz. If it >> determines it isn't there any more, it'll flip the BSS to the 40MHz >> channel. >> >> Now, why the hell it's causing the connection to fail? I have no idea. >> >> can someone file a PR that says it's all busted with 40MHz coxistence >> enabled? We can then start debugging from that position. >> > I am not so sure if it is a general problem or just a DLink problem. > > I just activated my own access point and it worked there. The only > problem is that it also works with DLink but only randomly. So, it > still could have been that I was just always lucky when connecting to > the ProLink access point I have. > > As the DLink is not mine, I am not even able to access its > administration interface. > > Can I suggest to wait a bit to get more feedback to see if it is a > general problem or a problem only linked to one manufacturer? > > Erich From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 03:52:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60EE9FB6; Wed, 9 Apr 2014 03:52:59 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F7B0127D; Wed, 9 Apr 2014 03:52:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=A+H6TeIdf1HFnI6kayuxrw9BwewDOS8Dwb8aNvrmG+E=; b=vdB6aKuwtFcSfe6vHpEvPKSOn+t6Kc820SsqtCYY52GLRELtxBvs+NSyf+Mjy+36+o1j/GKfsStygUrIZHAjnP+SPDD860o/gQIwjXIy3OWWHTV8p3eEdL+S2qehdub4oMVnN8C6+gXprJ4tPQP8fzp/cLKx26husVNDqaFx0dI=; Received: from [182.55.101.96] (port=63836 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WXjZK-004AXn-4Z; Tue, 08 Apr 2014 21:52:58 -0600 Date: Wed, 9 Apr 2014 11:52:54 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140409115254.43888002@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 03:52:59 -0000 Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd wrote: > I'm not sure. I'd really like to see what the story is with > coexistence somehow. > I cannot help there as my own access points do not have this feature. Erich From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 04:04:56 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC23110A; Wed, 9 Apr 2014 04:04:55 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF5761336; Wed, 9 Apr 2014 04:04:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=TuZ62NoKklCSbgkvZI1Ehc8larKIU9zEOEOmTo2CLW0=; b=fAQDiIMtCMxfAbQ8QUtI4kMEC2rrc/0O8f2gBEGtyyLOoDUi1tm8VfqgMlQiMneewHAC/nKSpqVhFMU2ozuiIWi3IdTZsKYJrbrDDT19sBfwomPFcnBNu5DyUry73SaYm/6Mk9WTc1Nqd3o7pofOlRf2bQQV3yYS2c01WgecBsk=; Received: from [182.55.101.96] (port=38291 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WXjks-004IuX-Mf; Tue, 08 Apr 2014 22:04:55 -0600 Date: Wed, 9 Apr 2014 12:04:51 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140409120451.4f60e599@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 04:04:56 -0000 Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd wrote: > I'm not sure. I'd really like to see what the story is with > coexistence somehow. one other note. I start my machine randomly with a kernel built from sources dated 26.03.14. I never faced this problem with these sources. Erich > > > -a > > > On 8 April 2014 20:32, Erich Dollansky > wrote: > > Hi, > > > > On Tue, 8 Apr 2014 20:07:39 -0700 > > Adrian Chadd wrote: > > > >> Coexistence is to deal with the fact that a 40MHz channel may > >> overlap a 20MHz-only AP in the extension channel. > >> > >> If the AP finds a 20MHz AP in the extension channel (ie, the other > >> half of its 40MHz) channel then it'll flip itself to 20MHz. If it > >> determines it isn't there any more, it'll flip the BSS to the 40MHz > >> channel. > >> > >> Now, why the hell it's causing the connection to fail? I have no > >> idea. > >> > >> can someone file a PR that says it's all busted with 40MHz > >> coxistence enabled? We can then start debugging from that position. > >> > > I am not so sure if it is a general problem or just a DLink problem. > > > > I just activated my own access point and it worked there. The only > > problem is that it also works with DLink but only randomly. So, it > > still could have been that I was just always lucky when connecting > > to the ProLink access point I have. > > > > As the DLink is not mine, I am not even able to access its > > administration interface. > > > > Can I suggest to wait a bit to get more feedback to see if it is a > > general problem or a problem only linked to one manufacturer? > > > > Erich From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 12:40:23 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E03C0A39 for ; Wed, 9 Apr 2014 12:40:23 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E9C111F7 for ; Wed, 9 Apr 2014 12:40:23 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id i8so2640248qcq.3 for ; Wed, 09 Apr 2014 05:40:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wukEMtWVBXaSKmmRRxblqKtV+KjbhdN+uditvaOCUBw=; b=KeCqnQdcdWw1NSwFvaZJFLeD+WsBWirw7KWgKthzr1/+wxhGFkmHUNCC8wQ4Voy5dk x1g63THy8Nd0t6M0Oo5X0YDAO5FvytuwIGQEHf/QIy+HGGoi1y4uWrCiKd8P5Uct+xGU btVbeJtQLYoFflqx1ViupI9z/g7gKbLls1iztw9SBCqqJfeYqlqmsgwwAwmjLx8ITXvM yF5wnKUWdmEajvkD0LbvoiE98h0A5yKatL11nj4GyZmf/YDSyF3+WTiB1ii5Bqd0JkAg b9CuV7G7iXj2+WNKMnEih4Z1QS72QHBHRZxl+0Q0XXmX2FX6UARGRWVnV/xye7qxTvzu cSTA== X-Received: by 10.224.69.193 with SMTP id a1mr2132855qaj.95.1397047222761; Wed, 09 Apr 2014 05:40:22 -0700 (PDT) Received: from lpnix002.local (static-68-239-84-57.washdc.east.verizon.net. [68.239.84.57]) by mx.google.com with ESMTPSA id a15sm943575qgf.16.2014.04.09.05.40.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 05:40:22 -0700 (PDT) Message-ID: <53453FB5.20707@gmail.com> Date: Wed, 09 Apr 2014 08:40:21 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: Fwd: Re: Atheros AR9565 References: <53453F74.5000403@gmail.com> In-Reply-To: <53453F74.5000403@gmail.com> X-Enigmail-Version: 1.6 X-Forwarded-Message-Id: <53453F74.5000403@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 12:40:23 -0000 I'm using the GENERIC kernel. Want me to create a custom kernel? pciconf info: hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'Haswell DRAM Controller' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 rev=0x06 hdr=0x01 vendor = 'Intel Corporation' device = 'Haswell PCI Express x16 Controller' class = bridge subclass = PCI-PCI vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'Haswell Integrated Graphics Controller' class = display subclass = VGA hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'Haswell HD Audio Controller' class = multimedia subclass = HDA xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point USB xHCI Host Controller' class = serial bus subclass = USB none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point MEI Controller' class = simple comms ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point USB Enhanced Host Controller' class = serial bus subclass = USB hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point High Definition Audio Controller' class = multimedia subclass = HDA pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 rev=0xd4 hdr=0x01 vendor = 'Intel Corporation' device = 'Lynx Point PCI Express Root Port' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 rev=0xd4 hdr=0x01 vendor = 'Intel Corporation' device = 'Lynx Point PCI Express Root Port' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 rev=0xd4 hdr=0x01 vendor = 'Intel Corporation' device = 'Lynx Point PCI Express Root Port' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point USB Enhanced Host Controller' class = serial bus subclass = USB isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point LPC Controller' class = bridge subclass = PCI-ISA none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point SMBus Controller' class = serial bus subclass = SMBus atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' class = mass storage subclass = ATA vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class = display subclass = 3D ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9565 Wireless Network Adapter' class = network none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 rev=0x10 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network subclass = ethernet On 04/08/14 18:29, Adrian Chadd wrote: > hi, > > ok. Can you please do a pciconf -lv and attach it here? > > Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? > > Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. > > > > -a > > > On 8 April 2014 13:38, tzoi516 wrote: >> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >> up I received a ton of these: >> >> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >> >> received those about 20 times then this: >> >> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >> >> And now the top 2 are slowly scrolling. >> >> Mike >> >> >> On 04/08/14 16:03, Adrian Chadd wrote: >>> Right. It sounds like it's not associated. >>> >>> Try wlandebug +assoc and then run wpa_supplicant >>> >>> >>> -a >>> >>> >>> On 8 April 2014 12:21, tzoi516 wrote: >>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>> ioctl errors that I get on shutdown. >>>> These are after logging in: >>>> >>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>> dhclient[1001]: send_packet: Invalid argument >>>> dhclient[1001]: send_packet: No buffer space available >>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>> dhclient[1001]: send_packet: No buffer space available >>>> dhclient[1001]: send_packet: Invalid argument >>>> dhclient[1001]: send_packet: Network is down >>>> >>>> Mike >>>> >>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>> Ah. Can you post the buffer errors you're seeing? >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> >>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>> This specific one: >>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>> >>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>> >>>>>>>> Mike >>>>>>>> _______________________________________________ >>>>>>>> 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" >>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>> scan and see available networks but I can't connect to any except for >>>>>> unprotected networks. >>>>>> >>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>> >>>>>> Mike From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 19:02:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99DD3B21 for ; Wed, 9 Apr 2014 19:02:49 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B4F21221 for ; Wed, 9 Apr 2014 19:02:49 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id f51so2794788qge.16 for ; Wed, 09 Apr 2014 12:02: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:cc:content-type; bh=kbFqeDMx6/BrXqkBZTmXETqiyWF/G0kqETsJv5WSg4o=; b=WeRA4+edl0WeGjWzKjeJmFXyyD9MTKiYboGxxoaFXxu1RR6iKqu/S/SDj1xxQvhOq4 s68XalqDyYvG8pGG1ReBU6+VySYCK0SbO8SD7xdg0BQAKtp2Deug2YHyaDXFahBrgeL5 HqHVgnQxhkV61a1aqzn6ducnFOthmJX4OU1rTvvvFcYCRRjJ9HTSgDyQ0lZCebX0dxzr zl56d/iD2hUPnrwdPT++sS0+Ezys6QMzgZpsNSW2wQfhDImlEoB69vf9eMLQqWOPU8E4 xywm/aXxWROz430+RYscFdQWkNcZm13MYE4wgjmCTBOEQTF5zEsTjw5F3z532fTnf25y UIjw== MIME-Version: 1.0 X-Received: by 10.140.22.197 with SMTP id 63mr14166554qgn.4.1397070168495; Wed, 09 Apr 2014 12:02:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Wed, 9 Apr 2014 12:02:48 -0700 (PDT) In-Reply-To: <53453FB5.20707@gmail.com> References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> Date: Wed, 9 Apr 2014 12:02:48 -0700 X-Google-Sender-Auth: xdgR8llEie3WXL5hqdM7mM-V-E0 Message-ID: Subject: Re: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 19:02:49 -0000 Hi, The AR9565 is a relatively new chip that hasn't really been thoroughly tested in FreeBSD. Laptop manufacturers have also gone and done some rather silly things to save cost on the wireless NIC itself and I'm not sure those patches / work arounds are in -HEAD. please file a PR with this problem complete with your pciconf -lv output as above. Thanks! -a On 9 April 2014 05:40, tzoi516 wrote: > I'm using the GENERIC kernel. Want me to create a custom kernel? > > pciconf info: > > hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Haswell DRAM Controller' > class = bridge > subclass = HOST-PCI > pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 > rev=0x06 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Haswell PCI Express x16 Controller' > class = bridge > subclass = PCI-PCI > vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Haswell Integrated Graphics Controller' > class = display > subclass = VGA > hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Haswell HD Audio Controller' > class = multimedia > subclass = HDA > xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point USB xHCI Host Controller' > class = serial bus > subclass = USB > none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point MEI Controller' > class = simple comms > ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point USB Enhanced Host Controller' > class = serial bus > subclass = USB > hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point High Definition Audio Controller' > class = multimedia > subclass = HDA > pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 > rev=0xd4 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lynx Point PCI Express Root Port' > class = bridge > subclass = PCI-PCI > pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 > rev=0xd4 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lynx Point PCI Express Root Port' > class = bridge > subclass = PCI-PCI > pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 > rev=0xd4 hdr=0x01 > vendor = 'Intel Corporation' > device = 'Lynx Point PCI Express Root Port' > class = bridge > subclass = PCI-PCI > ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point USB Enhanced Host Controller' > class = serial bus > subclass = USB > isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point LPC Controller' > class = bridge > subclass = PCI-ISA > none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point SMBus Controller' > class = serial bus > subclass = SMBus > atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' > class = mass storage > subclass = ATA > vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de > rev=0xa1 hdr=0x00 > vendor = 'NVIDIA Corporation' > class = display > subclass = 3D > ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR9565 Wireless Network Adapter' > class = network > none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 > rev=0x10 hdr=0x00 > vendor = 'Atheros Communications Inc.' > class = network > subclass = ethernet > > > > > On 04/08/14 18:29, Adrian Chadd wrote: >> hi, >> >> ok. Can you please do a pciconf -lv and attach it here? >> >> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >> >> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >> >> >> >> -a >> >> >> On 8 April 2014 13:38, tzoi516 wrote: >>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>> up I received a ton of these: >>> >>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>> >>> received those about 20 times then this: >>> >>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>> >>> And now the top 2 are slowly scrolling. >>> >>> Mike >>> >>> >>> On 04/08/14 16:03, Adrian Chadd wrote: >>>> Right. It sounds like it's not associated. >>>> >>>> Try wlandebug +assoc and then run wpa_supplicant >>>> >>>> >>>> -a >>>> >>>> >>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>> ioctl errors that I get on shutdown. >>>>> These are after logging in: >>>>> >>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>> dhclient[1001]: send_packet: Invalid argument >>>>> dhclient[1001]: send_packet: No buffer space available >>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>> dhclient[1001]: send_packet: No buffer space available >>>>> dhclient[1001]: send_packet: Invalid argument >>>>> dhclient[1001]: send_packet: Network is down >>>>> >>>>> Mike >>>>> >>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>> This specific one: >>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>> >>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>> >>>>>>>>> Mike >>>>>>>>> _______________________________________________ >>>>>>>>> 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" >>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>> scan and see available networks but I can't connect to any except for >>>>>>> unprotected networks. >>>>>>> >>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>> >>>>>>> Mike > > > _______________________________________________ > 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 Wed Apr 9 19:04:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 227D8B69 for ; Wed, 9 Apr 2014 19:04:47 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D73B01231 for ; Wed, 9 Apr 2014 19:04:46 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id k15so2914374qaq.29 for ; Wed, 09 Apr 2014 12:04:46 -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=Po1t8UG/ZxHvzGSI9whMVntgH2KD+rVn/XXVBw5diGs=; b=zEmlagAGCyu64uE1JqCXnZ7ay3OeJ/nkTQfu7pisZ+dILnAiCxDCccLA7dfSEPCWqa Xe4gp8GJ5mGqHswDL+Hd4BQcU2Zd/7EBA+URV3//FtTExbFnI0OKZx5lXHxdAth+U/UW loZsrkI1IVouPk9Mp92BxgHhJS4sETHBPUyEzf+8cFQBn1EqTftYSST4nyb5Va8SrJ0M 1z9AzvOy5Sx5lZo2UF7uUvaz5wfpCCZd1d+q3P8RWpE5KGgbwtfKvId/OwZygmd6Rnh+ 1NlEJ7hlK043oNaaoj5e4dXIP92t2lZ8Ix6H9FFCtpK7p0mqxrb9JxauFeKgjoH6U41R Wcvw== MIME-Version: 1.0 X-Received: by 10.224.47.130 with SMTP id n2mr15114131qaf.26.1397070285995; Wed, 09 Apr 2014 12:04:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Wed, 9 Apr 2014 12:04:45 -0700 (PDT) In-Reply-To: References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> Date: Wed, 9 Apr 2014 12:04:45 -0700 X-Google-Sender-Auth: qtKOOr8fg1HgjqsJb2D9NVojSZU Message-ID: Subject: Re: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 19:04:47 -0000 (.. and my standard offer applies here. I'm much better likely to fix things if I have one of them. I likely can't buy that specific NIC; I'd have to have the whole laptop. So if someone wishes to buy me one of these things, I'll endeavour to improve upon power saving and wifi support.) -a From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 19:28:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A3C24BC; Wed, 9 Apr 2014 19:28:08 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D99D514AB; Wed, 9 Apr 2014 19:28:07 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so2890528qgd.29 for ; Wed, 09 Apr 2014 12:28:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8Ask2//aeADCgdsGjy1i7ceRyncaf9Jrs5WoqJYkdZE=; b=HJ6kVyakbF6Md30cgMh2D7YXdtHiqF+YDXn5KOON0rvgOJdYAeoL55LTCZZ+sJk2jX veFH33BlvsYdtuyZirIekTkAkiKIorwNC1TCo4Jm6MhAjRvtvnQjwPVdkG5M+Ri3juis PHuFYKpT7mxtg9aZXmtQHzJRscuQPWAz6yINQq9I+va8IrNzhQOJvI/EQBeaRLZmahjC oS/fRKhw7/nzmNe6bpm/7W/N1JFpelMvaBVTx/N5hELGh2PYDSgGwmiCnhnO/GDmEXRU weaUuO9BusWgVh79zBW4khTilHUG/OAWmSv0EagVqIG8ed3tEs5y68823TEBc0pK6+z3 NetQ== X-Received: by 10.224.65.67 with SMTP id h3mr15103689qai.43.1397071686958; Wed, 09 Apr 2014 12:28:06 -0700 (PDT) Received: from lpnix002.local (static-68-239-84-57.washdc.east.verizon.net. [68.239.84.57]) by mx.google.com with ESMTPSA id m2sm3317921qac.3.2014.04.09.12.28.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 12:28:06 -0700 (PDT) Message-ID: <53459F44.2010102@gmail.com> Date: Wed, 09 Apr 2014 15:28:04 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 19:28:08 -0000 Hi, Thanks for all of the help. Where is the driver source code? I'll submit a PR today. Thanks, Mike On 04/09/14 15:02, Adrian Chadd wrote: > Hi, > > The AR9565 is a relatively new chip that hasn't really been thoroughly > tested in FreeBSD. Laptop manufacturers have also gone and done some > rather silly things to save cost on the wireless NIC itself and I'm > not sure those patches / work arounds are in -HEAD. > > please file a PR with this problem complete with your pciconf -lv > output as above. > > Thanks! > > > -a > > > On 9 April 2014 05:40, tzoi516 wrote: >> I'm using the GENERIC kernel. Want me to create a custom kernel? >> >> pciconf info: >> >> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell DRAM Controller' >> class = bridge >> subclass = HOST-PCI >> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >> rev=0x06 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Haswell PCI Express x16 Controller' >> class = bridge >> subclass = PCI-PCI >> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell Integrated Graphics Controller' >> class = display >> subclass = VGA >> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell HD Audio Controller' >> class = multimedia >> subclass = HDA >> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB xHCI Host Controller' >> class = serial bus >> subclass = USB >> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point MEI Controller' >> class = simple comms >> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB Enhanced Host Controller' >> class = serial bus >> subclass = USB >> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point High Definition Audio Controller' >> class = multimedia >> subclass = HDA >> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB Enhanced Host Controller' >> class = serial bus >> subclass = USB >> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point LPC Controller' >> class = bridge >> subclass = PCI-ISA >> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point SMBus Controller' >> class = serial bus >> subclass = SMBus >> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >> class = mass storage >> subclass = ATA >> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >> rev=0xa1 hdr=0x00 >> vendor = 'NVIDIA Corporation' >> class = display >> subclass = 3D >> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR9565 Wireless Network Adapter' >> class = network >> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >> rev=0x10 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> class = network >> subclass = ethernet >> >> >> >> >> On 04/08/14 18:29, Adrian Chadd wrote: >>> hi, >>> >>> ok. Can you please do a pciconf -lv and attach it here? >>> >>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >>> >>> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >>> >>> >>> >>> -a >>> >>> >>> On 8 April 2014 13:38, tzoi516 wrote: >>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>>> up I received a ton of these: >>>> >>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>>> >>>> received those about 20 times then this: >>>> >>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>> >>>> And now the top 2 are slowly scrolling. >>>> >>>> Mike >>>> >>>> >>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>> Right. It sounds like it's not associated. >>>>> >>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>>> ioctl errors that I get on shutdown. >>>>>> These are after logging in: >>>>>> >>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>> dhclient[1001]: send_packet: Network is down >>>>>> >>>>>> Mike >>>>>> >>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> >>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>> >>>>>>>>> >>>>>>>>> -a >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>> This specific one: >>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>> >>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>> >>>>>>>>>> Mike >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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" >>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>>> scan and see available networks but I can't connect to any except for >>>>>>>> unprotected networks. >>>>>>>> >>>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>>> >>>>>>>> Mike >> >> _______________________________________________ >> 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 Wed Apr 9 19:44:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5B2DA46 for ; Wed, 9 Apr 2014 19:44:02 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 964E41667 for ; Wed, 9 Apr 2014 19:44:02 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id 63so2750324qgz.33 for ; Wed, 09 Apr 2014 12:44:01 -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=fkcVwwe6aK/Jj7tJ0Sq/YLsWroqNQfk/7UZRBX3d/Xk=; b=utWFvc4uDQ+VNicsgFReWLQi8Nbc5xpHDccs/yZLBS6Wl+cIUELHZt8tcEI8ySZ+/1 tziaMiG6XmckOU3IcvZsA7pmysZpPTJcOBR1FBZ+1i2KGEXImh0j9fpMA4+OT5qtgRmZ 0GM5pZHqrtBHrlFMYxDEV02cjaD+qbrsCiNLcTOTL9Xz7bEQRoXcHZaTqqS3PELY5THH Mcvmp5JiIFGoNerarBrTe4oihVY0rH97AoiH3n5ToSq64r7Lc7FjeUHiby3jKB5Ocjg5 aTbZfJRZEkFT0+tj0kyEHw4cHcSYJW/dOYcBmWhYp7dWggx9yxuv165xxPLcbYBTsS5U ClqQ== MIME-Version: 1.0 X-Received: by 10.140.109.100 with SMTP id k91mr14604742qgf.12.1397072641727; Wed, 09 Apr 2014 12:44:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Wed, 9 Apr 2014 12:44:01 -0700 (PDT) In-Reply-To: <53459F44.2010102@gmail.com> References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <53459F44.2010102@gmail.com> Date: Wed, 9 Apr 2014 12:44:01 -0700 X-Google-Sender-Auth: P3ImGaGDkW1Qo-LJ8falFM9iDns Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: tzoi516 Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 19:44:02 -0000 The driver source is in sys/dev/ath/ and sys/contrib/dev/ath/ath_hal/ar9300/ I have all of the linux driver source and the atheros internal driver source for their AP products but their desktop drivers are .. very laptop specific and it's hard to get the driver source out of the relevant group(s). -a On 9 April 2014 12:28, tzoi516 wrote: > Hi, > > Thanks for all of the help. Where is the driver source code? I'll submit > a PR today. > > Thanks, > Mike > > On 04/09/14 15:02, Adrian Chadd wrote: >> Hi, >> >> The AR9565 is a relatively new chip that hasn't really been thoroughly >> tested in FreeBSD. Laptop manufacturers have also gone and done some >> rather silly things to save cost on the wireless NIC itself and I'm >> not sure those patches / work arounds are in -HEAD. >> >> please file a PR with this problem complete with your pciconf -lv >> output as above. >> >> Thanks! >> >> >> -a >> >> >> On 9 April 2014 05:40, tzoi516 wrote: >>> I'm using the GENERIC kernel. Want me to create a custom kernel? >>> >>> pciconf info: >>> >>> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >>> rev=0x06 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Haswell DRAM Controller' >>> class = bridge >>> subclass = HOST-PCI >>> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >>> rev=0x06 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Haswell PCI Express x16 Controller' >>> class = bridge >>> subclass = PCI-PCI >>> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >>> rev=0x06 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Haswell Integrated Graphics Controller' >>> class = display >>> subclass = VGA >>> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >>> rev=0x06 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Haswell HD Audio Controller' >>> class = multimedia >>> subclass = HDA >>> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point USB xHCI Host Controller' >>> class = serial bus >>> subclass = USB >>> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point MEI Controller' >>> class = simple comms >>> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point USB Enhanced Host Controller' >>> class = serial bus >>> subclass = USB >>> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point High Definition Audio Controller' >>> class = multimedia >>> subclass = HDA >>> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >>> rev=0xd4 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point PCI Express Root Port' >>> class = bridge >>> subclass = PCI-PCI >>> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >>> rev=0xd4 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point PCI Express Root Port' >>> class = bridge >>> subclass = PCI-PCI >>> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >>> rev=0xd4 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point PCI Express Root Port' >>> class = bridge >>> subclass = PCI-PCI >>> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point USB Enhanced Host Controller' >>> class = serial bus >>> subclass = USB >>> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point LPC Controller' >>> class = bridge >>> subclass = PCI-ISA >>> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point SMBus Controller' >>> class = serial bus >>> subclass = SMBus >>> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >>> class = mass storage >>> subclass = ATA >>> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >>> rev=0xa1 hdr=0x00 >>> vendor = 'NVIDIA Corporation' >>> class = display >>> subclass = 3D >>> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >>> rev=0x01 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> device = 'AR9565 Wireless Network Adapter' >>> class = network >>> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >>> rev=0x10 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> class = network >>> subclass = ethernet >>> >>> >>> >>> >>> On 04/08/14 18:29, Adrian Chadd wrote: >>>> hi, >>>> >>>> ok. Can you please do a pciconf -lv and attach it here? >>>> >>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >>>> >>>> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >>>> >>>> >>>> >>>> -a >>>> >>>> >>>> On 8 April 2014 13:38, tzoi516 wrote: >>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>>>> up I received a ton of these: >>>>> >>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>>>> >>>>> received those about 20 times then this: >>>>> >>>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>>> >>>>> And now the top 2 are slowly scrolling. >>>>> >>>>> Mike >>>>> >>>>> >>>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>>> Right. It sounds like it's not associated. >>>>>> >>>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>>>> ioctl errors that I get on shutdown. >>>>>>> These are after logging in: >>>>>>> >>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>> dhclient[1001]: send_packet: Network is down >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -a >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>>> This specific one: >>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>>> >>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>>> >>>>>>>>>>> Mike >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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" >>>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>>>> scan and see available networks but I can't connect to any except for >>>>>>>>> unprotected networks. >>>>>>>>> >>>>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>>>> >>>>>>>>> Mike >>> >>> _______________________________________________ >>> 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 Wed Apr 9 20:38:21 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 29951346 for ; Wed, 9 Apr 2014 20:38:21 +0000 (UTC) Received: from nm30-vm0.bullet.mail.bf1.yahoo.com (nm30-vm0.bullet.mail.bf1.yahoo.com [98.139.213.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD31D1C09 for ; Wed, 9 Apr 2014 20:38:20 +0000 (UTC) Received: from [98.139.212.153] by nm30.bullet.mail.bf1.yahoo.com with NNFMP; 09 Apr 2014 20:35:18 -0000 Received: from [98.139.212.199] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 09 Apr 2014 20:35:17 -0000 Received: from [127.0.0.1] by omp1008.mail.bf1.yahoo.com with NNFMP; 09 Apr 2014 20:35:17 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 942679.29666.bm@omp1008.mail.bf1.yahoo.com Received: (qmail 12738 invoked by uid 60001); 9 Apr 2014 20:35:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1397075717; bh=GVgevznmkwrCAK7mhQJJrJHUQxIFNrVELOFYjqUs510=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=zm04vORAvhi9Tz2XP5CIvI2v8srzDYe/KTLGIfJwOoTVDYp3BOx49NOz3o8/Hc2KEkZc4YT9/nh0QMuzyMBiSNhKpQjCmwsVmh4X89oPisy6iuBA0Kjw1WwuKOpUOaB10axBUy1pPHrhrkgEYzPBIqQrkzvtEF5VTqdL+mEu3wQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=dGevygGwT0QGgzPDBFQhD3rTZASi1hzeGfcytfmKi/YzeoWyQl8BHcZ07aKeDCZojkG4Tg7REbTw8iv5aALYqOLzNmswRFee2vxf5sOd/aTAQryupmn5m8ggrtW1PViRycblcZqc+VIdm21FcNqkpnUsQbyuoaZ5bB4+Vy6cJR0=; X-YMail-OSG: 03T48T8VM1nQkLWe8luWfJEt7UM1KHhtqWv28N7pfFDrOH4 OHPuRizfi3JvXnBFnmzhD1P9rgzxW9lH9h9CnekNKSICd8M09bb9Nbw92h2K dZeNjUhgPw_qzjBR0iX6uOyJ.lyKRY1MlocTAn_lwT3RNiVQj4OXRc_DbApW .Kldb_JmQxZfGaCQFgPTxV133DwV.zqnboPuXMp315iF_aPFxK1m6HXIPeNH 8JVxQtMS_6fcuHrcHibBaxREX99B.b2ts69mTaBEx8iUfk1NgSSzlaypFEjB 1oPrVXYmv6DfuYko.XwSbH2f08AsddXjE3SBoBRcNnKtcYFUXhl2nsQRT5JG VZyXlE1DKvqopNdUwT6TGewNiCaPGw4naaenKPf9.KFug.57IIMAwNrRIhfC L2DCimKFWSLp_nJWgqDZUuOo3abR3XUZZ4Qqm5yDl8wkRmCrGoQ9a6WM9TTA s8caZp3qyuRC.oC7vvBtVQhXSCnR3LTUxhy5bQHzJ0v.3P7XvIrPRLh6Xl1I rHG93PBoZq8BMdV4ciCDZoMwBoK6jtyywL4fhIqVIBxyucqBcjiApy8f4QbD MGGgA6ZBBz95IfKZeemDgB510iIKofE1NQltgYwHPsYwdDPcurA1S70PE20k w1zW6lUpZpk77wPEp65hWjG2Z4IPGBjhH6oEnfEr.hIUeC68AeSs7qGYnB65 3len4IeBQ6z.CM4miuwhxzYORCs2cbrktXruWqHs3.pb6BpUVlxdBaSTpByX x3Y473ihH Received: from [70.90.74.161] by web140701.mail.bf1.yahoo.com via HTTP; Wed, 09 Apr 2014 13:35:17 PDT X-Rocket-MIMEInfo: 002.001, SGV5LCBJJ3ZlIGdvdCBvbmUgb2YgdGhlc2UgYmFiaWVzIGluIG15IEhQIGxhcHRvcDsgSSBhY3R1YWxseSBwb3N0ZWQgc29tZSBwcm9ibGVtcyBJIHdhcyBoYXZpbmcgdG8gdGhlIGxpc3QgYmFjayBpbiBBdWcuICcxMy7CoCBJIGNvdWxkIGxvYW4geW91IG1pbmUgYW5kL29yIGFzc2lzdCB3aXRoIGRlYnVnZ2luZyBpZiBJIGNhbiBoYXZlIGl0IGJhY2sgKGNhbiBtYWtlIGRvIHdpdGggYW4gZXh0ZXJuYWwgd2lyZWxlc3MgZGV2aWNlKS4KCgpBbnRob255CgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX18BMAEBAQE- X-Mailer: YahooMailWebService/0.8.182.648 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> Message-ID: <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> Date: Wed, 9 Apr 2014 13:35:17 -0700 (PDT) From: Anthony Jenkins Subject: Re: Re: Atheros AR9565 To: Adrian Chadd , tzoi516 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Anthony Jenkins 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, 09 Apr 2014 20:38:21 -0000 Hey, I've got one of these babies in my HP laptop; I actually posted some p= roblems I was having to the list back in Aug. '13.=A0 I could loan you mine= and/or assist with debugging if I can have it back (can make do with an ex= ternal wireless device).=0A=0A=0AAnthony=0A=0A=0A__________________________= ______=0AFrom: Adrian Chadd =0ATo: tzoi516 =0ACc: "freebsd-wireless@freebsd.org" =0ASent: Wednesday, April 9, 2014 3:02 PM=0ASubject: Re: Re: Atheros AR95= 65=0A=0A=0AHi,=0A=0AThe AR9565 is a relatively new chip that hasn't really = been thoroughly=0Atested in FreeBSD. Laptop manufacturers have also gone an= d done some=0Arather silly things to save cost on the wireless NIC itself a= nd I'm=0Anot sure those patches / work arounds are in -HEAD.=0A=0Aplease fi= le a PR with this problem complete with your pciconf -lv=0Aoutput as above.= =0A=0AThanks!=0A=0A=0A-a=0A=0A=0AOn 9 April 2014 05:40, tzoi516 wrote:=0A> I'm using the GENERIC kernel. Want me to create a custo= m kernel?=0A>=0A> pciconf info:=0A>=0A> hostb0@pci0:0:0:0:=A0 =A0 class=3D0= x060000 card=3D0xfa401179 chip=3D0x0c048086=0A> rev=3D0x06 hdr=3D0x00=0A>= =A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0dev= ice=A0 =A0=A0=A0=3D 'Haswell DRAM Controller'=0A>=A0 =A0=A0=A0class=A0 =A0 = =A0 =3D bridge=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D HOST-PCI=0A> pcib1@pci0= :0:1:0:=A0 =A0 class=3D0x060400 card=3D0xfa471179 chip=3D0x0c018086=0A> rev= =3D0x06 hdr=3D0x01=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporatio= n'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Haswell PCI Express x16 Controll= er'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 =3D bridge=0A>=A0 =A0=A0=A0subclass=A0= =A0=A0=3D PCI-PCI=0A> vgapci1@pci0:0:2:0:=A0 =A0 class=3D0x030000 card=3D0x= fa471179 chip=3D0x04168086=0A> rev=3D0x06 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor= =A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D= 'Haswell Integrated Graphics Controller'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 = =3D display=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D VGA=0A> hdac0@pci0:0:3:0:= =A0 =A0 class=3D0x040300 card=3D0xfa4d1179 chip=3D0x0c0c8086=0A> rev=3D0x06= hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>= =A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Haswell HD Audio Controller'=0A>=A0 = =A0=A0=A0class=A0 =A0 =A0 =3D multimedia=0A>=A0 =A0=A0=A0subclass=A0=A0=A0= =3D HDA=0A> xhci0@pci0:0:20:0:=A0 =A0 class=3D0x0c0330 card=3D0xfa401179 ch= ip=3D0x8c318086=0A> rev=3D0x04 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0= =A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Lynx Poi= nt USB xHCI Host Controller'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 =3D serial bu= s=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D USB=0A> none0@pci0:0:22:0:=A0 =A0 cl= ass=3D0x078000 card=3D0xfa401179 chip=3D0x8c3a8086=0A> rev=3D0x04 hdr=3D0x0= 0=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0= =A0device=A0 =A0=A0=A0=3D 'Lynx Point MEI Controller'=0A>=A0 =A0=A0=A0class= =A0 =A0 =A0 =3D simple comms=0A> ehci0@pci0:0:26:0:=A0 =A0 class=3D0x0c0320= card=3D0xfa401179 chip=3D0x8c2d8086=0A> rev=3D0x04 hdr=3D0x00=0A>=A0 =A0= =A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0device=A0 = =A0=A0=A0=3D 'Lynx Point USB Enhanced Host Controller'=0A>=A0 =A0=A0=A0clas= s=A0 =A0 =A0 =3D serial bus=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D USB=0A> hd= ac1@pci0:0:27:0:=A0 =A0 class=3D0x040300 card=3D0xfa4d1179 chip=3D0x8c20808= 6=0A> rev=3D0x04 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel C= orporation'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Lynx Point High Definit= ion Audio Controller'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 =3D multimedia=0A>= =A0 =A0=A0=A0subclass=A0=A0=A0=3D HDA=0A> pcib2@pci0:0:28:0:=A0 =A0 class= =3D0x060400 card=3D0xfa401179 chip=3D0x8c108086=0A> rev=3D0xd4 hdr=3D0x01= =0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0= =A0device=A0 =A0=A0=A0=3D 'Lynx Point PCI Express Root Port'=0A>=A0 =A0=A0= =A0class=A0 =A0 =A0 =3D bridge=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D PCI-PCI= =0A> pcib3@pci0:0:28:2:=A0 =A0 class=3D0x060400 card=3D0xfa401179 chip=3D0x= 8c148086=0A> rev=3D0xd4 hdr=3D0x01=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D '= Intel Corporation'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Lynx Point PCI E= xpress Root Port'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 =3D bridge=0A>=A0 =A0=A0= =A0subclass=A0=A0=A0=3D PCI-PCI=0A> pcib4@pci0:0:28:3:=A0 =A0 class=3D0x060= 400 card=3D0xfa401179 chip=3D0x8c168086=0A> rev=3D0xd4 hdr=3D0x01=0A>=A0 = =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0device= =A0 =A0=A0=A0=3D 'Lynx Point PCI Express Root Port'=0A>=A0 =A0=A0=A0class= =A0 =A0 =A0 =3D bridge=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D PCI-PCI=0A> ehc= i1@pci0:0:29:0:=A0 =A0 class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c268086= =0A> rev=3D0x04 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Co= rporation'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Lynx Point USB Enhanced = Host Controller'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 =3D serial bus=0A>=A0 =A0= =A0=A0subclass=A0=A0=A0=3D USB=0A> isab0@pci0:0:31:0:=A0 =A0 class=3D0x0601= 00 card=3D0xfa401179 chip=3D0x8c498086=0A> rev=3D0x04 hdr=3D0x00=0A>=A0 =A0= =A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0device=A0 = =A0=A0=A0=3D 'Lynx Point LPC Controller'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 = =3D bridge=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D PCI-ISA=0A> none1@pci0:0:31= :3:=A0 =A0 class=3D0x0c0500 card=3D0xfa401179 chip=3D0x8c228086=0A> rev=3D0= x04 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'Intel Corporation'= =0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Lynx Point SMBus Controller'=0A>= =A0 =A0=A0=A0class=A0 =A0 =A0 =3D serial bus=0A>=A0 =A0=A0=A0subclass=A0=A0= =A0=3D SMBus=0A> atapci0@pci0:0:31:5:=A0 =A0 class=3D0x010185 card=3D0xfa40= 1179 chip=3D0x8c098086=0A> rev=3D0x04 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 = =A0=A0=A0=3D 'Intel Corporation'=0A>=A0 =A0=A0=A0device=A0 =A0=A0=A0=3D 'Ly= nx Point 2-port SATA Controller 2 [IDE mode]'=0A>=A0 =A0=A0=A0class=A0 =A0 = =A0 =3D mass storage=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D ATA=0A> vgapci0@p= ci0:1:0:0:=A0 =A0 class=3D0x030200 card=3D0xfa471179 chip=3D0x129210de=0A> = rev=3D0xa1 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0=A0=A0=3D 'NVIDIA Corpor= ation'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 =3D display=0A>=A0 =A0=A0=A0subclas= s=A0=A0=A0=3D 3D=0A> ath0@pci0:3:0:0:=A0 =A0 class=3D0x028000 card=3D0x0612= 11ad chip=3D0x0036168c=0A> rev=3D0x01 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 = =A0=A0=A0=3D 'Atheros Communications Inc.'=0A>=A0 =A0=A0=A0device=A0 =A0=A0= =A0=3D 'AR9565 Wireless Network Adapter'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 = =3D network=0A> none2@pci0:4:0:0:=A0 =A0 class=3D0x020000 card=3D0xfa401179= chip=3D0x10a11969=0A> rev=3D0x10 hdr=3D0x00=0A>=A0 =A0=A0=A0vendor=A0 =A0= =A0=A0=3D 'Atheros Communications Inc.'=0A>=A0 =A0=A0=A0class=A0 =A0 =A0 = =3D network=0A>=A0 =A0=A0=A0subclass=A0=A0=A0=3D ethernet=0A>=0A>=0A>=0A>= =0A> On 04/08/14 18:29, Adrian Chadd wrote:=0A>> hi,=0A>>=0A>> ok. Can you = please do a pciconf -lv and attach it here?=0A>>=0A>> Oh. Erm, did you comp= ile a kernel from source? is ATH_ENABLE_11N in your kernel?=0A>>=0A>> Do a = 'sysctl dev.ath.0.txagg=3D1' and then paste the output in dmesg here.=0A>>= =0A>>=0A>>=0A>> -a=0A>>=0A>>=0A>> On 8 April 2014 13:38, tzoi516 wrote:=0A>>> OK, killed wpa_supplicant and downed wlan0 and ath0.= After ifconfig ath0=0A>>> up I received a ton of these:=0A>>>=0A>>> ath0: = ath_edma_rxbuf_alloc: nothing on rxbuf?!=0A>>> ath0: ath_edma_rxfifo_alloc:= Q1: alloc failed: i=3D0, nbufs=3D128?=0A>>>=0A>>> received those about 20 = times then this:=0A>>>=0A>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf?= =0A>>>=0A>>> And now the top 2 are slowly scrolling.=0A>>>=0A>>> Mike=0A>>>= =0A>>>=0A>>> On 04/08/14 16:03, Adrian Chadd wrote:=0A>>>> Right. It sounds= like it's not associated.=0A>>>>=0A>>>> Try wlandebug +assoc and then run = wpa_supplicant=0A>>>>=0A>>>>=0A>>>> -a=0A>>>>=0A>>>>=0A>>>> On 8 April 2014= 12:21, tzoi516 wrote:=0A>>>>> Sorry for another email,= the errors are sporadic. I'm trying to find the=0A>>>>> ioctl errors that = I get on shutdown.=0A>>>>> These are after logging in:=0A>>>>>=0A>>>>> ath0= : ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping=0A>>>>> dhclient[1001= ]: send_packet: Invalid argument=0A>>>>> dhclient[1001]: send_packet: No bu= ffer space available=0A>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > = 0; skipping=0A>>>>> dhclient[1001]: send_packet: No buffer space available= =0A>>>>> dhclient[1001]: send_packet: Invalid argument=0A>>>>> dhclient[100= 1]: send_packet: Network is down=0A>>>>>=0A>>>>> Mike=0A>>>>>=0A>>>>> On 04= /08/14 14:38, Adrian Chadd wrote:=0A>>>>>> Ah. Can you post the buffer erro= rs you're seeing?=0A>>>>>>=0A>>>>>>=0A>>>>>> -a=0A>>>>>>=0A>>>>>>=0A>>>>>> = On 8 April 2014 11:37, tzoi516 wrote:=0A>>>>>>> On 04/0= 8/14 14:23, Adrian Chadd wrote:=0A>>>>>>>> It should work fine on -10 and H= EAD. Is it not working fine?=0A>>>>>>>>=0A>>>>>>>>=0A>>>>>>>> -a=0A>>>>>>>>= =0A>>>>>>>>=0A>>>>>>>> On 8 April 2014 09:12, tzoi516 w= rote:=0A>>>>>>>>> I have a Toshiba Satellite S55-A5169=0A>>>>>>>>> This spe= cific one:=0A>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/to= shiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html)=0A= >>>>>>>>>=0A>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi use= s the AR9565. For=0A>>>>>>>>> it to work I have to change the SATA Controll= er Mode in the BIOS from=0A>>>>>>>>> "AHCI" to "Compatibility". I don't kno= w if this information helps, and=0A>>>>>>>>> it's the only AHCI setting I c= an tweak.=0A>>>>>>>>>=0A>>>>>>>>> Mike=0A>>>>>>>>> ________________________= _______________________=0A>>>>>>>>> freebsd-wireless@freebsd.org mailing li= st=0A>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless= =0A>>>>>>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe= @freebsd.org"=0A>>>>>>> With SATA controller mode set to Compatibility then= it works, but a=0A>>>>>>> little wonky at startup - sometimes I'll have to= run wpa_supplicant -i=0A>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequ= ently a buffer error appears.=0A>>>>>>> With SATA controller mode set to AH= CI then I can ifconfig wlan0 list=0A>>>>>>> scan and see available networks= but I can't connect to any except for=0A>>>>>>> unprotected networks.=0A>>= >>>>>=0A>>>>>>> I'm currently running FreeBSD 10.0-STABLE=0A=0A>>>>>>>=0A>>= >>>>> Mike=0A>=0A>=0A> _______________________________________________=0A> = freebsd-wireless@freebsd.org mailing list=0A> http://lists.freebsd.org/mail= man/listinfo/freebsd-wireless=0A> To unsubscribe, send any mail to "freebsd= -wireless-unsubscribe@freebsd.org"=0A______________________________________= _________=0Afreebsd-wireless@freebsd.org mailing list=0Ahttp://lists.freebs= d.org/mailman/listinfo/freebsd-wireless=0ATo unsubscribe, send any mail to = "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 20:43:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 849B783E; Wed, 9 Apr 2014 20:43:59 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FF591CE5; Wed, 9 Apr 2014 20:43:59 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id a108so2978892qge.31 for ; Wed, 09 Apr 2014 13:43:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=KKy7Uu1Ifz3lKc4JteBT4XPhS1ghM266ctx0Qida+74=; b=VzBw6AC42yBardnyDh4S7c0qM5lg0kz/J/ZyIFs0LFFtX4lnOSD6okv8V8r7hKwT5F k3vZcFZMmqbtf/P+StiIv16gR3G/FdAI4XbULfDTaan7XRVUWtj5e9TKZJm3PtX+FvGt JT5XWunksQ5umEO9ulGLpSTSJM3RdazmQPuCCVgE2umdE3Zgirtmi00N/3/HSomYHGQH 7bR1b1EwjWw6F5+clv3M1blZ3+svxP+F/hl2DxzShL2QiI1MyIV3Ihm8kAdCce8kYnCb iHZ4j5whlOasF6f2ApWfoPKuhvdm2+ugddxU7mzjfa683TqK4HTChrfQrIxxSN7QZDco JEEg== X-Received: by 10.140.101.244 with SMTP id u107mr5391507qge.107.1397076238314; Wed, 09 Apr 2014 13:43:58 -0700 (PDT) Received: from lpnix002.local (static-68-239-84-57.washdc.east.verizon.net. [68.239.84.57]) by mx.google.com with ESMTPSA id c2sm3651497qan.4.2014.04.09.13.43.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 13:43:57 -0700 (PDT) Message-ID: <5345B10C.9020408@gmail.com> Date: Wed, 09 Apr 2014 16:43:56 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <53459F44.2010102@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 20:43:59 -0000 My computer is a laptop - the link to it is in my first email. I haven't touched code out of a Windows IDE since the mid-90's, so this might be a good learning experience for me. Thanks. On 04/09/14 15:44, Adrian Chadd wrote: > The driver source is in sys/dev/ath/ and sys/contrib/dev/ath/ath_hal/ar9300/ > > I have all of the linux driver source and the atheros internal driver > source for their AP products but their desktop drivers are .. very > laptop specific and it's hard to get the driver source out of the > relevant group(s). > > > > -a > > > On 9 April 2014 12:28, tzoi516 wrote: >> Hi, >> >> Thanks for all of the help. Where is the driver source code? I'll submit >> a PR today. >> >> Thanks, >> Mike >> >> On 04/09/14 15:02, Adrian Chadd wrote: >>> Hi, >>> >>> The AR9565 is a relatively new chip that hasn't really been thoroughly >>> tested in FreeBSD. Laptop manufacturers have also gone and done some >>> rather silly things to save cost on the wireless NIC itself and I'm >>> not sure those patches / work arounds are in -HEAD. >>> >>> please file a PR with this problem complete with your pciconf -lv >>> output as above. >>> >>> Thanks! >>> >>> >>> -a >>> >>> >>> On 9 April 2014 05:40, tzoi516 wrote: >>>> I'm using the GENERIC kernel. Want me to create a custom kernel? >>>> >>>> pciconf info: >>>> >>>> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >>>> rev=0x06 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell DRAM Controller' >>>> class = bridge >>>> subclass = HOST-PCI >>>> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >>>> rev=0x06 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell PCI Express x16 Controller' >>>> class = bridge >>>> subclass = PCI-PCI >>>> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >>>> rev=0x06 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell Integrated Graphics Controller' >>>> class = display >>>> subclass = VGA >>>> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >>>> rev=0x06 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell HD Audio Controller' >>>> class = multimedia >>>> subclass = HDA >>>> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point USB xHCI Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point MEI Controller' >>>> class = simple comms >>>> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point USB Enhanced Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point High Definition Audio Controller' >>>> class = multimedia >>>> subclass = HDA >>>> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >>>> rev=0xd4 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point PCI Express Root Port' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >>>> rev=0xd4 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point PCI Express Root Port' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >>>> rev=0xd4 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point PCI Express Root Port' >>>> class = bridge >>>> subclass = PCI-PCI >>>> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point USB Enhanced Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point LPC Controller' >>>> class = bridge >>>> subclass = PCI-ISA >>>> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point SMBus Controller' >>>> class = serial bus >>>> subclass = SMBus >>>> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >>>> class = mass storage >>>> subclass = ATA >>>> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >>>> rev=0xa1 hdr=0x00 >>>> vendor = 'NVIDIA Corporation' >>>> class = display >>>> subclass = 3D >>>> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >>>> rev=0x01 hdr=0x00 >>>> vendor = 'Atheros Communications Inc.' >>>> device = 'AR9565 Wireless Network Adapter' >>>> class = network >>>> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >>>> rev=0x10 hdr=0x00 >>>> vendor = 'Atheros Communications Inc.' >>>> class = network >>>> subclass = ethernet >>>> >>>> >>>> >>>> >>>> On 04/08/14 18:29, Adrian Chadd wrote: >>>>> hi, >>>>> >>>>> ok. Can you please do a pciconf -lv and attach it here? >>>>> >>>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >>>>> >>>>> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >>>>> >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 13:38, tzoi516 wrote: >>>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>>>>> up I received a ton of these: >>>>>> >>>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>>>>> >>>>>> received those about 20 times then this: >>>>>> >>>>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>>>> >>>>>> And now the top 2 are slowly scrolling. >>>>>> >>>>>> Mike >>>>>> >>>>>> >>>>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>>>> Right. It sounds like it's not associated. >>>>>>> >>>>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> >>>>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>>>>> ioctl errors that I get on shutdown. >>>>>>>> These are after logging in: >>>>>>>> >>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>>> dhclient[1001]: send_packet: Network is down >>>>>>>> >>>>>>>> Mike >>>>>>>> >>>>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>>>> >>>>>>>>> >>>>>>>>> -a >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -a >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>>>> This specific one: >>>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>>>> >>>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>>>> >>>>>>>>>>>> Mike >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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" >>>>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>>>>> scan and see available networks but I can't connect to any except for >>>>>>>>>> unprotected networks. >>>>>>>>>> >>>>>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>>>>> >>>>>>>>>> Mike >>>> _______________________________________________ >>>> 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 Wed Apr 9 21:18:42 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 771E9962 for ; Wed, 9 Apr 2014 21:18:42 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36EEE118B for ; Wed, 9 Apr 2014 21:18:42 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id 63so2843004qgz.19 for ; Wed, 09 Apr 2014 14:18: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=X4H4Jhu3jPokgcnavV21rtnMkcmASRzE5UAR7sWIsrk=; b=XHep9Fu3VBWUk9wLkaBwwEf3f+SwXkBajrI+3xMsoCPhdTPtYDAy1Jq/1A1UjqMBKw KQEhnTJS6yqg8uly/kHF6pj0JVF+2lWbqgz43LFU7d2wnrq2vsz7NQYrJIfzPB930zg/ QDVcLbsS/Amw3Ki+3rImadjhyEJ/6Two61Zou1v5EJClEhYHa712iwJURM4WPlvEi29z v4qeiTSpnHgwVO4zo8XQSBoDbtW2B6Cb++VAZ3fR85zujpPJif0D/FZwqMR54Kb6LIY+ VDZRvt92JoWpNMpUaKDYEOxsgH+R9KXKK2c+Vc7xF4o4ej3usl/kGmRMVXzpJQF7sN4b c/ZA== MIME-Version: 1.0 X-Received: by 10.140.42.38 with SMTP id b35mr14774197qga.87.1397078321389; Wed, 09 Apr 2014 14:18:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Wed, 9 Apr 2014 14:18:41 -0700 (PDT) In-Reply-To: <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> Date: Wed, 9 Apr 2014 14:18:41 -0700 X-Google-Sender-Auth: x5Qc6tuRAMHUdp72v86oaJtU77E Message-ID: Subject: Re: Re: Atheros AR9565 From: Adrian Chadd To: Anthony Jenkins Content-Type: text/plain; charset=ISO-8859-1 Cc: tzoi516 , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Apr 2014 21:18:42 -0000 Which HP laptop? -a On 9 April 2014 13:35, Anthony Jenkins wrote: > Hey, I've got one of these babies in my HP laptop; I actually posted some problems I was having to the list back in Aug. '13. I could loan you mine and/or assist with debugging if I can have it back (can make do with an external wireless device). > > > Anthony > > > ________________________________ > From: Adrian Chadd > To: tzoi516 > Cc: "freebsd-wireless@freebsd.org" > Sent: Wednesday, April 9, 2014 3:02 PM > Subject: Re: Re: Atheros AR9565 > > > Hi, > > The AR9565 is a relatively new chip that hasn't really been thoroughly > tested in FreeBSD. Laptop manufacturers have also gone and done some > rather silly things to save cost on the wireless NIC itself and I'm > not sure those patches / work arounds are in -HEAD. > > please file a PR with this problem complete with your pciconf -lv > output as above. > > Thanks! > > > -a > > > On 9 April 2014 05:40, tzoi516 wrote: >> I'm using the GENERIC kernel. Want me to create a custom kernel? >> >> pciconf info: >> >> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell DRAM Controller' >> class = bridge >> subclass = HOST-PCI >> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >> rev=0x06 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Haswell PCI Express x16 Controller' >> class = bridge >> subclass = PCI-PCI >> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell Integrated Graphics Controller' >> class = display >> subclass = VGA >> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell HD Audio Controller' >> class = multimedia >> subclass = HDA >> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB xHCI Host Controller' >> class = serial bus >> subclass = USB >> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point MEI Controller' >> class = simple comms >> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB Enhanced Host Controller' >> class = serial bus >> subclass = USB >> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point High Definition Audio Controller' >> class = multimedia >> subclass = HDA >> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB Enhanced Host Controller' >> class = serial bus >> subclass = USB >> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point LPC Controller' >> class = bridge >> subclass = PCI-ISA >> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point SMBus Controller' >> class = serial bus >> subclass = SMBus >> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >> class = mass storage >> subclass = ATA >> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >> rev=0xa1 hdr=0x00 >> vendor = 'NVIDIA Corporation' >> class = display >> subclass = 3D >> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR9565 Wireless Network Adapter' >> class = network >> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >> rev=0x10 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> class = network >> subclass = ethernet >> >> >> >> >> On 04/08/14 18:29, Adrian Chadd wrote: >>> hi, >>> >>> ok. Can you please do a pciconf -lv and attach it here? >>> >>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >>> >>> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >>> >>> >>> >>> -a >>> >>> >>> On 8 April 2014 13:38, tzoi516 wrote: >>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>>> up I received a ton of these: >>>> >>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>>> >>>> received those about 20 times then this: >>>> >>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>> >>>> And now the top 2 are slowly scrolling. >>>> >>>> Mike >>>> >>>> >>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>> Right. It sounds like it's not associated. >>>>> >>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>>> ioctl errors that I get on shutdown. >>>>>> These are after logging in: >>>>>> >>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>> dhclient[1001]: send_packet: Network is down >>>>>> >>>>>> Mike >>>>>> >>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> >>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>> >>>>>>>>> >>>>>>>>> -a >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>> This specific one: >>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>> >>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>> >>>>>>>>>> Mike >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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" >>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>>> scan and see available networks but I can't connect to any except for >>>>>>>> unprotected networks. >>>>>>>> >>>>>>>> I'm currently running FreeBSD 10.0-STABLE > >>>>>>>> >>>>>>>> Mike >> >> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 10 02:59:25 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74553588 for ; Thu, 10 Apr 2014 02:59:25 +0000 (UTC) Received: from nm24-vm0.bullet.mail.bf1.yahoo.com (nm24-vm0.bullet.mail.bf1.yahoo.com [98.139.213.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F8D714C2 for ; Thu, 10 Apr 2014 02:59:24 +0000 (UTC) Received: from [66.196.81.174] by nm24.bullet.mail.bf1.yahoo.com with NNFMP; 10 Apr 2014 02:59:17 -0000 Received: from [98.139.212.206] by tm20.bullet.mail.bf1.yahoo.com with NNFMP; 10 Apr 2014 02:59:17 -0000 Received: from [127.0.0.1] by omp1015.mail.bf1.yahoo.com with NNFMP; 10 Apr 2014 02:59:17 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 910160.26326.bm@omp1015.mail.bf1.yahoo.com Received: (qmail 35252 invoked by uid 60001); 10 Apr 2014 02:59:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1397098757; bh=7nls3LM7YTdkltwS7NzuWV0xf8wjBQkdKDoY0bl7p5k=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=fe6r9IN+oUchBstTxkxFOUvt/H9iEP527AGxuqyNEs049OqnuXYdAS4EzhwtTrDYvMWlTE3vbfue7FRiQh6b/WRXaxy/PsSKodVPdevkh6yeuRK2Z4Z7TaRjyoEWe6VwkUxDggS1hQv1y1f1m2PU+QGpelCVtNY/MzFCJsoF+Uk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=sJ11ZzxTzBsxn6ezH72G1NRx6ZmYqejKGZuEm087e3uvL5ptRAaoyAMx8QofAW23C7KvvJYjleSQD+qEHfjZyoMuUTX6K9W52e4bTk+/WEC93mM4Ls78YlgNIdWbAJ8+t3KtOOr60uuEFqwYVQm+Q1cu7FLHSbfwaKf4XVW5dU4=; X-YMail-OSG: aw3wQw8VM1lekOy8_xMV7ttwYoNGmQpYnu_PNCIPB0t8xSW WZd0XxkEgyvyAsT.r0sR0Vqdp1v99W8JlXuSwRgtMr75XPe5sPTuY2nWDnRN SojUMW26rwtzV6mH5BGqnT6WQ9EzFbKCKuihdxQa_CGVJUQ5GhgXYYNYp7DD KOTU1xhLzG4_UPvs4q_xY_763PLS4FNoBLLbsIrGiY7O751_kqN4fSMZBEPR mk3t.L.xAgP9nt_pSsKSfHKWWkr7szX2k2BgV2W5qAguQekN306zbH0Koqxd HXdUG.QGgtnBivCsAwINVM590MIpLcCKlQWpN.vvOr6wB.gn0lxwxYLdnN5U bc_r6yptUuG50NpeInF_rXzsUOVQc440ZMztGJ_3jx0KC4Va8xwjLI4IHxi2 EhxFJb.YhmCR3_zYKzPRu6oU3LvjqwRSaWqlsYG_4GYGYpJfBY3KKCpQTvRF tSFTYd0r_AJMc32EfiZgPVyGE12dHGmOC4PWNakErHCz_NIYqx_JZrxAquN6 Izs.kKS2RPaSEFccVRiUCs9MbBAL_jyQUA9T1CMVqyM52fRrHNIaian_Mktv NUV3eshACm3KidA2L0tYbgDywXh9TGRrrPFHYzFn76Hb.cS8vtUIFin4oHxR YSraso6Py3e7TCAzFChJLbsrmJ3_wZ_U6HqHddJmia2N5h.qKbhTbcL908wi 2pYOgERcMf6d.glFCm06iL2a40Dk4J3OY9I4pJOjQwcfTqNOgxGiI0SyoSTC wlRzQTkoSoKeHCz6dFbpRX_eg0jgQnWnRTJw8gQCVKzZ3mirrYE1A.n8YQPY 6qB1oGKe7izhj4pZY1aMfJGXyoesiGXPoDqIVpp.XV05wav86OAOZER6wumw - Received: from [99.62.101.19] by web140705.mail.bf1.yahoo.com via HTTP; Wed, 09 Apr 2014 19:59:17 PDT X-Rocket-MIMEInfo: 002.001, SFAgRU5WWSA2Wi0xMTAwIFNsZWVrYm9vawpodHRwOi8vaDEwMDI1Lnd3dzEuaHAuY29tL2V3ZnJmL3djL3Byb2R1Y3Q_Y2M9dXMmZGxjPWVuJmxjPWVuJnByb2R1Y3Q9NTMzMDEyMgoKCkFudGhvbnkKCgoKLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQpGcm9tOiBBZHJpYW4gQ2hhZGQgPGFkcmlhbkBmcmVlYnNkLm9yZz4KVG86IEFudGhvbnkgSmVua2lucyA8c2Nvb2JpX2Rvb0B5YWhvby5jb20.CkNjOiB0em9pNTE2IDx0em9pNTE2QGdtYWlsLmNvbT47ICJmcmVlYnNkLXdpcmVsZXNzQGZyZWVic2Qub3IBMAEBAQE- X-Mailer: YahooMailWebService/0.8.182.648 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> Message-ID: <1397098757.32711.YahooMailNeo@web140705.mail.bf1.yahoo.com> Date: Wed, 9 Apr 2014 19:59:17 -0700 (PDT) From: Anthony Jenkins Subject: Re: Re: Atheros AR9565 To: Adrian Chadd In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: tzoi516 , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Anthony Jenkins 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, 10 Apr 2014 02:59:25 -0000 HP ENVY 6Z-1100 Sleekbook=0Ahttp://h10025.www1.hp.com/ewfrf/wc/product?cc= =3Dus&dlc=3Den&lc=3Den&product=3D5330122=0A=0A=0AAnthony=0A=0A=0A=0A----- O= riginal Message -----=0AFrom: Adrian Chadd =0ATo: Antho= ny Jenkins =0ACc: tzoi516 ; "freeb= sd-wireless@freebsd.org" =0ASent: Wednesday, = April 9, 2014 5:18 PM=0ASubject: Re: Re: Atheros AR9565=0A=0AWhich HP lapto= p?=0A=0A=0A-a=0A=0A=0A=0AOn 9 April 2014 13:35, Anthony Jenkins wrote:=0A> Hey, I've got one of these babies in my HP laptop; I= actually posted some problems I was having to the list back in Aug. '13.= =A0 I could loan you mine and/or assist with debugging if I can have it bac= k (can make do with an external wireless device).=0A>=0A>=0A> Anthony=0A>= =0A>=0A> ________________________________=0A> From: Adrian Chadd =0A> To: tzoi516 =0A> Cc: "freebsd-wireless@fr= eebsd.org" =0A> Sent: Wednesday, April 9, 201= 4 3:02 PM=0A> Subject: Re: Re: Atheros AR9565=0A>=0A>=0A> Hi,=0A>=0A> The A= R9565 is a relatively new chip that hasn't really been thoroughly=0A> teste= d in FreeBSD. Laptop manufacturers have also gone and done some=0A> rather = silly things to save cost on the wireless NIC itself and I'm=0A> not sure t= hose patches / work arounds are in -HEAD.=0A>=0A> please file a PR with thi= s problem complete with your pciconf -lv=0A> output as above.=0A>=0A> Thank= s!=0A>=0A>=0A> -a=0A>=0A>=0A> On 9 April 2014 05:40, tzoi516 wrote:=0A>> I'm using the GENERIC kernel. Want me to create a custom = kernel?=0A>>=0A>> pciconf info:=0A>>=0A>> hostb0@pci0:0:0:0:=A0 =A0 class= =3D0x060000 card=3D0xfa401179 chip=3D0x0c048086=0A>> rev=3D0x06 hdr=3D0x00= =0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 =A0 device=A0= =A0 =3D 'Haswell DRAM Controller'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D bridg= e=0A>>=A0 =A0 subclass=A0 =3D HOST-PCI=0A>> pcib1@pci0:0:1:0:=A0 =A0 clas= s=3D0x060400 card=3D0xfa471179 chip=3D0x0c018086=0A>> rev=3D0x06 hdr=3D0x01= =0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 =A0 device=A0= =A0 =3D 'Haswell PCI Express x16 Controller'=0A>>=A0 =A0 class=A0 =A0 = =A0 =3D bridge=0A>>=A0 =A0 subclass=A0 =3D PCI-PCI=0A>> vgapci1@pci0:0:2:= 0:=A0 =A0 class=3D0x030000 card=3D0xfa471179 chip=3D0x04168086=0A>> rev=3D0= x06 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 = =A0 device=A0 =A0 =3D 'Haswell Integrated Graphics Controller'=0A>>=A0 = =A0 class=A0 =A0 =A0 =3D display=0A>>=A0 =A0 subclass=A0 =3D VGA=0A>> hd= ac0@pci0:0:3:0:=A0 =A0 class=3D0x040300 card=3D0xfa4d1179 chip=3D0x0c0c8086= =0A>> rev=3D0x06 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporat= ion'=0A>>=A0 =A0 device=A0 =A0 =3D 'Haswell HD Audio Controller'=0A>>=A0 = =A0 class=A0 =A0 =A0 =3D multimedia=0A>>=A0 =A0 subclass=A0 =3D HDA=0A>>= xhci0@pci0:0:20:0:=A0 =A0 class=3D0x0c0330 card=3D0xfa401179 chip=3D0x8c31= 8086=0A>> rev=3D0x04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corp= oration'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point USB xHCI Host Controll= er'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D serial bus=0A>>=A0 =A0 subclass=A0 = =3D USB=0A>> none0@pci0:0:22:0:=A0 =A0 class=3D0x078000 card=3D0xfa401179 c= hip=3D0x8c3a8086=0A>> rev=3D0x04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D= 'Intel Corporation'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point MEI Contro= ller'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D simple comms=0A>> ehci0@pci0:0:26:0= :=A0 =A0 class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c2d8086=0A>> rev=3D0x= 04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 = =A0 device=A0 =A0 =3D 'Lynx Point USB Enhanced Host Controller'=0A>>=A0 = =A0 class=A0 =A0 =A0 =3D serial bus=0A>>=A0 =A0 subclass=A0 =3D USB=0A>>= hdac1@pci0:0:27:0:=A0 =A0 class=3D0x040300 card=3D0xfa4d1179 chip=3D0x8c20= 8086=0A>> rev=3D0x04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corp= oration'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point High Definition Audio = Controller'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D multimedia=0A>>=A0 =A0 subcl= ass=A0 =3D HDA=0A>> pcib2@pci0:0:28:0:=A0 =A0 class=3D0x060400 card=3D0xfa= 401179 chip=3D0x8c108086=0A>> rev=3D0xd4 hdr=3D0x01=0A>>=A0 =A0 vendor=A0 = =A0 =3D 'Intel Corporation'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point PC= I Express Root Port'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D bridge=0A>>=A0 =A0 = subclass=A0 =3D PCI-PCI=0A>> pcib3@pci0:0:28:2:=A0 =A0 class=3D0x060400 ca= rd=3D0xfa401179 chip=3D0x8c148086=0A>> rev=3D0xd4 hdr=3D0x01=0A>>=A0 =A0 v= endor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx= Point PCI Express Root Port'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D bridge=0A>>= =A0 =A0 subclass=A0 =3D PCI-PCI=0A>> pcib4@pci0:0:28:3:=A0 =A0 class=3D0x= 060400 card=3D0xfa401179 chip=3D0x8c168086=0A>> rev=3D0xd4 hdr=3D0x01=0A>>= =A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 =A0 device=A0 =A0 = =3D 'Lynx Point PCI Express Root Port'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D b= ridge=0A>>=A0 =A0 subclass=A0 =3D PCI-PCI=0A>> ehci1@pci0:0:29:0:=A0 =A0 = class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c268086=0A>> rev=3D0x04 hdr=3D= 0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'=0A>>=A0 =A0 devic= e=A0 =A0 =3D 'Lynx Point USB Enhanced Host Controller'=0A>>=A0 =A0 class= =A0 =A0 =A0 =3D serial bus=0A>>=A0 =A0 subclass=A0 =3D USB=0A>> isab0@pci= 0:0:31:0:=A0 =A0 class=3D0x060100 card=3D0xfa401179 chip=3D0x8c498086=0A>> = rev=3D0x04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporation'= =0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point LPC Controller'=0A>>=A0 =A0 c= lass=A0 =A0 =A0 =3D bridge=0A>>=A0 =A0 subclass=A0 =3D PCI-ISA=0A>> none1= @pci0:0:31:3:=A0 =A0 class=3D0x0c0500 card=3D0xfa401179 chip=3D0x8c228086= =0A>> rev=3D0x04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel Corporat= ion'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point SMBus Controller'=0A>>=A0 = =A0 class=A0 =A0 =A0 =3D serial bus=0A>>=A0 =A0 subclass=A0 =3D SMBus=0A= >> atapci0@pci0:0:31:5:=A0 =A0 class=3D0x010185 card=3D0xfa401179 chip=3D0x= 8c098086=0A>> rev=3D0x04 hdr=3D0x00=0A>>=A0 =A0 vendor=A0 =A0 =3D 'Intel = Corporation'=0A>>=A0 =A0 device=A0 =A0 =3D 'Lynx Point 2-port SATA Contro= ller 2 [IDE mode]'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D mass storage=0A>>=A0 = =A0 subclass=A0 =3D ATA=0A>> vgapci0@pci0:1:0:0:=A0 =A0 class=3D0x030200 = card=3D0xfa471179 chip=3D0x129210de=0A>> rev=3D0xa1 hdr=3D0x00=0A>>=A0 =A0 = vendor=A0 =A0 =3D 'NVIDIA Corporation'=0A>>=A0 =A0 class=A0 =A0 =A0 =3D = display=0A>>=A0 =A0 subclass=A0 =3D 3D=0A>> ath0@pci0:3:0:0:=A0 =A0 class= =3D0x028000 card=3D0x061211ad chip=3D0x0036168c=0A>> rev=3D0x01 hdr=3D0x00= =0A>>=A0 =A0 vendor=A0 =A0 =3D 'Atheros Communications Inc.'=0A>>=A0 =A0 = device=A0 =A0 =3D 'AR9565 Wireless Network Adapter'=0A>>=A0 =A0 class=A0= =A0 =A0 =3D network=0A>> none2@pci0:4:0:0:=A0 =A0 class=3D0x020000 card=3D= 0xfa401179 chip=3D0x10a11969=0A>> rev=3D0x10 hdr=3D0x00=0A>>=A0 =A0 vendor= =A0 =A0 =3D 'Atheros Communications Inc.'=0A>>=A0 =A0 class=A0 =A0 =A0 = =3D network=0A>>=A0 =A0 subclass=A0 =3D ethernet=0A>>=0A>>=0A>>=0A>>=0A>>= On 04/08/14 18:29, Adrian Chadd wrote:=0A>>> hi,=0A>>>=0A>>> ok. Can you p= lease do a pciconf -lv and attach it here?=0A>>>=0A>>> Oh. Erm, did you com= pile a kernel from source? is ATH_ENABLE_11N in your kernel?=0A>>>=0A>>> Do= a 'sysctl dev.ath.0.txagg=3D1' and then paste the output in dmesg here.=0A= >>>=0A>>>=0A>>>=0A>>> -a=0A>>>=0A>>>=0A>>> On 8 April 2014 13:38, tzoi516 <= tzoi516@gmail.com> wrote:=0A>>>> OK, killed wpa_supplicant and downed wlan0= and ath0. After ifconfig ath0=0A>>>> up I received a ton of these:=0A>>>>= =0A>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?!=0A>>>> ath0: ath_edm= a_rxfifo_alloc: Q1: alloc failed: i=3D0, nbufs=3D128?=0A>>>>=0A>>>> receive= d those about 20 times then this:=0A>>>>=0A>>>> ath0: ath_edma_recv_proc_qu= eue: Q1: NULL bf?=0A>>>>=0A>>>> And now the top 2 are slowly scrolling.=0A>= >>>=0A>>>> Mike=0A>>>>=0A>>>>=0A>>>> On 04/08/14 16:03, Adrian Chadd wrote:= =0A>>>>> Right. It sounds like it's not associated.=0A>>>>>=0A>>>>> Try wla= ndebug +assoc and then run wpa_supplicant=0A>>>>>=0A>>>>>=0A>>>>> -a=0A>>>>= >=0A>>>>>=0A>>>>> On 8 April 2014 12:21, tzoi516 wrote:= =0A>>>>>> Sorry for another email, the errors are sporadic. I'm trying to f= ind the=0A>>>>>> ioctl errors that I get on shutdown.=0A>>>>>> These are af= ter logging in:=0A>>>>>>=0A>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_c= nt > 0; skipping=0A>>>>>> dhclient[1001]: send_packet: Invalid argument=0A>= >>>>> dhclient[1001]: send_packet: No buffer space available=0A>>>>>> ath0:= ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping=0A>>>>>> dhclient[1001= ]: send_packet: No buffer space available=0A>>>>>> dhclient[1001]: send_pac= ket: Invalid argument=0A>>>>>> dhclient[1001]: send_packet: Network is down= =0A>>>>>>=0A>>>>>> Mike=0A>>>>>>=0A>>>>>> On 04/08/14 14:38, Adrian Chadd w= rote:=0A>>>>>>> Ah. Can you post the buffer errors you're seeing?=0A>>>>>>>= =0A>>>>>>>=0A>>>>>>> -a=0A>>>>>>>=0A>>>>>>>=0A>>>>>>> On 8 April 2014 11:37= , tzoi516 wrote:=0A>>>>>>>> On 04/08/14 14:23, Adrian C= hadd wrote:=0A>>>>>>>>> It should work fine on -10 and HEAD. Is it not work= ing fine?=0A>>>>>>>>>=0A>>>>>>>>>=0A>>>>>>>>> -a=0A>>>>>>>>>=0A>>>>>>>>>=0A= >>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote:=0A>>>>>= >>>>> I have a Toshiba Satellite S55-A5169=0A>>>>>>>>>> This specific one:= =0A>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_psk= k6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html)=0A>>>>>>>>>= >=0A>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the A= R9565. For=0A>>>>>>>>>> it to work I have to change the SATA Controller Mod= e in the BIOS from=0A>>>>>>>>>> "AHCI" to "Compatibility". I don't know if = this information helps, and=0A>>>>>>>>>> it's the only AHCI setting I can t= weak.=0A>>>>>>>>>>=0A>>>>>>>>>> Mike=0A>>>>>>>>>> _________________________= ______________________=0A>>>>>>>>>> freebsd-wireless@freebsd.org mailing li= st=0A>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless= =0A>>>>>>>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscrib= e@freebsd.org"=0A>>>>>>>> With SATA controller mode set to Compatibility th= en it works, but a=0A>>>>>>>> little wonky at startup - sometimes I'll have= to run wpa_supplicant -i=0A>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Inf= requently a buffer error appears.=0A>>>>>>>> With SATA controller mode set = to AHCI then I can ifconfig wlan0 list=0A>>>>>>>> scan and see available ne= tworks but I can't connect to any except for=0A>>>>>>>> unprotected network= s.=0A>>>>>>>>=0A>>>>>>>> I'm currently running FreeBSD 10.0-STABLE=0A>=0A>>= >>>>>>=0A>>>>>>>> Mike=0A>>=0A>>=0A>> _____________________________________= __________=0A>> freebsd-wireless@freebsd.org mailing list=0A>> http://lists= .freebsd.org/mailman/listinfo/freebsd-wireless=0A>> To unsubscribe, send an= y mail to "freebsd-wireless-unsubscribe@freebsd.org"=0A> __________________= _____________________________=0A> freebsd-wireless@freebsd.org mailing list= =0A> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless=0A> To unsu= bscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"=0A From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 10 13:06:21 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B3FD7CB2 for ; Thu, 10 Apr 2014 13:06:21 +0000 (UTC) Received: from nm49-vm3.bullet.mail.bf1.yahoo.com (nm49-vm3.bullet.mail.bf1.yahoo.com [216.109.115.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 639831105 for ; Thu, 10 Apr 2014 13:06:21 +0000 (UTC) Received: from [66.196.81.174] by nm49.bullet.mail.bf1.yahoo.com with NNFMP; 10 Apr 2014 12:59:54 -0000 Received: from [68.142.230.70] by tm20.bullet.mail.bf1.yahoo.com with NNFMP; 10 Apr 2014 12:59:54 -0000 Received: from [127.0.0.1] by smtp227.mail.bf1.yahoo.com with NNFMP; 10 Apr 2014 12:59:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1397134794; bh=olL35eMi9krmGvoASLpRW8MsBWaeVsNt3Y4SsBo1mnk=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=s/BnxHE5SWm7MSbLnlfkAe7J1AumqonVJVreNSFiw10QUVol62umwJAvVflzE9Pv8DEHXvPaMytxK7vnjeCasO6Do1WyH/gibyy7qBaho9iitHl0MxvCdKoTX9Msl3McWojBrsS0aNyjwtWWtnZUXDt9sv4aYnOOeHCfZ1juMvE= X-Yahoo-Newman-Id: 105677.6774.bm@smtp227.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: l2msW2QVM1mL6YreLg2xlE6.lTnwZLiEJtlES_VUYJJqDsY SUNYRpL7W.u3yDI9oXbSBjly4KdfEgrKEK2Byt7HCx05Spd34VcykVVbsf6a lhb6764708CsUGWhl_KU_2hIfWGBpyHWY9h.5qvP1RuYapW_4oTYupMeugF8 EKlCHGSy51Hi4MHnXOgSvllbEAgYM0Nll6NaDxOoZ_TkxLVLj5BEFV9d60V5 oGgaRWxbiDlvlEembHcF2pE0E5tNDbd3Iv1WLczp28IHcNzd5VKZe8RN8OA2 53PwVRA9M1fVbdzh8KGT.TBYDY_5mD9MYjp3w6UFWgQy4gHZ_1qNfGh4qEHl kPMRo2Go4ghPWU24.ZZtMhjJ89QKJIoHJwvgPT81sRtGiVuYs_KYsEDTyHjG OsmaGtIyqJsyPJxFg3zVeft3TPnD.JriwjnoG5qsJv9BHfgMtl409XPlb3cV ax_xQSLwDqxuE_jw1awdsvM.dPB3_IUKr1hwtjwTXZ.V8pm05SoT5JJ1IYav PHPg8eW.JoTZSm8ABxx0R0ncazuPgEjBXYPNKHawUYaEQAUy0CKmf7olGf9d BkknGqIG2ZEgUrqkvZkkNrn_MKk2hlzjoefn5Jyemer81Ucf1AriYghUhiLk dmcp_8XNUqbLCyJD_fIONAtjKfB3gpfeGUq81CXTqI2Y55wtUE585EiV3rVQ f8daTSms6kN.QfMmWBnPmUDpcdhPaybh.4co.uBuJFh9NGcN3ww-- X-Yahoo-SMTP: 9sPoSQ2swBBlERuQ.0vs8XLc_MeClW0- X-Rocket-Received: from [10.0.1.147] (Scoobi_doo@70.90.74.161 with plain [98.138.105.21]) by smtp227.mail.bf1.yahoo.com with SMTP; 10 Apr 2014 12:59:54 +0000 UTC Message-ID: <534695C8.8000802@yahoo.com> Date: Thu, 10 Apr 2014 08:59:52 -0400 From: Anthony Jenkins User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: tzoi516 , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Apr 2014 13:06:21 -0000 HP ENVY 6Z-1100 Sleekbook Sorry, tried replying with a URL to HP's product website, but must've gotten blocked. Also my original (brief) email thread on my AR9565 was in July '13, not August. Anthony On 04/09/2014 05:18 PM, Adrian Chadd wrote: > Which HP laptop? > > > -a > > > On 9 April 2014 13:35, Anthony Jenkins wrote: >> Hey, I've got one of these babies in my HP laptop; I actually posted some problems I was having to the list back in Aug. '13. I could loan you mine and/or assist with debugging if I can have it back (can make do with an external wireless device). >> >> >> Anthony >> >> >> ________________________________ >> From: Adrian Chadd >> To: tzoi516 >> Cc: "freebsd-wireless@freebsd.org" >> Sent: Wednesday, April 9, 2014 3:02 PM >> Subject: Re: Re: Atheros AR9565 >> >> >> Hi, >> >> The AR9565 is a relatively new chip that hasn't really been thoroughly >> tested in FreeBSD. Laptop manufacturers have also gone and done some >> rather silly things to save cost on the wireless NIC itself and I'm >> not sure those patches / work arounds are in -HEAD. >> >> please file a PR with this problem complete with your pciconf -lv >> output as above. >> >> Thanks! >> >> >> -a >> >> >> On 9 April 2014 05:40, tzoi516 wrote: >>> I'm using the GENERIC kernel. Want me to create a custom kernel? >>> >>> pciconf info: >>> >>> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >>> rev=0x06 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Haswell DRAM Controller' >>> class = bridge >>> subclass = HOST-PCI >>> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >>> rev=0x06 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Haswell PCI Express x16 Controller' >>> class = bridge >>> subclass = PCI-PCI >>> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >>> rev=0x06 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Haswell Integrated Graphics Controller' >>> class = display >>> subclass = VGA >>> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >>> rev=0x06 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Haswell HD Audio Controller' >>> class = multimedia >>> subclass = HDA >>> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point USB xHCI Host Controller' >>> class = serial bus >>> subclass = USB >>> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point MEI Controller' >>> class = simple comms >>> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point USB Enhanced Host Controller' >>> class = serial bus >>> subclass = USB >>> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point High Definition Audio Controller' >>> class = multimedia >>> subclass = HDA >>> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >>> rev=0xd4 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point PCI Express Root Port' >>> class = bridge >>> subclass = PCI-PCI >>> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >>> rev=0xd4 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point PCI Express Root Port' >>> class = bridge >>> subclass = PCI-PCI >>> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >>> rev=0xd4 hdr=0x01 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point PCI Express Root Port' >>> class = bridge >>> subclass = PCI-PCI >>> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point USB Enhanced Host Controller' >>> class = serial bus >>> subclass = USB >>> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point LPC Controller' >>> class = bridge >>> subclass = PCI-ISA >>> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point SMBus Controller' >>> class = serial bus >>> subclass = SMBus >>> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >>> rev=0x04 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >>> class = mass storage >>> subclass = ATA >>> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >>> rev=0xa1 hdr=0x00 >>> vendor = 'NVIDIA Corporation' >>> class = display >>> subclass = 3D >>> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >>> rev=0x01 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> device = 'AR9565 Wireless Network Adapter' >>> class = network >>> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >>> rev=0x10 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> class = network >>> subclass = ethernet >>> >>> >>> >>> >>> On 04/08/14 18:29, Adrian Chadd wrote: >>>> hi, >>>> >>>> ok. Can you please do a pciconf -lv and attach it here? >>>> >>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >>>> >>>> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >>>> >>>> >>>> >>>> -a >>>> >>>> >>>> On 8 April 2014 13:38, tzoi516 wrote: >>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>>>> up I received a ton of these: >>>>> >>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>>>> >>>>> received those about 20 times then this: >>>>> >>>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>>> >>>>> And now the top 2 are slowly scrolling. >>>>> >>>>> Mike >>>>> >>>>> >>>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>>> Right. It sounds like it's not associated. >>>>>> >>>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>>>> ioctl errors that I get on shutdown. >>>>>>> These are after logging in: >>>>>>> >>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>> dhclient[1001]: send_packet: Network is down >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -a >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>>> This specific one: >>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>>> >>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>>> >>>>>>>>>>> Mike >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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" >>>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>>>> scan and see available networks but I can't connect to any except for >>>>>>>>> unprotected networks. >>>>>>>>> >>>>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>>>> Mike >>> >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 10 16:25:01 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 541F428B for ; Thu, 10 Apr 2014 16:25:01 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 123F9165E for ; Thu, 10 Apr 2014 16:25:01 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id m20so4711472qcx.10 for ; Thu, 10 Apr 2014 09:25:00 -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=jTEtcKacsNKnzioDzKiDWyJOMK9VI0/51+lvnQVphMs=; b=tyB+7SiGLCwmC6zv6J0N7TqD5Un7KdR1SpDRhkAvFvRgS4t6K4jgxqxup0b26xckcW /81KgmnF8UTX096QLSf8vML+z5zo10pGgOfIKgBkSsLk0RBf6+D+6WnmGCDST8shKFji RoqSGMDMske8dmiR2pFHajc7s685PgZ98+ympLtsYDJ0h1ATpD9ml+DSfdcBv0HTjm3w ZJpmp24hTJ/X5jRrkvkkIia9xtnsXWrJadB3koKGuO/bBN6Jxtfmq6/VOHliU8r7MIDD LENmeVw+bdc+Yjy8fxVQCWx5PAUb1pnmau+zI3lINmu9xDY/VOLpzdS0xE3z26ix3m3e fYtQ== MIME-Version: 1.0 X-Received: by 10.224.50.211 with SMTP id a19mr22040414qag.49.1397147100184; Thu, 10 Apr 2014 09:25:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Thu, 10 Apr 2014 09:25:00 -0700 (PDT) In-Reply-To: <534695C8.8000802@yahoo.com> References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> <534695C8.8000802@yahoo.com> Date: Thu, 10 Apr 2014 09:25:00 -0700 X-Google-Sender-Auth: HXAVaTG-oWm4UqdnitiVYmZe_R8 Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: Anthony Jenkins Content-Type: text/plain; charset=ISO-8859-1 Cc: tzoi516 , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Apr 2014 16:25:01 -0000 Hm, I think someone needs to buy me one of these. The AR9565 that I had tried on worked fine. -a On 10 April 2014 05:59, Anthony Jenkins wrote: > HP ENVY 6Z-1100 Sleekbook > > Sorry, tried replying with a URL to HP's product website, but must've gotten blocked. Also my original (brief) email thread on my AR9565 was in July '13, not August. > > Anthony > > On 04/09/2014 05:18 PM, Adrian Chadd wrote: >> Which HP laptop? >> >> >> -a >> >> >> On 9 April 2014 13:35, Anthony Jenkins wrote: >>> Hey, I've got one of these babies in my HP laptop; I actually posted some problems I was having to the list back in Aug. '13. I could loan you mine and/or assist with debugging if I can have it back (can make do with an external wireless device). >>> >>> >>> Anthony >>> >>> >>> ________________________________ >>> From: Adrian Chadd >>> To: tzoi516 >>> Cc: "freebsd-wireless@freebsd.org" >>> Sent: Wednesday, April 9, 2014 3:02 PM >>> Subject: Re: Re: Atheros AR9565 >>> >>> >>> Hi, >>> >>> The AR9565 is a relatively new chip that hasn't really been thoroughly >>> tested in FreeBSD. Laptop manufacturers have also gone and done some >>> rather silly things to save cost on the wireless NIC itself and I'm >>> not sure those patches / work arounds are in -HEAD. >>> >>> please file a PR with this problem complete with your pciconf -lv >>> output as above. >>> >>> Thanks! >>> >>> >>> -a >>> >>> >>> On 9 April 2014 05:40, tzoi516 wrote: >>>> I'm using the GENERIC kernel. Want me to create a custom kernel? >>>> >>>> pciconf info: >>>> >>>> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >>>> rev=0x06 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell DRAM Controller' >>>> class = bridge >>>> subclass = HOST-PCI >>>> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >>>> rev=0x06 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell PCI Express x16 Controller' >>>> class = bridge >>>> subclass = PCI-PCI >>>> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >>>> rev=0x06 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell Integrated Graphics Controller' >>>> class = display >>>> subclass = VGA >>>> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >>>> rev=0x06 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Haswell HD Audio Controller' >>>> class = multimedia >>>> subclass = HDA >>>> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point USB xHCI Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point MEI Controller' >>>> class = simple comms >>>> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point USB Enhanced Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point High Definition Audio Controller' >>>> class = multimedia >>>> subclass = HDA >>>> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >>>> rev=0xd4 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point PCI Express Root Port' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >>>> rev=0xd4 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point PCI Express Root Port' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >>>> rev=0xd4 hdr=0x01 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point PCI Express Root Port' >>>> class = bridge >>>> subclass = PCI-PCI >>>> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point USB Enhanced Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point LPC Controller' >>>> class = bridge >>>> subclass = PCI-ISA >>>> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point SMBus Controller' >>>> class = serial bus >>>> subclass = SMBus >>>> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >>>> class = mass storage >>>> subclass = ATA >>>> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >>>> rev=0xa1 hdr=0x00 >>>> vendor = 'NVIDIA Corporation' >>>> class = display >>>> subclass = 3D >>>> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >>>> rev=0x01 hdr=0x00 >>>> vendor = 'Atheros Communications Inc.' >>>> device = 'AR9565 Wireless Network Adapter' >>>> class = network >>>> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >>>> rev=0x10 hdr=0x00 >>>> vendor = 'Atheros Communications Inc.' >>>> class = network >>>> subclass = ethernet >>>> >>>> >>>> >>>> >>>> On 04/08/14 18:29, Adrian Chadd wrote: >>>>> hi, >>>>> >>>>> ok. Can you please do a pciconf -lv and attach it here? >>>>> >>>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel? >>>>> >>>>> Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here. >>>>> >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 8 April 2014 13:38, tzoi516 wrote: >>>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0 >>>>>> up I received a ton of these: >>>>>> >>>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? >>>>>> >>>>>> received those about 20 times then this: >>>>>> >>>>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>>>> >>>>>> And now the top 2 are slowly scrolling. >>>>>> >>>>>> Mike >>>>>> >>>>>> >>>>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>>>> Right. It sounds like it's not associated. >>>>>>> >>>>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> >>>>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>>>> Sorry for another email, the errors are sporadic. I'm trying to find the >>>>>>>> ioctl errors that I get on shutdown. >>>>>>>> These are after logging in: >>>>>>>> >>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>>> dhclient[1001]: send_packet: Network is down >>>>>>>> >>>>>>>> Mike >>>>>>>> >>>>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>>>> >>>>>>>>> >>>>>>>>> -a >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -a >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>>>> This specific one: >>>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>>>> >>>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For >>>>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and >>>>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>>>> >>>>>>>>>>>> Mike >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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" >>>>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i >>>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears. >>>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list >>>>>>>>>> scan and see available networks but I can't connect to any except for >>>>>>>>>> unprotected networks. >>>>>>>>>> >>>>>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>>>>> Mike >>>> >>>> _______________________________________________ >>>> freebsd-wireless@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 10:18:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83B61E91; Fri, 11 Apr 2014 10:18:54 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 04FC41366; Fri, 11 Apr 2014 10:18:53 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.8/8.14.8) with ESMTP id s3BAIHiB004536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Apr 2014 14:18:17 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.8/8.14.8/Submit) id s3BAIGkY004535; Fri, 11 Apr 2014 14:18:16 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 11 Apr 2014 14:18:16 +0400 From: Gleb Smirnoff To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140411101816.GC902@glebius.int.ru> References: <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> <20140408104650.GN44326@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Apr 2014 10:18:54 -0000 Adrian, On Tue, Apr 08, 2014 at 09:37:21AM -0700, Adrian Chadd wrote: A> Which hardware is it? iwn0: mem 0xf0c00000-0xf0c01fff irq 17 at device 0.0 on pci3 iwn0@pci0:3:0:0: class=0x028000 card=0xc2208086 chip=0x00858086 rev=0x96 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N 6205 [Taylor Peak]' class = network This is 2012 year made Thinkpad X1 Carbon. -- Totus tuus, Glebius. From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 10:19:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E852FED; Fri, 11 Apr 2014 10:19:54 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BBAB0137C; Fri, 11 Apr 2014 10:19:53 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id x13so5823132qcv.1 for ; Fri, 11 Apr 2014 03:19:52 -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=C4rHwRvIQHmxktN0rY4M3hioKZLVltx17yViU89CRlg=; b=W/++P2eQWCwNBhEyPzhuBnwNSJE4Z94Nee4oNRSXrdvA2OUz1DKATvHmED8AMeeDm1 b7j9d9Z6EYoKJzgfCKOq/cuiyGRzuUzg/TtXrHJKugr8T2nPNfolBVKxymNvGFljkBJt +rIl6NG11e8+SHFU4mBXrt4uaqQBkFMPWb4yihLdts24nvyXhbCLCw4pPOni1HtOkJX1 B/YEbN22Zw+Or3rT1ViQKXy/l3jttFbZM+vQOPtsBVNq7UNN7+nSPEgJNLQnZVaAbAn5 Agx8ys38cWNRZ1UG2eO4ky/jIUGt1EtgxMiVJ4U9qqcRoTCmlpH0N4nGIj7FhT/s005e pqXg== MIME-Version: 1.0 X-Received: by 10.140.38.149 with SMTP id t21mr25857817qgt.24.1397211592642; Fri, 11 Apr 2014 03:19:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Fri, 11 Apr 2014 03:19:52 -0700 (PDT) In-Reply-To: <20140411101816.GC902@glebius.int.ru> References: <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> <20140408104650.GN44326@FreeBSD.org> <20140411101816.GC902@glebius.int.ru> Date: Fri, 11 Apr 2014 03:19:52 -0700 X-Google-Sender-Auth: r8-Mg1ZxbY5EG0P7cLixYlVz6jg Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Gleb Smirnoff Content-Type: text/plain; charset=ISO-8859-1 Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Apr 2014 10:19:54 -0000 Ok, i have some of these. Which version of iwn(4) and net80211(4) work for you? We should do some bisecting of iwn/net80211 together to figure it out. -a On 11 April 2014 03:18, Gleb Smirnoff wrote: > Adrian, > > On Tue, Apr 08, 2014 at 09:37:21AM -0700, Adrian Chadd wrote: > A> Which hardware is it? > > iwn0: mem 0xf0c00000-0xf0c01fff irq 17 at device 0.0 on pci3 > > iwn0@pci0:3:0:0: class=0x028000 card=0xc2208086 chip=0x00858086 rev=0x96 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Centrino Advanced-N 6205 [Taylor Peak]' > class = network > > This is 2012 year made Thinkpad X1 Carbon. > > -- > Totus tuus, Glebius. From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 10:50:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1828F9C4; Fri, 11 Apr 2014 10:50:24 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C80116B6; Fri, 11 Apr 2014 10:50:23 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.8/8.14.8) with ESMTP id s3BAoDSS004686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Apr 2014 14:50:13 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.8/8.14.8/Submit) id s3BAnwUk004683; Fri, 11 Apr 2014 14:49:58 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 11 Apr 2014 14:49:58 +0400 From: Gleb Smirnoff To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140411104958.GD902@glebius.int.ru> References: <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> <20140408104650.GN44326@FreeBSD.org> <20140411101816.GC902@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Apr 2014 10:50:24 -0000 On Fri, Apr 11, 2014 at 03:19:52AM -0700, Adrian Chadd wrote: A> Ok, i have some of these. A> A> Which version of iwn(4) and net80211(4) work for you? We should do A> some bisecting of iwn/net80211 together to figure it out. I will bisect entire kernel. A lot of manual fixing needs to be applied to older iwn/net80211 to get it compilable with modern kernel. -- Totus tuus, Glebius. From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 13:49:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C3571CB; Fri, 11 Apr 2014 13:49:37 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AFC1A1BE8; Fri, 11 Apr 2014 13:49:35 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.8/8.14.8) with ESMTP id s3BDn5X8005951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Apr 2014 17:49:05 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.8/8.14.8/Submit) id s3BDn4tl005950; Fri, 11 Apr 2014 17:49:04 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 11 Apr 2014 17:49:04 +0400 From: Gleb Smirnoff To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140411134904.GF902@glebius.int.ru> References: <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> <20140408104650.GN44326@FreeBSD.org> <20140411101816.GC902@glebius.int.ru> <20140411104958.GD902@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140411104958.GD902@glebius.int.ru> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Apr 2014 13:49:37 -0000 On Fri, Apr 11, 2014 at 02:49:58PM +0400, Gleb Smirnoff wrote: T> On Fri, Apr 11, 2014 at 03:19:52AM -0700, Adrian Chadd wrote: T> A> Ok, i have some of these. T> A> T> A> Which version of iwn(4) and net80211(4) work for you? We should do T> A> some bisecting of iwn/net80211 together to figure it out. T> T> I will bisect entire kernel. A lot of manual fixing needs to be T> applied to older iwn/net80211 to get it compilable with modern T> kernel. Very strange. I bisected from 254098 up to today, moving closer and closer to current revision and finally came to it. No problems :( But I clearly remember that before I started this process, my download speed was 30 - 60 KBytes/s. May be this was some firmware issue that persisted during reboots? Old driver gave it a kick and new driver now works good? Yes, sounds mad. -- Totus tuus, Glebius. From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 14:12:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96519F1D for ; Fri, 11 Apr 2014 14:12:32 +0000 (UTC) Received: from nm40-vm4.bullet.mail.bf1.yahoo.com (nm40-vm4.bullet.mail.bf1.yahoo.com [72.30.239.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 345411FE5 for ; Fri, 11 Apr 2014 14:12:31 +0000 (UTC) Received: from [98.139.212.149] by nm40.bullet.mail.bf1.yahoo.com with NNFMP; 11 Apr 2014 14:09:52 -0000 Received: from [98.139.212.243] by tm6.bullet.mail.bf1.yahoo.com with NNFMP; 11 Apr 2014 14:09:51 -0000 Received: from [127.0.0.1] by omp1052.mail.bf1.yahoo.com with NNFMP; 11 Apr 2014 14:09:51 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 819479.87562.bm@omp1052.mail.bf1.yahoo.com Received: (qmail 10078 invoked by uid 60001); 11 Apr 2014 14:09:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1397225391; bh=Pl7PSFMK1R3YgR2Pjvr71assf66GiY5bgL5tdXeQFyM=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=C8ytJBUG6XQL4rvA79hnayt0JWFLrRjky0iImNbuiL29xBJrLwqvVZGvuZSzibkhXJ2OYN9qKycDQ51N31R8JTkVLXv9Xv2tCQrPU7EXP/m7fsTIzhWNHN3/Pe/LeTNrV9e1QhdV227wGdx0p5R/nIGWQ2FqVBokAtRVsM/4rC0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=PW3XN/yyRbBsUAml+E98MY1vVU+JhOiwMLk9iguTYYMq4gPYoYuu+7b72E+xWUyvJaJTQmNPXjhPhjH0AdHUs+LeMJJZjR89E0gKrtI7ZT6epIisst4yTEngu31v8EFO0bUsx79d+oLsWHNE2JnKitLWH45acYWJ61TXQSucoSc=; X-YMail-OSG: 4fJrTMMVM1n32AIKypUKEV9Uqku7wH9nX75ZKEbF94JOtOL iEsQx6LYMbgANVEtwArnABVQGhBJCx8PCZdSkWf0TO9e7EBhMqbt1Jdd7fq9 Yo5qSYeFeWvRfEkKbRFBdVEdh3GE95fpvZMPFgS9XzjrvV0WLwRZ_O2E1kCw Z.vGcdqYqaMLJvCiI3WFBiFdXUTOG_WTQ.vhMtP8VFyQqJI_cHHN7jIzM37z oIGNRONw0WCo.XJ1HvreMa2mu4_NCjnao4.gHiYhb0Lm8XWnduAeI2jCATOr CmPXUmvty1O1m0zaJTANCejFPgDSNw8V.1C8Kuz3S7k9g.WMxCRW6l.5qmZ6 20RmGhnY0L51Mou0Scq8zbQ1LegoRMxnCmVlFJf1y6jQszAJgEkK5FAO_OTx HvyscGdHlDSNpirlLbDOTEPymAKCQZpuNLfnAK_ou_N6S2N3afhvg3_5qS7g rWX17L2I_1m7T4Zg6IjSmGfp.x8_xqRjXjyixgm8nWHzpw_KXprgN949UqHJ IU.aWClzrMw40_obE7jS4HYD6agIZRicuQFGti2jf9tsmrikgZP8THW09axb BPgHsBYR3KryNGIxjjyF1_kEQQWbr7hd1v73zcdS61jUcsmc6FDqcgPdIcx1 CcYAnnCIbYV0UKwhk5BwOWnrcSFql23m23lXutHGIFXPzth7kgC5ax7tkyxd Uh8LpcZNDxRewASEuJwlGjwj5Kmby.hwruFeyms0reLXZH17Wt5g.rBdGTNw eIwOTsS6j Received: from [70.90.74.161] by web140701.mail.bf1.yahoo.com via HTTP; Fri, 11 Apr 2014 07:09:51 PDT X-Rocket-MIMEInfo: 002.001, SSdsbCBzdGljayAtQ1VSUkVOVCBiYWNrIG9uIGl0IGFuZCBzZWUgaWYgaXQgd29ya3MuLi4KCk5vcGUsIG15IEFSOTU2NSB3b24ndCBjb25uZWN0IHRvIGFuIGFjY2VzcyBwb2ludC7CoCBUaGUgd2lyZWxlc3MgTEVEIG9uIHRoZSBIUCBFTlZZIFNsZWVrYm9vayB3aXJlbGVzcyBrZXkgaXMgYW1iZXIgKG9mZikgYW5kIHByZXNzaW5nIEZuK3dpcmVsZXNzIGtleSBkb2Vzbid0IGRvIGFueXRoaW5nLsKgIEdQSU8gb3Igc29tZXRoaW5nP8KgIEkgY2FuIGdldCB5b3UgbG9nIG91dHB1dCBmcm9tICd3cGFfc3VwcGwBMAEBAQE- X-Mailer: YahooMailWebService/0.8.182.648 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> <534695C8.8000802@yahoo.com> Message-ID: <1397225391.66561.YahooMailNeo@web140701.mail.bf1.yahoo.com> Date: Fri, 11 Apr 2014 07:09:51 -0700 (PDT) From: Anthony Jenkins Subject: Re: Atheros AR9565 To: Adrian Chadd In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: tzoi516 , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Anthony Jenkins 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, 11 Apr 2014 14:12:32 -0000 I'll stick -CURRENT back on it and see if it works...=0A=0ANope, my AR9565 = won't connect to an access point.=A0 The wireless LED on the HP ENVY Sleekb= ook wireless key is amber (off) and pressing Fn+wireless key doesn't do any= thing.=A0 GPIO or something?=A0 I can get you log output from 'wpa_supplica= nt -d -d' or ath(4) debug messages or whatever, or can send the device (I k= inda wanna keep the laptop :-) ).=0A=0AAnthony=0A=0A=0A----- Original Messa= ge -----=0AFrom: Adrian Chadd =0ATo: Anthony Jenkins =0ACc: tzoi516 ; "freebsd-wireless@f= reebsd.org" =0ASent: Thursday, April 10, 2014= 12:25 PM=0ASubject: Re: Atheros AR9565=0A=0AHm,=0A=0AI think someone needs= to buy me one of these. The AR9565 that I had=0Atried on worked fine.=0A= =0A=0A-a=0A=0A=0A=0AOn 10 April 2014 05:59, Anthony Jenkins wrote:=0A> HP ENVY 6Z-1100 Sleekbook=0A>=0A> Sorry, tried replying = with a URL to HP's product website, but must've gotten blocked.=A0 Also my = original (brief) email thread on my AR9565 was in July '13, not August.=0A>= =0A> Anthony=0A>=0A> On 04/09/2014 05:18 PM, Adrian Chadd wrote:=0A>> Which= HP laptop?=0A>>=0A>>=0A>> -a=0A>>=0A>>=0A>> On 9 April 2014 13:35, Anthony= Jenkins wrote:=0A>>> Hey, I've got one of these bab= ies in my HP laptop; I actually posted some problems I was having to the li= st back in Aug. '13.=A0 I could loan you mine and/or assist with debugging = if I can have it back (can make do with an external wireless device).=0A>>>= =0A>>>=0A>>> Anthony=0A>>>=0A>>>=0A>>> ________________________________=0A>= >> From: Adrian Chadd =0A>>> To: tzoi516 =0A>>> Cc: "freebsd-wireless@freebsd.org" =0A>>> Sent: Wednesday, April 9, 2014 3:02 PM=0A>>> Subject: Re: Re: Athe= ros AR9565=0A>>>=0A>>>=0A>>> Hi,=0A>>>=0A>>> The AR9565 is a relatively new= chip that hasn't really been thoroughly=0A>>> tested in FreeBSD. Laptop ma= nufacturers have also gone and done some=0A>>> rather silly things to save = cost on the wireless NIC itself and I'm=0A>>> not sure those patches / work= arounds are in -HEAD.=0A>>>=0A>>> please file a PR with this problem compl= ete with your pciconf -lv=0A>>> output as above.=0A>>>=0A>>> Thanks!=0A>>>= =0A>>>=0A>>> -a=0A>>>=0A>>>=0A>>> On 9 April 2014 05:40, tzoi516 wrote:=0A>>>> I'm using the GENERIC kernel. Want me to create a c= ustom kernel?=0A>>>>=0A>>>> pciconf info:=0A>>>>=0A>>>> hostb0@pci0:0:0:0:= =A0 =A0 class=3D0x060000 card=3D0xfa401179 chip=3D0x0c048086=0A>>>> rev=3D0= x06 hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A= >>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Haswell DRAM Controller'=0A>>>>=A0 =A0= =A0 class=A0 =A0 =A0 =3D bridge=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D HOST-PC= I=0A>>>> pcib1@pci0:0:1:0:=A0 =A0 class=3D0x060400 card=3D0xfa471179 chip= =3D0x0c018086=0A>>>> rev=3D0x06 hdr=3D0x01=0A>>>>=A0 =A0=A0 vendor=A0 =A0= =A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Haswell = PCI Express x16 Controller'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D bridge=0A= >>>>=A0 =A0=A0 subclass=A0=A0 =3D PCI-PCI=0A>>>> vgapci1@pci0:0:2:0:=A0 =A0= class=3D0x030000 card=3D0xfa471179 chip=3D0x04168086=0A>>>> rev=3D0x06 hdr= =3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0= =A0=A0 device=A0 =A0=A0 =3D 'Haswell Integrated Graphics Controller'=0A>>>= >=A0 =A0=A0 class=A0 =A0 =A0 =3D display=0A>>>>=A0 =A0=A0 subclass=A0=A0 = =3D VGA=0A>>>> hdac0@pci0:0:3:0:=A0 =A0 class=3D0x040300 card=3D0xfa4d1179 = chip=3D0x0c0c8086=0A>>>> rev=3D0x06 hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 = =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Haswe= ll HD Audio Controller'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D multimedia=0A= >>>>=A0 =A0=A0 subclass=A0=A0 =3D HDA=0A>>>> xhci0@pci0:0:20:0:=A0 =A0 clas= s=3D0x0c0330 card=3D0xfa401179 chip=3D0x8c318086=0A>>>> rev=3D0x04 hdr=3D0x= 00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0= =A0 device=A0 =A0=A0 =3D 'Lynx Point USB xHCI Host Controller'=0A>>>>=A0 = =A0=A0 class=A0 =A0 =A0 =3D serial bus=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D = USB=0A>>>> none0@pci0:0:22:0:=A0 =A0 class=3D0x078000 card=3D0xfa401179 chi= p=3D0x8c3a8086=0A>>>> rev=3D0x04 hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0= =A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx Poi= nt MEI Controller'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D simple comms=0A>>>= > ehci0@pci0:0:26:0:=A0 =A0 class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c2= d8086=0A>>>> rev=3D0x04 hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'I= ntel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx Point USB Enh= anced Host Controller'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D serial bus=0A>= >>>=A0 =A0=A0 subclass=A0=A0 =3D USB=0A>>>> hdac1@pci0:0:27:0:=A0 =A0 class= =3D0x040300 card=3D0xfa4d1179 chip=3D0x8c208086=0A>>>> rev=3D0x04 hdr=3D0x0= 0=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0= =A0 device=A0 =A0=A0 =3D 'Lynx Point High Definition Audio Controller'=0A>>= >>=A0 =A0=A0 class=A0 =A0 =A0 =3D multimedia=0A>>>>=A0 =A0=A0 subclass=A0= =A0 =3D HDA=0A>>>> pcib2@pci0:0:28:0:=A0 =A0 class=3D0x060400 card=3D0xfa40= 1179 chip=3D0x8c108086=0A>>>> rev=3D0xd4 hdr=3D0x01=0A>>>>=A0 =A0=A0 vendor= =A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'L= ynx Point PCI Express Root Port'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D brid= ge=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D PCI-PCI=0A>>>> pcib3@pci0:0:28:2:=A0= =A0 class=3D0x060400 card=3D0xfa401179 chip=3D0x8c148086=0A>>>> rev=3D0xd4= hdr=3D0x01=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>= >=A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx Point PCI Express Root Port'=0A>>>>= =A0 =A0=A0 class=A0 =A0 =A0 =3D bridge=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D = PCI-PCI=0A>>>> pcib4@pci0:0:28:3:=A0 =A0 class=3D0x060400 card=3D0xfa401179= chip=3D0x8c168086=0A>>>> rev=3D0xd4 hdr=3D0x01=0A>>>>=A0 =A0=A0 vendor=A0 = =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx = Point PCI Express Root Port'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D bridge= =0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D PCI-PCI=0A>>>> ehci1@pci0:0:29:0:=A0 = =A0 class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c268086=0A>>>> rev=3D0x04 = hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>= =A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx Point USB Enhanced Host Controller'= =0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D serial bus=0A>>>>=A0 =A0=A0 subclass= =A0=A0 =3D USB=0A>>>> isab0@pci0:0:31:0:=A0 =A0 class=3D0x060100 card=3D0xf= a401179 chip=3D0x8c498086=0A>>>> rev=3D0x04 hdr=3D0x00=0A>>>>=A0 =A0=A0 ven= dor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D= 'Lynx Point LPC Controller'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D bridge= =0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D PCI-ISA=0A>>>> none1@pci0:0:31:3:=A0 = =A0 class=3D0x0c0500 card=3D0xfa401179 chip=3D0x8c228086=0A>>>> rev=3D0x04 = hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'Intel Corporation'=0A>>>>= =A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx Point SMBus Controller'=0A>>>>=A0 =A0= =A0 class=A0 =A0 =A0 =3D serial bus=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D SMB= us=0A>>>> atapci0@pci0:0:31:5:=A0 =A0 class=3D0x010185 card=3D0xfa401179 ch= ip=3D0x8c098086=0A>>>> rev=3D0x04 hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0= =A0 =3D 'Intel Corporation'=0A>>>>=A0 =A0=A0 device=A0 =A0=A0 =3D 'Lynx Poi= nt 2-port SATA Controller 2 [IDE mode]'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 = =3D mass storage=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D ATA=0A>>>> vgapci0@pci= 0:1:0:0:=A0 =A0 class=3D0x030200 card=3D0xfa471179 chip=3D0x129210de=0A>>>>= rev=3D0xa1 hdr=3D0x00=0A>>>>=A0 =A0=A0 vendor=A0 =A0=A0 =3D 'NVIDIA Corpor= ation'=0A>>>>=A0 =A0=A0 class=A0 =A0 =A0 =3D display=0A>>>>=A0 =A0=A0 subcl= ass=A0=A0 =3D 3D=0A>>>> ath0@pci0:3:0:0:=A0 =A0 class=3D0x028000 card=3D0x0= 61211ad chip=3D0x0036168c=0A>>>> rev=3D0x01 hdr=3D0x00=0A>>>>=A0 =A0=A0 ven= dor=A0 =A0=A0 =3D 'Atheros Communications Inc.'=0A>>>>=A0 =A0=A0 device=A0 = =A0=A0 =3D 'AR9565 Wireless Network Adapter'=0A>>>>=A0 =A0=A0 class=A0 =A0 = =A0 =3D network=0A>>>> none2@pci0:4:0:0:=A0 =A0 class=3D0x020000 card=3D0xf= a401179 chip=3D0x10a11969=0A>>>> rev=3D0x10 hdr=3D0x00=0A>>>>=A0 =A0=A0 ven= dor=A0 =A0=A0 =3D 'Atheros Communications Inc.'=0A>>>>=A0 =A0=A0 class=A0 = =A0 =A0 =3D network=0A>>>>=A0 =A0=A0 subclass=A0=A0 =3D ethernet=0A>>>>=0A>= >>>=0A>>>>=0A>>>>=0A>>>> On 04/08/14 18:29, Adrian Chadd wrote:=0A>>>>> hi,= =0A>>>>>=0A>>>>> ok. Can you please do a pciconf -lv and attach it here?=0A= >>>>>=0A>>>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_= 11N in your kernel?=0A>>>>>=0A>>>>> Do a 'sysctl dev.ath.0.txagg=3D1' and t= hen paste the output in dmesg here.=0A>>>>>=0A>>>>>=0A>>>>>=0A>>>>> -a=0A>>= >>>=0A>>>>>=0A>>>>> On 8 April 2014 13:38, tzoi516 wrot= e:=0A>>>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifco= nfig ath0=0A>>>>>> up I received a ton of these:=0A>>>>>>=0A>>>>>> ath0: at= h_edma_rxbuf_alloc: nothing on rxbuf?!=0A>>>>>> ath0: ath_edma_rxfifo_alloc= : Q1: alloc failed: i=3D0, nbufs=3D128?=0A>>>>>>=0A>>>>>> received those ab= out 20 times then this:=0A>>>>>>=0A>>>>>> ath0: ath_edma_recv_proc_queue: Q= 1: NULL bf?=0A>>>>>>=0A>>>>>> And now the top 2 are slowly scrolling.=0A>>>= >>>=0A>>>>>> Mike=0A>>>>>>=0A>>>>>>=0A>>>>>> On 04/08/14 16:03, Adrian Chad= d wrote:=0A>>>>>>> Right. It sounds like it's not associated.=0A>>>>>>>=0A>= >>>>>> Try wlandebug +assoc and then run wpa_supplicant=0A>>>>>>>=0A>>>>>>>= =0A>>>>>>> -a=0A>>>>>>>=0A>>>>>>>=0A>>>>>>> On 8 April 2014 12:21, tzoi516 = wrote:=0A>>>>>>>> Sorry for another email, the errors a= re sporadic. I'm trying to find the=0A>>>>>>>> ioctl errors that I get on s= hutdown.=0A>>>>>>>> These are after logging in:=0A>>>>>>>>=0A>>>>>>>> ath0:= ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping=0A>>>>>>>> dhclient[10= 01]: send_packet: Invalid argument=0A>>>>>>>> dhclient[1001]: send_packet: = No buffer space available=0A>>>>>>>> ath0: ath_edma_recv_tasklet: sc_inrese= t_cnt > 0; skipping=0A>>>>>>>> dhclient[1001]: send_packet: No buffer space= available=0A>>>>>>>> dhclient[1001]: send_packet: Invalid argument=0A>>>>>= >>> dhclient[1001]: send_packet: Network is down=0A>>>>>>>>=0A>>>>>>>> Mike= =0A>>>>>>>>=0A>>>>>>>> On 04/08/14 14:38, Adrian Chadd wrote:=0A>>>>>>>>> A= h. Can you post the buffer errors you're seeing?=0A>>>>>>>>>=0A>>>>>>>>>=0A= >>>>>>>>> -a=0A>>>>>>>>>=0A>>>>>>>>>=0A>>>>>>>>> On 8 April 2014 11:37, tzo= i516 wrote:=0A>>>>>>>>>> On 04/08/14 14:23, Adrian Chad= d wrote:=0A>>>>>>>>>>> It should work fine on -10 and HEAD. Is it not worki= ng fine?=0A>>>>>>>>>>>=0A>>>>>>>>>>>=0A>>>>>>>>>>> -a=0A>>>>>>>>>>>=0A>>>>>= >>>>>>=0A>>>>>>>>>>> On 8 April 2014 09:12, tzoi516 wro= te:=0A>>>>>>>>>>>> I have a Toshiba Satellite S55-A5169=0A>>>>>>>>>>>> This= specific one:=0A>>>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074= -REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.h= tml)=0A>>>>>>>>>>>>=0A>>>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and = the Wi-Fi uses the AR9565. For=0A>>>>>>>>>>>> it to work I have to change t= he SATA Controller Mode in the BIOS from=0A>>>>>>>>>>>> "AHCI" to "Compatib= ility". I don't know if this information helps, and=0A>>>>>>>>>>>> it's the= only AHCI setting I can tweak.=0A>>>>>>>>>>>>=0A>>>>>>>>>>>> Mike=0A>>>>>>= >>>>>> _______________________________________________=0A>>>>>>>>>>>> freeb= sd-wireless@freebsd.org mailing list=0A>>>>>>>>>>>> http://lists.freebsd.or= g/mailman/listinfo/freebsd-wireless=0A>>>>>>>>>>>> To unsubscribe, send any= mail to "freebsd-wireless-unsubscribe@freebsd.org"=0A>>>>>>>>>> With SATA = controller mode set to Compatibility then it works, but a=0A>>>>>>>>>> litt= le wonky at startup - sometimes I'll have to run wpa_supplicant -i=0A>>>>>>= >>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears= .=0A>>>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wl= an0 list=0A>>>>>>>>>> scan and see available networks but I can't connect t= o any except for=0A>>>>>>>>>> unprotected networks.=0A>>>>>>>>>>=0A>>>>>>>>= >> I'm currently running FreeBSD 10.0-STABLE=0A>>>>>>>>>> Mike=0A>>>>=0A>>>= > _______________________________________________=0A>>>> freebsd-wireless@f= reebsd.org mailing list=0A>>>> http://lists.freebsd.org/mailman/listinfo/fr= eebsd-wireless=0A>>>> To unsubscribe, send any mail to "freebsd-wireless-un= subscribe@freebsd.org"=0A>>> ______________________________________________= _=0A>>> freebsd-wireless@freebsd.org mailing list=0A>>> http://lists.freebs= d.org/mailman/listinfo/freebsd-wireless=0A>>> To unsubscribe, send any mail= to "freebsd-wireless-unsubscribe@freebsd.org"=0A>=0A From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 19:28:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69F173C2 for ; Fri, 11 Apr 2014 19:28:46 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2574D139A for ; Fri, 11 Apr 2014 19:28:46 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id j7so5643813qaq.22 for ; Fri, 11 Apr 2014 12:28: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:content-transfer-encoding; bh=Us+MxhJstwWcH5Zv+G2ovBVuCmi88OakbSojwBntLrM=; b=IpgXVkJ1Z7UMkG0jXU+fq8PzTOSpqRxdObDZiTfHu7worKYe9qNpQGmRY+nGk2lnBc 4OmQ376Nl3k7VpHjCcl45bDAOLm2SoMDekBvVMOc5u59fAewkbAlMuLZpX8cWnswoN1g U4MGqfNjYUX1zPvWs5vJMlxOTmFXpO1v666q/aBYdn1MbMjtPrCie171vSMtx69PemZg F0rr+ns8DVUP+wSgbud7ZcTc90eYs8MeNr8U+36ZuWJvSrwHDH92uJi9tpBma/q2BO8T ew+r1jAtE/weGK8xXCFpvk77UD3gO9qGoVBeBD2Yz4TbZLD9i9EwAEK526RMGkJz9d6e IwvA== MIME-Version: 1.0 X-Received: by 10.140.22.197 with SMTP id 63mr30088288qgn.4.1397244525289; Fri, 11 Apr 2014 12:28:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Fri, 11 Apr 2014 12:28:45 -0700 (PDT) In-Reply-To: <1397225391.66561.YahooMailNeo@web140701.mail.bf1.yahoo.com> References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> <534695C8.8000802@yahoo.com> <1397225391.66561.YahooMailNeo@web140701.mail.bf1.yahoo.com> Date: Fri, 11 Apr 2014 12:28:45 -0700 X-Google-Sender-Auth: wj7urApmjefDYdzEnXimsW7Owq0 Message-ID: Subject: Re: Atheros AR9565 From: Adrian Chadd To: Anthony Jenkins Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: tzoi516 , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Apr 2014 19:28:46 -0000 It could be a GPIO rfkill setup thing that requires ACPI hacking. Honestly - the easiest way to get it going is for someone to spring the $500 or so and by me one. :-) -a On 11 April 2014 07:09, Anthony Jenkins wrote: > I'll stick -CURRENT back on it and see if it works... > > Nope, my AR9565 won't connect to an access point. The wireless LED on th= e HP ENVY Sleekbook wireless key is amber (off) and pressing Fn+wireless ke= y doesn't do anything. GPIO or something? I can get you log output from '= wpa_supplicant -d -d' or ath(4) debug messages or whatever, or can send the= device (I kinda wanna keep the laptop :-) ). > > Anthony > > > ----- Original Message ----- > From: Adrian Chadd > To: Anthony Jenkins > Cc: tzoi516 ; "freebsd-wireless@freebsd.org" > Sent: Thursday, April 10, 2014 12:25 PM > Subject: Re: Atheros AR9565 > > Hm, > > I think someone needs to buy me one of these. The AR9565 that I had > tried on worked fine. > > > -a > > > > On 10 April 2014 05:59, Anthony Jenkins wrote: >> HP ENVY 6Z-1100 Sleekbook >> >> Sorry, tried replying with a URL to HP's product website, but must've go= tten blocked. Also my original (brief) email thread on my AR9565 was in Ju= ly '13, not August. >> >> Anthony >> >> On 04/09/2014 05:18 PM, Adrian Chadd wrote: >>> Which HP laptop? >>> >>> >>> -a >>> >>> >>> On 9 April 2014 13:35, Anthony Jenkins wrote: >>>> Hey, I've got one of these babies in my HP laptop; I actually posted s= ome problems I was having to the list back in Aug. '13. I could loan you m= ine and/or assist with debugging if I can have it back (can make do with an= external wireless device). >>>> >>>> >>>> Anthony >>>> >>>> >>>> ________________________________ >>>> From: Adrian Chadd >>>> To: tzoi516 >>>> Cc: "freebsd-wireless@freebsd.org" >>>> Sent: Wednesday, April 9, 2014 3:02 PM >>>> Subject: Re: Re: Atheros AR9565 >>>> >>>> >>>> Hi, >>>> >>>> The AR9565 is a relatively new chip that hasn't really been thoroughly >>>> tested in FreeBSD. Laptop manufacturers have also gone and done some >>>> rather silly things to save cost on the wireless NIC itself and I'm >>>> not sure those patches / work arounds are in -HEAD. >>>> >>>> please file a PR with this problem complete with your pciconf -lv >>>> output as above. >>>> >>>> Thanks! >>>> >>>> >>>> -a >>>> >>>> >>>> On 9 April 2014 05:40, tzoi516 wrote: >>>>> I'm using the GENERIC kernel. Want me to create a custom kernel? >>>>> >>>>> pciconf info: >>>>> >>>>> hostb0@pci0:0:0:0: class=3D0x060000 card=3D0xfa401179 chip=3D0x0c0= 48086 >>>>> rev=3D0x06 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Haswell DRAM Controller' >>>>> class =3D bridge >>>>> subclass =3D HOST-PCI >>>>> pcib1@pci0:0:1:0: class=3D0x060400 card=3D0xfa471179 chip=3D0x0c01= 8086 >>>>> rev=3D0x06 hdr=3D0x01 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Haswell PCI Express x16 Controller' >>>>> class =3D bridge >>>>> subclass =3D PCI-PCI >>>>> vgapci1@pci0:0:2:0: class=3D0x030000 card=3D0xfa471179 chip=3D0x04= 168086 >>>>> rev=3D0x06 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Haswell Integrated Graphics Controller' >>>>> class =3D display >>>>> subclass =3D VGA >>>>> hdac0@pci0:0:3:0: class=3D0x040300 card=3D0xfa4d1179 chip=3D0x0c0c= 8086 >>>>> rev=3D0x06 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Haswell HD Audio Controller' >>>>> class =3D multimedia >>>>> subclass =3D HDA >>>>> xhci0@pci0:0:20:0: class=3D0x0c0330 card=3D0xfa401179 chip=3D0x8c3= 18086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point USB xHCI Host Controller' >>>>> class =3D serial bus >>>>> subclass =3D USB >>>>> none0@pci0:0:22:0: class=3D0x078000 card=3D0xfa401179 chip=3D0x8c3= a8086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point MEI Controller' >>>>> class =3D simple comms >>>>> ehci0@pci0:0:26:0: class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c2= d8086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point USB Enhanced Host Controller' >>>>> class =3D serial bus >>>>> subclass =3D USB >>>>> hdac1@pci0:0:27:0: class=3D0x040300 card=3D0xfa4d1179 chip=3D0x8c2= 08086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point High Definition Audio Controller' >>>>> class =3D multimedia >>>>> subclass =3D HDA >>>>> pcib2@pci0:0:28:0: class=3D0x060400 card=3D0xfa401179 chip=3D0x8c1= 08086 >>>>> rev=3D0xd4 hdr=3D0x01 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point PCI Express Root Port' >>>>> class =3D bridge >>>>> subclass =3D PCI-PCI >>>>> pcib3@pci0:0:28:2: class=3D0x060400 card=3D0xfa401179 chip=3D0x8c1= 48086 >>>>> rev=3D0xd4 hdr=3D0x01 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point PCI Express Root Port' >>>>> class =3D bridge >>>>> subclass =3D PCI-PCI >>>>> pcib4@pci0:0:28:3: class=3D0x060400 card=3D0xfa401179 chip=3D0x8c1= 68086 >>>>> rev=3D0xd4 hdr=3D0x01 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point PCI Express Root Port' >>>>> class =3D bridge >>>>> subclass =3D PCI-PCI >>>>> ehci1@pci0:0:29:0: class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c2= 68086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point USB Enhanced Host Controller' >>>>> class =3D serial bus >>>>> subclass =3D USB >>>>> isab0@pci0:0:31:0: class=3D0x060100 card=3D0xfa401179 chip=3D0x8c4= 98086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point LPC Controller' >>>>> class =3D bridge >>>>> subclass =3D PCI-ISA >>>>> none1@pci0:0:31:3: class=3D0x0c0500 card=3D0xfa401179 chip=3D0x8c2= 28086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point SMBus Controller' >>>>> class =3D serial bus >>>>> subclass =3D SMBus >>>>> atapci0@pci0:0:31:5: class=3D0x010185 card=3D0xfa401179 chip=3D0x8= c098086 >>>>> rev=3D0x04 hdr=3D0x00 >>>>> vendor =3D 'Intel Corporation' >>>>> device =3D 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >>>>> class =3D mass storage >>>>> subclass =3D ATA >>>>> vgapci0@pci0:1:0:0: class=3D0x030200 card=3D0xfa471179 chip=3D0x12= 9210de >>>>> rev=3D0xa1 hdr=3D0x00 >>>>> vendor =3D 'NVIDIA Corporation' >>>>> class =3D display >>>>> subclass =3D 3D >>>>> ath0@pci0:3:0:0: class=3D0x028000 card=3D0x061211ad chip=3D0x00361= 68c >>>>> rev=3D0x01 hdr=3D0x00 >>>>> vendor =3D 'Atheros Communications Inc.' >>>>> device =3D 'AR9565 Wireless Network Adapter' >>>>> class =3D network >>>>> none2@pci0:4:0:0: class=3D0x020000 card=3D0xfa401179 chip=3D0x10a1= 1969 >>>>> rev=3D0x10 hdr=3D0x00 >>>>> vendor =3D 'Atheros Communications Inc.' >>>>> class =3D network >>>>> subclass =3D ethernet >>>>> >>>>> >>>>> >>>>> >>>>> On 04/08/14 18:29, Adrian Chadd wrote: >>>>>> hi, >>>>>> >>>>>> ok. Can you please do a pciconf -lv and attach it here? >>>>>> >>>>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in = your kernel? >>>>>> >>>>>> Do a 'sysctl dev.ath.0.txagg=3D1' and then paste the output in dmesg= here. >>>>>> >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 8 April 2014 13:38, tzoi516 wrote: >>>>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig= ath0 >>>>>>> up I received a ton of these: >>>>>>> >>>>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! >>>>>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=3D0, nbufs=3D128? >>>>>>> >>>>>>> received those about 20 times then this: >>>>>>> >>>>>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf? >>>>>>> >>>>>>> And now the top 2 are slowly scrolling. >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> >>>>>>> On 04/08/14 16:03, Adrian Chadd wrote: >>>>>>>> Right. It sounds like it's not associated. >>>>>>>> >>>>>>>> Try wlandebug +assoc and then run wpa_supplicant >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 8 April 2014 12:21, tzoi516 wrote: >>>>>>>>> Sorry for another email, the errors are sporadic. I'm trying to f= ind the >>>>>>>>> ioctl errors that I get on shutdown. >>>>>>>>> These are after logging in: >>>>>>>>> >>>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping >>>>>>>>> dhclient[1001]: send_packet: No buffer space available >>>>>>>>> dhclient[1001]: send_packet: Invalid argument >>>>>>>>> dhclient[1001]: send_packet: Network is down >>>>>>>>> >>>>>>>>> Mike >>>>>>>>> >>>>>>>>> On 04/08/14 14:38, Adrian Chadd wrote: >>>>>>>>>> Ah. Can you post the buffer errors you're seeing? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -a >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 8 April 2014 11:37, tzoi516 wrote: >>>>>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote: >>>>>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -a >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 8 April 2014 09:12, tzoi516 wrote: >>>>>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>>>>> This specific one: >>>>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_psk= k6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html) >>>>>>>>>>>>> >>>>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR= 9565. For >>>>>>>>>>>>> it to work I have to change the SATA Controller Mode in the B= IOS from >>>>>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information h= elps, and >>>>>>>>>>>>> it's the only AHCI setting I can tweak. >>>>>>>>>>>>> >>>>>>>>>>>>> Mike >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> freebsd-wireless@freebsd.org mailing list >>>>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>>>>>>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscrib= e@freebsd.org" >>>>>>>>>>> With SATA controller mode set to Compatibility then it works, b= ut a >>>>>>>>>>> little wonky at startup - sometimes I'll have to run wpa_suppli= cant -i >>>>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error = appears. >>>>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0= list >>>>>>>>>>> scan and see available networks but I can't connect to any exce= pt for >>>>>>>>>>> unprotected networks. >>>>>>>>>>> >>>>>>>>>>> I'm currently running FreeBSD 10.0-STABLE >>>>>>>>>>> Mike >>>>> >>>>> _______________________________________________ >>>>> freebsd-wireless@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebs= d.org" >>>> _______________________________________________ >>>> freebsd-wireless@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd= .org" >> > From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 11 21:49:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3CFB1BA; Fri, 11 Apr 2014 21:49:31 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C66C1236; Fri, 11 Apr 2014 21:49:31 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id m20so6583917qcx.35 for ; Fri, 11 Apr 2014 14:49: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=QU7TFYexCk9o7crXsQQKfeynVqM9JXLvlvIivyBbY3I=; b=nhsJGnGt3g6y9Wt1Qx1vtfA24KOr7aUG/t5QbmxNiYrp46vIBbcHaNnvpizNI2/I5i GSMbdt3nYelRO7bUnTtuDUzhmc/k9YEC3aY+QGUuM29Px8gt+nbACQby3YPbwKDiXPEy WjsfnAiETEs8rETzrdAGntqIlOmti7LwZXjx2PYdglUD6OTqNoZWfj5jujk6YexnPp1B RHLrq+ag6XTa3w+E9m3/E4Ajs5Q71WqPUIUMnFToh8PpDEnIVZVQu7CrJNPOIorI1PKN RradqzgL+tZH95B+Gr6gLujYmQdLkTKjkB9fJBQCiSo+dOO++P9tPIxFyJnrKbOI50dM wQlQ== MIME-Version: 1.0 X-Received: by 10.140.22.197 with SMTP id 63mr30883593qgn.4.1397252970398; Fri, 11 Apr 2014 14:49:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Fri, 11 Apr 2014 14:49:30 -0700 (PDT) In-Reply-To: <20140411134904.GF902@glebius.int.ru> References: <20140228230705.GA28290@syn.pertho.net> <20140403100207.GA23640@syn.pertho.net> <20140408104650.GN44326@FreeBSD.org> <20140411101816.GC902@glebius.int.ru> <20140411104958.GD902@glebius.int.ru> <20140411134904.GF902@glebius.int.ru> Date: Fri, 11 Apr 2014 14:49:30 -0700 X-Google-Sender-Auth: dMRK7aF9SDgfVFlIPdLJFy0dQKc Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Gleb Smirnoff Content-Type: text/plain; charset=ISO-8859-1 Cc: Tom Murphy , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Apr 2014 21:49:31 -0000 On 11 April 2014 06:49, Gleb Smirnoff wrote: > On Fri, Apr 11, 2014 at 02:49:58PM +0400, Gleb Smirnoff wrote: > T> On Fri, Apr 11, 2014 at 03:19:52AM -0700, Adrian Chadd wrote: > T> A> Ok, i have some of these. > T> A> > T> A> Which version of iwn(4) and net80211(4) work for you? We should do > T> A> some bisecting of iwn/net80211 together to figure it out. > T> > T> I will bisect entire kernel. A lot of manual fixing needs to be > T> applied to older iwn/net80211 to get it compilable with modern > T> kernel. > > Very strange. I bisected from 254098 up to today, moving closer and > closer to current revision and finally came to it. No problems :( > > But I clearly remember that before I started this process, my > download speed was 30 - 60 KBytes/s. > > May be this was some firmware issue that persisted during reboots? > Old driver gave it a kick and new driver now works good? Yes, > sounds mad. It's quite possible. I've seen this before with the intel stuff. Let me know if it happens again? -a From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 12 07:31:29 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 327E6C53 for ; Sat, 12 Apr 2014 07:31:29 +0000 (UTC) Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E852616DC for ; Sat, 12 Apr 2014 07:31:28 +0000 (UTC) Received: by mail-vc0-f170.google.com with SMTP id hu19so5834596vcb.1 for ; Sat, 12 Apr 2014 00:31:28 -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=WkltvnockFfUvhpm9h0bX9w04+49BJx8vgTfkbtY/I8=; b=rMC7FzJ9ZF43qXEvC0iRjW83oPVpEsCfTXkiSFDmrxDNEKwNNBeC7nO1umNQizk0Wi 10QZwxruTbyor8M4Z0nYcCDRBHIBCIz2eT8qs+dPevaTXicgN2gXmKIAsghfy5k+JOhQ doRPPlOXb9z4CdA4jA2mZlEDg3UvKgltzPerKoHGaUroYi2KCO1jcRkITiH+9hj5vHMn HnhwtAMMRSCcBJk5gk6tAUmyAuypgjjahasfbqxp3SHa0hG9khkmVssueHKIbVcow57y vpvBEsxlE+iLqZP59eSNUhehuo+YOvLaQElttKyCeobnFmvRg5GqMrH3QP2sZ3mbjBVi HyvA== MIME-Version: 1.0 X-Received: by 10.58.23.6 with SMTP id i6mr23684377vef.12.1397287888042; Sat, 12 Apr 2014 00:31:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.220.113.199 with HTTP; Sat, 12 Apr 2014 00:31:27 -0700 (PDT) Date: Sat, 12 Apr 2014 00:31:27 -0700 X-Google-Sender-Auth: mw-eifYdsgI_4hdTQGxjTZ1DQsk Message-ID: Subject: [rfc] net80211/ath station side sleep support From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Apr 2014 07:31:29 -0000 Hi, Here's a WIP for chip power saving support for net80211 and ath: http://people.freebsd.org/~adrian/ath/20140411-net80211-ath-sleep-3.diff (ignore the stuff for non-net80211 and non-ath drivers.) This implements: * basic chip power management for ath(4), allowing the NIC to go into network sleep in STA mode * .. and all the fiddly places where I have to actually force wake the thing up before I can access it! * implements IEEE80211_S_SLEEP for ath(4), so net80211 can drive when the VAP goes into sleep mode * very basic (and I do mean _very_) sleep state support in net80211 - it's just a timer that monitors for idle periods of greater than a second and puts the VAP into IEEE80211_S_SLEEP state. I should be triggering it off of beacon intervals and such. * .. and hook into the beacon receive path to check for the TIM and whether the VAP needs to wake up for active receive. What it doesn't implement: * ath(4) should only put the NIC into network sleep if all the VAPs are capable of it and all the VAPs are currently asleep. Very notably, STA+AP mode (ie, WDS) shouldn't put the NIC into network sleep. * i haven't verified at all that the net80211 code is correctly marking management frames with PWR=1 (ie, telling the peer that although a frame is being transmitted, it should be considered "asleep") if the sending VAP is asleep * mesh or adhoc sleep state handling - mostly because the TIM stuff needs checking _and_ we need to figure out how to handle ATIM stuff. * We don't yet have support to send out PS-POLL frames to ask the AP for individual data frames. I plan on yanking this out of madwifi at some point as it'll make it much, much easier to stay asleep for longer periods of time and thus get much better power savings. * .. and yes, we still don't support uAPSD. I have no plans to implement that at the moment. To test: * Apply to -HEAD and rebuild * .. make sure you have ATH_DEBUG, AH_DEBUG, ATH_DIAGAPI, IEEE80211_DEBUG in your kernel config files! * ifconfig wlan0 create wlandev ath0 powersave * wlandebug +power +state +debug to see the NIC go in and out of sleep state It's working for me so far on the AR5416 test device I have. I'm sure it'll work on the AR91xx and AR92xx series. The AR93xx stuff will need some further digging into as I haven't verified yet whether I'm waking the NIC up correctly before I do the FIFO descriptor programming. But yes, there's a noticable (2W) drop when the NIC is actually in and staying in power save state. -a From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 13 22:38:31 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C05423EB; Sun, 13 Apr 2014 22:38:31 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93ED41CF8; Sun, 13 Apr 2014 22:38:31 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3DMcVjO048902; Sun, 13 Apr 2014 22:38:31 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3DMcVYe048901; Sun, 13 Apr 2014 22:38:31 GMT (envelope-from linimon) Date: Sun, 13 Apr 2014 22:38:31 GMT Message-Id: <201404132238.s3DMcVYe048901@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/188415: [ath] Poor Atheros AR9565 performance X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2014 22:38:31 -0000 Old Synopsis: Poor Atheros AR9565 performance New Synopsis: [ath] Poor Atheros AR9565 performance Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 13 22:38:12 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=188415 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 13 22:51:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FF25DBD; Sun, 13 Apr 2014 22:51:37 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3A0A1FBF; Sun, 13 Apr 2014 22:51:36 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id w7so8098835qcr.39 for ; Sun, 13 Apr 2014 15:51:35 -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=C4OaUk5xq4PhJxd1loSnX2bt3oo1aSqSOFjzdisIoMM=; b=cM6tj1sZk6G2GKdm1XRvsfhrLq7cKoc53WDQoa596Raya6al+Kq1u0mb1FMP/ZaXNO zYRF9TLP+OcYG36qarA22/kuyorrLHHTe1By0wrjPUQcpuqz0wA/I1jdoDQilU5GDg0k 25w1crOowU4xF7/el/ycMvHQf9ehI0Lh7gR5SizsL5/YXG0x03DfiYiHI0q4sZfKKPrM CATwHGI+Meg6B2zbF+40ptUj+ac9oiqwsdmXb64VeWGXhQNHRT/Y132Voc+3Htt1guTt YN4jRJ/HyFemIH/GN3tyQE/cBI1CqT1F3loIK7HcPESK3XgoaF3tX/F5X+kqqZlRprtK BldQ== MIME-Version: 1.0 X-Received: by 10.224.115.3 with SMTP id g3mr32730592qaq.19.1397429495704; Sun, 13 Apr 2014 15:51:35 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Sun, 13 Apr 2014 15:51:35 -0700 (PDT) In-Reply-To: <201404132238.s3DMcVYe048901@freefall.freebsd.org> References: <201404132238.s3DMcVYe048901@freefall.freebsd.org> Date: Sun, 13 Apr 2014 15:51:35 -0700 X-Google-Sender-Auth: 1GMI1_KqDPRKloUE4KKnAJwKy8U Message-ID: Subject: Re: kern/188415: [ath] Poor Atheros AR9565 performance From: Adrian Chadd To: linimon@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bugs@freebsd.org, "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2014 22:51:37 -0000 Is ATH_ENABLE_11N In the kernel? What's the output of 'sysctl dev.ath.0.txagg' ? (it's logged in dmesg.) -a On 13 April 2014 15:38, wrote: > Old Synopsis: Poor Atheros AR9565 performance > New Synopsis: [ath] Poor Atheros AR9565 performance > > Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless > Responsible-Changed-By: linimon > Responsible-Changed-When: Sun Apr 13 22:38:12 UTC 2014 > Responsible-Changed-Why: > reclassify. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=188415 > _______________________________________________ > 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 Sun Apr 13 23:10:01 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FC3F259 for ; Sun, 13 Apr 2014 23:10:01 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5AE101127 for ; Sun, 13 Apr 2014 23:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3DNA1Tw058653 for ; Sun, 13 Apr 2014 23:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3DNA1wk058652; Sun, 13 Apr 2014 23:10:01 GMT (envelope-from gnats) Date: Sun, 13 Apr 2014 23:10:01 GMT Message-Id: <201404132310.s3DNA1wk058652@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Mark Linimon Subject: Re: kern/188415: [ath] Poor Atheros AR9565 performance X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Mark Linimon List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2014 23:10:01 -0000 The following reply was made to PR kern/188415; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/188415: [ath] Poor Atheros AR9565 performance Date: Sun, 13 Apr 2014 18:06:58 -0500 ----- Forwarded message from Adrian Chadd ----- Date: Sun, 13 Apr 2014 15:51:35 -0700 From: Adrian Chadd To: linimon@freebsd.org Cc: freebsd-bugs@freebsd.org, "freebsd-wireless@freebsd.org" Subject: Re: kern/188415: [ath] Poor Atheros AR9565 performance Is ATH_ENABLE_11N In the kernel? What's the output of 'sysctl dev.ath.0.txagg' ? (it's logged in dmesg.) ----- End forwarded message ----- From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 13 23:36:12 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89AC5A8B; Sun, 13 Apr 2014 23:36:12 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C718137F; Sun, 13 Apr 2014 23:36:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3DNaCWP069017; Sun, 13 Apr 2014 23:36:12 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3DNaCQF069016; Sun, 13 Apr 2014 23:36:12 GMT (envelope-from linimon) Date: Sun, 13 Apr 2014 23:36:12 GMT Message-Id: <201404132336.s3DNaCQF069016@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/188576: [ath] traffic hangs in station mode when downgrading from AMPDU TX or reassociating X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2014 23:36:12 -0000 Synopsis: [ath] traffic hangs in station mode when downgrading from AMPDU TX or reassociating Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 13 23:36:00 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=188576 From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 14 03:57:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A40C11AA; Mon, 14 Apr 2014 03:57:46 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 557541962; Mon, 14 Apr 2014 03:57:46 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id w7so8286161qcr.39 for ; Sun, 13 Apr 2014 20:57:44 -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=GWLQhOfuCKhGfDdPXiJIBiDez2diXpN0fAbkm83OMZE=; b=eV1Jm+jNLFKgHwKZ+uKds4+gD00Vx9V/LAhGwP27WtFD4BjztICou9Lju73tWp6pVO TD8OYVQkjX5R6k8Aam/EZgUArGYltiMNvgY5KttW+Cp8oqN/bN86Vjdoc7bVRDQNE7C2 bStCopJoqUKJXiDJBR7Emwo5zl7Q5VD4DV/Zy40+GYZuQ09ZCb7eALsJNTT07jTJ71SW J9xXc8gBJiqsJkQlI2i4WoNrM0Tef/wpiebC1SdAqssQ1zXR1qJGvgHw4YKKNF3PqMLs E+5D9uEEWqQpTnZxjvI9B6c2M7GEkWii224iwnQF9fz3fwBNvzPI/CdR2FP/Hu4V//Ie 744w== MIME-Version: 1.0 X-Received: by 10.224.14.14 with SMTP id e14mr7267871qaa.80.1397447864836; Sun, 13 Apr 2014 20:57:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.50.206 with HTTP; Sun, 13 Apr 2014 20:57:44 -0700 (PDT) In-Reply-To: <534B32FA.30500@herveybayaustralia.com.au> References: <534B32FA.30500@herveybayaustralia.com.au> Date: Sun, 13 Apr 2014 20:57:44 -0700 X-Google-Sender-Auth: etdt01228WV43SgAKBNT7gmQdPw Message-ID: Subject: Re: FBSD10 Atheros wifi not working From: Adrian Chadd To: Da Rock , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Questions X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 14 Apr 2014 03:57:46 -0000 Hi! You never said exactly what hardware it is Can you include a dmesg of the relevant bits during boot? Anything like the above kinda indicates there's some bigger issue going on. -a On 13 April 2014 17:59, Da Rock wrote: > The subject line may not be very descriptive, but I'm not sure exactly where > to point as to the problem. All other similar issues are a few years old > now, and on 8,9, some 7's. > > Long story short I'm just installing 10 (finally) on my laptop, and I need > to get it back up and running asap as I am swamped in work. I didn't think > it would be an issue as 9 had a decent working ath driver and I thought it > could only get better. I'm now emailing using yet another system with the > same device on 9, but a dying hdd which obviously also needs a reinstall on > new hdd. Wired is no good as we aren't equipped. > > So in bsdinstall, all works well and it sets up wifi easily. Reboot into the > new system an it has a coronary with messages from ath_reset_grablock, > ath_reset, ath_raw_xmit, ath_chan_set, ath_legacy_rx_tasklet: > > ath_reset: concurrent reset! danger! > > ath_reset_grablock: didn't finish after 10 iterations > ath_reset_grablock: warning, recursive reset path! > > ath_chan_set: concurrent reset! danger! > > ath_raw_xmit: sc_inreset_cnt > 0; bailing > > ath_legacy_rx_tasklet: sc_inreset_cnt > 0; bailing > > Scanning doesn't work; ath0 says it is associated, but wlan0 says no > channel. > > I've set dev.ath.0.hal.debug=1, but there is no ath.0.debug either under dev > or hw. I tried compiling the tools but it failed for lack of gcc. > > TIA guys, but I am really under the pump here as I thought this would be a > quick up and go now with the pkgng system as well in play. Now I'm up the > proverbial creek without a paddle. > > Cheers > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 14 07:53:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7BE7C33 for ; Mon, 14 Apr 2014 07:53:59 +0000 (UTC) Received: from smtpgate1.pacific.net.sg (smtpgate1.pacific.net.sg [192.169.41.31]) by mx1.freebsd.org (Postfix) with SMTP id 3A7D71FAF for ; Mon, 14 Apr 2014 07:53:58 +0000 (UTC) Received: (qmail 8939 invoked by uid 0); 14 Apr 2014 07:47:16 -0000 Received: from unknown (HELO UserPC) (lawrence.tan@streetdirectory.com@210.24.44.194) by smtpgate1.pacific.net.sg with ESMTPA; 14 Apr 2014 07:47:15 -0000 Message-ID: <27A323D2C8E14D9294A7FE6241DAE861@UserPC> From: "Lawrence Tan" To: Subject: configuring of wireless unix system Date: Mon, 14 Apr 2014 15:47:09 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 14 Apr 2014 07:54:00 -0000 Hi; Can you teach me how to configure wireless network connection in unix. Thanks and best regards Lawrence Tan From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 14 11:06:55 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05FD5284 for ; Mon, 14 Apr 2014 11:06:55 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CEBA41680 for ; Mon, 14 Apr 2014 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3EB6swr026070 for ; Mon, 14 Apr 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3EB6sr2026068 for freebsd-wireless@FreeBSD.org; Mon, 14 Apr 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Apr 2014 11:06:54 GMT Message-Id: <201404141106.s3EB6sr2026068@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.17 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, 14 Apr 2014 11:06:55 -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/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o kern/187624 wireless WEP and other ciphers do not work if h/w driver does n o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H 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/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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 195 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 15 00:36:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 774C9458 for ; Tue, 15 Apr 2014 00:36:24 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3921010BE for ; Tue, 15 Apr 2014 00:36:24 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id w8so8741121qac.13 for ; Mon, 14 Apr 2014 17:36: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=Mp/48lq4pmej/6mXUOSMXcoEh/dxIvvz27WMT+kksuk=; b=KRW3O0NN9cUZRNA0YVSIAdfpCpIRbyrKSda8+udCS3DELLJ8x+S1zUpNdyjKi2vE3z eZuezxm2Dwe9RhiRhhsxcYEMD0gJnOk1KPSb8U2K+wtZ8NkBKEH37UGIIAj6MtVBsyFp Oj+dOieC2fnvXy4xdDUQqLgOQFcFJtCZjn5uixg9fIEDuCUNPjZO9X5vFsAfLWJVELyd +xRnCf23bf0qD+DR1E4LeHRavF6I1IfYVkaA5QNia79G9hsALg53/++xK1WxljT8m4p/ h+ibNJmlpMmINRd8sNLrq1PFoHFCaqya3T6dz1r2yr/DZkKoXeYIRkcBQrCwBdKIRDQ7 NJSg== MIME-Version: 1.0 X-Received: by 10.140.38.149 with SMTP id t21mr52547434qgt.24.1397522183398; Mon, 14 Apr 2014 17:36:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Mon, 14 Apr 2014 17:36:23 -0700 (PDT) In-Reply-To: <27A323D2C8E14D9294A7FE6241DAE861@UserPC> References: <27A323D2C8E14D9294A7FE6241DAE861@UserPC> Date: Mon, 14 Apr 2014 17:36:23 -0700 X-Google-Sender-Auth: Dk3En96XEcqQ9gnjW3vrYppdzT4 Message-ID: Subject: Re: configuring of wireless unix system From: Adrian Chadd To: Lawrence Tan Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Apr 2014 00:36:24 -0000 Hi! ON FreeBSD? Try http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html -a On 14 April 2014 00:47, Lawrence Tan wrote: > Hi; > > Can you teach me how to configure wireless network connection in unix. > > Thanks and best regards > > Lawrence Tan > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 15 17:07:21 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D4562B3; Tue, 15 Apr 2014 17:07:21 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70C871396; Tue, 15 Apr 2014 17:07:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3FH7LlJ037936; Tue, 15 Apr 2014 17:07:21 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3FH7LHN037935; Tue, 15 Apr 2014 17:07:21 GMT (envelope-from linimon) Date: Tue, 15 Apr 2014 17:07:21 GMT Message-Id: <201404151707.s3FH7LHN037935@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/188654: [urtwn] tp-link wl-725n Realtek 8188 chip do not work with urtwn driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 15 Apr 2014 17:07:21 -0000 Old Synopsis: tp-link wl-725n Realtek 8188 chip do not work with urtwn driver New Synopsis: [urtwn] tp-link wl-725n Realtek 8188 chip do not work with urtwn driver Responsible-Changed-From-To: freebsd-amd64->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Tue Apr 15 17:06:39 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=188654 From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 15 17:50:02 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 565C6FFC for ; Tue, 15 Apr 2014 17:50:02 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4352E17D2 for ; Tue, 15 Apr 2014 17:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3FHo2wl051771 for ; Tue, 15 Apr 2014 17:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3FHo1Ag051770; Tue, 15 Apr 2014 17:50:01 GMT (envelope-from gnats) Date: Tue, 15 Apr 2014 17:50:01 GMT Message-Id: <201404151750.s3FHo1Ag051770@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Sean Bruno Subject: Re: kern/188654: [urtwn] tp-link wl-725n Realtek 8188 chip do not work with urtwn driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Sean Bruno 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, 15 Apr 2014 17:50:02 -0000 The following reply was made to PR kern/188654; it has been noted by GNATS. From: Sean Bruno To: bug-followup@FreeBSD.org, ogldelphi@mail.ru Cc: Subject: Re: kern/188654: [urtwn] tp-link wl-725n Realtek 8188 chip do not work with urtwn driver Date: Tue, 15 Apr 2014 10:45:19 -0700 --=-4Rw1Pi7ue+VLo81TboAf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Its hard to tell, but my scan of the internet seems to indicate that this is a chipset variant that isn't supported by urtwn(4). If this is a "v2" chipset then I think it applies. I'm not real sure how to tell if this link is applicable to you or not. http://www.raspberrypi.org/forums/viewtopic.php?f=3D91&t=3D29752 It looks like this is a rtl8188eu as opposed to a supported rtl8188cus. In linux-land they are seperate driver modules. sean --=-4Rw1Pi7ue+VLo81TboAf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTTXAoAAoJEBkJRdwI6BaHJPUH/3LZBzxXt5FCC7WLORc8kbK8 gU+bHo0WT23h8cQ76IjNsMl/JuIfccKrGITRaDqi6eSccaVPS/D/aZh8XVRxv84j RhjR3fAHYASprPg4AUKdoWazLOCPKj2kTZT219wDU4heTjOSiKWyhkV3l61MLql2 THxL9LpLNgfFifSLVdr9tnabUXorY0CfiWIeUtD8cY/hDLLODSSTrbyhZojJrIGt yGsKU/qbz30CyBVIXcBVH5m+ZKCk4iVY5D/4ZAv6xwaXuTwu165j91qJgtasIvII lixOJ4w2Ml2FSDEcoTWLIi8jpvaj/BO8VJ+QvXSejES6l45FBsB4Z2G2GVEmhOE= =7CoA -----END PGP SIGNATURE----- --=-4Rw1Pi7ue+VLo81TboAf-- From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 16 01:49:58 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C6338BB; Wed, 16 Apr 2014 01:49:58 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2EBF187F; Wed, 16 Apr 2014 01:49:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3G1nvEI015957; Wed, 16 Apr 2014 01:49:57 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3G1nvIF015956; Wed, 16 Apr 2014 01:49:57 GMT (envelope-from linimon) Date: Wed, 16 Apr 2014 01:49:57 GMT Message-Id: <201404160149.s3G1nvIF015956@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: bin/187470: [bthidd] [patch] Apple Wireless Keyboard (JIS) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 16 Apr 2014 01:49:58 -0000 Old Synopsis: [patch] Apple Wireless Keyboard (JIS) New Synopsis: [bthidd] [patch] Apple Wireless Keyboard (JIS) Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Wed Apr 16 01:48:47 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=187470 From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 17 10:40:02 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF878813 for ; Thu, 17 Apr 2014 10:40:02 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A08061932 for ; Thu, 17 Apr 2014 10:40:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3HAe2pQ010916 for ; Thu, 17 Apr 2014 10:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3HAe155010915; Thu, 17 Apr 2014 10:40:01 GMT (envelope-from gnats) Date: Thu, 17 Apr 2014 10:40:01 GMT Message-Id: <201404171040.s3HAe155010915@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Anton Shterenlikht Subject: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Anton Shterenlikht 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, 17 Apr 2014 10:40:02 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: Anton Shterenlikht To: bug-followup@freebsd.org Cc: Subject: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Thu, 17 Apr 2014 11:33:24 +0100 (BST) Still the same in r264294 amd64: iwn0: mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 iwn0: device timeout wlan0: link state changed to UP wlan0: link state changed to DOWN iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000203430000 branch link = 0x00007A10000004C2 interrupt link = 0x000006DE00007A4C time = 201920 driver status: tx ring 0: qid=0 cur=20 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=23 queued=0 tx ring 4: qid=4 cur=111 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=29 wlan0: Ethernet address: 00:21:5c:50:68:c3 iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000202030000 branch link = 0x00005CEE000004C2 interrupt link = 0x000006DE00007386 time = 270960 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=3 queued=0 tx ring 4: qid=4 cur=67 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=45 wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00003BBA000004C2 interrupt link = 0x000006DE00003C5A time = 3270454051 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=3 queued=0 tx ring 4: qid=4 cur=78 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=23 wlan0: link state changed to DOWN wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: Ethernet address: 00:21:5c:50:68:c3 iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DE000018B8 time = 11589053 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=1 queued=0 tx ring 4: qid=4 cur=45 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=42 wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 18 11:40:05 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C31BD719 for ; Fri, 18 Apr 2014 11:40:05 +0000 (UTC) Received: from mail.hemio.de (mail.hemio.de [176.9.40.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 878E715C3 for ; Fri, 18 Apr 2014 11:40:05 +0000 (UTC) Received: from bulldozer.local (p4FC24B24.dip0.t-ipconnect.de [79.194.75.36]) by mail.hemio.de (Postfix) with ESMTPSA id 5B29480 for ; Fri, 18 Apr 2014 13:32:02 +0200 (CEST) Date: Fri, 18 Apr 2014 13:32:00 +0200 From: Roman Naumann To: freebsd-wireless@FreeBSD.org Subject: State of ath(4) Driver Message-ID: <20140418113200.GB1217@bulldozer.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 18 Apr 2014 11:40:05 -0000 Hello list members! I plan to buy a ath(4) supported wlan card. unfortunately, the man page seems out of date by several years. It fails to mention chips newer than AR5416 and does not explain whether 40mhz channel width is supported (and some other features). Other information found on the internet says: https://www.freebsd.org/news/status/report-2011-07-2011-09.html: "AR5416, AR9160, and AR9280 functions in both station and hostap mode. Performance is good." but: "open task: Correct handling of 20<->20/40mhz transitions (without dropping frames)" http://adrianchadd.blogspot.de/2012/06/dont-let-anyone-tell-you-that-freebsd.html: The output of "athstats" indicates that 40mhz works, but I dont know how good and if there are the aforementioned packet losses when switching modes. Long story short: What is the status of the ath(4) driver, in particular regarding: -> 802.11{a,g}n -> multiple hostap virtual interfaces (man page "[yes,] on cards that use a 5212 part) -> WPA (man page says "WPA is not supported for 5210 parts") -> use of 5ghz band -> dualband (2.4ghz and 5ghz at same time) -> 40mhz channel width -> supported chipsets (newer than AR5416) Also, are there any issues (in general or with some chips) which users should know about before buying one? Is there another place where documentation can be found which I failed to find? Regards, Roman Naumann From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 19 14:34:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5EA544A6; Sat, 19 Apr 2014 14:34:54 +0000 (UTC) Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 091CC1804; Sat, 19 Apr 2014 14:34:53 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id w8so2423538qac.40 for ; Sat, 19 Apr 2014 07:34:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=stFRs5iZwefHas1I7a5/VEiyz/5URduqahj4AAbnNJw=; b=nMod5LJ371BfJXNmIxnxhr68aci9kOh6wsqq82HpjO6a/5LQplMJ+ct/Iy7POpNWS8 p4K0qhNJ4VQRvKOayR7VhfBY9yyrAISxjq190n64j8hyoUW332VkGHk7uY1IqZdgiCoJ yQ74dc7C+UHTnl7tD6pTXm3gAPDTNM+5SSWNRBtLbNB2U6ySGKXynjfbxAJhtRuprtBn R1ygko/G92Pvv1YJr2KbPEVZ/pW8NzxhzF8wVLcwFylAO4NSp1++YtfKyXKY9ZXG8Rth hrcri1DY43xLPFQtl2+9nsoeM9BKMIM3f/xgX1F0jL6Dys/cigRZiWXn95p0KHmMN+Vo FH4A== MIME-Version: 1.0 X-Received: by 10.224.29.4 with SMTP id o4mr26493909qac.55.1397918093005; Sat, 19 Apr 2014 07:34:53 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Sat, 19 Apr 2014 07:34:52 -0700 (PDT) In-Reply-To: <53511DC2.6070501@herveybayaustralia.com.au> References: <534B32FA.30500@herveybayaustralia.com.au> <534BC380.90608@herveybayaustralia.com.au> <534E80AB.4000007@herveybayaustralia.com.au> <5350780F.2070806@herveybayaustralia.com.au> <535116CA.9060009@herveybayaustralia.com.au> <53511DC2.6070501@herveybayaustralia.com.au> Date: Sat, 19 Apr 2014 07:34:52 -0700 X-Google-Sender-Auth: pplvgFwFb1pnzNMlOR9zs1Qikh4 Message-ID: Subject: Re: FBSD10 Atheros wifi not working From: Adrian Chadd To: Da Rock , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Questions X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 19 Apr 2014 14:34:54 -0000 On 18 April 2014 05:42, Da Rock wrote: > > Skipped another thought - I wouldn't have thought the laptop I have was too > badly built, and how would the noise cause the error messages? I didn't have > that many messages for the iwn in the m/c's prior, is it just the atheros > chipsets? I kind of expect some reconnection issues, but the hardware reset > messages (from 9.x) were disconcerting - these current ones are obviously > worse. > > And I meant to add: where do I go now? Should I send you the logs or other > errors? Well, I highly recommend rebuilding with debugging in your kernel config: * ATH_DEBUG * AH_DEBUG * ATH_DIAGAPI And then figure out why you can't build the ath tools. The output from athstats will likely be helpful. The reset stuff is interesting - it means the NIC is taking way too long to finish some task. Normally grabbing that lock doesn't take too long, but something has your NIC angry. Yes, please compile up athstats at least. :-) -a From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 19 14:46:25 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55F7E661 for ; Sat, 19 Apr 2014 14:46:25 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 182A818D0 for ; Sat, 19 Apr 2014 14:46:25 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id j15so2455868qaq.16 for ; Sat, 19 Apr 2014 07:46: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=pbOfUToa0QXhEkapymoWnQCn6BUv1zGqXJBO61bgNno=; b=ePyMC2ljxJcTfkpFmlAlK5JMnqgzR6NFFbUHpkc/Hhjd8kH00vRZOlKETfLLfCq8lB Thrn4vMgMjaLT8oDrpV1DaY5PzbVNNd93WfOWQvHF00DKjOS6hOXbCCfj3w2nTOZkPF+ L/Im9wUW7FIRE9izrSPP9DjPKoZG64o9d5enYZ/0piQDBb1rCLfsiYrdZyPTn9UreFQ8 F12BUDlOB62khy+JG8cF0kcTjE2lGHl/cwPedeRWSG7TdyxKAVmG2SiVhoYSyTrkBsO/ 1nLFn3a2nEpb0ow97yiF3m3LRDRUWQNhikkwvDMcyKay2S9i1FM07puggqw7TAcNVKV/ /XlQ== MIME-Version: 1.0 X-Received: by 10.224.13.142 with SMTP id c14mr26757768qaa.76.1397918784242; Sat, 19 Apr 2014 07:46:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Sat, 19 Apr 2014 07:46:24 -0700 (PDT) In-Reply-To: <20140418113200.GB1217@bulldozer.local> References: <20140418113200.GB1217@bulldozer.local> Date: Sat, 19 Apr 2014 07:46:24 -0700 X-Google-Sender-Auth: sd3G2FkulZLfkt-GZwqC-MZ3tJg Message-ID: Subject: Re: State of ath(4) Driver From: Adrian Chadd To: Roman Naumann Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 19 Apr 2014 14:46:25 -0000 Hi! I just updated the manpage for ath(4) in -HEAD. TL;DR: * 11n is fine in STA and hostap mode. I'm still debugging things, but it's usable. * multiple VAP is fine. Just put 'bssid' on the ifconfig create line so each VAP gets autoassigned a separate MAC address * WPA is supported. I even made it work on the 5210. * 5ghz is fine. * You can use both 2.4 and 5, just not simultaneously on the same card * 20 and 40MHz channel widths are fine * Everything up to the AR9565 should work okay. -a On 18 April 2014 04:32, Roman Naumann wrote: > Hello list members! > > I plan to buy a ath(4) supported wlan card. > > unfortunately, the man page seems out of date by several years. > It fails to mention chips newer than AR5416 and does not explain whether > 40mhz channel width is supported (and some other features). > > Other information found on the internet says: > > https://www.freebsd.org/news/status/report-2011-07-2011-09.html: > "AR5416, AR9160, and AR9280 functions in both station and hostap mode. Performance is good." > but: "open task: Correct handling of 20<->20/40mhz transitions (without dropping frames)" > > http://adrianchadd.blogspot.de/2012/06/dont-let-anyone-tell-you-that-freebsd.html: > The output of "athstats" indicates that 40mhz works, but I dont know how good and if there are the aforementioned packet losses when switching modes. > > Long story short: > > What is the status of the ath(4) driver, in particular regarding: > > -> 802.11{a,g}n > -> multiple hostap virtual interfaces (man page "[yes,] on cards that use a 5212 part) > -> WPA (man page says "WPA is not supported for 5210 parts") > -> use of 5ghz band > -> dualband (2.4ghz and 5ghz at same time) > -> 40mhz channel width > -> supported chipsets (newer than AR5416) > > Also, are there any issues (in general or with some chips) which > users should know about before buying one? > > Is there another place where documentation can be found which I failed to find? > > Regards, > Roman Naumann > _______________________________________________ > 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 Sun Apr 20 01:45:48 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 26191E27; Sun, 20 Apr 2014 01:45:48 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF6C51791; Sun, 20 Apr 2014 01:45:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3K1jlia086548; Sun, 20 Apr 2014 01:45:47 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3K1jlrs086547; Sun, 20 Apr 2014 01:45:47 GMT (envelope-from linimon) Date: Sun, 20 Apr 2014 01:45:47 GMT Message-Id: <201404200145.s3K1jlrs086547@freefall.freebsd.org> To: parv@pair.com, linimon@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/137592: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 01:45:48 -0000 Old Synopsis: [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network New Synopsis: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network State-Changed-From-To: open->open State-Changed-By: linimon State-Changed-When: Sun Apr 20 01:43:17 UTC 2014 State-Changed-Why: to submitter: is this PR still relevant? http://www.freebsd.org/cgi/query-pr.cgi?pr=137592 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 20 01:46:51 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E5F4F1B; Sun, 20 Apr 2014 01:46:51 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43D6417A0; Sun, 20 Apr 2014 01:46:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3K1kpaT086627; Sun, 20 Apr 2014 01:46:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3K1kpqQ086626; Sun, 20 Apr 2014 01:46:51 GMT (envelope-from linimon) Date: Sun, 20 Apr 2014 01:46:51 GMT Message-Id: <201404200146.s3K1kpqQ086626@freefall.freebsd.org> To: gjb@FreeBSD.org, linimon@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/178470: [panic][ath] bss vap can and does change X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 01:46:51 -0000 Synopsis: [panic][ath] bss vap can and does change State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Apr 20 01:43:17 UTC 2014 State-Changed-Why: committed over one year ago. http://www.freebsd.org/cgi/query-pr.cgi?pr=178470 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 20 01:47:19 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 622DCF45; Sun, 20 Apr 2014 01:47:19 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 387AE17B6; Sun, 20 Apr 2014 01:47:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3K1lJMr086838; Sun, 20 Apr 2014 01:47:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3K1lI5u086837; Sun, 20 Apr 2014 01:47:18 GMT (envelope-from linimon) Date: Sun, 20 Apr 2014 01:47:18 GMT Message-Id: <201404200147.s3K1lI5u086837@freefall.freebsd.org> To: w8hdkim@gmail.com, linimon@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/179232: [ath] panic in ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 01:47:19 -0000 Synopsis: [ath] panic in ath State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Apr 20 01:43:17 UTC 2014 State-Changed-Why: fixed nearly 1 year ago. http://www.freebsd.org/cgi/query-pr.cgi?pr=179232 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 20 02:52:34 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E43CCD8F; Sun, 20 Apr 2014 02:52:34 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B95B71CCC; Sun, 20 Apr 2014 02:52:34 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3K2qYs7012228; Sun, 20 Apr 2014 02:52:34 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3K2qYqk012227; Sun, 20 Apr 2014 02:52:34 GMT (envelope-from linimon) Date: Sun, 20 Apr 2014 02:52:34 GMT Message-Id: <201404200252.s3K2qYqk012227@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/168754: [ath] if_ath dont have internal name X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 02:52:35 -0000 Old Synopsis: if_ath dont have internal name New Synopsis: [ath] if_ath dont have internal name Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 20 02:52:15 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=168754 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 20 22:29:49 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4CC4F05 for ; Sun, 20 Apr 2014 22:29:49 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) by mx1.freebsd.org (Postfix) with ESMTP id 9A1F31AC9 for ; Sun, 20 Apr 2014 22:29:49 +0000 (UTC) Received: from [204.210.114.114] ([204.210.114.114:33754] helo=localhost.hawaii.res.rr.com) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 8F/74-30401-55A44535; Sun, 20 Apr 2014 22:29:41 +0000 Received: by localhost.hawaii.res.rr.com (Postfix, from userid 1000) id E203F5D90; Sun, 20 Apr 2014 12:30:22 -1000 (HST) Date: Sun, 20 Apr 2014 12:30:22 -1000 From: Parv To: linimon@FreeBSD.org Subject: Re: kern/137592: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network Message-ID: <20140420223022.GA2341@holstein.holy.cow> References: <201404200145.s3K1jlrs086547@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201404200145.s3K1jlrs086547@freefall.freebsd.org> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Cc: freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 22:29:49 -0000 in message <201404200145.s3K1jlrs086547@freefall.freebsd.org>, wrote linimon@FreeBSD.org thusly... > > Old Synopsis: [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network > New Synopsis: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network > > State-Changed-From-To: open->open > State-Changed-By: linimon > State-Changed-When: Sun Apr 20 01:43:17 UTC 2014 > State-Changed-Why: > to submitter: is this PR still relevant? I cannot say yet as Thinkpad T61 has been out of commission for now. It would be some time before I get to use it again. In that case, I would try 8- or 9-STABLE, skipping 7-STABLE. > http://www.freebsd.org/cgi/query-pr.cgi?pr=137592 - Parv -- From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 20 22:34:58 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99FCCF42; Sun, 20 Apr 2014 22:34:58 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F1E31B5A; Sun, 20 Apr 2014 22:34:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3KMYwSU015400; Sun, 20 Apr 2014 22:34:58 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3KMYv9e015399; Sun, 20 Apr 2014 22:34:57 GMT (envelope-from linimon) Date: Sun, 20 Apr 2014 22:34:57 GMT Message-Id: <201404202234.s3KMYv9e015399@freefall.freebsd.org> To: parv@pair.com, linimon@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/137592: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 22:34:58 -0000 Synopsis: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Apr 20 22:34:13 UTC 2014 State-Changed-Why: machine is no longer available to test with. http://www.freebsd.org/cgi/query-pr.cgi?pr=137592 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 20 22:40:02 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BAF64E3 for ; Sun, 20 Apr 2014 22:40:02 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A802A1B82 for ; Sun, 20 Apr 2014 22:40:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3KMe2BB015590 for ; Sun, 20 Apr 2014 22:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3KMe29U015589; Sun, 20 Apr 2014 22:40:02 GMT (envelope-from gnats) Date: Sun, 20 Apr 2014 22:40:02 GMT Message-Id: <201404202240.s3KMe29U015589@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Mark Linimon Subject: Re: kern/137592: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Mark Linimon List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 22:40:02 -0000 The following reply was made to PR kern/137592; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/137592: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network Date: Sun, 20 Apr 2014 17:34:40 -0500 ----- Forwarded message from Parv ----- Date: Sun, 20 Apr 2014 12:30:22 -1000 From: Parv To: linimon@FreeBSD.org Cc: freebsd-wireless@FreeBSD.org Subject: Re: kern/137592: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network in message <201404200145.s3K1jlrs086547@freefall.freebsd.org>, wrote linimon@FreeBSD.org thusly... > > Old Synopsis: [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network > New Synopsis: [ath] [panic] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on network > > State-Changed-From-To: open->open > State-Changed-By: linimon > State-Changed-When: Sun Apr 20 01:43:17 UTC 2014 > State-Changed-Why: > to submitter: is this PR still relevant? I cannot say yet as Thinkpad T61 has been out of commission for now. It would be some time before I get to use it again. In that case, I would try 8- or 9-STABLE, skipping 7-STABLE. > http://www.freebsd.org/cgi/query-pr.cgi?pr=137592 - Parv -- ----- End forwarded message ----- From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 21 11:06:56 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C1AA195 for ; Mon, 21 Apr 2014 11:06:56 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EF551981 for ; Mon, 21 Apr 2014 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3LB6unw085901 for ; Mon, 21 Apr 2014 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3LB6tN2085899 for freebsd-wireless@FreeBSD.org; Mon, 21 Apr 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Apr 2014 11:06:55 GMT Message-Id: <201404211106.s3LB6tN2085899@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.17 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 Apr 2014 11:06:56 -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/188654 wireless [urtwn] tp-link wl-725n Realtek 8188 chip do not work o kern/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o bin/187624 wireless [patch] wpa_supplicant(8): WEP and other ciphers do no o bin/187470 wireless [bthidd] [patch] Apple Wireless Keyboard (JIS) o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] [panic] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP fails, WPA o kern/185025 wireless [iwi] [panic] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181694 wireless [iwn] [patch] Initialize hardware in iwn(4) resume cod o kern/181161 wireless [wl] [panic] config a old compaq wl-110 wireless card 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/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/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/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/168754 wireless [ath] if_ath dont have internal name 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/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] kernel panic: page fault with ath0 taskq 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 195 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 21 12:15:52 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 039429BF for ; Mon, 21 Apr 2014 12:15:52 +0000 (UTC) Received: from nm7.bullet.mail.bf1.yahoo.com (nm7.bullet.mail.bf1.yahoo.com [98.139.212.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2FB811BC for ; Mon, 21 Apr 2014 12:15:51 +0000 (UTC) Received: from [98.139.214.32] by nm7.bullet.mail.bf1.yahoo.com with NNFMP; 21 Apr 2014 12:13:19 -0000 Received: from [68.142.230.72] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 21 Apr 2014 12:13:19 -0000 Received: from [127.0.0.1] by smtp229.mail.bf1.yahoo.com with NNFMP; 21 Apr 2014 12:13:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1398082399; bh=32mPkJG0IkyVi4hTfV8gLS0VDZrGfZ+cOfmXoDxr7xU=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=CpN3Wn3cDX2hOByJJM5sRkmX4iGlxMFNvn50Vz8uqDSI5APFgLchzih9QQM0UeA3w/L1P2uIyxs+y6VotlN/lgUz8sdiRhxMIxhOOItC5l9Td5sSMLcL93BxFHW45mVESIMuWRcnQ1kZiI5aDvzOPg3Q77puuQVs0rVj7SfSoh8= X-Yahoo-Newman-Id: 494133.61853.bm@smtp229.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 4pLHtW8VM1mIP6FbiaJErJZZFkQuXC_o3t5OH5lDO1L7hJu 0FEg_U.DeiynvFM0dWZG3A4KTwY5u3awL.gwOVVDvo.Htfy9cyz00DyF3zKm 4sfqpL561D7lJCd2V_uBrPfDjlTqKsqErRDjOP3ZZbO_BI11CHLyWVeYdEdo G5ghzuoapI.f9dGzR3ZjmuWBM4O9FxdcLpCa.dQ9Sz62aCgsBlI3x.POPzQf T5.Bx799xGIOoXbR3niNGNKY2sPjogzypq7UrILoKlT2JCWWaN5G7zERIMg0 J6vOCLi75sY4Ok7OindyCdBlJ9wiIdpj8qYBJDed5pBlwMHKqWx.83p4qJg2 Tx8rIzzeCIw2IDZfFa2hPKXo7yQLnm1BYlM.pFNl6dbwRu_XXZYRe8Djt1P_ pY4uGvf7k1SXX5M_Oz35WgwsB2ldTYhkpvILbu2EVpnqjzSvbWGPH8rRlbRv _fDetRnCapGI5M1gqwvHbzI73L0Bx38q1dLB1iHyRkYS9MT12fCEsBp9igkK ThzMWYJoN2cCdA_dgYQ5_ag-- X-Yahoo-SMTP: 9sPoSQ2swBBlERuQ.0vs8XLc_MeClW0- X-Rocket-Received: from [10.0.1.88] (Scoobi_doo@70.90.74.161 with plain [98.138.105.21]) by smtp229.mail.bf1.yahoo.com with SMTP; 21 Apr 2014 12:13:19 +0000 UTC Message-ID: <53550B59.6020103@yahoo.com> Date: Mon, 21 Apr 2014 08:13:13 -0400 From: Anthony Jenkins User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: urtwn panic Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 12:15:52 -0000 I'm getting a panic with the latest kernel (r264719) and the if_urtwn driver. I have a coredump available to triage. [root@ajenkins-hplaptop /usr/src]# kgdb /usr/obj/usr/src/sys/MYKERNEL/kernel.debug /var/crash/vmcore.last 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: Sleeping on "fwload" with the following non-sleepable locks held: exclusive sleep mutex urtwn0 (network driver) r = 0 (0xfffffe00175fe348) locked @ /usr/src/sys/dev/usb/usb_request.c:722 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0447e095e0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0447e09690 witness_warn() at witness_warn+0x4b5/frame 0xfffffe0447e09750 _sleep() at _sleep+0x70/frame 0xfffffe0447e097f0 firmware_get() at firmware_get+0x13a/frame 0xfffffe0447e09850 urtwn_init_locked() at urtwn_init_locked+0x18cd/frame 0xfffffe0447e09910 urtwn_ioctl() at urtwn_ioctl+0x12a/frame 0xfffffe0447e09960 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfffffe0447e099c0 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfffffe0447e099f0 fork_exit() at fork_exit+0x84/frame 0xfffffe0447e09a30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0447e09a30 --- trap 0, rip = 0, rsp = 0xfffffe0447e09af0, rbp = 0 --- Sleeping thread (tid 100892, pid 0) owns a non-sleepable lock KDB: stack backtrace of thread 100892: sched_switch() at sched_switch+0x47f/frame 0xfffffe0447e096a0 mi_switch() at mi_switch+0x179/frame 0xfffffe0447e096e0 sleepq_switch() at sleepq_switch+0x152/frame 0xfffffe0447e09720 sleepq_wait() at sleepq_wait+0x43/frame 0xfffffe0447e09750 _sleep() at _sleep+0x366/frame 0xfffffe0447e097f0 firmware_get() at firmware_get+0x13a/frame 0xfffffe0447e09850 urtwn_init_locked() at urtwn_init_locked+0x18cd/frame 0xfffffe0447e09910 urtwn_ioctl() at urtwn_ioctl+0x12a/frame 0xfffffe0447e09960 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfffffe0447e099c0 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfffffe0447e099f0 fork_exit() at fork_exit+0x84/frame 0xfffffe0447e09a30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0447e09a30 --- trap 0, rip = 0, rsp = 0xfffffe0447e09af0, rbp = 0 --- panic: sleeping thread cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0447e814b0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0447e81560 vpanic() at vpanic+0x124/frame 0xfffffe0447e815a0 panic() at panic+0x43/frame 0xfffffe0447e81600 propagate_priority() at propagate_priority+0x2fd/frame 0xfffffe0447e81640 turnstile_wait() at turnstile_wait+0x34f/frame 0xfffffe0447e81690 __mtx_lock_sleep() at __mtx_lock_sleep+0x1b6/frame 0xfffffe0447e81710 __mtx_lock_flags() at __mtx_lock_flags+0x102/frame 0xfffffe0447e81760 urtwn_ioctl() at urtwn_ioctl+0x41/frame 0xfffffe0447e817b0 ifioctl() at ifioctl+0x8f5/frame 0xfffffe0447e81870 kern_ioctl() at kern_ioctl+0x22b/frame 0xfffffe0447e818d0 sys_ioctl() at sys_ioctl+0x13c/frame 0xfffffe0447e81920 amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe0447e81a30 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0447e81a30 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x800fa342a, rsp = 0x7fffffffdc88, rbp = 0x7fffffffe500 --- KDB: enter: panic Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols ... #0 doadump (textdump=0) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump (textdump=0) at pcpu.h:219 #1 0xffffffff802fb8ae in db_dump (dummy=, dummy2=0, dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:543 #2 0xffffffff802fb34d in db_command (cmd_table=0x0) at /usr/src/sys/ddb/db_command.c:449 #3 0xffffffff802fb0c4 in db_command_loop () at /usr/src/sys/ddb/db_command.c:502 #4 0xffffffff802fda90 in db_trap (type=, code=0) at /usr/src/sys/ddb/db_main.c:231 #5 0xffffffff80628289 in kdb_trap (type=3, code=0, tf=) at /usr/src/sys/kern/subr_kdb.c:656 #6 0xffffffff808ad8ae in trap (frame=0xfffffe0447e81490) at /usr/src/sys/amd64/amd64/trap.c:573 #7 0xffffffff80892262 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff806279ee in kdb_enter (why=0xffffffff809d5a90 "panic", msg=) at cpufunc.h:63 #9 0xffffffff805f0594 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:749 #10 0xffffffff805f0603 in panic (fmt=0xffffffff80d41e50 "\004") at /usr/src/sys/kern/kern_shutdown.c:685 #11 0xffffffff8063ab6d in propagate_priority (td=) at /usr/src/sys/kern/subr_turnstile.c:226 ---Type to continue, or q to quit--- #12 0xffffffff8063b43f in turnstile_wait (ts=0xfffff801253a56c0, owner=, queue=0) at /usr/src/sys/kern/subr_turnstile.c:742 #13 0xffffffff805dbb76 in __mtx_lock_sleep (c=0xfffffe00175fe360, tid=18446735283083894784, opts=, file=, line=) at /usr/src/sys/kern/kern_mutex.c:508 #14 0xffffffff805db912 in __mtx_lock_flags (c=, opts=0, file=0xffffffff81ab33e8 "/usr/src/sys/modules/usb/urtwn/../../../dev/usb/wlan/if_urtwn.c", line=1787) at /usr/src/sys/kern/kern_mutex.c:223 #15 0xffffffff81aa9b51 in urtwn_ioctl (ifp=0xfffff80125a3e800, cmd=3223349575, data=0xfffff80011577780 "urtwn0") at /usr/src/sys/modules/usb/urtwn/../../../dev/usb/wlan/if_urtwn.c:1787 #16 0xffffffff806bad65 in ifioctl (so=0xfffff80192990828, cmd=3223349575, data=0xfffff80011577780 "urtwn0", td=0xfffff80145e16000) at /usr/src/sys/net/if.c:2465 #17 0xffffffff80648c5b in kern_ioctl (td=, fd=, com=) at file.h:323 #18 0xffffffff806489dc in sys_ioctl (td=0xfffff80145e16000, uap=0xfffffe0447e819c0) at /usr/src/sys/kern/sys_generic.c:702 #19 0xffffffff808ae78a in amd64_syscall (td=0xfffff80145e16000, traced=0) at subr_syscall.c:133 #20 0xffffffff8089254b in Xfast_syscall () ---Type to continue, or q to quit--- at /usr/src/sys/amd64/amd64/exception.S:390 #21 0x0000000800fa342a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) Anthony Jenkins From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 21 13:12:20 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1687429; Mon, 21 Apr 2014 13:12:19 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C688F166B; Mon, 21 Apr 2014 13:12:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3LDCJjQ029547; Mon, 21 Apr 2014 13:12:19 GMT (envelope-from sbruno@freefall.freebsd.org) Received: (from sbruno@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3LDCIDb029546; Mon, 21 Apr 2014 13:12:18 GMT (envelope-from sbruno) Date: Mon, 21 Apr 2014 13:12:18 GMT Message-Id: <201404211312.s3LDCIDb029546@freefall.freebsd.org> To: takawata@init-main.com, sbruno@FreeBSD.org, freebsd-usb@FreeBSD.org, freebsd-wireless@FreeBSD.org From: sbruno@FreeBSD.org Subject: Re: usb/184918: [ural] regression on WEP X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 13:12:20 -0000 Synopsis: [ural] regression on WEP State-Changed-From-To: open->feedback State-Changed-By: sbruno State-Changed-When: Mon Apr 21 13:11:36 UTC 2014 State-Changed-Why: Responsible-Changed-From-To: freebsd-usb->freebsd-wireless Responsible-Changed-By: sbruno Responsible-Changed-When: Mon Apr 21 13:11:36 UTC 2014 Responsible-Changed-Why: Update and moved to wireless as that's who fixed this http://www.freebsd.org/cgi/query-pr.cgi?pr=184918 From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 21 16:30:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68B9C790 for ; Mon, 21 Apr 2014 16:30:48 +0000 (UTC) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28F0E1963 for ; Mon, 21 Apr 2014 16:30:48 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id x3so4238269qcv.12 for ; Mon, 21 Apr 2014 09:30:47 -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=j5SY4zH4hwag/6PEwUknBq0W4GsEeBd8vhKBZ+07pRI=; b=sNj0LQTg05uFcC20wf0j4BN4vdFGxCy72EFtIJg+IcYRYWD0CZspnLVzMtqygsz6aF 9d3JlWfuS8R1fjUjilbCJzaj0QQtFSOFugGfCE/lLtQ3zHzXc98AbXlYgpYcJPGLcjIh sc3iuhp+GYbyUW8/6JqLnsKfCKhS3DTRiOYI9yBRHTdhUX29iMteOnVUkqu4d2DC7W1R t6AMDvfeq+yKnSqQfskmzvG0kmy9LffF+yQY1IJemPgeXS7ftPE7iBI4k2imcRgwjn3y kcT1RX4nsXp4RcxPHWBJhT/v5i+7bhLdU6w29n9mLFcDMm0qmbkpf/ZFIX9zTpoqRFhA OBfQ== MIME-Version: 1.0 X-Received: by 10.224.76.74 with SMTP id b10mr43291837qak.49.1398097847332; Mon, 21 Apr 2014 09:30:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Mon, 21 Apr 2014 09:30:47 -0700 (PDT) In-Reply-To: <20140421155853.GD1602@mail0.byshenk.net> References: <201404210205.s3L25p9U064240@svn.freebsd.org> <20140421155853.GD1602@mail0.byshenk.net> Date: Mon, 21 Apr 2014 09:30:47 -0700 X-Google-Sender-Auth: KIrEGnwT92QzzH78nujV8CSmNjE Message-ID: Subject: Re: svn commit: r264710 - head/sys/dev/ath From: Adrian Chadd To: Greg Byshenk , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 16:30:48 -0000 Hi, Which NIC? -a On 21 April 2014 08:58, Greg Byshenk wrote: > On Sun, Apr 20, 2014 at 07:09:33PM -0700, Adrian Chadd wrote: >> I didn't say it in the commit message, but this should be MFCed to stable/10 . > > > Adrian- > > I'm curious as to what this addresses. > > I attempted to move a router/access point to FreeBSD 10 over the > weekend, and had to revert back to 9 as it was a terrible failure. > > It would invariably spew out masses of 'stuck beacon; resetting' > errors, and then at some point (not obviuously correlated with > those errors) lock up (hard, requiring a hard reset). > > If it is something that the patch might address, then I'll watch > for an MFC to stable/10 > > Thanks, > -greg > > >> On 20 April 2014 19:05, Adrian Chadd wrote: >> > Author: adrian >> > Date: Mon Apr 21 02:05:51 2014 >> > New Revision: 264710 >> > URL: http://svnweb.freebsd.org/changeset/base/264710 >> > >> > Log: >> > Make sure bf_next is NULL'ed out when we're completing up an aggregate >> > frame through the cleanup path. >> > >> > Whilst here, fix the indenting for something I messed up. >> > >> > Tested: >> > >> > * AR5416, STA mode >> > >> > Modified: >> > head/sys/dev/ath/if_ath_tx.c >> > >> > Modified: head/sys/dev/ath/if_ath_tx.c >> > ============================================================================== >> > --- head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:04:37 2014 (r264709) >> > +++ head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:05:51 2014 (r264710) >> > @@ -4600,10 +4600,11 @@ ath_tx_comp_cleanup_aggr(struct ath_soft >> > >> > ATH_TX_UNLOCK(sc); >> > >> > - /* Handle frame completion */ >> > + /* Handle frame completion as individual frames */ >> > bf = bf_first; >> > while (bf) { >> > bf_next = bf->bf_next; >> > + bf->bf_next = NULL; >> > ath_tx_default_comp(sc, bf, 1); >> > bf = bf_next; >> > } >> > @@ -5849,7 +5850,7 @@ ath_tx_node_reassoc(struct ath_softc *sc >> > ":", >> > i); >> > /* >> > - * In case there's a followup call to this, only call it >> > + * In case there's a followup call to this, only call it >> > * if we don't have a cleanup in progress. >> > */ >> > if (! tid->cleanup_inprogress) { >> > >> _______________________________________________ >> svn-src-all@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/svn-src-all >> To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" > > -- > greg byshenk - gbyshenk@byshenk.net - Portland, OR USA From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 22 00:59:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8479DE4; Tue, 22 Apr 2014 00:59:57 +0000 (UTC) Received: from mail0.byshenk.net (portland1.byshenk.net [69.168.54.16]) by mx1.freebsd.org (Postfix) with ESMTP id 5B2631C24; Tue, 22 Apr 2014 00:59:57 +0000 (UTC) Received: by mail0.byshenk.net (Postfix, from userid 1002) id F012722CEF; Mon, 21 Apr 2014 17:59:50 -0700 (PDT) Date: Mon, 21 Apr 2014 17:59:50 -0700 From: Greg Byshenk To: Adrian Chadd Subject: Re: svn commit: r264710 - head/sys/dev/ath Message-ID: <20140422005950.GE1602@mail0.byshenk.net> References: <201404210205.s3L25p9U064240@svn.freebsd.org> <20140421155853.GD1602@mail0.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 00:59:57 -0000 On Mon, Apr 21, 2014 at 09:30:47AM -0700, Adrian Chadd wrote: > Which NIC? It is a TP-Link TL-WN951N "Wireless N PCI Adapter". dmesg: ath0: mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci4 ath0: AR5416 mac 13.10 RF2133 phy 8.1 pciconf: ath0@pci0:4:0:0: class=0x028000 card=0x3071168c chip=0x0023168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5008 Wireless Network Adapter' class = network On 9-STABLE, I see an occasional "stuck beacon" error, but all carries on more or less happily after. On 10-STABLE, the errors as mentioned. (It is 10-STABLE, revision 264683). -greg > On 21 April 2014 08:58, Greg Byshenk wrote: > > On Sun, Apr 20, 2014 at 07:09:33PM -0700, Adrian Chadd wrote: > >> I didn't say it in the commit message, but this should be MFCed to stable/10 . > > > > > > Adrian- > > > > I'm curious as to what this addresses. > > > > I attempted to move a router/access point to FreeBSD 10 over the > > weekend, and had to revert back to 9 as it was a terrible failure. > > > > It would invariably spew out masses of 'stuck beacon; resetting' > > errors, and then at some point (not obviuously correlated with > > those errors) lock up (hard, requiring a hard reset). > > > > If it is something that the patch might address, then I'll watch > > for an MFC to stable/10 > > > > Thanks, > > -greg > > > > > >> On 20 April 2014 19:05, Adrian Chadd wrote: > >> > Author: adrian > >> > Date: Mon Apr 21 02:05:51 2014 > >> > New Revision: 264710 > >> > URL: http://svnweb.freebsd.org/changeset/base/264710 > >> > > >> > Log: > >> > Make sure bf_next is NULL'ed out when we're completing up an aggregate > >> > frame through the cleanup path. > >> > > >> > Whilst here, fix the indenting for something I messed up. > >> > > >> > Tested: > >> > > >> > * AR5416, STA mode > >> > > >> > Modified: > >> > head/sys/dev/ath/if_ath_tx.c > >> > > >> > Modified: head/sys/dev/ath/if_ath_tx.c > >> > ============================================================================== > >> > --- head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:04:37 2014 (r264709) > >> > +++ head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:05:51 2014 (r264710) > >> > @@ -4600,10 +4600,11 @@ ath_tx_comp_cleanup_aggr(struct ath_soft > >> > > >> > ATH_TX_UNLOCK(sc); > >> > > >> > - /* Handle frame completion */ > >> > + /* Handle frame completion as individual frames */ > >> > bf = bf_first; > >> > while (bf) { > >> > bf_next = bf->bf_next; > >> > + bf->bf_next = NULL; > >> > ath_tx_default_comp(sc, bf, 1); > >> > bf = bf_next; > >> > } > >> > @@ -5849,7 +5850,7 @@ ath_tx_node_reassoc(struct ath_softc *sc > >> > ":", > >> > i); > >> > /* > >> > - * In case there's a followup call to this, only call it > >> > + * In case there's a followup call to this, only call it > >> > * if we don't have a cleanup in progress. > >> > */ > >> > if (! tid->cleanup_inprogress) { > >> > > >> _______________________________________________ > >> svn-src-all@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/svn-src-all > >> To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" > > > > -- > > greg byshenk - gbyshenk@byshenk.net - Portland, OR USA -- greg byshenk - gbyshenk@byshenk.net - Portland, OR USA From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 22 05:28:47 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F628BC; Tue, 22 Apr 2014 05:28:47 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5731149C; Tue, 22 Apr 2014 05:28:46 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3M5Skon047946; Tue, 22 Apr 2014 05:28:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3M5Sk0Q047945; Tue, 22 Apr 2014 05:28:46 GMT (envelope-from linimon) Date: Tue, 22 Apr 2014 05:28:46 GMT Message-Id: <201404220528.s3M5Sk0Q047945@freefall.freebsd.org> To: adrian@FreeBSD.org, linimon@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/169084: [ath] [suspend/resume] suspend/resume doesn't cause a rescan; the association stays even if the AP is not available X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 05:28:47 -0000 Old Synopsis: [ath] suspend/resume doesn't cause a rescan; the association stays even if the AP is not available New Synopsis: [ath] [suspend/resume] suspend/resume doesn't cause a rescan; the association stays even if the AP is not available State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Apr 22 05:27:54 UTC 2014 State-Changed-Why: should be fixed by commit from 2012. http://www.freebsd.org/cgi/query-pr.cgi?pr=169084 From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 22 18:04:56 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C84C82F1 for ; Tue, 22 Apr 2014 18:04:56 +0000 (UTC) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8547C1766 for ; Tue, 22 Apr 2014 18:04:56 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id e89so2045179qgf.34 for ; Tue, 22 Apr 2014 11:04:55 -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=gefJV5ZUPybsjId059bDHgZTiaJCvXghhC4yfqp88gY=; b=0rrF0SdlqgXBxkIT8jV4M+TYCxTqKVUWn7Tjqqx3vuqNZ0DGP6IL+BXo6WHzgekMpP Cmqq8X1xXtAOLNhYssK5XiHHAXyD5T17UcaTgaLwceNwH9roF0YLmQPu5LqA4k+eu0jO OvoaCblS3LD/HyvnG1+txcd+WAmdNYOpPqIMEi2uRuB0bglUPzOcsBrKtmFSpnrozk4i 9HZEFtmVigFn6at2IfVwhiimGuLlLhNgEum0kr+6LBXp+cyXhshijSvQIwIqw82NDmPL 3r/2AK+Nem+8RZP48uJ2fkh1zhgo8xs4ZIc63AxM3cFndH6dHRq3hsaxfD48DLgZWqPY x8iw== MIME-Version: 1.0 X-Received: by 10.224.38.138 with SMTP id b10mr13628596qae.98.1398189895611; Tue, 22 Apr 2014 11:04:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 22 Apr 2014 11:04:55 -0700 (PDT) In-Reply-To: <20140422005950.GE1602@mail0.byshenk.net> References: <201404210205.s3L25p9U064240@svn.freebsd.org> <20140421155853.GD1602@mail0.byshenk.net> <20140422005950.GE1602@mail0.byshenk.net> Date: Tue, 22 Apr 2014 11:04:55 -0700 X-Google-Sender-Auth: loof59ACE4uF0NNGJuRZB--TKRU Message-ID: Subject: Re: svn commit: r264710 - head/sys/dev/ath From: Adrian Chadd To: Greg Byshenk Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 18:04:56 -0000 Hi, Try setting it up without 11n enabled: ifconfig wlan0 create wlandev ath0 wlanmode hostap channel 6:g .. and if that doesn't help, try with 11n enabled but without ampdutx: ifconfig wlan0 -ampdutx I'm not using the AR5416 as an AP at the moment but it should be ok. I'm definitely using it as a station though. Can your try -HEAD instead? I don't plan on MFCing things myself back to stable/10; i rely on others who are actively using stable/10 to do it. -a On 21 April 2014 17:59, Greg Byshenk wrote: > On Mon, Apr 21, 2014 at 09:30:47AM -0700, Adrian Chadd wrote: > >> Which NIC? > > It is a TP-Link TL-WN951N "Wireless N PCI Adapter". > > dmesg: > ath0: mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci4 > ath0: AR5416 mac 13.10 RF2133 phy 8.1 > > pciconf: > ath0@pci0:4:0:0: class=0x028000 card=0x3071168c chip=0x0023168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5008 Wireless Network Adapter' > class = network > > On 9-STABLE, I see an occasional "stuck beacon" error, but all > carries on more or less happily after. On 10-STABLE, the errors > as mentioned. (It is 10-STABLE, revision 264683). > > -greg > > >> On 21 April 2014 08:58, Greg Byshenk wrote: >> > On Sun, Apr 20, 2014 at 07:09:33PM -0700, Adrian Chadd wrote: >> >> I didn't say it in the commit message, but this should be MFCed to stable/10 . >> > >> > >> > Adrian- >> > >> > I'm curious as to what this addresses. >> > >> > I attempted to move a router/access point to FreeBSD 10 over the >> > weekend, and had to revert back to 9 as it was a terrible failure. >> > >> > It would invariably spew out masses of 'stuck beacon; resetting' >> > errors, and then at some point (not obviuously correlated with >> > those errors) lock up (hard, requiring a hard reset). >> > >> > If it is something that the patch might address, then I'll watch >> > for an MFC to stable/10 >> > >> > Thanks, >> > -greg >> > >> > >> >> On 20 April 2014 19:05, Adrian Chadd wrote: >> >> > Author: adrian >> >> > Date: Mon Apr 21 02:05:51 2014 >> >> > New Revision: 264710 >> >> > URL: http://svnweb.freebsd.org/changeset/base/264710 >> >> > >> >> > Log: >> >> > Make sure bf_next is NULL'ed out when we're completing up an aggregate >> >> > frame through the cleanup path. >> >> > >> >> > Whilst here, fix the indenting for something I messed up. >> >> > >> >> > Tested: >> >> > >> >> > * AR5416, STA mode >> >> > >> >> > Modified: >> >> > head/sys/dev/ath/if_ath_tx.c >> >> > >> >> > Modified: head/sys/dev/ath/if_ath_tx.c >> >> > ============================================================================== >> >> > --- head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:04:37 2014 (r264709) >> >> > +++ head/sys/dev/ath/if_ath_tx.c Mon Apr 21 02:05:51 2014 (r264710) >> >> > @@ -4600,10 +4600,11 @@ ath_tx_comp_cleanup_aggr(struct ath_soft >> >> > >> >> > ATH_TX_UNLOCK(sc); >> >> > >> >> > - /* Handle frame completion */ >> >> > + /* Handle frame completion as individual frames */ >> >> > bf = bf_first; >> >> > while (bf) { >> >> > bf_next = bf->bf_next; >> >> > + bf->bf_next = NULL; >> >> > ath_tx_default_comp(sc, bf, 1); >> >> > bf = bf_next; >> >> > } >> >> > @@ -5849,7 +5850,7 @@ ath_tx_node_reassoc(struct ath_softc *sc >> >> > ":", >> >> > i); >> >> > /* >> >> > - * In case there's a followup call to this, only call it >> >> > + * In case there's a followup call to this, only call it >> >> > * if we don't have a cleanup in progress. >> >> > */ >> >> > if (! tid->cleanup_inprogress) { >> >> > >> >> _______________________________________________ >> >> svn-src-all@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/svn-src-all >> >> To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" >> > >> > -- >> > greg byshenk - gbyshenk@byshenk.net - Portland, OR USA > > -- > greg byshenk - gbyshenk@byshenk.net - Portland, OR USA From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 22 18:21:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2488CCC; Tue, 22 Apr 2014 18:21:08 +0000 (UTC) Received: from mail0.byshenk.net (portland1.byshenk.net [69.168.54.16]) by mx1.freebsd.org (Postfix) with ESMTP id 88DA4191C; Tue, 22 Apr 2014 18:21:08 +0000 (UTC) Received: by mail0.byshenk.net (Postfix, from userid 1002) id 11B4622C07; Tue, 22 Apr 2014 11:21:08 -0700 (PDT) Date: Tue, 22 Apr 2014 11:21:07 -0700 From: Greg Byshenk To: Adrian Chadd Subject: Re: svn commit: r264710 - head/sys/dev/ath Message-ID: <20140422182107.GF1602@mail0.byshenk.net> References: <201404210205.s3L25p9U064240@svn.freebsd.org> <20140421155853.GD1602@mail0.byshenk.net> <20140422005950.GE1602@mail0.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 18:21:08 -0000 On Tue, Apr 22, 2014 at 11:04:55AM -0700, Adrian Chadd wrote: > Try setting it up without 11n enabled: > > ifconfig wlan0 create wlandev ath0 wlanmode hostap channel 6:g > > .. and if that doesn't help, try with 11n enabled but without ampdutx: > > ifconfig wlan0 -ampdutx > > I'm not using the AR5416 as an AP at the moment but it should be ok. > I'm definitely using it as a station though. > > Can your try -HEAD instead? I don't plan on MFCing things myself back > to stable/10; i rely on others who are actively using stable/10 to do > it. I did try it to 11g (as I know that 11n wasn't supported before), but it didn't help. I did -not- try without ampdutx. I can try that, and I can also try HEAD --- but that will take a little bit of time, as I will need to do some reconfiguring of other things to ensure that my systems are up and available while I'm testing. I'll let you know when I have a chance to test. -greg > On 21 April 2014 17:59, Greg Byshenk wrote: > > On Mon, Apr 21, 2014 at 09:30:47AM -0700, Adrian Chadd wrote: > > > >> Which NIC? > > > > It is a TP-Link TL-WN951N "Wireless N PCI Adapter". > > > > dmesg: > > ath0: mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci4 > > ath0: AR5416 mac 13.10 RF2133 phy 8.1 > > > > pciconf: > > ath0@pci0:4:0:0: class=0x028000 card=0x3071168c chip=0x0023168c rev=0x01 hdr=0x00 > > vendor = 'Atheros Communications Inc.' > > device = 'AR5008 Wireless Network Adapter' > > class = network > > > > On 9-STABLE, I see an occasional "stuck beacon" error, but all > > carries on more or less happily after. On 10-STABLE, the errors > > as mentioned. (It is 10-STABLE, revision 264683). > > -- greg byshenk - gbyshenk@byshenk.net - Portland, OR USA From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 13:48:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9898FD39 for ; Wed, 23 Apr 2014 13:48:55 +0000 (UTC) Received: from nm12-vm0.bullet.mail.bf1.yahoo.com (nm12-vm0.bullet.mail.bf1.yahoo.com [98.139.213.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 527A51888 for ; Wed, 23 Apr 2014 13:48:55 +0000 (UTC) Received: from [98.139.215.141] by nm12.bullet.mail.bf1.yahoo.com with NNFMP; 23 Apr 2014 13:46:35 -0000 Received: from [98.139.213.11] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 23 Apr 2014 13:46:35 -0000 Received: from [127.0.0.1] by smtp111.mail.bf1.yahoo.com with NNFMP; 23 Apr 2014 13:46:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1398260795; bh=+uKsFkKekHruoKm9whos4g2fkX6uL6FoOPT96ohm0kM=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=ECZjg7zzzK/Eg8NZnTDS2DS+oNZWxMZ4orFNwJat0r1OjVNcjAC07SH+2MCTk202GCxysjlSxVN5SsPC1EuoVJBSMvm6Lkog93o8wOjEEYM3hGBums6ZRrM2yU08vaoIXuZIx90H5pded5/5R0TADsqK5NC4dfDZdWzkUIkD5z0= X-Yahoo-Newman-Id: 60107.17626.bm@smtp111.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: qoVUKMsVM1kWMXjTWTbm43gkDdm6PKrMm8IjQx12TkIFm_Q RDRcag67IMPCOwDxTxkCgktbwNtpyUx6vw.73L2MpyfsJP_P1EZspzEQTU.4 rEJfxt1j2rqvyXwAg9f_AgQ8dnmxrzXz2gzjO5Xit50ANcson5SW2fJSPOYH KwGiPR7TN9jT2Wd5wnHaKjOYViI9xmKQdkc11nyn20bZKf35Dohq8V6VBTtf be5TKpRC.MkqD3K8D79UZel2UwsCQMVdBkfcxy39Ec3pmWPwUNT8p5jhLeKh 0K0Y.053mXjIlHxB.lOt94H26H7nCD7S6uhLWhKdZe2XTeA5lUZrGIBgwE1W SBmraEVg0jZKPemvQ2sv78cEEZ_Fh.D0Q63b64u238GGOlCTjUYbaFdmrjvd W0UgWrmSBfhglr417zvb2IX5OMwz7olIA9k.wesFDTS6umrJ02VV8_gesxC4 r7sS2y..kBQ8Qj8VBOJdtAgALTsaRSh91_yVzAmZCa7kUd.xsPo1rdZ3QjPw Tjic23QEpQ8vVFD_7QxktDC2zL9QA0UZCOnvBu4a2BEItxrHGBaUcuG5wdZU cjnM5VqDawZ1HGtodEr0zd.hQkb0n.bXtpHGLowOVFQnK9bZ_JC2rjF3qqGz nA97WMFHUrf3dn4qgNoReXHtwvqVQIijzqmc7U_k- X-Yahoo-SMTP: 9sPoSQ2swBBlERuQ.0vs8XLc_MeClW0- X-Rocket-Received: from [10.0.1.147] (Scoobi_doo@70.90.74.161 with plain [98.138.105.21]) by smtp111.mail.bf1.yahoo.com with SMTP; 23 Apr 2014 06:46:35 -0700 PDT Message-ID: <5357C439.4040101@yahoo.com> Date: Wed, 23 Apr 2014 09:46:33 -0400 From: Anthony Jenkins User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: urtwn panic Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 13:48:55 -0000 Hi all, Tried to send this a couple days ago, but for some reason none of my emails post to the @freebsd.org mailing lists. Thinking it's my @yahoo.com return address. If this doesn't post, I'll try the @gmail.com one. I'm getting a panic with the latest kernel (r264719) and the if_urtwn driver. It happens ~75% of the time I plug the device into a USB port, and appears to occur when the driver holds a non-sleepable mutex while calling a USB firmware loading function which goes to sleep. I have a coredump available to triage. Here's the device details (from Linux, since I can't reliably plug the thing into FreeBSD): dmesg: [330849.645998] usb 1-5: Product: 802.11n WLAN Adapter [330849.646002] usb 1-5: Manufacturer: Realtek [330849.646006] usb 1-5: SerialNumber: 00e04c000001 [330849.703666] cfg80211: Calling CRDA to update world regulatory domain [330849.715428] cfg80211: World regulatory domain updated: [330849.715434] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [330849.715437] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [330849.715439] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [330849.715441] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [330849.715443] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [330849.715445] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [330849.731410] rtl8192cu: Chip version 0x10 [330849.809018] rtl8192cu: MAC address: 00:0b:81:81:54:69 [330849.809023] rtl8192cu: Board Type 0 [330849.809266] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [330849.809317] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [330849.809506] usbcore: registered new interface driver rtl8192cu [330849.818471] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [330849.819740] rtlwifi: wireless switch is on [330849.859663] rtl8192cu: MAC auto ON okay! [330849.895265] rtl8192cu: Tx queue select: 0x05 [330850.256751] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [330850.258132] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready ajenkins@kubuntu-ajenkins:~$ sudo lsusb -v -s 001:003 Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x8176 RTL8188CUS 802.11n WLAN Adapter bcdDevice 2.00 iManufacturer 1 Realtek iProduct 2 802.11n WLAN Adapter iSerial 3 00e04c000001 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered) Here's the FreeBSD coredump: [root@ajenkins-hplaptop /usr/src]# kgdb /usr/obj/usr/src/sys/MYKERNEL/kernel.debug /var/crash/vmcore.last 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: Sleeping on "fwload" with the following non-sleepable locks held: exclusive sleep mutex urtwn0 (network driver) r = 0 (0xfffffe00175fe348) locked @ /usr/src/sys/dev/usb/usb_request.c:722 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0447e095e0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0447e09690 witness_warn() at witness_warn+0x4b5/frame 0xfffffe0447e09750 _sleep() at _sleep+0x70/frame 0xfffffe0447e097f0 firmware_get() at firmware_get+0x13a/frame 0xfffffe0447e09850 urtwn_init_locked() at urtwn_init_locked+0x18cd/frame 0xfffffe0447e09910 urtwn_ioctl() at urtwn_ioctl+0x12a/frame 0xfffffe0447e09960 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfffffe0447e099c0 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfffffe0447e099f0 fork_exit() at fork_exit+0x84/frame 0xfffffe0447e09a30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0447e09a30 --- trap 0, rip = 0, rsp = 0xfffffe0447e09af0, rbp = 0 --- Sleeping thread (tid 100892, pid 0) owns a non-sleepable lock KDB: stack backtrace of thread 100892: sched_switch() at sched_switch+0x47f/frame 0xfffffe0447e096a0 mi_switch() at mi_switch+0x179/frame 0xfffffe0447e096e0 sleepq_switch() at sleepq_switch+0x152/frame 0xfffffe0447e09720 sleepq_wait() at sleepq_wait+0x43/frame 0xfffffe0447e09750 _sleep() at _sleep+0x366/frame 0xfffffe0447e097f0 firmware_get() at firmware_get+0x13a/frame 0xfffffe0447e09850 urtwn_init_locked() at urtwn_init_locked+0x18cd/frame 0xfffffe0447e09910 urtwn_ioctl() at urtwn_ioctl+0x12a/frame 0xfffffe0447e09960 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfffffe0447e099c0 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfffffe0447e099f0 fork_exit() at fork_exit+0x84/frame 0xfffffe0447e09a30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0447e09a30 --- trap 0, rip = 0, rsp = 0xfffffe0447e09af0, rbp = 0 --- panic: sleeping thread cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0447e814b0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0447e81560 vpanic() at vpanic+0x124/frame 0xfffffe0447e815a0 panic() at panic+0x43/frame 0xfffffe0447e81600 propagate_priority() at propagate_priority+0x2fd/frame 0xfffffe0447e81640 turnstile_wait() at turnstile_wait+0x34f/frame 0xfffffe0447e81690 __mtx_lock_sleep() at __mtx_lock_sleep+0x1b6/frame 0xfffffe0447e81710 __mtx_lock_flags() at __mtx_lock_flags+0x102/frame 0xfffffe0447e81760 urtwn_ioctl() at urtwn_ioctl+0x41/frame 0xfffffe0447e817b0 ifioctl() at ifioctl+0x8f5/frame 0xfffffe0447e81870 kern_ioctl() at kern_ioctl+0x22b/frame 0xfffffe0447e818d0 sys_ioctl() at sys_ioctl+0x13c/frame 0xfffffe0447e81920 amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe0447e81a30 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0447e81a30 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x800fa342a, rsp = 0x7fffffffdc88, rbp = 0x7fffffffe500 --- KDB: enter: panic Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols ... #0 doadump (textdump=0) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump (textdump=0) at pcpu.h:219 #1 0xffffffff802fb8ae in db_dump (dummy=, dummy2=0, dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:543 #2 0xffffffff802fb34d in db_command (cmd_table=0x0) at /usr/src/sys/ddb/db_command.c:449 #3 0xffffffff802fb0c4 in db_command_loop () at /usr/src/sys/ddb/db_command.c:502 #4 0xffffffff802fda90 in db_trap (type=, code=0) at /usr/src/sys/ddb/db_main.c:231 #5 0xffffffff80628289 in kdb_trap (type=3, code=0, tf=) at /usr/src/sys/kern/subr_kdb.c:656 #6 0xffffffff808ad8ae in trap (frame=0xfffffe0447e81490) at /usr/src/sys/amd64/amd64/trap.c:573 #7 0xffffffff80892262 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff806279ee in kdb_enter (why=0xffffffff809d5a90 "panic", msg=) at cpufunc.h:63 #9 0xffffffff805f0594 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:749 #10 0xffffffff805f0603 in panic (fmt=0xffffffff80d41e50 "\004") at /usr/src/sys/kern/kern_shutdown.c:685 #11 0xffffffff8063ab6d in propagate_priority (td=) at /usr/src/sys/kern/subr_turnstile.c:226 ---Type to continue, or q to quit--- #12 0xffffffff8063b43f in turnstile_wait (ts=0xfffff801253a56c0, owner=, queue=0) at /usr/src/sys/kern/subr_turnstile.c:742 #13 0xffffffff805dbb76 in __mtx_lock_sleep (c=0xfffffe00175fe360, tid=18446735283083894784, opts=, file=, line=) at /usr/src/sys/kern/kern_mutex.c:508 #14 0xffffffff805db912 in __mtx_lock_flags (c=, opts=0, file=0xffffffff81ab33e8 "/usr/src/sys/modules/usb/urtwn/../../../dev/usb/wlan/if_urtwn.c", line=1787) at /usr/src/sys/kern/kern_mutex.c:223 #15 0xffffffff81aa9b51 in urtwn_ioctl (ifp=0xfffff80125a3e800, cmd=3223349575, data=0xfffff80011577780 "urtwn0") at /usr/src/sys/modules/usb/urtwn/../../../dev/usb/wlan/if_urtwn.c:1787 #16 0xffffffff806bad65 in ifioctl (so=0xfffff80192990828, cmd=3223349575, data=0xfffff80011577780 "urtwn0", td=0xfffff80145e16000) at /usr/src/sys/net/if.c:2465 #17 0xffffffff80648c5b in kern_ioctl (td=, fd=, com=) at file.h:323 #18 0xffffffff806489dc in sys_ioctl (td=0xfffff80145e16000, uap=0xfffffe0447e819c0) at /usr/src/sys/kern/sys_generic.c:702 #19 0xffffffff808ae78a in amd64_syscall (td=0xfffff80145e16000, traced=0) at subr_syscall.c:133 #20 0xffffffff8089254b in Xfast_syscall () ---Type to continue, or q to quit--- at /usr/src/sys/amd64/amd64/exception.S:390 #21 0x0000000800fa342a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) Thanks in advance, Anthony Jenkins From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 20:39:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8296C8A7 for ; Wed, 23 Apr 2014 20:39:00 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11C191515 for ; Wed, 23 Apr 2014 20:38:59 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBFFA4.dip0.t-ipconnect.de [93.203.255.164]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id s3NKcYTs079298; Wed, 23 Apr 2014 20:38:35 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 s3NKchsD064116; Wed, 23 Apr 2014 22:38:43 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id s3NKcP2X054576; Wed, 23 Apr 2014 22:38:37 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201404232038.s3NKcP2X054576@fire.js.berklix.net> To: Anthony Jenkins Subject: Re: urtwn panic From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 23 Apr 2014 09:46:33 -0400." <5357C439.4040101@yahoo.com> Date: Wed, 23 Apr 2014 22:38:25 +0200 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 20:39:00 -0000 Anthony Jenkins wrote: > I'm getting a panic with the latest kernel (r264719) and the if_urtwn driver. Might the urtwn device overheat, not return & cause a panic ? My urtwn device is very small, no thermal path to dump heat. I've not tried on current, but on 10.0-RELEASE I saw my urtwn0 interface disappearing; I read parts of the driver; & noticed there's mention of a temperature level, I didn't tweak it, but hung my device on a USB extension cable at 10 C outside the window, & later in front of a chassis input fan at ~ 20 C room temp., I think both locations lasted longer or perhaps indefinately without urtwn0 , can't remember, I suspended pursuing it. Device picture for those who don't know how small this, & other URLs via: http://www.berklix.com/~jhs/hardware/urtwn/ 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 "> ". Google breach privacy http://berklix.com/jhs/adverts/ From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 22:04:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 206B2E3E; Wed, 23 Apr 2014 22:04:49 +0000 (UTC) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C86CE1D35; Wed, 23 Apr 2014 22:04:48 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id gq1so1742767obb.5 for ; Wed, 23 Apr 2014 15:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xP+CUh8OmDeMUZsBWxl/2Q1eilBwL/eCZCXN0mVk/pA=; b=nAGgO94xwWqGuClF9R0KyBDuXNlGfEMIpZeFBPbMXfnfXfK2A537zny4ifTN1D1dQ/ dd11QVbs6r4v/ziOU28ZG32fRN88/3csINCU0lKi1xDUi4xKd85f8ihmieCJb9OgqdDV /RE+KTmsn64qh0bL6dLXfyuDtFPeBSFgvGqa/8JYQhGEzAPvDJTOfMOkX9wFkje8lXLs c2DOwvuE4hOh1XjZUXgXvXPe0o/H8exmikMLWAvEhWmqnUV9kV9BmNC4jPBDTpz/sLJt wUkN064Eio8jXUbzYg+xMIKBPrjlNXbOrNZMDPxc3hKY6z3gzQegIT8NUJCj5RPc65LD mmlQ== MIME-Version: 1.0 X-Received: by 10.60.50.197 with SMTP id e5mr40428965oeo.39.1398290688111; Wed, 23 Apr 2014 15:04:48 -0700 (PDT) Received: by 10.76.87.73 with HTTP; Wed, 23 Apr 2014 15:04:48 -0700 (PDT) In-Reply-To: <4F861C10.5020503@gmail.com> References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> <4F8604C1.4090902@gmail.com> <4F861C10.5020503@gmail.com> Date: Wed, 23 Apr 2014 23:04:48 +0100 Message-ID: Subject: Re: ath(4) fails to attach From: "Sevan / Venture37" 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.17 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 Apr 2014 22:04:49 -0000 On 12 April 2012 01:04, Sevan / Venture37 wrote: > On 11/04/2012 23:34, Adrian Chadd wrote: >> >> So it attaches fine with debugging enabled, but not with debugging >> disabled? > > > Nope, neither. Just over 2 years on Tried the ath(4) card again on a new snapshot freshly installed on my X61s unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 cbb0: Opening memory: cbb0: Normal: 0xd4000000-0xd400ffff cardbus0: Expecting link target, got 0xff cbb0: Opening memory: pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of pci0:6:0:0 unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 cbb0: Opening memory: cbb0: Normal: 0xd4000000-0xd400ffff cardbus0: Expecting link target, got 0xff cbb0: Opening memory: found-> vendor=0x168c, dev=0x0013, revid=0x01 domain=0, bus=6, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0002, statreg=0x8210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 ath0: irq 16 at device 0.0 on cardbus0 pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of ath0 ath0: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 cbb0: Opening memory: cbb0: Normal: 0xd4000000-0xd400ffff ath0: unable to attach hardware; HAL status 14 cbb0: Opening memory: device_attach: ath0 attach returned 6 Verbose dmesg: Table 'FACP' at 0xbf6bd300 Table 'SSDT' at 0xbf6bd4b4 Table 'ECDT' at 0xbf6cba38 Table 'TCPA' at 0xbf6cba8a Table 'APIC' at 0xbf6cbabc APIC: Found table at 0xbf6cbabc APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 1: enabled SMP: Added CPU 1 (AP) Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #0 r264459: Mon Apr 14 18:10:10 UTC 2014 root@grind.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4 (tags/RELEASE_34/final 197956) 20140216 WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81e99000. Preloaded elf obj module "/boot/kernel/zfs.ko" at 0xffffffff81e99d90. Preloaded elf obj module "/boot/kernel/opensolaris.ko" at 0xffffffff81e9a5b8. Calibrating TSC clock ... TSC clock: 1596037768 Hz CPU: Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz (1596.04-MHz K8-class CPU) Origin="GenuineIntel" Id=0x6fb Family=0x6 Model=0xf Stepping=11 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) Physical memory chunk(s): 0x0000000000010000 - 0x0000000000099fff, 565248 bytes (138 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x0000000001eca000 - 0x00000000bf6affff, 3179175936 bytes (776166 pages) 0x0000000100000000 - 0x000000022d671fff, 5056700416 bytes (1234546 pages) avail memory = 8183607296 (7804 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 x86bios: IVT 0x000000-0x0004ff at 0xfffff80000000000 x86bios: SSEG 0x098000-0x098fff at 0xfffffe01eb3ea000 x86bios: EBDA 0x09d000-0x09ffff at 0xfffff8000009d000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffff800000a0000 ULE: setup cpu 0 ULE: setup cpu 1 ACPI: RSDP 0xf6950 00024 (v02 LENOVO) ACPI: XSDT 0xbf6bd1b7 0009C (v01 LENOVO TP-7V 00002220 LTP 00000000) ACPI: FACP 0xbf6bd300 000F4 (v03 LENOVO TP-7V 00002220 LNVO 00000001) ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 0/32 (20130823/tbfadt-601) ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has zero address or length: 0x000000000000102C/0x0 (20130823/tbfadt-630) ACPI: DSDT 0xbf6bd6db 0E35D (v01 LENOVO TP-7V 00002220 MSFT 03000000) ACPI: FACS 0xbf6e4000 00040 ACPI: SSDT 0xbf6bd4b4 00227 (v01 LENOVO TP-7V 00002220 MSFT 03000000) ACPI: ECDT 0xbf6cba38 00052 (v01 LENOVO TP-7V 00002220 LNVO 00000001) ACPI: TCPA 0xbf6cba8a 00032 (v02 LENOVO TP-7V 00002220 LNVO 00000001) ACPI: APIC 0xbf6cbabc 00068 (v01 LENOVO TP-7V 00002220 LNVO 00000001) ACPI: MCFG 0xbf6cbb24 0003C (v01 LENOVO TP-7V 00002220 LNVO 00000001) ACPI: HPET 0xbf6cbb60 00038 (v01 LENOVO TP-7V 00002220 LNVO 00000001) ACPI: SLIC 0xbf6cbb98 00176 (v01 LENOVO TP-7V 00002220 SLIC 00000000) ACPI: SLAC 0xbf6cbdf0 00176 (v01 LENOVO TP-7V 00002220 LTP 00000000) ACPI: BOOT 0xbf6cbf66 00028 (v01 LENOVO TP-7V 00002220 LTP 00000001) ACPI: ASF! 0xbf6cbf8e 00072 (v16 LENOVO TP-7V 00002220 PTL 00000001) ACPI: SSDT 0xbf6e2697 0025F (v01 LENOVO TP-7V 00002220 INTL 20050513) ACPI: SSDT 0xbf6e28f6 000A6 (v01 LENOVO TP-7V 00002220 INTL 20050513) ACPI: SSDT 0xbf6e299c 004F7 (v01 LENOVO TP-7V 00002220 INTL 20050513) ACPI: SSDT 0xbf6e2e93 001D8 (v01 LENOVO TP-7V 00002220 INTL 20050513) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic1: Routing NMI -> LINT1 lapic1: LINT1 trigger: edge lapic1: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 wlan: <802.11 Link Layer> Hardware, Intel IvyBridge+ RNG: RDRAND is not present Hardware, VIA Nehemiah Padlock RNG: VIA Padlock RNG not present nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: VESA: INT 0x10 vector 0xc000:0x0014 VESA: information block 0000 56 45 53 41 00 03 00 01 00 99 01 00 00 00 40 00 0010 00 99 77 00 00 01 3d 01 00 99 4f 01 00 99 7d 01 0020 00 99 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040 60 01 61 01 62 01 63 01 64 01 65 01 66 01 67 01 0050 68 01 69 01 6a 01 6b 01 6c 01 6d 01 6e 01 6f 01 0060 70 01 71 01 3c 01 4d 01 5c 01 3a 01 4b 01 5a 01 0070 07 01 1a 01 1b 01 05 01 17 01 18 01 12 01 14 01 0080 15 01 01 01 03 01 11 01 ff ff 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 49 6e 74 65 6c 28 72 29 47 4d 39 36 35 2f 50 4d 0110 39 36 35 2f 47 4c 39 36 30 20 47 72 61 70 68 69 0120 63 73 20 43 68 69 70 20 41 63 63 65 6c 65 72 61 0130 74 65 64 20 56 47 41 20 42 49 4f 53 00 49 6e 74 0140 65 6c 20 43 6f 72 70 6f 72 61 74 69 6f 6e 00 49 0150 6e 74 65 6c 28 72 29 47 4d 39 36 35 2f 50 4d 39 0160 36 35 2f 47 4c 39 36 30 20 47 72 61 70 68 69 63 0170 73 20 43 6f 6e 74 72 6f 6c 6c 65 72 00 48 61 72 0180 64 77 61 72 65 20 56 65 72 73 69 6f 6e 20 30 2e 0190 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 12 mode(s) found VESA: v3.0, 7616k memory, flags:0x1, mode table:0xfffffe01eb3ff040 (99000040) VESA: Intel(r)GM965/PM965/GL960 Graphics Chip Accelerated VGA BIOS VESA: Intel Corporation Intel(r)GM965/PM965/GL960 Graphics Controller Hardware Version 0.0 io: VMBUS: load null: Falling back to random adaptor random: initialized hptnr: R750/DC7280 controller driver v1.0 hpt27xx: RocketRAID 27xx controller driver v1.1 hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 acpi0: on motherboard ACPI: All ACPI Tables successfully acquired PCIe: Memory Mapped configuration base @ 0xf0000000 CPU0: local APIC error 0x40 ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bff00000 (3) failed cpu0: Processor \134_PR_.CPU0 (ACPI ID 0) -> APIC ID 0 cpu0: on acpi0 ACPI: SSDT 0xbf6e1b32 00282 (v01 PmRef Cpu0Ist 00000100 INTL 20050513) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0 00282 (v01 PmRef Cpu0Ist 00000100 INTL 20050513) ACPI: SSDT 0xbf6e1e39 0085E (v01 PmRef Cpu0Cst 00000100 INTL 20050513) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0 0085E (v01 PmRef Cpu0Cst 00000100 INTL 20050513) cpu1: Processor \134_PR_.CPU1 (ACPI ID 1) -> APIC ID 1 cpu1: on acpi0 ACPI: SSDT 0xbf6e1a6a 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513) ACPI: SSDT 0xbf6e1db4 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513) ACPI: Dynamic OEM Table Load: ACPI: SSDT 0 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513) attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 hpet0: vendor 0x8086, rev 0x1, 14318180Hz 64bit, 3 timers, legacy route hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic hpet0: t1: irqs 0x00f00000 (0) hpet0: t2: irqs 0x00f00800 (0) Timecounter "HPET" frequency 14318180 Hz quality 950 ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 0 vector 50 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 atrtc0: port 0x70-0x71 irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 51 Event timer "RTC" frequency 32768 Hz quality 0 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 9 10 11 Validation 0 10 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 Validation 0 11 N 0 3 4 5 6 7 9 10 11 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pcib0: decoding 5 range 0-0xff pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xd0000-0xd3fff pcib0: decoding 3 range 0xd4000-0xd7fff pcib0: decoding 3 range 0xd8000-0xdbfff pcib0: decoding 3 range 0xdc000-0xdffff pcib0: decoding 3 range 0xc0000000-0xfebfffff pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x2a00, revid=0x0c domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2a02, revid=0x0c domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message map[10]: type Memory, range 64, base 0xf8000000, size 20, enabled pcib0: allocated type 3 (0xf8000000-0xf80fffff) for rid 10 of pci0:0:2:0 map[18]: type Prefetchable Memory, range 64, base 0xe0000000, size 28, enabled pcib0: allocated type 3 (0xe0000000-0xefffffff) for rid 18 of pci0:0:2:0 map[20]: type I/O Port, range 32, base 0x1800, size 3, enabled pcib0: allocated type 4 (0x1800-0x1807) for rid 20 of pci0:0:2:0 pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x2a03, revid=0x0c domain=0, bus=0, slot=2, func=1 class=03-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 map[10]: type Memory, range 64, base 0xf8100000, size 20, enabled pcib0: allocated type 3 (0xf8100000-0xf81fffff) for rid 10 of pci0:0:2:1 found-> vendor=0x8086, dev=0x1049, revid=0x03 domain=0, bus=0, slot=25, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 32, base 0xf8200000, size 17, enabled pcib0: allocated type 3 (0xf8200000-0xf821ffff) for rid 10 of pci0:0:25:0 map[14]: type Memory, range 32, base 0xf8225000, size 12, enabled pcib0: allocated type 3 (0xf8225000-0xf8225fff) for rid 14 of pci0:0:25:0 map[18]: type I/O Port, range 32, base 0x1840, size 5, enabled pcib0: allocated type 4 (0x1840-0x185f) for rid 18 of pci0:0:25:0 pcib0: matched entry for 0.25.INTA pcib0: slot 25 INTA hardwired to IRQ 20 found-> vendor=0x8086, dev=0x2834, revid=0x03 domain=0, bus=0, slot=26, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type I/O Port, range 32, base 0x1860, size 5, enabled pcib0: allocated type 4 (0x1860-0x187f) for rid 20 of pci0:0:26:0 pcib0: matched entry for 0.26.INTA pcib0: slot 26 INTA hardwired to IRQ 20 found-> vendor=0x8086, dev=0x2835, revid=0x03 domain=0, bus=0, slot=26, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[20]: type I/O Port, range 32, base 0x1880, size 5, enabled pcib0: allocated type 4 (0x1880-0x189f) for rid 20 of pci0:0:26:1 pcib0: matched entry for 0.26.INTB pcib0: slot 26 INTB hardwired to IRQ 21 found-> vendor=0x8086, dev=0x283a, revid=0x03 domain=0, bus=0, slot=26, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf8426c00, size 10, enabled pcib0: allocated type 3 (0xf8426c00-0xf8426fff) for rid 10 of pci0:0:26:7 pcib0: matched entry for 0.26.INTC pcib0: slot 26 INTC hardwired to IRQ 22 found-> vendor=0x8086, dev=0x284b, revid=0x03 domain=0, bus=0, slot=27, func=0 class=04-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xf8220000, size 14, enabled pcib0: allocated type 3 (0xf8220000-0xf8223fff) for rid 10 of pci0:0:27:0 pcib0: matched entry for 0.27.INTB pcib0: slot 27 INTB hardwired to IRQ 17 found-> vendor=0x8086, dev=0x283f, revid=0x03 domain=0, bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 20 secbus=2, subbus=2 found-> vendor=0x8086, dev=0x2841, revid=0x03 domain=0, bus=0, slot=28, func=1 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTB pcib0: slot 28 INTB hardwired to IRQ 21 secbus=3, subbus=3 found-> vendor=0x8086, dev=0x2830, revid=0x03 domain=0, bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 map[20]: type I/O Port, range 32, base 0x18a0, size 5, enabled pcib0: allocated type 4 (0x18a0-0x18bf) for rid 20 of pci0:0:29:0 pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x2831, revid=0x03 domain=0, bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[20]: type I/O Port, range 32, base 0x18c0, size 5, enabled pcib0: allocated type 4 (0x18c0-0x18df) for rid 20 of pci0:0:29:1 pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 17 found-> vendor=0x8086, dev=0x2836, revid=0x03 domain=0, bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf8427000, size 10, enabled pcib0: allocated type 3 (0xf8427000-0xf84273ff) for rid 10 of pci0:0:29:7 pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 19 found-> vendor=0x8086, dev=0x2448, revid=0xf3 domain=0, bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0005, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) secbus=5, subbus=8 found-> vendor=0x8086, dev=0x2811, revid=0x03 domain=0, bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2850, revid=0x03 domain=0, bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0288, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=255 pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:31:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:31:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:31:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:31:1 map[20]: type I/O Port, range 32, base 0x18e0, size 4, enabled pcib0: allocated type 4 (0x18e0-0x18ef) for rid 20 of pci0:0:31:1 found-> vendor=0x8086, dev=0x2829, revid=0x03 domain=0, bus=0, slot=31, func=2 class=01-06-01, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 4 messages map[10]: type I/O Port, range 32, base 0x1c30, size 3, enabled pcib0: allocated type 4 (0x1c30-0x1c37) for rid 10 of pci0:0:31:2 map[14]: type I/O Port, range 32, base 0x1c24, size 2, enabled pcib0: allocated type 4 (0x1c24-0x1c27) for rid 14 of pci0:0:31:2 map[18]: type I/O Port, range 32, base 0x1c28, size 3, enabled pcib0: allocated type 4 (0x1c28-0x1c2f) for rid 18 of pci0:0:31:2 map[1c]: type I/O Port, range 32, base 0x1c20, size 2, enabled pcib0: allocated type 4 (0x1c20-0x1c23) for rid 1c of pci0:0:31:2 map[20]: type I/O Port, range 32, base 0x1c00, size 5, enabled pcib0: allocated type 4 (0x1c00-0x1c1f) for rid 20 of pci0:0:31:2 map[24]: type Memory, range 32, base 0xf8426000, size 11, enabled pcib0: allocated type 3 (0xf8426000-0xf84267ff) for rid 24 of pci0:0:31:2 pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 16 found-> vendor=0x8086, dev=0x283e, revid=0x03 domain=0, bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0103, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type Memory, range 32, base 0xf8427400, size 8, enabled pcib0: allocated type 3 (0xf8427400-0xf84274ff) for rid 10 of pci0:0:31:3 map[20]: type I/O Port, range 32, base 0x1c40, size 5, enabled pcib0: allocated type 4 (0x1c40-0x1c5f) for rid 20 of pci0:0:31:3 pcib0: matched entry for 0.31.INTA pcib0: slot 31 INTA hardwired to IRQ 23 vgapci0: port 0x1800-0x1807 mem 0xf8000000-0xf80fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 pcib0: allocated type 3 (0xc0000000-0xc0000fff) for rid 64 of agp0 agp0: Allocated flush page phys 0xc0000000 virt 0xfffff800c0000000 agp0: aperture size is 256M, detected 7676k stolen memory agp0: AGP_I965_PGTBL_CTL2: 00000000 agp0: AGP_I855_GCC1: 0x30 agp0: AGP_I965_MSAC: 0x00 agp0: Mappable GTT entries: 65536 agp0: Total GTT entries: 131072 vgapci0: Boot video device vgapci1: mem 0xf8100000-0xf81fffff at device 2.1 on pci0 em0: port 0x1840-0x185f mem 0xf8200000-0xf821ffff,0xf8225000-0xf8225fff irq 20 at device 25.0 on pci0 em0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to local APIC 0 vector 52 em0: using IRQ 256 for MSI em0: Using an MSI interrupt em0: bpf attached em0: Ethernet address: 00:1d:72: uhci0: port 0x1860-0x187f irq 20 at device 26.0 on pci0 usbus0 on uhci0 uhci0: usbpf: Attached uhci1: port 0x1880-0x189f irq 21 at device 26.1 on pci0 ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 53 usbus1 on uhci1 uhci1: usbpf: Attached ehci0: mem 0xf8426c00-0xf8426fff irq 22 at device 26.7 on pci0 ioapic0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 54 usbus2: EHCI version 1.0 usbus2 on ehci0 ehci0: usbpf: Attached hdac0: mem 0xf8220000-0xf8223fff irq 17 at device 27.0 on pci0 hdac0: PCI card vendor: 0x17aa, device: 0x20ac hdac0: HDA Driver Revision: 20120126_0002 hdac0: Config options: on=0x00000000 off=0x00000000 hdac0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 257 to local APIC 0 vector 55 hdac0: using IRQ 257 for MSI hdac0: Caps: OSS 4, ISS 4, BSS 0, NSDO 1, 64bit, CORB 256, RIRB 256 pcib1: irq 20 at device 28.0 on pci0 pcib1: allocating non-ISA range 0x2000-0x20ff pcib0: allocated type 4 (0x2000-0x20ff) for rid 1c of pcib1 pcib1: allocating non-ISA range 0x2400-0x24ff pcib0: allocated type 4 (0x2400-0x24ff) for rid 1c of pcib1 pcib1: allocating non-ISA range 0x2800-0x28ff pcib0: allocated type 4 (0x2800-0x28ff) for rid 1c of pcib1 pcib1: allocating non-ISA range 0x2c00-0x2cff pcib0: allocated type 4 (0x2c00-0x2cff) for rid 1c of pcib1 pcib0: allocated type 3 (0xf4000000-0xf5ffffff) for rid 20 of pcib1 pcib0: allocated type 3 (0xf8500000-0xf85fffff) for rid 24 of pcib1 pcib1: domain 0 pcib1: secondary bus 2 pcib1: subordinate bus 2 pcib1: I/O decode 0x2000-0x2fff pcib1: memory decode 0xf4000000-0xf5ffffff pcib1: prefetched decode 0xf8500000-0xf85fffff pcib1: special decode ISA pci2: on pcib1 pcib1: allocated bus range (2-2) for rid 0 of pci2 pci2: domain=0, physical bus=2 pcib2: irq 21 at device 28.1 on pci0 pcib2: allocating non-ISA range 0x3000-0x30ff pcib0: allocated type 4 (0x3000-0x30ff) for rid 1c of pcib2 pcib2: allocating non-ISA range 0x3400-0x34ff pcib0: allocated type 4 (0x3400-0x34ff) for rid 1c of pcib2 pcib2: allocating non-ISA range 0x3800-0x38ff pcib0: allocated type 4 (0x3800-0x38ff) for rid 1c of pcib2 pcib2: allocating non-ISA range 0x3c00-0x3cff pcib0: allocated type 4 (0x3c00-0x3cff) for rid 1c of pcib2 pcib0: allocated type 3 (0xf6000000-0xf7ffffff) for rid 20 of pcib2 pcib0: allocated type 3 (0xf8600000-0xf86fffff) for rid 24 of pcib2 pcib2: domain 0 pcib2: secondary bus 3 pcib2: subordinate bus 3 pcib2: I/O decode 0x3000-0x3fff pcib2: memory decode 0xf6000000-0xf7ffffff pcib2: prefetched decode 0xf8600000-0xf86fffff pcib2: special decode ISA pci3: on pcib2 pcib2: allocated bus range (3-3) for rid 0 of pci3 pci3: domain=0, physical bus=3 found-> vendor=0x1814, dev=0x0781, revid=0x00 domain=0, bus=3, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 3 supports D0 D3 current D0 MSI supports 32 messages, 64 bit map[10]: type Memory, range 32, base 0xf7f00000, size 16, enabled pcib2: allocated memory range (0xf7f00000-0xf7f0ffff) for rid 10 of pci0:3:0:0 pcib2: matched entry for 3.0.INTA pcib2: slot 0 INTA hardwired to IRQ 17 ral0: mem 0xf7f00000-0xf7f0ffff irq 17 at device 0.0 on pci3 ral0: attempting to allocate 1 MSI vectors (32 supported) msi: routing MSI IRQ 258 to local APIC 0 vector 56 ral0: using IRQ 258 for MSI ral0: MAC/BBP RT2872 (rev 0x0200), RF RT2720 (MIMO 1T2R), address 00:15:af: ral0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ral0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps uhci2: port 0x18a0-0x18bf irq 16 at device 29.0 on pci0 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 57 usbus3 on uhci2 uhci2: usbpf: Attached uhci3: port 0x18c0-0x18df irq 17 at device 29.1 on pci0 ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 0 vector 58 usbus4 on uhci3 uhci3: usbpf: Attached ehci1: mem 0xf8427000-0xf84273ff irq 19 at device 29.7 on pci0 ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 0 vector 59 usbus5: EHCI version 1.0 usbus5 on ehci1 ehci1: usbpf: Attached pcib3: at device 30.0 on pci0 pcib0: allocated type 4 (0x4000-0x7fff) for rid 1c of pcib3 pcib0: allocated type 3 (0xd4000000-0xd7efffff) for rid 20 of pcib3 pcib0: allocated type 3 (0xd8000000-0xdbffffff) for rid 24 of pcib3 pcib3: domain 0 pcib3: secondary bus 5 pcib3: subordinate bus 8 pcib3: I/O decode 0x4000-0x7fff pcib3: memory decode 0xd4000000-0xd7efffff pcib3: prefetched decode 0xd8000000-0xdbffffff pcib3: special decode subtractive pci5: on pcib3 pcib3: allocated bus range (5-5) for rid 0 of pci5 pci5: domain=0, physical bus=5 found-> vendor=0x1180, dev=0x0476, revid=0xba domain=0, bus=5, slot=0, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd7eff000, size 12, enabled pcib3: allocated memory range (0xd7eff000-0xd7efffff) for rid 10 of pci0:5:0:0 pcib3: matched entry for 5.0.INTA pcib3: slot 0 INTA hardwired to IRQ 16 secbus=6, subbus=8 pcib3: allocated bus range (6-8) for rid 0 of pci0:5:0:0 found-> vendor=0x1180, dev=0x0822, revid=0x21 domain=0, bus=5, slot=0, func=2 class=08-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd7efec00, size 8, enabled pcib3: allocated memory range (0xd7efec00-0xd7efecff) for rid 10 of pci0:5:0:2 pcib3: matched entry for 5.0.INTC pcib3: slot 0 INTC hardwired to IRQ 18 cbb0: mem 0xd7eff000-0xd7efffff irq 16 at device 0.0 on pci5 cardbus0: on cbb0 cbb0: allocated bus range (6-6) for rid 0 of cardbus0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: PCI Configuration space: 0x00: 0x04761180 0x02100007 0x060700ba 0x00822008 0x10: 0xd7eff000 0x020000dc 0xb0080605 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000110 0x40: 0x20c617aa 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x04a00001 0x00000000 0x04630463 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000000 0x09000000 0x00f00000 0x00000005 0xb0: 0x00000000 0xb6000000 0x00003000 0x00000000 0xc0: 0x20c617aa 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 sdhci_pci0: mem 0xd7efec00-0xd7efecff irq 18 at device 0.2 on pci5 sdhci_pci0-slot0: 33MHz HS 4bits 3.3V DMA sdhci_pci0-slot0: ============== REGISTER DUMP ============== sdhci_pci0-slot0: Sys addr: 0x00000000 | Version: 0x00000400 sdhci_pci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci_pci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000 sdhci_pci0-slot0: Present: 0x01f20000 | Host ctl: 0x00000000 sdhci_pci0-slot0: Power: 0x00000000 | Blk gap: 0x00000000 sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000000 sdhci_pci0-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci_pci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci_pci0-slot0: Caps: 0x01e021a1 | Max curr: 0x00000040 sdhci_pci0-slot0: =========================================== sdhci_pci0: 1 slot(s) allocated ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18e0-0x18ef at device 31.1 on pci0 ata0: at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 61 ahci0: port 0x1c30-0x1c37,0x1c24-0x1c27,0x1c28-0x1c2f,0x1c20-0x1c23,0x1c00-0x1c1f mem 0xf8426000-0xf84267ff irq 16 at device 31.2 on pci0 ahci0: attempting to allocate 4 MSI vectors (4 supported) msi: routing MSI IRQ 259 to local APIC 0 vector 64 msi: routing MSI IRQ 260 to local APIC 0 vector 65 msi: routing MSI IRQ 261 to local APIC 0 vector 66 msi: routing MSI IRQ 262 to local APIC 0 vector 67 ahci0: using IRQs 259-262 for MSI ahci0: AHCI v1.10 with 3 3Gbps ports, Port Multiplier not supported ahci0: Caps: 64bit NCQ SNTF ALP AL CLO 3Gbps PMD SSC PSC 32cmd CCC 3ports ahcich0: at channel 0 on ahci0 ahcich0: Caps: ahcich1: not probed (disabled) ahcich2: not probed (disabled) pci0: at device 31.3 (no driver attached) acpi_tz0: on acpi0 acpi_tz1: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x54ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 62 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0047 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 63 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00004000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 battery0: on acpi0 acpi_acad0: on acpi0 ACPI: Enabled 3 GPEs in block 00 to 1F acpi0: wakeup code va 0xfffffe0235249000 pa 0x94000 ex_isa_identify() ahc_isa_identify 0: ioport 0xc00 alloc failed ahc_isa_identify 1: ioport 0x1c00 alloc failed ahc_isa_identify 2: ioport 0x2c00 alloc failed ahc_isa_identify 3: ioport 0x3c00 alloc failed ahc_isa_identify 4: ioport 0x4c00 alloc failed ahc_isa_identify 5: ioport 0x5c00 alloc failed ahc_isa_identify 6: ioport 0x6c00 alloc failed ahc_isa_identify 7: ioport 0x7c00 alloc failed ahc_isa_identify 8: ioport 0x8c00 alloc failed ahc_isa_identify 9: ioport 0x9c00 alloc failed ahc_isa_identify 10: ioport 0xac00 alloc failed ahc_isa_identify 11: ioport 0xbc00 alloc failed ahc_isa_identify 12: ioport 0xcc00 alloc failed ahc_isa_identify 13: ioport 0xdc00 alloc failed ahc_isa_identify 14: ioport 0xec00 alloc failed pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 pcib0: allocated type 3 (0xd0000-0xd07ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd0800-0xd0fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd1000-0xd17ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd1800-0xd1fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd2000-0xd27ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd2800-0xd2fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd3000-0xd37ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd3800-0xd3fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd4000-0xd47ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd4800-0xd4fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd5000-0xd57ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd5800-0xd5fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd6000-0xd67ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd6800-0xd6fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd7000-0xd77ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd7800-0xd7fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd8000-0xd87ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd8800-0xd8fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd9000-0xd97ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd9800-0xd9fff) for rid 1 of orm0 pcib0: allocated type 3 (0xda000-0xda7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xda800-0xdafff) for rid 1 of orm0 pcib0: allocated type 3 (0xdb000-0xdb7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdb800-0xdbfff) for rid 1 of orm0 pcib0: allocated type 3 (0xdc000-0xdc7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdc800-0xdcfff) for rid 1 of orm0 pcib0: allocated type 3 (0xdd000-0xdd7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdd800-0xddfff) for rid 1 of orm0 pcib0: allocated type 3 (0xde000-0xde7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xde800-0xdefff) for rid 1 of orm0 pcib0: allocated type 3 (0xdf000-0xdf7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdf800-0xdffff) for rid 1 of orm0 isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 pcib0: allocated type 4 (0x3f0-0x3f5) for rid 0 of fdc0 pcib0: allocated type 4 (0x3f7-0x3f7) for rid 1 of fdc0 fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x3f8-0x3ff) for rid 0 of uart0 uart0 failed to probe at port 0x3f8-0x3ff irq 4 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 Device configuration finished. procfs registered ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 65536 lo0: bpf attached hptnr: no controller detected. hpt27xx: no controller detected. hptrr: no controller detected. hdac0: Command timeout on address 1 hdac0: Command timeout on address 1 hdac0: CODEC is not responding! hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 hdaa0: Subsystem ID: 0x17aa20d6 hdaa0: NumGPIO=3 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdaa0: GPIO0: disabled hdaa0: GPIO1: input state=0 hdaa0: GPIO2: disabled hdaa0: WARNING: nid=2 has cnid outside of the AFG range j=0 entnum=4 index=0 res=0x00090801 hdaa0: Original pins configuration: hdaa0: nid 0x as seq device conn jack loc color misc hdaa0: 17 0421401f 1 15 Headphones Jack 1/8 Right Green 0 hdaa0: 18 90170110 1 0 Speaker Fixed Analog Internal Unknown 1 hdaa0: 19 511301f0 15 0 Speaker None ATAPI 0x11 Unknown 1 hdaa0: 20 04a15021 2 1 Mic Jack 1/8 Right Red 0 hdaa0: 21 90a7012e 2 14 Mic Fixed Analog Internal Unknown 1 hdaa0: 22 593301f0 15 0 CD None ATAPI Onboard Unknown 1 hdaa0: 23 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 hdaa0: 24 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 hdaa0: 26 91f311f0 15 0 Other Fixed ATAPI 0x11 Black 1 hdaa0: 27 614411f0 15 0 SPDIF-out None RCA Ext-Rear Black 1 hdaa0: 28 21a15020 2 0 Mic Jack 1/8 Ext-Rear Red 0 hdaa0: Patching widget caps nid=26 0x00400000 -> 0x00700000 hdaa0: Patched pins configuration: hdaa0: nid 0x as seq device conn jack loc color misc hdaa0: 17 0421401f 1 15 Headphones Jack 1/8 Right Green 0 hdaa0: 18 90170110 1 0 Speaker Fixed Analog Internal Unknown 1 hdaa0: 19 511301f0 15 0 Speaker None ATAPI 0x11 Unknown 1 DISA hdaa0: 20 04a15021 2 1 Mic Jack 1/8 Right Red 0 hdaa0: 21 90a7012e 2 14 Mic Fixed Analog Internal Unknown 1 hdaa0: 22 593301f0 15 0 CD None ATAPI Onboard Unknown 1 DISA hdaa0: 23 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 DISA hdaa0: 24 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 DISA hdaa0: 27 614411f0 15 0 SPDIF-out None RCA Ext-Rear Black 1 DISA hdaa0: 28 21a15020 2 0 Mic Jack 1/8 Ext-Rear Red 0 hdaa0: 2 associations found: hdaa0: Association 0 (1) out: hdaa0: Pin nid=18 seq=0 hdaa0: Pin nid=17 seq=15 hdaa0: Association 1 (2) in: hdaa0: Pin nid=28 seq=0 hdaa0: Pin nid=20 seq=1 hdaa0: Pin nid=21 seq=14 hdaa0: Tracing association 0 (1) hdaa0: Pin 18 traced to DAC 4 hdaa0: Pin 17 traced to DAC 4 and hpredir 0 hdaa0: Association 0 (1) trace succeeded hdaa0: Tracing association 1 (2) hdaa0: Unable to trace pin 28 to ADC 5, undo traces hdaa0: Unable to trace pin 28 to ADC 6, undo traces hdaa0: Pin 28 traced to ADC 8 hdaa0: Pin 20 traced to ADC 8 hdaa0: Pin 21 traced to ADC 8 hdaa0: Association 1 (2) trace succeeded hdaa0: Looking for additional DAC for association 0 (1) hdaa0: Looking for additional ADC for association 1 (2) hdaa0: ADC 9 considered equal to ADC 8 hdaa0: Tracing input monitor hdaa0: Tracing nid 32 to out hdaa0: nid 32 is input monitor hdaa0: Tracing other input monitors hdaa0: Tracing nid 20 to out hdaa0: Tracing nid 21 to out hdaa0: Tracing nid 28 to out hdaa0: Tracing beeper hdaa0: Headphones redirection for association 0 nid=17 using unsolicited responses. hdaa0: Redirect output to: main hdaa0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref pcm0: at nid 18,17 and 28,20,21 on hdaa0 pcm0: Playback: pcm0: Stream cap: 0x00000001 PCM pcm0: PCM cap: 0x000e07ff 16 20 24 bits, 8 11 16 22 32 44 48 88 96 176 192 KHz pcm0: DAC: 4 pcm0: pcm0: nid=18 [pin: Speaker (Fixed)] pcm0: + <- nid=10 [audio mixer] [src: pcm, mix] pcm0: + <- nid=4 [audio output] [src: pcm] pcm0: + <- nid=33 [audio selector] [src: mix] pcm0: + <- nid=32 [audio mixer] [src: mix] pcm0: pcm0: nid=17 [pin: Headphones (Green Jack)] pcm0: + <- nid=7 [audio mixer] [src: pcm, mix] pcm0: + <- nid=34 [audio selector] [src: pcm] pcm0: + <- nid=4 [audio output] [src: pcm] pcm0: + <- nid=33 [audio selector] [src: mix] pcm0: + <- nid=32 [audio mixer] [src: mix] pcm0: pcm0: Record: pcm0: Stream cap: 0x00000001 PCM pcm0: PCM cap: 0x000e07ff 16 20 24 bits, 8 11 16 22 32 44 48 88 96 176 192 KHz pcm0: ADC: 8 pcm0: ADC: 9 pcm0: pcm0: nid=8 [audio input] pcm0: + <- nid=12 [audio selector] [src: line, mic, mix, monitor] pcm0: + <- nid=20 [pin: Mic (Red Jack)] [src: mic] pcm0: + <- nid=21 [pin: Mic (Fixed)] [src: monitor] pcm0: + <- nid=32 [audio mixer] [src: mix] pcm0: + <- nid=37 [audio selector] [src: line] pcm0: + <- nid=28 [pin: Mic (Red Jack)] [src: line] pcm0: pcm0: nid=9 [audio input] pcm0: + <- nid=13 [audio selector] [src: line, mic, mix, monitor] pcm0: + <- nid=20 [pin: Mic (Red Jack)] [src: mic] pcm0: + <- nid=21 [pin: Mic (Fixed)] [src: monitor] pcm0: + <- nid=32 [audio mixer] [src: mix] pcm0: + <- nid=37 [audio selector] [src: line] pcm0: + <- nid=28 [pin: Mic (Red Jack)] [src: line] pcm0: pcm0: Input Mix: pcm0: pcm0: nid=32 [audio mixer] pcm0: + <- nid=20 [pin: Mic (Red Jack)] [src: mic] pcm0: + <- nid=21 [pin: Mic (Fixed)] [src: monitor] pcm0: + <- nid=26 [beep widget] [src: speaker] pcm0: + <- nid=37 [audio selector] [src: line] pcm0: + <- nid=28 [pin: Mic (Red Jack)] [src: line] pcm0: pcm0: Master Volume (OSS: vol): -58/0dB pcm0: +- ctl 2 (nid 4 out): -58/0dB (40 steps) pcm0: +- ctl 5 (nid 7 in 0): mute pcm0: +- ctl 6 (nid 7 in 1): mute pcm0: +- ctl 7 (nid 10 in 0): mute pcm0: +- ctl 8 (nid 10 in 1): mute pcm0: +- ctl 14 (nid 17 in ): mute pcm0: +- ctl 15 (nid 18 in ): mute pcm0: pcm0: PCM Volume (OSS: pcm): -58/0dB pcm0: +- ctl 2 (nid 4 out): -58/0dB (40 steps) pcm0: +- ctl 5 (nid 7 in 0): mute pcm0: +- ctl 7 (nid 10 in 0): mute pcm0: pcm0: Microphone Volume (OSS: mic): 0/30dB pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute pcm0: +- ctl 17 (nid 20 out): 0/30dB (4 steps) pcm0: +- ctl 24 (nid 32 in 0): -34/12dB (32 steps) + mute pcm0: pcm0: Microphone2 Volume (OSS: monitor): 0/30dB pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute pcm0: +- ctl 18 (nid 21 out): 0/30dB (4 steps) pcm0: +- ctl 25 (nid 32 in 1): -34/12dB (32 steps) + mute pcm0: pcm0: Line-in Volume (OSS: line): 0/30dB pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute pcm0: +- ctl 28 (nid 32 in 4): -34/12dB (32 steps) + mute pcm0: +- ctl 32 (nid 37 out): 0/30dB (4 steps) pcm0: pcm0: Speaker/Beep Volume (OSS: speaker): -34/0dB pcm0: +- ctl 13 (nid 16 out): -45/0dB (16 steps) + mute pcm0: +- ctl 27 (nid 32 in 3): -34/12dB (32 steps) + mute pcm0: pcm0: Recording Level (OSS: rec): -58/22dB pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute pcm0: pcm0: Input Mix Level (OSS: mix): -46/0dB pcm0: +- ctl 6 (nid 7 in 1): mute pcm0: +- ctl 8 (nid 10 in 1): mute pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute pcm0: +- ctl 29 (nid 33 out): -46/0dB (32 steps) + mute pcm0: pcm0: Input Monitoring Level (OSS: igain): 0/0dB pcm0: +- ctl 6 (nid 7 in 1): mute pcm0: +- ctl 8 (nid 10 in 1): mute pcm0: pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "mix": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "ogain": pcm0: Mixer "monitor": pcm0: Playback channel set is: Front Left, Front Right, pcm0: Playback channel matrix is: 2.0 (unknown) pcm0: Automatically set rec source to: monitor pcm0: Recording channel set is: Front Left, Front Right, pcm0: Recording channel matrix is: 2.0 (unknown) random: unblocking device. usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 ata0: reset tp1 mask=03 ostat0=7f ostat1=7f ugen0.1: at usbus0 uhub0: on usbus0 ugen3.1: at usbus3 uhub1: on usbus3 ugen2.1: at usbus2 uhub2: on usbus2 ugen1.1: at usbus1 uhub3: on usbus1 ugen5.1: at usbus5 uhub4: on usbus5 ugen4.1: at usbus4 uhub5: on usbus4 ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of pci0:6:0:0 unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 cbb0: Opening memory: cbb0: Normal: 0xd4000000-0xd400ffff cardbus0: Expecting link target, got 0xff cbb0: Opening memory: pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of pci0:6:0:0 unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 cbb0: Opening memory: cbb0: Normal: 0xd4000000-0xd400ffff cardbus0: Expecting link target, got 0xff cbb0: Opening memory: found-> vendor=0x168c, dev=0x0013, revid=0x01 domain=0, bus=6, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0002, statreg=0x8210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 ath0: irq 16 at device 0.0 on cardbus0 pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of ath0 ath0: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 cbb0: Opening memory: cbb0: Normal: 0xd4000000-0xd400ffff ath0: unable to attach hardware; HAL status 14 cbb0: Opening memory: device_attach: ath0 attach returned 6 ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat1=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: reset tp2 stat0=ff stat1=ff devices=0x0 ahcich0: AHCI reset... ahcich0: SATA connect time=100us status=00000123 ahcich0: AHCI reset: device found battery0: battery initialization start acpi_acad0: acline initialization start battery0: battery initialization done, tried 1 times acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times ahcich0: AHCI reset: device ready after 100ms pass0 at ahcich0 bus 0 scbus1 target 0 lun 0 pass0: ATA-8 SATA 2.x device pass0: Serial Number OCZ-0350VO37893A086L pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) pass0: Command Queueing enabled ada0 at ahcich0 bus 0 scbus1 target 0 lun 0 GEOM: new disk ada0 ada0: ATA-8 SATA 2.x device ada0: Serial Number OCZ-0350VO37893A086L ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 Netvsc initializing... done! SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010200 err: 0x000000f0 pmc: 0x00010400 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 1 vector 49 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 1 vector 50 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 1 vector 51 ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 1 vector 52 msi: Assigning MSI IRQ 256 to local APIC 1 vector 53 msi: Assigning MSI IRQ 258 to local APIC 1 vector 54 TSC timecounter disabled: C3 enabled. Timecounter "TSC" frequency 1596037768 Hz quality -1000 WARNING: WITNESS option enabled, expect reduced performance. Root mount waiting for: usbus5 usbus2 uhub4: 4 ports with 4 removable, self powered uhub2: 4 ports with 4 removable, self powered Trying to mount root from zfs:zroot/ROOT/default []... start_init: trying /sbin/init ugen0.2: at usbus0 From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 22:08:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 626BFFBF for ; Wed, 23 Apr 2014 22:08:02 +0000 (UTC) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 175A41D54 for ; Wed, 23 Apr 2014 22:08:02 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id x3so1638080qcv.26 for ; Wed, 23 Apr 2014 15:08:01 -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=GEtP7bIpM08c+zgerJY1vIQL/R4/gy0tsP0agXxstew=; b=ha0xzle9FX8NZbsVJeJQCjFKuTHtmQWfA+7G6MIcyCG0pqYEK4cNWi86WTUCHOES/m lDiIldwDKHtoWmvserAQHcRo9/j9laxVq0u1hSzVAl1VipmRyYHlaHbqfPbI2Ep1uH6a KSxnXSZl855j6tWiKDZRUZI8ks+iWZUN2j7sbWC3zGRHfnn7WkNUUqxMy1U1IM+R9051 5Hnai9Xqis/dWB+yetZnJ2QjXga6SsKxSknnI/QCqOYcZgUxPp7GZ3LizeuG/cL3sw7X 9HeNAcXAQYHMRVBosfV6VOkASRrPbT9k6nCFk5ZuRRrAZUqw7MkrS5vMLYAOyjG4TRmj TZbQ== MIME-Version: 1.0 X-Received: by 10.140.42.38 with SMTP id b35mr56370798qga.87.1398290881116; Wed, 23 Apr 2014 15:08:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 23 Apr 2014 15:08:01 -0700 (PDT) In-Reply-To: References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> <4F8604C1.4090902@gmail.com> <4F861C10.5020503@gmail.com> Date: Wed, 23 Apr 2014 15:08:01 -0700 X-Google-Sender-Auth: H1mLmmI8HMG4aBubdCp7vC4QhcA Message-ID: Subject: Re: ath(4) fails to attach From: Adrian Chadd To: "Sevan / Venture37" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 22:08:02 -0000 It's failing the selftest (error 14 is ESELFTEST.) -a On 23 April 2014 15:04, Sevan / Venture37 wrote: > On 12 April 2012 01:04, Sevan / Venture37 wrote: >> On 11/04/2012 23:34, Adrian Chadd wrote: >>> >>> So it attaches fine with debugging enabled, but not with debugging >>> disabled? >> >> >> Nope, neither. > > Just over 2 years on > Tried the ath(4) card again on a new snapshot freshly installed on my X61s > > unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 > cbb0: Opening memory: > cbb0: Normal: 0xd4000000-0xd400ffff > cardbus0: Expecting link target, got 0xff > cbb0: Opening memory: > pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of pci0:6:0:0 > unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 > cbb0: Opening memory: > cbb0: Normal: 0xd4000000-0xd400ffff > cardbus0: Expecting link target, got 0xff > cbb0: Opening memory: > found-> vendor=0x168c, dev=0x0013, revid=0x01 > domain=0, bus=6, slot=0, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0002, statreg=0x8210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) > intpin=a, irq=16 > powerspec 2 supports D0 D3 current D0 > ath0: irq 16 at device 0.0 on cardbus0 > pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of ath0 > ath0: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 > cbb0: Opening memory: > cbb0: Normal: 0xd4000000-0xd400ffff > ath0: unable to attach hardware; HAL status 14 > cbb0: Opening memory: > device_attach: ath0 attach returned 6 > > Verbose dmesg: > > Table 'FACP' at 0xbf6bd300 > Table 'SSDT' at 0xbf6bd4b4 > Table 'ECDT' at 0xbf6cba38 > Table 'TCPA' at 0xbf6cba8a > Table 'APIC' at 0xbf6cbabc > APIC: Found table at 0xbf6cbabc > APIC: Using the MADT enumerator. > MADT: Found CPU APIC ID 0 ACPI ID 0: enabled > SMP: Added CPU 0 (AP) > MADT: Found CPU APIC ID 1 ACPI ID 1: enabled > SMP: Added CPU 1 (AP) > Copyright (c) 1992-2014 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-CURRENT #0 r264459: Mon Apr 14 18:10:10 UTC 2014 > root@grind.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.4 (tags/RELEASE_34/final 197956) 20140216 > WARNING: WITNESS option enabled, expect reduced performance. > Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81e99000. > Preloaded elf obj module "/boot/kernel/zfs.ko" at 0xffffffff81e99d90. > Preloaded elf obj module "/boot/kernel/opensolaris.ko" at 0xffffffff81e9a5b8. > Calibrating TSC clock ... TSC clock: 1596037768 Hz > CPU: Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz (1596.04-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x6fb Family=0x6 Model=0xf Stepping=11 > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant, performance statistics > real memory = 8589934592 (8192 MB) > Physical memory chunk(s): > 0x0000000000010000 - 0x0000000000099fff, 565248 bytes (138 pages) > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) > 0x0000000001eca000 - 0x00000000bf6affff, 3179175936 bytes (776166 pages) > 0x0000000100000000 - 0x000000022d671fff, 5056700416 bytes (1234546 pages) > avail memory = 8183607296 (7804 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > INTR: Adding local APIC 1 as a target > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > APIC: CPU 0 has ACPI ID 0 > APIC: CPU 1 has ACPI ID 1 > x86bios: IVT 0x000000-0x0004ff at 0xfffff80000000000 > x86bios: SSEG 0x098000-0x098fff at 0xfffffe01eb3ea000 > x86bios: EBDA 0x09d000-0x09ffff at 0xfffff8000009d000 > x86bios: ROM 0x0a0000-0x0fefff at 0xfffff800000a0000 > ULE: setup cpu 0 > ULE: setup cpu 1 > ACPI: RSDP 0xf6950 00024 (v02 LENOVO) > ACPI: XSDT 0xbf6bd1b7 0009C (v01 LENOVO TP-7V 00002220 LTP 00000000) > ACPI: FACP 0xbf6bd300 000F4 (v03 LENOVO TP-7V 00002220 LNVO 00000001) > ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: > 0/32 (20130823/tbfadt-601) > ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has zero > address or length: 0x000000000000102C/0x0 (20130823/tbfadt-630) > ACPI: DSDT 0xbf6bd6db 0E35D (v01 LENOVO TP-7V 00002220 MSFT 03000000) > ACPI: FACS 0xbf6e4000 00040 > ACPI: SSDT 0xbf6bd4b4 00227 (v01 LENOVO TP-7V 00002220 MSFT 03000000) > ACPI: ECDT 0xbf6cba38 00052 (v01 LENOVO TP-7V 00002220 LNVO 00000001) > ACPI: TCPA 0xbf6cba8a 00032 (v02 LENOVO TP-7V 00002220 LNVO 00000001) > ACPI: APIC 0xbf6cbabc 00068 (v01 LENOVO TP-7V 00002220 LNVO 00000001) > ACPI: MCFG 0xbf6cbb24 0003C (v01 LENOVO TP-7V 00002220 LNVO 00000001) > ACPI: HPET 0xbf6cbb60 00038 (v01 LENOVO TP-7V 00002220 LNVO 00000001) > ACPI: SLIC 0xbf6cbb98 00176 (v01 LENOVO TP-7V 00002220 SLIC 00000000) > ACPI: SLAC 0xbf6cbdf0 00176 (v01 LENOVO TP-7V 00002220 LTP 00000000) > ACPI: BOOT 0xbf6cbf66 00028 (v01 LENOVO TP-7V 00002220 LTP 00000001) > ACPI: ASF! 0xbf6cbf8e 00072 (v16 LENOVO TP-7V 00002220 PTL 00000001) > ACPI: SSDT 0xbf6e2697 0025F (v01 LENOVO TP-7V 00002220 INTL 20050513) > ACPI: SSDT 0xbf6e28f6 000A6 (v01 LENOVO TP-7V 00002220 INTL 20050513) > ACPI: SSDT 0xbf6e299c 004F7 (v01 LENOVO TP-7V 00002220 INTL 20050513) > ACPI: SSDT 0xbf6e2e93 001D8 (v01 LENOVO TP-7V 00002220 INTL 20050513) > MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 > ioapic0: Changing APIC ID to 1 > ioapic0: Routing external 8259A's -> intpin 0 > MADT: Interrupt override: source 0, irq 2 > ioapic0: Routing IRQ 0 -> intpin 2 > MADT: Interrupt override: source 9, irq 9 > ioapic0: intpin 9 trigger: level > lapic0: Routing NMI -> LINT1 > lapic0: LINT1 trigger: edge > lapic0: LINT1 polarity: high > lapic1: Routing NMI -> LINT1 > lapic1: LINT1 trigger: edge > lapic1: LINT1 polarity: high > ioapic0 irqs 0-23 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 > snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] > feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 > feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 > wlan: <802.11 Link Layer> > Hardware, Intel IvyBridge+ RNG: RDRAND is not present > Hardware, VIA Nehemiah Padlock RNG: VIA Padlock RNG not present > nfslock: pseudo-device > kbd: new array size 4 > kbd1 at kbdmux0 > mem: > VESA: INT 0x10 vector 0xc000:0x0014 > VESA: information block > 0000 56 45 53 41 00 03 00 01 00 99 01 00 00 00 40 00 > 0010 00 99 77 00 00 01 3d 01 00 99 4f 01 00 99 7d 01 > 0020 00 99 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0040 60 01 61 01 62 01 63 01 64 01 65 01 66 01 67 01 > 0050 68 01 69 01 6a 01 6b 01 6c 01 6d 01 6e 01 6f 01 > 0060 70 01 71 01 3c 01 4d 01 5c 01 3a 01 4b 01 5a 01 > 0070 07 01 1a 01 1b 01 05 01 17 01 18 01 12 01 14 01 > 0080 15 01 01 01 03 01 11 01 ff ff 00 00 00 00 00 00 > 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0100 49 6e 74 65 6c 28 72 29 47 4d 39 36 35 2f 50 4d > 0110 39 36 35 2f 47 4c 39 36 30 20 47 72 61 70 68 69 > 0120 63 73 20 43 68 69 70 20 41 63 63 65 6c 65 72 61 > 0130 74 65 64 20 56 47 41 20 42 49 4f 53 00 49 6e 74 > 0140 65 6c 20 43 6f 72 70 6f 72 61 74 69 6f 6e 00 49 > 0150 6e 74 65 6c 28 72 29 47 4d 39 36 35 2f 50 4d 39 > 0160 36 35 2f 47 4c 39 36 30 20 47 72 61 70 68 69 63 > 0170 73 20 43 6f 6e 74 72 6f 6c 6c 65 72 00 48 61 72 > 0180 64 77 61 72 65 20 56 65 72 73 69 6f 6e 20 30 2e > 0190 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > VESA: 12 mode(s) found > VESA: v3.0, 7616k memory, flags:0x1, mode table:0xfffffe01eb3ff040 (99000040) > VESA: Intel(r)GM965/PM965/GL960 Graphics Chip Accelerated VGA BIOS > VESA: Intel Corporation Intel(r)GM965/PM965/GL960 Graphics Controller > Hardware Version 0.0 > io: > VMBUS: load > null: > Falling back to random adaptor > random: initialized > hptnr: R750/DC7280 controller driver v1.0 > hpt27xx: RocketRAID 27xx controller driver v1.1 > hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 > acpi0: on motherboard > ACPI: All ACPI Tables successfully acquired > PCIe: Memory Mapped configuration base @ 0xf0000000 > CPU0: local APIC error 0x40 > ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 > acpi_ec0: port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, bff00000 (3) failed > cpu0: Processor \134_PR_.CPU0 (ACPI ID 0) -> APIC ID 0 > cpu0: on acpi0 > ACPI: SSDT 0xbf6e1b32 00282 (v01 PmRef Cpu0Ist 00000100 INTL 20050513) > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0 00282 (v01 PmRef Cpu0Ist 00000100 INTL 20050513) > ACPI: SSDT 0xbf6e1e39 0085E (v01 PmRef Cpu0Cst 00000100 INTL 20050513) > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0 0085E (v01 PmRef Cpu0Cst 00000100 INTL 20050513) > cpu1: Processor \134_PR_.CPU1 (ACPI ID 1) -> APIC ID 1 > cpu1: on acpi0 > ACPI: SSDT 0xbf6e1a6a 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513) > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513) > ACPI: SSDT 0xbf6e1db4 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513) > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513) > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 > Event timer "i8254" frequency 1193182 Hz quality 100 > hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > hpet0: vendor 0x8086, rev 0x1, 14318180Hz 64bit, 3 timers, legacy route > hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic > hpet0: t1: irqs 0x00f00000 (0) > hpet0: t2: irqs 0x00f00800 (0) > Timecounter "HPET" frequency 14318180 Hz quality 950 > ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 0 vector 50 > Event timer "HPET" frequency 14318180 Hz quality 450 > Event timer "HPET1" frequency 14318180 Hz quality 440 > Event timer "HPET2" frequency 14318180 Hz quality 440 > atrtc0: port 0x70-0x71 irq 8 on acpi0 > atrtc0: registered as a time-of-day clock (resolution 1000000us, > adjustment 0.500000000s) > ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 51 > Event timer "RTC" frequency 32768 Hz quality 0 > ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > pci_link0: Index IRQ Rtd Ref IRQs > Initial Probe 0 10 N 0 3 4 5 6 7 9 10 11 > Validation 0 10 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link1: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link2: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link3: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link4: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link5: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link6: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > pci_link7: Index IRQ Rtd Ref IRQs > Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 > Validation 0 11 N 0 3 4 5 6 7 9 10 11 > After Disable 0 255 N 0 3 4 5 6 7 9 10 11 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pcib0: decoding 5 range 0-0xff > pcib0: decoding 4 range 0-0xcf7 > pcib0: decoding 4 range 0xd00-0xffff > pcib0: decoding 3 range 0xa0000-0xbffff > pcib0: decoding 3 range 0xd0000-0xd3fff > pcib0: decoding 3 range 0xd4000-0xd7fff > pcib0: decoding 3 range 0xd8000-0xdbfff > pcib0: decoding 3 range 0xdc000-0xdffff > pcib0: decoding 3 range 0xc0000000-0xfebfffff > pci0: on pcib0 > pci0: domain=0, physical bus=0 > found-> vendor=0x8086, dev=0x2a00, revid=0x0c > domain=0, bus=0, slot=0, func=0 > class=06-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x2a02, revid=0x0c > domain=0, bus=0, slot=2, func=0 > class=03-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > powerspec 3 supports D0 D3 current D0 > MSI supports 1 message > map[10]: type Memory, range 64, base 0xf8000000, size 20, enabled > pcib0: allocated type 3 (0xf8000000-0xf80fffff) for rid 10 of pci0:0:2:0 > map[18]: type Prefetchable Memory, range 64, base 0xe0000000, size 28, enabled > pcib0: allocated type 3 (0xe0000000-0xefffffff) for rid 18 of pci0:0:2:0 > map[20]: type I/O Port, range 32, base 0x1800, size 3, enabled > pcib0: allocated type 4 (0x1800-0x1807) for rid 20 of pci0:0:2:0 > pcib0: matched entry for 0.2.INTA > pcib0: slot 2 INTA hardwired to IRQ 16 > found-> vendor=0x8086, dev=0x2a03, revid=0x0c > domain=0, bus=0, slot=2, func=1 > class=03-80-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > powerspec 3 supports D0 D3 current D0 > map[10]: type Memory, range 64, base 0xf8100000, size 20, enabled > pcib0: allocated type 3 (0xf8100000-0xf81fffff) for rid 10 of pci0:0:2:1 > found-> vendor=0x8086, dev=0x1049, revid=0x03 > domain=0, bus=0, slot=25, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > powerspec 2 supports D0 D3 current D0 > MSI supports 1 message, 64 bit > map[10]: type Memory, range 32, base 0xf8200000, size 17, enabled > pcib0: allocated type 3 (0xf8200000-0xf821ffff) for rid 10 of pci0:0:25:0 > map[14]: type Memory, range 32, base 0xf8225000, size 12, enabled > pcib0: allocated type 3 (0xf8225000-0xf8225fff) for rid 14 of pci0:0:25:0 > map[18]: type I/O Port, range 32, base 0x1840, size 5, enabled > pcib0: allocated type 4 (0x1840-0x185f) for rid 18 of pci0:0:25:0 > pcib0: matched entry for 0.25.INTA > pcib0: slot 25 INTA hardwired to IRQ 20 > found-> vendor=0x8086, dev=0x2834, revid=0x03 > domain=0, bus=0, slot=26, func=0 > class=0c-03-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > map[20]: type I/O Port, range 32, base 0x1860, size 5, enabled > pcib0: allocated type 4 (0x1860-0x187f) for rid 20 of pci0:0:26:0 > pcib0: matched entry for 0.26.INTA > pcib0: slot 26 INTA hardwired to IRQ 20 > found-> vendor=0x8086, dev=0x2835, revid=0x03 > domain=0, bus=0, slot=26, func=1 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > map[20]: type I/O Port, range 32, base 0x1880, size 5, enabled > pcib0: allocated type 4 (0x1880-0x189f) for rid 20 of pci0:0:26:1 > pcib0: matched entry for 0.26.INTB > pcib0: slot 26 INTB hardwired to IRQ 21 > found-> vendor=0x8086, dev=0x283a, revid=0x03 > domain=0, bus=0, slot=26, func=7 > class=0c-03-20, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=c, irq=11 > powerspec 2 supports D0 D3 current D0 > map[10]: type Memory, range 32, base 0xf8426c00, size 10, enabled > pcib0: allocated type 3 (0xf8426c00-0xf8426fff) for rid 10 of pci0:0:26:7 > pcib0: matched entry for 0.26.INTC > pcib0: slot 26 INTC hardwired to IRQ 22 > found-> vendor=0x8086, dev=0x284b, revid=0x03 > domain=0, bus=0, slot=27, func=0 > class=04-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x0010, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > powerspec 2 supports D0 D3 current D0 > MSI supports 1 message, 64 bit > map[10]: type Memory, range 64, base 0xf8220000, size 14, enabled > pcib0: allocated type 3 (0xf8220000-0xf8223fff) for rid 10 of pci0:0:27:0 > pcib0: matched entry for 0.27.INTB > pcib0: slot 27 INTB hardwired to IRQ 17 > found-> vendor=0x8086, dev=0x283f, revid=0x03 > domain=0, bus=0, slot=28, func=0 > class=06-04-00, hdrtype=0x01, mfdev=1 > cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > powerspec 2 supports D0 D3 current D0 > MSI supports 1 message > pcib0: matched entry for 0.28.INTA > pcib0: slot 28 INTA hardwired to IRQ 20 > secbus=2, subbus=2 > found-> vendor=0x8086, dev=0x2841, revid=0x03 > domain=0, bus=0, slot=28, func=1 > class=06-04-00, hdrtype=0x01, mfdev=1 > cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > powerspec 2 supports D0 D3 current D0 > MSI supports 1 message > pcib0: matched entry for 0.28.INTB > pcib0: slot 28 INTB hardwired to IRQ 21 > secbus=3, subbus=3 > found-> vendor=0x8086, dev=0x2830, revid=0x03 > domain=0, bus=0, slot=29, func=0 > class=0c-03-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > map[20]: type I/O Port, range 32, base 0x18a0, size 5, enabled > pcib0: allocated type 4 (0x18a0-0x18bf) for rid 20 of pci0:0:29:0 > pcib0: matched entry for 0.29.INTA > pcib0: slot 29 INTA hardwired to IRQ 16 > found-> vendor=0x8086, dev=0x2831, revid=0x03 > domain=0, bus=0, slot=29, func=1 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > map[20]: type I/O Port, range 32, base 0x18c0, size 5, enabled > pcib0: allocated type 4 (0x18c0-0x18df) for rid 20 of pci0:0:29:1 > pcib0: matched entry for 0.29.INTB > pcib0: slot 29 INTB hardwired to IRQ 17 > found-> vendor=0x8086, dev=0x2836, revid=0x03 > domain=0, bus=0, slot=29, func=7 > class=0c-03-20, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=d, irq=11 > powerspec 2 supports D0 D3 current D0 > map[10]: type Memory, range 32, base 0xf8427000, size 10, enabled > pcib0: allocated type 3 (0xf8427000-0xf84273ff) for rid 10 of pci0:0:29:7 > pcib0: matched entry for 0.29.INTD > pcib0: slot 29 INTD hardwired to IRQ 19 > found-> vendor=0x8086, dev=0x2448, revid=0xf3 > domain=0, bus=0, slot=30, func=0 > class=06-04-01, hdrtype=0x01, mfdev=0 > cmdreg=0x0005, statreg=0x0010, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > secbus=5, subbus=8 > found-> vendor=0x8086, dev=0x2811, revid=0x03 > domain=0, bus=0, slot=31, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x8086, dev=0x2850, revid=0x03 > domain=0, bus=0, slot=31, func=1 > class=01-01-8a, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0288, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=c, irq=255 > pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:31:1 > pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:31:1 > pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:31:1 > pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:31:1 > map[20]: type I/O Port, range 32, base 0x18e0, size 4, enabled > pcib0: allocated type 4 (0x18e0-0x18ef) for rid 20 of pci0:0:31:1 > found-> vendor=0x8086, dev=0x2829, revid=0x03 > domain=0, bus=0, slot=31, func=2 > class=01-06-01, hdrtype=0x00, mfdev=0 > cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=b, irq=10 > powerspec 3 supports D0 D3 current D0 > MSI supports 4 messages > map[10]: type I/O Port, range 32, base 0x1c30, size 3, enabled > pcib0: allocated type 4 (0x1c30-0x1c37) for rid 10 of pci0:0:31:2 > map[14]: type I/O Port, range 32, base 0x1c24, size 2, enabled > pcib0: allocated type 4 (0x1c24-0x1c27) for rid 14 of pci0:0:31:2 > map[18]: type I/O Port, range 32, base 0x1c28, size 3, enabled > pcib0: allocated type 4 (0x1c28-0x1c2f) for rid 18 of pci0:0:31:2 > map[1c]: type I/O Port, range 32, base 0x1c20, size 2, enabled > pcib0: allocated type 4 (0x1c20-0x1c23) for rid 1c of pci0:0:31:2 > map[20]: type I/O Port, range 32, base 0x1c00, size 5, enabled > pcib0: allocated type 4 (0x1c00-0x1c1f) for rid 20 of pci0:0:31:2 > map[24]: type Memory, range 32, base 0xf8426000, size 11, enabled > pcib0: allocated type 3 (0xf8426000-0xf84267ff) for rid 24 of pci0:0:31:2 > pcib0: matched entry for 0.31.INTB > pcib0: slot 31 INTB hardwired to IRQ 16 > found-> vendor=0x8086, dev=0x283e, revid=0x03 > domain=0, bus=0, slot=31, func=3 > class=0c-05-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0103, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > map[10]: type Memory, range 32, base 0xf8427400, size 8, enabled > pcib0: allocated type 3 (0xf8427400-0xf84274ff) for rid 10 of pci0:0:31:3 > map[20]: type I/O Port, range 32, base 0x1c40, size 5, enabled > pcib0: allocated type 4 (0x1c40-0x1c5f) for rid 20 of pci0:0:31:3 > pcib0: matched entry for 0.31.INTA > pcib0: slot 31 INTA hardwired to IRQ 23 > vgapci0: port 0x1800-0x1807 mem > 0xf8000000-0xf80fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on > pci0 > agp0: on vgapci0 > pcib0: allocated type 3 (0xc0000000-0xc0000fff) for rid 64 of agp0 > agp0: Allocated flush page phys 0xc0000000 virt 0xfffff800c0000000 > agp0: aperture size is 256M, detected 7676k stolen memory > agp0: AGP_I965_PGTBL_CTL2: 00000000 > agp0: AGP_I855_GCC1: 0x30 > agp0: AGP_I965_MSAC: 0x00 > agp0: Mappable GTT entries: 65536 > agp0: Total GTT entries: 131072 > vgapci0: Boot video device > vgapci1: mem 0xf8100000-0xf81fffff at device > 2.1 on pci0 > em0: port 0x1840-0x185f > mem 0xf8200000-0xf821ffff,0xf8225000-0xf8225fff irq 20 at device 25.0 > on pci0 > em0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 256 to local APIC 0 vector 52 > em0: using IRQ 256 for MSI > em0: Using an MSI interrupt > em0: bpf attached > em0: Ethernet address: 00:1d:72: > uhci0: port 0x1860-0x187f > irq 20 at device 26.0 on pci0 > usbus0 on uhci0 > uhci0: usbpf: Attached > uhci1: port 0x1880-0x189f > irq 21 at device 26.1 on pci0 > ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 53 > usbus1 on uhci1 > uhci1: usbpf: Attached > ehci0: mem > 0xf8426c00-0xf8426fff irq 22 at device 26.7 on pci0 > ioapic0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 54 > usbus2: EHCI version 1.0 > usbus2 on ehci0 > ehci0: usbpf: Attached > hdac0: mem 0xf8220000-0xf8223fff irq 17 > at device 27.0 on pci0 > hdac0: PCI card vendor: 0x17aa, device: 0x20ac > hdac0: HDA Driver Revision: 20120126_0002 > hdac0: Config options: on=0x00000000 off=0x00000000 > hdac0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 257 to local APIC 0 vector 55 > hdac0: using IRQ 257 for MSI > hdac0: Caps: OSS 4, ISS 4, BSS 0, NSDO 1, 64bit, CORB 256, RIRB 256 > pcib1: irq 20 at device 28.0 on pci0 > pcib1: allocating non-ISA range 0x2000-0x20ff > pcib0: allocated type 4 (0x2000-0x20ff) for rid 1c of pcib1 > pcib1: allocating non-ISA range 0x2400-0x24ff > pcib0: allocated type 4 (0x2400-0x24ff) for rid 1c of pcib1 > pcib1: allocating non-ISA range 0x2800-0x28ff > pcib0: allocated type 4 (0x2800-0x28ff) for rid 1c of pcib1 > pcib1: allocating non-ISA range 0x2c00-0x2cff > pcib0: allocated type 4 (0x2c00-0x2cff) for rid 1c of pcib1 > pcib0: allocated type 3 (0xf4000000-0xf5ffffff) for rid 20 of pcib1 > pcib0: allocated type 3 (0xf8500000-0xf85fffff) for rid 24 of pcib1 > pcib1: domain 0 > pcib1: secondary bus 2 > pcib1: subordinate bus 2 > pcib1: I/O decode 0x2000-0x2fff > pcib1: memory decode 0xf4000000-0xf5ffffff > pcib1: prefetched decode 0xf8500000-0xf85fffff > pcib1: special decode ISA > pci2: on pcib1 > pcib1: allocated bus range (2-2) for rid 0 of pci2 > pci2: domain=0, physical bus=2 > pcib2: irq 21 at device 28.1 on pci0 > pcib2: allocating non-ISA range 0x3000-0x30ff > pcib0: allocated type 4 (0x3000-0x30ff) for rid 1c of pcib2 > pcib2: allocating non-ISA range 0x3400-0x34ff > pcib0: allocated type 4 (0x3400-0x34ff) for rid 1c of pcib2 > pcib2: allocating non-ISA range 0x3800-0x38ff > pcib0: allocated type 4 (0x3800-0x38ff) for rid 1c of pcib2 > pcib2: allocating non-ISA range 0x3c00-0x3cff > pcib0: allocated type 4 (0x3c00-0x3cff) for rid 1c of pcib2 > pcib0: allocated type 3 (0xf6000000-0xf7ffffff) for rid 20 of pcib2 > pcib0: allocated type 3 (0xf8600000-0xf86fffff) for rid 24 of pcib2 > pcib2: domain 0 > pcib2: secondary bus 3 > pcib2: subordinate bus 3 > pcib2: I/O decode 0x3000-0x3fff > pcib2: memory decode 0xf6000000-0xf7ffffff > pcib2: prefetched decode 0xf8600000-0xf86fffff > pcib2: special decode ISA > pci3: on pcib2 > pcib2: allocated bus range (3-3) for rid 0 of pci3 > pci3: domain=0, physical bus=3 > found-> vendor=0x1814, dev=0x0781, revid=0x00 > domain=0, bus=3, slot=0, func=0 > class=02-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > powerspec 3 supports D0 D3 current D0 > MSI supports 32 messages, 64 bit > map[10]: type Memory, range 32, base 0xf7f00000, size 16, enabled > pcib2: allocated memory range (0xf7f00000-0xf7f0ffff) for rid 10 of pci0:3:0:0 > pcib2: matched entry for 3.0.INTA > pcib2: slot 0 INTA hardwired to IRQ 17 > ral0: mem 0xf7f00000-0xf7f0ffff irq 17 at > device 0.0 on pci3 > ral0: attempting to allocate 1 MSI vectors (32 supported) > msi: routing MSI IRQ 258 to local APIC 0 vector 56 > ral0: using IRQ 258 for MSI > ral0: MAC/BBP RT2872 (rev 0x0200), RF RT2720 (MIMO 1T2R), address 00:15:af: > ral0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > ral0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps > 24Mbps 36Mbps 48Mbps 54Mbps > uhci2: port 0x18a0-0x18bf > irq 16 at device 29.0 on pci0 > ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 57 > usbus3 on uhci2 > uhci2: usbpf: Attached > uhci3: port 0x18c0-0x18df > irq 17 at device 29.1 on pci0 > ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 0 vector 58 > usbus4 on uhci3 > uhci3: usbpf: Attached > ehci1: mem > 0xf8427000-0xf84273ff irq 19 at device 29.7 on pci0 > ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 0 vector 59 > usbus5: EHCI version 1.0 > usbus5 on ehci1 > ehci1: usbpf: Attached > pcib3: at device 30.0 on pci0 > pcib0: allocated type 4 (0x4000-0x7fff) for rid 1c of pcib3 > pcib0: allocated type 3 (0xd4000000-0xd7efffff) for rid 20 of pcib3 > pcib0: allocated type 3 (0xd8000000-0xdbffffff) for rid 24 of pcib3 > pcib3: domain 0 > pcib3: secondary bus 5 > pcib3: subordinate bus 8 > pcib3: I/O decode 0x4000-0x7fff > pcib3: memory decode 0xd4000000-0xd7efffff > pcib3: prefetched decode 0xd8000000-0xdbffffff > pcib3: special decode subtractive > pci5: on pcib3 > pcib3: allocated bus range (5-5) for rid 0 of pci5 > pci5: domain=0, physical bus=5 > found-> vendor=0x1180, dev=0x0476, revid=0xba > domain=0, bus=5, slot=0, func=0 > class=06-07-00, hdrtype=0x02, mfdev=1 > cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) > lattimer=0x20 (960 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) > intpin=a, irq=10 > powerspec 2 supports D0 D1 D2 D3 current D0 > map[10]: type Memory, range 32, base 0xd7eff000, size 12, enabled > pcib3: allocated memory range (0xd7eff000-0xd7efffff) for rid 10 of pci0:5:0:0 > pcib3: matched entry for 5.0.INTA > pcib3: slot 0 INTA hardwired to IRQ 16 > secbus=6, subbus=8 > pcib3: allocated bus range (6-8) for rid 0 of pci0:5:0:0 > found-> vendor=0x1180, dev=0x0822, revid=0x21 > domain=0, bus=5, slot=0, func=2 > class=08-05-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0006, statreg=0x0210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=c, irq=11 > powerspec 2 supports D0 D1 D2 D3 current D0 > map[10]: type Memory, range 32, base 0xd7efec00, size 8, enabled > pcib3: allocated memory range (0xd7efec00-0xd7efecff) for rid 10 of pci0:5:0:2 > pcib3: matched entry for 5.0.INTC > pcib3: slot 0 INTC hardwired to IRQ 18 > cbb0: mem 0xd7eff000-0xd7efffff irq 16 at > device 0.0 on pci5 > cardbus0: on cbb0 > cbb0: allocated bus range (6-6) for rid 0 of cardbus0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: PCI Configuration space: > 0x00: 0x04761180 0x02100007 0x060700ba 0x00822008 > 0x10: 0xd7eff000 0x020000dc 0xb0080605 0xfffff000 > 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc > 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000110 > 0x40: 0x20c617aa 0x00000001 0x00000000 0x00000000 > 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 > 0x80: 0x04a00001 0x00000000 0x04630463 0x00000000 > 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 > 0xa0: 0x00000000 0x09000000 0x00f00000 0x00000005 > 0xb0: 0x00000000 0xb6000000 0x00003000 0x00000000 > 0xc0: 0x20c617aa 0x00000000 0x00000000 0x00000000 > 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 > 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 > 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 > sdhci_pci0: mem 0xd7efec00-0xd7efecff irq 18 at > device 0.2 on pci5 > sdhci_pci0-slot0: 33MHz HS 4bits 3.3V DMA > sdhci_pci0-slot0: ============== REGISTER DUMP ============== > sdhci_pci0-slot0: Sys addr: 0x00000000 | Version: 0x00000400 > sdhci_pci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 > sdhci_pci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000 > sdhci_pci0-slot0: Present: 0x01f20000 | Host ctl: 0x00000000 > sdhci_pci0-slot0: Power: 0x00000000 | Blk gap: 0x00000000 > sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000000 > sdhci_pci0-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 > sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb > sdhci_pci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > sdhci_pci0-slot0: Caps: 0x01e021a1 | Max curr: 0x00000040 > sdhci_pci0-slot0: =========================================== > sdhci_pci0: 1 slot(s) allocated > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18e0-0x18ef at device 31.1 on > pci0 > ata0: at channel 0 on atapci0 > ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 61 > ahci0: port > 0x1c30-0x1c37,0x1c24-0x1c27,0x1c28-0x1c2f,0x1c20-0x1c23,0x1c00-0x1c1f > mem 0xf8426000-0xf84267ff irq 16 at device 31.2 on pci0 > ahci0: attempting to allocate 4 MSI vectors (4 supported) > msi: routing MSI IRQ 259 to local APIC 0 vector 64 > msi: routing MSI IRQ 260 to local APIC 0 vector 65 > msi: routing MSI IRQ 261 to local APIC 0 vector 66 > msi: routing MSI IRQ 262 to local APIC 0 vector 67 > ahci0: using IRQs 259-262 for MSI > ahci0: AHCI v1.10 with 3 3Gbps ports, Port Multiplier not supported > ahci0: Caps: 64bit NCQ SNTF ALP AL CLO 3Gbps PMD SSC PSC 32cmd CCC 3ports > ahcich0: at channel 0 on ahci0 > ahcich0: Caps: > ahcich1: not probed (disabled) > ahcich2: not probed (disabled) > pci0: at device 31.3 (no driver attached) > acpi_tz0: on acpi0 > acpi_tz1: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x54ab (2) > kbd0 at atkbd0 > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 > ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 62 > atkbd0: [GIANT-LOCKED] > psm0: unable to allocate IRQ > psmcpnp0: irq 12 on acpi0 > psm0: current command byte:0047 > psm0: irq 12 on atkbdc0 > ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 63 > psm0: [GIANT-LOCKED] > psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons > psm0: config:00004000, flags:00000008, packet size:3 > psm0: syncmask:c0, syncbits:00 > battery0: on acpi0 > acpi_acad0: on acpi0 > ACPI: Enabled 3 GPEs in block 00 to 1F > acpi0: wakeup code va 0xfffffe0235249000 pa 0x94000 > ex_isa_identify() > ahc_isa_identify 0: ioport 0xc00 alloc failed > ahc_isa_identify 1: ioport 0x1c00 alloc failed > ahc_isa_identify 2: ioport 0x2c00 alloc failed > ahc_isa_identify 3: ioport 0x3c00 alloc failed > ahc_isa_identify 4: ioport 0x4c00 alloc failed > ahc_isa_identify 5: ioport 0x5c00 alloc failed > ahc_isa_identify 6: ioport 0x6c00 alloc failed > ahc_isa_identify 7: ioport 0x7c00 alloc failed > ahc_isa_identify 8: ioport 0x8c00 alloc failed > ahc_isa_identify 9: ioport 0x9c00 alloc failed > ahc_isa_identify 10: ioport 0xac00 alloc failed > ahc_isa_identify 11: ioport 0xbc00 alloc failed > ahc_isa_identify 12: ioport 0xcc00 alloc failed > ahc_isa_identify 13: ioport 0xdc00 alloc failed > ahc_isa_identify 14: ioport 0xec00 alloc failed > pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 > pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 > pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 > pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 > pcib0: allocated type 3 (0xd0000-0xd07ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd0800-0xd0fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd1000-0xd17ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd1800-0xd1fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd2000-0xd27ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd2800-0xd2fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd3000-0xd37ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd3800-0xd3fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd4000-0xd47ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd4800-0xd4fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd5000-0xd57ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd5800-0xd5fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd6000-0xd67ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd6800-0xd6fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd7000-0xd77ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd7800-0xd7fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd8000-0xd87ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd8800-0xd8fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd9000-0xd97ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xd9800-0xd9fff) for rid 1 of orm0 > pcib0: allocated type 3 (0xda000-0xda7ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xda800-0xdafff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdb000-0xdb7ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdb800-0xdbfff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdc000-0xdc7ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdc800-0xdcfff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdd000-0xdd7ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdd800-0xddfff) for rid 1 of orm0 > pcib0: allocated type 3 (0xde000-0xde7ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xde800-0xdefff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdf000-0xdf7ff) for rid 1 of orm0 > pcib0: allocated type 3 (0xdf800-0xdffff) for rid 1 of orm0 > isa_probe_children: disabling PnP devices > atkbdc: atkbdc0 already exists; skipping it > atrtc: atrtc0 already exists; skipping it > attimer: attimer0 already exists; skipping it > sc: sc0 already exists; skipping it > isa_probe_children: probing non-PnP devices > orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 > pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 > pcib0: allocated type 4 (0x3f0-0x3f5) for rid 0 of fdc0 > pcib0: allocated type 4 (0x3f7-0x3f7) for rid 1 of fdc0 > fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > ppc0: cannot reserve I/O port range > ppc0 failed to probe at irq 7 on isa0 > pcib0: allocated type 4 (0x3f8-0x3ff) for rid 0 of uart0 > uart0 failed to probe at port 0x3f8-0x3ff irq 4 on isa0 > pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 > uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 > wbwd0 failed to probe on isa0 > isa_probe_children: probing PnP devices > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > p4tcc1: on cpu1 > Device configuration finished. > procfs registered > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Timecounters tick every 1.000 msec > vlan: initialized, using hash tables with chaining > tcp_init: net.inet.tcp.tcbhashsize auto tuned to 65536 > lo0: bpf attached > hptnr: no controller detected. > hpt27xx: no controller detected. > hptrr: no controller detected. > hdac0: Command timeout on address 1 > hdac0: Command timeout on address 1 > hdac0: CODEC is not responding! > hdacc0: at cad 0 on hdac0 > hdaa0: at nid 1 on hdacc0 > hdaa0: Subsystem ID: 0x17aa20d6 > hdaa0: NumGPIO=3 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 > hdaa0: GPIO0: disabled > hdaa0: GPIO1: input state=0 > hdaa0: GPIO2: disabled > hdaa0: WARNING: nid=2 has cnid outside of the AFG range j=0 entnum=4 > index=0 res=0x00090801 > hdaa0: Original pins configuration: > hdaa0: nid 0x as seq device conn jack loc color misc > hdaa0: 17 0421401f 1 15 Headphones Jack 1/8 Right Green 0 > hdaa0: 18 90170110 1 0 Speaker Fixed Analog Internal Unknown 1 > hdaa0: 19 511301f0 15 0 Speaker None ATAPI 0x11 Unknown 1 > hdaa0: 20 04a15021 2 1 Mic Jack 1/8 Right Red 0 > hdaa0: 21 90a7012e 2 14 Mic Fixed Analog Internal Unknown 1 > hdaa0: 22 593301f0 15 0 CD None ATAPI Onboard Unknown 1 > hdaa0: 23 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 > hdaa0: 24 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 > hdaa0: 26 91f311f0 15 0 Other Fixed ATAPI 0x11 Black 1 > hdaa0: 27 614411f0 15 0 SPDIF-out None RCA Ext-Rear Black 1 > hdaa0: 28 21a15020 2 0 Mic Jack 1/8 Ext-Rear Red 0 > hdaa0: Patching widget caps nid=26 0x00400000 -> 0x00700000 > hdaa0: Patched pins configuration: > hdaa0: nid 0x as seq device conn jack loc color misc > hdaa0: 17 0421401f 1 15 Headphones Jack 1/8 Right Green 0 > hdaa0: 18 90170110 1 0 Speaker Fixed Analog Internal Unknown 1 > hdaa0: 19 511301f0 15 0 Speaker None ATAPI 0x11 Unknown 1 DISA > hdaa0: 20 04a15021 2 1 Mic Jack 1/8 Right Red 0 > hdaa0: 21 90a7012e 2 14 Mic Fixed Analog Internal Unknown 1 > hdaa0: 22 593301f0 15 0 CD None ATAPI Onboard Unknown 1 DISA > hdaa0: 23 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 DISA > hdaa0: 24 55a601f0 15 0 Mic None Digital 0x15 Unknown 1 DISA > hdaa0: 27 614411f0 15 0 SPDIF-out None RCA Ext-Rear Black 1 DISA > hdaa0: 28 21a15020 2 0 Mic Jack 1/8 Ext-Rear Red 0 > hdaa0: 2 associations found: > hdaa0: Association 0 (1) out: > hdaa0: Pin nid=18 seq=0 > hdaa0: Pin nid=17 seq=15 > hdaa0: Association 1 (2) in: > hdaa0: Pin nid=28 seq=0 > hdaa0: Pin nid=20 seq=1 > hdaa0: Pin nid=21 seq=14 > hdaa0: Tracing association 0 (1) > hdaa0: Pin 18 traced to DAC 4 > hdaa0: Pin 17 traced to DAC 4 and hpredir 0 > hdaa0: Association 0 (1) trace succeeded > hdaa0: Tracing association 1 (2) > hdaa0: Unable to trace pin 28 to ADC 5, undo traces > hdaa0: Unable to trace pin 28 to ADC 6, undo traces > hdaa0: Pin 28 traced to ADC 8 > hdaa0: Pin 20 traced to ADC 8 > hdaa0: Pin 21 traced to ADC 8 > hdaa0: Association 1 (2) trace succeeded > hdaa0: Looking for additional DAC for association 0 (1) > hdaa0: Looking for additional ADC for association 1 (2) > hdaa0: ADC 9 considered equal to ADC 8 > hdaa0: Tracing input monitor > hdaa0: Tracing nid 32 to out > hdaa0: nid 32 is input monitor > hdaa0: Tracing other input monitors > hdaa0: Tracing nid 20 to out > hdaa0: Tracing nid 21 to out > hdaa0: Tracing nid 28 to out > hdaa0: Tracing beeper > hdaa0: Headphones redirection for association 0 nid=17 using > unsolicited responses. > hdaa0: Redirect output to: main > hdaa0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref > pcm0: at nid 18,17 and > 28,20,21 on hdaa0 > pcm0: Playback: > pcm0: Stream cap: 0x00000001 PCM > pcm0: PCM cap: 0x000e07ff 16 20 24 bits, 8 11 16 22 32 44 48 > 88 96 176 192 KHz > pcm0: DAC: 4 > pcm0: > pcm0: nid=18 [pin: Speaker (Fixed)] > pcm0: + <- nid=10 [audio mixer] [src: pcm, mix] > pcm0: + <- nid=4 [audio output] [src: pcm] > pcm0: + <- nid=33 [audio selector] [src: mix] > pcm0: + <- nid=32 [audio mixer] [src: mix] > pcm0: > pcm0: nid=17 [pin: Headphones (Green Jack)] > pcm0: + <- nid=7 [audio mixer] [src: pcm, mix] > pcm0: + <- nid=34 [audio selector] [src: pcm] > pcm0: + <- nid=4 [audio output] [src: pcm] > pcm0: + <- nid=33 [audio selector] [src: mix] > pcm0: + <- nid=32 [audio mixer] [src: mix] > pcm0: > pcm0: Record: > pcm0: Stream cap: 0x00000001 PCM > pcm0: PCM cap: 0x000e07ff 16 20 24 bits, 8 11 16 22 32 44 48 > 88 96 176 192 KHz > pcm0: ADC: 8 > pcm0: ADC: 9 > pcm0: > pcm0: nid=8 [audio input] > pcm0: + <- nid=12 [audio selector] [src: line, mic, mix, monitor] > pcm0: + <- nid=20 [pin: Mic (Red Jack)] [src: mic] > pcm0: + <- nid=21 [pin: Mic (Fixed)] [src: monitor] > pcm0: + <- nid=32 [audio mixer] [src: mix] > pcm0: + <- nid=37 [audio selector] [src: line] > pcm0: + <- nid=28 [pin: Mic (Red Jack)] [src: line] > pcm0: > pcm0: nid=9 [audio input] > pcm0: + <- nid=13 [audio selector] [src: line, mic, mix, monitor] > pcm0: + <- nid=20 [pin: Mic (Red Jack)] [src: mic] > pcm0: + <- nid=21 [pin: Mic (Fixed)] [src: monitor] > pcm0: + <- nid=32 [audio mixer] [src: mix] > pcm0: + <- nid=37 [audio selector] [src: line] > pcm0: + <- nid=28 [pin: Mic (Red Jack)] [src: line] > pcm0: > pcm0: Input Mix: > pcm0: > pcm0: nid=32 [audio mixer] > pcm0: + <- nid=20 [pin: Mic (Red Jack)] [src: mic] > pcm0: + <- nid=21 [pin: Mic (Fixed)] [src: monitor] > pcm0: + <- nid=26 [beep widget] [src: speaker] > pcm0: + <- nid=37 [audio selector] [src: line] > pcm0: + <- nid=28 [pin: Mic (Red Jack)] [src: line] > pcm0: > pcm0: Master Volume (OSS: vol): -58/0dB > pcm0: +- ctl 2 (nid 4 out): -58/0dB (40 steps) > pcm0: +- ctl 5 (nid 7 in 0): mute > pcm0: +- ctl 6 (nid 7 in 1): mute > pcm0: +- ctl 7 (nid 10 in 0): mute > pcm0: +- ctl 8 (nid 10 in 1): mute > pcm0: +- ctl 14 (nid 17 in ): mute > pcm0: +- ctl 15 (nid 18 in ): mute > pcm0: > pcm0: PCM Volume (OSS: pcm): -58/0dB > pcm0: +- ctl 2 (nid 4 out): -58/0dB (40 steps) > pcm0: +- ctl 5 (nid 7 in 0): mute > pcm0: +- ctl 7 (nid 10 in 0): mute > pcm0: > pcm0: Microphone Volume (OSS: mic): 0/30dB > pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 17 (nid 20 out): 0/30dB (4 steps) > pcm0: +- ctl 24 (nid 32 in 0): -34/12dB (32 steps) + mute > pcm0: > pcm0: Microphone2 Volume (OSS: monitor): 0/30dB > pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 18 (nid 21 out): 0/30dB (4 steps) > pcm0: +- ctl 25 (nid 32 in 1): -34/12dB (32 steps) + mute > pcm0: > pcm0: Line-in Volume (OSS: line): 0/30dB > pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 28 (nid 32 in 4): -34/12dB (32 steps) + mute > pcm0: +- ctl 32 (nid 37 out): 0/30dB (4 steps) > pcm0: > pcm0: Speaker/Beep Volume (OSS: speaker): -34/0dB > pcm0: +- ctl 13 (nid 16 out): -45/0dB (16 steps) + mute > pcm0: +- ctl 27 (nid 32 in 3): -34/12dB (32 steps) + mute > pcm0: > pcm0: Recording Level (OSS: rec): -58/22dB > pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute > pcm0: > pcm0: Input Mix Level (OSS: mix): -46/0dB > pcm0: +- ctl 6 (nid 7 in 1): mute > pcm0: +- ctl 8 (nid 10 in 1): mute > pcm0: +- ctl 11 (nid 12 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 12 (nid 13 out): -58/22dB (55 steps) + mute > pcm0: +- ctl 29 (nid 33 out): -46/0dB (32 steps) + mute > pcm0: > pcm0: Input Monitoring Level (OSS: igain): 0/0dB > pcm0: +- ctl 6 (nid 7 in 1): mute > pcm0: +- ctl 8 (nid 10 in 1): mute > pcm0: > pcm0: Mixer "vol": > pcm0: Mixer "pcm": > pcm0: Mixer "speaker": > pcm0: Mixer "line": > pcm0: Mixer "mic": > pcm0: Mixer "mix": > pcm0: Mixer "rec": > pcm0: Mixer "igain": > pcm0: Mixer "ogain": > pcm0: Mixer "monitor": > pcm0: Playback channel set is: Front Left, Front Right, > pcm0: Playback channel matrix is: 2.0 (unknown) > pcm0: Automatically set rec source to: monitor > pcm0: Recording channel set is: Front Left, Front Right, > pcm0: Recording channel matrix is: 2.0 (unknown) > random: unblocking device. > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > usbus2: 480Mbps High Speed USB v2.0 > usbus3: 12Mbps Full Speed USB v1.0 > usbus4: 12Mbps Full Speed USB v1.0 > usbus5: 480Mbps High Speed USB v2.0 > ata0: reset tp1 mask=03 ostat0=7f ostat1=7f > ugen0.1: at usbus0 > uhub0: on usbus0 > ugen3.1: at usbus3 > uhub1: on usbus3 > ugen2.1: at usbus2 > uhub2: on usbus2 > ugen1.1: at usbus1 > uhub3: on usbus1 > ugen5.1: at usbus5 > uhub4: on usbus5 > ugen4.1: at usbus4 > uhub5: on usbus4 > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > uhub0: 2 ports with 2 removable, self powered > uhub1: 2 ports with 2 removable, self powered > uhub3: 2 ports with 2 removable, self powered > uhub5: 2 ports with 2 removable, self powered > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of pci0:6:0:0 > unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 > cbb0: Opening memory: > cbb0: Normal: 0xd4000000-0xd400ffff > cardbus0: Expecting link target, got 0xff > cbb0: Opening memory: > pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of pci0:6:0:0 > unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 > cbb0: Opening memory: > cbb0: Normal: 0xd4000000-0xd400ffff > cardbus0: Expecting link target, got 0xff > cbb0: Opening memory: > found-> vendor=0x168c, dev=0x0013, revid=0x01 > domain=0, bus=6, slot=0, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0002, statreg=0x8210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) > intpin=a, irq=16 > powerspec 2 supports D0 D3 current D0 > ath0: irq 16 at device 0.0 on cardbus0 > pcib3: allocated memory range (0xd4000000-0xd400ffff) for rid 10 of ath0 > ath0: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0xd4000000 > cbb0: Opening memory: > cbb0: Normal: 0xd4000000-0xd400ffff > ath0: unable to attach hardware; HAL status 14 > cbb0: Opening memory: > device_attach: ath0 attach returned 6 > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: stat1=0x7f err=0x7f lsb=0x7f msb=0x7f > ata0: reset tp2 stat0=ff stat1=ff devices=0x0 > ahcich0: AHCI reset... > ahcich0: SATA connect time=100us status=00000123 > ahcich0: AHCI reset: device found > battery0: battery initialization start > acpi_acad0: acline initialization start > battery0: battery initialization done, tried 1 times > acpi_acad0: On Line > acpi_acad0: acline initialization done, tried 1 times > ahcich0: AHCI reset: device ready after 100ms > pass0 at ahcich0 bus 0 scbus1 target 0 lun 0 > pass0: ATA-8 SATA 2.x device > pass0: Serial Number OCZ-0350VO37893A086L > pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > pass0: Command Queueing enabled > ada0 at ahcich0 bus 0 scbus1 target 0 lun 0 > GEOM: new disk ada0 > ada0: ATA-8 SATA 2.x device > ada0: Serial Number OCZ-0350VO37893A086L > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C) > ada0: quirks=0x1<4K> > ada0: Previously was known as ad4 > Netvsc initializing... done! > SMP: AP CPU #1 Launched! > cpu1 AP: > ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000100ef therm: 0x00010200 err: 0x000000f0 pmc: 0x00010400 > ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 > ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 1 vector 49 > ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 1 vector 50 > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 1 vector 51 > ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 1 vector 52 > msi: Assigning MSI IRQ 256 to local APIC 1 vector 53 > msi: Assigning MSI IRQ 258 to local APIC 1 vector 54 > TSC timecounter disabled: C3 enabled. > Timecounter "TSC" frequency 1596037768 Hz quality -1000 > WARNING: WITNESS option enabled, expect reduced performance. > Root mount waiting for: usbus5 usbus2 > uhub4: 4 ports with 4 removable, self powered > uhub2: 4 ports with 4 removable, self powered > Trying to mount root from zfs:zroot/ROOT/default []... > start_init: trying /sbin/init > ugen0.2: at usbus0 From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 22:12:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EDFFC6; Wed, 23 Apr 2014 22:12:04 +0000 (UTC) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 02FF61DFD; Wed, 23 Apr 2014 22:12:03 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id wn1so1753142obc.4 for ; Wed, 23 Apr 2014 15:12:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FoIDcsxItx5TK8kwjMWPLL2kcPwbea6SMkDcSWLDdjc=; b=alOoZdqZhhAuJtKlnvxzFLxA32ul1GLcUlUToaA/yRpoLshJAwIqcyLRKiTkexj0Jh nAzBHHDEAvtDOUjuM19V8wPBSpVKnj04OnSU67Q/yLikZvsjzczNR1DXHX5LzejaxmVt XcfvpkyacuG2AOWFsYJaLsYJ1av4dKqVeXfppsFhHstCBgVfcUyizRhdO5Scm9FQYIA8 UQFCTmCHSQW9UZD+X1bXPvZwuzyU9twVpwrIzFooI/tR91um8dTW2hrJz7XnxHZGCIAz vkLcfcK6A8JurbdMKPGswikrMowC3amh2CjRUl6jcqMhKvEVjDqxmVotigkxFCsIw6pQ TV1A== MIME-Version: 1.0 X-Received: by 10.182.40.201 with SMTP id z9mr15352863obk.45.1398291123291; Wed, 23 Apr 2014 15:12:03 -0700 (PDT) Received: by 10.76.87.73 with HTTP; Wed, 23 Apr 2014 15:12:03 -0700 (PDT) In-Reply-To: References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> <4F8604C1.4090902@gmail.com> <4F861C10.5020503@gmail.com> Date: Wed, 23 Apr 2014 23:12:03 +0100 Message-ID: Subject: Re: ath(4) fails to attach From: "Sevan / Venture37" 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.17 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 Apr 2014 22:12:04 -0000 On 23 April 2014 23:08, Adrian Chadd wrote: > It's failing the selftest (error 14 is ESELFTEST.) > > > -a Indicating hardware failure? Sevan From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 22:15:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0BA324A for ; Wed, 23 Apr 2014 22:15:37 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 655581E53 for ; Wed, 23 Apr 2014 22:15:37 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id c9so1628401qcz.5 for ; Wed, 23 Apr 2014 15:15:36 -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=EVnxiPi1rba+Hcjk+mUEhlY/7WH8rYxRKBxdjE7WCpo=; b=XewKZuPdyZkINc9oJ/XZU+No63J2blX5424TxDlhQTnNfVx8q6cnD207pWQ+p5gvti S6S7sLeMwlTKOEgiZ6W8l2bxkmQS2n74io3YKZ26r5nhoRufl1lY7D4ECC5vTmZd/+2W cAK2wEu+hHSdX6rCaOlXwtuqHTI6WgSQEtSQ07jZx7NSB6PcvUWYMw6jwbQA9bpDG+1H bFTcsvV48RE0o/oefZQHNI7uOamu1BZspYqdfAL1dsy9P4lp1dtTR5iGoorSw3XThIbK iRtqE8y6DR14VfNwULsXUWHs0V+krVHQg05fwFR4OShsVw0f6NxrK0GXgVXCZ6Cd0HmC BEYg== MIME-Version: 1.0 X-Received: by 10.224.129.66 with SMTP id n2mr24395302qas.55.1398291336578; Wed, 23 Apr 2014 15:15:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 23 Apr 2014 15:15:36 -0700 (PDT) In-Reply-To: References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> <4F8604C1.4090902@gmail.com> <4F861C10.5020503@gmail.com> Date: Wed, 23 Apr 2014 15:15:36 -0700 X-Google-Sender-Auth: FeaH-o6S1f01R8nSBT55kaZdc7w Message-ID: Subject: Re: ath(4) fails to attach From: Adrian Chadd To: "Sevan / Venture37" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 22:15:37 -0000 That, or the wrong addresses are mapped to the hardware. -a On 23 April 2014 15:12, Sevan / Venture37 wrote: > On 23 April 2014 23:08, Adrian Chadd wrote: >> It's failing the selftest (error 14 is ESELFTEST.) >> >> >> -a > > Indicating hardware failure? > > > Sevan From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 24 02:38:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40E68F39 for ; Thu, 24 Apr 2014 02:38:09 +0000 (UTC) Received: from nm35-vm5.bullet.mail.bf1.yahoo.com (nm35-vm5.bullet.mail.bf1.yahoo.com [72.30.238.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E36361745 for ; Thu, 24 Apr 2014 02:38:08 +0000 (UTC) Received: from [66.196.81.174] by nm35.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 02:35:46 -0000 Received: from [98.139.212.196] by tm20.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 02:35:46 -0000 Received: from [127.0.0.1] by omp1005.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 02:35:46 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 283650.82585.bm@omp1005.mail.bf1.yahoo.com Received: (qmail 89865 invoked by uid 60001); 24 Apr 2014 02:35:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1398306946; bh=tDWvXGXNGbaDrrPsZSC8gcNrDmB7hj1/6q++XxIV5fg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6U/nVGn7YkgJr8IOEGmzYqbTMA77e2eXGPifXmw3bgiyTWrMTtzn0WcGOm0Ep4ONyYpcK688t1TTwxmxPdEbl0LhZkqQ4m8saedb/bYK1253BDiGTV1HOMmxa3FN/j1M1mh+J5R58ZNSrcXKfBA2pcIikFWTDXl3o8i1QE5oh2Y= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=blStpAjorM5R6SivTHIoFW+SOtSUhUQw6H6VAMnnFyQ6/eQk2pXo4AeU3KpF9IItaVly2SaSR7jLIMdYI5UjGV2Cjx2PYNfPADkFpaXEkmU3jXw2aklX/Vn2GIGrlL16isBDirNEY0EIy0Q8mnT1rmeG4nYbaaymg+d+gPHCpEM=; X-YMail-OSG: yaV0OqIVM1m5kJyxjlZ0_VDz7_ZRbuKoTQIz.dVzwwDCJPy D7XXZlCFP3H557q_A4JHVUYx8GIU762K0TxXX6.Q6TyAd7NGpeVeEsNAPvTM hwX9fYjlbfbygiT8Sn0GbCYcsuDhFp3B2uIBNxRAefyyOPOVcaXpUrS0UBg5 RGEX_oq58wUbTtkZXXNMMyU7NeBPdrmUvJ.RXwBf0lHI.X4Ds2g9i7Rb59WX sSjc0UA6Q1e9HJraPmfQvVAAGEM8uXjTQcOi0oMUbCIRbyHY5k_xko_sCxK7 _5QSeOEcnWYGjdvIq4MPnlZNJGZ3CNo3pPi89jH61BqLz.F.JIbR0jINJLpU HnSak669dOf7bVxe4BDDOBM60EdUuvJkApnJhx2DFoxNgYLYOGGeED7Kxoxe U4qFg_6GAgipT17wvj8uAy46Z3cLzT7d.Y9u23MMEAkOgzIWeHVnzzIZwmlu TWTJmMzuya120ISGkP2.nBPuFBRVqIXtzuNPAB4OEjHtrwCcO.lMnf5slSPY pB350BkjPOxpm61MvkXzqiEKLpWjIDeTBmac_xP6jSTkiIDDyfnhcHwew4vt 0MtVJcXIaFImjeFQXfOKODW3x8Vh0mMwcqQx.2QhuYh4- Received: from [99.62.101.19] by web140706.mail.bf1.yahoo.com via HTTP; Wed, 23 Apr 2014 19:35:46 PDT X-Rocket-MIMEInfo: 002.001, VGhhbmtzIGZvciByZXBseSwgSnVsaWFuLsKgIFllcyBpdCBpcyB0aW55LCBJIGhhZG4ndCBjb25zaWRlcmVkIHRoZXJtYWwgaXNzdWVzLsKgIEl0cyBzaXplIGlzIHdoeSBJIGxpa2UgdGhlIHRoaW5nLCB2ZXJ5IHVub2J0cnVzaXZlIGluIG15IGxhcHRvcCAod2hpbGUgSSB0cnkgZGVidWdnaW5nIHRoZSBBUjk1NjUgcHJvYmxlbXMgSSdtIGhhdmluZykuwqAgSSdsbCBnaXZlIHRoZSBkb25nbGUgaWRlYSBhIHdoaXJsLCBhbHNvIHRyeSBpdCBpbiBteSBkZXNrdG9wIGRvd25zdGFpcnMgKGFsc28gcnVubmluZyABMAEBAQE- X-Mailer: YahooMailWebService/0.8.185.657 References: <5357C439.4040101@yahoo.com> <201404232038.s3NKcP2X054576@fire.js.berklix.net> Message-ID: <1398306946.28300.YahooMailNeo@web140706.mail.bf1.yahoo.com> Date: Wed, 23 Apr 2014 19:35:46 -0700 (PDT) From: Anthony Jenkins Subject: Re: urtwn panic To: "Julian H. Stacey" In-Reply-To: <201404232038.s3NKcP2X054576@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Anthony Jenkins 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 Apr 2014 02:38:09 -0000 Thanks for reply, Julian.=A0 Yes it is tiny, I hadn't considered thermal is= sues.=A0 Its size is why I like the thing, very unobtrusive in my laptop (w= hile I try debugging the AR9565 problems I'm having).=A0 I'll give the dong= le idea a whirl, also try it in my desktop downstairs (also running a decen= tly recent kernel).=0A=0A=0ASoooo possibly nothing to the whole sleeping-wh= ile-holding-a-lock thing? :-)=0A=0A=0AThanks,=0A=0AAnthony=0A=0A___________= _____________________=0AFrom: Julian H. Stacey =0ATo: Anth= ony Jenkins =0ACc: freebsd-wireless@freebsd.org =0AS= ent: Wednesday, April 23, 2014 4:38 PM=0ASubject: Re: urtwn panic=0A=0A=0AA= nthony Jenkins wrote:=0A> I'm getting a panic with the latest kernel (r2647= 19) and the if_urtwn driver.=0A=0AMight the urtwn device overheat, not retu= rn & cause a panic ?=0AMy urtwn device is very small, no thermal path to du= mp heat.=A0 I've=0Anot tried on current, but on 10.0-RELEASE I saw my urtwn= 0 interface=0Adisappearing; I read parts of the driver; & noticed there's m= ention=0Aof a temperature level, I didn't tweak it, but hung my device on a= =0AUSB extension cable at 10 C outside the window, & later in front=0Aof a = chassis input fan at ~ 20 C room temp., I think both locations=0Alasted lon= ger or perhaps indefinately without urtwn0 , can't remember,=0AI suspended = pursuing it.=A0 Device picture for those who don't know=0Ahow small this, &= other URLs via: http://www.berklix.com/~jhs/hardware/urtwn/=0A=0ACheers,= =0AJulian=0A-- =0AJulian Stacey, BSD Unix Linux C Sys Eng Consultant, Munic= h http://berklix.com=0AInterleave replies below like a play script.=A0 Inde= nt old text with "> ".=0A=A0=A0=A0 Google breach privacy http://berklix.com= /jhs/adverts/=0A_______________________________________________=0Afreebsd-w= ireless@freebsd.org mailing list=0Ahttp://lists.freebsd.org/mailman/listinf= o/freebsd-wireless=0ATo unsubscribe, send any mail to "freebsd-wireless-uns= ubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 24 02:51:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42727E1 for ; Thu, 24 Apr 2014 02:51:32 +0000 (UTC) Received: from nm12-vm0.bullet.mail.bf1.yahoo.com (nm12-vm0.bullet.mail.bf1.yahoo.com [98.139.213.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6B991834 for ; Thu, 24 Apr 2014 02:51:31 +0000 (UTC) Received: from [98.139.215.143] by nm12.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 02:51:30 -0000 Received: from [98.139.212.212] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 02:51:30 -0000 Received: from [127.0.0.1] by omp1021.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 02:51:30 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 22903.6123.bm@omp1021.mail.bf1.yahoo.com Received: (qmail 2450 invoked by uid 60001); 24 Apr 2014 02:51:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1398307889; bh=DbPWQ1gQzYbDWzKHxQh+ix9dNkwDZjee9w7+LgC8BuA=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=kauiCDrI9AfhE9sXDxaFhy3sJML6AzCcNuFYgm59+bW5oZz6kZW9+9j6r8VyxLOR7Dk63jXJIeZ9RpsdDMxB7C/8mF5x8mikrTiTaXOvrJnOgM6WacZ8TGV2nkSi708D6soVeLQTSy4QRIuIsWjBMc2pt/yDAxJRy8YUWT9Jm8s= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=WVsZHw78AF02ZmG+l1CXqyCP0haESsRt18P6FMre4+tuabz8Y7SDUGNDaMFPbGDyOyTClXrSjkjXn16LvYuXt8iGBxPaaq6mQpaxkWlZ6a2C5K7e6aRQBODeVIGqY/R20HXo5JYH3BeJ9R9Vmib0cdx65qvCzRlYVffWFNPtDj4=; X-YMail-OSG: 64TY.WwVM1kqTt4JSdPicS1d1.JNRkYueEnUlw3LOnOk8pb ysUwZIB6N0pAtXiouMovFBPieEE1ndJHdPrhPtS1u5QfWDM1BE4xSRP.HM6t UF5fHLT_2mMu_7Yklnn_FN8RqfmTpFYxgSNSK5mxP777XoccKVdgZL1FKrOf 30K8pUbQIS8NbLdD9_g21SY6c35kEC_yn28TOeUTn4UBlTt.qKjzqMzmD_no r7_vMeLIVAlfhMIyYoPu2CA62PRw5qcY1wM_lR7d59xjwOL6sD42lhG11uds oHNoZQ6CStmp70jtLunygnke9qunF._UhUkFQ3crVLSgBfPBD2m9QHm56o0P fkJ.CHXye6BDLDUuCChnpkxhMNK3y_UpNwAceBlKP2NnxAqyEvKBg7pQefVr qahI3xyTGZ_xhsCIT96vyi_IL_qhzeiFDNYmdJiefNN4_Frd7ERrOWeIYJc8 WRvhE2SCuIIZAf6HJ.Ff1mMADGVHRoOp6GTgEskoAP6c4jIPlpqoxL8AHBcY 1CkcjyYuhHzq7CGoInppGh8pZOa8hcsr8pQcMeVHD6NbTOEmY Received: from [99.62.101.19] by web140702.mail.bf1.yahoo.com via HTTP; Wed, 23 Apr 2014 19:51:29 PDT X-Rocket-MIMEInfo: 002.001, CgoKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRnJvbTogS2V2aW4gTG8gPGtldmxvQEZyZWVCU0Qub3JnPgpUbzogQW50aG9ueSBKZW5raW5zIDxTY29vYmlfZG9vQHlhaG9vLmNvbT4gClNlbnQ6IFdlZG5lc2RheSwgQXByaWwgMjMsIDIwMTQgMTA6MjggUE0KU3ViamVjdDogUmU6IHVydHduIHBhbmljCgoKQW50aG9ueSBKZW5raW5zIHdyb3RlOgoKPiBJJ20gZ2V0dGluZyBhIHBhbmljIHdpdGggdGhlIGxhdGVzdCBrZXJuZWwgKHIyNjQ3MTkpIGFuZCB0aGUgaWZfdXJ0d24gCj4gZHJpdmUBMAEBAQE- X-Mailer: YahooMailWebService/0.8.185.657 References: <53550B59.6020103@yahoo.com> <535876D1.3020001@FreeBSD.org> Message-ID: <1398307889.10841.YahooMailNeo@web140702.mail.bf1.yahoo.com> Date: Wed, 23 Apr 2014 19:51:29 -0700 (PDT) From: Anthony Jenkins Subject: Re: urtwn panic To: Kevin Lo In-Reply-To: <535876D1.3020001@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-589800495-1293293886-1398307889=:10841" Cc: Freebsd-wireless X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Anthony Jenkins 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 Apr 2014 02:51:32 -0000 ---589800495-1293293886-1398307889=:10841 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A=0A=0A________________________________=0AFrom: Kevin Lo =0ATo: Anthony Jenkins =0ASent: Wednesda= y, April 23, 2014 10:28 PM=0ASubject: Re: urtwn panic=0A=0A=0AAnthony Jenki= ns wrote:=0A=0A> I'm getting a panic with the latest kernel (r264719) and t= he if_urtwn =0A> driver.=A0 I have a coredump available to triage.=0A=0ACou= ld you try attached patch? Thanks.=0A=0A=0A=A0 =A0=A0=A0Kevin=0A=0ANice, se= veral insertions/extractions and no panics!=0A=0AUnfortunately the !@#$& do= ngle's so small I just now managed to separate the device from the metal sl= eeve...grrr.=A0 Should be able to fix tho, and it's still functional.=0A=0A= =0AMany thanks!=0AAnthony=0A ---589800495-1293293886-1398307889=:10841 Content-Type: application/octet-stream; name=patch-urtwn Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=patch-urtwn SW5kZXg6IHN5cy9kZXYvdXNiL3dsYW4vaWZfdXJ0d24uYwo9PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09Ci0tLSBzeXMvZGV2L3VzYi93bGFuL2lmX3VydHduLmMJ KHJldmlzaW9uIDI2NDg1NSkKKysrIHN5cy9kZXYvdXNiL3dsYW4vaWZfdXJ0 d24uYwkod29ya2luZyBjb3B5KQpAQCAtMjA1NCw2ICsyMDU0LDcgQEAgdXJ0 d25fbG9hZF9maXJtd2FyZShzdHJ1Y3QgdXJ0d25fc29mdGMgKnNjKQogCXVp bnQzMl90IHJlZzsKIAlpbnQgbWxlbiwgbnRyaWVzLCBwYWdlLCBlcnJvcjsK IAorCVVSVFdOX1VOTE9DSyhzYyk7CiAJLyogUmVhZCBmaXJtd2FyZSBpbWFn ZSBmcm9tIHRoZSBmaWxlc3lzdGVtLiAqLwogCWlmICgoc2MtPmNoaXAgJiAo VVJUV05fQ0hJUF9VTUNfQV9DVVQgfCBVUlRXTl9DSElQXzkyQykpID09CiAJ ICAgIFVSVFdOX0NISVBfVU1DX0FfQ1VUKQpAQCAtMjA2Miw2ICsyMDYzLDcg QEAgdXJ0d25fbG9hZF9maXJtd2FyZShzdHJ1Y3QgdXJ0d25fc29mdGMgKnNj KQogCQlpbWFnZW5hbWUgPSAidXJ0d24tcnRsODE5MmNmd1QiOwogCiAJZncg PSBmaXJtd2FyZV9nZXQoaW1hZ2VuYW1lKTsKKwlVUlRXTl9MT0NLKHNjKTsK IAlpZiAoZncgPT0gTlVMTCkgewogCQlkZXZpY2VfcHJpbnRmKHNjLT5zY19k ZXYsCiAJCSAgICAiZmFpbGVkIGxvYWRmaXJtd2FyZSBvZiBmaWxlICVzXG4i LCBpbWFnZW5hbWUpOwpAQCAtMjgxNiw2ICsyODE4LDggQEAgdXJ0d25faW5p dF9sb2NrZWQodm9pZCAqYXJnKQogCXVpbnQzMl90IHJlZzsKIAlpbnQgZXJy b3I7CiAKKwlVUlRXTl9BU1NFUlRfTE9DS0VEKHNjKTsKKwogCWlmIChpZnAt PmlmX2Rydl9mbGFncyAmIElGRl9EUlZfUlVOTklORykKIAkJdXJ0d25fc3Rv cF9sb2NrZWQoaWZwKTsKIApAQCAtMjk3OSw2ICsyOTgzLDggQEAgdXJ0d25f c3RvcF9sb2NrZWQoc3RydWN0IGlmbmV0ICppZnApCiB7CiAJc3RydWN0IHVy dHduX3NvZnRjICpzYyA9IGlmcC0+aWZfc29mdGM7CiAKKwlVUlRXTl9BU1NF UlRfTE9DS0VEKHNjKTsKKwogCWlmcC0+aWZfZHJ2X2ZsYWdzICY9IH4oSUZG X0RSVl9SVU5OSU5HIHwgSUZGX0RSVl9PQUNUSVZFKTsKIAogCWNhbGxvdXRf c3RvcCgmc2MtPnNjX3dhdGNoZG9nX2NoKTsK ---589800495-1293293886-1398307889=:10841-- From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 24 03:21:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 781A35C6 for ; Thu, 24 Apr 2014 03:21:49 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F3FC1BFE for ; Thu, 24 Apr 2014 03:21:48 +0000 (UTC) Received: from [127.0.0.1] (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s3O3LgeU025006; Thu, 24 Apr 2014 11:21:42 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <53588348.6020408@FreeBSD.org> Date: Thu, 24 Apr 2014 11:21:44 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Anthony Jenkins Subject: Re: urtwn panic References: <53550B59.6020103@yahoo.com> <535876D1.3020001@FreeBSD.org> <1398307889.10841.YahooMailNeo@web140702.mail.bf1.yahoo.com> In-Reply-To: <1398307889.10841.YahooMailNeo@web140702.mail.bf1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Freebsd-wireless X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 03:21:49 -0000 Anthony Jenkins wrote: > > > > > > ________________________________ > From: Kevin Lo > To: Anthony Jenkins > Sent: Wednesday, April 23, 2014 10:28 PM > Subject: Re: urtwn panic > > > Anthony Jenkins wrote: > >> I'm getting a panic with the latest kernel (r264719) and the if_urtwn >> driver. I have a coredump available to triage. > Could you try attached patch? Thanks. > > > Kevin > > Nice, several insertions/extractions and no panics! Cool! Fixed in *r264864, thanks. *** > > Unfortunately the !@#$& dongle's so small I just now managed to separate the device from the metal sleeve...grrr. Should be able to fix tho, and it's still functional. > > > Many thanks! > Anthony Kevin From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 24 05:48:44 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B857CE5 for ; Thu, 24 Apr 2014 05:48:44 +0000 (UTC) Received: from nm11.bullet.mail.ne1.yahoo.com (nm11.bullet.mail.ne1.yahoo.com [98.138.90.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF5BA18C1 for ; Thu, 24 Apr 2014 05:48:43 +0000 (UTC) Received: from [98.138.100.113] by nm11.bullet.mail.ne1.yahoo.com with NNFMP; 24 Apr 2014 05:47:01 -0000 Received: from [98.138.104.116] by tm104.bullet.mail.ne1.yahoo.com with NNFMP; 24 Apr 2014 05:47:01 -0000 Received: from [127.0.0.1] by smtp225.mail.ne1.yahoo.com with NNFMP; 24 Apr 2014 05:47:01 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1398318421; bh=/n1H9v6YtRM43sXaj1ps+S75/SuR9gkd+l4tCX1GIYo=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:Subject; b=jb0HLU4i0vNX6/Yxw+3eVKkK4QyKjVVkT/WXse3EGoB8Vi6732YpOhxAvUP0nejpY4Nan5BoMIhQfGWqMZuCnEOFO4QXcVIapWSNAzhYxiry+826aHVXUa6dRTC3s+82BjO/6/eSqDWoA3kphqxaawC+jbq8nqAS5Q5pjkRH0nE= X-Yahoo-Newman-Id: 392176.6965.bm@smtp225.mail.ne1.yahoo.com Message-ID: <392176.6965.bm@smtp225.mail.ne1.yahoo.com> Date: Thu, 24 Apr 2014 05:47:01 +0000 (UTC) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: hIvsTjAVM1kkFH4MaSmqRZKD45C_rDMJ8unWzOjrXj9yr.I azdJy8kYAW7lbJlO1v.SdCvMirn6C_Kk2kkgBsoo14dLSDPtP7LiBP5s1fVp PBZMGrBVVySPOrKeSRXiz3ZbKqS0pCb4AomytzoxKgVQt_UWhiS.fqUqO7mA u10DfJSVkXZOVf6own_WDD85dtQNn6VmMmAfj.OxCDan_jyBJf6fs.V.3pfG 8EVl9wEmmDDTisMWRXNSrAv8RJdW4O8nUGTWv8IJztnfdWgqVofvjt4UmOXX U_dvLPpn7A35PntFrmXNYhipQf8Vy72Tv9TM2rNnjQyu48ydtj8a9.h_CEBI NsN1Iqq9duDKeHXPtZ6Tf7.DNd_.KdWL_tPA.giKbm_EXb3PRU924Bo_4ifB T.Re2WtFHLnWHY6B5CMgYmOFrz6lwbwKGeax37rlNXodWapZbI3WHsWNatfc 9gqhzv2w3suGQxQVSjc7awQw7JvVUoH9vVivR7uAvQJrPneRprHlQA6GmWec _dkblpV6UiFu0N4EUrVgc X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.138.105.24]) by smtp225.mail.ne1.yahoo.com with SMTP; 24 Apr 2014 05:47:01 +0000 UTC From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: rsu0: could not send site survey command 0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 05:48:44 -0000 What is the meaning of this message? I find my wireless connection has gone down and get that message on ttyv1, making that console unusable, at least temporarily. I logged in on another root console and typed ifconfig wlan0 down and that seems to have stopped the ill message. Not good enough, I had to type ifconfig wlan0 destroy before starting up again, which I was able to do; svn update of ports appeared successful. But I am still curious about the meaning of that message. WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. Tom From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 24 16:51:31 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59AE04A4 for ; Thu, 24 Apr 2014 16:51:31 +0000 (UTC) Received: from mail-ie0-x242.google.com (mail-ie0-x242.google.com [IPv6:2607:f8b0:4001:c03::242]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BC21132B for ; Thu, 24 Apr 2014 16:51:31 +0000 (UTC) Received: by mail-ie0-f194.google.com with SMTP id to1so625122ieb.5 for ; Thu, 24 Apr 2014 09:51:30 -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=k2YOLUzQonZs+r+cZkC99VjXJcYVR72JwVgF5rgdI40=; b=hVw9i9Wll3w9paMMVU5z04M4XQBfmFfkl+XOMzIeQ/bVvT1lO3omu8K4JCDqZ0mmaR pTOR3fN2TTb+6/GO/jm1/qrKvg/HNisbeIzhdIADqp3IW1c32w7wXkG3W3JV82dE1/57 3r5b6nEfFXc8SWwhPAnBRrAIhcj/QO3HjNZzN9F8i9ZYZdbfZqxcgYoQAWMgsqkCewRT nrQMso70Uq6xXM6txJ3JnXIwz5X/qkX7mtOUU2uRxMjdaW+FsJ1MkVCYvR/cWAwWL4jS eKB1uZ95JLpORcB5Bz9+yy4Tz5HG3YL1lnCy14N2ZzUF+bx80TmXevkdCkFdrBsuh1Kk 5Wgg== MIME-Version: 1.0 X-Received: by 10.50.13.100 with SMTP id g4mr10902001igc.9.1398358290660; Thu, 24 Apr 2014 09:51:30 -0700 (PDT) Received: by 10.42.145.72 with HTTP; Thu, 24 Apr 2014 09:51:30 -0700 (PDT) Date: Thu, 24 Apr 2014 13:51:30 -0300 Message-ID: Subject: Urtwn module and Realteck RTL8188CE support. From: Thiago F To: freebsd-wireless@FreeBSD.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 16:51:31 -0000 Is RTL8188CE already supported by urtwn or other FreeBSD's module ? There is a way to get this device to work on FreeBSD ? From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 25 01:26:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1D4AD7E1 for ; Fri, 25 Apr 2014 01:26:02 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5A7D1871 for ; Fri, 25 Apr 2014 01:26:01 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id i8so3350731qcq.37 for ; Thu, 24 Apr 2014 18:26:01 -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=bnPYAKfS4MYIduhVDcYXwdVjsuL9GdmGt2F1s935eD0=; b=eFu786f3oGnOgCFan/VExJ13lA0vPeTp48KFydO73lx6yBjXQnXrbiXT1BKunBT9LS qlTYjd8NtaBIZtFUUCdaHt5TkyAVbpmhMlBsUg/6RaUoAZPgx0hVmEbNdOpWadhHMIwN uSIoxm2ZKFtUm2xoJlKmBBFH8cjbQs0ZVWaqWFCbr4jTPCw8VR2lwWmlxaITklnuhNIM NXSNmb6w49efI6IDwgGNQ5EAPmnpGIqpOBDYRWLmUXCR8oI0VbQUI3thWZmtSYiwCTTh Q+P9yFHZK3TIYz1pnhhuNLk5M12b2knylMfctFeVxnQHyXz8/DZpAQPb4u1oN7Q+y9BI qPNw== MIME-Version: 1.0 X-Received: by 10.224.47.130 with SMTP id n2mr7805994qaf.26.1398389161083; Thu, 24 Apr 2014 18:26:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Thu, 24 Apr 2014 18:26:01 -0700 (PDT) Date: Thu, 24 Apr 2014 18:26:01 -0700 X-Google-Sender-Auth: AvE8sy0lvgnH7NkmDcaDUJPc6ko Message-ID: Subject: [rfc] station mode powersave for ath(4) From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 01:26:02 -0000 Hi, This is close to my final first cut of this station mode powersave stuff for the atheros hardware. Combined with the net80211 changes that are now in HEAD, the driver can be put into network sleep in order to conserve power and only wake up when it needs to. http://people.freebsd.org/~adrian/ath/20140424-net80211-ath-sleep-11.diff Now, this is the first cut. It works on the AR5211, AR5212, AR5416. I haven't tested it on the AR9160, AR9280 and later hardware (but I will before I commit it.) It isn't going to support the aggressive power save stuff yet (like uapsd and ps-poll.) It just puts the NIC into network-sleep if there's been no active transmit work for 500ms. It also puts the NIC to sleep if all the VAPs are down. It also isn't on by default - you need to add 'powersave' to the ifconfig create line. It does save up to a couple of watts of power at idle, so it's worthwhile to start testing. I would however like some wider testing. Please have ATH_DEBUG and AH_DEBUG defined before using this. -a From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 25 06:21:11 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FFEC90B for ; Fri, 25 Apr 2014 06:21:11 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CF27613D5 for ; Fri, 25 Apr 2014 06:21:09 +0000 (UTC) Received: from srg.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s3P6Kv0E034657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 25 Apr 2014 14:21:00 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <5359FECE.4070604@FreeBSD.org> Date: Fri, 25 Apr 2014 14:21:02 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Thiago F Subject: Re: Urtwn module and Realteck RTL8188CE support. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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 Apr 2014 06:21:11 -0000 On 2014/04/25 00:51, Thiago F wrote: > Is RTL8188CE already supported by urtwn or other FreeBSD's module ? Sorry, RTL8188CE is not supported yet. > There is a way to get this device to work on FreeBSD ? Try ndis(4). It may work for you. Kevin From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 28 11:06:57 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3FB33623 for ; Mon, 28 Apr 2014 11:06:57 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 123BE1ABB for ; Mon, 28 Apr 2014 11:06:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3SB6uF5086327 for ; Mon, 28 Apr 2014 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3SB6ubt086324 for freebsd-wireless@FreeBSD.org; Mon, 28 Apr 2014 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Apr 2014 11:06:56 GMT Message-Id: <201404281106.s3SB6ubt086324@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.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2014 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/188654 wireless [urtwn] tp-link wl-725n Realtek 8188 chip do not work o kern/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o bin/187624 wireless [patch] wpa_supplicant(8): WEP and other ciphers do no o bin/187470 wireless [bthidd] [patch] Apple Wireless Keyboard (JIS) o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] [panic] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP fails, WPA o kern/185025 wireless [iwi] [panic] iwi driver panic on 10.0rc2 f usb/184918 wireless [ural] regression on WEP o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181694 wireless [iwn] [suspend/resume] [patch] Initialize hardware in o kern/181161 wireless [wl] [panic] config a old compaq wl-110 wireless card 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/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/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/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/168754 wireless [ath] if_ath dont have internal name o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless [ath] [suspend/resume] 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/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] kernel panic: page fault with ath0 taskq 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 195 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 29 06:28:40 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA9225C6; Tue, 29 Apr 2014 06:28:40 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (elam.kais.kyoto-u.ac.jp [130.54.60.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F3801791; Tue, 29 Apr 2014 06:28:40 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (localhost [127.0.0.1]) by elam.kais.kyoto-u.ac.jp (8.14.8/8.14.8) with ESMTP id s3T65mSD075499; Tue, 29 Apr 2014 15:05:48 +0900 (JST) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) From: Kaho Toshikazu To: Adrian Chadd Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> X-Mailer: MH-E 8.0.3; MH 6.8.4.JP-3.05; GNU Emacs 22.3.1 User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?G?= =?ISO-8859-4?Q?oj=F2?=) APEL/10.8 Emacs/22.3 (i386-portbld-freebsd8.4) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Date: Tue, 29 Apr 2014 15:05:48 +0900 Message-ID: <75498.1398751548@elam.kais.kyoto-u.ac.jp> Sender: kaho@elam.kais.kyoto-u.ac.jp X-Virus-Scanned: clamav-milter 0.98.1 at elam.kais.kyoto-u.ac.jp X-Virus-Status: Clean Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 06:28:40 -0000 Hello, sorry for too delay reply. During a holiday week in Japan, I traced changes of if_iwn. r258030 broke and its problem were willing to be coverd by r258085, then slightly modified r258034 with changes from r258035 to r258085 can operate normally. r258035 introduced some program structure changes and some breakages. I cannot chase what is incorrect in r258035. -- kaho@elam.kais.kyoto-u.ac.jp > Date: Thu, 27 Feb 2014 19:40:26 -0800 > Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in > -HEAD supporting Centrino Wireless-N 135) > From: Adrian Chadd > > Hi, > > Yes there are issues; I'm too busy to try and chase them down. > > I'd appreciate some help in chasing down why things are unhappy. > > Thanks, > > > -a > > > > On 27 February 2014 17:17, Kaho Toshikazu wrote: > > Hello, -current members > > > > I have a similar problem with Centrino Wireless-N 1000. > > It operated until r257951 and have a trouble after r258030. > > I use r262433 kernel with sys/dev/iwn reverted to r257951 > > and changed from IEEE80211_FC1_WEP to EEE80211_FC1_PROTECTED. > > > > r262422 if_iwn module with IWN_DEBUG in opt_iwn.h and dev.iwn.0.debug=1 says: > > > > -- output of `dmesg -a` -- > > iwn0: mem 0xd2500000-0xd2501fff irq 19 at device 0.0 on pci2 > > wlan0: Ethernet address: 00:1e:64:45:f5:64 > > iwn0: iwn_setregdomain: invalid channel 8 freq 2447/0x20480 > > iwn_notif_intr: scanning channel 1 status 1 > > iwn_notif_intr: scanning channel 6 status 1 > > iwn_notif_intr: scanning channel 11 status 1 > > iwn_notif_intr: scanning channel 7 status 1 > > iwn_notif_intr: scanning channel 13 status 1 > > iwn_notif_intr: scanning channel 2 status 1 > > iwn_notif_intr: scanning channel 3 status 1 > > iwn_notif_intr: scanning channel 4 status 1 > > iwn_notif_intr: scanning channel 5 status 1 > > iwn_notif_intr: scanning channel 8 status 1 > > iwn_notif_intr: scanning channel 9 status 1 > > iwn_notif_intr: scanning channel 10 status 1 > > iwn_notif_intr: scanning channel 12 status 1 > > iwn_tx_data_raw: qid 3 idx 0 len 6 nsegs 1 > > iwn5000_tx_done: qid 3 idx 0 retries 0 nkill 0 rate 420a duration 778 status 201 > > iwn_tx_data_raw: qid 3 idx 1 len 86 nsegs 1 > > iwn5000_tx_done: qid 3 idx 1 retries 0 nkill 0 rate 420a duration 1418 status 201 > > iwn_set_link_quality: 1stream antenna=0x01, 2stream antenna=0x03, ntxstreams=1 > > iwn_set_link_quality: i=0, txrate=7, rate=0x87 > > iwn_set_link_quality: i=1, txrate=6, rate=0x86 > > iwn_set_link_quality: i=2, txrate=5, rate=0x85 > > iwn_set_link_quality: i=3, txrate=4, rate=0x84 > > iwn_set_link_quality: i=4, txrate=3, rate=0x83 > > iwn_set_link_quality: i=5, txrate=2, rate=0x82 > > iwn_set_link_quality: i=6, txrate=1, rate=0x81 > > iwn_set_link_quality: i=7, txrate=0, rate=0x80 > > iwn_set_link_quality: i=8, txrate=0, rate=0x80 > > iwn_set_link_quality: i=9, txrate=0, rate=0x80 > > iwn_set_link_quality: i=10, txrate=0, rate=0x80 > > iwn_set_link_quality: i=11, txrate=0, rate=0x80 > > iwn_set_link_quality: i=12, txrate=0, rate=0x80 > > iwn_set_link_quality: i=13, txrate=0, rate=0x80 > > iwn_set_link_quality: i=14, txrate=0, rate=0x80 > > iwn_set_link_quality: i=15, txrate=0, rate=0x80 > > wlan0: link state changed to UP > > iwn0: iwn_intr: fatal firmware error > > firmware error log: > > error type = "SYSASSERT" (0x00000005) > > program counter = 0x00018DBC > > source line = 0x00000032 > > error data = 0x0000000100000000 > > branch link = 0x00018D6E00018D6E > > interrupt link = 0x0000082600000000 > > time = 1043083265 > > driver status: > > tx ring 0: qid=0 cur=0 queued=0 > > tx ring 1: qid=1 cur=0 queued=0 > > tx ring 2: qid=2 cur=0 queued=0 > > tx ring 3: qid=3 cur=2 queued=0 > > tx ring 4: qid=4 cur=57 queued=0 > > tx ring 5: qid=5 cur=0 queued=0 > > tx ring 6: qid=6 cur=0 queued=0 > > tx ring 7: qid=7 cur=0 queued=0 > > tx ring 8: qid=8 cur=0 queued=0 > > tx ring 9: qid=9 cur=0 queued=0 > > tx ring 10: qid=10 cur=0 queued=0 > > tx ring 11: qid=11 cur=0 queued=0 > > tx ring 12: qid=12 cur=0 queued=0 > > tx ring 13: qid=13 cur=0 queued=0 > > tx ring 14: qid=14 cur=0 queued=0 > > tx ring 15: qid=15 cur=0 queued=0 > > tx ring 16: qid=16 cur=0 queued=0 > > tx ring 17: qid=17 cur=0 queued=0 > > tx ring 18: qid=18 cur=0 queued=0 > > tx ring 19: qid=19 cur=0 queued=0 > > rx ring: cur=55 > > > > -- output of `pciconf -lvcb` -- > > iwn0@pci0:2:0:0: class=0x028000 card=0x13058086 chip=0x00838086 rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Centrino Wireless-N 1000 [Condor Peak]' > > class = network > > bar [10] = type Memory, range 64, base 0xd2500000, size 8192, enabled > > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR link x1(x1) > > speed 2.5(2.5) ASPM L1(L0s/L1) > > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 3 corrected > > ecap 0003[140] = Serial 1 001e64ffff45f564 > > > > -- > > Kaho Toshikazu From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 29 19:28:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 065A111B for ; Tue, 29 Apr 2014 19:27:59 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFF4510D5 for ; Tue, 29 Apr 2014 19:27:59 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id x13so778897qcv.35 for ; Tue, 29 Apr 2014 12:27:58 -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=ZUGad+OKPoAAzCT7Qp8GCibr0LhoC92+ZY2yjXiGkJY=; b=a22WQfKExto+pRtuHF1O4i+9+Nu+Z8E9QEkxaGHd0qWwP3PxkdbZEzLubEiQNj6O+K 9egvSD9mqbz0UY523NX/COW1R7H9xevECU8V57PNRB8WtK6PiDJugCifLjIKZMgLp4et b3BfHHHQT6rP1VGI6ySfpSBFagKbhCO/oVBMRw9aCId9o4DOecGKukyzL5r6rRZu1/Fz hocIcaStCVHx45EOBeGs1J/yvd6JkHnnji6ZWU3ta/sRdWrFMJ96l50M6O7rLP6+OjUh 8x6sDWS2hRtyMtID5e7Qe7GZONgAnMNckG/tQcSIL0cLCzaGf2aM+tfu39fOuMiXPaoU LgRw== MIME-Version: 1.0 X-Received: by 10.224.38.138 with SMTP id b10mr14754805qae.98.1398799678127; Tue, 29 Apr 2014 12:27:58 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 29 Apr 2014 12:27:58 -0700 (PDT) In-Reply-To: <75498.1398751548@elam.kais.kyoto-u.ac.jp> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> Date: Tue, 29 Apr 2014 12:27:58 -0700 X-Google-Sender-Auth: eHzOyYVxcEctM_jSZRKUK16jWxY Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 19:28:00 -0000 Hi! Would you mind clarifying what you wrote a little more? What I'm reading this as: * If I grab an r258030 tree, it's broken on your NIC * If I then do what, apply r258034, it works? * If I apply 258035 -> 258085, it also works? I really would appreciate it if you would re-state what you've written so I/we can better understand :-) Something like: * Revision X, doesn't work * Revision X with revisions A, B and then C applied, does work * Revision X with A, B and C applied, and a modified revision D applied, does work (and attach the modified revision D) That way I/we can clearly reproduce what you've done. :-) Thanks! -a On 28 April 2014 23:05, Kaho Toshikazu wrote: > Hello, sorry for too delay reply. > > During a holiday week in Japan, I traced changes of if_iwn. > > r258030 broke and its problem were willing to be coverd by r258085, > then slightly modified r258034 with changes from r258035 to r258085 > can operate normally. > > r258035 introduced some program structure changes and some breakages. > I cannot chase what is incorrect in r258035. > > -- > kaho@elam.kais.kyoto-u.ac.jp > >> Date: Thu, 27 Feb 2014 19:40:26 -0800 >> Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in >> -HEAD supporting Centrino Wireless-N 135) >> From: Adrian Chadd >> >> Hi, >> >> Yes there are issues; I'm too busy to try and chase them down. >> >> I'd appreciate some help in chasing down why things are unhappy. >> >> Thanks, >> >> >> -a >> >> >> >> On 27 February 2014 17:17, Kaho Toshikazu wrote: >> > Hello, -current members >> > >> > I have a similar problem with Centrino Wireless-N 1000. >> > It operated until r257951 and have a trouble after r258030. >> > I use r262433 kernel with sys/dev/iwn reverted to r257951 >> > and changed from IEEE80211_FC1_WEP to EEE80211_FC1_PROTECTED. >> > >> > r262422 if_iwn module with IWN_DEBUG in opt_iwn.h and dev.iwn.0.debug=1 says: >> > >> > -- output of `dmesg -a` -- >> > iwn0: mem 0xd2500000-0xd2501fff irq 19 at device 0.0 on pci2 >> > wlan0: Ethernet address: 00:1e:64:45:f5:64 >> > iwn0: iwn_setregdomain: invalid channel 8 freq 2447/0x20480 >> > iwn_notif_intr: scanning channel 1 status 1 >> > iwn_notif_intr: scanning channel 6 status 1 >> > iwn_notif_intr: scanning channel 11 status 1 >> > iwn_notif_intr: scanning channel 7 status 1 >> > iwn_notif_intr: scanning channel 13 status 1 >> > iwn_notif_intr: scanning channel 2 status 1 >> > iwn_notif_intr: scanning channel 3 status 1 >> > iwn_notif_intr: scanning channel 4 status 1 >> > iwn_notif_intr: scanning channel 5 status 1 >> > iwn_notif_intr: scanning channel 8 status 1 >> > iwn_notif_intr: scanning channel 9 status 1 >> > iwn_notif_intr: scanning channel 10 status 1 >> > iwn_notif_intr: scanning channel 12 status 1 >> > iwn_tx_data_raw: qid 3 idx 0 len 6 nsegs 1 >> > iwn5000_tx_done: qid 3 idx 0 retries 0 nkill 0 rate 420a duration 778 status 201 >> > iwn_tx_data_raw: qid 3 idx 1 len 86 nsegs 1 >> > iwn5000_tx_done: qid 3 idx 1 retries 0 nkill 0 rate 420a duration 1418 status 201 >> > iwn_set_link_quality: 1stream antenna=0x01, 2stream antenna=0x03, ntxstreams=1 >> > iwn_set_link_quality: i=0, txrate=7, rate=0x87 >> > iwn_set_link_quality: i=1, txrate=6, rate=0x86 >> > iwn_set_link_quality: i=2, txrate=5, rate=0x85 >> > iwn_set_link_quality: i=3, txrate=4, rate=0x84 >> > iwn_set_link_quality: i=4, txrate=3, rate=0x83 >> > iwn_set_link_quality: i=5, txrate=2, rate=0x82 >> > iwn_set_link_quality: i=6, txrate=1, rate=0x81 >> > iwn_set_link_quality: i=7, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=8, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=9, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=10, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=11, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=12, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=13, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=14, txrate=0, rate=0x80 >> > iwn_set_link_quality: i=15, txrate=0, rate=0x80 >> > wlan0: link state changed to UP >> > iwn0: iwn_intr: fatal firmware error >> > firmware error log: >> > error type = "SYSASSERT" (0x00000005) >> > program counter = 0x00018DBC >> > source line = 0x00000032 >> > error data = 0x0000000100000000 >> > branch link = 0x00018D6E00018D6E >> > interrupt link = 0x0000082600000000 >> > time = 1043083265 >> > driver status: >> > tx ring 0: qid=0 cur=0 queued=0 >> > tx ring 1: qid=1 cur=0 queued=0 >> > tx ring 2: qid=2 cur=0 queued=0 >> > tx ring 3: qid=3 cur=2 queued=0 >> > tx ring 4: qid=4 cur=57 queued=0 >> > tx ring 5: qid=5 cur=0 queued=0 >> > tx ring 6: qid=6 cur=0 queued=0 >> > tx ring 7: qid=7 cur=0 queued=0 >> > tx ring 8: qid=8 cur=0 queued=0 >> > tx ring 9: qid=9 cur=0 queued=0 >> > tx ring 10: qid=10 cur=0 queued=0 >> > tx ring 11: qid=11 cur=0 queued=0 >> > tx ring 12: qid=12 cur=0 queued=0 >> > tx ring 13: qid=13 cur=0 queued=0 >> > tx ring 14: qid=14 cur=0 queued=0 >> > tx ring 15: qid=15 cur=0 queued=0 >> > tx ring 16: qid=16 cur=0 queued=0 >> > tx ring 17: qid=17 cur=0 queued=0 >> > tx ring 18: qid=18 cur=0 queued=0 >> > tx ring 19: qid=19 cur=0 queued=0 >> > rx ring: cur=55 >> > >> > -- output of `pciconf -lvcb` -- >> > iwn0@pci0:2:0:0: class=0x028000 card=0x13058086 chip=0x00838086 rev=0x00 hdr=0x00 >> > vendor = 'Intel Corporation' >> > device = 'Centrino Wireless-N 1000 [Condor Peak]' >> > class = network >> > bar [10] = type Memory, range 64, base 0xd2500000, size 8192, enabled >> > cap 01[c8] = powerspec 3 supports D0 D3 current D0 >> > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR link x1(x1) >> > speed 2.5(2.5) ASPM L1(L0s/L1) >> > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 3 corrected >> > ecap 0003[140] = Serial 1 001e64ffff45f564 >> > >> > -- >> > Kaho Toshikazu > > > > From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 29 19:37:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47A4E215 for ; Tue, 29 Apr 2014 19:37:19 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03B681193 for ; Tue, 29 Apr 2014 19:37:18 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id i17so43103qcy.11 for ; Tue, 29 Apr 2014 12:37:18 -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=FxqUzgjAbuBdrRc+7UxvrZWU/+7JEPRKo0+HKPlwT88=; b=mweMzEZSDhdeTwVJLNR4PYKRwbZ2nQkPM0Rzcai04D/zu56eR4M7N5MWgcpHBvJu8Q Xj5xXLPOvps0yYWdIAl1gvJFJsSiCv+qDxq+VrriTeVie8J/MF4CvnI0ez1Iz03u6dyr l7Ol/TQld9JgSKwtKnSFFOpL2YvkHUoXvh7J9qzHyY9Z4mAwfoauCy+JXP0CONPd9gVW SEGG50GXU5xNOS1283pA4IujxWVDp22Phf5LqPACEQmQenC34KZNnUGexDOBoVzuqRtQ 32qOP7H3RwPHm0FFvNQk5mzViNqxwDGvc5usuNOurDHTXRtJ8G5gHnKUIIgKUBGikF6k Yifw== MIME-Version: 1.0 X-Received: by 10.224.38.138 with SMTP id b10mr14814536qae.98.1398800238036; Tue, 29 Apr 2014 12:37:18 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 29 Apr 2014 12:37:17 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> Date: Tue, 29 Apr 2014 12:37:17 -0700 X-Google-Sender-Auth: _JgnYkEZhPp5V_nlSaxD4lyleFg Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 19:37:19 -0000 Hi, Ok. So r258030 changed the antenna configuration for transmitting to use the tx chainmask from the EEPROM settings,r ather than hard-coding it to IWN_ANT_AB. This is needed because a bunch of NICs actually don't have two antennas and if you feed it IWN_ANT_AB it just plainly doesn't work. So, if you try -HEAD, but you set antmask_2stream to be IWN_ANT_AB, does it fix the problem? Ie, add this line linkq.antmsk_2stream = IWN_ANT_AB; .. just after this line: linkq.ampdu_limit = htole16(4000); Thanks, -a From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 30 00:53:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B95A7FE; Wed, 30 Apr 2014 00:53:48 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (elam.kais.kyoto-u.ac.jp [130.54.60.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D7D9102A; Wed, 30 Apr 2014 00:53:47 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (localhost [127.0.0.1]) by elam.kais.kyoto-u.ac.jp (8.14.8/8.14.8) with ESMTP id s3U0rjuG084651; Wed, 30 Apr 2014 09:53:45 +0900 (JST) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) To: Adrian Chadd Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> X-Mailer: MH-E 8.0.3; MH 6.8.4.JP-3.05; GNU Emacs 22.3.1 User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?G?= =?ISO-8859-4?Q?oj=F2?=) APEL/10.8 Emacs/22.3 (i386-portbld-freebsd8.4) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Date: Wed, 30 Apr 2014 09:53:45 +0900 Message-ID: <84650.1398819225@elam.kais.kyoto-u.ac.jp> From: Kaho Toshikazu X-Virus-Scanned: clamav-milter 0.98.1 at elam.kais.kyoto-u.ac.jp X-Virus-Status: Clean Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2014 00:53:48 -0000 Hello, thank you for your reply. > Would you mind clarifying what you wrote a little more? > What I'm reading this as: > > * If I grab an r258030 tree, it's broken on your NIC > * If I then do what, apply r258034, it works? > * If I apply 258035 -> 258085, it also works? > > I really would appreciate it if you would re-state what you've written > so I/we can better understand :-) > > Something like: > > * Revision X, doesn't work > * Revision X with revisions A, B and then C applied, does work > * Revision X with A, B and C applied, and a modified revision D > applied, does work (and attach the modified revision D) > > That way I/we can clearly reproduce what you've done. :-) > > Thanks! I'm sorry for my ambiguous representation. Until Revision 257951, work. =46rom r258030 to r258034, doesn't work. If antmask_2stream set to be IWN_ANT_AB, work. After r258035, doesn't work. antmask_2stream =3D IWN_ANT_AB doesn't help. > Ok. So r258030 changed the antenna configuration for transmitting to > use the tx chainmask from the EEPROM settings,r ather than hard-coding > it to IWN_ANT_AB. This is needed because a bunch of NICs actually > don't have two antennas and if you feed it IWN_ANT_AB it just plainly > doesn't work. > > So, if you try -HEAD, but you set antmask_2stream to be IWN_ANT_AB, > does it fix the problem? > > Ie, add this line > > linkq.antmsk_2stream =3D IWN_ANT_AB; > > .. just after this line: > > linkq.ampdu_limit =3D htole16(4000); Yes, it fix the problem until r258034, but doesn't fix after r258035. Rivision 258035 changed many lines and if_iwn_chip_cfg.h was created. I faced a trouble about where should I try to change. --=20 Kaho Toshikazu From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 30 00:54:28 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A02FC117 for ; Wed, 30 Apr 2014 00:54:28 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A7581038 for ; Wed, 30 Apr 2014 00:54:28 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id z60so1113448qgd.24 for ; Tue, 29 Apr 2014 17:54:27 -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=vxC231fzRHyjGqJKN/tG2aZtQjVhuMW83kB65HzydTY=; b=AwTYs5KgEXNqwBakZ0AXpw5wzH+a2e2FTeTgcmOyvsZzwJdPmxujKA+peODNM/Q8Km hJWJJv9vxTHxHl/++6no8t5eiEjW56rGvH4atFf5N+JtHd0YxC7WVz5gcIZQit8YNHIa TKgB/A+Yn6zZ4PKglMn6phGa6djOzIN9YXqmNuYgkqWi4iupo26S7hGkPbIaYAKT8oWF lc0itzUrD+FHUKTJip3QqaQUCOkJiKvqntvvMgKnaEW8V5gjl2JHRMXtEXkfg5uIlvbP IJVshNA7U5UoqwWXKSi3qqjiDIf5XlNblcy1lw6cawWzHT4EmuiKpTXhcNmgflFDKDAc vL7Q== MIME-Version: 1.0 X-Received: by 10.224.38.138 with SMTP id b10mr1253242qae.98.1398819267468; Tue, 29 Apr 2014 17:54:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 29 Apr 2014 17:54:27 -0700 (PDT) In-Reply-To: <84650.1398819225@elam.kais.kyoto-u.ac.jp> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> Date: Tue, 29 Apr 2014 17:54:27 -0700 X-Google-Sender-Auth: yQLWu8wR1fpxvRu9SfS9qyYQ-Xc Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2014 00:54:28 -0000 Ok, this is much, much clearer. I'll go look at r258035, which is the new chip config stuff. -a On 29 April 2014 17:53, Kaho Toshikazu wrote: > Hello, thank you for your reply. > >> Would you mind clarifying what you wrote a little more? >> What I'm reading this as: >> >> * If I grab an r258030 tree, it's broken on your NIC >> * If I then do what, apply r258034, it works? >> * If I apply 258035 -> 258085, it also works? >> >> I really would appreciate it if you would re-state what you've written >> so I/we can better understand :-) >> >> Something like: >> >> * Revision X, doesn't work >> * Revision X with revisions A, B and then C applied, does work >> * Revision X with A, B and C applied, and a modified revision D >> applied, does work (and attach the modified revision D) >> >> That way I/we can clearly reproduce what you've done. :-) >> >> Thanks! > > I'm sorry for my ambiguous representation. > > Until Revision 257951, work. > > From r258030 to r258034, doesn't work. If antmask_2stream set to > be IWN_ANT_AB, work. > > After r258035, doesn't work. antmask_2stream = IWN_ANT_AB doesn't help. > >> Ok. So r258030 changed the antenna configuration for transmitting to >> use the tx chainmask from the EEPROM settings,r ather than hard-coding >> it to IWN_ANT_AB. This is needed because a bunch of NICs actually >> don't have two antennas and if you feed it IWN_ANT_AB it just plainly >> doesn't work. >> >> So, if you try -HEAD, but you set antmask_2stream to be IWN_ANT_AB, >> does it fix the problem? >> >> Ie, add this line >> >> linkq.antmsk_2stream = IWN_ANT_AB; >> >> .. just after this line: >> >> linkq.ampdu_limit = htole16(4000); > > Yes, it fix the problem until r258034, but doesn't fix after r258035. > Rivision 258035 changed many lines and if_iwn_chip_cfg.h was created. > I faced a trouble about where should I try to change. > > -- > Kaho Toshikazu From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 30 17:16:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4420D4AF; Wed, 30 Apr 2014 17:16:04 +0000 (UTC) Received: from mail0.byshenk.net (portland1.byshenk.net [69.168.54.16]) by mx1.freebsd.org (Postfix) with ESMTP id 29BEF1AEB; Wed, 30 Apr 2014 17:16:03 +0000 (UTC) Received: by mail0.byshenk.net (Postfix, from userid 1002) id EC08422CE3; Wed, 30 Apr 2014 10:07:40 -0700 (PDT) Date: Wed, 30 Apr 2014 10:07:40 -0700 From: Greg Byshenk To: Adrian Chadd Subject: Re: svn commit: r264710 - head/sys/dev/ath Message-ID: <20140430170740.GA5964@mail0.byshenk.net> References: <201404210205.s3L25p9U064240@svn.freebsd.org> <20140421155853.GD1602@mail0.byshenk.net> <20140422005950.GE1602@mail0.byshenk.net> <20140422182107.GF1602@mail0.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140422182107.GF1602@mail0.byshenk.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2014 17:16:04 -0000 On Tue, Apr 22, 2014 at 11:21:07AM -0700, Greg Byshenk wrote: > On Tue, Apr 22, 2014 at 11:04:55AM -0700, Adrian Chadd wrote: > > > Try setting it up without 11n enabled: > > > > ifconfig wlan0 create wlandev ath0 wlanmode hostap channel 6:g > > > > .. and if that doesn't help, try with 11n enabled but without ampdutx: > > > > ifconfig wlan0 -ampdutx > > > > I'm not using the AR5416 as an AP at the moment but it should be ok. > > I'm definitely using it as a station though. > > > > Can your try -HEAD instead? I don't plan on MFCing things myself back > > to stable/10; i rely on others who are actively using stable/10 to do > > it. > > I did try it to 11g (as I know that 11n wasn't supported before), > but it didn't help. > > I did -not- try without ampdutx. I can try that, and I can also > try HEAD --- but that will take a little bit of time, as I will > need to do some reconfiguring of other things to ensure that my > systems are up and available while I'm testing. > > I'll let you know when I have a chance to test. Just to update this for the record: my problem appears to have been a false alarm. Under heavy load yesterday, the same thing happened under 9-STABLE as I reported under 10-STABLE. My suspicion now is that the power supply is failing (or something similar) and it was just my testing under 10-STABLE that was pushing it too hard. -- greg byshenk - gbyshenk@byshenk.net - Portland, OR USA From owner-freebsd-wireless@FreeBSD.ORG Thu May 1 06:19:33 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA1DB178 for ; Thu, 1 May 2014 06:19:32 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACED611D3 for ; Thu, 1 May 2014 06:19:32 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id s7so2622438qap.37 for ; Wed, 30 Apr 2014 23:19:31 -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=qOLifPnGWm+9kVSUHZtMGlbHKNpT16O/75xilfJ6/XY=; b=xakA+m4llZBELgvM1Y571QIlLP3nM2wLJc6+2tXG2uKFH+EoGjTzvEoTBnh2ohY6Qz pNfUzi1/T5652yNWPGjRzFvC38NYr9laN//NoUePMq4GrmtL9oF7d5EL3oeQZUJqFfRT EIA/rvQt4TOIfsVDJZ+v2D8Y486I0N60CTpZnJplmjFUknaFEGy8DuPIJeI59VFGd3H0 KdNDtIQWmGHEvibva1f/oG5k4FHNra4nCU6H8kWpH6wpYrVQ/QVQn4HfWKigrYs0BTNY Fl+WEwbjY81NCSKHmxYeJ/YBQBofxCva0lPrwlzR5FlghzsF0JrvepdJFJLCJG8hfHKH eiKw== MIME-Version: 1.0 X-Received: by 10.224.47.130 with SMTP id n2mr11450650qaf.26.1398925171846; Wed, 30 Apr 2014 23:19:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 30 Apr 2014 23:19:31 -0700 (PDT) Date: Wed, 30 Apr 2014 23:19:31 -0700 X-Google-Sender-Auth: e0sxcaFZ5oWSis6BfydJ1cw86zo Message-ID: Subject: [ath] basic STA powersave for atheros devices is in -HEAD, be warned! From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 01 May 2014 06:19:33 -0000 TL;DR: I've just committed basic STA mode powersave support to Freebsd-HEAD. If you add 'powersave' to your ifconfig wlan0 clone line, the NIC will dip in and out of chip sleep state if the link is idle. Don't do this without IEEE80211_DEBUG, ATH_DEBUG and AH_DEBUG or you won't be able to debug it. Works for me. YMMV. The long version. I've been working on basic chipset powersave support in station mode on and off for the last three weeks or so. It's nowhere near complete or what I would even begin to call correct. It however is a required step towards well, all the correct stuff. The chipset sleep stuff lets the chip drift into powersave if it isn't currently actively doing transmit or receive. It wakes up for beacons; it stays awake if there's multicast traffic to receive or anything to transmit. The driver now wakes up and sleeps based on what net80211 tells it to do. It's the same highly inefficient sleep management from circa 2002 or so, but it's better than no sleep management. However, the thing is, 802.11 powersave as it's implemented is .. tricksy. There's a bit in the 802.11 header (PWRMGT) that when set to 1 tells the recipient that it's actually asleep, and to buffer frames until the transmitter is awake. When PWRMGT is set to 0, the recipient now knows the transmitter is awake and buffered frames can be transmitted. So the only way this can work is if everything happens in the right order. Ie, if we're going to sleep, we need to: * pause transmitting anything other than the NULL "I'm going to sleep" data frame; * finish transmitting what we're transmitting; * once everything is transmitted, transition the NIC from power save to network sleep; * transmit the NULL data frame that says we're asleep; * any further frames transmitted need to be marked with PWRMGT=1 so the peer stays asleep. Then, the wakeup is the opposite: transition the VAP to awake, send a data frame with PWRGMT=0, and everything subsequent to that should be transmitted with PWRGMT=0. However, none of this is currently going on. The net80211 stack just transitions things to and from sleep state, but there's currently nothing that implements all that buffering, pausing, resuming and such. So it's quite possible that: * data frames are going out with PWRMGT=0; * the VAP transitions to SLEEP; * the NULL data frame goes out to tell the receiver that the transmitter is asleep; * .. then some other concurrently sending frames go out with PWRMGT=0. .. then the station think it's asleep; the hardware is asleep and not receiving things, but the AP or other peer decides the station is awake and sends it data. Which isn't received. Sigh. So, I'm not going to fix all of that just yet. I wanted to debug the hardware side of things. The NIC gets extremely upset if it's put to sleep and then programmed in any way other than "please wake up now." I'll work out the kinks in the driver side of things before I worry about tackling the rest of the legacy power save stuff. There's a bunch more work to do before I start down the path of PS-POLL station support (where the station sends PS-POLL frames to get a single frame back from the AP or peer.) I have no ETA on that; it's likely "whenever I get a bunch of free weekends." So if you have an Atheros NIC in your device and you feel a little adventurous, update to the latest -HEAD and flip on powersave. You can debug by using "wlandebug +power" to see the NIC going in and out of powersave and why it is or isn't doing it. Don't be afraid to report weird stuff to the mailing list. -a From owner-freebsd-wireless@FreeBSD.ORG Sun May 4 05:13:22 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E05088D5; Sun, 4 May 2014 05:13:22 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B674B1D8D; Sun, 4 May 2014 05:13:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s445DMXl092146; Sun, 4 May 2014 05:13:22 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s445DMDF092145; Sun, 4 May 2014 05:13:22 GMT (envelope-from linimon) Date: Sun, 4 May 2014 05:13:22 GMT Message-Id: <201405040513.s445DMDF092145@freefall.freebsd.org> To: eimar.koort@gmail.com, linimon@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: conf/184657: freebsd 10 unable to connect hidden wifi X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2014 05:13:23 -0000 Synopsis: freebsd 10 unable to connect hidden wifi State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun May 4 05:12:54 UTC 2014 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=184657 From owner-freebsd-wireless@FreeBSD.ORG Mon May 5 11:06:53 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BAD7EF54 for ; Mon, 5 May 2014 11:06:53 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89BF51D08 for ; Mon, 5 May 2014 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s45B6rvS083307 for ; Mon, 5 May 2014 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s45B6rbI083304 for freebsd-wireless@FreeBSD.org; Mon, 5 May 2014 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 May 2014 11:06:53 GMT Message-Id: <201405051106.s45B6rbI083304@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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2014 11:06:53 -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/188654 wireless [urtwn] tp-link wl-725n Realtek 8188 chip do not work o kern/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o bin/187624 wireless [patch] wpa_supplicant(8): WEP and other ciphers do no o bin/187470 wireless [bthidd] [patch] Apple Wireless Keyboard (JIS) o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] [panic] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP fails, WPA o kern/185025 wireless [iwi] [panic] iwi driver panic on 10.0rc2 f usb/184918 wireless [ural] regression on WEP o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181694 wireless [iwn] [suspend/resume] [patch] Initialize hardware in o kern/181161 wireless [wl] [panic] config a old compaq wl-110 wireless card 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/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/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/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/168754 wireless [ath] if_ath dont have internal name o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless [ath] [suspend/resume] 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/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] kernel panic: page fault with ath0 taskq 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 194 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed May 7 03:02:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB8E82A7 for ; Wed, 7 May 2014 03:02:30 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 767D6616 for ; Wed, 7 May 2014 03:02:30 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id i17so429986qcy.39 for ; Tue, 06 May 2014 20:02: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=Shi9yTTpz3wr78xNBCE8s4QZoU9UWODn4giJk8JO9Sc=; b=eO11LZPurYl6Z7ePZERf1bijn5Wz4pqEcsAPHq4Hdmt2DLipUip6zCBOkKfmxi+oYx 6rzZQI3eTgjCf+92xCT7Bx5PlRC7h8s/NfJhAbzvi2wiJq+Xaeo869e5SmycDYscPBBZ zFrtjqWPlbW+WfDV9GT/9ZMydlKZLY64GwQgwHhUdckrAHd+IqPmgE7tlH4SJJBIAUaM A7ZdqmhYqmIGztNTZP2h+BkjUF8LhicmsjQWlCqugkNf35s+ZAG3OSE06GSYd7W4Jfgi 7RG/XEjmxePL2nWrkPZpiBCfT7BFHiEj5qRtnoaoKpTFq4cwFwuJrQB9ZFilg2P7qNUR u7KQ== MIME-Version: 1.0 X-Received: by 10.140.96.51 with SMTP id j48mr56380555qge.24.1399431749585; Tue, 06 May 2014 20:02:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 6 May 2014 20:02:29 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> Date: Tue, 6 May 2014 20:02:29 -0700 X-Google-Sender-Auth: ggHQHG6_CsYLDvmfBpOSuFTKy2c Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2014 03:02:30 -0000 Hi! So, it turns out that I don't have any Centrino 1000 devices. I have Centrino 100 and Centrino 1030 devices, which isn't at all Centrino 1000. I'll go and see if I can acquire one. I'll also see if I can come up with a diff for you. Thanks! -a From owner-freebsd-wireless@FreeBSD.ORG Wed May 7 03:16:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 420318CC for ; Wed, 7 May 2014 03:16:30 +0000 (UTC) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE8687E0 for ; Wed, 7 May 2014 03:16:29 +0000 (UTC) Received: by mail-qg0-f54.google.com with SMTP id q108so414024qgd.41 for ; Tue, 06 May 2014 20:16:28 -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=Hcc/+XgDPoenToxTnOX91njix+2kE0Uk0dA9Ng2jpKU=; b=Tl+YDFh3r2dlRA6hhHrcUvNPlV7mkit3SJqas1eZYahB1aC6dZBkyy0WLj1vXtrRaS aN+2T7+UFPfRwUT2HlXBKPIIYUinAYAy9qqsUANLdvgFjdj5YiKYjLnK/9ud/hsST3m4 W2+SsGIha1PP335X59nShh6/P/U7SK4f/snYkm57W7BYTuX+Hu+cALxRulqV6DkV5k/B PN38S3onrDgKLHUyy/CCjp+ZvDpWbgSfS6LuUg66sulpdqHd6W7WeeQnbpI0sgXFL5Wz PI/opOGPLEK0t4NC+Pz/CaABXjZ9TeAMLbE4pAK5sTv31ZqqoTEqnqo3wmRolWOxYXfC wreA== MIME-Version: 1.0 X-Received: by 10.140.42.85 with SMTP id b79mr52812026qga.87.1399432588552; Tue, 06 May 2014 20:16:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 6 May 2014 20:16:28 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> Date: Tue, 6 May 2014 20:16:28 -0700 X-Google-Sender-Auth: LbCukq-bYa3Vy20Klm2aF4x6G6I Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2014 03:16:30 -0000 Hi! Would you mind trying this? What values do you have for sc_txchainmask and sc_rxchainmask? Before they're over-ridden? Thanks! -a adrian@sabrina:~/work/freebsd/head/src/sys/dev/iwn % svn diff . Index: if_iwn.c =================================================================== --- if_iwn.c (revision 265478) +++ if_iwn.c (working copy) @@ -744,6 +744,8 @@ sc->limits = &iwn1000_sensitivity_limits; sc->base_params = &iwn1000_base_params; sc->fwname = "iwn1000fw"; + /* XXX override chainmasks? */ + sc->txchainmask = IWN_ANT_AB; break; default: device_printf(sc->sc_dev, "adapter type id : 0x%04x sub id :" Index: if_iwn_chip_cfg.h =================================================================== --- if_iwn_chip_cfg.h (revision 265478) +++ if_iwn_chip_cfg.h (working copy) @@ -219,14 +219,18 @@ .regulatory_bands = iwn5000_regulatory_bands, .enhanced_TX_power = false, .calib_need = - ( IWN_FLG_NEED_PHY_CALIB_DC + ( +// IWN_FLG_NEED_PHY_CALIB_DC | IWN_FLG_NEED_PHY_CALIB_LO + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC | IWN_FLG_NEED_PHY_CALIB_TX_IQ - | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), + | IWN_FLG_NEED_PHY_CALIB_BASE_BAND + ), .support_hostap = false, .no_multi_vaps = true, .additional_gp_drv_bit = IWN_GP_DRIVER_NONE, - .bt_mode = IWN_BT_NONE, +// .bt_mode = IWN_BT_NONE, + .bt_mode = IWN_BT_SIMPLE, .plcp_err_threshold = IWN_PLCP_ERR_EXT_LONG_THRESHOLD, }; static const struct iwn_base_params iwn_6000_base_params = { From owner-freebsd-wireless@FreeBSD.ORG Wed May 7 03:23:20 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D351CBA for ; Wed, 7 May 2014 03:23:20 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 361FC8BD for ; Wed, 7 May 2014 03:23:20 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id m5so411453qaj.16 for ; Tue, 06 May 2014 20:23:18 -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=Hcc/+XgDPoenToxTnOX91njix+2kE0Uk0dA9Ng2jpKU=; b=kVSCwD+0XeratDNwkyWuNVePtuomWnlip59wLqoy8ALfwJ0fMllmAiFEjYQz1dhaZX MPEd37idiZKv9G9kjWh6EQF6YijDqtSn+GWQ8NiCzNTcmBuXN0F8INQzN6SFUYV5ugDU B/uLEfLiK+nDBp3J5AjYUB8F6ZhvicHsArSAcg2evq7GeR47D3+H8s7mcJZhMcCYC2y3 tirTzBlE5LTAKlP5AaaV5nRsv+Yzgbi9pufkmjZfEk1hak5IIYd13BIcCsmLyRGb6jOH o7Y+OptMXydJZv3NR5NVA6ZrrWvuxrn2kvEABvn4Gg7iwAuCV5aNzcE0UooeqjQjKdP1 BtfA== MIME-Version: 1.0 X-Received: by 10.224.129.66 with SMTP id n2mr61662539qas.55.1399432998741; Tue, 06 May 2014 20:23:18 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Tue, 6 May 2014 20:23:18 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> Date: Tue, 6 May 2014 20:23:18 -0700 X-Google-Sender-Auth: uzGg4fD9dCbjTln15FURqxMYVJ4 Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2014 03:23:20 -0000 Hi! Would you mind trying this? What values do you have for sc_txchainmask and sc_rxchainmask? Before they're over-ridden? Thanks! -a adrian@sabrina:~/work/freebsd/head/src/sys/dev/iwn % svn diff . Index: if_iwn.c =================================================================== --- if_iwn.c (revision 265478) +++ if_iwn.c (working copy) @@ -744,6 +744,8 @@ sc->limits = &iwn1000_sensitivity_limits; sc->base_params = &iwn1000_base_params; sc->fwname = "iwn1000fw"; + /* XXX override chainmasks? */ + sc->txchainmask = IWN_ANT_AB; break; default: device_printf(sc->sc_dev, "adapter type id : 0x%04x sub id :" Index: if_iwn_chip_cfg.h =================================================================== --- if_iwn_chip_cfg.h (revision 265478) +++ if_iwn_chip_cfg.h (working copy) @@ -219,14 +219,18 @@ .regulatory_bands = iwn5000_regulatory_bands, .enhanced_TX_power = false, .calib_need = - ( IWN_FLG_NEED_PHY_CALIB_DC + ( +// IWN_FLG_NEED_PHY_CALIB_DC | IWN_FLG_NEED_PHY_CALIB_LO + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC | IWN_FLG_NEED_PHY_CALIB_TX_IQ - | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), + | IWN_FLG_NEED_PHY_CALIB_BASE_BAND + ), .support_hostap = false, .no_multi_vaps = true, .additional_gp_drv_bit = IWN_GP_DRIVER_NONE, - .bt_mode = IWN_BT_NONE, +// .bt_mode = IWN_BT_NONE, + .bt_mode = IWN_BT_SIMPLE, .plcp_err_threshold = IWN_PLCP_ERR_EXT_LONG_THRESHOLD, }; static const struct iwn_base_params iwn_6000_base_params = { From owner-freebsd-wireless@FreeBSD.ORG Wed May 7 05:06:28 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42942746; Wed, 7 May 2014 05:06:28 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 166E5136; Wed, 7 May 2014 05:06:28 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4756R4t022481; Wed, 7 May 2014 05:06:27 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4756REQ022480; Wed, 7 May 2014 05:06:27 GMT (envelope-from linimon) Date: Wed, 7 May 2014 05:06:27 GMT Message-Id: <201405070506.s4756REQ022480@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/189405: [run] [wlan] hostapd, kernel panic, wlan using run device, run0: RT3071, RF RT3022 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2014 05:06:28 -0000 Old Synopsis: hostapd, kernel panic, wlan using run device, run0: RT3071, RF RT3022 New Synopsis: [run] [wlan] hostapd, kernel panic, wlan using run device, run0: RT3071, RF RT3022 Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Wed May 7 05:05:57 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=189405 From owner-freebsd-wireless@FreeBSD.ORG Thu May 8 04:59:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67C0F9E1 for ; Thu, 8 May 2014 04:59:47 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20755A48 for ; Thu, 8 May 2014 04:59:47 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id j5so2083755qaq.1 for ; Wed, 07 May 2014 21:59:46 -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=casZfBdoVu7plAjV9dY3CUpgePkRqpkKJtygQQun/+8=; b=ZkYZZFVtoP6BLGWAWwlOhTeEXnlkoWi39b3NMag7hYVUn1nP7lUDwUhvZ/k5zqEfHq PQVpFC6YI7Y56z75jemt/AL6v7CfjPRhai14nP0pfsmBf6Bt2DQVBVBSKT3i5MpXYxUM Nh9/6YlQK/7MfPe5jKRviegBdjFHS0er2dUGKPcgfgMakAXfQ3dZkkWsZywvrUkyiaha 00bCv5K7YDCdzn13JW3zymeHl/BnMwkaS4XD0Y39nmMGRqPam+aNdKmvUFC54NB7OhDY iqFg6tILStcgRmwbuBlYKtV18ZgkOdQbJ+zc8rEUvMY+uDIMc5WoI+0QTss5rguP4jSF ii0A== MIME-Version: 1.0 X-Received: by 10.140.96.51 with SMTP id j48mr1568883qge.24.1399525186283; Wed, 07 May 2014 21:59:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 7 May 2014 21:59:46 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> Date: Wed, 7 May 2014 21:59:46 -0700 X-Google-Sender-Auth: ve9he5HRZ_wE-gaX61TXs27kUt0 Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 04:59:47 -0000 .. and I just ordered a Centrino 1000 NIC. Wish me luck. Thanks! -a On 6 May 2014 20:23, Adrian Chadd wrote: > Hi! > > Would you mind trying this? > > What values do you have for sc_txchainmask and sc_rxchainmask? Before > they're over-ridden? > > Thanks! > > > -a > > adrian@sabrina:~/work/freebsd/head/src/sys/dev/iwn % svn diff . > Index: if_iwn.c > =================================================================== > --- if_iwn.c (revision 265478) > +++ if_iwn.c (working copy) > @@ -744,6 +744,8 @@ > sc->limits = &iwn1000_sensitivity_limits; > sc->base_params = &iwn1000_base_params; > sc->fwname = "iwn1000fw"; > + /* XXX override chainmasks? */ > + sc->txchainmask = IWN_ANT_AB; > break; > default: > device_printf(sc->sc_dev, "adapter type id : 0x%04x sub id :" > Index: if_iwn_chip_cfg.h > =================================================================== > --- if_iwn_chip_cfg.h (revision 265478) > +++ if_iwn_chip_cfg.h (working copy) > @@ -219,14 +219,18 @@ > .regulatory_bands = iwn5000_regulatory_bands, > .enhanced_TX_power = false, > .calib_need = > - ( IWN_FLG_NEED_PHY_CALIB_DC > + ( > +// IWN_FLG_NEED_PHY_CALIB_DC > | IWN_FLG_NEED_PHY_CALIB_LO > + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC > | IWN_FLG_NEED_PHY_CALIB_TX_IQ > - | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), > + | IWN_FLG_NEED_PHY_CALIB_BASE_BAND > + ), > .support_hostap = false, > .no_multi_vaps = true, > .additional_gp_drv_bit = IWN_GP_DRIVER_NONE, > - .bt_mode = IWN_BT_NONE, > +// .bt_mode = IWN_BT_NONE, > + .bt_mode = IWN_BT_SIMPLE, > .plcp_err_threshold = IWN_PLCP_ERR_EXT_LONG_THRESHOLD, > }; > static const struct iwn_base_params iwn_6000_base_params = { From owner-freebsd-wireless@FreeBSD.ORG Thu May 8 10:37:39 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA5DDC47; Thu, 8 May 2014 10:37:38 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (elam.kais.kyoto-u.ac.jp [130.54.60.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9136DBE2; Thu, 8 May 2014 10:37:38 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (localhost [127.0.0.1]) by elam.kais.kyoto-u.ac.jp (8.14.8/8.14.8) with ESMTP id s48AU86I014910; Thu, 8 May 2014 19:30:08 +0900 (JST) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) To: Adrian Chadd Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> X-Mailer: MH-E 8.0.3; MH 6.8.4.JP-3.05; GNU Emacs 22.3.1 User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?G?= =?ISO-8859-4?Q?oj=F2?=) APEL/10.8 Emacs/22.3 (i386-portbld-freebsd8.4) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Date: Thu, 08 May 2014 19:30:08 +0900 Message-ID: <14909.1399545008@elam.kais.kyoto-u.ac.jp> From: Kaho Toshikazu X-Virus-Scanned: clamav-milter 0.98.1 at elam.kais.kyoto-u.ac.jp X-Virus-Status: Clean Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 10:37:39 -0000 Hello adrian, Thank you for a patch, and I'm sorry for late reply. Your patch fixes the problem. ".calib_need" flag's change helps. Other changes doesn't need to fix, but they doesn't seem to make any problem. The minimum necessary change is below. if_iwn.c : no change if_iwn_chip_cfg.h: remove IWN_FLG_NEED_PHY_CALIB_DC, add IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC Index: if_iwn_chip_cfg.h =================================================================== --- if_iwn_chip_cfg.h (revision 265665) +++ if_iwn_chip_cfg.h (working copy) @@ -219,8 +219,9 @@ .regulatory_bands = iwn5000_regulatory_bands, .enhanced_TX_power = false, .calib_need = - ( IWN_FLG_NEED_PHY_CALIB_DC - | IWN_FLG_NEED_PHY_CALIB_LO + ( + IWN_FLG_NEED_PHY_CALIB_LO + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC | IWN_FLG_NEED_PHY_CALIB_TX_IQ | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), .support_hostap = false, -- Kaho Toshikazu Adrian Chadd wrote: > Hi! > > Would you mind trying this? > > What values do you have for sc_txchainmask and sc_rxchainmask? Before > they're over-ridden? > > Thanks! > > > -a > > adrian@sabrina:~/work/freebsd/head/src/sys/dev/iwn % svn diff . > Index: if_iwn.c > =================================================================== > --- if_iwn.c (revision 265478) > +++ if_iwn.c (working copy) > @@ -744,6 +744,8 @@ > sc->limits = &iwn1000_sensitivity_limits; > sc->base_params = &iwn1000_base_params; > sc->fwname = "iwn1000fw"; > + /* XXX override chainmasks? */ > + sc->txchainmask = IWN_ANT_AB; > break; > default: > device_printf(sc->sc_dev, "adapter type id : 0x%04x sub id :" > Index: if_iwn_chip_cfg.h > =================================================================== > --- if_iwn_chip_cfg.h (revision 265478) > +++ if_iwn_chip_cfg.h (working copy) > @@ -219,14 +219,18 @@ > .regulatory_bands = iwn5000_regulatory_bands, > .enhanced_TX_power = false, > .calib_need = > - ( IWN_FLG_NEED_PHY_CALIB_DC > + ( > +// IWN_FLG_NEED_PHY_CALIB_DC > | IWN_FLG_NEED_PHY_CALIB_LO > + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC > | IWN_FLG_NEED_PHY_CALIB_TX_IQ > - | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), > + | IWN_FLG_NEED_PHY_CALIB_BASE_BAND > + ), > .support_hostap = false, > .no_multi_vaps = true, > .additional_gp_drv_bit = IWN_GP_DRIVER_NONE, > - .bt_mode = IWN_BT_NONE, > +// .bt_mode = IWN_BT_NONE, > + .bt_mode = IWN_BT_SIMPLE, > .plcp_err_threshold = IWN_PLCP_ERR_EXT_LONG_THRESHOLD, > }; > static const struct iwn_base_params iwn_6000_base_params = { From owner-freebsd-wireless@FreeBSD.ORG Thu May 8 16:43:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9045E3C1 for ; Thu, 8 May 2014 16:43:17 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47C9D826 for ; Thu, 8 May 2014 16:43:17 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id x13so3221543qcv.30 for ; Thu, 08 May 2014 09:43:15 -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=rCSiL862vnlwFDjGOCQQbhkEhZh48SIdvSnFqBndDuM=; b=mlYe/3PpReqUv7rLiwd6+7j5pEiSqh+TPQMycba17ulP2MqVyCTE5nYqaHiKqWQH8U ibS3X2IZ35cpeHruTUI7Ji6/Usme74yXH2NtiyDRwkKA722KS9mgnvoONJ7VyQ4blw+i wSIU+T317KS1xN1wchsSwdpxhOtxjDh8x6iTbJOAansyyzvMAq4lcETbcxGRtw1qmqVb e9YMux8kTkQIdcY/sDRLbgYKrc+2r18Mqnii+zQVyngtzQdKABbXSGvxqzy3vXZ3Yza4 a/X+kFB0P2tsHH5r2S3QDLjI57tC4K8r4+91lA+NxZHtJp5Omxit4f5Nk6UHJCXVIlwy C0HA== MIME-Version: 1.0 X-Received: by 10.224.129.66 with SMTP id n2mr6587118qas.55.1399567395787; Thu, 08 May 2014 09:43:15 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Thu, 8 May 2014 09:43:15 -0700 (PDT) In-Reply-To: <14909.1399545008@elam.kais.kyoto-u.ac.jp> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> <14909.1399545008@elam.kais.kyoto-u.ac.jp> Date: Thu, 8 May 2014 09:43:15 -0700 X-Google-Sender-Auth: IRHVhGf22K7AKiw5cznO85-ek9w Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 16:43:17 -0000 Hi! Cool! So what's the value of txchainmask and rxchainmask from the EEPROM? before things get overridden? I'd like to figure out what that changed. Thanks! -a On 8 May 2014 03:30, Kaho Toshikazu wrote: > Hello adrian, > > Thank you for a patch, and I'm sorry for late reply. > Your patch fixes the problem. ".calib_need" flag's change helps. > Other changes doesn't need to fix, but they doesn't > seem to make any problem. > > The minimum necessary change is below. > if_iwn.c : no change > if_iwn_chip_cfg.h: remove IWN_FLG_NEED_PHY_CALIB_DC, > add IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC > > > Index: if_iwn_chip_cfg.h > =================================================================== > --- if_iwn_chip_cfg.h (revision 265665) > +++ if_iwn_chip_cfg.h (working copy) > @@ -219,8 +219,9 @@ > .regulatory_bands = iwn5000_regulatory_bands, > .enhanced_TX_power = false, > .calib_need = > - ( IWN_FLG_NEED_PHY_CALIB_DC > - | IWN_FLG_NEED_PHY_CALIB_LO > + ( > + IWN_FLG_NEED_PHY_CALIB_LO > + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC > | IWN_FLG_NEED_PHY_CALIB_TX_IQ > | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), > .support_hostap = false, > > -- > Kaho Toshikazu > > > Adrian Chadd wrote: > >> Hi! >> >> Would you mind trying this? >> >> What values do you have for sc_txchainmask and sc_rxchainmask? Before >> they're over-ridden? >> >> Thanks! >> >> >> -a >> >> adrian@sabrina:~/work/freebsd/head/src/sys/dev/iwn % svn diff . >> Index: if_iwn.c >> =================================================================== >> --- if_iwn.c (revision 265478) >> +++ if_iwn.c (working copy) >> @@ -744,6 +744,8 @@ >> sc->limits = &iwn1000_sensitivity_limits; >> sc->base_params = &iwn1000_base_params; >> sc->fwname = "iwn1000fw"; >> + /* XXX override chainmasks? */ >> + sc->txchainmask = IWN_ANT_AB; >> break; >> default: >> device_printf(sc->sc_dev, "adapter type id : 0x%04x sub id :" >> Index: if_iwn_chip_cfg.h >> =================================================================== >> --- if_iwn_chip_cfg.h (revision 265478) >> +++ if_iwn_chip_cfg.h (working copy) >> @@ -219,14 +219,18 @@ >> .regulatory_bands = iwn5000_regulatory_bands, >> .enhanced_TX_power = false, >> .calib_need = >> - ( IWN_FLG_NEED_PHY_CALIB_DC >> + ( >> +// IWN_FLG_NEED_PHY_CALIB_DC >> | IWN_FLG_NEED_PHY_CALIB_LO >> + | IWN_FLG_NEED_PHY_CALIB_TX_IQ_PERIODIC >> | IWN_FLG_NEED_PHY_CALIB_TX_IQ >> - | IWN_FLG_NEED_PHY_CALIB_BASE_BAND ), >> + | IWN_FLG_NEED_PHY_CALIB_BASE_BAND >> + ), >> .support_hostap = false, >> .no_multi_vaps = true, >> .additional_gp_drv_bit = IWN_GP_DRIVER_NONE, >> - .bt_mode = IWN_BT_NONE, >> +// .bt_mode = IWN_BT_NONE, >> + .bt_mode = IWN_BT_SIMPLE, >> .plcp_err_threshold = IWN_PLCP_ERR_EXT_LONG_THRESHOLD, >> }; >> static const struct iwn_base_params iwn_6000_base_params = { From owner-freebsd-wireless@FreeBSD.ORG Fri May 9 03:48:21 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1ED23A4; Fri, 9 May 2014 03:48:21 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (elam.kais.kyoto-u.ac.jp [130.54.60.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D110BE1; Fri, 9 May 2014 03:48:20 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (localhost [127.0.0.1]) by elam.kais.kyoto-u.ac.jp (8.14.8/8.14.8) with ESMTP id s493mIgn020397; Fri, 9 May 2014 12:48:18 +0900 (JST) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) To: Adrian Chadd Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> <14909.1399545008@elam.kais.kyoto-u.ac.jp> X-Mailer: MH-E 8.0.3; MH 6.8.4.JP-3.05; GNU Emacs 22.3.1 User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?G?= =?ISO-8859-4?Q?oj=F2?=) APEL/10.8 Emacs/22.3 (i386-portbld-freebsd8.4) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Date: Fri, 09 May 2014 12:48:18 +0900 Message-ID: <20396.1399607298@elam.kais.kyoto-u.ac.jp> From: Kaho Toshikazu X-Virus-Scanned: clamav-milter 0.98.1 at elam.kais.kyoto-u.ac.jp X-Virus-Status: Clean Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 03:48:21 -0000 Hello, Adrian Chadd wrote: > So what's the value of txchainmask and rxchainmask from the EEPROM? > before things get overridden? > > I'd like to figure out what that changed. In both before and after applying the patch, sc->txchainmask=1, sc->rxchainmask=3, ntxsteams=1. I think that 1st breakage introduced by r258030 in the function iwn_set_link_quality() was already fixed by r258085. 2nd breakage introduced by r258035 seems to be fixed by the patch. Because 2nd breakage was introduced before 1st breakage was fixed, we faced to a difficulty tracking down the problem. I don't know a meaning of a parameter .calib_need, but it is something wrong and it is corrected by the patch. -- Kaho Toshikazu From owner-freebsd-wireless@FreeBSD.ORG Fri May 9 04:09:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4DA6D169 for ; Fri, 9 May 2014 04:09:10 +0000 (UTC) Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04A8EE3E for ; Fri, 9 May 2014 04:09:09 +0000 (UTC) Received: by mail-qg0-f45.google.com with SMTP id z60so3819747qgd.4 for ; Thu, 08 May 2014 21:09:09 -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=7CekH+eGRim1MKju3YmvpQeV8sDCEufndL02MXcOr1Y=; b=JqWyqqvFjnEudci7xJlUye6VTl21eck72oVf0wuRNNP6ag4zErGhcJNsUNzGDt8BXm 9MntKK8GQMAwggWRQ+IMwTxd1FQ9vmpG001jOhwNtHGODmUMAtTddThqLeRuytvUjCMI 1fJ/VQpocg2Myl914nncNAn4JqZSVu5csuF+YaNDFODZfMqfbOhNdiinoxDVjyap0ASc TQCuUIrEX63lYLWwi/8/ULsl47hXn2tY4pT1kQ/mdySQkWuC0c902HlcFXNCt3gUDDiE Op1zVX448zzLRSQrnuO6uAI+ylzrOCCv1o8KRU+r9YUgKECKWdCRovpC85vyYKMJfkSO 7D5g== MIME-Version: 1.0 X-Received: by 10.224.16.199 with SMTP id p7mr11220191qaa.76.1399608549048; Thu, 08 May 2014 21:09:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Thu, 8 May 2014 21:09:08 -0700 (PDT) In-Reply-To: <20396.1399607298@elam.kais.kyoto-u.ac.jp> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> <14909.1399545008@elam.kais.kyoto-u.ac.jp> <20396.1399607298@elam.kais.kyoto-u.ac.jp> Date: Thu, 8 May 2014 21:09:08 -0700 X-Google-Sender-Auth: O56Ozh9PwPU0fnUTdxf2P7pvc-o Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 04:09:10 -0000 Ok, lemme commit the config fix. Thanks for persisting with this! -a On 8 May 2014 20:48, Kaho Toshikazu wrote: > Hello, > > Adrian Chadd wrote: > >> So what's the value of txchainmask and rxchainmask from the EEPROM? >> before things get overridden? >> >> I'd like to figure out what that changed. > > In both before and after applying the patch, sc->txchainmask=1, > sc->rxchainmask=3, ntxsteams=1. I think that 1st breakage > introduced by r258030 in the function iwn_set_link_quality() > was already fixed by r258085. > > 2nd breakage introduced by r258035 seems to be fixed by the patch. > Because 2nd breakage was introduced before 1st breakage was fixed, > we faced to a difficulty tracking down the problem. > I don't know a meaning of a parameter .calib_need, > but it is something wrong and it is corrected by the patch. > > -- > Kaho Toshikazu > > From owner-freebsd-wireless@FreeBSD.ORG Sat May 10 21:26:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08B6A90A for ; Sat, 10 May 2014 21:26:00 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2367C0B for ; Sat, 10 May 2014 21:25:59 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so6144591qgd.29 for ; Sat, 10 May 2014 14:25:58 -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=53PwHMBrqcnEMfm9rTTdQV7JyXkc579LUJivwecgj/s=; b=XaY4WKk+t9r5oyYwjTLnXp9CJBoX0ga0/E0piM5k1GqYx/jZIYM10MbG+91PhikUbI YluIKPjv8QRUdBceBOPwfp7PEqcV8yI3LRtR7ShYOQHgI+ROhcdez5zbymy3xeG5MJbr IsiKzessTS/GT7NNbgr/3JFiCNlieCVnPUEDs+b9Qt3/NlynjkpfAOre1tL+iOojNz+I kjf+cPM1MjF7J3G3PQOP2CEr5voV9mhwBL1rLFbXKhBJQeocZhRy48ki3TN881NWSjMd 0DafGpnS/dIENpYANluWISOi+x0GdoJ8lrlgbKj0kH8/1MLgl95lMozWpoHiti/YjPx4 8anw== MIME-Version: 1.0 X-Received: by 10.140.22.209 with SMTP id 75mr24745054qgn.4.1399757158918; Sat, 10 May 2014 14:25:58 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Sat, 10 May 2014 14:25:58 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <24791.1393550277@elam.kais.kyoto-u.ac.jp> <75498.1398751548@elam.kais.kyoto-u.ac.jp> <84650.1398819225@elam.kais.kyoto-u.ac.jp> <14909.1399545008@elam.kais.kyoto-u.ac.jp> <20396.1399607298@elam.kais.kyoto-u.ac.jp> Date: Sat, 10 May 2014 14:25:58 -0700 X-Google-Sender-Auth: LohFLfc35OxeSxmIsR5NBdZv6Jo Message-ID: Subject: Re: Centrino Wireless-N 1000 support is also broken (Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135) From: Adrian Chadd To: Kaho Toshikazu Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2014 21:26:00 -0000 committed! Thanks! -a On 8 May 2014 21:09, Adrian Chadd wrote: > Ok, lemme commit the config fix. > > Thanks for persisting with this! > > > -a > > > On 8 May 2014 20:48, Kaho Toshikazu wrote: >> Hello, >> >> Adrian Chadd wrote: >> >>> So what's the value of txchainmask and rxchainmask from the EEPROM? >>> before things get overridden? >>> >>> I'd like to figure out what that changed. >> >> In both before and after applying the patch, sc->txchainmask=1, >> sc->rxchainmask=3, ntxsteams=1. I think that 1st breakage >> introduced by r258030 in the function iwn_set_link_quality() >> was already fixed by r258085. >> >> 2nd breakage introduced by r258035 seems to be fixed by the patch. >> Because 2nd breakage was introduced before 1st breakage was fixed, >> we faced to a difficulty tracking down the problem. >> I don't know a meaning of a parameter .calib_need, >> but it is something wrong and it is corrected by the patch. >> >> -- >> Kaho Toshikazu >> >> From owner-freebsd-wireless@FreeBSD.ORG Sun May 11 19:31:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 56473DA3 for ; Sun, 11 May 2014 19:31:14 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DABA62D5D for ; Sun, 11 May 2014 19:31:13 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id i8so6979010qcq.29 for ; Sun, 11 May 2014 12:31:13 -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=y6FV3VXoCfKaSr20p80jRJ55GRnqXVsdDo/vsDp7Qmg=; b=V9baH6JyReDovtyGoIcF0RG36jP+AVx8MIMAvI+VmIV2RUSwyseoJyZvKYcHoBxeik dWgRDdfSyqmmHtqMG81O95RMPAFvKi35rmu8Wke2vtw28MVg2HsSBg8im86yswlc++47 NTqqVWqAdMLfAoW26F3rNBiTAWOyBX+18vQVLKYmJJUz3Y9shJ71EsRcye04Pc8jSB/c AdDvuB44Ls09QeMVNI5fjFo3k8Zt7hSdt2E+45YEtO2934qn7yTH9o0uuueHIQuMCuKg r27w4aTu1x4zj8fwt0Y8A5odgWMuz+N7A8WbSGJHxmwB/eJX9IBFnrMSu6hZ/fL39pyx JjrQ== MIME-Version: 1.0 X-Received: by 10.224.129.66 with SMTP id n2mr32500468qas.55.1399836672959; Sun, 11 May 2014 12:31:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Sun, 11 May 2014 12:31:12 -0700 (PDT) In-Reply-To: References: <51C8AE67.7040801@unsane.co.uk> Date: Sun, 11 May 2014 12:31:12 -0700 X-Google-Sender-Auth: JafUJMsWrqZep_dJwzoWJe8zXkY Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Adrian Chadd To: Lyubomir Yotov , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2014 19:31:14 -0000 Hi, I've seen the AR5416 get into this state sometimes. I haven't yet figured out what it is. -a On 11 May 2014 12:29, Lyubomir Yotov wrote: > Hi again, > Sorry for troubling you again with this but two days ago I brought my > notebook in the office and noticed that the wlan is not working again (I > usually use the LAN where ever I can). I did some checks at home as well > but unfortunately things look the same as before. I have installed some > packages after my last mail to you and I tried with disabling all things in > /etc/rc.conf and /boot/loader.conf but still with no success. The last time > I managed to start up my wlan0 properly was two boots ago and it happened > after restart from USB drive with FreeBSD10 amd64 on it (I had to change > some rc.conf lines...). Now I get: > > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address > > and of course: > wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='ssid' freq=2432 > MHz) > wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out. > wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 > locally_generated=1 > > I still get 'kernel: ath0: device timeout'. > Attached are the files 'wpa_supplicant_20140511.log' from 'wpa_supplicant > -d -i wlan0 -c wpa_supplicant.tmp' command and 'wpa_supplicant.tmp'. > > Any ideas? > > Regards, > > Lyubo > > > On 5 May 2014 23:24, Adrian Chadd wrote: > >> Sweet! >> >> -a >> >> >> >> On 5 May 2014 13:19, Lyubomir Yotov wrote: >> >>> Hello Adrian, >>> >>> Yesterday I was forced to upgrade my T60 from 9.2 (i386) to 10 (amd64) >>> and now I can say that my atheros wireless is working (although when I >>> previously checked with 10 from live-cd it didn't. I only can't say whether >>> is was i386 or amd64). Thanks a lot for the help. As a solution I can >>> recommend to upgrade to FreeBSD 10 amd64 (if possible). >>> Best regards, >>> >>> Lyubo >>> >>> >>> On 23 January 2014 12:00, Lyubomir Yotov wrote: >>> >>>> Hello Adrian, >>>> Any news from the cracking :) ? >>>> >>>> Lyubo >>>> >>>> >>>> On 6 January 2014 21:22, Lyubomir Yotov wrote: >>>> >>>>> It depends on the antenna diversion probably how many antennas will be >>>>> connected. I thought over this and also checked if the antennas are >>>>> connected correctly - in the right order, but the antennas are fine and >>>>> what is more it works every time under windows and linux. I am wondering >>>>> what causes the timeouts after shutdown cycle - is there anything in the >>>>> firmware that responds differently to initialization in FreeBSD rather than >>>>> in Windows for example (it works under XP and under Win7). I read somewhere >>>>> that the WLAN switch on the panel under the arm rest makes no difference >>>>> under non Windows OS. >>>>> Do you manage to reproduce the problem? >>>>> >>>>> >>>>> >>>>> On 6 January 2014 17:00, Adrian Chadd wrote: >>>>> >>>>>> Ok, it's not an antenna thing then. Sometimes they only connect two >>>>>> antennas. :( >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 6 January 2014 06:58, Lyubomir Yotov wrote: >>>>>> >>>>>>> 1,3 and 2 (on two I have a black cable, not very clear from my >>>>>>> picture - sorry). >>>>>>> >>>>>>> >>>>>>> On 6 January 2014 16:35, Adrian Chadd wrote: >>>>>>> >>>>>>>> So you're connected to 1 and 3? >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 6 January 2014 06:34, Lyubomir Yotov wrote: >>>>>>>> >>>>>>>>> Should be 1,3 and 2. See the attached picture. It looks the same. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 6 January 2014 16:01, Adrian Chadd wrote: >>>>>>>>> >>>>>>>>>> ok, are there numbers (0, 1, 2) next to those antenna sockets? >>>>>>>>>> >>>>>>>>>> -a >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 5 January 2014 23:46, Lyubomir Yotov wrote: >>>>>>>>>> >>>>>>>>>>> This is how the cables are attached in my book. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 6 January 2014 09:03, Adrian Chadd wrote: >>>>>>>>>>> >>>>>>>>>>>> Which antenna connectors are they hooked up to? Can you send me >>>>>>>>>>>> a photograph? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -a >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 5 January 2014 22:57, Lyubomir Yotov wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Yes, I have opened it up. There are two antennas. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 6 January 2014 07:51, Adrian Chadd wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Have you opened this up? Are two or three antennas connected? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -a >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 5 January 2014 21:48, Lyubomir Yotov wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>> Here comes dmesg: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> lyubd@T60:/home/lyubd % dmesg >>>>>>>>>>>>>>> Copyright (c) 1992-2013 The FreeBSD Project. >>>>>>>>>>>>>>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, >>>>>>>>>>>>>>> 1992, 1993, 1994 >>>>>>>>>>>>>>> The Regents of the University of California. All >>>>>>>>>>>>>>> rights reserved. >>>>>>>>>>>>>>> FreeBSD is a registered trademark of The FreeBSD Foundation. >>>>>>>>>>>>>>> FreeBSD 9.2-RELEASE #0 r255898: Fri Sep 27 03:52:52 UTC 2013 >>>>>>>>>>>>>>> root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC >>>>>>>>>>>>>>> i386 >>>>>>>>>>>>>>> gcc version 4.2.1 20070831 patched [FreeBSD] >>>>>>>>>>>>>>> CPU: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz >>>>>>>>>>>>>>> (2161.30-MHz 686-class CPU) >>>>>>>>>>>>>>> Origin = "GenuineIntel" Id = 0x6f6 Family = 0x6 Model = >>>>>>>>>>>>>>> 0xf Stepping = 6 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Features=0xbfebfbff >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Features2=0xe3bd >>>>>>>>>>>>>>> AMD Features=0x20100000 >>>>>>>>>>>>>>> AMD Features2=0x1 >>>>>>>>>>>>>>> TSC: P-state invariant, performance statistics >>>>>>>>>>>>>>> real memory = 3221225472 (3072 MB) >>>>>>>>>>>>>>> avail memory = 3136278528 (2990 MB) >>>>>>>>>>>>>>> Event timer "LAPIC" quality 400 >>>>>>>>>>>>>>> ACPI APIC Table: >>>>>>>>>>>>>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>>>>>>>>>>>>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>>>>>>>>>>>>>> cpu0 (BSP): APIC ID: 0 >>>>>>>>>>>>>>> cpu1 (AP): APIC ID: 1 >>>>>>>>>>>>>>> ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 >>>>>>>>>>>>>>> (20110527/tbfadt-556) >>>>>>>>>>>>>>> ACPI Warning: Optional field Gpe1Block has zero address or >>>>>>>>>>>>>>> length: 0x000000000000102C/0x0 (20110527/tbfadt-586) >>>>>>>>>>>>>>> ioapic0: Changing APIC ID to 1 >>>>>>>>>>>>>>> ioapic0 irqs 0-23 on motherboard >>>>>>>>>>>>>>> kbd1 at kbdmux0 >>>>>>>>>>>>>>> acpi0: on motherboard >>>>>>>>>>>>>>> CPU0: local APIC error 0x40 >>>>>>>>>>>>>>> acpi_ec0: port >>>>>>>>>>>>>>> 0x62,0x66 on acpi0 >>>>>>>>>>>>>>> acpi0: Power Button (fixed) >>>>>>>>>>>>>>> acpi0: reservation of 0, a0000 (3) failed >>>>>>>>>>>>>>> acpi0: reservation of 100000, bff00000 (3) failed >>>>>>>>>>>>>>> cpu0: on acpi0 >>>>>>>>>>>>>>> cpu1: on acpi0 >>>>>>>>>>>>>>> attimer0: port 0x40-0x43 irq 0 on acpi0 >>>>>>>>>>>>>>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>>>>>>>>>>>>>> Event timer "i8254" frequency 1193182 Hz quality 100 >>>>>>>>>>>>>>> hpet0: iomem >>>>>>>>>>>>>>> 0xfed00000-0xfed003ff on acpi0 >>>>>>>>>>>>>>> Timecounter "HPET" frequency 14318180 Hz quality 950 >>>>>>>>>>>>>>> Event timer "HPET" frequency 14318180 Hz quality 450 >>>>>>>>>>>>>>> Event timer "HPET1" frequency 14318180 Hz quality 440 >>>>>>>>>>>>>>> Event timer "HPET2" frequency 14318180 Hz quality 440 >>>>>>>>>>>>>>> atrtc0: port 0x70-0x71 irq 8 on acpi0 >>>>>>>>>>>>>>> Event timer "RTC" frequency 32768 Hz quality 0 >>>>>>>>>>>>>>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 >>>>>>>>>>>>>>> acpi_timer0: <24-bit timer at 3.579545MHz> port >>>>>>>>>>>>>>> 0x1008-0x100b on acpi0 >>>>>>>>>>>>>>> acpi_lid0: on acpi0 >>>>>>>>>>>>>>> acpi_button0: on acpi0 >>>>>>>>>>>>>>> pcib0: port 0xcf8-0xcff on acpi0 >>>>>>>>>>>>>>> pci0: on pcib0 >>>>>>>>>>>>>>> pcib1: irq 16 at device 1.0 on pci0 >>>>>>>>>>>>>>> pci1: on pcib1 >>>>>>>>>>>>>>> vgapci0: port 0x2000-0x20ff mem >>>>>>>>>>>>>>> 0xd8000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 >>>>>>>>>>>>>>> hdac0: mem >>>>>>>>>>>>>>> 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 >>>>>>>>>>>>>>> pcib2: irq 20 at device 28.0 on pci0 >>>>>>>>>>>>>>> pci2: on pcib2 >>>>>>>>>>>>>>> em0: port >>>>>>>>>>>>>>> 0x3000-0x301f mem 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 >>>>>>>>>>>>>>> em0: Using an MSI interrupt >>>>>>>>>>>>>>> em0: Ethernet address: 00:1a:6b:69:c0:a8 >>>>>>>>>>>>>>> pcib3: irq 21 at device 28.1 on pci0 >>>>>>>>>>>>>>> pci3: on pcib3 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ath0: mem 0xedf00000-0xedf0ffff irq 17 at >>>>>>>>>>>>>>> device 0.0 on pci3 >>>>>>>>>>>>>>> ath0: AR5418 mac 12.10 RF5133 phy 8.1 >>>>>>>>>>>>>>> pcib4: irq 22 at device 28.2 on pci0 >>>>>>>>>>>>>>> pci4: on pcib4 >>>>>>>>>>>>>>> pcib5: irq 23 at device 28.3 on pci0 >>>>>>>>>>>>>>> pci12: on pcib5 >>>>>>>>>>>>>>> uhci0: port >>>>>>>>>>>>>>> 0x1800-0x181f irq 16 at device 29.0 on pci0 >>>>>>>>>>>>>>> usbus0 on uhci0 >>>>>>>>>>>>>>> uhci1: port >>>>>>>>>>>>>>> 0x1820-0x183f irq 17 at device 29.1 on pci0 >>>>>>>>>>>>>>> usbus1 on uhci1 >>>>>>>>>>>>>>> uhci2: port >>>>>>>>>>>>>>> 0x1840-0x185f irq 18 at device 29.2 on pci0 >>>>>>>>>>>>>>> usbus2 on uhci2 >>>>>>>>>>>>>>> uhci3: port >>>>>>>>>>>>>>> 0x1860-0x187f irq 19 at device 29.3 on pci0 >>>>>>>>>>>>>>> usbus3 on uhci3 >>>>>>>>>>>>>>> ehci0: mem >>>>>>>>>>>>>>> 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 >>>>>>>>>>>>>>> usbus4: EHCI version 1.0 >>>>>>>>>>>>>>> usbus4 on ehci0 >>>>>>>>>>>>>>> pcib6: at device 30.0 on pci0 >>>>>>>>>>>>>>> pci21: on pcib6 >>>>>>>>>>>>>>> cbb0: mem 0xe4300000-0xe4300fff >>>>>>>>>>>>>>> irq 16 at device 0.0 on pci21 >>>>>>>>>>>>>>> cardbus0: on cbb0 >>>>>>>>>>>>>>> pccard0: <16-bit PCCard bus> on cbb0 >>>>>>>>>>>>>>> isab0: at device 31.0 on pci0 >>>>>>>>>>>>>>> isa0: on isab0 >>>>>>>>>>>>>>> atapci0: port >>>>>>>>>>>>>>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 >>>>>>>>>>>>>>> ata0: at channel 0 on atapci0 >>>>>>>>>>>>>>> ahci0: port >>>>>>>>>>>>>>> 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf mem >>>>>>>>>>>>>>> 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 >>>>>>>>>>>>>>> ahci0: AHCI v1.10 with 4 1.5Gbps ports, Port Multiplier not >>>>>>>>>>>>>>> supported >>>>>>>>>>>>>>> ahcich0: at channel 0 on ahci0 >>>>>>>>>>>>>>> pci0: at device 31.3 (no driver attached) >>>>>>>>>>>>>>> acpi_tz0: on acpi0 >>>>>>>>>>>>>>> acpi_tz1: on acpi0 >>>>>>>>>>>>>>> atkbdc0: port 0x60,0x64 irq 1 >>>>>>>>>>>>>>> on acpi0 >>>>>>>>>>>>>>> atkbd0: irq 1 on atkbdc0 >>>>>>>>>>>>>>> kbd0 at atkbd0 >>>>>>>>>>>>>>> atkbd0: [GIANT-LOCKED] >>>>>>>>>>>>>>> psm0: flags 0x1000 irq 12 on atkbdc0 >>>>>>>>>>>>>>> psm0: [GIANT-LOCKED] >>>>>>>>>>>>>>> psm0: model Synaptics Touchpad, device ID 0 >>>>>>>>>>>>>>> battery0: on acpi0 >>>>>>>>>>>>>>> acpi_acad0: on acpi0 >>>>>>>>>>>>>>> acpi_ibm0: on acpi0 >>>>>>>>>>>>>>> pmtimer0 on isa0 >>>>>>>>>>>>>>> orm0: at iomem >>>>>>>>>>>>>>> 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid >>>>>>>>>>>>>>> ORM0000 on isa0 >>>>>>>>>>>>>>> sc0: at flags 0x100 on isa0 >>>>>>>>>>>>>>> sc0: VGA <16 virtual consoles, flags=0x300> >>>>>>>>>>>>>>> vga0: at port 0x3c0-0x3df iomem >>>>>>>>>>>>>>> 0xa0000-0xbffff on isa0 >>>>>>>>>>>>>>> ppc0: parallel port not found. >>>>>>>>>>>>>>> est0: on cpu0 >>>>>>>>>>>>>>> p4tcc0: on cpu0 >>>>>>>>>>>>>>> est1: on cpu1 >>>>>>>>>>>>>>> p4tcc1: on cpu1 >>>>>>>>>>>>>>> Timecounters tick every 1.000 msec >>>>>>>>>>>>>>> hdac0: Command timeout on address 1 >>>>>>>>>>>>>>> hdac0: Command timeout on address 1 >>>>>>>>>>>>>>> hdac0: CODEC is not responding! >>>>>>>>>>>>>>> hdacc0: at cad 0 on hdac0 >>>>>>>>>>>>>>> hdaa0: at nid >>>>>>>>>>>>>>> 1 on hdacc0 >>>>>>>>>>>>>>> pcm0: at nid 5 and 25,8 >>>>>>>>>>>>>>> on hdaa0 >>>>>>>>>>>>>>> pcm1: at nid 10 on >>>>>>>>>>>>>>> hdaa0 >>>>>>>>>>>>>>> usbus0: 12Mbps Full Speed USB v1.0 >>>>>>>>>>>>>>> usbus1: 12Mbps Full Speed USB v1.0 >>>>>>>>>>>>>>> usbus2: 12Mbps Full Speed USB v1.0 >>>>>>>>>>>>>>> usbus3: 12Mbps Full Speed USB v1.0 >>>>>>>>>>>>>>> usbus4: 480Mbps High Speed USB v2.0 >>>>>>>>>>>>>>> ugen0.1: at usbus0 >>>>>>>>>>>>>>> uhub0: >>>>>>>>>>>>>> 1> on usbus0 >>>>>>>>>>>>>>> ugen1.1: at usbus1 >>>>>>>>>>>>>>> uhub1: >>>>>>>>>>>>>> 1> on usbus1 >>>>>>>>>>>>>>> ugen2.1: at usbus2 >>>>>>>>>>>>>>> uhub2: >>>>>>>>>>>>>> 1> on usbus2 >>>>>>>>>>>>>>> ugen3.1: at usbus3 >>>>>>>>>>>>>>> uhub3: >>>>>>>>>>>>>> 1> on usbus3 >>>>>>>>>>>>>>> ugen4.1: at usbus4 >>>>>>>>>>>>>>> uhub4: >>>>>>>>>>>>>> 1> on usbus4 >>>>>>>>>>>>>>> ada0 at ahcich0 bus 0 scbus1 target 0 lun 0 >>>>>>>>>>>>>>> ada0: ATA-8 SATA 2.x device >>>>>>>>>>>>>>> ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) >>>>>>>>>>>>>>> ada0: Command Queueing enabled >>>>>>>>>>>>>>> ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) >>>>>>>>>>>>>>> ada0: quirks=0x1<4K> >>>>>>>>>>>>>>> cd0 at ata0 bus 0 scbus0 target 0 lun 0 >>>>>>>>>>>>>>> cd0: Removable CD-ROM >>>>>>>>>>>>>>> SCSI-0 device >>>>>>>>>>>>>>> cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO >>>>>>>>>>>>>>> 65534bytes) >>>>>>>>>>>>>>> cd0: Attempt to query device size failed: NOT READY, Medium >>>>>>>>>>>>>>> not present >>>>>>>>>>>>>>> ada0: Previously was known as ad4 >>>>>>>>>>>>>>> SMP: AP CPU #1 Launched! >>>>>>>>>>>>>>> uhub0: 2 ports with 2 removable, self powered >>>>>>>>>>>>>>> uhub1: 2 ports with 2 removable, self powered >>>>>>>>>>>>>>> uhub2: 2 ports with 2 removable, self powered >>>>>>>>>>>>>>> uhub3: 2 ports with 2 removable, self powered >>>>>>>>>>>>>>> Root mount waiting for: usbus4 >>>>>>>>>>>>>>> Root mount waiting for: usbus4 >>>>>>>>>>>>>>> uhub4: 8 ports with 8 removable, self powered >>>>>>>>>>>>>>> Root mount waiting for: usbus4 >>>>>>>>>>>>>>> Trying to mount root from ufs:/dev/ada0s4a [rw]... >>>>>>>>>>>>>>> ugen3.2: at usbus3 >>>>>>>>>>>>>>> fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.19 >>>>>>>>>>>>>>> drm0: on vgapci0 >>>>>>>>>>>>>>> info: [drm] MSI enabled 1 message(s) >>>>>>>>>>>>>>> info: [drm] Initialized radeon 1.31.0 20080613 >>>>>>>>>>>>>>> info: [drm] Setting GART location based on new memory map >>>>>>>>>>>>>>> info: [drm] Loading R500 Microcode >>>>>>>>>>>>>>> info: [drm] Num pipes: 1 >>>>>>>>>>>>>>> info: [drm] writeback test succeeded in 1 usecs >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Lyubo >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 6 January 2014 07:10, Adrian Chadd wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Ok, can you provide me a dmesg please? That way I can see >>>>>>>>>>>>>>>> what the specific chipset revision is. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Lemme go crack open my T60 and put an AR5418 in there :-) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -a >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 5 January 2014 14:10, Lyubomir Yotov wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Adrian, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I tried with 11.0-CURRENT as a livecd but no success >>>>>>>>>>>>>>>>> (below is the wpa_supplicant after issuing 'ifconfig wlan0 create wlandev >>>>>>>>>>>>>>>>> ath0'): >>>>>>>>>>>>>>>>> wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf >>>>>>>>>>>>>>>>> ###remark - start of wpa_supplicant output >>>>>>>>>>>>>>>>> Successfully initialized wpa_supplicant >>>>>>>>>>>>>>>>> wlan0: Trying to associate with 54:e6:fc:ae:6a:bc >>>>>>>>>>>>>>>>> (SSID='aero-gate' freq=2432 MHz) >>>>>>>>>>>>>>>>> wlan0: Authentication with 54:e6:fc:ae:6a:bc timed out. >>>>>>>>>>>>>>>>> wlan0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:ae:6a:bc >>>>>>>>>>>>>>>>> reason=3 locally_generated=1 >>>>>>>>>>>>>>>>> wlan0: Trying to associate with 54:e6:fc:ae:6a:bc >>>>>>>>>>>>>>>>> (SSID='aero-gate' freq=2432 MHz) >>>>>>>>>>>>>>>>> wlan0: Authentication with 54:e6:fc:ae:6a:bc timed out. >>>>>>>>>>>>>>>>> wlan0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:ae:6a:bc >>>>>>>>>>>>>>>>> reason=3 locally_generated=1 >>>>>>>>>>>>>>>>> wlan0: Trying to associate with 54:e6:fc:ae:6a:bc >>>>>>>>>>>>>>>>> (SSID='aero-gate' freq=2432 MHz) >>>>>>>>>>>>>>>>> wlan0: CTRL-EVENT-DISCONNECTED bssid=54:e6:fc:ae:6a:bc >>>>>>>>>>>>>>>>> reason=3 locally_generated=1 >>>>>>>>>>>>>>>>> ###remark - here I press Ctrl+C >>>>>>>>>>>>>>>>> ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign >>>>>>>>>>>>>>>>> requested address >>>>>>>>>>>>>>>>> ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not >>>>>>>>>>>>>>>>> supported >>>>>>>>>>>>>>>>> wlan0: CTRL-EVENT-TERMINATING >>>>>>>>>>>>>>>>> ###remark - end of wpa_supplicant output >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Any ideas? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Lyubo >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On 5 January 2014 23:57, Adrian Chadd wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Ok, please do. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have a T60 with me and some AR5418 NICs, so I don't >>>>>>>>>>>>>>>>>> mind doing a transplant and trying to make it work! >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -a >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On 5 January 2014 08:53, Lyubomir Yotov < >>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Not yet but I will give it a go these days. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Lyubomir >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On 5 January 2014 09:45, Adrian Chadd < >>>>>>>>>>>>>>>>>>> adrian@freebsd.org> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Have you tried -11? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -a >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On 30 December 2013 09:25, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hi Andrian, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Merry Christmas and all the best for the New Year! >>>>>>>>>>>>>>>>>>>>> I would like to ask if there is something on the >>>>>>>>>>>>>>>>>>>>> horizon with the Atheros time outs? Is there any chance in getting it >>>>>>>>>>>>>>>>>>>>> working without restart to Windows (in my case)? Is there anything else I >>>>>>>>>>>>>>>>>>>>> can try? Currently I am with 9.2-RELEASE #0 r255898. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> All the best, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Lyubomir >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On 17 July 2013 23:06, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>>>>>> No problem, I fully understand you. If you manage to >>>>>>>>>>>>>>>>>>>>>> find something I will be more than grateful. Anyway thanks for your time! I >>>>>>>>>>>>>>>>>>>>>> think you are doing quite a god job! >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Lyubo >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On 16 July 2013 11:51, Adrian Chadd < >>>>>>>>>>>>>>>>>>>>>> adrian@freebsd.org> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I'm sorry, I don't have the time to try and debug >>>>>>>>>>>>>>>>>>>>>>> this issue. If I had a T60 here that demonstrated this behaviour then I >>>>>>>>>>>>>>>>>>>>>>> could try to fix it. But I unfortunately don't; all my T60 hardware has >>>>>>>>>>>>>>>>>>>>>>> intel wifi. :( >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I can try putting an AR5418 in a T60 in a few weeks >>>>>>>>>>>>>>>>>>>>>>> and see if it exhibits this behaviour. But don't hold your breath. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Sorry :( >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -adrian >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On 15 July 2013 13:30, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Hi Adrian, >>>>>>>>>>>>>>>>>>>>>>>> I tried with -HEAD liveCD as proposed by Vincent >>>>>>>>>>>>>>>>>>>>>>>> and ghostbsd live cd but the situation is the same. I feel like I am >>>>>>>>>>>>>>>>>>>>>>>> missing something. On one hand I can scan the wireless networks and the >>>>>>>>>>>>>>>>>>>>>>>> wifi card seems to be working. On the other hand I cannot attach as the ath >>>>>>>>>>>>>>>>>>>>>>>> device times out (which according to the ath man pages should not occur). I >>>>>>>>>>>>>>>>>>>>>>>> also tried to encrypt the psk phrase with pwa_passphrase but with no >>>>>>>>>>>>>>>>>>>>>>>> success either. I tested with Kali linux live cd and the wireless was >>>>>>>>>>>>>>>>>>>>>>>> working fine. I also noticed that if I shutdown Windows and then start >>>>>>>>>>>>>>>>>>>>>>>> FreeBSD then the wifi also behaves the same way - ath0: device timed out. >>>>>>>>>>>>>>>>>>>>>>>> Only restart from Windows or restart from FreeBSD with working wifi can >>>>>>>>>>>>>>>>>>>>>>>> make the wifi work again. >>>>>>>>>>>>>>>>>>>>>>>> Do you have any other proposals? >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Lyubomir >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> On 24 June 2013 23:39, Vincent Hoffman < >>>>>>>>>>>>>>>>>>>>>>>> vince@unsane.co.uk> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> As an easy test if you arent keen on making the >>>>>>>>>>>>>>>>>>>>>>>>> leap just yet I'd >>>>>>>>>>>>>>>>>>>>>>>>> suggest getting a snapshot CD and just boot it as >>>>>>>>>>>>>>>>>>>>>>>>> a liveCD to test. >>>>>>>>>>>>>>>>>>>>>>>>> either a snapshot >>>>>>>>>>>>>>>>>>>>>>>>> http://www.freebsd.org/snapshots/ >>>>>>>>>>>>>>>>>>>>>>>>> or one of the daily builds from >>>>>>>>>>>>>>>>>>>>>>>>> https://pub.allbsd.org/FreeBSD-snapshots/ >>>>>>>>>>>>>>>>>>>>>>>>> (for example >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> https://pub.allbsd.org/FreeBSD-snapshots/amd64-amd64/10.0-HEAD-r252115-JPSNAP/iso/FreeBSD-10.0-HEAD-r252115-JPSNAP-amd64-amd64-release.iso >>>>>>>>>>>>>>>>>>>>>>>>> ) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> That said I run -CURRENT on my server at home (for >>>>>>>>>>>>>>>>>>>>>>>>> the atheros driver) >>>>>>>>>>>>>>>>>>>>>>>>> and dont have any problems with it. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Vince >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On 24/06/2013 21:01, Lyubomir Yotov wrote: >>>>>>>>>>>>>>>>>>>>>>>>> > Hi Adrian, >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > I will try to get -HEAD on my T60 and will >>>>>>>>>>>>>>>>>>>>>>>>> report back. >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > Regards, >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > Lyubomir >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> > On 24 June 2013 20:21, Adrian Chadd < >>>>>>>>>>>>>>>>>>>>>>>>> adrian@freebsd.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> >> Hi, >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> Would you be willing to try a -HEAD snapshot on >>>>>>>>>>>>>>>>>>>>>>>>> your laptop? >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> Maybe I've fixed it as part of the other driver >>>>>>>>>>>>>>>>>>>>>>>>> work that I've done as >>>>>>>>>>>>>>>>>>>>>>>>> >> part of development in -HEAD. >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> But right now I really have no idea. I don't >>>>>>>>>>>>>>>>>>>>>>>>> have a T60 here that has >>>>>>>>>>>>>>>>>>>>>>>>> >> that chip in it. If all the T60 BIOSes allow >>>>>>>>>>>>>>>>>>>>>>>>> AR5418 NICs then I can >>>>>>>>>>>>>>>>>>>>>>>>> >> try it out, but all of the T60's I've played >>>>>>>>>>>>>>>>>>>>>>>>> with thus far have the >>>>>>>>>>>>>>>>>>>>>>>>> >> intel hardware in it. >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> Adrian >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>>>>>>>>>> >> On 21 June 2013 02:02, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>> Hello Adrian, >>>>>>>>>>>>>>>>>>>>>>>>> >>> >>>>>>>>>>>>>>>>>>>>>>>>> >>> Do you have any feedback on the matter? >>>>>>>>>>>>>>>>>>>>>>>>> >>> >>>>>>>>>>>>>>>>>>>>>>>>> >>> Regards, >>>>>>>>>>>>>>>>>>>>>>>>> >>> >>>>>>>>>>>>>>>>>>>>>>>>> >>> Lyubomir >>>>>>>>>>>>>>>>>>>>>>>>> >>> >>>>>>>>>>>>>>>>>>>>>>>>> >>> >>>>>>>>>>>>>>>>>>>>>>>>> >>> On 13 June 2013 10:09, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>> Hello Adrian, >>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>> I enabled acpi_ibm.ko but this didn't help >>>>>>>>>>>>>>>>>>>>>>>>> and after "halt" the wifi is >>>>>>>>>>>>>>>>>>>>>>>>> >>>> not working again. >>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>> Regards, >>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>> Lyubomir >>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>> On 13 June 2013 08:03, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Hello Adrian, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> I did some tests and discovered that the >>>>>>>>>>>>>>>>>>>>>>>>> problem is related to >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> "halt"/"shutdown" of system. If "reboot" is >>>>>>>>>>>>>>>>>>>>>>>>> carried out than there is >>>>>>>>>>>>>>>>>>>>>>>>> >> no >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> problem and the wifi works properly (even if >>>>>>>>>>>>>>>>>>>>>>>>> done from Gnome - Gnome >>>>>>>>>>>>>>>>>>>>>>>>> >> seems >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> to have no relation to the problem). So what >>>>>>>>>>>>>>>>>>>>>>>>> could lead to "ath0: time >>>>>>>>>>>>>>>>>>>>>>>>> >> out" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> after shutting down or halting the system? I >>>>>>>>>>>>>>>>>>>>>>>>> noticed that there are irq >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> storms on irq 17 which is the wifi irq >>>>>>>>>>>>>>>>>>>>>>>>> (interrupt storm detected on >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> "irq17:"; throttling interrupt source). >>>>>>>>>>>>>>>>>>>>>>>>> Something else that I am not >>>>>>>>>>>>>>>>>>>>>>>>> >> sure to >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> have relevance - after shutdown during the >>>>>>>>>>>>>>>>>>>>>>>>> start-up ath0 is reported >>>>>>>>>>>>>>>>>>>>>>>>> >> to use >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> autoselect mode 11g: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> (below is from dmesg) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> ath0: >>>>>>>>>>>>>>>>>>>>>>>>> flags=8843 metric 0 mtu >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> 2290 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> ether 00:19:7e:91:xx:xx >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> nd6 >>>>>>>>>>>>>>>>>>>>>>>>> options=29 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> media: IEEE 802.11 Wireless Ethernet >>>>>>>>>>>>>>>>>>>>>>>>> autoselect mode 11g >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> status: associated >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> After the boot has finished the mode changes >>>>>>>>>>>>>>>>>>>>>>>>> to 11a: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> #ifconfig ath0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> ath0: >>>>>>>>>>>>>>>>>>>>>>>>> flags=8843 metric 0 mtu >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> 2290 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> ether 00:19:7e:91:xx:xx >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> nd6 >>>>>>>>>>>>>>>>>>>>>>>>> options=29 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> media: IEEE 802.11 Wireless Ethernet >>>>>>>>>>>>>>>>>>>>>>>>> autoselect mode 11a >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> status: associated >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Do you have any idea where to look for now? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Regards, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Lyubomir >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> P.S. I will try to play with acpi_ibm.ko and >>>>>>>>>>>>>>>>>>>>>>>>> see if things change if I >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> make it auto-load. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>> On 10 June 2013 16:06, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> Hello Adrian, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> Attached are files with consecutive vmstat >>>>>>>>>>>>>>>>>>>>>>>>> -i when the wlan is working >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> (vmstat-i_working.txt) and when the wlan is >>>>>>>>>>>>>>>>>>>>>>>>> not working >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> (vmstat-i_not_working.txt). There is also >>>>>>>>>>>>>>>>>>>>>>>>> output from ifconfig when >>>>>>>>>>>>>>>>>>>>>>>>> >> the wlan >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> is not working (ifconfig.txt). >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> After some more deeper investigation it >>>>>>>>>>>>>>>>>>>>>>>>> seems to me that the problem >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> appears after starting X with Gnome. I will >>>>>>>>>>>>>>>>>>>>>>>>> continue investigating >>>>>>>>>>>>>>>>>>>>>>>>> >> with >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> "reboot"/"halt -p" and inform you. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> BTW do you think that starting Gnome >>>>>>>>>>>>>>>>>>>>>>>>> session (using startx, as I >>>>>>>>>>>>>>>>>>>>>>>>> >> haven't >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> set auto start of X if this is of any >>>>>>>>>>>>>>>>>>>>>>>>> importance) can cause problems >>>>>>>>>>>>>>>>>>>>>>>>> >> - in >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> Gnome I have no settings for the network in >>>>>>>>>>>>>>>>>>>>>>>>> the "System->Network" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> application and I start it with normal user? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> Regards, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> Lyubo >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> On 9 June 2013 18:28, Adrian Chadd < >>>>>>>>>>>>>>>>>>>>>>>>> adrian@freebsd.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> Can you please paste the vmstat -i output? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> adrian >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> On 9 June 2013 06:53, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> Hi, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> After restart from Windows and working >>>>>>>>>>>>>>>>>>>>>>>>> wireless the number of >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> interrupts >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> increases and the rate increases. After >>>>>>>>>>>>>>>>>>>>>>>>> next restart (the ath0 >>>>>>>>>>>>>>>>>>>>>>>>> >> times >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> out) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> the interrupts increase but the rate is >>>>>>>>>>>>>>>>>>>>>>>>> going down. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> I noticed that after restart from Windows >>>>>>>>>>>>>>>>>>>>>>>>> and working wifi if I >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> restart >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> /etc/rc.d/netif the wifi is working >>>>>>>>>>>>>>>>>>>>>>>>> again. If I shutdown wlan0 and >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> bring it >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> up again then I wlan0 doesn't get address >>>>>>>>>>>>>>>>>>>>>>>>> but ath0 is not timing >>>>>>>>>>>>>>>>>>>>>>>>> >> out. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> I can >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> still get a list with the available APs >>>>>>>>>>>>>>>>>>>>>>>>> around. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> Regards, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> Lyubo >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> On 8 June 2013 18:28, Adrian Chadd < >>>>>>>>>>>>>>>>>>>>>>>>> adrian@freebsd.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> Hm! >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> Ok, this should be working. I frequently >>>>>>>>>>>>>>>>>>>>>>>>> test (read: every other >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> day) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> with the AR5416. But you're not the >>>>>>>>>>>>>>>>>>>>>>>>> first person to report this >>>>>>>>>>>>>>>>>>>>>>>>> >> bug. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> Unfortunately when this happens, the >>>>>>>>>>>>>>>>>>>>>>>>> interrupts aren't actually >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> making >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> it to the OS. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> Can you check the output of vmstat -i >>>>>>>>>>>>>>>>>>>>>>>>> whilst you're doing it? The >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> ath0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> counter should be increasing. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> adrian >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> On 8 June 2013 06:49, Lyubomir Yotov < >>>>>>>>>>>>>>>>>>>>>>>>> l.yotov@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> I have a Thinkpad T60 with dual boot >>>>>>>>>>>>>>>>>>>>>>>>> between Windows XP and >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> FreeBSD >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 9.1-Release: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> uname -a >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> FreeBSD T60.workgroup 9.1-RELEASE >>>>>>>>>>>>>>>>>>>>>>>>> FreeBSD 9.1-RELEASE #0 >>>>>>>>>>>>>>>>>>>>>>>>> >> r243826: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Tue >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Dec >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 4 06:55:39 UTC 2012 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> root@obrian.cse.buffalo.edu: >>>>>>>>>>>>>>>>>>>>>>>>> /usr/obj/usr/src/sys/GENERIC >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> i386 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> I am trying to use my wifi card which >>>>>>>>>>>>>>>>>>>>>>>>> is: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> dmesg >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> .... >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ath0: mem >>>>>>>>>>>>>>>>>>>>>>>>> 0xedf00000-0xedf0ffff irq 17 at device >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 0.0 on >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> pci3 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ath0: AR5418 mac 12.10 RF5133 phy 8.1 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> .... >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> pciconf -lv >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> .... >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ath0@pci0:3:0:0: class=0x028000 >>>>>>>>>>>>>>>>>>>>>>>>> card=0x0033168c >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> chip=0x0024168c >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> rev=0x01 hdr=0x00 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> vendor = 'Atheros >>>>>>>>>>>>>>>>>>>>>>>>> Communications Inc.' >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> device = 'AR5008 Wireless >>>>>>>>>>>>>>>>>>>>>>>>> Network Adapter' >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> class = network >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ..... >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> I followed several HOW-TOs in order to >>>>>>>>>>>>>>>>>>>>>>>>> make it work. >>>>>>>>>>>>>>>>>>>>>>>>> >> Unfortunately >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> I it >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> is >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> working only after I reboot from my >>>>>>>>>>>>>>>>>>>>>>>>> Windows installation >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> (regardless of >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> position of the wifi switch on the >>>>>>>>>>>>>>>>>>>>>>>>> front panel of the notebook). >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> After >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> restart from Windows everything is fine >>>>>>>>>>>>>>>>>>>>>>>>> - the wifi associates >>>>>>>>>>>>>>>>>>>>>>>>> >> with >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> AP >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> and I can use it. If I reboot the >>>>>>>>>>>>>>>>>>>>>>>>> system during the boot and >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> afterwards >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> I >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> constantly get: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ath0: device timeout >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> When I get the device status through >>>>>>>>>>>>>>>>>>>>>>>>> ifconfig I can see that >>>>>>>>>>>>>>>>>>>>>>>>> >> ath0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> is >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> associated but wlan0 is not associated. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ifconfig ath0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ath0: >>>>>>>>>>>>>>>>>>>>>>>>> flags=8843 metric >>>>>>>>>>>>>>>>>>>>>>>>> >> 0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> mtu >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 2290 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ether 00:19:7e:91:xx:xx >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> nd6 >>>>>>>>>>>>>>>>>>>>>>>>> options=29 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> media: IEEE 802.11 Wireless >>>>>>>>>>>>>>>>>>>>>>>>> Ethernet autoselect mode 11g >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> status: associated >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ifconfig wlan0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> wlan0: >>>>>>>>>>>>>>>>>>>>>>>>> flags=8843 >>>>>>>>>>>>>>>>>>>>>>>>> >> metric 0 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> mtu >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 1500 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ether 00:19:7e:91:xx:xx >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> nd6 >>>>>>>>>>>>>>>>>>>>>>>>> options=29 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> media: IEEE 802.11 Wireless >>>>>>>>>>>>>>>>>>>>>>>>> Ethernet autoselect >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> (autoselect) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> status: no carrier >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ssid "" channel 5 (2432 MHz 11g) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> regdomain 98 indoor ecm >>>>>>>>>>>>>>>>>>>>>>>>> authmode WPA privacy ON deftxkey >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> UNDEF >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> txpower 20 bmiss 7 scanvalid >>>>>>>>>>>>>>>>>>>>>>>>> 450 bgscan bgscanintvl 300 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> bgscanidle >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 250 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> roam:rssi 7 roam:rate 5 >>>>>>>>>>>>>>>>>>>>>>>>> protmode CTS wme burst roaming >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> MANUAL >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> In /var/log/messages I get: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Jun 8 16:39:16 PC >>>>>>>>>>>>>>>>>>>>>>>>> wpa_supplicant[3463]: Trying to associate >>>>>>>>>>>>>>>>>>>>>>>>> >> with >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 54:e6:fc:ae:xx:xx (SSID='access1' >>>>>>>>>>>>>>>>>>>>>>>>> freq=2432 MHz) >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Jun 8 16:39:20 PC kernel: ath0: device >>>>>>>>>>>>>>>>>>>>>>>>> timeout >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Jun 8 16:39:26 PC >>>>>>>>>>>>>>>>>>>>>>>>> wpa_supplicant[3463]: Authentication with >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 54:e6:fc:ae:xx:xx timed out. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> If I scan for wireless networks I get a >>>>>>>>>>>>>>>>>>>>>>>>> list and my ap is in the >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> list >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ifconfig wlan0 scan >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> SSID/MESH ID BSSID CHAN >>>>>>>>>>>>>>>>>>>>>>>>> RATE S:N INT CAPS >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> net1 00:11:11:01:xx:xx 6 54M >>>>>>>>>>>>>>>>>>>>>>>>> -68:-96 100 EP >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> 5edf9c 70:71:bc:26:xx:xx 11 >>>>>>>>>>>>>>>>>>>>>>>>> 54M -68:-96 100 EP >>>>>>>>>>>>>>>>>>>>>>>>> >> WPS >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> WPA >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> WME >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> access1 54:e6:fc:ae:xx:xx 5 >>>>>>>>>>>>>>>>>>>>>>>>> 54M -66:-96 100 EP WPA >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> HTCAP >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> WME >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> In rc.local I have: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> wlans_ath0="wlan0" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ifconfig_wlan0="WPA DHCP" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> In wpa_supplicant I have: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ctrl_interface=/var/run/wpa_supplicant >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> eapol_version=2 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ap_scan=1 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> fast_reauth=1 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> network={ >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ssid="access1" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> psk="secret1" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> priority=5 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> } >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> network={ >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> ssid="access2" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> psk="secret2" >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> priority=5 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> } >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> I searched the net for solution to my >>>>>>>>>>>>>>>>>>>>>>>>> problem but I couldn't >>>>>>>>>>>>>>>>>>>>>>>>> >> find >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> one. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Can >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> you help me with this? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> Lyubomir >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> freebsd-mobile@freebsd.org mailing list >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> To unsubscribe, send any mail to >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>> "freebsd-mobile-unsubscribe@freebsd.org >>>>>>>>>>>>>>>>>>>>>>>>> " >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> > _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>> > freebsd-wireless@freebsd.org mailing list >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>>>>>>>>>>>>>>>>>>>>>>> > To unsubscribe, send any mail to " >>>>>>>>>>>>>>>>>>>>>>>>> freebsd-wireless-unsubscribe@freebsd.org" >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > From owner-freebsd-wireless@FreeBSD.ORG Sun May 11 23:57:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB5C372A for ; Sun, 11 May 2014 23:57:43 +0000 (UTC) Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8054521CF for ; Sun, 11 May 2014 23:57:43 +0000 (UTC) Received: by mail-yk0-f176.google.com with SMTP id q9so5337563ykb.7 for ; Sun, 11 May 2014 16:57:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=AuAyZ3BPJNSbeiJ/iD66am7hnEDrBi86XMOe/33GEbs=; b=D5/TPsEg40CpFMg/v3EBzrYdTrB01gQtrP81DfIIK1C/zS8EOc+PZm+vrLZR2iE6ac lzzf6RJabTLNYqUMfUKB9H6f82QYg+hUoHmJGbSrYMh72BNUn2+vOw+TFcXYo/VOnblK PJ2f7+mrhjW/PrQAtpMQxuQNStuVV1ddFogA+haD/hWypc9deqkejBy33RlBT8k84Obg 7bRhwMU8VhJSEac5hJvRSdHYtl5LtFAKMLflsGpMJHPqLHqLP9wDuhOI72CkKZX4xd/P te2N/St/7r6M9zEXklaUvfBpjJ3eP4WYkUFr3sqg0ILoJhD5aqEMNkRzsVMudFmUh+r3 4A6w== X-Received: by 10.236.172.170 with SMTP id t30mr36474808yhl.136.1399852662554; Sun, 11 May 2014 16:57:42 -0700 (PDT) Received: from zhabar.att.net (107-222-186-3.lightspeed.sntcca.sbcglobal.net. [107.222.186.3]) by mx.google.com with ESMTPSA id r27sm5579525yhk.17.2014.05.11.16.57.42 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Sun, 11 May 2014 16:57:42 -0700 (PDT) Date: Sun, 11 May 2014 16:57:39 -0700 From: Justin Hibbits To: Subject: Machine check on suspend Message-ID: <20140511165739.45671291@zhabar.att.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; powerpc64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2014 23:57:43 -0000 Obviously this is a different case than most. I'm working on suspend/resume for PowerPC (PowerBooks, to be precise), and part of that involves testing the cardbus. When suspending, it suspends children first (obviously), followed by parents, etc. In this case, I have a ar5416 card in a cardbus slot. The ath0 suspends, followed by cbb0, then a machine check: Suspending ath0, child of cardbus0 Suspending cardbus0, child of cbb0 pci1:1:0:0: Resource still owned, oops. (type=3, rid=16, addr=88000000) pci1:1:0:0: Resource still owned, oops. (type=1, rid=0, addr=3a) fatal kernel trap: exception = 0x200 (machine check) srr0 = 0x5d5530 srr1 = 0x149030 lr = 0xd20896f8 curthread = 0x4c6e620 pid = 12, comm = irq58: cbb0 ath0 [ thread pid 12 tid 100108 ] Stopped at 0x5d5530: sync db> bt Tracing pid 12 tid 100108 td 0x4c6e620 0xe4770a20: at +0x226530(326cbc) 0xe4770a50: at ar5416IsInterruptPending+0x3c(d20ca368) 0xe4770a70: at ath_intr+0xf0(d2064ef4) 0xe4770ab0: at cbb_func_intr+0x40(d1fd71b4) 0xe4770ad0: at +0x2074d4(307c60) 0xe4770b00: at +0x209034(3097c0) 0xe4770b50: at +0x203e78(304604) 0xe4770b80: at +0x4e4b70(5e52fc) I'm using the projects/pmac_pmu branch, for anyone who may want to test (synced with head a couple weeks ago). Does anything need to be done before actually suspending the devices (kill wpa_supplicant, or anything else)? - Justin From owner-freebsd-wireless@FreeBSD.ORG Mon May 12 00:05:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A850B853 for ; Mon, 12 May 2014 00:05:12 +0000 (UTC) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B5FF2274 for ; Mon, 12 May 2014 00:05:12 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id e16so6891428qcx.41 for ; Sun, 11 May 2014 17:05:11 -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=+nJkWjtBzi7k34CJm9NsSYaAhBeWJBQAvUBjvg8bdvo=; b=gRlFa4QyfvKtiAnkNOLmhv11IsnhbXvPcTJg7yt6NM2/R+BaiDQFnwrXBsF5SUiJrv gvxdLPnAMZkFqWNpyUWuyVln9/EXfijudSrlwqOMVNhCnHrH+349fh2LsNXAkwmWZOaI gc05MRiDFXqGeOx0hTyP9N7Ze6AnCIsRfgE05Kb7wkIDOePztAc/nzfr7KG/you92lwc euRYGdNPx/kyiQx+oDygj9v7ceqqfqkey2SNxc04XbOLqIZOc3mJRSPBDSuoTWDfyV5N q7lK6TNUJzpDRxvNGZJ3BFvojVnp3u1V8NqM+GgTsiI2cgctuDpUS/sPycasvPOY05X5 jDrg== MIME-Version: 1.0 X-Received: by 10.224.125.74 with SMTP id x10mr6504200qar.99.1399853102106; Sun, 11 May 2014 17:05:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Sun, 11 May 2014 17:05:02 -0700 (PDT) In-Reply-To: <20140511165739.45671291@zhabar.att.net> References: <20140511165739.45671291@zhabar.att.net> Date: Sun, 11 May 2014 17:05:02 -0700 X-Google-Sender-Auth: UHUc2yhN7y-i_BCNmiBuKhFhWkc Message-ID: Subject: Re: Machine check on suspend From: Adrian Chadd To: Justin Hibbits Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 00:05:12 -0000 It's getting an interrupt what, after the slot is powered down? Why's cbb_func_intr passing up an interrupt? :p -a On 11 May 2014 16:57, Justin Hibbits wrote: > Obviously this is a different case than most. I'm working on > suspend/resume for PowerPC (PowerBooks, to be precise), and part of > that involves testing the cardbus. > > When suspending, it suspends children first (obviously), followed by > parents, etc. In this case, I have a ar5416 card in a cardbus slot. > The ath0 suspends, followed by cbb0, then a machine check: > > Suspending ath0, child of cardbus0 > Suspending cardbus0, child of cbb0 > pci1:1:0:0: Resource still owned, oops. (type=3, rid=16, addr=88000000) > pci1:1:0:0: Resource still owned, oops. (type=1, rid=0, addr=3a) > > fatal kernel trap: > > exception = 0x200 (machine check) > srr0 = 0x5d5530 > srr1 = 0x149030 > lr = 0xd20896f8 > curthread = 0x4c6e620 > pid = 12, comm = irq58: cbb0 ath0 > > [ thread pid 12 tid 100108 ] > Stopped at 0x5d5530: sync > db> bt > Tracing pid 12 tid 100108 td 0x4c6e620 > 0xe4770a20: at +0x226530(326cbc) > 0xe4770a50: at ar5416IsInterruptPending+0x3c(d20ca368) > 0xe4770a70: at ath_intr+0xf0(d2064ef4) > 0xe4770ab0: at cbb_func_intr+0x40(d1fd71b4) > 0xe4770ad0: at +0x2074d4(307c60) > 0xe4770b00: at +0x209034(3097c0) > 0xe4770b50: at +0x203e78(304604) > 0xe4770b80: at +0x4e4b70(5e52fc) > > I'm using the projects/pmac_pmu branch, for anyone who may want to test > (synced with head a couple weeks ago). > > Does anything need to be done before actually suspending the devices > (kill wpa_supplicant, or anything else)? > > - Justin > _______________________________________________ > 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 Mon May 12 00:22:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 563FAE3F; Mon, 12 May 2014 00:22:02 +0000 (UTC) Received: from mail-yk0-x22f.google.com (mail-yk0-x22f.google.com [IPv6:2607:f8b0:4002:c07::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09A4F23C0; Mon, 12 May 2014 00:22:01 +0000 (UTC) Received: by mail-yk0-f175.google.com with SMTP id 131so5329246ykp.34 for ; Sun, 11 May 2014 17:22:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=4tjK+iaHRAt7P76tqww2GBQJGWYiVL6/lmhlc81Gw0o=; b=El0EgpkhkmDMJJvKnOXNc1rA39M94spQeRxEZgBO6h9d90kFMZU6QpSiWyA1FeJEpO OU8t1mxar/xOiX/UXcq4M3zDC0MNQvrZ/d0W3IOB6DUPBpkkxu/MhAOeIu0W7jWjabFo 5vcbbTxd3rEHdXX9LT/7X8HyEtKN4xZpkYUM2FJ3/9EhgblVaFTILTW4MQ7IhQS4jPAn cYFpUK1X5DpL3bXEyWyXbMLVfrTpk036kTlOxIPOypn2s87wWOWDIDRqVaI5KUHMymzf DQgEdpx3fImhjvR0rOmNO46BC+8jVc+KSakQAshSRi/rCisyWMKGOPwCM/grIv57pUDc UgSg== X-Received: by 10.236.124.237 with SMTP id x73mr35763230yhh.137.1399854121242; Sun, 11 May 2014 17:22:01 -0700 (PDT) Received: from zhabar.att.net (107-222-186-3.lightspeed.sntcca.sbcglobal.net. [107.222.186.3]) by mx.google.com with ESMTPSA id 63sm17198037yhi.13.2014.05.11.17.22.00 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Sun, 11 May 2014 17:22:01 -0700 (PDT) Date: Sun, 11 May 2014 17:21:57 -0700 From: Justin Hibbits To: Adrian Chadd Subject: Re: Machine check on suspend Message-ID: <20140511172157.175a3ab2@zhabar.att.net> In-Reply-To: References: <20140511165739.45671291@zhabar.att.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; powerpc64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 00:22:02 -0000 On Sun, 11 May 2014 17:05:02 -0700 Adrian Chadd wrote: > It's getting an interrupt what, after the slot is powered down? That's what it looks like. > > Why's cbb_func_intr passing up an interrupt? :p Your guess is as good as mine. I don't disable interrupts yet, but I do lock Giant (means little these days, of course). cbb_func_intr() is supposed to handle the device going away between interrupt firing and the function being called. - Justin > > > -a > > > On 11 May 2014 16:57, Justin Hibbits wrote: > > Obviously this is a different case than most. I'm working on > > suspend/resume for PowerPC (PowerBooks, to be precise), and part of > > that involves testing the cardbus. > > > > When suspending, it suspends children first (obviously), followed by > > parents, etc. In this case, I have a ar5416 card in a cardbus slot. > > The ath0 suspends, followed by cbb0, then a machine check: > > > > Suspending ath0, child of cardbus0 > > Suspending cardbus0, child of cbb0 > > pci1:1:0:0: Resource still owned, oops. (type=3, rid=16, > > addr=88000000) pci1:1:0:0: Resource still owned, oops. (type=1, > > rid=0, addr=3a) > > > > fatal kernel trap: > > > > exception = 0x200 (machine check) > > srr0 = 0x5d5530 > > srr1 = 0x149030 > > lr = 0xd20896f8 > > curthread = 0x4c6e620 > > pid = 12, comm = irq58: cbb0 ath0 > > > > [ thread pid 12 tid 100108 ] > > Stopped at 0x5d5530: sync > > db> bt > > Tracing pid 12 tid 100108 td 0x4c6e620 > > 0xe4770a20: at +0x226530(326cbc) > > 0xe4770a50: at ar5416IsInterruptPending+0x3c(d20ca368) > > 0xe4770a70: at ath_intr+0xf0(d2064ef4) > > 0xe4770ab0: at cbb_func_intr+0x40(d1fd71b4) > > 0xe4770ad0: at +0x2074d4(307c60) > > 0xe4770b00: at +0x209034(3097c0) > > 0xe4770b50: at +0x203e78(304604) > > 0xe4770b80: at +0x4e4b70(5e52fc) > > > > I'm using the projects/pmac_pmu branch, for anyone who may want to > > test (synced with head a couple weeks ago). > > > > Does anything need to be done before actually suspending the devices > > (kill wpa_supplicant, or anything else)? > > > > - Justin > > _______________________________________________ > > 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 Mon May 12 11:06:54 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7627DC58 for ; Mon, 12 May 2014 11:06:54 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A5C226E6 for ; Mon, 12 May 2014 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4CB6sor068027 for ; Mon, 12 May 2014 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4CB6rid068024 for freebsd-wireless@FreeBSD.org; Mon, 12 May 2014 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 May 2014 11:06:53 GMT Message-Id: <201405121106.s4CB6rid068024@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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/189405 wireless [run] [wlan] hostapd, kernel panic, wlan using run dev o kern/188654 wireless [urtwn] tp-link wl-725n Realtek 8188 chip do not work o kern/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o bin/187624 wireless [patch] wpa_supplicant(8): WEP and other ciphers do no o bin/187470 wireless [bthidd] [patch] Apple Wireless Keyboard (JIS) o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] [panic] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP fails, WPA o kern/185025 wireless [iwi] [panic] iwi driver panic on 10.0rc2 f usb/184918 wireless [ural] regression on WEP o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181694 wireless [iwn] [suspend/resume] [patch] Initialize hardware in o kern/181161 wireless [wl] [panic] config a old compaq wl-110 wireless card 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/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/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/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/168754 wireless [ath] if_ath dont have internal name o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless [ath] [suspend/resume] 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/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] kernel panic: page fault with ath0 taskq 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 195 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed May 14 14:00:02 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5540A3C7 for ; Wed, 14 May 2014 14:00:02 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2873E2276 for ; Wed, 14 May 2014 14:00:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4EE01i3080394 for ; Wed, 14 May 2014 14:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4EE017Q080393; Wed, 14 May 2014 14:00:01 GMT (envelope-from gnats) Date: Wed, 14 May 2014 14:00:01 GMT Message-Id: <201405141400.s4EE017Q080393@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Anton Shterenlikht Subject: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Reply-To: Anton Shterenlikht X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2014 14:00:02 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: Anton Shterenlikht To: bug-followup@freebsd.org Cc: Subject: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Wed, 14 May 2014 14:54:22 +0100 (BST) See also http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/189802 Seems iwn causes panic now. From owner-freebsd-wireless@FreeBSD.ORG Fri May 16 20:05:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D008A6B; Fri, 16 May 2014 20:05:57 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0B5A23A9; Fri, 16 May 2014 20:05:56 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id q107so4950034qgd.38 for ; Fri, 16 May 2014 13:05:55 -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=BoGSO8VQMODqNOzZiJ4YopPNtZDFdWt/Ak/pYRv1vGg=; b=iRvhhyouh0fdq8CrOJYXY+8G6eQBDofAUYdIiFY7TCxx7b+7BS3EUf1HstxzJbM/t4 qGTPnuvySwui2/83GMlFkYn+yBC6tvJ7KaiMMr2JZ1sjoyo5lxfIOOHdDzdM+PmxQjR5 xH1oX5MDnYQmRnThK3v48CNvkWepEx4I/l8E2zPfjqE2MthApEmOOy1Uh+zycE8jOvKb 87z4rQlvdsGyb6tHP5M4lD6IeGLmKqepsO3y9m741fxnSPmd8jGzPXaO8U0c9T9t28xJ 3K1Ipn3giwLlQKSt43I2EyVjC4CL1X+vVhmtEF70wruhqeVX98Q/fdaGxoFG8ReDBSzQ R1sA== MIME-Version: 1.0 X-Received: by 10.229.97.71 with SMTP id k7mr29246238qcn.4.1400270755868; Fri, 16 May 2014 13:05:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 16 May 2014 13:05:55 -0700 (PDT) In-Reply-To: <201405161821.s4GILXit029854@mech-cluster241.men.bris.ac.uk> References: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org> <201405161821.s4GILXit029854@mech-cluster241.men.bris.ac.uk> Date: Fri, 16 May 2014 13:05:55 -0700 X-Google-Sender-Auth: qFBMNU3xQU3dEenwFLJDhm-q5Cw Message-ID: Subject: Re: Workaround for "fatal firmware error" iwn(4) problem. From: Adrian Chadd To: mexas@bris.ac.uk, "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 20:05:57 -0000 It's likely part the firmware and pat the driver. Yeah, we need a way to recover from a firmware crash. I and others in the open source community don't have documentation to know what the hell is or isn't permissable with firmware :( Ed - the reason why ieee80211_runtask() doesn't always run is because it can get paused during things like scanning and interface-down things. Your best bet is to create a new taskqueue in iwn and a task that runs on an iwn taskqueue. (And yeah, I really do need to rip out the taskqueue abuse by the net80211 scan code so a scan doesn't stop tasks from running. Grr.) -a On 16 May 2014 11:21, Anton Shterenlikht wrote: >>From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= >>Subject: Workaround for "fatal firmware error" iwn(4) problem. >>Date: Fri, 16 May 2014 20:06:02 +0200 >>To: "freebsd-hackers@freebsd.org" >> >>I've started using FreeBSD laptop and iwn(4) failing at random moments >>like this... > > see also > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/176104 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/189802 > > BTW, I disabled iwn and tried pccard bwn device instead, > and the errors are gone. Also wireless doesn't disconnect > as it used to with iwn. This is just because I thought > my laptop or setup were to blame. So this is further > evidence that iwn driver is at fault. > > Anton > _______________________________________________ > 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 Mon May 19 11:06:56 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE531614 for ; Mon, 19 May 2014 11:06:55 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B15A52DD6 for ; Mon, 19 May 2014 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4JB6tuL080223 for ; Mon, 19 May 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4JB6tSX080220 for freebsd-wireless@FreeBSD.org; Mon, 19 May 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 May 2014 11:06:55 GMT Message-Id: <201405191106.s4JB6tSX080220@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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 11:06:56 -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/189405 wireless [run] [wlan] hostapd, kernel panic, wlan using run dev o kern/188654 wireless [urtwn] tp-link wl-725n Realtek 8188 chip do not work o kern/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o bin/187624 wireless [patch] wpa_supplicant(8): WEP and other ciphers do no o bin/187470 wireless [bthidd] [patch] Apple Wireless Keyboard (JIS) o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] [panic] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP fails, WPA o kern/185025 wireless [iwi] [panic] iwi driver panic on 10.0rc2 f usb/184918 wireless [ural] regression on WEP o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181694 wireless [iwn] [suspend/resume] [patch] Initialize hardware in o kern/181161 wireless [wl] [panic] config a old compaq wl-110 wireless card 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/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/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/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/168754 wireless [ath] if_ath dont have internal name o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless [ath] [suspend/resume] 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/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] kernel panic: page fault with ath0 taskq 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 195 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon May 19 18:25:51 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9432B25; Mon, 19 May 2014 18:25:51 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B79D279D; Mon, 19 May 2014 18:25:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4JIPpdk027278; Mon, 19 May 2014 18:25:51 GMT (envelope-from allanjude@freefall.freebsd.org) Received: (from allanjude@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4JIPpoE027277; Mon, 19 May 2014 18:25:51 GMT (envelope-from allanjude) Date: Mon, 19 May 2014 18:25:51 GMT Message-Id: <201405191825.s4JIPpoE027277@freefall.freebsd.org> To: sbruno@freebsd.org, allanjude@FreeBSD.org, freebsd-wireless@FreeBSD.org From: allanjude@FreeBSD.org Subject: Re: bin/187624: [patch] wpa_supplicant(8): WEP and other ciphers do not work if h/w driver does not declare support [regression] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 18:25:51 -0000 Synopsis: [patch] wpa_supplicant(8): WEP and other ciphers do not work if h/w driver does not declare support [regression] State-Changed-From-To: open->closed State-Changed-By: allanjude State-Changed-When: Mon May 19 18:24:55 UTC 2014 State-Changed-Why: Fixed in head r263925 Sean and I discovered this at AsiaBSDCon and a fix was commited by rpaulo http://www.freebsd.org/cgi/query-pr.cgi?pr=187624 From owner-freebsd-wireless@FreeBSD.ORG Mon May 19 21:21:42 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D6DE92B; Mon, 19 May 2014 21:21:42 +0000 (UTC) Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBAE9299E; Mon, 19 May 2014 21:21:41 +0000 (UTC) Received: by mail-yk0-f177.google.com with SMTP id 19so4995431ykq.36 for ; Mon, 19 May 2014 14:21:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=SJBP7n+xLb6PGSFqedUjTD/zYOAlWIiyYJfxtzPqy5Y=; b=Di97SdPyhPLcnd9V6dtxrL/CygZlGw3S4Sq9Oi4wrjHjRHp3XfmwZHJUkOMxzUGS06 UFHDfWXHIkkYNC0EFrmtmiE/eGICUWS51oMuH8ceBe6qS7IhoF6glyyOzmgFj9+zVjNL vCYQpvcIJFrIC7cc5xj6qdjffCgp+SFKobgDqG/npQGJsZRVwqFsuBe/Fc1d8gDmSZj8 Il/1iHdoV+ugf6Lofeqpt8DA/iOQ7NarAdxVjexwnglVNcC+v8m7/C0GWDgikeHxdz5a bqebERv8XtIt5ZVvjPhDAkSmV/5iHwDQJwxjU2GKnaDmPSx94MOaOpUF4tjQQm5YvRjs qiMg== MIME-Version: 1.0 X-Received: by 10.236.112.37 with SMTP id x25mr57851850yhg.26.1400534501097; Mon, 19 May 2014 14:21:41 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Mon, 19 May 2014 14:21:41 -0700 (PDT) Date: Mon, 19 May 2014 23:21:41 +0200 Message-ID: Subject: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: freebsd-usb@freebsd.org, freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: hps@bitfrost.no X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 21:21:42 -0000 ..while running a kernel that has rsu_debug set to >0. Line 1712: "fault virtual address = 0xffff804000000000" core0.txt -> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt HTH, Idwer From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 05:46:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67FD8D34; Tue, 20 May 2014 05:46:54 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 26E482E94; Tue, 20 May 2014 05:46:53 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 986B11FE029; Tue, 20 May 2014 07:46:48 +0200 (CEST) Message-ID: <537AEC79.6080406@selasky.org> Date: Tue, 20 May 2014 07:47:37 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering , freebsd-usb@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hps@bitfrost.no X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 05:46:54 -0000 On 05/19/14 23:21, Idwer Vollering wrote: > ..while running a kernel that has rsu_debug set to >0. > > Line 1712: "fault virtual address = 0xffff804000000000" > core0.txt -> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt > > HTH, Hi, Does this patch make any difference? --HPS === ./if_rsu.c ================================================================== --- ./if_rsu.c (revision 266400) +++ ./if_rsu.c (local) @@ -423,8 +423,6 @@ struct ifnet *ifp = sc->sc_ifp; struct ieee80211com *ic = ifp->if_l2com; - if (!device_is_attached(self)) - return (0); rsu_stop(ifp, 1); usbd_transfer_unsetup(sc->sc_xfer, RSU_N_TRANSFER); ieee80211_ifdetach(ic); From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 12:13:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6652E892; Tue, 20 May 2014 12:13:02 +0000 (UTC) Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E1B12ECC; Tue, 20 May 2014 12:13:02 +0000 (UTC) Received: by mail-yh0-f47.google.com with SMTP id z6so251178yhz.6 for ; Tue, 20 May 2014 05:13:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5Ww9n81ADjuM1GSBC+jODb9T9cXCG9aOk5b1/qjQx9g=; b=vbHcaP5LpZCFawO2FyhzHJOJsYk526OT2ApuU0WxX7cV7rAWXp8xJS4lmJCn0nARrg 2F2BZSGhwCAk+NGMvaEz/6i6m2hhgj2JN5dwm10r0lSLtOmF6V7QhfVEVgm/3JiPqj2A e4MK+ZlbIz1oKf8tei/W+Ilu7Ttgy2F4O6Trzz/IcFRxjbXsy7vihQ5AuglU/mq6mhdY FoWN6AFPoGhia/a94myiZ7bSanIEYdp5mz8I0T5MLcYOWnO5Xywxil7DjGgzRPaWsn7j Xsl04eECXfM4NWnF52qxWz/edyGS80N6ezj1viHfPXkxftz7uBlqp7n8SM148AQ0HDAZ oTzg== MIME-Version: 1.0 X-Received: by 10.236.25.10 with SMTP id y10mr26130204yhy.63.1400587981329; Tue, 20 May 2014 05:13:01 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Tue, 20 May 2014 05:13:01 -0700 (PDT) In-Reply-To: <537AEC79.6080406@selasky.org> References: <537AEC79.6080406@selasky.org> Date: Tue, 20 May 2014 14:13:01 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: hps@bitfrost.no, freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 12:13:02 -0000 2014-05-20 7:47 GMT+02:00 Hans Petter Selasky : > On 05/19/14 23:21, Idwer Vollering wrote: >> >> ..while running a kernel that has rsu_debug set to >0. >> >> Line 1712: "fault virtual address = 0xffff804000000000" >> core0.txt -> >> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt >> >> HTH, > > > Hi, > > Does this patch make any difference? Yes, this solves the panic. > > --HPS > > === ./if_rsu.c > ================================================================== > --- ./if_rsu.c (revision 266400) > +++ ./if_rsu.c (local) > @@ -423,8 +423,6 @@ > struct ifnet *ifp = sc->sc_ifp; > struct ieee80211com *ic = ifp->if_l2com; > > - if (!device_is_attached(self)) > - return (0); > rsu_stop(ifp, 1); > usbd_transfer_unsetup(sc->sc_xfer, RSU_N_TRANSFER); > ieee80211_ifdetach(ic); > From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 12:23:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32124C71; Tue, 20 May 2014 12:23:43 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E81EC2FAF; Tue, 20 May 2014 12:23:42 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0F59F1FE029; Tue, 20 May 2014 14:23:42 +0200 (CEST) Message-ID: <537B497E.8070701@selasky.org> Date: Tue, 20 May 2014 14:24:30 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 12:23:43 -0000 On 05/20/14 14:13, Idwer Vollering wrote: > 2014-05-20 7:47 GMT+02:00 Hans Petter Selasky : >> On 05/19/14 23:21, Idwer Vollering wrote: >>> >>> ..while running a kernel that has rsu_debug set to >0. >>> >>> Line 1712: "fault virtual address = 0xffff804000000000" >>> core0.txt -> >>> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt >>> >>> HTH, >> >> >> Hi, >> >> Does this patch make any difference? > > Yes, this solves the panic. > Hi, Please verify: http://svnweb.freebsd.org/changeset/base/266466 --HPS From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 13:31:36 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D81290 for ; Tue, 20 May 2014 13:31:36 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F6AF2575 for ; Tue, 20 May 2014 13:31:36 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Wmk8l-00061P-GZ for freebsd-wireless@freebsd.org; Tue, 20 May 2014 06:31:35 -0700 Date: Tue, 20 May 2014 06:31:35 -0700 (PDT) From: sergeylukin To: freebsd-wireless@freebsd.org Message-ID: <1400592695456-5913789.post@n5.nabble.com> In-Reply-To: <20131201171459.GA54266@bulldozer.local> References: <20131201171459.GA54266@bulldozer.local> Subject: Re: FreeBSD - Intel 7260 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 13:31:36 -0000 Are there any news on Intel 7260 support? Would love to help with testing. -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-Intel-7260-tp5865163p5913789.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 15:00:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 97F4650C; Tue, 20 May 2014 15:00:24 +0000 (UTC) Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EE042E42; Tue, 20 May 2014 15:00:24 +0000 (UTC) Received: by mail-yh0-f54.google.com with SMTP id i57so453157yha.13 for ; Tue, 20 May 2014 08:00:23 -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=LKR+2oz80BZlx3xJL5gdbeDJUwW4UwqaUTMetUnnMpA=; b=vSsnx2WOKpeW+G5xmVgNkmGtF45OG7cC/ItKLc/BLPVD6aYNygWtD25h2OpGnLeAUm BpMOZi9JZcLuwgXUMnkaALMmXNyuwFrJ0JIuZCocsxnfgmT3JxsL2y+L8E1rJ6NkTRGE ODxyB4PyzrduXhqhicokn87Ya6pBYY/UMasdBWsGnwSN2hzVG5iBtoPQ5OweLw4FNP7Y opq4B+JjX17z5wjKNRvrg0aNlbnZm7npZGwne9MS4xWo8IxI6gtd4GBzCkX0A+vkOlms XaHi36jX09mWQwK4nuTB+u7c+0o1vFd0eR5TgRd/oQbE4efLkiH5phRP4z1AQRz1pmGY vcRA== MIME-Version: 1.0 X-Received: by 10.236.46.225 with SMTP id r61mr63001722yhb.107.1400598023460; Tue, 20 May 2014 08:00:23 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Tue, 20 May 2014 08:00:23 -0700 (PDT) In-Reply-To: <537B497E.8070701@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> Date: Tue, 20 May 2014 17:00:23 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 15:00:24 -0000 2014-05-20 14:24 GMT+02:00 Hans Petter Selasky : > On 05/20/14 14:13, Idwer Vollering wrote: >> >> 2014-05-20 7:47 GMT+02:00 Hans Petter Selasky : >>> >>> On 05/19/14 23:21, Idwer Vollering wrote: >>>> >>>> >>>> ..while running a kernel that has rsu_debug set to >0. >>>> >>>> Line 1712: "fault virtual address = 0xffff804000000000" >>>> core0.txt -> >>>> >>>> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt >>>> >>>> HTH, >>> >>> >>> >>> Hi, >>> >>> Does this patch make any difference? >> >> >> Yes, this solves the panic. >> > > Hi, > > Please verify: > > http://svnweb.freebsd.org/changeset/base/266466 > > --HPS Looks good to me.. if only it wasn't panicking on insertion, again with rsu_debug set to anything greater than 0 (5, in this case). The panic on insertion is reproducable with otherwise unmodified r266465. Any thoughts? From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 15:04:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 723EE79B; Tue, 20 May 2014 15:04:53 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 32A5C2ED1; Tue, 20 May 2014 15:04:53 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 13FE01FE026; Tue, 20 May 2014 17:04:52 +0200 (CEST) Message-ID: <537B6F44.6070905@selasky.org> Date: Tue, 20 May 2014 17:05:40 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 15:04:53 -0000 On 05/20/14 17:00, Idwer Vollering wrote: > 2014-05-20 14:24 GMT+02:00 Hans Petter Selasky : >> On 05/20/14 14:13, Idwer Vollering wrote: >>> >>> 2014-05-20 7:47 GMT+02:00 Hans Petter Selasky : >>>> >>>> On 05/19/14 23:21, Idwer Vollering wrote: >>>>> >>>>> >>>>> ..while running a kernel that has rsu_debug set to >0. >>>>> >>>>> Line 1712: "fault virtual address = 0xffff804000000000" >>>>> core0.txt -> >>>>> >>>>> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt >>>>> >>>>> HTH, >>>> >>>> >>>> >>>> Hi, >>>> >>>> Does this patch make any difference? >>> >>> >>> Yes, this solves the panic. >>> >> >> Hi, >> >> Please verify: >> >> http://svnweb.freebsd.org/changeset/base/266466 >> >> --HPS > > Looks good to me.. if only it wasn't panicking on insertion, again > with rsu_debug set to anything greater than 0 (5, in this case). The > panic on insertion is reproducable with otherwise unmodified r266465. > Any thoughts? > Hi, Can you get the backtrace of this panic? --HPS From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 15:12:33 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DEC579CA; Tue, 20 May 2014 15:12:33 +0000 (UTC) Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 945352FCF; Tue, 20 May 2014 15:12:33 +0000 (UTC) Received: by mail-yk0-f179.google.com with SMTP id 19so447526ykq.38 for ; Tue, 20 May 2014 08:12:32 -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=LC4q8EEBWadKYdtbDr1P2BbXJtujiW4aAuSkUvZSqBg=; b=GwdX86+wujIHlN2tqSIP768jB4swPi3bfnoXIOH8IuU66aR0kqRPUPhJHMlV4/PLu9 B+HFoJ+la3XTv53QR7O+O4aY3uPjL2BSWe3cvUAKDiY6he+cMYR1/JBDZoe8kANCpwO0 dcU+YZ1vVoOOoqCSJvxoWVrdcC9omkvcLKK8z7GcYfGP74fPxMGueM+xJ6LJDHCQmuiy wKym+IctYdt+PfoZKscmktH9Kv+Ep6geRAQyzjAWYPfk8Ww4MAf1MnCx+7kvmehqu5tI KSYDKuIHaUtF3GZSNl7hOL91hWp/uiYj9fYlrz5ZS+tok6xEX9aLlzzjYAh6A8jLffya FzoA== MIME-Version: 1.0 X-Received: by 10.236.112.37 with SMTP id x25mr65556397yhg.26.1400598752826; Tue, 20 May 2014 08:12:32 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Tue, 20 May 2014 08:12:32 -0700 (PDT) In-Reply-To: <537B6F44.6070905@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> Date: Tue, 20 May 2014 17:12:32 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 15:12:34 -0000 2014-05-20 17:05 GMT+02:00 Hans Petter Selasky : > On 05/20/14 17:00, Idwer Vollering wrote: >> >> 2014-05-20 14:24 GMT+02:00 Hans Petter Selasky : >>> >>> On 05/20/14 14:13, Idwer Vollering wrote: >>>> >>>> >>>> 2014-05-20 7:47 GMT+02:00 Hans Petter Selasky : >>>>> >>>>> >>>>> On 05/19/14 23:21, Idwer Vollering wrote: >>>>>> >>>>>> >>>>>> >>>>>> ..while running a kernel that has rsu_debug set to >0. >>>>>> >>>>>> Line 1712: "fault virtual address = 0xffff804000000000" >>>>>> core0.txt -> >>>>>> >>>>>> >>>>>> http://ra.openbios.org/~idwer/freebsd/fbsd_10-stable_rsu_panic_core_0.txt >>>>>> >>>>>> HTH, >>>>> >>>>> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> Does this patch make any difference? >>>> >>>> >>>> >>>> Yes, this solves the panic. >>>> >>> >>> Hi, >>> >>> Please verify: >>> >>> http://svnweb.freebsd.org/changeset/base/266466 >>> >>> --HPS >> >> >> Looks good to me.. if only it wasn't panicking on insertion, again >> with rsu_debug set to anything greater than 0 (5, in this case). The >> panic on insertion is reproducable with otherwise unmodified r266465. >> Any thoughts? >> > > Hi, > > Can you get the backtrace of this panic? > > --HPS Hi, Certainly, here it is: http://ra.openbios.org/~idwer/freebsd/core.txt.9_fbsd_10-stable_rsu-panic-on-insertion Idwer From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 16:13:21 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ADD5B5AA for ; Tue, 20 May 2014 16:13:21 +0000 (UTC) Received: from mta04.bitpro.no (mta04.bitpro.no [92.42.64.203]) by mx1.freebsd.org (Postfix) with ESMTP id 698EE2599 for ; Tue, 20 May 2014 16:13:20 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta04.bitpro.no (Postfix) with ESMTPS id B76031001FD; Tue, 20 May 2014 17:55:25 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 3353E1E071B; Tue, 20 May 2014 17:55:35 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no Received: from mail.lockless.no ([127.0.0.1]) by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEplCI9+-NIj; Tue, 20 May 2014 17:55:25 +0200 (CEST) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) by mail.lockless.no (Postfix) with ESMTPSA id F32631E071A; Tue, 20 May 2014 17:55:24 +0200 (CEST) Message-ID: <537B7B15.8040505@bitfrost.no> Date: Tue, 20 May 2014 17:56:05 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 16:13:21 -0000 Hi, Is your kernel built clean with modules? --HPS From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 18:22:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7027FCB; Tue, 20 May 2014 18:22:04 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48B4B223A; Tue, 20 May 2014 18:22:04 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D30431FE026; Tue, 20 May 2014 20:22:00 +0200 (CEST) Message-ID: <537B9D78.3030103@selasky.org> Date: Tue, 20 May 2014 20:22:48 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> In-Reply-To: Content-Type: multipart/mixed; boundary="------------060006010008000807010602" Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 18:22:04 -0000 This is a multi-part message in MIME format. --------------060006010008000807010602 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit > Hi, > > Certainly, here it is: > http://ra.openbios.org/~idwer/freebsd/core.txt.9_fbsd_10-stable_rsu-panic-on-insertion > > Idwer > Does the attached patch make any difference? --HPS --------------060006010008000807010602 Content-Type: text/x-diff; name="rsu.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rsu.diff" === if_rsu.c ================================================================== --- if_rsu.c (revision 266476) +++ if_rsu.c (local) @@ -189,9 +189,9 @@ static void rsu_init_locked(struct rsu_softc *); static void rsu_watchdog(void *); static int rsu_tx_start(struct rsu_softc *, struct ieee80211_node *, - struct mbuf *, struct rsu_data *); + struct mbuf *, struct rsu_data *, struct usb_xfer *); static void rsu_start(struct ifnet *); -static void rsu_start_locked(struct ifnet *); +static void rsu_start_locked(struct ifnet *, struct usb_xfer *); static int rsu_ioctl(struct ifnet *, u_long, caddr_t); static void rsu_stop(struct ifnet *, int); static void rsu_stop_locked(struct ifnet *, int); @@ -1610,7 +1610,7 @@ usbd_xfer_set_frame_data(xfer, 0, data->buf, data->buflen); DPRINTF("submitting transfer %p\n", data); usbd_transfer_submit(xfer); - rsu_start_locked(ifp); + rsu_start_locked(ifp, xfer); break; default: data = STAILQ_FIRST(&sc->sc_tx_active); @@ -1631,7 +1631,7 @@ static int rsu_tx_start(struct rsu_softc *sc, struct ieee80211_node *ni, - struct mbuf *m0, struct rsu_data *data) + struct mbuf *m0, struct rsu_data *data, struct usb_xfer *xfer_self) { struct ifnet *ifp = sc->sc_ifp; struct ieee80211com *ic = ifp->if_l2com; @@ -1736,8 +1736,9 @@ data->ni = ni; data->m = m0; STAILQ_INSERT_TAIL(&sc->sc_tx_pending, data, next); - usbd_transfer_start(xfer); + if (xfer != xfer_self) + usbd_transfer_start(xfer); return (0); } @@ -1750,12 +1751,12 @@ return; RSU_LOCK(sc); - rsu_start_locked(ifp); + rsu_start_locked(ifp, NULL); RSU_UNLOCK(sc); } static void -rsu_start_locked(struct ifnet *ifp) +rsu_start_locked(struct ifnet *ifp, struct usb_xfer *xfer_self) { struct rsu_softc *sc = ifp->if_softc; struct ieee80211_node *ni; @@ -1776,7 +1777,7 @@ ni = (struct ieee80211_node *)m->m_pkthdr.rcvif; m->m_pkthdr.rcvif = NULL; - if (rsu_tx_start(sc, ni, m, bf) != 0) { + if (rsu_tx_start(sc, ni, m, bf, xfer_self) != 0) { ifp->if_oerrors++; STAILQ_INSERT_HEAD(&sc->sc_tx_inactive, bf, next); ieee80211_free_node(ni); @@ -2303,7 +2304,7 @@ return (ENOBUFS); } ifp->if_opackets++; - if (rsu_tx_start(sc, ni, m, bf) != 0) { + if (rsu_tx_start(sc, ni, m, bf, NULL) != 0) { ieee80211_free_node(ni); ifp->if_oerrors++; STAILQ_INSERT_HEAD(&sc->sc_tx_inactive, bf, next); --------------060006010008000807010602-- From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 21:11:06 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B13987B2 for ; Tue, 20 May 2014 21:11:06 +0000 (UTC) Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 765892364 for ; Tue, 20 May 2014 21:11:06 +0000 (UTC) Received: by mail-yh0-f53.google.com with SMTP id i57so909724yha.26 for ; Tue, 20 May 2014 14:11:05 -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=TneX0VM4ufnvy6C+I3w/TI8pWRBrm85R4yT0no7ExII=; b=l9oLM850LVRDPa9dgz+7xbZzvnrvc1vRuzmflngHAeXFmDvj8VkaOoxsmcfm4+e8WP 1HQhOOT8PwAwRTEcyHT6nxb6jv1h2fEt+hpm+6E3m/FVg/A5wKuUE/Rd9lRL0vOqOWzl 3JkcfOqxahaVeKStAg86kfuckY+qT3edxTOBQyeX2KebEFqLaxl3XS83o1NOvegqip8U iYSZsT0YNP9PpCO8WKpushJ1HVeCTNEnJo0UadQ1eRWK0f72pvAhbpoI7glXaQEWoiM/ 5x8fztkAd1qijwYCOGvgOoybT4WNDFV/uqm8dpvwelscSwitip9GDTq2usneqWzIvKkT e26Q== MIME-Version: 1.0 X-Received: by 10.236.25.10 with SMTP id y10mr30513971yhy.63.1400620265665; Tue, 20 May 2014 14:11:05 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Tue, 20 May 2014 14:11:05 -0700 (PDT) In-Reply-To: <537B7B15.8040505@bitfrost.no> References: <537AEC79.6080406@selasky.org> <537B7B15.8040505@bitfrost.no> Date: Tue, 20 May 2014 23:11:05 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 21:11:06 -0000 2014-05-20 17:56 GMT+02:00 Hans Petter Selasky : > Hi, > > Is your kernel built clean with modules? > > --HPS Yes; earlier I passed -DNO_CLEAN, but build time is below ten minutes I'm compiling without that option. I've applied the patch you sent, expect results soon. Idwer From owner-freebsd-wireless@FreeBSD.ORG Tue May 20 22:16:03 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FCDBC87; Tue, 20 May 2014 22:16:03 +0000 (UTC) Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0387B298F; Tue, 20 May 2014 22:16:02 +0000 (UTC) Received: by mail-yk0-f176.google.com with SMTP id q9so921809ykb.35 for ; Tue, 20 May 2014 15:16:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mbNOHnCMO8R+23tuBi3p0dZAwuOQkHlPuNgUAio/hDI=; b=LAK/CZpXMCSB3DfvbA+3RhxD8K41/Ln5t+nywreHZ7EoG63j6oZIyINLq8IvAiGm3t vTjty/CeeaG/rGLnnBA2RWacQkqCcVEhJyptHk1Xn8ZkGwXbC9SlIWyoEwE8oMLxZlbB ZbKrH/a+sueekmefIpJm5crwnkAK9vWHw+JWCQd3ZzON8bLU+VLzEp40PNdlWyB7Yp9c PgaMxcH64NI1CUdJ3P9HjZS8f0ER/SUlQVxTsMCbUyY2XHtD8TsKzHwLZpTxO3vcnEhb IEE3C29W1FLtaC6Sg4P40x6x+7hL1Vdw5J3LdCns8zh6Wd/Mo1/dFne13E6Wd/e5m2vR 1F9A== MIME-Version: 1.0 X-Received: by 10.236.172.170 with SMTP id t30mr19158918yhl.136.1400624162152; Tue, 20 May 2014 15:16:02 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Tue, 20 May 2014 15:16:02 -0700 (PDT) In-Reply-To: <537B9D78.3030103@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> Date: Wed, 21 May 2014 00:16:02 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 22:16:03 -0000 2014-05-20 20:22 GMT+02:00 Hans Petter Selasky : >> Hi, >> >> Certainly, here it is: >> >> http://ra.openbios.org/~idwer/freebsd/core.txt.9_fbsd_10-stable_rsu-panic-on-insertion >> >> Idwer >> > > Does the attached patch make any difference? > > --HPS Yes, it seems to improve the situation. Apparently putting "wlandebug_wlan2=0x40000000" in /etc/rc.conf and compiling+booting with rsu_debug=5 triggers the panic. A verbose boot, so that debug.boothowto=2048 and debug.bootverbose=1, doesn't seem to influence behaviour. From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 06:25:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B8E7E87; Wed, 21 May 2014 06:25:41 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59FE22F4F; Wed, 21 May 2014 06:25:41 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 293621FE026; Wed, 21 May 2014 08:25:39 +0200 (CEST) Message-ID: <537C4712.908@selasky.org> Date: Wed, 21 May 2014 08:26:26 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 06:25:41 -0000 On 05/21/14 00:16, Idwer Vollering wrote: > 2014-05-20 20:22 GMT+02:00 Hans Petter Selasky : >>> Hi, >>> >>> Certainly, here it is: >>> >>> http://ra.openbios.org/~idwer/freebsd/core.txt.9_fbsd_10-stable_rsu-panic-on-insertion >>> >>> Idwer >>> >> >> Does the attached patch make any difference? >> >> --HPS > > Yes, it seems to improve the situation. > Apparently putting "wlandebug_wlan2=0x40000000" in /etc/rc.conf and > compiling+booting with rsu_debug=5 triggers the panic. > > A verbose boot, so that debug.boothowto=2048 and debug.bootverbose=1, > doesn't seem to influence behaviour. > Hi, Can you SVN up to: http://svnweb.freebsd.org/changeset/base/266484 at least, and compile a new kernel and modules without any additional patches. Then send backtrace of any new panics. --HPS From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 14:13:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C216A3A3 for ; Wed, 21 May 2014 14:13:53 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A549A2B3F for ; Wed, 21 May 2014 14:13:53 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Wn7H8-0008Mm-Eo for freebsd-wireless@freebsd.org; Wed, 21 May 2014 07:13:46 -0700 Date: Wed, 21 May 2014 07:13:46 -0700 (PDT) From: Andy To: freebsd-wireless@freebsd.org Message-ID: <1400681626433-5914139.post@n5.nabble.com> Subject: fail to do the bridge on tdma by using the scripts under net80211 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 14:13:53 -0000 Recently I just wanna try the TDMA wireless network of FreeBSD. My network is simple, just three computers, two connect by TDMA each other(one master, one slave) and another computer connect the TDMA master computer by ethernet port(wired). For start, I just run the scripts setup.tdma-master and setup.tdma-slave(under /usr/src/tools/tools/net80211/scripts) on each TDMA computer. These two scripts will create two tdma nodes with both bridged to each wired NIC. After this, I think I could ping between these two bridge but it doesn't work!! At First I think the problem is happen in TDMA connection, so I set IP addresses for two TDMA nodes, and I can ping between them, so the problem maybe in the bridge setting. But looking into the scripts, I find there is nothing differece with bridge setting in the handbook. Am I missing something important here? I would greatly appreciate it if anyone could offer some information on these questions! Following are some of my network setting on the master node: on the slave node: wlan0: flags=8943 metric 0 mtu 1500 ether 00:15:6d:6a:a6:bd inet6 fe80::215:6dff:fe6a:a6bd%wlan0 prefixlen 64 scopeid 0x4 inet 192.168.4.2 netmask 0xffffff00 broadcast 192.168.4.255 nd6 options=21 media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11g status: running ssid freebsd+tdma channel 10 (2457 MHz 11g) bssid ec:88:8f:c4:40:18 country US ecm authmode OPEN privacy OFF txpower 21 ucastrate 24 mcastrate 24 scanvalid 60 protmode CTS wme burst tdmaslot 1 tdmaslotcnt 2 tdmaslotlen 10000 tdmabintval 5 bridge0: flags=8843 metric 0 mtu 1500 ether 02:84:ff:8d:58:00 inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=1 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: wlan0 flags=143 ifmaxaddr 0 port 4 priority 128 path cost 370370 Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 127.0.0.1 link#3 UH 0 0 lo0 192.168.2.0/24 link#5 U 0 1 bridge 192.168.2.2 link#5 UHS 0 0 lo0 192.168.4.0/24 link#4 U 0 4 wlan0 192.168.4.2 link#4 UHS 0 0 lo0 -- View this message in context: http://freebsd.1045724.n5.nabble.com/fail-to-do-the-bridge-on-tdma-by-using-the-scripts-under-net80211-tp5914139.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 14:23:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC0DE646; Wed, 21 May 2014 14:23:31 +0000 (UTC) Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9ECCC2C22; Wed, 21 May 2014 14:23:31 +0000 (UTC) Received: by mail-yh0-f44.google.com with SMTP id b6so1706514yha.31 for ; Wed, 21 May 2014 07:23:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XP03jHIrrBBsUdc6iDTsRK7qmrUJbucpVBC+67Ytxik=; b=dYT2Ei9LGCzU0NBFOBf0ePSS8ES/BCo5tocVrFmFWzkI40j5Mg/8PyVyLFivTocz22 lbteEkqjaOsSS+1pJlm7j4C1t8O4MJ/qhsFvT2fOIW8yWwvmyfrbwQ65wIbO3q8ymune CbO7nPYnu6wd48/f1j7pfD1Cy/1emJIDZsVSWf8DO660ShqoBS0IEACqeodZhMSthtrV RQQPg40FAQ8BSwyxxYr9U6J7LUYb1QtJ4REHjnffxrLZE6JGFfQAh+rAgfvvUmz+8Se8 UNabj0/UGz3nIH8KfuBDSOAH1kRHlfGV84oDYhoQtQlG3eSqyMUtB6xieTyZrkLi07d+ ZUOw== MIME-Version: 1.0 X-Received: by 10.236.25.10 with SMTP id y10mr38868505yhy.63.1400682210839; Wed, 21 May 2014 07:23:30 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Wed, 21 May 2014 07:23:30 -0700 (PDT) In-Reply-To: <537C4712.908@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> Date: Wed, 21 May 2014 16:23:30 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 14:23:32 -0000 2014-05-21 8:26 GMT+02:00 Hans Petter Selasky : > Hi, > > Can you SVN up to: > > http://svnweb.freebsd.org/changeset/base/266484 > > at least, and compile a new kernel and modules without any additional > patches. As said earlier, the only local change is 'int rsu_debug=5'. > Then send backtrace of any new panics. http://ra.openbios.org/~idwer/freebsd/core.txt.0_fbsd-current-r266496-rsu-panic-insertion > > --HPS From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 15:22:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD8D93B8; Wed, 21 May 2014 15:22:16 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EFB3210B; Wed, 21 May 2014 15:22:15 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 558331FE026; Wed, 21 May 2014 17:22:08 +0200 (CEST) Message-ID: <537CC4CF.9030509@selasky.org> Date: Wed, 21 May 2014 17:22:55 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> In-Reply-To: Content-Type: multipart/mixed; boundary="------------070705010309030008020503" Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 15:22:17 -0000 This is a multi-part message in MIME format. --------------070705010309030008020503 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 05/21/14 16:23, Idwer Vollering wrote: > 2014-05-21 8:26 GMT+02:00 Hans Petter Selasky : >> Hi, >> >> Can you SVN up to: >> >> http://svnweb.freebsd.org/changeset/base/266484 >> >> at least, and compile a new kernel and modules without any additional >> patches. > > As said earlier, the only local change is 'int rsu_debug=5'. > >> Then send backtrace of any new panics. > > http://ra.openbios.org/~idwer/freebsd/core.txt.0_fbsd-current-r266496-rsu-panic-insertion > >> >> --HPS > Hi, Can you try the attached patch and report back? --HPS --------------070705010309030008020503 Content-Type: text/x-diff; name="if_rsu.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="if_rsu.diff" === ./if_rsu.c ================================================================== --- ./if_rsu.c (revision 266497) +++ ./if_rsu.c (local) @@ -128,7 +128,10 @@ static device_probe_t rsu_match; static device_attach_t rsu_attach; static device_detach_t rsu_detach; -static usb_callback_t rsu_bulk_tx_callback; +static usb_callback_t rsu_bulk_tx_callback_0; +static usb_callback_t rsu_bulk_tx_callback_1; +static usb_callback_t rsu_bulk_tx_callback_2; +static usb_callback_t rsu_bulk_tx_callback_3; static usb_callback_t rsu_bulk_rx_callback; static usb_error_t rsu_do_request(struct rsu_softc *, struct usb_device_request *, void *); @@ -241,7 +244,7 @@ .pipe_bof = 1, .force_short_xfer = 1 }, - .callback = rsu_bulk_tx_callback, + .callback = rsu_bulk_tx_callback_0, .timeout = RSU_TX_TIMEOUT }, [RSU_BULK_TX_BK] = { @@ -254,7 +257,7 @@ .pipe_bof = 1, .force_short_xfer = 1 }, - .callback = rsu_bulk_tx_callback, + .callback = rsu_bulk_tx_callback_1, .timeout = RSU_TX_TIMEOUT }, [RSU_BULK_TX_VI] = { @@ -267,7 +270,7 @@ .pipe_bof = 1, .force_short_xfer = 1 }, - .callback = rsu_bulk_tx_callback, + .callback = rsu_bulk_tx_callback_2, .timeout = RSU_TX_TIMEOUT }, [RSU_BULK_TX_VO] = { @@ -280,7 +283,7 @@ .pipe_bof = 1, .force_short_xfer = 1 }, - .callback = rsu_bulk_tx_callback, + .callback = rsu_bulk_tx_callback_3, .timeout = RSU_TX_TIMEOUT }, }; @@ -598,10 +601,13 @@ if (error != 0) return (error); - STAILQ_INIT(&sc->sc_tx_active); STAILQ_INIT(&sc->sc_tx_inactive); - STAILQ_INIT(&sc->sc_tx_pending); + for (i = 0; i != RSU_MAX_TX_EP; i++) { + STAILQ_INIT(&sc->sc_tx_active[i]); + STAILQ_INIT(&sc->sc_tx_pending[i]); + } + for (i = 0; i < RSU_TX_LIST_COUNT; i++) { STAILQ_INSERT_HEAD(&sc->sc_tx_inactive, &sc->sc_tx[i], next); } @@ -843,10 +849,12 @@ static int rsu_fw_cmd(struct rsu_softc *sc, uint8_t code, void *buf, int len) { + const uint8_t which = RSU_BULK_TX_VO - RSU_BULK_TX_BE; struct rsu_data *data; struct r92s_tx_desc *txd; struct r92s_fw_cmd_hdr *cmd; - int cmdsz, xferlen; + int cmdsz; + int xferlen; data = rsu_getbuf(sc); if (data == NULL) @@ -879,8 +887,8 @@ DPRINTFN(2, "Tx cmd code=0x%x len=0x%x\n", code, cmdsz); data->buflen = xferlen; - STAILQ_INSERT_TAIL(&sc->sc_tx_pending, data, next); - usbd_transfer_start(sc->sc_xfer[RSU_BULK_TX_VO]); + STAILQ_INSERT_TAIL(&sc->sc_tx_pending[which], data, next); + usbd_transfer_start(sc->sc_xfer[which + RSU_BULK_TX_BE]); return (0); } @@ -1580,7 +1588,7 @@ } static void -rsu_bulk_tx_callback(struct usb_xfer *xfer, usb_error_t error) +rsu_bulk_tx_callback_sub(struct usb_xfer *xfer, usb_error_t error, uint8_t which) { struct rsu_softc *sc = usbd_xfer_softc(xfer); struct ifnet *ifp = sc->sc_ifp; @@ -1590,23 +1598,23 @@ switch (USB_GET_STATE(xfer)) { case USB_ST_TRANSFERRED: - data = STAILQ_FIRST(&sc->sc_tx_active); + data = STAILQ_FIRST(&sc->sc_tx_active[which]); if (data == NULL) goto tr_setup; DPRINTF("transfer done %p\n", data); - STAILQ_REMOVE_HEAD(&sc->sc_tx_active, next); + STAILQ_REMOVE_HEAD(&sc->sc_tx_active[which], next); rsu_txeof(xfer, data); STAILQ_INSERT_TAIL(&sc->sc_tx_inactive, data, next); /* FALLTHROUGH */ case USB_ST_SETUP: tr_setup: - data = STAILQ_FIRST(&sc->sc_tx_pending); + data = STAILQ_FIRST(&sc->sc_tx_pending[which]); if (data == NULL) { DPRINTF("empty pending queue sc %p\n", sc); return; } - STAILQ_REMOVE_HEAD(&sc->sc_tx_pending, next); - STAILQ_INSERT_TAIL(&sc->sc_tx_active, data, next); + STAILQ_REMOVE_HEAD(&sc->sc_tx_pending[which], next); + STAILQ_INSERT_TAIL(&sc->sc_tx_active[which], data, next); usbd_xfer_set_frame_data(xfer, 0, data->buf, data->buflen); DPRINTF("submitting transfer %p\n", data); usbd_transfer_submit(xfer); @@ -1613,14 +1621,21 @@ rsu_start_locked(ifp, xfer); break; default: - data = STAILQ_FIRST(&sc->sc_tx_active); - if (data == NULL) + data = STAILQ_FIRST(&sc->sc_tx_active[which]); + if (data == NULL) { + if (error == USB_ERR_CANCELLED) + break; + + usbd_xfer_set_stall(xfer); goto tr_setup; - if (data->ni != NULL) { - ieee80211_free_node(data->ni); - data->ni = NULL; - ifp->if_oerrors++; } + + STAILQ_REMOVE_HEAD(&sc->sc_tx_active[which], next); + rsu_txeof(xfer, data); + STAILQ_INSERT_TAIL(&sc->sc_tx_inactive, data, next); + + ifp->if_oerrors++; + if (error != USB_ERR_CANCELLED) { usbd_xfer_set_stall(xfer); goto tr_setup; @@ -1629,6 +1644,30 @@ } } +static void +rsu_bulk_tx_callback_0(struct usb_xfer *xfer, usb_error_t error) +{ + rsu_bulk_tx_callback_sub(xfer, error, 0); +} + +static void +rsu_bulk_tx_callback_1(struct usb_xfer *xfer, usb_error_t error) +{ + rsu_bulk_tx_callback_sub(xfer, error, 1); +} + +static void +rsu_bulk_tx_callback_2(struct usb_xfer *xfer, usb_error_t error) +{ + rsu_bulk_tx_callback_sub(xfer, error, 2); +} + +static void +rsu_bulk_tx_callback_3(struct usb_xfer *xfer, usb_error_t error) +{ + rsu_bulk_tx_callback_sub(xfer, error, 3); +} + static int rsu_tx_start(struct rsu_softc *sc, struct ieee80211_node *ni, struct mbuf *m0, struct rsu_data *data, struct usb_xfer *xfer_self) @@ -1639,15 +1678,11 @@ struct ieee80211_frame *wh; struct ieee80211_key *k = NULL; struct r92s_tx_desc *txd; - struct usb_xfer *xfer; - uint8_t type, tid = 0; - int hasqos, xferlen; - struct usb_xfer *rsu_pipes[4] = { - sc->sc_xfer[RSU_BULK_TX_BE], - sc->sc_xfer[RSU_BULK_TX_BK], - sc->sc_xfer[RSU_BULK_TX_VI], - sc->sc_xfer[RSU_BULK_TX_VO] - }; + uint8_t type; + uint8_t tid = 0; + uint8_t which; + int hasqos; + int xferlen; RSU_ASSERT_LOCKED(sc); @@ -1668,12 +1703,12 @@ switch (type) { case IEEE80211_FC0_TYPE_CTL: case IEEE80211_FC0_TYPE_MGT: - xfer = sc->sc_xfer[RSU_BULK_TX_VO]; + which = RSU_BULK_TX_VO - RSU_BULK_TX_BE; break; default: KASSERT(M_WME_GETAC(m0) < 4, ("unsupported WME pipe %d", M_WME_GETAC(m0))); - xfer = rsu_pipes[M_WME_GETAC(m0)]; + which = M_WME_GETAC(m0) + RSU_BULK_TX_BE; break; } hasqos = 0; @@ -1735,10 +1770,10 @@ data->buflen = xferlen; data->ni = ni; data->m = m0; - STAILQ_INSERT_TAIL(&sc->sc_tx_pending, data, next); + STAILQ_INSERT_TAIL(&sc->sc_tx_pending[which], data, next); - if (xfer != xfer_self) - usbd_transfer_start(xfer); + if (sc->sc_xfer[which + RSU_BULK_TX_BE] != xfer_self) + usbd_transfer_start(sc->sc_xfer[which + RSU_BULK_TX_BE]); return (0); } @@ -2073,6 +2108,7 @@ static int rsu_fw_loadsection(struct rsu_softc *sc, const uint8_t *buf, int len) { + const uint8_t which = RSU_BULK_TX_VO - RSU_BULK_TX_BE; struct rsu_data *data; struct r92s_tx_desc *txd; int mlen; @@ -2093,11 +2129,11 @@ memcpy(&txd[1], buf, mlen); data->buflen = sizeof(*txd) + mlen; DPRINTF("starting transfer %p\n", data); - STAILQ_INSERT_TAIL(&sc->sc_tx_pending, data, next); + STAILQ_INSERT_TAIL(&sc->sc_tx_pending[which], data, next); buf += mlen; len -= mlen; } - usbd_transfer_start(sc->sc_xfer[RSU_BULK_TX_VO]); + usbd_transfer_start(sc->sc_xfer[RSU_BULK_TX_BE + which]); return (0); } === ./if_rsureg.h ================================================================== --- ./if_rsureg.h (revision 266497) +++ ./if_rsureg.h (local) @@ -735,6 +735,8 @@ #define RSU_UNLOCK(sc) mtx_unlock(&(sc)->sc_mtx) #define RSU_ASSERT_LOCKED(sc) mtx_assert(&(sc)->sc_mtx, MA_OWNED) +#define RSU_MAX_TX_EP 4 + struct rsu_softc { struct ifnet *sc_ifp; device_t sc_dev; @@ -764,9 +766,9 @@ STAILQ_HEAD(, rsu_data) sc_rx_active; STAILQ_HEAD(, rsu_data) sc_rx_inactive; - STAILQ_HEAD(, rsu_data) sc_tx_active; + STAILQ_HEAD(, rsu_data) sc_tx_active[RSU_MAX_TX_EP]; STAILQ_HEAD(, rsu_data) sc_tx_inactive; - STAILQ_HEAD(, rsu_data) sc_tx_pending; + STAILQ_HEAD(, rsu_data) sc_tx_pending[RSU_MAX_TX_EP]; union { struct rsu_rx_radiotap_header th; --------------070705010309030008020503-- From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 17:34:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 390949E1; Wed, 21 May 2014 17:34:19 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EAA852CF0; Wed, 21 May 2014 17:34:18 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 434E01FE026; Wed, 21 May 2014 19:34:18 +0200 (CEST) Message-ID: <537CE3C9.7090807@selasky.org> Date: Wed, 21 May 2014 19:35:05 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> In-Reply-To: <537CC4CF.9030509@selasky.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 17:34:19 -0000 FYI: http://svnweb.freebsd.org/changeset/base/266505 --HPS From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 18:39:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB6217D6 for ; Wed, 21 May 2014 18:39:31 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:214:c2ff:fe64:b2d3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BF482301 for ; Wed, 21 May 2014 18:39:31 +0000 (UTC) Received: from [192.168.1.94] (unknown [173.52.87.124]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ryao@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 0331D33FE81; Wed, 21 May 2014 18:39:29 +0000 (UTC) From: Richard Yao Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Wed, 21 May 2014 14:39:26 -0400 Subject: Can we obtain higher wireless link throughput by abusing 802.11 radios to form unidirectional simplex pipes? To: freebsd-wireless@freebsd.org Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-Mailer: Apple Mail (2.1878.2) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 18:39:31 -0000 Dear Everyone, I recently read about Ubiquiti=92s AirFiber hardware and noticed that = its link efficiency is remarkable. Air Fiber=92s link speed is about = 770Mbps up and 770Mbps down (a 1:1 split). People are reporting = benchmarks that show 700Mbps throughput over miles. The link efficiency = is therefore in the range of wired ethernet, which typically obtains = iperf results in the range of 85% to 95%. So far, all benchmarks of WiFi = that I have seen never touch 1/e or roughly 37% efficiency. A few have = come rather close to 1/e though. The 1/e number is significant because I am told that it is the = theoretical limit on the efficiency of wired ethernet when a there is a = shared collision domain on a coaxial cable. After reading about how the = Air Fiber hardware works, I hav suspicion that its link efficiency can = be replicated between two computers with off the shelf Wi-Fi hardware by = abusing the radios via the kernel driver. In specific, you would have = two systems, each with two radios on different frequencies. I will call = each system A and B and refer to their radios as indices into an array. = e.g. A[0] and B[1]. Much like the AirFiber, I envision node A as having A[0] be = transmit-only on the frequency that B[0] uses (frequency 0) with B[0] = being receive only. Similarly, I envision node B as having B[1] be = transmit-only on the frequency that A[1] uses (frequency 1) with A[1] be = receive only. The kernel driver is to instruct the WiFi hardware to = ignore everything about the 802.11 protocol possible (e.g. RTS is to be = ignored), send frames when given a packet (in send mode) and receive = forward frames when hearing a packet (in receive mode). No radio in send = mode is to listen to packets and no radio in listen mode is to send = packets. The radios would be attached to directional antennas and = frequency 0 !=3D frequency 1. I asked Adrian Chadd about this in IRC. He replied that it is possible = to hack the driver to obtain tight control over when 802.11 frames are = received/sent, but doing something like this would require oscillator = isolation and baseband RF isolation. He also asked that I send my = question to the list, so here it is. How doable is this with off the shelf hardware? Could simultaneous = dual-band equipment be abused to obtain the proper isolation (where = 2.4GHz is 1 direction and 5GHz is another)? Would it be reasonable to = expect wireless throughput to achieve 90% of the link speed in this = configuration? Yours truly, Richard Yao P.S. I am not on the mailing list, so please include me on CC.= From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 20:08:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47754B40 for ; Wed, 21 May 2014 20:08:46 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 074242B23 for ; Wed, 21 May 2014 20:08:45 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id l6so4019288qcy.17 for ; Wed, 21 May 2014 13:08: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:content-transfer-encoding; bh=HpI6X5JHKRsZvlIvh5Lhnqbl/qoNr27uHU4K1L7WI6s=; b=FMRtQE/v7I9XpsKanfUA+i5umqw3tIFqOWLUyicKb0cvN3OiFEG/bgDBoTGvywIGfg A45jk6r3dtJo5k/NKi14A3OkS+DhzabJei7X8bv9NfG3zrc2AtBTaT0257l4RjKhqP1O C9XbGleNBgFTyhh5CZiGEMTytraD9qtQsgZq1ZQ1KUr7PQagTRVfeYVwCMN/ZfsU3c5J c4tOUDjM25TgzKWw71xE1RxEDXvbVyj0a+tGWmMkvUDBPs/iBkUUhyAyh5ZYlFI7fT04 JtC1g64/OBDcH06xzrqax/ozXg/Un5rJluW2W7dFuFWh0jpK2/Bc7opLQof8cu8UC2Aq aQVg== MIME-Version: 1.0 X-Received: by 10.140.22.209 with SMTP id 75mr70101925qgn.4.1400702924756; Wed, 21 May 2014 13:08:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 21 May 2014 13:08:44 -0700 (PDT) In-Reply-To: References: Date: Wed, 21 May 2014 13:08:44 -0700 X-Google-Sender-Auth: FR18QnMrDqmg3hJms9zrEukMSPI Message-ID: Subject: Re: Can we obtain higher wireless link throughput by abusing 802.11 radios to form unidirectional simplex pipes? From: Adrian Chadd To: Richard Yao Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 20:08:46 -0000 Hi, Yes. There's nothing really stopping you from doing this. You can just associate in both directions and then only send data out one link. Now, having the nic be _transmit only_ and the other nic be _receive only_ is a little tricky, as there's a bunch of 802.11 negotiation stuff that's going on that really assumes it's happening on a single VAP. The net80211 code could be hacked to transmit things out a different device - ie, one VAP has a transmit device and a receive device. You'd have to turn off things like hardware ACK, hardware RTS/CTS, etc. But it's doable. -a On 21 May 2014 11:39, Richard Yao wrote: > Dear Everyone, > > I recently read about Ubiquiti=E2=80=99s AirFiber hardware and noticed th= at its link efficiency is remarkable. Air Fiber=E2=80=99s link speed is abo= ut 770Mbps up and 770Mbps down (a 1:1 split). People are reporting benchmar= ks that show 700Mbps throughput over miles. The link efficiency is therefor= e in the range of wired ethernet, which typically obtains iperf results in = the range of 85% to 95%. So far, all benchmarks of WiFi that I have seen ne= ver touch 1/e or roughly 37% efficiency. A few have come rather close to 1= /e though. > > The 1/e number is significant because I am told that it is the theoretica= l limit on the efficiency of wired ethernet when a there is a shared collis= ion domain on a coaxial cable. After reading about how the Air Fiber hardwa= re works, I hav suspicion that its link efficiency can be replicated betwee= n two computers with off the shelf Wi-Fi hardware by abusing the radios via= the kernel driver. In specific, you would have two systems, each with two = radios on different frequencies. I will call each system A and B and refer = to their radios as indices into an array. e.g. A[0] and B[1]. > > Much like the AirFiber, I envision node A as having A[0] be transmit-only= on the frequency that B[0] uses (frequency 0) with B[0] being receive only= . Similarly, I envision node B as having B[1] be transmit-only on the frequ= ency that A[1] uses (frequency 1) with A[1] be receive only. The kernel dri= ver is to instruct the WiFi hardware to ignore everything about the 802.11 = protocol possible (e.g. RTS is to be ignored), send frames when given a pac= ket (in send mode) and receive forward frames when hearing a packet (in rec= eive mode). No radio in send mode is to listen to packets and no radio in l= isten mode is to send packets. The radios would be attached to directional = antennas and frequency 0 !=3D frequency 1. > > I asked Adrian Chadd about this in IRC. He replied that it is possible to= hack the driver to obtain tight control over when 802.11 frames are receiv= ed/sent, but doing something like this would require oscillator isolation a= nd baseband RF isolation. He also asked that I send my question to the list= , so here it is. > > How doable is this with off the shelf hardware? Could simultaneous dual-b= and equipment be abused to obtain the proper isolation (where 2.4GHz is 1 d= irection and 5GHz is another)? Would it be reasonable to expect wireless th= roughput to achieve 90% of the link speed in this configuration? > > Yours truly, > Richard Yao > > P.S. I am not on the mailing list, so please include me on CC. > _______________________________________________ > 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" From owner-freebsd-wireless@FreeBSD.ORG Wed May 21 20:13:42 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1920FC4E for ; Wed, 21 May 2014 20:13:42 +0000 (UTC) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CEDDA2BC7 for ; Wed, 21 May 2014 20:13:41 +0000 (UTC) Received: by mail-qg0-f48.google.com with SMTP id i50so4149809qgf.35 for ; Wed, 21 May 2014 13:13:40 -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=DAN+jltaHqTZ36TuM5IFPPMph89BgHA8STjQgvBX6Aw=; b=Fr3K9qJnTuoVl6DuQojOegCyrC10rE3troZoCkIfFZ34WZ5gWNA103oe7a+YWPMdBE DQKbNcXgsIOVHlnYE/xJ8mUUcARZH+avHNtLCbV2RIh+ffjML+aWp66nObqtrcqB8KWG UX/JNNoO0ionokWqUJKkOmBMTwDBZMIlVx/MD/i6ZvzhRwywWhfMtiNy3spdmQUF48/N JROb5nl1N0GJdetvZ6+rfsXc5Wo6vNcYuCP6jRmBDeT955yqz9vMsFweFxlE1pa+gAaT jwrUU8e46Wl9+aAjIiBGQhLruO7qHEWlnEhtB4QRrFBUYdi2qLKnHzHzTo4Z3W4lhlOb jnrA== MIME-Version: 1.0 X-Received: by 10.140.22.209 with SMTP id 75mr70144229qgn.4.1400703220697; Wed, 21 May 2014 13:13:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 21 May 2014 13:13:40 -0700 (PDT) In-Reply-To: <1400681626433-5914139.post@n5.nabble.com> References: <1400681626433-5914139.post@n5.nabble.com> Date: Wed, 21 May 2014 13:13:40 -0700 X-Google-Sender-Auth: omF9RfB-5CqprmRIKy_2lRwGqtc Message-ID: Subject: Re: fail to do the bridge on tdma by using the scripts under net80211 From: Adrian Chadd To: Andy Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 20:13:42 -0000 Hi, Are you doing bridging on the master? Does the slave have an IP address, or are you trying to do bridging on the slave too? -a On 21 May 2014 07:13, Andy wrote: > Recently I just wanna try the TDMA wireless network of FreeBSD. My network is > simple, just three computers, two connect by TDMA each other(one master, one > slave) and another computer connect the TDMA master computer by ethernet > port(wired). > > For start, I just run the scripts setup.tdma-master and > setup.tdma-slave(under /usr/src/tools/tools/net80211/scripts) on each TDMA > computer. These two scripts will create two tdma nodes with both bridged to > each wired NIC. After this, I think I could ping between these two bridge > but it doesn't work!! > > At First I think the problem is happen in TDMA connection, so I set IP > addresses for two TDMA nodes, and I can ping between them, so the problem > maybe in the bridge setting. But looking into the scripts, I find there is > nothing differece with bridge setting in the handbook. > > Am I missing something important here? > > I would greatly appreciate it if anyone could offer some information on > these questions! > > Following are some of my network setting > on the master node: > > > > > on the slave node: > > wlan0: flags=8943 metric 0 > mtu 1500 > ether 00:15:6d:6a:a6:bd > inet6 fe80::215:6dff:fe6a:a6bd%wlan0 prefixlen 64 scopeid 0x4 > inet 192.168.4.2 netmask 0xffffff00 broadcast 192.168.4.255 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11g > status: running > ssid freebsd+tdma channel 10 (2457 MHz 11g) bssid ec:88:8f:c4:40:18 > country US ecm authmode OPEN privacy OFF txpower 21 ucastrate 24 > mcastrate 24 scanvalid 60 protmode CTS wme burst tdmaslot 1 > tdmaslotcnt 2 tdmaslotlen 10000 tdmabintval 5 > bridge0: flags=8843 metric 0 mtu > 1500 > ether 02:84:ff:8d:58:00 > inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255 > nd6 options=1 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: wlan0 flags=143 > ifmaxaddr 0 port 4 priority 128 path cost 370370 > > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > 127.0.0.1 link#3 UH 0 0 lo0 > 192.168.2.0/24 link#5 U 0 1 bridge > 192.168.2.2 link#5 UHS 0 0 lo0 > 192.168.4.0/24 link#4 U 0 4 wlan0 > 192.168.4.2 link#4 UHS 0 0 lo0 > > > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/fail-to-do-the-bridge-on-tdma-by-using-the-scripts-under-net80211-tp5914139.html > Sent from the freebsd-wireless mailing list archive at Nabble.com. > _______________________________________________ > 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 Wed May 21 21:23:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6ED97671; Wed, 21 May 2014 21:23:14 +0000 (UTC) Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2022F21FC; Wed, 21 May 2014 21:23:14 +0000 (UTC) Received: by mail-yh0-f52.google.com with SMTP id z6so2209188yhz.39 for ; Wed, 21 May 2014 14:23:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PvBeKrPOUeqI1pjhrHW55cVx81uf5Rrq3PHAsOs7qZc=; b=ZxWf199owPd/V+rTk/HfEcuMYjZGa+3rBARkfUVNB7M/k8DawKJDa+5OhfH8+fcC7a 19cqZmDHauRZ4WnfD8hOWdJiJuI4Q3ZMXLNVV5f9S1znLnCYzuY1vzvmBXzJ9b0qtB8K EoQBFXkk9YOjs8mDemgkaRfx1lD9kvsLZV7/euuIrSfzacC7nHzZPFgNDHeW7sfVmWr3 dXIHUB6anNtMYGMFyXgjb+tR8iWTXA2RFsNCxpy/s9UVC89Jbi57o+oitsZJxyQPHFsN PCE60yIYHhfJn/z+l18lWTebBiGDCQBCrB1secS6+GKuKsjZG7umim/VGEGoMfntmHNE y7Yw== MIME-Version: 1.0 X-Received: by 10.236.172.170 with SMTP id t30mr29987380yhl.136.1400707393354; Wed, 21 May 2014 14:23:13 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Wed, 21 May 2014 14:23:13 -0700 (PDT) In-Reply-To: <537CE3C9.7090807@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> Date: Wed, 21 May 2014 23:23:13 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 21:23:14 -0000 2014-05-21 19:35 GMT+02:00 Hans Petter Selasky : > FYI: > > http://svnweb.freebsd.org/changeset/base/266505 > > --HPS Newer backtrace: http://ra.openbios.org/~idwer/freebsd/core.txt.0_fbsd-current-r266514-rsu-panic-insertion From owner-freebsd-wireless@FreeBSD.ORG Thu May 22 05:32:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 197F5EA; Thu, 22 May 2014 05:32:54 +0000 (UTC) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC80127E5; Thu, 22 May 2014 05:32:53 +0000 (UTC) Received: by mail-qg0-f54.google.com with SMTP id q108so4828080qgd.27 for ; Wed, 21 May 2014 22:32:52 -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=Wy8xqeIWCMmlVm6V9P20hFgfHIZwwB/zCi9Aam7PUYo=; b=KXRw2wQTbLZFQhVYrUCbbvPnsTM0ewrS0Gn1uHijqzlFGPlgPK97U54rE3a8B64KVA CGLGdDBkKWTpVdGSe2iZfSo1DRHSm1bV1hK+V9OMZmNp0RAs1cWFmHiYva5z88RmVK0r Zu8w7Z1WwZaDL8lHWAuzM/tnnC2dUjfXoINAYuFGs+iAuYxpz37scZ7MfoAb+JWO7CMc UxEC1BjCQeHu1dRzYGp7X8syXBaWHKAMdjxOtU3a649/ycqHGnLUP0M5HJlnBFdXodpf 10LEdRpaP7CAGjZ0Em6535Dem0SIQwhEwZAC5sNQ9txnr1DaRzvZ0SGp/NBIrwi+eTmH HA3w== MIME-Version: 1.0 X-Received: by 10.229.112.5 with SMTP id u5mr76479813qcp.3.1400736772864; Wed, 21 May 2014 22:32:52 -0700 (PDT) Received: by 10.96.43.105 with HTTP; Wed, 21 May 2014 22:32:52 -0700 (PDT) In-Reply-To: References: <1400681626433-5914139.post@n5.nabble.com> Date: Thu, 22 May 2014 13:32:52 +0800 Message-ID: Subject: Re: fail to do the bridge on tdma by using the scripts under net80211 From: =?UTF-8?B?6ZmG5qyj5oWw?= To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: "freebsd-wireless@freebsd.org" , Andy X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 05:32:54 -0000 I was trying to do bridge just on master and now I can ping the bridge on the master from slave node . But I still cannot ping the third computer (which is connected to master node by wired) on slave node. The ip addresses I set are as followes: on mater node : wlan0:192.168.4.1/24 bridge0:192.168.2.1/24 bge0:192.168.6.1 and I run a dhcp server on bge0, then the third computer get ip address 192.168.6.118 from this dhcp server. on slave node wlan0 192.168.4.2/24 Now on slave node I can ping 192.168.2.1 and 192.168.6.1 but fail to ping 192.168.6.118. From owner-freebsd-wireless@FreeBSD.ORG Thu May 22 06:28:59 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E743CB9D; Thu, 22 May 2014 06:28:59 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C9972CA6; Thu, 22 May 2014 06:28:58 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id B37121FE026; Thu, 22 May 2014 08:28:56 +0200 (CEST) Message-ID: <537D9955.3070001@selasky.org> Date: Thu, 22 May 2014 08:29:41 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 06:29:00 -0000 On 05/21/14 23:23, Idwer Vollering wrote: > 2014-05-21 19:35 GMT+02:00 Hans Petter Selasky : >> FYI: >> >> http://svnweb.freebsd.org/changeset/base/266505 >> >> --HPS > > Newer backtrace: > http://ra.openbios.org/~idwer/freebsd/core.txt.0_fbsd-current-r266514-rsu-panic-insertion > Hi, Try this: http://svnweb.freebsd.org/changeset/base/266535 --HPS From owner-freebsd-wireless@FreeBSD.ORG Thu May 22 11:22:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC814DC4; Thu, 22 May 2014 11:22:46 +0000 (UTC) Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B9FD26EF; Thu, 22 May 2014 11:22:46 +0000 (UTC) Received: by mail-yh0-f45.google.com with SMTP id b6so2795203yha.32 for ; Thu, 22 May 2014 04:22:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=RvZ34x+tXvsXPCxoT4+Ek3Ch2WPXllyHTHR1xixJeqc=; b=bV/FRUp2FgZNldwwgqSuhvwkjYmRFYaqs5FRitYFpsF1FzTRh8Bm45EWm/wi9o5EFw ty0jt6s5ZIemDzXak3NvAKPoDTYK0B6NA8oPo0n/6+W5V/75aydCTFCtEdjuBGYKOS7q jQ+mAHcGvg/jkmJLdLRcIxKih5ahWfk726JLmFnNQ2vdPZNtRdW3U0zWIqZXnqJabLJq 4k26OcmlbHwtr9hNChqBfUZaMmb7aUjO6N1iWkUKT0qQRGsFOOWh72TUpLp/Bc6eUmLU l3LavAzrRoHjyyzCou4nPzj8WanU+hdatr7Q0qwxzEYFWkQmB+Yu7hNRrZB1B2XvRrqu Ym5w== MIME-Version: 1.0 X-Received: by 10.236.127.109 with SMTP id c73mr40449043yhi.1.1400757765779; Thu, 22 May 2014 04:22:45 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Thu, 22 May 2014 04:22:45 -0700 (PDT) In-Reply-To: <537D9955.3070001@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> <537D9955.3070001@selasky.org> Date: Thu, 22 May 2014 13:22:45 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 11:22:46 -0000 2014-05-22 8:29 GMT+02:00 Hans Petter Selasky : > > Hi, > > Try this: > > http://svnweb.freebsd.org/changeset/base/266535 > > --HPS That is much better, thanks. As in: the panics are gone, although wpa_supplicant won't bring IP up: ugen3.3: at usbus3 rsu0: on u= sbus3 rsu_do_request: Control request failed, USB_ERR_TIMEOUT (retrying) 29:81:00:00:a9:16:00:00:da:0b:71:81:90:85:62:9c:06:00:00:e0:4c:04:52:a3:17:= 03:4d:61:6e:75:66:61:63:74:75:72:65:72:20:52:65:61:6c:74:65:6b:20:18:03:52:= 54:4c:38:31:38:38:53:20:57:4c:41:4e:20:41:64:61:70:74:65:72:20:00:00:00:00:= 00:00:00:00:00:02:05:00:00:00:27:27:27:1b:1b:1b:28:29:29:2d:2d:2d:2d:2d:2d:= 2d:2d:2d:44:12:00:00:09:0d:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:= 00:00:00: rsu0: MAC/BB RTL8712 cut 3 rsu0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps rsu0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wlan2: bpf attached wlan2: bpf attached wlan2: Ethernet address: wlan2: start running, 0 vaps running wlan2: ieee80211_start_locked: up parent rsu0 rsu_do_request: Control request failed, USB_ERR_TIMEOUT (retrying) firmware: 'rsu-rtl8712fw' version 120: 122328 bytes loaded at 0xffffffff820= 551e0 rsu_load_firmware: FW V4588 05-30 16:53 rsu_fw_loadsection: starting transfer 0xfffffe0005ff47d8 (output abbreviated) rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0005ff47d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0005ff47d8 (output abbreviated) rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe0005ff2000 rsu_fw_loadsection: starting transfer 0xfffffe0005ff42f8 (output abbreviated) rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0005ff42f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0005ff42f8 (output abbreviated) rsu0: timeout waiting for EMEM transfer wlan2: start running, 1 vaps running May 22 13:14:07 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D103, val=3D0, arg_len=3D128]: Device not configured ugen3.3: at usbus3 (disconnected) rsu0: at uhub1, port 2, addr 3 (disconnected) wlan2: stop running, 1 vaps running rsu_newstate: INIT -> INIT May 22 13:14:19 machete last message repeated 12 times May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D25, val=3D0, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D95, val=3D208, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D17, val=3D0, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D26, val=3D0, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D95, val=3D208, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D17, val=3D0, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D26, val=3D0, arg_len=3D0]: Device not configured May 22 13:14:19 machete wpa_supplicant[822]: ioctl[SIOCS80211, op=3D16, val=3D1, arg_len=3D0]: Device not configured From owner-freebsd-wireless@FreeBSD.ORG Thu May 22 11:51:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8DC0155C; Thu, 22 May 2014 11:51:17 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4398E2993; Thu, 22 May 2014 11:51:16 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 307D51FE026; Thu, 22 May 2014 13:51:16 +0200 (CEST) Message-ID: <537DE4DF.1060703@selasky.org> Date: Thu, 22 May 2014 13:51:59 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> <537D9955.3070001@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 11:51:17 -0000 On 05/22/14 13:22, Idwer Vollering wrote: > rsu0: timeout waiting for EMEM transfer Does this patch make any difference: === ./if_rsu.c ================================================================== --- ./if_rsu.c (revision 266539) +++ ./if_rsu.c (local) @@ -2220,13 +2220,13 @@ goto fail; } /* Wait for load to complete. */ - for (ntries = 0; ntries != 10; ntries++) { + for (ntries = 0; ntries != 50; ntries++) { usb_pause_mtx(&sc->sc_mtx, hz / 100); reg = rsu_read_2(sc, R92S_TCR); if (reg & R92S_TCR_EMEM_CODE_DONE) break; } - if (ntries == 10) { + if (ntries == 50) { device_printf(sc->sc_dev, "timeout waiting for EMEM transfer\n"); error = ETIMEDOUT; goto fail; From owner-freebsd-wireless@FreeBSD.ORG Thu May 22 18:35:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E53C49A6; Thu, 22 May 2014 18:34:59 +0000 (UTC) Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 91D702E56; Thu, 22 May 2014 18:34:59 +0000 (UTC) Received: by mail-yk0-f171.google.com with SMTP id 142so3133874ykq.2 for ; Thu, 22 May 2014 11:34:58 -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=3Ib7nuTrZlVZSjptX53cLyqBmAM/vw/cm17DKD9BIiw=; b=dQ9U6isZE3rpT3sjz5Pmvz2kQ51Q6BT0YoIm/sm63N++IAyZo2PZU+CD9Yy6Q7/9Gd O7UeInss19SLMnp9+fr8owY9HHBHIyDDCHgfMOAmxuh5xpn+0WpMMhlR38Bm3Wwzoiet vyjNjimBJm+EpP0I0/XBiSyiQRNLVWhbv6j5mFmz/pfC1Z/eMGq0vVD9U0lle/7QN3Wv K3UiuX21H7IIBpdgxNTvY5SmeX2aDLBjJ8ElskUqvYAY9r1YW5hTQ0cZJE6MemcgXNcv gCodl5A9Y+kZ9iOqaO6FptokWpLrLbWecD/0GZVW//x10RLc5pM4XSNvJYLMXxPZdnm+ w1Aw== MIME-Version: 1.0 X-Received: by 10.236.172.170 with SMTP id t30mr39281569yhl.136.1400783698721; Thu, 22 May 2014 11:34:58 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Thu, 22 May 2014 11:34:58 -0700 (PDT) In-Reply-To: <537DE4DF.1060703@selasky.org> References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> <537D9955.3070001@selasky.org> <537DE4DF.1060703@selasky.org> Date: Thu, 22 May 2014 20:34:58 +0200 Message-ID: Subject: Re: if_rsu hardware causes a kernel panic on removal.. From: Idwer Vollering To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 18:35:00 -0000 2014-05-22 13:51 GMT+02:00 Hans Petter Selasky : > On 05/22/14 13:22, Idwer Vollering wrote: >> >> rsu0: timeout waiting for EMEM transfer > > > Does this patch make any difference: > > === ./if_rsu.c > ================================================================== > --- ./if_rsu.c (revision 266539) > +++ ./if_rsu.c (local) > @@ -2220,13 +2220,13 @@ > goto fail; > } > /* Wait for load to complete. */ > - for (ntries = 0; ntries != 10; ntries++) { > + for (ntries = 0; ntries != 50; ntries++) { > usb_pause_mtx(&sc->sc_mtx, hz / 100); > reg = rsu_read_2(sc, R92S_TCR); > if (reg & R92S_TCR_EMEM_CODE_DONE) > break; > } > - if (ntries == 10) { > + if (ntries == 50) { > device_printf(sc->sc_dev, "timeout waiting for EMEM > transfer\n"); > error = ETIMEDOUT; > goto fail; > Hi, This patch again improves its stability, but the interface keeps flapping: May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Device not configured May 22 20:29:03 machete last message repeated 3 times May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=25, val=0, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=95, val=208, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=17, val=0, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=95, val=208, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=17, val=0, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Device not configured May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=16, val=1, arg_len=0]: Device not configured May 22 20:30:27 machete dhclient[2734]: send_packet: Invalid argument wlan2: link state changed to UP wlan2: link state changed to DOWN wlan2: link state changed to UP wlan2: link state changed to DOWN May 22 20:30:27 machete dhclient[2734]: send_packet: Invalid argument wlan2: link state changed to UP May 22 20:30:36 machete dhclient[2734]: send_packet: No buffer space available wlan2: link state changed to DOWN wlan2: link state changed to UP May 22 20:31:03 machete dhclient[2734]: send_packet: No buffer space available From owner-freebsd-wireless@FreeBSD.ORG Thu May 22 18:37:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFE56A40; Thu, 22 May 2014 18:37:30 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 742992E88; Thu, 22 May 2014 18:37:30 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C28B41FE026; Thu, 22 May 2014 20:37:22 +0200 (CEST) Message-ID: <537E440E.5010208@selasky.org> Date: Thu, 22 May 2014 20:38:06 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> <537D9955.3070001@selasky.org> <537DE4DF.1060703@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 18:37:30 -0000 On 05/22/14 20:34, Idwer Vollering wrote: > Hi, > > This patch again improves its stability, but the interface keeps flapping: > > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=20, > val=0, arg_len=7]: Device not configured > May 22 20:29:03 machete last message repeated 3 times > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=25, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=95, > val=208, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=17, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=26, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=95, > val=208, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=17, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=26, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=16, > val=1, arg_len=0]: Device not configured > > May 22 20:30:27 machete dhclient[2734]: send_packet: Invalid argument > wlan2: link state changed to UP > wlan2: link state changed to DOWN > wlan2: link state changed to UP > wlan2: link state changed to DOWN > May 22 20:30:27 machete dhclient[2734]: send_packet: Invalid argument > wlan2: link state changed to UP > May 22 20:30:36 machete dhclient[2734]: send_packet: No buffer space available > wlan2: link state changed to DOWN > wlan2: link state changed to UP > May 22 20:31:03 machete dhclient[2734]: send_packet: No buffer space available > Hi, I guess you need to enable rsu debugging to figure out why the hardware reports link loss. --HPS From owner-freebsd-wireless@FreeBSD.ORG Fri May 23 09:59:50 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDDA22E3; Fri, 23 May 2014 09:59:50 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9459628D2; Fri, 23 May 2014 09:59:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=1fETEnakpdfJOigot4VTjVSrb6cN5Bwdww2hEEazGJk=; b=yA+qsImn8U5K1YoUjJSHikdieqWosrrCKMPacZ14px9cJNrRzAMwf8SdCgqVLscAJTAVPqHRT04nJktq3AM/sBW0qo8HgjJo5OXQ76Z3iq51IMZlewKHGQ1kvHQeuBrcYMWtVIId5M7l2sEXDPF5dQOn0oRF1wffifnh1r4DUOs=; Received: from [182.7.116.7] (port=15880 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WnmGM-001y09-Ti; Fri, 23 May 2014 03:59:43 -0600 Date: Fri, 23 May 2014 17:59:35 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140523175935.468039f4@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 09:59:50 -0000 Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd wrote: > I'm not sure. I'd really like to see what the story is with > coexistence somehow. > I upgraded my machine to this: FreeBSD X220.alogt.com 10.0-STABLE FreeBSD 10.0-STABLE #36 r266578: Fri May 23 16:56:23 WITA 2014 erich@X220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 It is still the same with iwn. It crashes when trying to read instruction at 0x20:0. It seems to me that this behaviour is now quite normal on my machine. What can I do best to help finding the source of the problem? Erich > > -a > > > On 8 April 2014 20:32, Erich Dollansky > wrote: > > Hi, > > > > On Tue, 8 Apr 2014 20:07:39 -0700 > > Adrian Chadd wrote: > > > >> Coexistence is to deal with the fact that a 40MHz channel may > >> overlap a 20MHz-only AP in the extension channel. > >> > >> If the AP finds a 20MHz AP in the extension channel (ie, the other > >> half of its 40MHz) channel then it'll flip itself to 20MHz. If it > >> determines it isn't there any more, it'll flip the BSS to the 40MHz > >> channel. > >> > >> Now, why the hell it's causing the connection to fail? I have no > >> idea. > >> > >> can someone file a PR that says it's all busted with 40MHz > >> coxistence enabled? We can then start debugging from that position. > >> > > I am not so sure if it is a general problem or just a DLink problem. > > > > I just activated my own access point and it worked there. The only > > problem is that it also works with DLink but only randomly. So, it > > still could have been that I was just always lucky when connecting > > to the ProLink access point I have. > > > > As the DLink is not mine, I am not even able to access its > > administration interface. > > > > Can I suggest to wait a bit to get more feedback to see if it is a > > general problem or a problem only linked to one manufacturer? > > > > Erich From owner-freebsd-wireless@FreeBSD.ORG Fri May 23 11:13:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 773B5C46; Fri, 23 May 2014 11:13:43 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D7F32FC7; Fri, 23 May 2014 11:13:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=M/ZiDqS4eN1sv6JSmZAdYIMwJwGVTipRAlWvvDLN59s=; b=yDSQO7/ipnmqrs09Wce9A4sGn757ZyImOr7/cRzCFy5BgnuL6TrUua3Tn5/Ir33UVIWtJnyRYufvPpm31+da5mPU5ckAhja/kcANb5zraNv4BqyYFRFyxz+2+PCM6hCRoApdJCZr816ad5hMchA/pYtDPnlMKFHSCbMdRRVuaJc=; Received: from [114.122.94.132] (port=13996 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WnnPw-002dhK-Q8; Fri, 23 May 2014 05:13:41 -0600 Date: Fri, 23 May 2014 19:13:29 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140523191329.62027b64@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 11:13:43 -0000 Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd wrote: > I'm not sure. I'd really like to see what the story is with > coexistence somehow. > I did some more investigations and came to the result that iwn crashes in 'in6_ifattach_linklocal'. When I disable ipv6, it all works fine. I did several reboots without a problem. To make this a bit more complicated, if I use only em0, the machine starts normal. When I use iwn0 alone or together with lagg0 and em0, the machine crashes during the boot process. The crashes only happen when IPV6 is enabled in rc.conf. Erich From owner-freebsd-wireless@FreeBSD.ORG Fri May 23 15:36:33 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48DA58C4; Fri, 23 May 2014 15:36:33 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E3A002938; Fri, 23 May 2014 15:36:32 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id c9so217552qcz.16 for ; Fri, 23 May 2014 08:36: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=mDQ3uLVREeSX3qkjPt+UHNIzVudJRjisU/nMww5QEjQ=; b=c4gHXjRw1pKXGe0eO11jOYRUzwVIeqVCgTjHy3Sv136ZhEkhi14PlQzn2qO/CunVtg 03MUkEJNJl13Ez1tZf6j065t5mM1pch6AFxE0/fA2rkBMcgjYn2LjeK6E2quyUpwBUxa HdsuZeeDgqO3pl53jvLm4U/ZUBe2cKoIYlnwKUiOBE2nxPN4EgXRtRk5jajwRmG15eDM xBqyA+o3fJXhxSjmFZ+wz5vG6iKhWOjShavLwXx56f2uRJg+PnULS/iES7DKovpQGVse b+UgnR/xks4k1qE0tErP2VmIMNlz5G3RnthQ1U2BN0DBByZeZWeZR+L+OtFBwhKyoIgw TVYQ== MIME-Version: 1.0 X-Received: by 10.224.129.66 with SMTP id n2mr7861374qas.55.1400859391982; Fri, 23 May 2014 08:36:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 23 May 2014 08:36:31 -0700 (PDT) In-Reply-To: <20140523191329.62027b64@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> Date: Fri, 23 May 2014 08:36:31 -0700 X-Google-Sender-Auth: 2gx8aknI0FMjHb8cMEHLKbmxxI0 Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 15:36:33 -0000 Ok, it's a null pointer dereference (based on the address you posted) and it's ipv6 related. That's .. odd. Can you provide a backtrace from the crash? -a On 23 May 2014 04:13, Erich Dollansky wrote: > Hi, > > On Tue, 8 Apr 2014 20:40:01 -0700 > Adrian Chadd wrote: > >> I'm not sure. I'd really like to see what the story is with >> coexistence somehow. >> > I did some more investigations and came to the result that iwn crashes > in 'in6_ifattach_linklocal'. > > When I disable ipv6, it all works fine. I did several reboots without a > problem. > > To make this a bit more complicated, if I use only em0, the machine > starts normal. When I use iwn0 alone or together with lagg0 and em0, > the machine crashes during the boot process. The crashes only happen > when IPV6 is enabled in rc.conf. > > Erich From owner-freebsd-wireless@FreeBSD.ORG Fri May 23 16:00:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3B2A136; Fri, 23 May 2014 16:00:02 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A923B2B92; Fri, 23 May 2014 16:00:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=sJK/F6hT/qmHUZFuVaqWoNvHLn91jNxCHYU4rQTEun8=; b=LmKYqPa4vX8tTnhTdGIk67aoKl1F256anoFMe034MWkBnNXfbamsqpYtcmhCfdCaqjN0TQBQ4JUrQZ5szAYrKYQoF9Bf7bbz0mIoXOUAAWJiAvwtZWoEMjAvocAq+7U0a5Pyxk6WMNpTgS8s/mLPn+oL1HzwaV5AlhgOhGPWXLw=; Received: from [114.122.94.132] (port=61227 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1Wnrt2-000dzO-6N; Fri, 23 May 2014 10:00:01 -0600 Date: Fri, 23 May 2014 23:59:53 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140523235953.7f8dbb4d@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 16:00:02 -0000 Hi, On Fri, 23 May 2014 08:36:31 -0700 Adrian Chadd wrote: > Ok, it's a null pointer dereference (based on the address you posted) > and it's ipv6 related. That's .. odd. > > Can you provide a backtrace from the crash? > I can try tomorrow. Am I right that I can only take photos of the screen at this point of the boot process? Erich > > > -a > > > On 23 May 2014 04:13, Erich Dollansky > wrote: > > Hi, > > > > On Tue, 8 Apr 2014 20:40:01 -0700 > > Adrian Chadd wrote: > > > >> I'm not sure. I'd really like to see what the story is with > >> coexistence somehow. > >> > > I did some more investigations and came to the result that iwn > > crashes in 'in6_ifattach_linklocal'. > > > > When I disable ipv6, it all works fine. I did several reboots > > without a problem. > > > > To make this a bit more complicated, if I use only em0, the machine > > starts normal. When I use iwn0 alone or together with lagg0 and em0, > > the machine crashes during the boot process. The crashes only > > happen when IPV6 is enabled in rc.conf. > > > > Erich From owner-freebsd-wireless@FreeBSD.ORG Fri May 23 16:01:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 12CC7192; Fri, 23 May 2014 16:01:38 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B20082C1F; Fri, 23 May 2014 16:01:37 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id e16so8514781qcx.0 for ; Fri, 23 May 2014 09:01:36 -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=6CWGgtxhD7EUTaJEY1i9EW6nhonah2UyRprDUJQnxjg=; b=fU9l3fpDIrV5IG2pQSOVtryGandC7BRj7264G8+DecspR1A6cawbJX4u1wDbg3y4f7 3TrACt/6wMbzNGukwF6bdfkpW+sD/J1c2RjC6Uwq95F3KepgHUCf2iJ7Mo7OfHeqagWr GXph97TnqZy6FYhOSNHSEbUyLnWoWZlGULo2RONt8xR14+JrsJ6hNqlCm9ZtaAT9Visg 3PkvYxbZyN3nEllWiGKrkzCnsuMZJGjP/54MJI/Ni+cv3ELarOY+hIQmZKUUtjGpjarI 8qEu1wCA0q1kYt+xG9eimAAjS/SF+OdqsaCkkpD48RPd1cFRmWcPlUs2rSSwgon9xmOc g2HA== MIME-Version: 1.0 X-Received: by 10.224.51.2 with SMTP id b2mr8053932qag.49.1400860896925; Fri, 23 May 2014 09:01:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 23 May 2014 09:01:36 -0700 (PDT) In-Reply-To: <20140523235953.7f8dbb4d@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> <20140523235953.7f8dbb4d@X220.alogt.com> Date: Fri, 23 May 2014 09:01:36 -0700 X-Google-Sender-Auth: lIr5gIzDVeMDf4DFzZ66-FQIGRc Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 16:01:38 -0000 a photo will be fine. :-) -a On 23 May 2014 08:59, Erich Dollansky wrote: > Hi, > > On Fri, 23 May 2014 08:36:31 -0700 > Adrian Chadd wrote: > >> Ok, it's a null pointer dereference (based on the address you posted) >> and it's ipv6 related. That's .. odd. >> >> Can you provide a backtrace from the crash? >> > I can try tomorrow. Am I right that I can only take photos of the > screen at this point of the boot process? > > Erich >> >> >> -a >> >> >> On 23 May 2014 04:13, Erich Dollansky >> wrote: >> > Hi, >> > >> > On Tue, 8 Apr 2014 20:40:01 -0700 >> > Adrian Chadd wrote: >> > >> >> I'm not sure. I'd really like to see what the story is with >> >> coexistence somehow. >> >> >> > I did some more investigations and came to the result that iwn >> > crashes in 'in6_ifattach_linklocal'. >> > >> > When I disable ipv6, it all works fine. I did several reboots >> > without a problem. >> > >> > To make this a bit more complicated, if I use only em0, the machine >> > starts normal. When I use iwn0 alone or together with lagg0 and em0, >> > the machine crashes during the boot process. The crashes only >> > happen when IPV6 is enabled in rc.conf. >> > >> > Erich > From owner-freebsd-wireless@FreeBSD.ORG Sat May 24 02:19:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 402E4D87; Sat, 24 May 2014 02:19:47 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0516F2CFE; Sat, 24 May 2014 02:19:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=r/oRe2Qanmyf3S4Ceh+jnbZXHYbsHXKLAjnXCdz1Uic=; b=BsSBgLdSQo4y6vexVWcHTvzPAsAdFC0uef8JhGAtwYU+vXkeyV+xiAktsoghbo/bGzf+V7/7xeIoKmQ/dZ3pBVf/Zp0cvvupiLht8qClv4V7MNRk3kSR6aep3KUQ75fVrxIE0M08bghAHQebnAH/g1v6Gqop6a0ruwEsUK2zRp4=; Received: from [182.13.46.227] (port=32175 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1Wo1Yn-004CJw-7P; Fri, 23 May 2014 20:19:46 -0600 Date: Sat, 24 May 2014 10:19:38 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140524101938.590df1c1@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> <20140523235953.7f8dbb4d@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2014 02:19:47 -0000 Hi Adrian, On Fri, 23 May 2014 09:01:36 -0700 Adrian Chadd wrote: > a photo will be fine. :-) > The photos are here: http:/www.alogt.com/freebsd/network/SAM_0379.JPG The first photo shows a hang of IWN after the machine successfully started. The remaining photos show the backtrace. http:/www.alogt.com/freebsd/network/SAM_0380.JPG http:/www.alogt.com/freebsd/network/SAM_0381.JPG http:/www.alogt.com/freebsd/network/SAM_0382.JPG http:/www.alogt.com/freebsd/network/SAM_0383.JPG http:/www.alogt.com/freebsd/network/SAM_0384.JPG Erich > > -a > > > On 23 May 2014 08:59, Erich Dollansky > wrote: > > Hi, > > > > On Fri, 23 May 2014 08:36:31 -0700 > > Adrian Chadd wrote: > > > >> Ok, it's a null pointer dereference (based on the address you > >> posted) and it's ipv6 related. That's .. odd. > >> > >> Can you provide a backtrace from the crash? > >> > > I can try tomorrow. Am I right that I can only take photos of the > > screen at this point of the boot process? > > > > Erich > >> > >> > >> -a > >> > >> > >> On 23 May 2014 04:13, Erich Dollansky > >> wrote: > >> > Hi, > >> > > >> > On Tue, 8 Apr 2014 20:40:01 -0700 > >> > Adrian Chadd wrote: > >> > > >> >> I'm not sure. I'd really like to see what the story is with > >> >> coexistence somehow. > >> >> > >> > I did some more investigations and came to the result that iwn > >> > crashes in 'in6_ifattach_linklocal'. > >> > > >> > When I disable ipv6, it all works fine. I did several reboots > >> > without a problem. > >> > > >> > To make this a bit more complicated, if I use only em0, the > >> > machine starts normal. When I use iwn0 alone or together with > >> > lagg0 and em0, the machine crashes during the boot process. The > >> > crashes only happen when IPV6 is enabled in rc.conf. > >> > > >> > Erich > > From owner-freebsd-wireless@FreeBSD.ORG Mon May 26 11:06:55 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CCE4DFC0 for ; Mon, 26 May 2014 11:06:55 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FA3D24FA for ; Mon, 26 May 2014 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4QB6tII032219 for ; Mon, 26 May 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4QB6tQ7032216 for freebsd-wireless@FreeBSD.org; Mon, 26 May 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 May 2014 11:06:55 GMT Message-Id: <201405261106.s4QB6tQ7032216@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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2014 11:06:55 -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/189405 wireless [run] [wlan] hostapd, kernel panic, wlan using run dev o kern/188654 wireless [urtwn] tp-link wl-725n Realtek 8188 chip do not work o kern/188576 wireless [ath] traffic hangs in station mode when downgrading f o kern/188415 wireless [ath] Poor Atheros AR9565 performance o bin/187470 wireless [bthidd] [patch] Apple Wireless Keyboard (JIS) o kern/186733 wireless [iwn] iwn device (5100) periodically times out killing o kern/186553 wireless [wi] No wireless connection possible, driver not worki o kern/185478 wireless [iwi] [panic] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino Advanced–N + WiMAX 6250: WEP fails, WPA o kern/185025 wireless [iwi] [panic] iwi driver panic on 10.0rc2 f usb/184918 wireless [ural] regression on WEP o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) "stops" working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181694 wireless [iwn] [suspend/resume] [patch] Initialize hardware in o kern/181161 wireless [wl] [panic] config a old compaq wl-110 wireless card 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/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/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/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/168754 wireless [ath] if_ath dont have internal name o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless [ath] [suspend/resume] 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/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] kernel panic: page fault with ath0 taskq 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/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 o bin/98218 wireless wpa_supplicant(8) blacklist not working 194 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed May 28 12:00:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 318B2EC8 for ; Wed, 28 May 2014 12:00:38 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 13AA72E5D for ; Wed, 28 May 2014 12:00:37 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WpcX1-0005d1-I1 for freebsd-wireless@freebsd.org; Wed, 28 May 2014 05:00:31 -0700 Date: Wed, 28 May 2014 05:00:31 -0700 (PDT) From: Andy To: freebsd-wireless@freebsd.org Message-ID: <1401278431550-5915936.post@n5.nabble.com> Subject: Does TDMA on FreeBSD only support point to point applications MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2014 12:00:38 -0000 When I try to use TDMA options of FreeBSD on atheros chips, I found it works fine with point to point applications. But when I try to set tdmaslotcnt to bigger than 2, it give the following error message: ifconfig: SIOCS80211: Invalid argument Then I try to read man page of ifconfig to get some help, and it is said that current implementation of TDMA is only tested with two stations.But the value of the slot cout may be at most 8. So now the TDMA of FreeBSD only support point to point connection? How could I setup a TDMA network bigger than 2 nodes? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Does-TDMA-on-FreeBSD-only-support-point-to-point-applications-tp5915936.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Thu May 29 06:53:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 133F110E for ; Thu, 29 May 2014 06:53:09 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C69A22442 for ; Thu, 29 May 2014 06:53:08 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id z60so21237781qgd.9 for ; Wed, 28 May 2014 23:53: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=UY9LP8JKz91YbtOeJ8ML8K6QIUp0xlsJLGxUWZgxwKY=; b=b3Pm+tEtNHfQLNmZIdlK3QScAiz61raU4Q7qtAvw3YDe4ZetzpvZsgDeJJkB0WXw0r 3u7U2Em39YlaaHm2Txadz/xVEx0zZfZz/HlxgHn38ciWHtPQiuerb5B9Y2JOBj7LQwVK eclo/Y/LzHnE4+kraDfY0LgFz4xsPNbyw5xZzic/4gAvGURC36l0KVzFmSMM02Bd8l5O UgEC5Q19B1BpGsvx3Tk6iXn7Dmem8xxpmez+bWMi5I6A7hlqrig+jqGzhz4eY7zAx7Xa QwXnuVuc6FjV4N6aK+o0uzkIyrlIjSPpolW0wdSdjzq4ozk4j07Mia10XibXJBv3oRLv bSzQ== MIME-Version: 1.0 X-Received: by 10.229.192.7 with SMTP id do7mr7025035qcb.1.1401346387720; Wed, 28 May 2014 23:53:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Wed, 28 May 2014 23:53:07 -0700 (PDT) In-Reply-To: <1401278431550-5915936.post@n5.nabble.com> References: <1401278431550-5915936.post@n5.nabble.com> Date: Wed, 28 May 2014 23:53:07 -0700 X-Google-Sender-Auth: iShJqZKi9J0_oImQ9YKH4hdSVvs Message-ID: Subject: Re: Does TDMA on FreeBSD only support point to point applications From: Adrian Chadd To: Andy Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 06:53:09 -0000 Hi! Yup. I don't think anyone sat down to figure out how the slot timings should work for >1 slave station. If someone wants to figure it out based on what Sam's paper covers, I'll be happy to help try hacking it up on the Atheros hardware. :-) -a On 28 May 2014 05:00, Andy wrote: > When I try to use TDMA options of FreeBSD on atheros chips, I found it works > fine with point to point applications. > > But when I try to set tdmaslotcnt to bigger than 2, it give the following > error message: > > ifconfig: SIOCS80211: Invalid argument > > Then I try to read man page of ifconfig to get some help, and it is said > that current implementation of TDMA is only tested with two stations.But the > value of the slot cout may be at most 8. > > So now the TDMA of FreeBSD only support point to point connection? > > How could I setup a TDMA network bigger than 2 nodes? > > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/Does-TDMA-on-FreeBSD-only-support-point-to-point-applications-tp5915936.html > Sent from the freebsd-wireless mailing list archive at Nabble.com. > _______________________________________________ > 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 May 29 21:25:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6273F527 for ; Thu, 29 May 2014 21:25:09 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F03CA2967 for ; Thu, 29 May 2014 21:25:08 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id x12so1035562wgg.6 for ; Thu, 29 May 2014 14:25:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=/9fyq6ij/fxe82WLk5LGanKwH7qYGbRHC4goJpx7OTA=; b=fTwPTNyaAHCFQzlipRjQ8dlXasaVVswKHSc+jA2frnTtosFyLTzjXKOrYob/09eZig /1q0uF1MMLC6KmfEYQJSOZ8PZiIcGaeqdnYniGLx/Ai9tETCjKFoMZUFCM7eyUuwfqQ8 YJOipPo22cuE2JPfJMwQyi320AeFadd4bWW1AlJzlkNiOrnL5wI2xFWP1BwTTECbdUua Wsxd+zhHBDO2Ep8s7qVw1OFrPRhCCpln9tyZRWyqoX4xWqcIINNs+yEuD6zG1gFQ400O RvmIpy9at4VrhbSXUqG/33GAUTY5Khr/uX6xMnPiq+SkcX+48DzZPNuBrKwmdguzzODG ak7Q== X-Received: by 10.194.6.166 with SMTP id c6mr14715528wja.64.1401398706159; Thu, 29 May 2014 14:25:06 -0700 (PDT) Received: from netas3k-air.lan (78-60-118-183.static.zebra.lt. [78.60.118.183]) by mx.google.com with ESMTPSA id iy13sm274058wic.1.2014.05.29.14.25.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 May 2014 14:25:05 -0700 (PDT) From: Jonas Liepuonius Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: TP-Link TL-MR3020 Message-Id: Date: Fri, 30 May 2014 00:25:02 +0300 To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-Mailer: Apple Mail (2.1878.2) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 21:25:09 -0000 Hello, I was talking with Adrian, when he said that there is a FreeBSD port for = the TP-Link TL-MR3020. And I want to help, if the person/persons behind = the port are willing to teach me a little bit (I=92m new to the embedded = devices, so I have knowledge that equals almost 0% when it comes to = porting). I would be happy to help and maybe, given time I would port = FreeBSD to TL-MR3040. Thanks, -J= From owner-freebsd-wireless@FreeBSD.ORG Thu May 29 21:26:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 57433549 for ; Thu, 29 May 2014 21:26:08 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 198F3296D for ; Thu, 29 May 2014 21:26:08 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id a108so2835568qge.36 for ; Thu, 29 May 2014 14:26: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:content-transfer-encoding; bh=3YPu14V5rTbBB994stYLi1BDUTGrZjrDtguSYvHPHFM=; b=p+rKpYVNB3vR614PyZRA3aEvwsN++uS2QosNnD2q/c2/BUsWQnkbVqaHFyBU1XUDaJ rceyvmmqY1Bwt1zsw/269PRYir6ApTUWtU8ZKlXPYkCtQwr6C5u2GTjMWA7Fe9vCyynA Xtwe07khm4Pzi21tXih6hVxDRUh0p/U3+UYbg3XKabp/PXsacv7ZxF2DdYaa3S55jBIE Uffx+wGqDTN3HhipZ59dxWqIel4fNeuBDFs1UjJ305thDXOchY0D7TmYv0+ggaEi05zn 8fV/90u/ZBmsZH+7T8jQztVKGdutoP3ZVIn/qwpBVWC6qivEjbX7l9igLLC8aA6xIsnA weGA== MIME-Version: 1.0 X-Received: by 10.140.35.212 with SMTP id n78mr13449730qgn.87.1401398767277; Thu, 29 May 2014 14:26:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Thu, 29 May 2014 14:26:07 -0700 (PDT) In-Reply-To: References: Date: Thu, 29 May 2014 14:26:07 -0700 X-Google-Sender-Auth: E8cwXpo8zWBcz0XdMitCLgQ2sLI Message-ID: Subject: Re: TP-Link TL-MR3020 From: Adrian Chadd To: Jonas Liepuonius Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 21:26:08 -0000 Yeah, so who's doing the MR3020? Sean? -a On 29 May 2014 14:25, Jonas Liepuonius wrote: > Hello, > > I was talking with Adrian, when he said that there is a FreeBSD port for = the TP-Link TL-MR3020. And I want to help, if the person/persons behind the= port are willing to teach me a little bit (I=E2=80=99m new to the embedded= devices, so I have knowledge that equals almost 0% when it comes to portin= g). I would be happy to help and maybe, given time I would port FreeBSD to = TL-MR3040. > > Thanks, > -J > _______________________________________________ > 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" From owner-freebsd-wireless@FreeBSD.ORG Thu May 29 21:45:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DC229DA; Thu, 29 May 2014 21:45:38 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD46E2B43; Thu, 29 May 2014 21:45:37 +0000 (UTC) Received: from [10.168.50.108] (182.sub-70-197-8.myvzw.com [70.197.8.182]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 2744D194139; Thu, 29 May 2014 21:45:36 +0000 (UTC) Date: Thu, 29 May 2014 14:45:33 -0700 Subject: Re: TP-Link TL-MR3020 Message-ID: Importance: normal From: Sean Bruno To: Adrian Chadd , Jonas Liepuonius MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 21:45:38 -0000 WXVwLCB0aGF0J3MgbWUuIEkndmUgZ290dGVuIHRvIHRoZSBuZXRib290IHN0YWdlIGFuZCBub3cg aXMgdGhlIHRpbWUgdG8gZmlndXJlIG91dCBhbGwgdGhlIGJlZnVkZGxpbmcga2VybmNvbmYgdGhp bmdzLiBMZXQgbWUgZ2V0IGhvbWUgYW5kIHJlcGx5IHdpdGggc29tZSBkZXRhaWxzIGFuZCBzdGF0 dXMuCgotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tCkZyb206IEFkcmlhbiBDaGFk ZCA8YWRyaWFuQGZyZWVic2Qub3JnPiAKRGF0ZTowNS8yOS8yMDE0ICAyOjI2IFBNICAoR01ULTA4 OjAwKSAKVG86IEpvbmFzIExpZXB1b25pdXMgPHRoaW5rZXIubHBAZ21haWwuY29tPiAKQ2M6IGZy ZWVic2Qtd2lyZWxlc3NAZnJlZWJzZC5vcmcgClN1YmplY3Q6IFJlOiBUUC1MaW5rIFRMLU1SMzAy MCAKClllYWgsIHNvIHdobydzIGRvaW5nIHRoZSBNUjMwMjA/IFNlYW4/CgoKLWEKCgpPbiAyOSBN YXkgMjAxNCAxNDoyNSwgSm9uYXMgTGllcHVvbml1cyA8dGhpbmtlci5scEBnbWFpbC5jb20+IHdy b3RlOgo+IEhlbGxvLAo+Cj4gSSB3YXMgdGFsa2luZyB3aXRoIEFkcmlhbiwgd2hlbiBoZSBzYWlk IHRoYXQgdGhlcmUgaXMgYSBGcmVlQlNEIHBvcnQgZm9yIHRoZSBUUC1MaW5rIFRMLU1SMzAyMC4g QW5kIEkgd2FudCB0byBoZWxwLCBpZiB0aGUgcGVyc29uL3BlcnNvbnMgYmVoaW5kIHRoZSBwb3J0 IGFyZSB3aWxsaW5nIHRvIHRlYWNoIG1lIGEgbGl0dGxlIGJpdCAoSeKAmW0gbmV3IHRvIHRoZSBl bWJlZGRlZCBkZXZpY2VzLCBzbyBJIGhhdmUga25vd2xlZGdlIHRoYXQgZXF1YWxzIGFsbW9zdCAw JSB3aGVuIGl0IGNvbWVzIHRvIHBvcnRpbmcpLiBJIHdvdWxkIGJlIGhhcHB5IHRvIGhlbHAgYW5k IG1heWJlLCBnaXZlbiB0aW1lIEkgd291bGQgcG9ydCBGcmVlQlNEIHRvIFRMLU1SMzA0MC4KPgo+ IFRoYW5rcywKPiAtSgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fCj4gZnJlZWJzZC13aXJlbGVzc0BmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QKPiBodHRw Oi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXdpcmVsZXNzCj4g VG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8gImZyZWVic2Qtd2lyZWxlc3MtdW5zdWJz Y3JpYmVAZnJlZWJzZC5vcmciCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fCmZyZWVic2Qtd2lyZWxlc3NAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0Cmh0dHA6 Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2Qtd2lyZWxlc3MKVG8g dW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8gImZyZWVic2Qtd2lyZWxlc3MtdW5zdWJzY3Jp YmVAZnJlZWJzZC5vcmci From owner-freebsd-wireless@FreeBSD.ORG Thu May 29 21:47:51 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64545B7B for ; Thu, 29 May 2014 21:47:51 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFA3F2B6A for ; Thu, 29 May 2014 21:47:50 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id n15so79313wiw.14 for ; Thu, 29 May 2014 14:47:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wV0bKHouRUEsJd3ONFKMufDEXFXjexm84afRiOftz8M=; b=rBd8hgU0RPCaZMi/+iyMqeNX5PR/Ka2dWm9SV/96LzFO1ZxnzVDiGf0dih034EQOfr rfhCH4ZDrOw1NgOdLI2igJimfdqRkL/WBsO9kYIDHgiD4P/oMNrnGbcO15W1Ib6fPAWf yRKA16RrOvqLXR8DbpvhdxUsAoxD3LteAsNP6wolyf7ucKUN5m79E3PZD5vLaHiPVE+Y 3rxhjGNHhkKE2uXZmsBX6byhoJARBYipBp9p4QWm2gYzzcH/XvKfnE3gxRMEEaVRf5tk ApV3c50XfSjwyWNTee0zSAKhV331iaEvf6ofdbHyyKf3qrHVqqFbb28DSlXstHD1L8DT /hyQ== X-Received: by 10.194.22.100 with SMTP id c4mr14806949wjf.89.1401400069050; Thu, 29 May 2014 14:47:49 -0700 (PDT) Received: from netas3k-air.lan (78-60-118-183.static.zebra.lt. [78.60.118.183]) by mx.google.com with ESMTPSA id p15sm388699wiv.8.2014.05.29.14.47.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 May 2014 14:47:48 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: TP-Link TL-MR3020 From: Jonas Liepuonius In-Reply-To: Date: Fri, 30 May 2014 00:47:45 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <627DCC50-A228-4C03-B604-0587C4933A11@gmail.com> References: To: Sean Bruno X-Mailer: Apple Mail (2.1878.2) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 21:47:51 -0000 I=92m off to sleep, it=92s a little late here, so I will see your email = tomorrow, till then. -J On 30 May 2014, at 00:45, Sean Bruno wrote: > Yup, that's me. I've gotten to the netboot stage and now is the time = to figure out all the befuddling kernconf things. Let me get home and = reply with some details and status. >=20 > -------- Original message -------- > From: Adrian Chadd=20 > Date:05/29/2014 2:26 PM (GMT-08:00)=20 > To: Jonas Liepuonius=20 > Cc: freebsd-wireless@freebsd.org=20 > Subject: Re: TP-Link TL-MR3020=20 >=20 > Yeah, so who's doing the MR3020? Sean? >=20 >=20 > -a >=20 >=20 > On 29 May 2014 14:25, Jonas Liepuonius wrote: > > Hello, > > > > I was talking with Adrian, when he said that there is a FreeBSD port = for the TP-Link TL-MR3020. And I want to help, if the person/persons = behind the port are willing to teach me a little bit (I=92m new to the = embedded devices, so I have knowledge that equals almost 0% when it = comes to porting). I would be happy to help and maybe, given time I = would port FreeBSD to TL-MR3040. > > > > Thanks, > > -J > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to = "freebsd-wireless-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri May 30 19:20:02 2014 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE46DAD9 for ; Fri, 30 May 2014 19:20:02 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2A8D2754 for ; Fri, 30 May 2014 19:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4UJK2tl084827 for ; Fri, 30 May 2014 19:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4UJK2WP084826; Fri, 30 May 2014 19:20:02 GMT (envelope-from gnats) Date: Fri, 30 May 2014 19:20:02 GMT Message-Id: <201405301920.s4UJK2WP084826@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Sevan Janiyan Subject: Re: docs/120456: ath(4) needs to specify requirement on wlan_scan_sta Reply-To: Sevan Janiyan X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2014 19:20:02 -0000 The following reply was made to PR docs/120456; it has been noted by GNATS. From: Sevan Janiyan To: bug-followup@FreeBSD.org, kargl@troutmask.apl.washington.edu Cc: Subject: Re: docs/120456: ath(4) needs to specify requirement on wlan_scan_sta Date: Fri, 30 May 2014 20:15:32 +0100 This PR is no longer valid, from UPDATING 20080420 "As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta modules were merged into the base wlan module. All references to these modules (e.g. in kernel config files) must be removed." From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 1 07:35:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22146F23 for ; Sun, 1 Jun 2014 07:35:31 +0000 (UTC) Received: from nm23-vm8.access.bullet.mail.bf1.yahoo.com (nm23-vm8.access.bullet.mail.bf1.yahoo.com [216.109.115.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A92572050 for ; Sun, 1 Jun 2014 07:35:30 +0000 (UTC) Received: from [66.196.81.159] by nm23.access.bullet.mail.bf1.yahoo.com with NNFMP; 01 Jun 2014 07:29:10 -0000 Received: from [98.139.244.52] by tm5.access.bullet.mail.bf1.yahoo.com with NNFMP; 01 Jun 2014 07:29:10 -0000 Received: from [127.0.0.1] by smtp114.sbc.mail.bf1.yahoo.com with NNFMP; 01 Jun 2014 07:29:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1401607750; bh=o/ORA2ERDbygnnk/Ne9WLDEUu22NMBmHGA+fqbWWbks=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject; b=WVaMzAnKBwHZ034vebWs7V/pzzfW4JxvPOGuwyUhCRMF9OHT1TDeF/83nEgkBSYsaE35FRRXoB1rTDHHGvjR3anYLekPy8JWVqyYIp9AqmwveStV92Cr94CeQo97bWsRemGv/FrHZdjB9TkeKeNXM6pA4jfpBhCzTOs++xmnYlQ= X-Yahoo-Newman-Id: 422562.69233.bm@smtp114.sbc.mail.bf1.yahoo.com Message-ID: <422562.69233.bm@smtp114.sbc.mail.bf1.yahoo.com> Date: Sun, 1 Jun 2014 00:29:10 -0700 (PDT) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 1TocwREVM1mcDNvbemihtiAnLUyDLdblOL9HmEhS._jYFS8 .e2CQ1UigllkfACjJ.xQF.jKHb4m4I3AW.wsRZHnr9gb2DQluSyaqKn0J3cG haeOVR.xPhsqvtK.Tjhbw5D49YdGzBw_CpGrz2buHO.zGICUzH41ws444IYB RAVGdFPp_Mj7wSyGpXFQ.rhD4P0AANRiM_jBcPCIvNh7ocdhPmyWB.K.szON 72k8FYXQIQytFeaUtgq_SALBnEYt.FSCWV9d4VumZ72ncBspQnBu3eM8pToj AWFEXQqEJaTkjjKGAf5mE7AyU88m.NCaFED9NGYmICWqXQjX8otTw8uLJntG 79IFfxBDSw2IzbHUGTyb55FWzkXKxD0_dX4SUD4MaGKD7JTwTCl7vPWZYT.X G7ZyBwOLyM0mzZatiQDX30ZQ7xwCOBL2CWjYOaOrC1uuZxiImWGXUhexE2EH 6WMSWx0AXpH8q2Ij9wTorZPHmpgTf5y5Q6K6LrZLCTQZqX99g8BiBWvaV_nW T5NdGVnIa.yCTRO3W X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.139.221.42]) by smtp114.sbc.mail.bf1.yahoo.com with SMTP; 01 Jun 2014 00:29:10 -0700 PDT From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: Problem fetching for textproc/qt4-xml Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2014 07:35:31 -0000 I had a problem downloading the big distfile for textproc/qt4-xml, didn't post on the emailing list the first time, but this happened last night with 4.8.6, after previously happening with 4.8.5. It would be unable to connect, or it would connect and then after getting partway through, stop and go to another server and start again. I use Hiro H50191 USB-stick wireless adapter, device rsu, which normally works, but something strrange happens with this port. I got around this problem, first by downloading to a USB stick on the other computer, and sneakernetting, copying to distfiles directory, and then resuming port build. Last night, wireless connection bugged out, and system crashed (11-head amd64). Then. after several reboots trying to fix scrambled state of memory on the computer, booted successfully with NetBSD-current amd64, ran "dhcpcd re0", was conected, went into lynx and downloaded the distifile into FreeBSD ports distfiles directory. I subsequently rebooted into FreeBSD and upgraded the qt4-xml port (4.8.5 was marked vulnerable). A bug in re(4) prevents me from Ethernet connection in FreeBSD, also OpenBSD and DragonFlyBSD, but OK with NetBSD and Linux. This puts Hiro H50191 wireless adapter into heavy use for FreeBSD. This is mysterious to me, why I get stuck on this particular distfile download. I can download other big things, such as System Rescue CD ISO image. Tom From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 2 03:59:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DDAF1789 for ; Mon, 2 Jun 2014 03:59:41 +0000 (UTC) Received: from nm11-vm6.access.bullet.mail.gq1.yahoo.com (nm11-vm6.access.bullet.mail.gq1.yahoo.com [216.39.63.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9169B22BA for ; Mon, 2 Jun 2014 03:59:40 +0000 (UTC) Received: from [216.39.60.167] by nm11.access.bullet.mail.gq1.yahoo.com with NNFMP; 02 Jun 2014 03:57:27 -0000 Received: from [98.138.226.242] by tm3.access.bullet.mail.gq1.yahoo.com with NNFMP; 02 Jun 2014 03:57:27 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.ne1.yahoo.com with NNFMP; 02 Jun 2014 03:57:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1401681447; bh=L9JmNmrDd5+fmfrTcCBG57Q7Yrv6oAHp9JbV25hfGf0=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:Subject; b=OUDgrb6hz8d69Lt8CwPNaHNUFa/wNMoEZctmFgeUxsdnxA+j0SfH5DpGIrcdcx1aQv27MZfxxfYik5b/fyr6YH+q8AjcQock1NH9U0vN+p2msz7AZQpiEbrbdtQtpr4g9n1REV/++XWt+LrlWeeopqW1Xp3HjjdNgd74bGUvFY0= X-Yahoo-Newman-Id: 834918.48417.bm@smtp113.sbc.mail.ne1.yahoo.com Message-ID: <834918.48417.bm@smtp113.sbc.mail.ne1.yahoo.com> Date: Mon, 2 Jun 2014 03:57:27 +0000 (UTC) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: KHmR2XcVM1mSXCofi9KSI9eXreUXxUMIoZywJU7ar7cWXnX Yu7A6hEditEPsGjbWpVqUoddJet.pgEt8p.V3tkQ4Uf48puj7zI763S6LpW8 4oyyog_sG5HXLpNEFDuX2PE__5YlbjZSfDCBvfJ4HIM6FcTIA4_jVNM1q8Iq ivoOfCs3kFXZbI1bkWmzvy_mCJgHGM5w2xQ1zonDW1toXUbn0zjxrfN4bx8V 4R8Wa_8eaTKrvHNWf4Jh_qcG3oPPgbQMcXHvO9GkFluix0jOYvrDAYn6Y7Q3 CZ4zYgbyx9AHsBBNdq2pgosa_hAURcIgrd_xnIFYoY5HN4g6qLAr1nG9lQdj cl18L67rutw8q_.9YGRikr.5gN8YzLOBMyu8H4hGkNImarWoybrUH5B4J2nS hbMQ_xYp2X6UHlSVoMrP0SUgjuDWiSphW2ieotmxFsgfgDKArYz1YCEzU77n 3Ic_8iDcV18pfwCSZI1vK1n5V8V9tnlM9DO0yeAzWa6zb7Plr.6PDQ0hln1r JADqYI7ZNXA1dJoFSz9CYYk7f71XxqI._EeyfoRmOEOrMJ0_TNPI65G.5 X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.138.31.74]) by smtp113.sbc.mail.ne1.yahoo.com with SMTP; 02 Jun 2014 03:57:27 +0000 UTC From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Change for the worse in rsu wireless driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 03:59:41 -0000 WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. I just updated FreeBSD-current, both amd64 and i386, now both rsu and Xorg are highly unstable, at least on amd64. FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r266948: Sun Jun 1 19:12:44 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 root@amelia4:~ # ls -l /usr/src/sys/dev/usb/wlan total 1164 -rw-r--r-- 1 root wheel 65759 Jun 1 16:23 if_rsu.c -rw-r--r-- 1 root wheel 19964 Jun 1 16:23 if_rsureg.h (snip) This is a change for the worse. Now I can connect with Hiro H50191; bug in re Ethernet driver persists, so I can't connect that way. I also had several crashes in Xorg, so am typing this with vi in newcons. Tom From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 2 05:36:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 768E2B1F for ; Mon, 2 Jun 2014 05:36:55 +0000 (UTC) Received: from nm7-vm8.access.bullet.mail.bf1.yahoo.com (nm7-vm8.access.bullet.mail.bf1.yahoo.com [216.109.114.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0AD542AC9 for ; Mon, 2 Jun 2014 05:36:54 +0000 (UTC) Received: from [66.196.81.156] by nm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 02 Jun 2014 05:30:21 -0000 Received: from [98.139.244.50] by tm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 02 Jun 2014 05:30:21 -0000 Received: from [127.0.0.1] by smtp112.sbc.mail.bf1.yahoo.com with NNFMP; 02 Jun 2014 05:30:21 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1401687021; bh=yoiML6cuuCxpFuLf0U4JfKcUJOG2piOLe7+c+4TwoSc=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject; b=0DwTFICoTwdzYCD6fGzqygK6/HOiA8WrT+kFJ+sZSttteS4FzUuoCWSArqYyuQtE8jx0zTrvnTQe8REYOOdiRWvVC09osllCg2lRJ4SltgW9/1fP4bhs811rqa9vfWtYf3EnUdD5z/6P48gXc3CiXH54bWp8N1GmNtrqIKcU5Ss= X-Yahoo-Newman-Id: 792139.75850.bm@smtp112.sbc.mail.bf1.yahoo.com Message-ID: <792139.75850.bm@smtp112.sbc.mail.bf1.yahoo.com> Date: Sun, 1 Jun 2014 22:30:21 -0700 (PDT) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: k50tE7QVM1kFF_._7.bk3PTcuIM0CoEnEkmpw7L8QFsdQxI 4gh7pHI7lk1ipIQNTjb7T3iLODMXgHMTCYyRfmMNPnD0vOgtjFEehIQjhgJe S22kyjXre0uHA8lsh9YZ9sVQnYLBp6lJOja1VUX6NQGtQDWEF82ZGNm_6ppH KDEUxWnTcHV7H2JvaKzKyE_DznOn0wYe6E4EYh4zxoN_Nw2_UPHeRL9VHxXc Hd1MIrRzpeRDR_Jm5SlpQ2mxM4Je2A0wFheQHHrMIoZfZUyii0KBeoBfHmD. HwooFZj5FLnV7enIYBn3ug5ydKle.1cRvXViOCYp46373UJoGGu_2mzMRMbX uuOmK3OS76bLRkQS9CpYIqg2.KwX4IQ8WINeiCyrpbza0PBZsICFSwvV7GnJ qxiq9A2du9ulR8A0.yn78b8z_PWzXSHJmX_3kPVwAS3kK2VP3H3MWpsvQ5EG EcS84S3pCML4ybllGdvXg1sPB2iYYkND_0m0lLrEMO6.m7bJxI72NUrArrM5 d26xYiR2nKcO8kheiz.CR8KKBLo0I4JLIyGcXH7Ka4CCFgVj8kuKHmvqi X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.139.221.42]) by smtp112.sbc.mail.bf1.yahoo.com with SMTP; 01 Jun 2014 22:30:21 -0700 PDT From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Change for the worse in rsu wireless driver Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 05:36:55 -0000 I sent this message, without this top part, over an hour ago, and notice wlan0 is still up. I intended but forgot to CC to freebsd-current. But I am in newcons, having not started X so far this boot session. Maybe something rotten with Xorg, or interaction between rsu and X, or rsu and Firefox. I am afraid to try again with X, don't want to mess the file system to the extent of losing data. WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. I just updated FreeBSD-current, both amd64 and i386, now both rsu and Xorg are highly unstable, at least on amd64. FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r266948: Sun Jun 1 19:12:44 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 root@amelia4:~ # ls -l /usr/src/sys/dev/usb/wlan total 1164 -rw-r--r-- 1 root wheel 65759 Jun 1 16:23 if_rsu.c -rw-r--r-- 1 root wheel 19964 Jun 1 16:23 if_rsureg.h (snip) This is a change for the worse. Now I can connect with Hiro H50191; bug in re Ethernet driver persists, so I can't connect that way. I also had several crashes in Xorg, so am typing this with vi in newcons. Tom From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 2 07:12:44 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 36EFFEDC; Mon, 2 Jun 2014 07:12:44 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB58321F1; Mon, 2 Jun 2014 07:12:43 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 248611FE026; Mon, 2 Jun 2014 09:12:41 +0200 (CEST) Message-ID: <538C2412.4030600@selasky.org> Date: Mon, 02 Jun 2014 09:13:22 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <792139.75850.bm@smtp112.sbc.mail.bf1.yahoo.com> In-Reply-To: <792139.75850.bm@smtp112.sbc.mail.bf1.yahoo.com> 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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 07:12:44 -0000 On 06/02/14 07:30, Thomas Mueller wrote: > I sent this message, without this top part, over an hour ago, and notice wlan0 is still up. I intended but forgot to CC to freebsd-current. But I am in newcons, having not started X so far this boot session. Maybe something rotten with Xorg, or interaction between rsu and X, or rsu and Firefox. > > I am afraid to try again with X, don't want to mess the file system to the extent of losing data. > > WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. > > I just updated FreeBSD-current, both amd64 and i386, now both rsu and Xorg are highly unstable, at least on amd64. > > FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r266948: Sun Jun 1 19:12:44 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 > > root@amelia4:~ # ls -l /usr/src/sys/dev/usb/wlan > > total 1164 > > -rw-r--r-- 1 root wheel 65759 Jun 1 16:23 if_rsu.c > > -rw-r--r-- 1 root wheel 19964 Jun 1 16:23 if_rsureg.h > > (snip) > > This is a change for the worse. Now I can connect with Hiro H50191; bug in re Ethernet driver persists, so I can't connect that way. > > I also had several crashes in Xorg, so am typing this with vi in newcons. > > Tom Hi, Re-compile the rsu module with USB debugging enabled: Add to: sys/modules/usb/rsu/Makefile CFLAGS+= -DUSB_DEBUG Rebuild and install. After that lookup the debug knob using "sysctl hw.usb | grep rsu" and set it to 16. Then collect some debug messages in dmesg, when problems appear. Thank you. --HPS From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 2 17:21:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 752373B9 for ; Mon, 2 Jun 2014 17:21:37 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EE002EF9 for ; Mon, 2 Jun 2014 17:21:36 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id k14so5488469wgh.19 for ; Mon, 02 Jun 2014 10:21:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=4ub3QHRa9PDGxbH86IfQXk8Cg2mepG+xqq6jtGmtWnI=; b=NyJPPXGyo+jgkBw35sKrmpq/PFL/u1d9uJpSpHAl/4dLGVNkfLfrProB9BjWGGQ4Vp x7i/E6iM8FTxMJqCjje8xjHeKu2mJHMygfpDM1D0W44XlHnjud/HJafRD0q65vcidOaf 93QJBItT8q9LRd2i2+sgCP3CxrTvu1k1qHXoWYgNfhVejdh7sVNiHMbrJgqeruX2cCvf a5B6pkIotLBwJzVQzTdnIk4uLG2UKGZ4hIiiadUbpoG/ekaMNDY/djo9U68OeCE/Mx7J nfuMPmkEVH8souvkMHQw4WVHbZOmIKXXeoJ8ahSj9BQZRZRKyNdY3gEc9Hef+BhvZJ1R 0WLg== X-Received: by 10.180.81.102 with SMTP id z6mr8447394wix.54.1401729695245; Mon, 02 Jun 2014 10:21:35 -0700 (PDT) Received: from [192.168.178.21] (s529c5c1b.adsl.online.nl. [82.156.92.27]) by mx.google.com with ESMTPSA id hi6sm36929253wjc.32.2014.06.02.10.21.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Jun 2014 10:21:34 -0700 (PDT) Message-ID: <538CB2A1.2080904@gmail.com> Date: Mon, 02 Jun 2014 19:21:37 +0200 From: Idwer Vollering User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <538C2412.4030600@selasky.org> In-Reply-To: <538C2412.4030600@selasky.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 17:21:37 -0000 I have a patch for that: Index: head/sys/dev/usb/wlan/if_rsu.c =================================================================== --- head/sys/dev/usb/wlan/if_rsu.c (revision 266970) +++ head/sys/dev/usb/wlan/if_rsu.c (working copy) @@ -69,11 +69,13 @@ #include +static SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); + #ifdef USB_DEBUG -static int rsu_debug = 0; -SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); -SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW, &rsu_debug, 0, +int rsu_debug = 0; +SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW | CTLFLAG_TUN, &rsu_debug, 0, "Debug level"); +TUNABLE_INT("hw.usb.rsu.debug", &rsu_debug); #endif static const STRUCT_USB_HOST_ID rsu_devs[] = { @@ -1284,7 +1286,7 @@ DPRINTF("WPS PBC pushed.\n"); break; case R92S_EVT_FWDBG: - if (ifp->if_flags & IFF_DEBUG) { + if (rsu_debug >= 6) { buf[60] = '\0'; printf("FWDBG: %s\n", (char *)buf); } From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 10:16:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EDA0F96C for ; Tue, 3 Jun 2014 10:16:32 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) by mx1.freebsd.org (Postfix) with ESMTP id BE0392720 for ; Tue, 3 Jun 2014 10:16:32 +0000 (UTC) Received: from [96.28.178.143] ([96.28.178.143:53642] helo=localhost) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 5E/43-11813-830AD835; Tue, 03 Jun 2014 10:15:20 +0000 Date: Tue, 03 Jun 2014 10:15:20 +0000 Message-ID: <5E.43.11813.830AD835@dnvrco-oedge02> From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Change for the worse in rsu wireless driver X-RR-Connecting-IP: 107.14.64.130:25 X-Authority-Analysis: v=2.1 cv=a+i+9CiF c=1 sm=1 tr=0 a=RKm8ZHSrUWUxlfG+7GhaOw==:117 a=RKm8ZHSrUWUxlfG+7GhaOw==:17 a=ayC55rCoAAAA:8 a=8SutbUg_jKoA:10 a=DvSzqBOGy98A:10 a=pedpZTtsAAAA:8 a=pGLkceISAAAA:8 a=5bXU4cA67BCs1vZ52VAA:9 a=MSl-tDqOz04A:10 X-Cloudmark-Score: 0 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 10:16:33 -0000 from Idwer Vollering : I have a patch for that: Index: head/sys/dev/usb/wlan/if_rsu.c =================================================================== --- head/sys/dev/usb/wlan/if_rsu.c (revision 266970) +++ head/sys/dev/usb/wlan/if_rsu.c (working copy) @@ -69,11 +69,13 @@ #include +static SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); + #ifdef USB_DEBUG -static int rsu_debug = 0; -SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); -SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW, &rsu_debug, 0, +int rsu_debug = 0; +SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW | CTLFLAG_TUN, &rsu_debug, 0, "Debug level"); +TUNABLE_INT("hw.usb.rsu.debug", &rsu_debug); #endif static const STRUCT_USB_HOST_ID rsu_devs[] = { @@ -1284,7 +1286,7 @@ DPRINTF("WPS PBC pushed.\n"); break; case R92S_EVT_FWDBG: - if (ifp->if_flags & IFF_DEBUG) { + if (rsu_debug >= 6) { buf[60] = '\0'; printf("FWDBG: %s\n", (char *)buf); } (end of quote) I do not put "> " in front of these lines for quoting here. Patch failed to apply, something was malformed. I have no directory named head, but even removing that left errors. I suppose I could look through original file and patch, and manually make the changes with vi. Should I try that? I am already long overdue for bed. Anyway, I have other stuff to do on computer, including NetBSD-current amd64 and i386 installations on USB sticks, plan to install on new hard drive as well. I'll be more inclined to come back when cups 1.7.3 becomes available in ports tree. I need to be able to print. Maybe NetBSD will be mainly a way station for cross-compiling Linux? Now FreeBSD 11-current amd64 betrays me again as I lost the wireless connection and have to boot into my FreeBSD 10-stable amd64 or i386 installation or NetBSD-head amd64. Tom From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 18:24:11 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D626B25D; Tue, 3 Jun 2014 18:24:11 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 98E022804; Tue, 3 Jun 2014 18:24:11 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 3D9331FE027; Tue, 3 Jun 2014 20:24:10 +0200 (CEST) Message-ID: <538E12ED.3050101@selasky.org> Date: Tue, 03 Jun 2014 20:24:45 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <5E.43.11813.830AD835@dnvrco-oedge02> In-Reply-To: <5E.43.11813.830AD835@dnvrco-oedge02> 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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 18:24:11 -0000 On 06/03/14 12:15, Thomas Mueller wrote: > from Idwer Vollering : > > I have a patch for that: > > Index: head/sys/dev/usb/wlan/if_rsu.c > =================================================================== > --- head/sys/dev/usb/wlan/if_rsu.c (revision 266970) > +++ head/sys/dev/usb/wlan/if_rsu.c (working copy) > @@ -69,11 +69,13 @@ > > #include > > +static SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); > + > #ifdef USB_DEBUG > -static int rsu_debug = 0; > -SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); > -SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW, &rsu_debug, 0, > +int rsu_debug = 0; > +SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW | CTLFLAG_TUN, > &rsu_debug, 0, > "Debug level"); > +TUNABLE_INT("hw.usb.rsu.debug", &rsu_debug); > #endif > > static const STRUCT_USB_HOST_ID rsu_devs[] = { > @@ -1284,7 +1286,7 @@ > DPRINTF("WPS PBC pushed.\n"); > break; > case R92S_EVT_FWDBG: > - if (ifp->if_flags & IFF_DEBUG) { > + if (rsu_debug >= 6) { > buf[60] = '\0'; > printf("FWDBG: %s\n", (char *)buf); > } > > (end of quote) > > I do not put "> " in front of these lines for quoting here. > > Patch failed to apply, something was malformed. > > I have no directory named head, but even removing that left errors. > > I suppose I could look through original file and patch, and manually make the changes with vi. Should I try that? I am already long overdue for bed. > > Anyway, I have other stuff to do on computer, including NetBSD-current amd64 and i386 installations on USB sticks, plan to install on new hard drive as well. > > I'll be more inclined to come back when cups 1.7.3 becomes available in ports tree. I need to be able to print. Maybe NetBSD will be mainly a way station for cross-compiling Linux? > > Now FreeBSD 11-current amd64 betrays me again as I lost the wireless connection and have to boot into my FreeBSD 10-stable amd64 or i386 installation or NetBSD-head amd64. > > Tom Yes, please apply by hand. I'll see if I can do some testing myself. I happen to have one of these adapters too and the link is very unstable :-) --HPS From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 18:37:22 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA7D4A33 for ; Tue, 3 Jun 2014 18:37:22 +0000 (UTC) Received: from server1.weites.net (mail.weites.com [89.188.29.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9247B2928 for ; Tue, 3 Jun 2014 18:37:21 +0000 (UTC) Received: from [10.14.92.96] (5ED685D2.cm-7-7c.dynamic.ziggo.nl [94.214.133.210]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: harm@weites.com) by server1.weites.net (Postfix) with ESMTPSA id 97040722BA for ; Tue, 3 Jun 2014 20:30:02 +0200 (CEST) Message-ID: <538E144C.1080400@weites.com> Date: Tue, 03 Jun 2014 20:30:36 +0200 From: Harm Weites User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Trouble setting up multi SSID and 802.1X Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 18:37:23 -0000 Hi, While trying to setup an AP with two SSID's I ran into some issues. Environment: TP-Link 1043ND (MIPS) ath0 ether 00:19:e0:66:66:68 wlan0 ether 02:ab:cd:ef:12:30 wlan1 ether 00:19:e0:66:66:68 Both wlan0 and wlan1 have been created with wlandev ath0 and wlanmode hostap. The goal is to have one guest wifi network, locked down using pf and having a proper wifi network using radius for personal use (thus, without pf). This is the hostapd config: # ctrl_interface=/var/run/hostapd hw_mode=g bss=wlan0 interface=wlan0 driver=bsd ssid=gasten wpa=3 wpa_key_mgmt=WPA-PSK wpa_passphrase=comegetsome wpa_pairwise=CCMP bss=wlan1 driver=bsd ssid=prive wpa=1 wpa_key_mgmt=WPA-EAP wpa_pairwise=TKIP wpa_group_rekey=300 wpa_gmk_rekey=640 ieee8021x=1 auth_algs=1 eapol_key_index_workaround=1 own_ip_addr=127.0.0.1 nas_identifier=wifi.example.com auth_server_addr=10.65.0.130 auth_server_port=1812 auth_server_shared_secret=secret acct_server_addr=10.65.0.130 acct_server_port=1813 acct_server_shared_secret=secret # Now, hostapd complains about the following: Configuration file: /etc/hostapd.conf Using interface wlan0 with hwaddr 02:ab:cd:ef:12:30 and ssid "gasten" Failed to add BSS (BSSID=02:ab:cd:ef:12:31) wlan0: Unable to setup interface. Failed to remove BSS interface wlan0 Thats it for having multiple (2) SSID's. Now, the 2nd issue: radius. For this, I've disabled the passphrase'd SSID to have just one (working) SSID. I haven't given the backend much attention just yet, but I'm seeing the following error after trying to associate: wlan0: STA a8:16:b2:54:9c:ef IEEE 802.11: associated wlan0: CTRL-EVENT-EAP-STARTED a8:16:b2:54:9c:ef wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 wlan0: STA a8:16:b2:54:9c:ef IEEE 802.11: disassociated ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory This is using an Android device, with PEAP. I haven't got a clue yet on which mode I should be using, or how to configure that but since I'm seeing a 'No such file or directory' I'm afraid something needs to be resolved before diving into the final configuration (if this was about cert/key files, shouldn't it just explicitly say it's missing just that?). Attached to this message is some debug output from hostapd from the connection attempt. Regards, Harm From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 18:40:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B3B01A77 for ; Tue, 3 Jun 2014 18:40:46 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 746E12940 for ; Tue, 3 Jun 2014 18:40:46 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id m5so5610361qaj.30 for ; Tue, 03 Jun 2014 11:40: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=ZKbUkoOfr5CBYQ4ZcqiGzahsetYORa4StSHR5A4kUQI=; b=KEofk/QQuRpBcXoR7E1A1mJHh0VDAYN0mDEhKFtjFy38uNfi5CaxGdUeFolOTnPwkC JDkV1L+/Wri3GexXRB/LkE9JGn6tHCjsL2HqMOc4NKVeTWJT+0aNRxQWSd+XBrAqSVSf lYDHIfZb1HximnoRDktgm8ZSzL2/LmDPHUN7Q40Z1JY2OIaysPufUHFuXC2/WgFiJ/4Q +M7Jo2y3CiToz4IqGFtrYXraC1qHxdgx/kTunkqav00XwIwzrEAier5zTKuYmIX+tTnf URJFs+LuZPHKVvutL4OHV4Xm5wQtC+MvF+3aSubnu/+BDVwNA7dRZQem0r1qrcq3PngM M9Eg== MIME-Version: 1.0 X-Received: by 10.224.135.66 with SMTP id m2mr65874308qat.55.1401820845564; Tue, 03 Jun 2014 11:40:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Tue, 3 Jun 2014 11:40:45 -0700 (PDT) In-Reply-To: <538E144C.1080400@weites.com> References: <538E144C.1080400@weites.com> Date: Tue, 3 Jun 2014 11:40:45 -0700 X-Google-Sender-Auth: SoUxfHgaKCt51pEPddkFJP75H4Q Message-ID: Subject: Re: Trouble setting up multi SSID and 802.1X From: Adrian Chadd To: Harm Weites Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 18:40:46 -0000 Is hat in one config file? Or two hostapd config files? -a On 3 June 2014 11:30, Harm Weites wrote: > Hi, > > While trying to setup an AP with two SSID's I ran into some issues. > > Environment: > TP-Link 1043ND (MIPS) > ath0 ether 00:19:e0:66:66:68 > wlan0 ether 02:ab:cd:ef:12:30 > wlan1 ether 00:19:e0:66:66:68 > > Both wlan0 and wlan1 have been created with wlandev ath0 and wlanmode > hostap. The goal is to have one guest wifi network, locked down using pf > and having a proper wifi network using radius for personal use (thus, > without pf). > > This is the hostapd config: > > # > ctrl_interface=/var/run/hostapd > hw_mode=g > > bss=wlan0 > interface=wlan0 > driver=bsd > ssid=gasten > wpa=3 > wpa_key_mgmt=WPA-PSK > wpa_passphrase=comegetsome > wpa_pairwise=CCMP > > bss=wlan1 > driver=bsd > ssid=prive > wpa=1 > wpa_key_mgmt=WPA-EAP > wpa_pairwise=TKIP > wpa_group_rekey=300 > wpa_gmk_rekey=640 > ieee8021x=1 > auth_algs=1 > eapol_key_index_workaround=1 > own_ip_addr=127.0.0.1 > nas_identifier=wifi.example.com > auth_server_addr=10.65.0.130 > auth_server_port=1812 > auth_server_shared_secret=secret > acct_server_addr=10.65.0.130 > acct_server_port=1813 > acct_server_shared_secret=secret > # > > Now, hostapd complains about the following: > > Configuration file: /etc/hostapd.conf > Using interface wlan0 with hwaddr 02:ab:cd:ef:12:30 and ssid "gasten" > Failed to add BSS (BSSID=02:ab:cd:ef:12:31) > wlan0: Unable to setup interface. > Failed to remove BSS interface wlan0 > > Thats it for having multiple (2) SSID's. > > Now, the 2nd issue: radius. For this, I've disabled the passphrase'd > SSID to have just one (working) SSID. > > I haven't given the backend much attention just yet, but I'm seeing the > following error after trying to associate: > > wlan0: STA a8:16:b2:54:9c:ef IEEE 802.11: associated > wlan0: CTRL-EVENT-EAP-STARTED a8:16:b2:54:9c:ef > wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 > wlan0: STA a8:16:b2:54:9c:ef IEEE 802.11: disassociated > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory > > This is using an Android device, with PEAP. I haven't got a clue yet on > which mode I should be using, or how to configure that but since I'm > seeing a 'No such file or directory' I'm afraid something needs to be > resolved before diving into the final configuration (if this was about > cert/key files, shouldn't it just explicitly say it's missing just > that?). Attached to this message is some debug output from hostapd from > the connection attempt. > > Regards, > Harm > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 19:25:50 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 38BB7A1D for ; Tue, 3 Jun 2014 19:25:50 +0000 (UTC) Received: from server1.weites.net (mail.weites.com [89.188.29.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC7CE2DA6 for ; Tue, 3 Jun 2014 19:25:49 +0000 (UTC) Received: from [10.14.92.96] (5ED685D2.cm-7-7c.dynamic.ziggo.nl [94.214.133.210]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: harm@weites.com) by server1.weites.net (Postfix) with ESMTPSA id 5D049722BA for ; Tue, 3 Jun 2014 21:25:11 +0200 (CEST) Message-ID: <538E213A.8060902@weites.com> Date: Tue, 03 Jun 2014 21:25:46 +0200 From: Harm Weites User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: Re: Trouble setting up multi SSID and 802.1X References: <538E144C.1080400@weites.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 19:25:50 -0000 Just a single file. I'm running a single instance of hostapd, like this: /sbin/hostapd -B /etc/hostapd.conf op 03-06-14 20:40, Adrian Chadd schreef: > Is hat in one config file? Or two hostapd config files? > > > > -a > > > On 3 June 2014 11:30, Harm Weites wrote: >> Hi, >> >> While trying to setup an AP with two SSID's I ran into some issues. >> >> Environment: >> TP-Link 1043ND (MIPS) >> ath0 ether 00:19:e0:66:66:68 >> wlan0 ether 02:ab:cd:ef:12:30 >> wlan1 ether 00:19:e0:66:66:68 >> >> Both wlan0 and wlan1 have been created with wlandev ath0 and wlanmode >> hostap. The goal is to have one guest wifi network, locked down using pf >> and having a proper wifi network using radius for personal use (thus, >> without pf). >> >> This is the hostapd config: >> >> # >> ctrl_interface=/var/run/hostapd >> hw_mode=g >> >> bss=wlan0 >> interface=wlan0 >> driver=bsd >> ssid=gasten >> wpa=3 >> wpa_key_mgmt=WPA-PSK >> wpa_passphrase=comegetsome >> wpa_pairwise=CCMP >> >> bss=wlan1 >> driver=bsd >> ssid=prive >> wpa=1 >> wpa_key_mgmt=WPA-EAP >> wpa_pairwise=TKIP >> wpa_group_rekey=300 >> wpa_gmk_rekey=640 >> ieee8021x=1 >> auth_algs=1 >> eapol_key_index_workaround=1 >> own_ip_addr=127.0.0.1 >> nas_identifier=wifi.example.com >> auth_server_addr=10.65.0.130 >> auth_server_port=1812 >> auth_server_shared_secret=secret >> acct_server_addr=10.65.0.130 >> acct_server_port=1813 >> acct_server_shared_secret=secret >> # >> >> Now, hostapd complains about the following: >> >> Configuration file: /etc/hostapd.conf >> Using interface wlan0 with hwaddr 02:ab:cd:ef:12:30 and ssid "gasten" >> Failed to add BSS (BSSID=02:ab:cd:ef:12:31) >> wlan0: Unable to setup interface. >> Failed to remove BSS interface wlan0 >> >> Thats it for having multiple (2) SSID's. >> >> Now, the 2nd issue: radius. For this, I've disabled the passphrase'd >> SSID to have just one (working) SSID. >> >> I haven't given the backend much attention just yet, but I'm seeing the >> following error after trying to associate: >> >> wlan0: STA a8:16:b2:54:9c:ef IEEE 802.11: associated >> wlan0: CTRL-EVENT-EAP-STARTED a8:16:b2:54:9c:ef >> wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 >> wlan0: STA a8:16:b2:54:9c:ef IEEE 802.11: disassociated >> ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory >> ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory >> >> This is using an Android device, with PEAP. I haven't got a clue yet on >> which mode I should be using, or how to configure that but since I'm >> seeing a 'No such file or directory' I'm afraid something needs to be >> resolved before diving into the final configuration (if this was about >> cert/key files, shouldn't it just explicitly say it's missing just >> that?). Attached to this message is some debug output from hostapd from >> the connection attempt. >> >> Regards, >> Harm >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 20:21:50 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53F9F1C5 for ; Tue, 3 Jun 2014 20:21:50 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B69D26B7 for ; Tue, 3 Jun 2014 20:21:50 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s53KLoGx043398 for ; Tue, 3 Jun 2014 21:21:50 +0100 (BST) (envelope-from no-reply-bugzilla-daemon@freebsd.org) From: no-reply-bugzilla-daemon@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 170397] [ath] [patch] Uninitialized variables in ah_eeprom_9287.c Date: Tue, 03 Jun 2014 20:21:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dim@FreeBSD.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 20:21:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170397 Dimitry Andric changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |FIXED --- Comment #2 from Dimitry Andric --- Fixed in r239704. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 3 20:23:16 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF4B7203 for ; Tue, 3 Jun 2014 20:23:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A68C926D6 for ; Tue, 3 Jun 2014 20:23:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s53KNG3t061877 for ; Tue, 3 Jun 2014 21:23:16 +0100 (BST) (envelope-from no-reply-bugzilla-daemon@freebsd.org) From: no-reply-bugzilla-daemon@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 170411] [ath] Uninitialized variables in if_ath.c Date: Tue, 03 Jun 2014 20:23:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dim@FreeBSD.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 20:23:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170411 Dimitry Andric changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |FIXED --- Comment #2 from Dimitry Andric --- Fixed in r241229. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 00:00:10 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2256B61C for ; Wed, 4 Jun 2014 00:00:10 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04D512927 for ; Wed, 4 Jun 2014 00:00:10 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s54009uu024255 for ; Wed, 4 Jun 2014 01:00:09 +0100 (BST) (envelope-from no-reply-bugzilla-daemon@freebsd.org) From: no-reply-bugzilla-daemon@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 177530] [ath] ath driver isn't 32 bit int clean Date: Wed, 04 Jun 2014 00:00:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 00:00:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177530 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved CC| |adrian@freebsd.org Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 02:19:06 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C525EBF1 for ; Wed, 4 Jun 2014 02:19:06 +0000 (UTC) Received: from nm3-vm3.access.bullet.mail.bf1.yahoo.com (nm3-vm3.access.bullet.mail.bf1.yahoo.com [216.109.114.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5638A243D for ; Wed, 4 Jun 2014 02:19:06 +0000 (UTC) Received: from [66.196.81.158] by nm3.access.bullet.mail.bf1.yahoo.com with NNFMP; 04 Jun 2014 02:13:38 -0000 Received: from [98.138.104.97] by tm4.access.bullet.mail.bf1.yahoo.com with NNFMP; 04 Jun 2014 02:13:38 -0000 Received: from [127.0.0.1] by smtp117.sbc.mail.ne1.yahoo.com with NNFMP; 04 Jun 2014 02:13:38 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1401848018; bh=JEDJTvXq9VA8WpWvmSjUEBvjeD+gt7QGz6WJWThX83g=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject:References; b=VNJqzHLUzy6JoFCwjtiJoWppbxjqPdxuRYpxz7a2vSH+XSjMprw3GTVkdsinhQ/RZSeebHCwcU2RGN611//uaTma7XQuNoALEQiNAkpB/SRRLomKyPHYLEj6vRVcZOaGLgrEOSDoIdzc+dTHTdcaZpR6W1QxNWjCtzYZvH/B66w= X-Yahoo-Newman-Id: 547734.11001.bm@smtp117.sbc.mail.ne1.yahoo.com Message-ID: <547734.11001.bm@smtp117.sbc.mail.ne1.yahoo.com> Date: Wed, 4 Jun 2014 02:13:38 +0000 (UTC) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: MnZlS_gVM1keYZLMG29zGD8geCfaCI7tBvMpWylBRaKqjut LptOe8PJ4CGKE9JsojulzXwKKwMzVUEC8UaT2m2RXHbBwScI0wNWb4SM9xci mwKcDmaxCf_RmCLZlhuoCeNHdP55qSsZI23edfYH5kyaciO0y1CohL6Z8iTk QkaDsl6stbvMYupAP.hMIC9Z05Y.cby3mrVZC96pStLVYVvTDi2XvWUQK8ZG kaI1xZvNB7UEwZUh6ZMDW6StRGTFTWaU1KhniaobO7_n_IMr.LHv0vn0dgwk UrRzk_MbzKz04kg53DWAHZv2xjtOOILChIR.suYkss.TjTHJ.n7yB8qotdSN TwzXOJQzfgEp4Sp9_WVqxcIlTOP_BqVhFH62tZYjeZIJNEma4soIURWteSVV NTk6vaGQfx0kmyCEnaS.YRRtEQqo4uPOxbl2DaA_fRhDzm9QrmT2umeRz.eB dPVpLF4zkzdgeKQ8WroFLkXVVmLJYOtx46ifaUtNefDAxRhX8.rihC7YL8if fjTRZPaRqn5FMqvIs5MsTKVWDItzzVgDJyGBwNF7xi9RgNz5rvXLZ9pyZqWH vFLwruQPVvb3e_ION9y69wsi51QI2JEjwElVCZJ4iX2dzKy_4Nedbn8RDuTP THR0npF.sTQVldDJeAMB3Bjsy X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.138.31.74]) by smtp117.sbc.mail.ne1.yahoo.com with SMTP; 04 Jun 2014 02:13:38 +0000 UTC From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <5E.43.11813.830AD835@dnvrco-oedge02> <538E12ED.3050101@selasky.org> Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 02:19:06 -0000 > Yes, please apply by hand. I'll see if I can do some testing myself. I happen to have one of these adapters too and the link is very unstable :-) --HPS Sometimes Hiro H50191 USB-stick wireless adapter works well in FreeBSD, sometimes, like now and the past few days, it's flaky. It can't seem to download distfile for qt4-xml, on two occasions. I also have Atheros AR9271 quasi-USB wireless adapter on this motherboard as well as Realtek 8111E (?) Ethernet that is recognized by FreeBSD but fails to connect (same as with OpenBSD and DragonFlyBSD, but good with NetBSD and Linux). So I don't want to buy another wireless adapter (USB or PCIE?) until I find if the Hiro H50191 works better with Linux and OpenBSD. Maybe the hardware is perfectly good and the software is soft. All I have for OpenBSD is LiveUSB OpenBSD 5.4 from liveusb-openbsd.sourceforge.net , since OpenBSD can't read my hard drive at all, neither could DragonFlyBSD. Tom From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 04:07:30 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7EF4F968 for ; Wed, 4 Jun 2014 04:07:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65A132E83 for ; Wed, 4 Jun 2014 04:07:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5447UNL087099 for ; Wed, 4 Jun 2014 05:07:30 +0100 (BST) (envelope-from no-reply-bugzilla-daemon@freebsd.org) From: no-reply-bugzilla-daemon@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 173711] [ath] powerd kills ath on the Asus EeePC 1005HA Date: Wed, 04 Jun 2014 04:07:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rpaulo@FreeBSD.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 04:07:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173711 Rui Paulo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |FIXED --- Comment #2 from Rui Paulo --- Issue no longer happens in stable/10. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 06:52:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53162F32; Wed, 4 Jun 2014 06:52:57 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1101A2D1F; Wed, 4 Jun 2014 06:52:56 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 861DB1FE028; Wed, 4 Jun 2014 08:52:54 +0200 (CEST) Message-ID: <538EC269.8020701@selasky.org> Date: Wed, 04 Jun 2014 08:53:29 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <5E.43.11813.830AD835@dnvrco-oedge02> <538E12ED.3050101@selasky.org> <547734.11001.bm@smtp117.sbc.mail.ne1.yahoo.com> In-Reply-To: <547734.11001.bm@smtp117.sbc.mail.ne1.yahoo.com> 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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 06:52:57 -0000 On 06/04/14 04:13, Thomas Mueller wrote: >> Yes, please apply by hand. I'll see if I can do some testing myself. I happen to have one of these adapters too and the link is very unstable :-) > --HPS > > Sometimes Hiro H50191 USB-stick wireless adapter works well in FreeBSD, sometimes, like now and the past few days, it's flaky. It can't seem to download distfile for qt4-xml, on two occasions. > > I also have Atheros AR9271 quasi-USB wireless adapter on this motherboard as well as Realtek 8111E (?) Ethernet that is recognized by FreeBSD but fails to connect (same as with OpenBSD and DragonFlyBSD, but good with NetBSD and Linux). > > So I don't want to buy another wireless adapter (USB or PCIE?) until I find if the Hiro H50191 works better with Linux and OpenBSD. Maybe the hardware is perfectly good and the software is soft. > > All I have for OpenBSD is LiveUSB OpenBSD 5.4 from liveusb-openbsd.sourceforge.net , since OpenBSD can't read my hard drive at all, neither could DragonFlyBSD. > > Tom Previously there was a bug in the if_rsu driver that prevented the firmware from loading. Is this device on your mainboard? Does the BIOS support it? --HPS From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 08:00:25 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2AC5A332 for ; Wed, 4 Jun 2014 08:00:25 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0EBB322EE for ; Wed, 4 Jun 2014 08:00:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5480OAL052199 for ; Wed, 4 Jun 2014 09:00:24 +0100 (BST) (envelope-from bz-noreply@freebsd.org) Message-Id: <201406040800.s5480OAL052199@kenobi.freebsd.org> From: bz-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Wed, 04 Jun 2014 08:00:24 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 08:00:25 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is an experimental feature. Please file a bug or mail bugmeister@ with concerns. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 09:22:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FF91722; Wed, 4 Jun 2014 09:22:57 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12E2929EC; Wed, 4 Jun 2014 09:22:56 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C0BAE1FE029; Wed, 4 Jun 2014 11:22:55 +0200 (CEST) Message-ID: <538EE593.90802@selasky.org> Date: Wed, 04 Jun 2014 11:23:31 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <5E.43.11813.830AD835@dnvrco-oedge02> <538E12ED.3050101@selasky.org> <547734.11001.bm@smtp117.sbc.mail.ne1.yahoo.com> <538EC269.8020701@selasky.org> In-Reply-To: <538EC269.8020701@selasky.org> 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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 09:22:57 -0000 On 06/04/14 08:53, Hans Petter Selasky wrote: > On 06/04/14 04:13, Thomas Mueller wrote: >>> Yes, please apply by hand. I'll see if I can do some testing myself. >>> I happen to have one of these adapters too and the link is very >>> unstable :-) >> --HPS Hi, Please test the following patch, applied to top of 10-stable as of now: http://svnweb.freebsd.org/changeset/base/267041 At least my adapter is working a bit more stable now :-) --HPS From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 13:48:59 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 825A9C72 for ; Wed, 4 Jun 2014 13:48:59 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68DB624AF for ; Wed, 4 Jun 2014 13:48:59 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s54DmxqW067654 for ; Wed, 4 Jun 2014 14:48:59 +0100 (BST) (envelope-from bz-noreply@freebsd.org) From: bz-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 175183] [iwn] iwn(4) becomes unresponsive during initial configuration Date: Wed, 04 Jun 2014 13:48:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 13:48:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=175183 Sean Bruno changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |FIXED --- Comment #2 from Sean Bruno --- This no longer happens on the T520/420 AFAIK. Closing out. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 16:43:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F2FC896 for ; Wed, 4 Jun 2014 16:43:37 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1FFC9263B for ; Wed, 4 Jun 2014 16:43:36 +0000 (UTC) Received: from [192.168.200.104] (c-50-131-4-11.hsd1.ca.comcast.net [50.131.4.11]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id BE8F019294A; Wed, 4 Jun 2014 16:43:35 +0000 (UTC) Subject: Re: TP-Link TL-MR3020 From: Sean Bruno Reply-To: sbruno@freebsd.org To: Jonas Liepuonius In-Reply-To: <627DCC50-A228-4C03-B604-0587C4933A11@gmail.com> References: <627DCC50-A228-4C03-B604-0587C4933A11@gmail.com> Content-Type: text/plain; charset="iso-8859-13" Date: Wed, 04 Jun 2014 09:43:34 -0700 Message-ID: <1401900214.1123.21.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 16:43:37 -0000 On Fri, 2014-05-30 at 00:47 +0300, Jonas Liepuonius wrote: > Iÿm off to sleep, itÿs a little late here, so I will see your email tomorrow, till then. > > -J > > On 30 May 2014, at 00:45, Sean Bruno wrote: Ok, so in order to mess around here, I've posted my first version of the kernconf and kern hints files: http://people.freebsd.org/~sbruno/TP-MR3020 http://people.freebsd.org/~sbruno/TP-MR3020.hints The hints file is most definitely wrong, but I only work on this stuff periodically. In order to boot the box, I suggest setting up TFTPBOOT in this enviroonment first. Then building the netboot image for the TP link requires the freebsd-wifi options be run in a different order (build the ramdisk, then the kernel, then the firmware image). sean From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 4 21:39:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88A78FA0 for ; Wed, 4 Jun 2014 21:39:53 +0000 (UTC) Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50C4227A5 for ; Wed, 4 Jun 2014 21:39:53 +0000 (UTC) Received: by mail-yk0-f169.google.com with SMTP id 200so105265ykr.0 for ; Wed, 04 Jun 2014 14:39:52 -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=I/ZNsF2/2uhs7uwdK6Nksv1L2JyionOCDrZWhmo/I7c=; b=MjN4pABZSkNf7A+fJZTKR8zcIB3NRzC+D4SrVVepI4Cu0KUCiaucnFT8pv2yQ1obGQ BZm5+ErR7AWk8F+dDiATLb6jEje5OPUIjo+8zwZOnGgYiopUiD0TpmJ8OQHf+HTW1Kk3 uWs9cMWHwnYuYc0uhKDrluDw/XkNtkPSzzMJ7KAt4VTZtlpVWlC7rOQ5YDhvOMcmAZ+3 WgOfBbRFPRkb88Vlm1GosADqcRCzE5e6s5CqZmG/MPVw9A1T3Jx69cT8HRHg9Gpm/vvf xbt4C39HQpneLA6B3ckFgH6Iaimz+6cfNuDagoT5H+7LNQiPLu0zi6GxYRKUl4Yygq8j WwVw== MIME-Version: 1.0 X-Received: by 10.236.7.51 with SMTP id 39mr2153377yho.1.1401917992485; Wed, 04 Jun 2014 14:39:52 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Wed, 4 Jun 2014 14:39:52 -0700 (PDT) Date: Wed, 4 Jun 2014 23:39:52 +0200 Message-ID: Subject: Change for the worse in rsu wireless driver From: Idwer Vollering To: "mailto:freebsd-wireless@freebsd.org?Subject=Re: Change for the worse in rsu wireless driver&In-Reply-To=" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 21:39:53 -0000 > On 06/04/14 08:53, Hans Petter Selasky wrote: > > On 06/04/14 04:13, Thomas Mueller wrote: > >>> Yes, please apply by hand. I'll see if I can do some testing myself. > >>> I happen to have one of these adapters too and the link is very > >>> unstable :-) > >> --HPS > > Hi, > > Please test the following patch, applied to top of 10-stable as of now: > > http://svnweb.freebsd.org/changeset/base/267041 I'm on 10-STABLE r267049, with a local change to sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3. > > At least my adapter is working a bit more stable now :-) Mine seems to get stuck in "rsu_calib_task: running calibration task" often. > > --HPS HTH, Idwer From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 5 05:52:36 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 231E5E8A for ; Thu, 5 Jun 2014 05:52:36 +0000 (UTC) Received: from nm9-vm10.access.bullet.mail.bf1.yahoo.com (nm9-vm10.access.bullet.mail.bf1.yahoo.com [216.109.114.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA16120C5 for ; Thu, 5 Jun 2014 05:52:35 +0000 (UTC) Received: from [66.196.81.164] by nm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 05 Jun 2014 05:46:01 -0000 Received: from [98.139.221.156] by tm10.access.bullet.mail.bf1.yahoo.com with NNFMP; 05 Jun 2014 05:46:01 -0000 Received: from [127.0.0.1] by smtp116.sbc.mail.bf1.yahoo.com with NNFMP; 05 Jun 2014 05:46:01 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1401947161; bh=BBJS6UW7038tisO+51c7brzCWCksGMT32M02GVTDsW4=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject; b=HJ3hgyQZuxSMyfqemd8ElQLh29fiZRdfN0q6/972vYjxwBb3RHxXw0UgpoJ/KJU/ozfpGTWdFckhEtERVdJ8JjSkBCQhBF+usLAs60pb0N7RwvwggnAlWaJyjtLsPP+9amhHTC3Db0CMLk7kqsVTC1NxtiqQTsd2jU2YlDgSKRk= X-Yahoo-Newman-Id: 14007.73013.bm@smtp116.sbc.mail.bf1.yahoo.com Message-ID: <14007.73013.bm@smtp116.sbc.mail.bf1.yahoo.com> Date: Thu, 5 Jun 2014 05:46:01 +0000 (UTC) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: O6tl7GsVM1nxr1oojseNSAGVQaYouBL6U2ErJSRB7Qz0oOU 0dhMBJV7Z8Mz6KXZnqfbeZ3eTpibGY_g2u4thIIefKYy9PmKMbkqIIr0CJk8 hiQ7gWh6_LT9SxzbM0nizWOJAmmNOJjtvNtHlk2P3T8RtnPLflZzffUAnQMZ UqArXSechqGZ9HlswfV.UXFjPZU14qc04Ul43Cy8XWEy6Va0B8fdxvokHKTZ D3XlSlL5o72abO60BtiA11cdultzSKhKAGxGvWSxBbMn84qbwDSocrPMoVAE 68E602L.Tu_2zEB_4FuUcJ.DXQf3UJmp_CdZVZ1RbEJJ8.OCDtDgjvHu14DF auZPPoP0yKF2ZC4pPjcHOrDm3gSFkyA3d9Q9N2RIxRwhLk9X.7TXedNl8sP_ qHPGyOsJaPgW1V4qIR5wR6orjp6WhnDAtZBiWVQxIh0ayND.AI3.fRQtNEPT z2vRERAmvlp8duTzRj8VijmDm1.w1FYIxKlpN1nhDh7tV0WOxGznJNCDrl5W z.VstO2xSNbWBS.6pR10g.SALcOR5DWO1dn51fpWZQ3yMcsSm6GVN9Rm3Le4 vPdpeA73i22mJUSSxynGeJyBQ7miftchNAf80VbfOlan_cjgg9eT5zQ-- X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.139.221.42]) by smtp116.sbc.mail.bf1.yahoo.com with SMTP; 05 Jun 2014 05:46:00 +0000 UTC From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Change for the worse in rsu wireless driver Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 05:52:36 -0000 from Idwer Vollering : > I'm on 10-STABLE r267049, with a local change to > sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3. > > At least my adapter is working a bit more stable now :-) > Mine seems to get stuck in "rsu_calib_task: running calibration task" often. > HTH, > Idwer I browsed svnweb.freebsd.org for rsu and re in stable/10 and head, also for cups in ports. I found an update, 4 hours old, for rsu in head, so that pushed me to update the head src tree. That was after a time when the wireless adapter didn't connect at all, didn't see the network. FreeBSD is flaky at times with USB, not recognizing a good USB stick in a good USB port. After some time web-browsing with Midori 0.5.5 on System Rescue CD, which itself is fickle and flaky, not as good as Midori 0.5.8 from FreeBSD ports, Hiro H50191 USB wireless adapter came back and is still working, though I still intend to do the system build/update for 11-head, both amd64 and i386. Tom From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 5 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43B468DF for ; Thu, 5 Jun 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 27A0B2B72 for ; Thu, 5 Jun 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5580MkZ041509 for ; Thu, 5 Jun 2014 09:00:22 +0100 (BST) (envelope-from bz-noreply@freebsd.org) Message-Id: <201406050800.s5580MkZ041509@kenobi.freebsd.org> From: bz-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Thu, 05 Jun 2014 08:00:22 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is an experimental feature. Please file a bug or mail bugmeister@ with concerns. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 5 11:05:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D47D3CF8 for ; Thu, 5 Jun 2014 11:05:24 +0000 (UTC) Received: from mail-yh0-x22a.google.com (mail-yh0-x22a.google.com [IPv6:2607:f8b0:4002:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 991B32BBA for ; Thu, 5 Jun 2014 11:05:24 +0000 (UTC) Received: by mail-yh0-f42.google.com with SMTP id f10so446233yha.1 for ; Thu, 05 Jun 2014 04:05:23 -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=j8jU1UtdU+g8oHBvgadE9ZRCzKH2dupAfJ3iIJojmWk=; b=rVfq3qPuLJmxVsLF1QTBFUGKes1qUBTu+AHzhWOTAmtSx2D90ehEtbKNgVlOv/R6vP 6sA07fsg2TpF0nZz2noO4GsPZmyRXwOaq3wXw6xLO9IrhkKpblkTP1gJO+MP75q9Stb6 DVqahKN4nt6+zq9Gpb1L6+dFfKTzRg2EGRRcO3oVO8t4g/I6I4rs7gX+VS8KkHVUr3se BbazErXEKGrpVg4e/Vqq+b52ISXuTkaGSSr0Mu50O7/9rCFrrL4f+WcA+V2Tsq9mwSPT PMBOj/86GLBVpyev+Yc6TFYL+ZRGRCBxNDbcDa3yQndtbwoXaL9oL+xiSOJr8g5VqbnB eK9g== MIME-Version: 1.0 X-Received: by 10.236.40.81 with SMTP id e57mr83803264yhb.26.1401966323807; Thu, 05 Jun 2014 04:05:23 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Thu, 5 Jun 2014 04:05:23 -0700 (PDT) In-Reply-To: <53900748.20108@bitfrost.no> References: <20140604213334.88E351FE02B@mail.turbocat.net> <53900748.20108@bitfrost.no> Date: Thu, 5 Jun 2014 13:05:23 +0200 Message-ID: Subject: Re: Fwd: Undelivered Mail Returned to Sender From: Idwer Vollering To: "mailto:freebsd-wireless@freebsd.org?Subject=Re: Change for the worse in rsu wireless driver&In-Reply-To=" Content-Type: text/plain; charset=UTF-8 Cc: Hans Petter Selasky X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 11:05:24 -0000 2014-06-05 7:59 GMT+02:00 Hans Petter Selasky : > > Hi, > > Is that a patch I need to add to 10-stable? Hi, Not yet, as I can work with if_rsu code from -CURRENT until things are sorted out. > > >>> >>> At least my adapter is working a bit more stable now :-) >> >> >> Mine seems to get stuck in "rsu_calib_task: running calibration task" >> often > > > Yeah. Looking at the driver code and comparing to Linux, I see a lot of > things missing :-) Another problem about the calibration task, is that it > runs asynchronous to the other code possibly programming the chip. The adapter works fine from OpenBSD, does not (seem to) get confused during calibration. > > Can you turn on: hw.usb.rsu.debug=15 when errors happen? > > Or send what is printed in dmesg? With hw.usb.rsu.debug=6: Yes, the dmesg buffer is full :) $ dmesg rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-102 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=18 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-56 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=9 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-81 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-1 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-25 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-74 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-86 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090418 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090418 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090388 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090388 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090358 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090358 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090328 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090328 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902f8 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-45 rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-64 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-79 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=10 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-13 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-67 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-70 rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-33 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-16 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-14 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=-32 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=-103 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_rx_multi_frame: Rx 3 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=19 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=19 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-87 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-101 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-39 rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-42 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-49 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=5 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-95 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-89 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-1 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-58 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090418 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-59 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090418 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=-101 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903e8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-14 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=125 rate=11 infosz=32 rssi=-3 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-70 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-41 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-77 rsu_calib_task: running calibration task rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090388 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090388 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=10 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090358 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090358 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-89 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090328 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090328 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-59 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-95 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-37 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=19 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_calib_task: running calibration task rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-80 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-49 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-105 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-39 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=17 rsu_calib_task: running calibration task rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-79 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_calib_task: running calibration task rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=394 rate=9 infosz=32 rssi=-25 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=146 rate=9 infosz=32 rssi=-30 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=146 rate=9 infosz=32 rssi=-96 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=146 rate=9 infosz=32 rssi=-11 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=1203 rate=9 infosz=32 rssi=-58 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=409 rate=9 infosz=32 rssi=-94 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=765 rate=9 infosz=32 rssi=-52 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=771 rate=9 infosz=32 rssi=-87 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090418 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090418 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=134 rate=9 infosz=32 rssi=6 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-30 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090388 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090388 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_calib_task: running calibration task rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-85 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090358 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090358 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-59 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090328 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090328 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=15 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-12 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=8 infosz=32 rssi=-42 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=9 infosz=32 rssi=-7 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=9 infosz=32 rssi=-88 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=-101 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=-48 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=8 infosz=32 rssi=-11 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-106 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=8 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 > > --HPS > From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 5 11:09:39 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 025FED3C for ; Thu, 5 Jun 2014 11:09:39 +0000 (UTC) Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE0242BD2 for ; Thu, 5 Jun 2014 11:09:38 +0000 (UTC) Received: by mail-yk0-f179.google.com with SMTP id q200so50572ykb.10 for ; Thu, 05 Jun 2014 04:09:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=NntVDZVu+PWE5uvmagylb4KoMb4nR3c3X14LBHFNhFw=; b=CiInTB0HC4Cn9YWKUS6nJsg4mgLM0OD3XM+IhnFNpIFcjeAClIr908I5topn+dTvL2 FReOop8WPrmjpGF39A/K3iIYyBVpaO1ve3YE2z/8YTAUXjxcE6b1EpU3qlOExsJk9Gv3 i4Yhzp++2oj1S+3fSddA/0L7oKPOTqxqgUr3SaNKhdYUyWVpvy1kILUz2vKbm6dtLXly YHDS5S9sJhYAjCYAbrrTaWO+Utgc8ilw8/gOaJl5Lu/pc1KY9vZCPNYtSztEEBeH8OrO ghDYYwEPln4LWLjZBXgn+4+QZvEoPOAHTFdSF11iQrkcJ/w5deaCFMs1XRKazqrXbutx 4UpQ== MIME-Version: 1.0 X-Received: by 10.236.134.169 with SMTP id s29mr82001108yhi.4.1401966577846; Thu, 05 Jun 2014 04:09:37 -0700 (PDT) Received: by 10.170.89.65 with HTTP; Thu, 5 Jun 2014 04:09:37 -0700 (PDT) Date: Thu, 5 Jun 2014 13:09:37 +0200 Message-ID: Subject: Change for the worse in rsu wireless driver From: Idwer Vollering To: "mailto:freebsd-wireless@freebsd.org?Subject=Re: Change for the worse in rsu wireless driver&In-Reply-To=" Content-Type: text/plain; charset=UTF-8 Cc: Hans Petter Selasky X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 11:09:39 -0000 2014-06-05 7:59 GMT+02:00 Hans Petter Selasky : > > Hi, > > Is that a patch I need to add to 10-stable? Hi, Not yet, as I can work with if_rsu code from -CURRENT until things are sorted out. > Yeah. Looking at the driver code and comparing to Linux, I see a lot of > things missing :-) Another problem about the calibration task, is that it > runs asynchronous to the other code possibly programming the chip. The adapter works fine from OpenBSD, does not (seem to) get confused during calibration. > Can you turn on: hw.usb.rsu.debug=15 when errors happen? > > Or send what is printed in dmesg? With hw.usb.rsu.debug=6: Yes, the dmesg buffer is full :) $ dmesg rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-102 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=18 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-56 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=9 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-81 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-1 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-25 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-74 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-86 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090418 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090418 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090388 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090388 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090358 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090358 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090328 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090328 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902f8 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-45 rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-64 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-79 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=10 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-13 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-67 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-70 rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-33 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-16 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-14 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=-32 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=-103 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_rx_multi_frame: Rx 3 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=19 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=19 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-87 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-101 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-39 rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-42 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-49 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=5 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-95 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-89 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_rx_multi_frame: Rx 2 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-1 rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-58 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090418 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-59 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090418 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=100 rate=11 infosz=32 rssi=-101 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903e8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-14 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=125 rate=11 infosz=32 rssi=-3 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-70 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=108 rate=11 infosz=32 rssi=-41 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-77 rsu_calib_task: running calibration task rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090388 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090388 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=10 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090358 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090358 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-89 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090328 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090328 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-59 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-95 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-37 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=19 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_calib_task: running calibration task rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-80 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-49 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-105 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-39 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=17 rsu_calib_task: running calibration task rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-79 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_calib_task: running calibration task rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=394 rate=9 infosz=32 rssi=-25 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=146 rate=9 infosz=32 rssi=-30 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=146 rate=9 infosz=32 rssi=-96 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=146 rate=9 infosz=32 rssi=-11 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=1203 rate=9 infosz=32 rssi=-58 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=409 rate=9 infosz=32 rssi=-94 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=765 rate=9 infosz=32 rssi=-52 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=771 rate=9 infosz=32 rssi=-87 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090418 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090418 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903e8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060903b8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=134 rate=9 infosz=32 rssi=6 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-30 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090388 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090388 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_calib_task: running calibration task rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-85 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090358 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090358 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-59 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090328 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090328 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060902c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090208 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=15 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-12 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907d8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907d8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=8 infosz=32 rssi=-42 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090748 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090718 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090688 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090658 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090658 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=9 infosz=32 rssi=-7 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=9 infosz=32 rssi=-88 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=-101 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=9 infosz=32 rssi=-48 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=96 rate=8 infosz=32 rssi=-11 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090628 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090568 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090538 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090508 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfffffe00060904a8 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=9 infosz=32 rssi=-106 rsu_bulk_tx_callback_sub: submitting transfer 0xfffffe0006090478 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=8 infosz=32 rssi=15 rsu_bulk_tx_callback_sub: transfer done 0xfffffe0006090478 rsu_bulk_tx_callback_sub: empty pending queue sc 0xfffffe000608e000 > > --HPS > From owner-freebsd-wireless@FreeBSD.ORG Fri Jun 6 01:56:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE5E7B5E; Fri, 6 Jun 2014 01:56:32 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7ECCF23AD; Fri, 6 Jun 2014 01:56:32 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id a108so3089071qge.36 for ; Thu, 05 Jun 2014 18:56: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:content-transfer-encoding; bh=yKeE5vmTG29qSpEV0vHYW8OPXLU3BtXvCb8Hnjs2p6I=; b=pWY8De3MwtzPiFOKDo5NZped/XSewMDShelmxQsTkOoImoH1A3x4Z6Ra5Co6La0gJc ZwHSWhPKdsP8L4VEprBk9/bpFU6hv97TIxzFKvUUoS3FuPVCmjXKllUNEiIezPBwKyBU x0mUzrcqZHptLjl+DgDz/P8l/SRjQ4QH+nEam7B7UE2J7qtxa+sMBJGZJwL6wzu9BssH iYnCJ3IgXLr6H3tSFYQ2Ik9Z0CBYH3+fhG7KSuT7/kekzaKDDkltaSl8pXBOuO3PBMkJ eQSMDSvrDqvKPvGPE0AEmDDN04gw3USLH/SO12wY+U96ZJJn8YWp/P8hdLB8XAC6nHfD oegw== MIME-Version: 1.0 X-Received: by 10.224.43.148 with SMTP id w20mr2933806qae.26.1402019791629; Thu, 05 Jun 2014 18:56:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Thu, 5 Jun 2014 18:56:31 -0700 (PDT) In-Reply-To: <14007.73013.bm@smtp116.sbc.mail.bf1.yahoo.com> References: <14007.73013.bm@smtp116.sbc.mail.bf1.yahoo.com> Date: Thu, 5 Jun 2014 21:56:31 -0400 X-Google-Sender-Auth: ET9n86QsBq6ilsw_Uxiw07TDACA Message-ID: Subject: Re: Change for the worse in rsu wireless driver From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" , freebsd-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2014 01:56:32 -0000 hi, please bug freebsd-usb@ about flakey usb devices. I have a couple that i need to chase up hans about. they used to be less fl= akey. -a On 5 June 2014 01:46, Thomas Mueller wrote: > from Idwer Vollering : > >> I'm on 10-STABLE r267049, with a local change to >> sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3. > >> > At least my adapter is working a bit more stable now :-) > >> Mine seems to get stuck in "rsu_calib_task: running calibration task" of= ten. > >> HTH, > >> Idwer > > I browsed svnweb.freebsd.org for rsu and re in stable/10 and head, also f= or cups in ports. > > I found an update, 4 hours old, for rsu in head, so that pushed me to upd= ate the head src tree. > > That was after a time when the wireless adapter didn't connect at all, di= dn't see the network. > > FreeBSD is flaky at times with USB, not recognizing a good USB stick in a= good USB port. > > After some time web-browsing with Midori 0.5.5 on System Rescue CD, which= itself is fickle and flaky, not as good as Midori 0.5.8 from FreeBSD ports= , Hiro H50191 USB wireless adapter came back and is still working, though I= still intend to do the system build/update for 11-head, both amd64 and i38= 6. > > Tom > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-wireless@FreeBSD.ORG Fri Jun 6 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1686E4F1 for ; Fri, 6 Jun 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EEF0221E3 for ; Fri, 6 Jun 2014 08:00:21 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5680LZv092885 for ; Fri, 6 Jun 2014 09:00:21 +0100 (BST) (envelope-from bz-noreply@freebsd.org) Message-Id: <201406060800.s5680LZv092885@kenobi.freebsd.org> From: bz-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Fri, 06 Jun 2014 08:00:21 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is an experimental feature. Please file a bug or mail bugmeister@ with concerns. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 8 01:21:50 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE54F5A1; Sun, 8 Jun 2014 01:21:50 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91D262492; Sun, 8 Jun 2014 01:21:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=C7uybX+nbFwUsxFAT8JMLDn0iuyszyh1I0JF0zH78c8=; b=r2gBVwLvMYH/xTVBJDXWSNmcbUbvFQAV/KN2TBI0V+4j0EJH6ZDQ2RaT4qt97umJK+JnUy1NBnDiieeHuGxH6T71Kl4oYq2OwSg9LtDCoNoYoBh6TgXEMESwqTpqH4lqHAwTQTo7tnPOSjYrjXTc7h4xt9mSbXA1IqRwy7+KPmk=; Received: from [39.193.232.236] (port=13814 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WtRnw-001NLz-Sl; Sat, 07 Jun 2014 19:21:49 -0600 Date: Sun, 8 Jun 2014 09:21:42 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140608092142.746a09db@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> <20140523235953.7f8dbb4d@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2014 01:21:50 -0000 Hi Adrian, On Fri, 23 May 2014 09:01:36 -0700 Adrian Chadd wrote: > a photo will be fine. :-) > did the photos help? I did not have any problems anymore since I deactivated IPV6. Erich > > -a > > > On 23 May 2014 08:59, Erich Dollansky > wrote: > > Hi, > > > > On Fri, 23 May 2014 08:36:31 -0700 > > Adrian Chadd wrote: > > > >> Ok, it's a null pointer dereference (based on the address you > >> posted) and it's ipv6 related. That's .. odd. > >> > >> Can you provide a backtrace from the crash? > >> > > I can try tomorrow. Am I right that I can only take photos of the > > screen at this point of the boot process? > > > > Erich > >> > >> > >> -a > >> > >> > >> On 23 May 2014 04:13, Erich Dollansky > >> wrote: > >> > Hi, > >> > > >> > On Tue, 8 Apr 2014 20:40:01 -0700 > >> > Adrian Chadd wrote: > >> > > >> >> I'm not sure. I'd really like to see what the story is with > >> >> coexistence somehow. > >> >> > >> > I did some more investigations and came to the result that iwn > >> > crashes in 'in6_ifattach_linklocal'. > >> > > >> > When I disable ipv6, it all works fine. I did several reboots > >> > without a problem. > >> > > >> > To make this a bit more complicated, if I use only em0, the > >> > machine starts normal. When I use iwn0 alone or together with > >> > lagg0 and em0, the machine crashes during the boot process. The > >> > crashes only happen when IPV6 is enabled in rc.conf. > >> > > >> > Erich > > From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 8 01:41:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72F5B7DA; Sun, 8 Jun 2014 01:41:12 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D5EB2573; Sun, 8 Jun 2014 01:41:12 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id q107so7401895qgd.10 for ; Sat, 07 Jun 2014 18:41:10 -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=FzBN7NUSV3nGTXoV3ihnoOizxYYwGYCzeBTYZQz9ROU=; b=Lz8JyEy/4t7Ttv+UG0yl1o4WG/B91akKACDvZhwBal+Xx+NxvFiGzVJpM1nmUyXp3o Pj4QxhyfR0DcfGNwzKZ1XHJROJWTulYkGwOz9x0LMOVW63Ynsj5m2S+kMKWIcAw6N4Db l0cdOI8PQiR0IfQhCXh0bEhpQ3iwqYigEk7cgufDm8DfTAumNT4PB7Y3+mQGs2jWG4YD MlAYFn2I3OdDFYZLBh/eqtQBUiviDkQTgw81xEDDiNhWALQo0pG7eQSXhN6E12/XK9uS hzQCmv86PmPgcnP/F2fn0D3wmShG/lCjU4NVXtFE51D+JAct9q9v1uEdp9xZAyo/W2Ok qWmQ== MIME-Version: 1.0 X-Received: by 10.224.160.202 with SMTP id o10mr22200706qax.8.1402191670732; Sat, 07 Jun 2014 18:41:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Sat, 7 Jun 2014 18:41:10 -0700 (PDT) In-Reply-To: <20140608092142.746a09db@X220.alogt.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> <20140523235953.7f8dbb4d@X220.alogt.com> <20140608092142.746a09db@X220.alogt.com> Date: Sat, 7 Jun 2014 21:41:10 -0400 X-Google-Sender-Auth: XV-6WR-GSQtIQOwSCvkprwWNsDc Message-ID: Subject: Re: iwn0 hangs randomly when starting the machine From: Adrian Chadd To: Erich Dollansky Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2014 01:41:12 -0000 Hi, Can you pleease chase this up with me next week? We need to find/fix these issues. I'm not running v6 at home; I can easily flip that on when I get home next week. THanks, -a On 7 June 2014 21:21, Erich Dollansky wrote: > Hi Adrian, > > On Fri, 23 May 2014 09:01:36 -0700 > Adrian Chadd wrote: > >> a photo will be fine. :-) >> > did the photos help? > > I did not have any problems anymore since I deactivated IPV6. > > Erich >> >> -a >> >> >> On 23 May 2014 08:59, Erich Dollansky >> wrote: >> > Hi, >> > >> > On Fri, 23 May 2014 08:36:31 -0700 >> > Adrian Chadd wrote: >> > >> >> Ok, it's a null pointer dereference (based on the address you >> >> posted) and it's ipv6 related. That's .. odd. >> >> >> >> Can you provide a backtrace from the crash? >> >> >> > I can try tomorrow. Am I right that I can only take photos of the >> > screen at this point of the boot process? >> > >> > Erich >> >> >> >> >> >> -a >> >> >> >> >> >> On 23 May 2014 04:13, Erich Dollansky >> >> wrote: >> >> > Hi, >> >> > >> >> > On Tue, 8 Apr 2014 20:40:01 -0700 >> >> > Adrian Chadd wrote: >> >> > >> >> >> I'm not sure. I'd really like to see what the story is with >> >> >> coexistence somehow. >> >> >> >> >> > I did some more investigations and came to the result that iwn >> >> > crashes in 'in6_ifattach_linklocal'. >> >> > >> >> > When I disable ipv6, it all works fine. I did several reboots >> >> > without a problem. >> >> > >> >> > To make this a bit more complicated, if I use only em0, the >> >> > machine starts normal. When I use iwn0 alone or together with >> >> > lagg0 and em0, the machine crashes during the boot process. The >> >> > crashes only happen when IPV6 is enabled in rc.conf. >> >> > >> >> > Erich >> > > From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 8 03:54:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59CA8D4C; Sun, 8 Jun 2014 03:54:41 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 21C852EEE; Sun, 8 Jun 2014 03:54:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=eSFnB3TivDqovhEPVz7EZIGnaRe/iavK5mRaWGtOpD8=; b=EKebjRPbj8x2oPplTB27AVX7Niab8UD52o78Y7ke1UDY+XZjiposKiE+1dOsx5b7yA3wIzfS4cmS23qEFy9lRuaWcgSTQ69UEAJbP60iVeBwt2Q/Z0RBCIrMudqPPCbPngBANLIn6rvdiTrSrGQWjEf6SAod/A1rf2LCxTy+nUA=; Received: from [39.193.232.236] (port=18814 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WtUBq-0037e3-Sl; Sat, 07 Jun 2014 21:54:39 -0600 Date: Sun, 8 Jun 2014 11:54:33 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140608115433.69b66023@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> <20140523235953.7f8dbb4d@X220.alogt.com> <20140608092142.746a09db@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2014 03:54:41 -0000 Hi Adrian, On Sat, 7 Jun 2014 21:41:10 -0400 Adrian Chadd wrote: > Can you pleease chase this up with me next week? We need to find/fix should be possible. > these issues. I'm not running v6 at home; I can easily flip that on > when I get home next week. You only need to turn it on and the machine crashes very often while booting. I was also irritated as it originally crashed only when connecting to TPLink access points. I have meanwhile the feeling that it crashes even more often on other access points. Erich From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 9 07:50:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F42102B5 for ; Mon, 9 Jun 2014 07:50:26 +0000 (UTC) Received: from nm20-vm7.access.bullet.mail.bf1.yahoo.com (nm20-vm7.access.bullet.mail.bf1.yahoo.com [216.109.115.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 84FA3274B for ; Mon, 9 Jun 2014 07:50:25 +0000 (UTC) Received: from [66.196.81.156] by nm20.access.bullet.mail.bf1.yahoo.com with NNFMP; 09 Jun 2014 07:43:29 -0000 Received: from [98.138.226.241] by tm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 09 Jun 2014 07:43:29 -0000 Received: from [127.0.0.1] by smtp112.sbc.mail.ne1.yahoo.com with NNFMP; 09 Jun 2014 07:43:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1402299809; bh=HkMrrkHpDsd+IKMkMAeZAn5S3gn+h8prNJoYeoARAj4=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject; b=sGa8lh/O0oNuPttPgRdSelC1jAdAkvXz842rOUK6O3umgaDq2gwg7ZCeAknQ5PqgJgzNFbrJF/swosZxsUqMzHOr35+RAp3HePV7Zr0bH8MtXF7Cv99k/ZaMdnyLbuh+A7cTQC2dCB85dK3S0I0BT/U/3WyXi+PKmDit1dhoOFk= X-Yahoo-Newman-Id: 394751.84774.bm@smtp112.sbc.mail.ne1.yahoo.com Message-ID: <394751.84774.bm@smtp112.sbc.mail.ne1.yahoo.com> Date: Mon, 9 Jun 2014 00:43:29 -0700 (PDT) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: EwWc75QVM1n3faYH7aRgPt_6558TEMl5i.PKXUgVHSfXssc plDQU4SB.jlPSq3PZ4O24xveCh01iUdL84QOMg1jWIoskMkjiE4IToTDk9iQ mhYCBvrcjQik6FrJ8QkgcRkyhIjNpM3xH5Y6LvyXLuk1UOIVF.avehYB4h5e MLqkXM.WCTqgQWIG30sRh.wHTWX.NOscYPWEPDR.bwduQ_V17uFupAr.Eu3D .qs20aOoMKkRLbB7mAt4kSbl0.zoZuLbum4J4wt5yu4zT5Ad6MoSIEDmsxLi .CiVD3B3a_y287ly6g7W9KTyMxc8_lBYyP6DWiWJkwKJNHZJGBpXTNnH2NVr 1qBNTINsHKbGehOHr1rPyXHgWWYAhVlSuXZ38YRvzqV_yGlLpZDVFJpcRX7H luKvLbScmtKuooy5A51T3u9FvxRACK5T.kQjYj_2ngHjn8OlKXpvRINPLTma TypfmmaaeOjqnSTKcoAa3eUDRycmSm.LnCMm2RCRQEnC1_gLJXkCYE8Y7HUv 5qIlXbeLxv2pxAtujnb.5fsqw8_9GFMzrKfOV0AtzJ2utNey6BJeLM6S_ X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.138.31.74]) by smtp112.sbc.mail.ne1.yahoo.com with SMTP; 09 Jun 2014 00:43:29 -0700 PDT From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 07:50:27 -0000 from Adrian Chadd: > please bug freebsd-usb@ about flakey usb devices. > I have a couple that i need to chase up hans about. they used to be less flakey. Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless adapters. I get console messages about keyboard and mouse losing connection, when in many cases, mouse and keyboard are still working. Now I think FreeBSD is topping NetBSD for flaky USB connections. NetBSD has no support for Hiro H50191 wireless adapter, device rsu, but supports Atheros on-motherboard (quasi-)USB AR9271. Most of the time, NetBSD fails to load firmware for this Atheros AR9271, error 35, not allowing enough time, but sometimes the firmware loads. Sorry to be late in responding, losing connection slows me down. I've been updating FreeBSD-current and stable/10 from source, both amd64 and i386, whenever I see a change in rsu or re driver. On MSI Z77 MPOWER motherboard, of open-source OSes, only Linux and NetBSD connect with Realtek 8111E/8168 Ethernet. DragonFly newest release, 3.8.0, and OpenBSD 5.4, have same bug as does FreeBSD with this Ethernet. I've also been busy installing NetBSD-current amd64 and i386, now on hard drive on other computer. Now I wish I had installed NetBSD-current amd64 and i386 on this computer with MSI Z77 MPOWER motherboard before FreeBSD to have something to fall back on when FreeBSD misbehaves with Hiro H50191. Remember, I needed to update NetBSD-current amd64 and packages, with subversion, using wired Ethernet, to checkout and update FreeBSD src, ports and doc trees; also had to buy a new wireless router when the Netgear router stopped working. Tom From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 9 14:21:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A234A13C; Mon, 9 Jun 2014 14:21:43 +0000 (UTC) Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51E6C2989; Mon, 9 Jun 2014 14:21:43 +0000 (UTC) Received: by mail-qa0-f46.google.com with SMTP id i13so1385141qae.5 for ; Mon, 09 Jun 2014 07:21:42 -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=GTELi4EhlSZ2zoN32SscZS94QqxGZNgTUhRNm/G+BZM=; b=rAn2dXR21pnaY4Eh+Vt97yscp2zg3pvVH9QXwnqZDEtyXjYuSkwu55UqkJ3P13K70e jP1gxf/fxryV2Cak08rZNcMgGGCvcSFCIsAT20Jkkvzs40I7W+zRx/SocPj6LBFstN45 zHu7fMUZrguQBIywtdKPqpkr/KRNxX3jkvNarGGbMAfJ5ZBci9XgmIUEi/K2W9E8bg0d WL4JSqEjq/FGXIaOAyP4cgIC2yZZMdjPsQBKZ2nubARyImXNkjpbD59+2BkO5yywW/5B UTHpBs4I/Wv4fts5n12PFetGvTmUVQ5Foao1MC/dPoZgY+DaAJbnG+t5RyTvixkL3X/B 4fuA== MIME-Version: 1.0 X-Received: by 10.140.91.5 with SMTP id y5mr31383972qgd.12.1402323702383; Mon, 09 Jun 2014 07:21:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Mon, 9 Jun 2014 07:21:42 -0700 (PDT) In-Reply-To: <394751.84774.bm@smtp112.sbc.mail.ne1.yahoo.com> References: <394751.84774.bm@smtp112.sbc.mail.ne1.yahoo.com> Date: Mon, 9 Jun 2014 10:21:42 -0400 X-Google-Sender-Auth: OTO8P03-PS2lM0Xi0v8TtMsIQV8 Message-ID: Subject: Re: Change for the worse in rsu wireless driver From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , freebsd-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 14:21:43 -0000 Hi, Buy a mini-pcie atheros wifi card. -a On 9 June 2014 03:43, Thomas Mueller wrote: > from Adrian Chadd: > >> please bug freebsd-usb@ about flakey usb devices. > >> I have a couple that i need to chase up hans about. they used to be less flakey. > > Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless adapters. > > I get console messages about keyboard and mouse losing connection, when in many cases, mouse and keyboard are still working. > > Now I think FreeBSD is topping NetBSD for flaky USB connections. > > NetBSD has no support for Hiro H50191 wireless adapter, device rsu, but supports Atheros on-motherboard (quasi-)USB AR9271. > > Most of the time, NetBSD fails to load firmware for this Atheros AR9271, error 35, not allowing enough time, but sometimes the firmware loads. > > Sorry to be late in responding, losing connection slows me down. > > I've been updating FreeBSD-current and stable/10 from source, both amd64 and i386, whenever I see a change in rsu or re driver. > > On MSI Z77 MPOWER motherboard, of open-source OSes, only Linux and NetBSD connect with Realtek 8111E/8168 Ethernet. > > DragonFly newest release, 3.8.0, and OpenBSD 5.4, have same bug as does FreeBSD with this Ethernet. > > I've also been busy installing NetBSD-current amd64 and i386, now on hard drive on other computer. > > Now I wish I had installed NetBSD-current amd64 and i386 on this computer with MSI Z77 MPOWER motherboard before FreeBSD to have something to fall back on when FreeBSD misbehaves with Hiro H50191. > > Remember, I needed to update NetBSD-current amd64 and packages, with subversion, using wired Ethernet, to checkout and update FreeBSD src, ports and doc trees; also had to buy a new wireless router when the Netgear router stopped working. > > Tom > > _______________________________________________ > 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 Wed Jun 11 03:41:39 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1018EBA9 for ; Wed, 11 Jun 2014 03:41:39 +0000 (UTC) Received: from nm9-vm3.access.bullet.mail.bf1.yahoo.com (nm9-vm3.access.bullet.mail.bf1.yahoo.com [216.109.114.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B51112209 for ; Wed, 11 Jun 2014 03:41:37 +0000 (UTC) Received: from [66.196.81.157] by nm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 11 Jun 2014 03:34:30 -0000 Received: from [98.138.226.240] by tm3.access.bullet.mail.bf1.yahoo.com with NNFMP; 11 Jun 2014 03:34:30 -0000 Received: from [127.0.0.1] by smtp111.sbc.mail.ne1.yahoo.com with NNFMP; 11 Jun 2014 03:34:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1402457670; bh=5YMpAUaNU3IKm05yzKB+kyR8HFtadyNAqRAh5hclrL0=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject:References; b=k8FvzPvv+q3wGUvg5ZRVIOjmoC7bEkA/ddWugVOAT5qTxGWORJh3IQ6uGzEMKWILbqVoo2ayM0z21vQ86NWxeTkpzjEffxJjZX9zbteV0f17UyAo3/ZFFpoSmG4o+fpR0vc5HP11WR/6LpHQnMpYayN0+1OSpiknr1J/htuUgSw= X-Yahoo-Newman-Id: 84065.87016.bm@smtp111.sbc.mail.ne1.yahoo.com Message-ID: <84065.87016.bm@smtp111.sbc.mail.ne1.yahoo.com> Date: Tue, 10 Jun 2014 20:34:30 -0700 (PDT) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Ja_EN6MVM1kMqGw0xMdYchlJylrh51HaX7Cv2DI72fykWLc GlSRsb0gfAPsndnlXts9ujyFAWsu5E5vc3tSMomhYEsT5NY_NFRNy5gbgu63 cjFhkSly368YBpJS4_eVNKXhKhw04C6ZQ5XTLB2rWaAjuhbzYhYTBk1nRC1l C_g.VB7AaWhgf5k4Lnk84uApRWB2V6IAzhoIUfVp7mUD8DeorSAbM8jbDT55 StCmVDG9ahPro2O3BR8JPg2TWtqkfcMqp1My8dkNrvPln7hc6LVslWWSGSzW TL7S0vvmZej_M9dCLOMrfSrwPBLENCLweYqsplUKDHfGdDbdJaxbeukM0Tdo jgZLEL0iXiGHGiNZQokJGvP98SjvUyB5YMfHdxNcQ6LMop12mhc4Mm6kfMeq XDBAzs5zlSdC2VFK_gwaQe2m6uQ3crbH0tkUe0uExhXQPTyRYM1XTyhV7bwD SGCVrGpgW6rJLTxfuJ_kDlae1KYolrwSrSaKCx12XYwqIetY4RUsGgPw4nvr pOsnYZNY8ROSyXR7d1JD6qfVw3l1VI_zedzrtAxqr6bI8NcXqwNKeFvjE X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.138.31.74]) by smtp111.sbc.mail.ne1.yahoo.com with SMTP; 10 Jun 2014 20:34:30 -0700 PDT From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: Re: Change for the worse in rsu wireless driver References: <5E.43.11813.830AD835@dnvrco-oedge02> <538E12ED.3050101@selasky.org> Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 03:41:39 -0000 from Adrian Chadd: > Buy a mini-pcie atheros wifi card. How do I know this would work with FreeBSD and/or NetBSD? I could switch the hard drives between the two computers, or put one hard drive in a Sabrent enclosure: IDE and SATA inside, USB 2.0 and eSATA outside interface. I could also buy a USB-to-Ethernet adapter, don't know how these things work under FreeBSD. But I would still have to plug into the 25 ft Ethernet cable that goes across the floor and creates a tripping hazard, though I haven't tripped over it yet in over two years. I already have one wired and two wireless ways of connecting to the Internet, think they might all work with Linux but really need to test them. Again I seem to have lost the Internet connection, despite "ifconfig" showing lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 rsu0: flags=8843 metric 0 mtu 2290 options=1 ether 00:13:33:a2:86:f0 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:13:33:a2:86:f0 inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid Maclura_pomifera channel 8 (2447 MHz 11g) bssid a0:f3:c1:f9:39:7a country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 0 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS roaming MANUAL uname -a shows FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #8 r267220M: Sun Jun 8 17:16:53 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 Tom From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 11 08:24:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3070D721 for ; Wed, 11 Jun 2014 08:24:05 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3889289D for ; Wed, 11 Jun 2014 08:24:04 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id k14so7548836wgh.6 for ; Wed, 11 Jun 2014 01:24:02 -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=QAdoDmlQQSawznj4Oo6F5otZawadV98jjprxCt4zKk0=; b=NJhwvOrp1D5BTaQVfuurHgGJv4y1QCSjnmmC09SY+oQEc9vxlku/jIvjT/rVwYGVDW N80oBYyDM5GGZLdjZo3haB23uw5T7Jf0wxVk4XhJX1sWEseyh6mR2YHfpvQE6ulOppJS 2KM5t++J+WOgcsWokFiRcA5M40u6SmSY3q5LUNNtpH1NadA9UitBYE06dz7gHg6+NRtJ 23VPtPxzQYgpJIXSuvJlOnU+1tOuj0ofS13KKYCYSE3eGiiybWM3c42LsJ9yMAQwbqk7 4otLDBbZg042AgRv8W0gPGzDKp38snBVP74aDM4bFIJQatrUwokpH1i9gnuNZOksGXtL DqzA== MIME-Version: 1.0 X-Received: by 10.194.11.74 with SMTP id o10mr21953552wjb.82.1402475042309; Wed, 11 Jun 2014 01:24:02 -0700 (PDT) Received: by 10.180.93.170 with HTTP; Wed, 11 Jun 2014 01:24:02 -0700 (PDT) Date: Wed, 11 Jun 2014 18:24:02 +1000 Message-ID: Subject: Best mini-PCIe Card for AP From: Hanson Wong To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 08:24:05 -0000 Hi all, I've been sifting through posts from the list, but some of the advice is a couple of years old, and as we all know, so much changes so quickly nowadays... I'm looking to get FreeBSD up and running as a wireless AP, here are some things that would be nice: - mini-PCIe. - Simultaneous dual-band. - Multiple SSIDs to separate guest/"real" network. I'm assuming ath9x is still the best bet at the moment? Which particular models work the best in FreeBSD? Cheers, Hanson From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 14 23:12:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0838A233 for ; Sat, 14 Jun 2014 23:12:13 +0000 (UTC) Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B747E2802 for ; Sat, 14 Jun 2014 23:12:12 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id ij19so3702500vcb.9 for ; Sat, 14 Jun 2014 16:12:11 -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=6uz3c+Ei3YkAO9Uu+GMG+v1G0eRvD2b0tKGaQXq7j54=; b=Ub1iBgbwXozfF1Zi47oj8FPYpVFYiG05aUTMF3tGVH4p/Ou+3Y1TqeURNAOEIHW0Nb F15SgkvxQGHIdWNZ2zHA/MeOAEd3bHIfBX+O0QMK4mG2uMkzfv6yIQAiLTAGTiX68Jq/ 19Q9okIA8g+Gf35oifxhcAWYvIfziYB9BpcVsJsf9a09/EiOooXcg4y0is9vRUH0PAf7 IpGijp2zmj1ag70O+OCnyqGlVARcxpMT7jUyMOHHlyMKGwZ3ZO265W9C8/Aw/ar0tQgq oqP3suLxkilrmYK5/86Dd6Wzi9tnwtsaboqail7omX+3QYm+UEQyNQvI6rpBsh4DFa/O X/cw== MIME-Version: 1.0 X-Received: by 10.220.159.4 with SMTP id h4mr8596413vcx.1.1402787531708; Sat, 14 Jun 2014 16:12:11 -0700 (PDT) Received: by 10.220.13.10 with HTTP; Sat, 14 Jun 2014 16:12:11 -0700 (PDT) Date: Sat, 14 Jun 2014 16:12:11 -0700 Message-ID: Subject: in-depth wireless troubleshooting From: Peter Kryszkiewicz To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2014 23:12:13 -0000 I've installed this device (dmesg output) rum0: on usbus1 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 and had it running fine on a new install, until I started populating the ports tree. Somewhere along the way the interface stopped working. I've done everything I know to diagnose the problem but need some more surgical tools and advice now. Here's what I've got: *>uname -a*: FreeBSD dfwr.worldwins.net 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 *>ifconfig -a* nfe0: flags=8843 metric 0 mtu 1500 options=82008 ether 00:1e:8c:36:15:37 inet6 fe80::21e:8cff:fe36:1537%nfe0 prefixlen 64 scopeid 0x1 inet 192.168.0.111 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=23 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 rum0: flags=8843 metric 0 mtu 2290 ether 00:16:44:89:46:1a nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:16:44:89:46:1a inet6 fe80::216:44ff:fe89:461a%wlan0 prefixlen 64 scopeid 0x4 inet 192.168.1.73 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=23 media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g *> less /boot/loader.conf* if_nfe_load="YES" if_rum_load="YES" wlan_scan_ap_load="YES" wlan_scan_stn_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" kern.maxfiles=25000 *> less /var/db/dhclient.leases.wlan0* lease { interface "wlan0"; fixed-address 192.168.1.73; option subnet-mask 255.255.255.0; option routers 192.168.1.254; option domain-name-servers 192.168.1.254; option domain-name "Home"; option dhcp-lease-time 86400; option dhcp-message-type 5; option dhcp-server-identifier 192.168.1.254; renew 0 2014/6/15 09:38:30; rebind 0 2014/6/15 18:38:30; expire 0 2014/6/15 21:38:30; *> less /var/db/dhclient.leases.nfe0* lease { interface "nfe0"; fixed-address 192.168.0.111; option subnet-mask 255.255.255.0; option routers 192.168.0.1; option domain-name-servers 192.168.0.1; option dhcp-lease-time 86400; option dhcp-message-type 5; option dhcp-server-identifier 192.168.0.1; option dhcp-renewal-time 43200; option dhcp-rebinding-time 75600; renew 0 2014/6/15 09:33:27; rebind 0 2014/6/15 18:33:27; expire 0 2014/6/15 21:33:27; *> less /etc/resolv.conf* nameserver 192.168.0.1 *>less /etc/hosts* ::1 localhost localhost.worldwins.net dfwr 127.0.0.1 localhost localhost.worldwins.net dfwr # 192.168.1.111 dfwr.worldwins.net dfwr I've got another machine, a 386 laptop running 10.0, and it uses the same AP. The only difference is that the fixed adress of the internal NIC is 192.168.0.110 and its resolv.conf gives me: *(resolv.conf on laptop)* search Home nameserver 192.168.1.254 When I set the non-working machine's resolv.conf to the same, dhclient resets it immediately to the original contents. I've tried the script fix to disable dhclient from changing resolv.conf, but all that did was kill the network even 'deader' (before that, it looked as though requests were getting out - eg *ping http://someadress.com * would try for a few seconds before finally giving up with 'host name lookup failure'. Where can I go from here? BTW: how can I submit all the source snippets in a cleaner way? I've seen messages where the source was in a scrolling window. Haven't had time to find out how to do that. I have to head for the bush in a few hours, and am hoping to set up my box to install those huge ports before I go. Thanks for your consideration. From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 15 06:17:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 386126BD for ; Sun, 15 Jun 2014 06:17:27 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1DADE25D2 for ; Sun, 15 Jun 2014 06:17:26 +0000 (UTC) Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 48D404FC37 for ; Sat, 14 Jun 2014 23:09:58 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: gapedotardy@fulvetta.riseup.net) with ESMTPSA id 132B1246 Message-ID: <539D38AA.7080903@riseup.net> Date: Sun, 15 Jun 2014 06:09:46 +0000 From: Pan Candyfur User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Currently unsupported WLAN adapter? X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.1 at mx1 X-Virus-Status: Clean X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2014 06:17:27 -0000 Yo freebsd-wireless, Spring is in the air, and I've come across a RealTek RTL8188EE chip that is single and ready to mingle. Perhaps urtw has a charming younger brother? Just thought you friendly little nymphs and satyrs might like to know... Utterly yours, -P.C. From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 02:59:07 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD25798D; Mon, 16 Jun 2014 02:59:07 +0000 (UTC) Received: from roadkill.tharned.org (roadkill.tharned.org [75.145.12.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E91D2B47; Mon, 16 Jun 2014 02:59:07 +0000 (UTC) Received: from angus.tharned.org (angus.tharned.org [10.10.10.7]) (authenticated bits=0) by roadkill.tharned.org (8.14.9/8.14.9) with ESMTP id s5G2x1IG012545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Jun 2014 21:59:06 -0500 (CDT) (envelope-from gcr+freebsd-wireless@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2014; t=1402887546; bh=502j2chSJJNUmfWJNMcQAlgIG7EGpbpQwQwal7OOx64=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=JFT7t/Y3342x0cMyhiAIn29y97gA7Z6RAv2APDHiSaqIRJd5wGfsgcffy3dmQ6XHA fFUEvT5wmQhjUQz/YUny3x4bRnMaZofVGrLWSUJrmyy2UTS6L5K3sBbIpegOSVH6jo UpwKlfsQGBqIjxPO1tuInSCzS3NCMWWHe3VeDozB1+7CiiqpM+c97MjSCRf0/9asxx 8IwXqfAxhuplla3nox5IJXR9FBjYK/VSFXrIhdEdCMicnT79afe5q2EMS7eMfd1rzY gaaqss+oXasqN0wi5VWzcSs/TcYiFJh3S+pthv8I8lkYQacFaTdppQ7yBeRlxEQKpa xdp8IZYrmvs1Q== Date: Sun, 15 Jun 2014 21:59:01 -0500 (CDT) From: Greg Rivers To: Adrian Chadd Subject: Re: recommended usb wifi device? In-Reply-To: Message-ID: References: <52F16122.9010106@freebsd.org> <52F17F60.8040900@da3m0n8t3r.com> <52F18C00.2030706@freebsd.org> <52F18DB5.70407@da3m0n8t3r.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (roadkill.tharned.org [75.145.12.185]); Sun, 15 Jun 2014 21:59:06 -0500 (CDT) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 02:59:07 -0000 On Tue, 4 Feb 2014, Adrian Chadd wrote: > I promise I'll write a 7260 driver soon. if it's not done by bsdcan, > twist my arm. > Has there been any (hopefully polite) twisting yet? Does the 7260 support AP mode? Seems this chip set is becoming more and more common. -- Greg Rivers From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 03:07:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80043B6C for ; Mon, 16 Jun 2014 03:07:13 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F0682C96 for ; Mon, 16 Jun 2014 03:07:13 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id dc16so6837156qab.29 for ; Sun, 15 Jun 2014 20:07:12 -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=k+62b0jiyur9KKiUYgpj7otCvJS2OiZJoaMQTFgL8qM=; b=gRijYpRFf65KxkOudwEa/wzfsmhMToj7lpLSh0d1q600TBuhThqYL0P4gcC6ClMg1E zXgTogHj9sj7+91ZmvB91qyp5NUh/p95I9s9CH23wMnsA0LTyuEPwFr9tF41vU24OYNh n2u02G5/XkRDoeCBcCJXaTQMwFgHIYtaFa4DmpitwA8voaVuzxQdyUm/KmSvXlJFOgRT 3RB0r0ZSiFpvAtG97fPLorTffYMi1bWalSh6LnpSnJA99iLVfgLiaWaxfxHHvblteb3T nht9gazwyJjg2DUf3MICbkzukFEA3zCsrYayfaZdA2TD1vqGE7kX8RbeOGcsZcI/76or N3gQ== MIME-Version: 1.0 X-Received: by 10.140.47.16 with SMTP id l16mr21622657qga.24.1402888032259; Sun, 15 Jun 2014 20:07:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Sun, 15 Jun 2014 20:07:12 -0700 (PDT) In-Reply-To: References: <52F16122.9010106@freebsd.org> <52F17F60.8040900@da3m0n8t3r.com> <52F18C00.2030706@freebsd.org> <52F18DB5.70407@da3m0n8t3r.com> Date: Sun, 15 Jun 2014 20:07:12 -0700 X-Google-Sender-Auth: RQ3Ed7hSVCo8vjPnsreR6h3N1wM Message-ID: Subject: Re: recommended usb wifi device? From: Adrian Chadd To: Greg Rivers Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 03:07:13 -0000 I mostly ran out of energy and motivation to write this. I'm trying to get the basic firmware loading bits done tonight. The linux driver is .. special. -a On 15 June 2014 19:59, Greg Rivers wrote: > On Tue, 4 Feb 2014, Adrian Chadd wrote: > >> I promise I'll write a 7260 driver soon. if it's not done by bsdcan, >> twist my arm. >> > Has there been any (hopefully polite) twisting yet? Does the 7260 support > AP mode? Seems this chip set is becoming more and more common. > > -- > Greg Rivers From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2BB992D4 for ; Mon, 16 Jun 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0E09D234A for ; Mon, 16 Jun 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5G80LhL074889 for ; Mon, 16 Jun 2014 09:00:21 +0100 (BST) (envelope-from bz-noreply@freebsd.org) Message-Id: <201406160800.s5G80LhL074889@kenobi.freebsd.org> From: bz-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 16 Jun 2014 08:00:21 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 09:04:01 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EF4C5275 for ; Mon, 16 Jun 2014 09:04:01 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 52467293D for ; Mon, 16 Jun 2014 09:04:01 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id k14so5179117wgh.6 for ; Mon, 16 Jun 2014 02:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=lmGgc/YL4jGT4/vMZjI9576aO8p7IrVJGF4inVG/ZAU=; b=FmdiHciNeDQuJRMiVHrvxID4ef8B69iKtswWVKKLWJ8SBffhwmxj7wDvRdGiOveqg8 fuiSFslQVLNw1SFJjvThdYe0WdN6SVbM81ChcFRdiPftkEaaLulCmPFoy+Kjq6cd0Mt0 Qu5YhpjkuVzEuVvKA2qvEUZY/fI0CgcjBmUZSsmmU17grhOgmMSyePAdOHx+LrZFeSZr fznimX58AteSXz1JlUzWIfrK5EzKUGZr7D9H25avSRGJPwKJauICxiMQAv6+auRRefIX AUbl1BLp8AI32qdjzhJnYnBv5mef8TdH00N9oqELF8kOSeDuDsTOgyMa6E4HfoMLx7G8 ARhQ== X-Received: by 10.180.92.69 with SMTP id ck5mr25650278wib.15.1402909439487; Mon, 16 Jun 2014 02:03:59 -0700 (PDT) Received: from [192.168.2.30] ([2.176.192.255]) by mx.google.com with ESMTPSA id z7sm32666187eeo.42.2014.06.16.02.03.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 02:03:58 -0700 (PDT) Message-ID: <539EB2FA.3050700@gmail.com> Date: Mon, 16 Jun 2014 13:33:54 +0430 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: need your opnion about wifi device Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 09:04:02 -0000 Hi, I am planning to buy one the following USB WiFi devices: 1.Tenda W311U+ 2.TP-Link TL-WN7200ND I would appriciate if anyone share his experiences with the above devices. BTW, I plan to use the device on freebsd/8. -- Best regards. Hooman Fazaeli From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 14:04:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CAA772B0 for ; Mon, 16 Jun 2014 14:04:08 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AAE13249D for ; Mon, 16 Jun 2014 14:04:08 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id CA2EE1936DE; Mon, 16 Jun 2014 14:04:07 +0000 (UTC) Subject: Re: need your opnion about wifi device From: Sean Bruno Reply-To: sbruno@freebsd.org To: Hooman Fazaeli In-Reply-To: <539EB2FA.3050700@gmail.com> References: <539EB2FA.3050700@gmail.com> Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Jun 2014 07:04:07 -0700 Message-ID: <1402927447.16961.3.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 14:04:08 -0000 On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > Hi, > > I am planning to buy one the following USB WiFi devices: > > 1.Tenda W311U+ > 2.TP-Link TL-WN7200ND > > I would appriciate if anyone share his experiences with the above devices. > BTW, I plan to use the device on freebsd/8. > These both appear to be Ralink based devices. AFAIK there is no FreeBSD support for either device. sean From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 18:18:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F2EA95EA for ; Mon, 16 Jun 2014 18:18:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D9FDC2D85 for ; Mon, 16 Jun 2014 18:18:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5GIIMss074208 for ; Mon, 16 Jun 2014 19:18:22 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 191090] New: rsu panics when reboot Date: Mon, 16 Jun 2014 18:18:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dchagin@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 18:18:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191090 Bug ID: 191090 Summary: rsu panics when reboot Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: dchagin@FreeBSD.org Mon Jun 16 10:01:48 MSK 2014 FreeBSD dchagin.static.corbina.net 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r267493+5636483(lemul): Mon Jun 16 09:18:14 MSK 2014=20=20=20=20 root@dchagin.static.corbina.net:/home/dchagin/garbage/obj/home/dchagin/head= /sys/YOY amd64 panic: 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 condition= s. 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: <118>Jun 16 09:47:26 dchagin reboot: rebooted by root <118>Jun 16 09:47:26 dchagin syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...7 2 2 1 0 0 0 0 done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done All buffers synced. lock order reversal: 1st 0xfffff8001128e5f0 ufs (ufs) @ /home/dchagin/head/sys/kern/vfs_mount.c:1237 2nd 0xfffff800114d2d50 devfs (devfs) @ /home/dchagin/head/sys/ufs/ffs/ffs_vfsops.c:1412 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe033d1e4= 380 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe033d1e4430 witness_checkorder() at witness_checkorder+0xdc2/frame 0xfffffe033d1e44c0 __lockmgr_args() at __lockmgr_args+0xdca/frame 0xfffffe033d1e4600 vop_stdlock() at vop_stdlock+0x3c/frame 0xfffffe033d1e4620 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x14a/frame 0xfffffe033d1e4670 _vn_lock() at _vn_lock+0xaa/frame 0xfffffe033d1e46e0 ffs_flushfiles() at ffs_flushfiles+0x88/frame 0xfffffe033d1e4740 softdep_flushfiles() at softdep_flushfiles+0x1e3/frame 0xfffffe033d1e47a0 ffs_unmount() at ffs_unmount+0x152/frame 0xfffffe033d1e4800 dounmount() at dounmount+0x445/frame 0xfffffe033d1e4890 vfs_unmountall() at vfs_unmountall+0xb1/frame 0xfffffe033d1e48e0 kern_reboot() at kern_reboot+0x5d0/frame 0xfffffe033d1e4960 sys_reboot() at sys_reboot+0x41/frame 0xfffffe033d1e4980 amd64_syscall() at amd64_syscall+0x27d/frame 0xfffffe033d1e4ab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe033d1e4ab0 --- syscall (55, FreeBSD ELF64, sys_reboot), rip =3D 0x80086380c, rsp =3D 0x7fffffffe9d8, rbp =3D 0x7fffffffeb40 --- lock order reversal: 1st 0xfffff8001128e5f0 ufs (ufs) @ /home/dchagin/head/sys/kern/vfs_mount.c:1237 2nd 0xffffffff80feefb8 GEOM topology (GEOM topology) @ /home/dchagin/head/sys/ufs/ffs/ffs_vfsops.c:1302 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe033d1e4= 600 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe033d1e46b0 witness_checkorder() at witness_checkorder+0xdc2/frame 0xfffffe033d1e4740 _sx_xlock() at _sx_xlock+0x78/frame 0xfffffe033d1e47a0 ffs_unmount() at ffs_unmount+0x306/frame 0xfffffe033d1e4800 dounmount() at dounmount+0x445/frame 0xfffffe033d1e4890 vfs_unmountall() at vfs_unmountall+0xb1/frame 0xfffffe033d1e48e0 kern_reboot() at kern_reboot+0x5d0/frame 0xfffffe033d1e4960 sys_reboot() at sys_reboot+0x41/frame 0xfffffe033d1e4980 amd64_syscall() at amd64_syscall+0x27d/frame 0xfffffe033d1e4ab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe033d1e4ab0 --- syscall (55, FreeBSD ELF64, sys_reboot), rip =3D 0x80086380c, rsp =3D 0x7fffffffe9d8, rbp =3D 0x7fffffffeb40 --- lock order reversal: 1st 0xfffff800111f67c8 ufs (ufs) @ /home/dchagin/head/sys/kern/vfs_mount.c:1237 2nd 0xffffffff810090b0 allproc (allproc) @ /home/dchagin/head/sys/kern/kern_descrip.c:2790 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe033d1e4= 610 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe033d1e46c0 witness_checkorder() at witness_checkorder+0xdc2/frame 0xfffffe033d1e4750 _sx_slock() at _sx_slock+0x79/frame 0xfffffe033d1e47b0 mountcheckdirs() at mountcheckdirs+0x47/frame 0xfffffe033d1e4800 dounmount() at dounmount+0x390/frame 0xfffffe033d1e4890 vfs_unmountall() at vfs_unmountall+0xb1/frame 0xfffffe033d1e48e0 kern_reboot() at kern_reboot+0x5d0/frame 0xfffffe033d1e4960 sys_reboot() at sys_reboot+0x41/frame 0xfffffe033d1e4980 amd64_syscall() at amd64_syscall+0x27d/frame 0xfffffe033d1e4ab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe033d1e4ab0 --- syscall (55, FreeBSD ELF64, sys_reboot), rip =3D 0x80086380c, rsp =3D 0x7fffffffe9d8, rbp =3D 0x7fffffffeb40 --- Uptime: 26m18s Fatal trap 9: general protection fault while in kernel mode cpuid =3D 4; apic id =3D 04 instruction pointer =3D 0x20:0xffffffff806658f8 stack pointer =3D 0x28:0xfffffe0000331680 frame pointer =3D 0x28:0xfffffe00003316a0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 15 (usbus2) Reading symbols from /boot/modules/acpi_call.ko...done. Loaded symbols for /boot/modules/acpi_call.ko Reading symbols from /boot/kernel/acpi_ibm.ko.symbols...done. Loaded symbols for /boot/kernel/acpi_ibm.ko.symbols #0 doadump (textdump=3D-2134647920) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=3D-2134647920) at pcpu.h:219 #1 0xffffffff802ffa75 in db_fncall (dummy1=3D, dummy2=3D, dummy3=3D, dummy4=3D) at /home/dchagin/head/sys/ddb/db_command.c:578 #2 0xffffffff802ff75d in db_command (cmd_table=3D0x0) at /home/dchagin/head/sys/ddb/db_command.c:449 #3 0xffffffff802ff4d4 in db_command_loop () at /home/dchagin/head/sys/ddb/db_command.c:502 #4 0xffffffff80301f50 in db_trap (type=3D, code=3D0) at /home/dchagin/head/sys/ddb/db_main.c:231 #5 0xffffffff8058c3c9 in kdb_trap (type=3D9, code=3D0, tf=3D) at /home/dchagin/head/sys/kern/subr_kdb.c:656 #6 0xffffffff8081b17c in trap_fatal (frame=3D0xfffffe00003315d0, eva=3D) at /home/dchagin/head/sys/amd64/amd64/trap.c:875 #7 0xffffffff8081ae16 in trap (frame=3D) at /home/dchagin/head/sys/amd64/amd64/trap.c:202 #8 0xffffffff807feae2 in calltrap () at /home/dchagin/head/sys/amd64/amd64/exception.S:231 #9 0xffffffff806658f8 in node_free (ni=3D0xfffffe0002e74000) at ieee80211_ratectl.h:84 #10 0xffffffff80451f07 in rsu_detach (self=3D) at /home/dchagin/head/sys/dev/usb/wlan/if_rsu.c:647 #11 0xffffffff8058080f in device_detach (dev=3D0xfffff80011135200) at device_if.h:214 #12 0xffffffff8043c081 in usb_detach_device (udev=3D0xfffff8001111a000, iface_index=3D, flag=3D0 '\0') at /home/dchagin/head/sys/dev/usb/usb_device.c:1141 #13 0xffffffff8043b154 in usb_unconfigure (udev=3D0xfffff8001111a000, flag=3D2 '\002') at /home/dchagin/head/sys/dev/usb/usb_device.c:530 #14 0xffffffff8043e2d6 in usb_free_device (udev=3D0xfffff8001111a000, flag=3D) at /home/dchagin/head/sys/dev/usb/usb_device.c:2168 #15 0xffffffff80446811 in uhub_detach (dev=3D) at /home/dchagin/head/sys/dev/usb/usb_hub.c:1519 #16 0xffffffff8058080f in device_detach (dev=3D0xfffff800110c3000) at device_if.h:214 #17 0xffffffff8043c081 in usb_detach_device (udev=3D0xfffff800110b6000, iface_index=3D, flag=3D0 '\0') at /home/dchagin/head/sys/dev/usb/usb_device.c:1141 #18 0xffffffff8043b154 in usb_unconfigure (udev=3D0xfffff800110b6000, flag=3D2 '\002') at /home/dchagin/head/sys/dev/usb/usb_device.c:530 #19 0xffffffff8043e2d6 in usb_free_device (udev=3D0xfffff800110b6000, flag=3D) at /home/dchagin/head/sys/dev/usb/usb_device.c:2168 #20 0xffffffff80446811 in uhub_detach (dev=3D) at /home/dchagin/head/sys/dev/usb/usb_hub.c:1519 #21 0xffffffff8058080f in device_detach (dev=3D0xfffff80003b07700) at device_if.h:214 #22 0xffffffff8043c081 in usb_detach_device (udev=3D0xfffff80010f41000, iface_index=3D, flag=3D0 '\0') at /home/dchagin/head/sys/dev/usb/usb_device.c:1141 #23 0xffffffff8043b154 in usb_unconfigure (udev=3D0xfffff80010f41000, flag=3D0 '\0') at /home/dchagin/head/sys/dev/usb/usb_device.c:530 #24 0xffffffff8043ab60 in usbd_set_config_index (udev=3D0xfffff80010f41000, index=3D255 '=D0=AA') at /home/dchagin/head/sys/dev/usb/usb_device.c:593 #25 0xffffffff8042eb02 in usb_bus_shutdown (pm=3D) at /home/dchagin/head/sys/dev/usb/controller/usb_controller.c:616 #26 0xffffffff80449c6f in usb_process (arg=3D0xfffffe0000d52db0) at /home/dchagin/head/sys/dev/usb/usb_process.c:177 #27 0xffffffff8051d199 in fork_exit ( callout=3D0xffffffff80449b60 , arg=3D0xfffffe0000d52db0, frame=3D0xfffffe0000331ac0) at /home/dchagin/head/sys/kern/kern_fork.c:= 977 #28 0xffffffff807ff01e in fork_trampoline () at /home/dchagin/head/sys/amd64/amd64/exception.S:605 #29 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 20:01:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D2E33733; Mon, 16 Jun 2014 20:01:37 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20586288A; Mon, 16 Jun 2014 20:01:36 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id el20so3364191lab.1 for ; Mon, 16 Jun 2014 13:01:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=AC9MoNkwcr+GPDOY/3Dn3Iz7CJ/sU0SLn6DSG2Imj4Y=; b=eVo3KhTEL8xsC0rDvCdRwwgejaZLTZpIQ0vQu2IcoDxHPctiUgr3NfiTPoT0x4Vt2V OHd8uux9ivSyDsUJf6rNvLvSDbMJ8WetxcKThBJ1trNw/oU0ebASkX9jGu8NSZtcPzxz pkTqiHs85cHQ3OO/blCfbBekJ8PQVfXXlbrcZYBBwOAyStX7Ndac2UjvqJQb8hNiEj/Y iMMTPQi05e7J1jx2J3JNG+w3zgFJlVwiOGBhpFx6rV4KxgphxJm8Yf94RLkPozEVq5hi ePi92STAlXPs9nBx8RC5nfIhywGqe+5wt7W2sB8pP4v2djhVgHu2+LYzhxN1rt844xXe GTrg== X-Received: by 10.112.46.97 with SMTP id u1mr3089362lbm.50.1402948894521; Mon, 16 Jun 2014 13:01:34 -0700 (PDT) Received: from dchagin.static.corbina.net (dchagin.static.corbina.ru. [78.107.232.239]) by mx.google.com with ESMTPSA id lv10sm4885641lac.41.2014.06.16.13.01.32 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Jun 2014 13:01:33 -0700 (PDT) Sender: Dmitry Chagin Received: from dchagin.static.corbina.net (localhost [127.0.0.1]) by dchagin.static.corbina.net (8.14.9/8.14.8) with ESMTP id s5GK1WoH002916; Tue, 17 Jun 2014 00:01:32 +0400 (MSK) (envelope-from dchagin@dchagin.static.corbina.net) Received: (from dchagin@localhost) by dchagin.static.corbina.net (8.14.9/8.14.8/Submit) id s5GK1UE6002915; Tue, 17 Jun 2014 00:01:30 +0400 (MSK) (envelope-from dchagin) Date: Tue, 17 Jun 2014 00:01:30 +0400 From: Chagin Dmitry To: Adrian Chadd Subject: Re: recommended usb wifi device? Message-ID: <20140616200130.GA2888@dchagin.static.corbina.net> References: <52F16122.9010106@freebsd.org> <52F17F60.8040900@da3m0n8t3r.com> <52F18C00.2030706@freebsd.org> <52F18DB5.70407@da3m0n8t3r.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 20:01:37 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 15, 2014 at 08:07:12PM -0700, Adrian Chadd wrote: > I mostly ran out of energy and motivation to write this. >=20 > I'm trying to get the basic firmware loading bits done tonight. The > linux driver is .. special. >=20 >=20 Hi Adrian, please tell me if i can help. at least i can test :) --=20 Have fun! chd --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlOfTRoACgkQ0t2Tb3OO/O1KlQCfc+wWEXB4E7BUQph4U/NYK4xp KzYAoMN5qqsbEGTxpTjY50BXv+XTZOun =QbXH -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 22:29:37 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB436F4F; Mon, 16 Jun 2014 22:29:36 +0000 (UTC) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C67A253C; Mon, 16 Jun 2014 22:29:36 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id x48so6331547wes.39 for ; Mon, 16 Jun 2014 15:29:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=a+YJHVxJ/LwNxpDpQv3yStqqX40cv1S2fmU11aa28m4=; b=TjLjOgKXYM48YbvRhv/TlHJHcFbTesoY1n2iyQbD+XGmOPXNgQ6bHt4NeazUgvDsWY wk5TVpx8DDQzJMRnIcySt87JYp0DGPfR7EMDEY4UMBzuKbGQgWPWuiN+FJ2DOOowfNOh y41R40JScUmn/dB58BdV5gRd5mnMwiT6+yNsiqyGiU5XgHgyam5cZeq48yUUmvg/uGOc QD4ZUAI3WZ2n28CBws7NjLKWqfdzv6y6BEv3S3R2Wz4KUYRdzuB4oVdwv96/OTZDH/EA RzbZ0KfPLvmYJXMwaKArb/mjXLQeTs6Tm2Qh6OEAOKyYF/n9zjpLMzVZQM7gEP7VVxQ8 JDaw== X-Received: by 10.180.38.107 with SMTP id f11mr30718310wik.59.1402957774331; Mon, 16 Jun 2014 15:29:34 -0700 (PDT) Received: from [192.168.2.30] ([2.176.192.255]) by mx.google.com with ESMTPSA id r44sm36876629eeo.18.2014.06.16.15.29.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Jun 2014 15:29:33 -0700 (PDT) Message-ID: <539F6FCC.7030003@gmail.com> Date: Tue, 17 Jun 2014 02:59:32 +0430 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: sbruno@freebsd.org Subject: Re: need your opnion about wifi device References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> In-Reply-To: <1402927447.16961.3.camel@bruno> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: Sean Bruno , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 22:29:37 -0000 On 6/16/2014 6:34 PM, Sean Bruno wrote: > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: >> Hi, >> >> I am planning to buy one the following USB WiFi devices: >> >> 1.Tenda W311U+ >> 2.TP-Link TL-WN7200ND >> >> I would appriciate if anyone share his experiences with the above devices. >> BTW, I plan to use the device on freebsd/8. >> > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > support for either device. > > sean > According to: https://wikidevi.com/wiki/Tenda_W311U%2B https://wikidevi.com/wiki/TP-LINK_TL-WN7200ND Both devices use Ralink RT3070 chipset, which are apparently supported by run(4) driver, as stated in the man page. Am I missing something obvious? -- Best regards. Hooman Fazaeli From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 23:34:15 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69632E5 for ; Mon, 16 Jun 2014 23:34:15 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 495FD2AED for ; Mon, 16 Jun 2014 23:34:14 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id C42AB1936DE; Mon, 16 Jun 2014 23:34:13 +0000 (UTC) Subject: Re: need your opnion about wifi device From: Sean Bruno Reply-To: sbruno@freebsd.org To: Hooman Fazaeli In-Reply-To: <539F6FCC.7030003@gmail.com> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> <539F6FCC.7030003@gmail.com> Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Jun 2014 16:34:12 -0700 Message-ID: <1402961652.1905.2.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 23:34:15 -0000 On Tue, 2014-06-17 at 02:59 +0430, Hooman Fazaeli wrote: > On 6/16/2014 6:34 PM, Sean Bruno wrote: > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > > Hi, > > > > > > I am planning to buy one the following USB WiFi devices: > > > > > > 1.Tenda W311U+ > > > 2.TP-Link TL-WN7200ND > > > > > > I would appriciate if anyone share his experiences with the above devices. > > > BTW, I plan to use the device on freebsd/8. > > > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > > support for either device. > > > > sean > > > > According to: > > https://wikidevi.com/wiki/Tenda_W311U%2B > https://wikidevi.com/wiki/TP-LINK_TL-WN7200ND > > Both devices use Ralink RT3070 chipset, which are apparently supported > by run(4) driver, as stated in the man page. > Am I missing something obvious? > > > > > Looked at sys/dev/usb/wlan/if_run.c I don't see a TP-LINK in there ... you may be able to get away with adding it. sean From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 16 23:37:39 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE3A9135 for ; Mon, 16 Jun 2014 23:37:39 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B5FE52B08 for ; Mon, 16 Jun 2014 23:37:39 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5GNbdI4029747 for ; Tue, 17 Jun 2014 00:37:39 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 191090] rsu panics when reboot Date: Mon, 16 Jun 2014 23:37:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: vidwer+fbsdbugs@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 23:37:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090 vidwer+fbsdbugs@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vidwer+fbsdbugs@gmail.com --- Comment #1 from vidwer+fbsdbugs@gmail.com --- Can you tell more about the hardware: what is the commercial name of the adapter, how is attached: to usb 2.0 or 3.0, etcetera? How does your 'YOY' kernel configuration look like? When does the panic happen, is it plugged in while rebooting? Does your machine panic when removing the USB device? Can you reproduce the panic with 10-STABLE? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 02:48:23 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3B85DA; Tue, 17 Jun 2014 02:48:23 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C24A2964; Tue, 17 Jun 2014 02:48:22 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s5H2jprP012852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 Jun 2014 10:45:51 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s5H2jpT5012851; Tue, 17 Jun 2014 10:45:51 +0800 (CST) (envelope-from kevlo) Date: Tue, 17 Jun 2014 10:45:50 +0800 From: Kevin Lo To: sbruno@freebsd.org Subject: Re: need your opnion about wifi device Message-ID: <20140617024550.GA12842@ns.kevlo.org> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1402927447.16961.3.camel@bruno> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 02:48:23 -0000 On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote: > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > Hi, > > > > I am planning to buy one the following USB WiFi devices: > > > > 1.Tenda W311U+ > > 2.TP-Link TL-WN7200ND > > > > I would appriciate if anyone share his experiences with the above devices. > > BTW, I plan to use the device on freebsd/8. > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > support for either device. I think there's a typo s/no// :) Both devices are in fact supported by FreeBSD. > sean Kevin From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 08:35:23 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79DD5FB9 for ; Tue, 17 Jun 2014 08:35:23 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 610452392 for ; Tue, 17 Jun 2014 08:35:23 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5H8ZN9Z087872 for ; Tue, 17 Jun 2014 09:35:23 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 191090] rsu panics when reboot Date: Tue, 17 Jun 2014 08:35:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dchagin@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 08:35:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090 --- Comment #2 from Dmitry Chagin --- Created attachment 143861 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143861&action=edit YOY kernel config -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 08:35:33 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3ABF3FD6 for ; Tue, 17 Jun 2014 08:35:33 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 228CA2398 for ; Tue, 17 Jun 2014 08:35:33 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5H8ZXMM089587 for ; Tue, 17 Jun 2014 09:35:33 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 191090] rsu panics when reboot Date: Tue, 17 Jun 2014 08:35:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dchagin@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 08:35:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090 --- Comment #3 from Dmitry Chagin --- According to a trap trace i do not think what panic is hw specific... Nonetheless, it is a asus usb-n10 adapter. usbus2 on ehci1 which is Intel Lynx Point USB 2.0 controller, panic occurs when adapter plugged in. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 09:58:38 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DFFDA9A7 for ; Tue, 17 Jun 2014 09:58:38 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD5782B4E for ; Tue, 17 Jun 2014 09:58:38 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5H9wcbq019716 for ; Tue, 17 Jun 2014 10:58:38 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 191090] rsu panics when reboot Date: Tue, 17 Jun 2014 09:58:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dchagin@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 09:58:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191090 --- Comment #4 from Dmitry Chagin --- yet another panic, when removing rsu: rsu0: on usbus2 rsu0: MAC/BB RTL8712 cut 3 wlan1: Ethernet address: 50:46:5d:76:ef:15 ugen2.3: at usbus2 (disconnected) rsu0: at uhub3, port 3, addr 3 (disconnected) Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex rsu0 (network driver) r = 0 (0xfffffe0002c330a0) locked @ /home/dchagin/head/sys/dev/usb/usb_util.c:146 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe033d2292e0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe033d229390 witness_warn() at witness_warn+0x4b5/frame 0xfffffe033d229450 trap_pfault() at trap_pfault+0x59/frame 0xfffffe033d2294f0 trap() at trap+0x752/frame 0xfffffe033d229840 calltrap() at calltrap+0x8/frame 0xfffffe033d229840 --- trap 0xc, rip = 0xffffffff804358fe, rsp = 0xfffffe033d229900, rbp = 0xfffffe033d229980 --- rsu_init_locked() at rsu_init_locked+0x19ce/frame 0xfffffe033d229980 rsu_ioctl() at rsu_ioctl+0xa6/frame 0xfffffe033d2299b0 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfffffe033d229a10 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfffffe033d229a40 fork_exit() at fork_exit+0xd9/frame 0xfffffe033d229ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe033d229ab0 --- trap 0, rip = 0, rsp = 0xfffffe033d229b70, rbp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff804358fe stack pointer = 0x28:0xfffffe033d229900 frame pointer = 0x28:0xfffffe033d229980 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 = 0 (rsu0 net80211 taskq) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 14:04:28 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37F67578 for ; Tue, 17 Jun 2014 14:04:28 +0000 (UTC) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::103]) by mx1.freebsd.org (Postfix) with ESMTP id 1138C2321 for ; Tue, 17 Jun 2014 14:04:28 +0000 (UTC) Received: from [172.16.1.182] (unknown [172.16.1.182]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 8C9442432A for ; Tue, 17 Jun 2014 14:04:27 +0000 (UTC) Message-ID: <53A04AE9.1070401@metricspace.net> Date: Tue, 17 Jun 2014 10:04:25 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Intel 7620AC? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 14:04:28 -0000 Hello, I recently purchased a new laptop, which came with an Intel 7260AC card, which doesn't seem to be supported on FreeBSD. I thought I might replace it with a supported card, like an Atheros, but the device seems to be a different form-factor than micro-PCIe (NGFF M.2, I think is what it's called). Cursory googling seems to indicate that there's a linux driver. Are there any plans to port it? Or as an alternative, are there any supported cards that use the M.2 interface? Thanks, Eric From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 14:07:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04A38622; Tue, 17 Jun 2014 14:07:38 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7EE9237B; Tue, 17 Jun 2014 14:07:37 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 18D7E1936DE; Tue, 17 Jun 2014 14:07:36 +0000 (UTC) Subject: Re: need your opnion about wifi device From: Sean Bruno Reply-To: sbruno@freebsd.org To: Kevin Lo In-Reply-To: <20140617024550.GA12842@ns.kevlo.org> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> <20140617024550.GA12842@ns.kevlo.org> Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Jun 2014 07:07:33 -0700 Message-ID: <1403014053.1905.4.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 14:07:38 -0000 On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote: > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote: > > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > > Hi, > > > > > > I am planning to buy one the following USB WiFi devices: > > > > > > 1.Tenda W311U+ > > > 2.TP-Link TL-WN7200ND > > > > > > I would appriciate if anyone share his experiences with the above devices. > > > BTW, I plan to use the device on freebsd/8. > > > > > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > > support for either device. > > I think there's a typo s/no// :) > Both devices are in fact supported by FreeBSD. > > > sean > > Kevin Really? I didn't see any indication in the driver that they were supported. sean From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 15:22:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DB773D2 for ; Tue, 17 Jun 2014 15:22:08 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20A192B08 for ; Tue, 17 Jun 2014 15:22:08 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id i8so9994592qcq.6 for ; Tue, 17 Jun 2014 08:22: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=oSI3teWxOLGajBp6Eb0BVXUDG79v7bA9Q4qGHwvtVL0=; b=cP9xDDFJcDJ8Fez2H3r246Y1G9cWxLhAa2ZVO0oCca8eO8t1MYqppkgCd4g2Fs5RGN L1S5yX3or2VslODbE3W1IgFAENw5CC2CC9+jBDEaJK/wMzH+AamLvrJ2FbDkbbWPPxzG bmLJVF1nNXn9VqLJ6tsl8CXPUBcbe/ZI4SLVHQkAu7CoQdXJBXVv3A9dj5L2HE4HtLer lkD+FpWmJSNhHk+4oIe873Q5IhyKzbwe7cwUr4B8fEUT0WMHsNRa2C+2/gqA25ufrqLq Il8Q5bPIVH+reBvG3Z6uUDcZUdyKpdwn8aX5/0CHj4zRqyNHgPVM8Oox5eoPHXxVWnrT srpQ== MIME-Version: 1.0 X-Received: by 10.229.93.133 with SMTP id v5mr37248302qcm.1.1403018527265; Tue, 17 Jun 2014 08:22:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Tue, 17 Jun 2014 08:22:07 -0700 (PDT) In-Reply-To: <53A04AE9.1070401@metricspace.net> References: <53A04AE9.1070401@metricspace.net> Date: Tue, 17 Jun 2014 08:22:07 -0700 X-Google-Sender-Auth: -1tdGHHrp9QsDBpFZf8LJuHMW-0 Message-ID: Subject: Re: Intel 7620AC? From: Adrian Chadd To: Eric McCorkle Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 15:22:08 -0000 Hi, I'm tinkering with the 7260, but I currently have no plans to actively port the driver. Sorry, -a On 17 June 2014 07:04, Eric McCorkle wrote: > Hello, > > I recently purchased a new laptop, which came with an Intel 7260AC card, > which doesn't seem to be supported on FreeBSD. I thought I might replace it > with a supported card, like an Atheros, but the device seems to be a > different form-factor than micro-PCIe (NGFF M.2, I think is what it's > called). > > Cursory googling seems to indicate that there's a linux driver. Are there > any plans to port it? > > Or as an alternative, are there any supported cards that use the M.2 > interface? > > > Thanks, > Eric > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 15:43:35 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D53AA3B; Tue, 17 Jun 2014 15:43:35 +0000 (UTC) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::103]) by mx1.freebsd.org (Postfix) with ESMTP id 138562CEA; Tue, 17 Jun 2014 15:43:35 +0000 (UTC) Received: from [10.139.152.225] (mobile-198-228-205-150.mycingular.net [198.228.205.150]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id DE41224BE1; Tue, 17 Jun 2014 15:43:33 +0000 (UTC) References: <53A04AE9.1070401@metricspace.net> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11B511) From: Eric McCorkle Subject: Re: Intel 7620AC? Date: Tue, 17 Jun 2014 11:43:25 -0400 To: Adrian Chadd Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 15:43:35 -0000 Are there likely to be any issues that you know of? I'm rather busy, but I'= d be willing to try porting the driver myself. > On Jun 17, 2014, at 11:22 AM, Adrian Chadd wrote: >=20 > Hi, >=20 > I'm tinkering with the 7260, but I currently have no plans to actively > port the driver. >=20 > Sorry, >=20 >=20 > -a >=20 >=20 >> On 17 June 2014 07:04, Eric McCorkle wrote: >> Hello, >>=20 >> I recently purchased a new laptop, which came with an Intel 7260AC card, >> which doesn't seem to be supported on FreeBSD. I thought I might replace= it >> with a supported card, like an Atheros, but the device seems to be a >> different form-factor than micro-PCIe (NGFF M.2, I think is what it's >> called). >>=20 >> Cursory googling seems to indicate that there's a linux driver. Are ther= e >> any plans to port it? >>=20 >> Or as an alternative, are there any supported cards that use the M.2 >> interface? >>=20 >>=20 >> Thanks, >> Eric >> _______________________________________________ >> 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" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 15:44:45 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BAE5B59; Tue, 17 Jun 2014 15:44:45 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 361042D03; Tue, 17 Jun 2014 15:44:44 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s5HFiaT2017722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 Jun 2014 23:44:37 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s5HFia6B017721; Tue, 17 Jun 2014 23:44:36 +0800 (CST) (envelope-from kevlo) Date: Tue, 17 Jun 2014 23:44:36 +0800 From: Kevin Lo To: sbruno@freebsd.org Subject: Re: need your opnion about wifi device Message-ID: <20140617154436.GA17667@ns.kevlo.org> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> <20140617024550.GA12842@ns.kevlo.org> <1403014053.1905.4.camel@bruno> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1403014053.1905.4.camel@bruno> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 15:44:45 -0000 On Tue, Jun 17, 2014 at 07:07:33AM -0700, Sean Bruno wrote: > On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote: > > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote: > > > > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > > > Hi, > > > > > > > > I am planning to buy one the following USB WiFi devices: > > > > > > > > 1.Tenda W311U+ > > > > 2.TP-Link TL-WN7200ND > > > > > > > > I would appriciate if anyone share his experiences with the above devices. > > > > BTW, I plan to use the device on freebsd/8. > > > > > > > > > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > > > support for either device. > > > > I think there's a typo s/no// :) > > Both devices are in fact supported by FreeBSD. > > > > > sean > > > > Kevin > > > Really? I didn't see any indication in the driver that they were > supported. At line 265 of file if_run.c: RUN_DEV(RALINK, RT3070) > sean Kevin From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 15:48:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78EBDE02 for ; Tue, 17 Jun 2014 15:48:09 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 39DC32D3C for ; Tue, 17 Jun 2014 15:48:09 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id dc16so9542127qab.15 for ; Tue, 17 Jun 2014 08:48:08 -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=315PYeO8MLfWVOFoxuWVrRp6q/gPTEcpKmV/kQ1EQFA=; b=03MTAOfFmzpBLyRxJZLcpwmoTKOKpQsNTeFz1qKJ+UdnNLmpGdzBzYO7e9kdekG1Rr wYpKS1tNWOpMlRxnb2mYmQ6OSUYsRmQGBeRgnuIh7mjUn+IOpsFNKNiMeunZ/QiCeAx7 UkWAnkqfB2yrW2hRJmJlAOdS/44MOqIpQlW2DVXdOJPks7sFCYTFsFphumlQHiafmHzH 3z+jd+kY2cr6ZsuvzzjH75BDVWbvgsDeIl7ijMb4rgdVr0ilg4Yg3IvpNKTYtPGOjonF 4FpoCeWwB9yVQ/+lx7zaV7UgXD52X4vGtv2LQg+UX87/u5KwMduUCtGKaZdKkxc5CVw/ cm9g== MIME-Version: 1.0 X-Received: by 10.224.66.70 with SMTP id m6mr38526720qai.55.1403020088178; Tue, 17 Jun 2014 08:48:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Tue, 17 Jun 2014 08:48:08 -0700 (PDT) In-Reply-To: References: <53A04AE9.1070401@metricspace.net> Date: Tue, 17 Jun 2014 08:48:08 -0700 X-Google-Sender-Auth: tYUL_oDWbF-vIinv0z2pOGp42WU Message-ID: Subject: Re: Intel 7620AC? From: Adrian Chadd To: Eric McCorkle Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 15:48:09 -0000 It's a linux driver, so you have to port the linux interface-y bits too and whatever else is missing. You also have to be careful that you don't fall afoul of any RCU style patents. One of the many reasons why mac80211 from linux hasn't been ported over is that it contains RCU code. I have a very basic probe/attach working. My next task is implementing their "transaction" layer that speaks to various busses (although the only thing they currently ship in Linux is PCIe.) I'm kind of hoping that once I've implemented that, porting the rest of the driver won't be so terrible-sounding. -a On 17 June 2014 08:43, Eric McCorkle wrote: > Are there likely to be any issues that you know of? I'm rather busy, but I'd be willing to try porting the driver myself. > >> On Jun 17, 2014, at 11:22 AM, Adrian Chadd wrote: >> >> Hi, >> >> I'm tinkering with the 7260, but I currently have no plans to actively >> port the driver. >> >> Sorry, >> >> >> -a >> >> >>> On 17 June 2014 07:04, Eric McCorkle wrote: >>> Hello, >>> >>> I recently purchased a new laptop, which came with an Intel 7260AC card, >>> which doesn't seem to be supported on FreeBSD. I thought I might replace it >>> with a supported card, like an Atheros, but the device seems to be a >>> different form-factor than micro-PCIe (NGFF M.2, I think is what it's >>> called). >>> >>> Cursory googling seems to indicate that there's a linux driver. Are there >>> any plans to port it? >>> >>> Or as an alternative, are there any supported cards that use the M.2 >>> interface? >>> >>> >>> Thanks, >>> Eric >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 16:09:29 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34FF187B; Tue, 17 Jun 2014 16:09:29 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 134632F17; Tue, 17 Jun 2014 16:09:28 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 72E131936DE; Tue, 17 Jun 2014 16:09:27 +0000 (UTC) Subject: Re: need your opnion about wifi device From: Sean Bruno Reply-To: sbruno@freebsd.org To: Kevin Lo In-Reply-To: <20140617154436.GA17667@ns.kevlo.org> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> <20140617024550.GA12842@ns.kevlo.org> <1403014053.1905.4.camel@bruno> <20140617154436.GA17667@ns.kevlo.org> Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Jun 2014 09:09:26 -0700 Message-ID: <1403021366.39699.7.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 16:09:29 -0000 On Tue, 2014-06-17 at 23:44 +0800, Kevin Lo wrote: > On Tue, Jun 17, 2014 at 07:07:33AM -0700, Sean Bruno wrote: > > On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote: > > > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote: > > > > > > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > > > > Hi, > > > > > > > > > > I am planning to buy one the following USB WiFi devices: > > > > > > > > > > 1.Tenda W311U+ > > > > > 2.TP-Link TL-WN7200ND > > > > > > > > > > I would appriciate if anyone share his experiences with the above devices. > > > > > BTW, I plan to use the device on freebsd/8. > > > > > > > > > > > > > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > > > > support for either device. > > > > > > I think there's a typo s/no// :) > > > Both devices are in fact supported by FreeBSD. > > > > > > > sean > > > > > > Kevin > > > > > > Really? I didn't see any indication in the driver that they were > > supported. > > At line 265 of file if_run.c: > RUN_DEV(RALINK, RT3070) > > > sean > > Kevin Oh, does the device report itself as a RALINK usb device? sean From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 16:19:29 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D0071CC7; Tue, 17 Jun 2014 16:19:29 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 64B7B2041; Tue, 17 Jun 2014 16:19:28 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s5HGJLoQ017947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Jun 2014 00:19:22 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s5HGJLDT017946; Wed, 18 Jun 2014 00:19:21 +0800 (CST) (envelope-from kevlo) Date: Wed, 18 Jun 2014 00:19:20 +0800 From: Kevin Lo To: sbruno@freebsd.org Subject: Re: need your opnion about wifi device Message-ID: <20140617161920.GA17931@ns.kevlo.org> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> <20140617024550.GA12842@ns.kevlo.org> <1403014053.1905.4.camel@bruno> <20140617154436.GA17667@ns.kevlo.org> <1403021366.39699.7.camel@bruno> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1403021366.39699.7.camel@bruno> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 16:19:29 -0000 On Tue, Jun 17, 2014 at 09:09:26AM -0700, Sean Bruno wrote: > On Tue, 2014-06-17 at 23:44 +0800, Kevin Lo wrote: > > On Tue, Jun 17, 2014 at 07:07:33AM -0700, Sean Bruno wrote: > > > On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote: > > > > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote: > > > > > > > > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > > > > > Hi, > > > > > > > > > > > > I am planning to buy one the following USB WiFi devices: > > > > > > > > > > > > 1.Tenda W311U+ > > > > > > 2.TP-Link TL-WN7200ND > > > > > > > > > > > > I would appriciate if anyone share his experiences with the above devices. > > > > > > BTW, I plan to use the device on freebsd/8. > > > > > > > > > > > > > > > > > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > > > > > support for either device. > > > > > > > > I think there's a typo s/no// :) > > > > Both devices are in fact supported by FreeBSD. > > > > > > > > > sean > > > > > > > > Kevin > > > > > > > > > Really? I didn't see any indication in the driver that they were > > > supported. > > > > At line 265 of file if_run.c: > > RUN_DEV(RALINK, RT3070) > > > > > sean > > > > Kevin > > Oh, does the device report itself as a RALINK usb device? Does it matter? > sean Kevin From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 17 16:25:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FCF3F03; Tue, 17 Jun 2014 16:25:46 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F129A2118; Tue, 17 Jun 2014 16:25:45 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 8BDFE1936DE; Tue, 17 Jun 2014 16:25:44 +0000 (UTC) Subject: Re: need your opnion about wifi device From: Sean Bruno Reply-To: sbruno@freebsd.org To: Kevin Lo In-Reply-To: <20140617161920.GA17931@ns.kevlo.org> References: <539EB2FA.3050700@gmail.com> <1402927447.16961.3.camel@bruno> <20140617024550.GA12842@ns.kevlo.org> <1403014053.1905.4.camel@bruno> <20140617154436.GA17667@ns.kevlo.org> <1403021366.39699.7.camel@bruno> <20140617161920.GA17931@ns.kevlo.org> Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Jun 2014 09:25:43 -0700 Message-ID: <1403022343.39699.8.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 16:25:46 -0000 On Wed, 2014-06-18 at 00:19 +0800, Kevin Lo wrote: > On Tue, Jun 17, 2014 at 09:09:26AM -0700, Sean Bruno wrote: > > On Tue, 2014-06-17 at 23:44 +0800, Kevin Lo wrote: > > > On Tue, Jun 17, 2014 at 07:07:33AM -0700, Sean Bruno wrote: > > > > On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote: > > > > > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote: > > > > > > > > > > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote: > > > > > > > Hi, > > > > > > > > > > > > > > I am planning to buy one the following USB WiFi devices: > > > > > > > > > > > > > > 1.Tenda W311U+ > > > > > > > 2.TP-Link TL-WN7200ND > > > > > > > > > > > > > > I would appriciate if anyone share his experiences with the above devices. > > > > > > > BTW, I plan to use the device on freebsd/8. > > > > > > > > > > > > > > > > > > > > > > > > > These both appear to be Ralink based devices. AFAIK there is no FreeBSD > > > > > > support for either device. > > > > > > > > > > I think there's a typo s/no// :) > > > > > Both devices are in fact supported by FreeBSD. > > > > > > > > > > > sean > > > > > > > > > > Kevin > > > > > > > > > > > > Really? I didn't see any indication in the driver that they were > > > > supported. > > > > > > At line 265 of file if_run.c: > > > RUN_DEV(RALINK, RT3070) > > > > > > > sean > > > > > > Kevin > > > > Oh, does the device report itself as a RALINK usb device? > > Does it matter? > > > I thought it did, but its obvious that I should shut up now as I have given bad information to the requestor. sean From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 21 02:41:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EFA020D; Sat, 21 Jun 2014 02:41:58 +0000 (UTC) Received: from mail.metricspace.net (207-172-209-89.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.89]) by mx1.freebsd.org (Postfix) with ESMTP id 2359D24C2; Sat, 21 Jun 2014 02:41:57 +0000 (UTC) Received: from [172.16.1.182] (unknown [172.16.1.182]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 2A92325C50; Sat, 21 Jun 2014 02:41:57 +0000 (UTC) Message-ID: <53A4F0F4.7090507@metricspace.net> Date: Fri, 20 Jun 2014 22:41:56 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Intel 7620AC? References: <53A04AE9.1070401@metricspace.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2014 02:41:58 -0000 On 06/17/2014 11:48, Adrian Chadd wrote: > You also have to be careful that you don't fall afoul of any RCU style > patents. One of the many reasons why mac80211 from linux hasn't been > ported over is that it contains RCU code. Ugh. That sounds like nasty business. Is there any sort of write-up for driver development that outlines the patents we're trying to dodge? > I have a very basic probe/attach working. My next task is implementing > their "transaction" layer that speaks to various busses (although the > only thing they currently ship in Linux is PCIe.) I'm kind of hoping > that once I've implemented that, porting the rest of the driver won't > be so terrible-sounding. > Well, I'm not promising any results, and I only have time for it as a side-project, but if you point me to what you've got or send it to me, I'll take a swing at it. From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 21 15:55:26 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4AA7AEC7 for ; Sat, 21 Jun 2014 15:55:26 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BFBE2D90 for ; Sat, 21 Jun 2014 15:55:25 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 07FE61936DE for ; Sat, 21 Jun 2014 15:55:23 +0000 (UTC) Subject: wireless mcast updates, ic->ic_update_mcast From: Sean Bruno Reply-To: sbruno@freebsd.org To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="us-ascii" Date: Sat, 21 Jun 2014 08:55:23 -0700 Message-ID: <1403366123.39384.10.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2014 15:55:26 -0000 My T61 has a wpi(4) card in it. I noted that the console message "needs muticast update" is emitted as it doesn't implement the required function in its code and uses the default of the net80211 stack. I haven't noted any issues, but I took a journey through some of the wireless drivers to see what the status of implementation was. It seems most of the drivers stub out the required function to get rid of the warning. I perceive that with 6 exceptions, most of our wireless adapters don't have an implementation, or worse, they implement a stub to squash the warning. Shouldn't these stub functions be removed? Perhaps wrapp the net80211 default behavior in bootverbose? -- implemented ic_update_mcast() ath/if_ath.c -- implemented and working usb/wlan/if_zyd.c -- implemented and working usb/wlan/if_wi.c -- implemented and working -- sets a flag to default o/s behvavior? mwl/if_mlw.c -- function coded out, most code if 0'd out usb/wlan/if_upgt.c -- looks to default to whatever the o/s can do. usr/wlan/if_run.c -- looks to default to whatever the o/s can do -- stubbed out function to squash warning (bug?) iwn/if_iwn.c -- stubbed out in if_iwn to remove default error usb/wlan/if_rum.c -- stubbed out to remove default error usb/wlan/if_urtwn.c -- stubbed out to remove default error usb/wlan/if_urtw.c -- stubbed out to remove default error usr/wlan/if_uath.c -- stubbed out to remove default error usb/wlan/if_rsu.c -- stubbed out to remove default error wtap/if_wtap.c -- stubbed out to remove default error -- undefined, emits error correctly wpi/if_wpi.c bwi/if_bwi.c bwn/if_bwn.c ipw/if_ipw.c malo/if_malo.c ral/rt2560.c ral/rt2860.c ral/rt2661.c wi/if_wi.c usb/wlan/if_ural.c From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 21 19:47:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04ACF84D; Sat, 21 Jun 2014 19:47:38 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABA582DCA; Sat, 21 Jun 2014 19:47:37 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id q107so4524996qgd.5 for ; Sat, 21 Jun 2014 12:47:36 -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=HPQkUP7KpEh1p5PRsqZGmBsJDo22qlH4P4WlywsKolc=; b=q7E1WJNTXt0PMy2Fx87ahk3bN7a1je1RC5jWIE2FyXrh6XaF7p5HwiYxy0d/0hOPTO OP/TPos4GVf3s8l97s6hzVc5LF7XdZsPy0NUCwkTROXm2MG3SilmPJfnO+kYQyLdZTRs falux7AKMCN6KENHASBnmp/SGuZsbH/qq7ASteLVbaWPfieSzFeqlVP1lIhppPA0ny3o gq3v70G3HBxxJII0k4dNdRKpwSjhWF55f/aXkt0T5PCdJOYOPZGx7OUoewS64P/UPpGV IjLwI9SrI00aRMfc4nuwqTCjSzBXDnDxK+q0XKKsj516x6hHSJWP7gYBuxwtr4nMC+++ pY9Q== MIME-Version: 1.0 X-Received: by 10.140.35.212 with SMTP id n78mr16356606qgn.87.1403380056836; Sat, 21 Jun 2014 12:47:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Sat, 21 Jun 2014 12:47:36 -0700 (PDT) In-Reply-To: <1403366123.39384.10.camel@bruno> References: <1403366123.39384.10.camel@bruno> Date: Sat, 21 Jun 2014 12:47:36 -0700 X-Google-Sender-Auth: r763KbE8TbTHelf03p-oCNbaOuw Message-ID: Subject: Re: wireless mcast updates, ic->ic_update_mcast From: Adrian Chadd To: Sean Bruno Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2014 19:47:38 -0000 Well, it depends on what the hardware may want or desire to function correctly. I've no idea what theose chips require for multicast behaviour. -a On 21 June 2014 08:55, Sean Bruno wrote: > My T61 has a wpi(4) card in it. I noted that the console message "needs > muticast update" is emitted as it doesn't implement the required > function in its code and uses the default of the net80211 stack. I > haven't noted any issues, but I took a journey through some of the > wireless drivers to see what the status of implementation was. It seems > most of the drivers stub out the required function to get rid of the > warning. > > I perceive that with 6 exceptions, most of our wireless adapters don't > have an implementation, or worse, they implement a stub to squash the > warning. Shouldn't these stub functions be removed? Perhaps wrapp the > net80211 default behavior in bootverbose? > > -- implemented ic_update_mcast() > ath/if_ath.c -- implemented and working > usb/wlan/if_zyd.c -- implemented and working > usb/wlan/if_wi.c -- implemented and working > > -- sets a flag to default o/s behvavior? > mwl/if_mlw.c -- function coded out, most code if 0'd out > usb/wlan/if_upgt.c -- looks to default to whatever the o/s can do. > usr/wlan/if_run.c -- looks to default to whatever the o/s can do > > -- stubbed out function to squash warning (bug?) > iwn/if_iwn.c -- stubbed out in if_iwn to remove default error > usb/wlan/if_rum.c -- stubbed out to remove default error > usb/wlan/if_urtwn.c -- stubbed out to remove default error > usb/wlan/if_urtw.c -- stubbed out to remove default error > usr/wlan/if_uath.c -- stubbed out to remove default error > usb/wlan/if_rsu.c -- stubbed out to remove default error > wtap/if_wtap.c -- stubbed out to remove default error > > -- undefined, emits error correctly > wpi/if_wpi.c > bwi/if_bwi.c > bwn/if_bwn.c > ipw/if_ipw.c > malo/if_malo.c > ral/rt2560.c > ral/rt2860.c > ral/rt2661.c > wi/if_wi.c > usb/wlan/if_ural.c > > _______________________________________________ > 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 Mon Jun 23 07:18:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45D9B6CE for ; Mon, 23 Jun 2014 07:18:47 +0000 (UTC) Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07D2525FE for ; Mon, 23 Jun 2014 07:18:46 +0000 (UTC) Received: by mail-vc0-f172.google.com with SMTP id hy10so5518563vcb.17 for ; Mon, 23 Jun 2014 00:18:46 -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=IZujHUp7HWB2h/hwgOqq8dsCc2hU45GNHusEIHi1t2U=; b=smYZnnIe74AYcv9T8AQdm+d1wF9GbwBvfEXP361i4CinPfX3AzAHzm3oeyXScmalyk GwxriGmxPSkcHSZIMmjwqRoZrPpF0F6Gv4XlNIHMihn0Vlxf9Pbd79GuvGzP8zh2wyn7 W6OaAX/+7xw7RxMRmhHI7gEmwjZho0VKWk4bBX8tvF6xJs+CgdT9tvffRp4vZqW9UJe5 SGg3S3UlmrIetx2mlR5lRc/rurxWWhVj2ANmvntMBUUnuRUZvUo8SSBYvUkStOZCrVC1 MOQXGtAzA5YNs7/dbq2Zt52LifU3vL0Eb/3AuIscseswAP39G0fD/ovfqiBQ76D4I3bc hTbA== MIME-Version: 1.0 X-Received: by 10.221.56.132 with SMTP id wc4mr124318vcb.38.1403507925919; Mon, 23 Jun 2014 00:18:45 -0700 (PDT) Received: by 10.52.10.3 with HTTP; Mon, 23 Jun 2014 00:18:45 -0700 (PDT) Received: by 10.52.10.3 with HTTP; Mon, 23 Jun 2014 00:18:45 -0700 (PDT) Date: Mon, 23 Jun 2014 10:18:45 +0300 Message-ID: Subject: Re: Contents of freebsd-wireless digest. From: Siyar Erdemli To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 07:18:47 -0000 From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 23 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AADA37D7 for ; Mon, 23 Jun 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D1BB2961 for ; Mon, 23 Jun 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5N80Msm089356 for ; Mon, 23 Jun 2014 09:00:22 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201406230800.s5N80Msm089356@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 23 Jun 2014 08:00:22 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 23 12:02:07 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D53F3D0 for ; Mon, 23 Jun 2014 12:02:07 +0000 (UTC) Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 967E92F85 for ; Mon, 23 Jun 2014 12:02:07 +0000 (UTC) Received: by mail-vc0-f174.google.com with SMTP id hy4so5805193vcb.19 for ; Mon, 23 Jun 2014 05:02:06 -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=Dao6kg4Ub6l9HPkApIockckaDz4PCFp5WxjQVTJ0TuM=; b=zdRn/wx3wheg72QbWG9Nlh2O0nWu/ht7EKVFVMt4il/Ea0Bqfl86cm7OCzcT1Ux1OQ vrFfd7OQ369dee2u92xUtilcNnJcpbPEKMxdR1ugw3AO/V6BnLEWZnD9IdRI98a3//pk 3dLs3QS9q5Z9hjVWfdO71guyeo4hB6O51MNjnsoilt8PAT0DkVIinxXo3V3M2pixT9x4 zUtTBhtv+Gw2xMeGPgFQ0VWuGHTSqLEHvUE/mizZgEohRf3yDhRGs48PMqq3mlnf5zbc rPYlSlLEs7Ch7LFXYI5gp/hTIo5QRY1Ex1w5fxx361aU1fpArgRcZSiwgECePxEDYSFE k6tA== MIME-Version: 1.0 X-Received: by 10.58.56.102 with SMTP id z6mr18398369vep.7.1403524926361; Mon, 23 Jun 2014 05:02:06 -0700 (PDT) Received: by 10.52.10.3 with HTTP; Mon, 23 Jun 2014 05:02:06 -0700 (PDT) Received: by 10.52.10.3 with HTTP; Mon, 23 Jun 2014 05:02:06 -0700 (PDT) Date: Mon, 23 Jun 2014 15:02:06 +0300 Message-ID: Subject: Re: Contents of freebsd-wireless digest..." From: Siyar Erdemli To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 12:02:07 -0000 Re: Contents of freebsd-wireless digest..." From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 24 01:22:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0BC0D66E; Tue, 24 Jun 2014 01:22:08 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFCD72BEB; Tue, 24 Jun 2014 01:22:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=leCxYSSj8R8mCexLkhQpIDxAYIdrSlGNxoL7nQ2eeek=; b=pEIOe47A/Bw6JNMrafhhAkTQWjFkmmGWUfpu2CoFqtEH21SRifJy6xNY8j/Kj3rdUDzojKu035gMc2HtWw7UY1S8SUdHKDFe6HVFOkTxghI1vZyyeVstkddT2qWFLYm6E2Inl46FUz7ww/4NSFy66dMgRtHETUP1dNPWv/mkSy8=; Received: from [182.0.211.115] (port=19262 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WzFQy-000pE2-CH; Mon, 23 Jun 2014 19:22:05 -0600 Date: Tue, 24 Jun 2014 09:21:56 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140624092156.7cad84e8@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> <20140523191329.62027b64@X220.alogt.com> <20140523235953.7f8dbb4d@X220.alogt.com> <20140608092142.746a09db@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 01:22:08 -0000 Hi Adrian, On Sat, 7 Jun 2014 21:41:10 -0400 Adrian Chadd wrote: > Can you pleease chase this up with me next week? We need to find/fix > these issues. I'm not running v6 at home; I can easily flip that on > when I get home next week. > sorry for being late. I was travelling myself until yesterday. I updated my machine over the weekend to FreeBSD X220.alogt.com 10.0-STABLE FreeBSD 10.0-STABLE #38 r267699: Sun Jun 22 16:32:07 WITA 2014 erich@X220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 I started it only a single time with IPV6 enabled and the machine crashed again. It looked to me that it was the same location but I did not verify it. I run the machine since then with IPV4 only and did not have any trouble. Maybe a word to the timezone. It seems that we are 12h apart. So, early morning and early evening would be the best pairing for us. Erich > THanks, > > > -a > > > On 7 June 2014 21:21, Erich Dollansky > wrote: > > Hi Adrian, > > > > On Fri, 23 May 2014 09:01:36 -0700 > > Adrian Chadd wrote: > > > >> a photo will be fine. :-) > >> > > did the photos help? > > > > I did not have any problems anymore since I deactivated IPV6. > > > > Erich > >> > >> -a > >> > >> > >> On 23 May 2014 08:59, Erich Dollansky > >> wrote: > >> > Hi, > >> > > >> > On Fri, 23 May 2014 08:36:31 -0700 > >> > Adrian Chadd wrote: > >> > > >> >> Ok, it's a null pointer dereference (based on the address you > >> >> posted) and it's ipv6 related. That's .. odd. > >> >> > >> >> Can you provide a backtrace from the crash? > >> >> > >> > I can try tomorrow. Am I right that I can only take photos of the > >> > screen at this point of the boot process? > >> > > >> > Erich > >> >> > >> >> > >> >> -a > >> >> > >> >> > >> >> On 23 May 2014 04:13, Erich Dollansky > >> >> wrote: > >> >> > Hi, > >> >> > > >> >> > On Tue, 8 Apr 2014 20:40:01 -0700 > >> >> > Adrian Chadd wrote: > >> >> > > >> >> >> I'm not sure. I'd really like to see what the story is with > >> >> >> coexistence somehow. > >> >> >> > >> >> > I did some more investigations and came to the result that iwn > >> >> > crashes in 'in6_ifattach_linklocal'. > >> >> > > >> >> > When I disable ipv6, it all works fine. I did several reboots > >> >> > without a problem. > >> >> > > >> >> > To make this a bit more complicated, if I use only em0, the > >> >> > machine starts normal. When I use iwn0 alone or together with > >> >> > lagg0 and em0, the machine crashes during the boot process. > >> >> > The crashes only happen when IPV6 is enabled in rc.conf. > >> >> > > >> >> > Erich > >> > > > From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 24 15:19:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D4A4651; Tue, 24 Jun 2014 15:19:49 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6D115255B; Tue, 24 Jun 2014 15:19:49 +0000 (UTC) Received: from [10.12.76.47] (unknown [69.164.56.1]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 4669A1936DE; Tue, 24 Jun 2014 15:19:48 +0000 (UTC) Subject: Re: wireless mcast updates, ic->ic_update_mcast From: Sean Bruno Reply-To: sbruno@freebsd.org To: Adrian Chadd In-Reply-To: References: <1403366123.39384.10.camel@bruno> Content-Type: text/plain; charset="us-ascii" Date: Tue, 24 Jun 2014 08:19:47 -0700 Message-ID: <1403623187.7781.6.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 15:19:49 -0000 On Sat, 2014-06-21 at 12:47 -0700, Adrian Chadd wrote: > Well, it depends on what the hardware may want or desire to function > correctly. I've no idea what theose chips require for multicast > behaviour. > > > -a > > I think that was kind of my point of bringing this up. Only a handful of cards really implement the appropriate code. Most of the rest, implement stub functions that hide a console print message indicating missing functionality. I propose nuking most of these stub functions and wrapping the console printf in a bootverbose. sean > On 21 June 2014 08:55, Sean Bruno wrote: > > My T61 has a wpi(4) card in it. I noted that the console message "needs > > muticast update" is emitted as it doesn't implement the required > > function in its code and uses the default of the net80211 stack. I > > haven't noted any issues, but I took a journey through some of the > > wireless drivers to see what the status of implementation was. It seems > > most of the drivers stub out the required function to get rid of the > > warning. > > > > I perceive that with 6 exceptions, most of our wireless adapters don't > > have an implementation, or worse, they implement a stub to squash the > > warning. Shouldn't these stub functions be removed? Perhaps wrapp the > > net80211 default behavior in bootverbose? > > > > -- implemented ic_update_mcast() > > ath/if_ath.c -- implemented and working > > usb/wlan/if_zyd.c -- implemented and working > > usb/wlan/if_wi.c -- implemented and working > > > > -- sets a flag to default o/s behvavior? > > mwl/if_mlw.c -- function coded out, most code if 0'd out > > usb/wlan/if_upgt.c -- looks to default to whatever the o/s can do. > > usr/wlan/if_run.c -- looks to default to whatever the o/s can do > > > > -- stubbed out function to squash warning (bug?) > > iwn/if_iwn.c -- stubbed out in if_iwn to remove default error > > usb/wlan/if_rum.c -- stubbed out to remove default error > > usb/wlan/if_urtwn.c -- stubbed out to remove default error > > usb/wlan/if_urtw.c -- stubbed out to remove default error > > usr/wlan/if_uath.c -- stubbed out to remove default error > > usb/wlan/if_rsu.c -- stubbed out to remove default error > > wtap/if_wtap.c -- stubbed out to remove default error > > > > -- undefined, emits error correctly > > wpi/if_wpi.c > > bwi/if_bwi.c > > bwn/if_bwn.c > > ipw/if_ipw.c > > malo/if_malo.c > > ral/rt2560.c > > ral/rt2860.c > > ral/rt2661.c > > wi/if_wi.c > > usb/wlan/if_ural.c > > > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 24 18:01:31 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 54BA3313; Tue, 24 Jun 2014 18:01:31 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0389C2761; Tue, 24 Jun 2014 18:01:30 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s5OI1T3L087101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 24 Jun 2014 12:01:29 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s5OI1TdO087098; Tue, 24 Jun 2014 12:01:29 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 24 Jun 2014 12:01:29 -0600 (MDT) From: Warren Block To: sbruno@freebsd.org Subject: Re: wireless mcast updates, ic->ic_update_mcast In-Reply-To: <1403623187.7781.6.camel@bruno> Message-ID: References: <1403366123.39384.10.camel@bruno> <1403623187.7781.6.camel@bruno> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 24 Jun 2014 12:01:29 -0600 (MDT) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 18:01:31 -0000 On Tue, 24 Jun 2014, Sean Bruno wrote: > On Sat, 2014-06-21 at 12:47 -0700, Adrian Chadd wrote: >> Well, it depends on what the hardware may want or desire to function >> correctly. I've no idea what theose chips require for multicast >> behaviour. > > I think that was kind of my point of bringing this up. Only a handful > of cards really implement the appropriate code. Most of the rest, > implement stub functions that hide a console print message indicating > missing functionality. > > I propose nuking most of these stub functions and wrapping the console > printf in a bootverbose. FWIW, I agree. That little error-that's-not-an-error is what new users see, and it obviously must be the problem. So not only is it not helping, it often distracts from real problems. From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 24 18:50:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 646C713B; Tue, 24 Jun 2014 18:50:58 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13D202BCA; Tue, 24 Jun 2014 18:50:58 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id w7so710783qcr.7 for ; Tue, 24 Jun 2014 11:50: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=ZpUp6InR4WztmmrH5cPce3bEL3tZrWd5P3yrB+FCmoU=; b=b3xHIzEpbrLu40edbfU9dMezz+V5nDACbES/YP/iDr2G/dw72fw58841qW2Lj5wa1n La/G6RUa+lBM1vNtY2ajuJTgdvHjY8fA2cm3c9PfpY+ciamP8GXPT2WU+/Xkg3Iu4UyX neKu7Zb/iIk5RgJfYWebPndXwZlg1uBAE3QkMzk/04ySibHybVuBEAzR0Dl2bMT71GYR wQyJ6n/uZTiII6LWpgtl/yVNstSYfq1+GvK2Wz9v3UTFXFdTCivbjNgRPZJ1J3hgn0T3 7q5mDj+t+0KsUXx7iJPCqUU+Vir4Rs5ZbChs4fodFiVQQQvDyfOD7tVamB7w/Of2IJhb ipbQ== MIME-Version: 1.0 X-Received: by 10.224.130.201 with SMTP id u9mr4729489qas.98.1403635857125; Tue, 24 Jun 2014 11:50:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.43.134 with HTTP; Tue, 24 Jun 2014 11:50:57 -0700 (PDT) In-Reply-To: References: <1403366123.39384.10.camel@bruno> <1403623187.7781.6.camel@bruno> Date: Tue, 24 Jun 2014 11:50:57 -0700 X-Google-Sender-Auth: rXh2KvPiu_sgE_7fN2KQlcEbf0E Message-ID: Subject: Re: wireless mcast updates, ic->ic_update_mcast From: Adrian Chadd To: Warren Block Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 18:50:58 -0000 Cool. Wrap it up in bootverbose. Hm, or what about a print_once kind of thing? As far as I can briefly tell, the drivers -should- work with multicast as long as they're treating it like broadcast traffic and not requiring that you program a multicast filter for specific link-local things. The problem is that noone has gone through and verified that is indeed the case. -a On 24 June 2014 11:01, Warren Block wrote: > On Tue, 24 Jun 2014, Sean Bruno wrote: > >> On Sat, 2014-06-21 at 12:47 -0700, Adrian Chadd wrote: >>> >>> Well, it depends on what the hardware may want or desire to function >>> correctly. I've no idea what theose chips require for multicast >>> behaviour. >> >> >> I think that was kind of my point of bringing this up. Only a handful >> of cards really implement the appropriate code. Most of the rest, >> implement stub functions that hide a console print message indicating >> missing functionality. >> >> I propose nuking most of these stub functions and wrapping the console >> printf in a bootverbose. > > > FWIW, I agree. That little error-that's-not-an-error is what new users see, > and it obviously must be the problem. So not only is it not > helping, it often distracts from real problems. From owner-freebsd-wireless@FreeBSD.ORG Fri Jun 27 04:46:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6CC31930 for ; Fri, 27 Jun 2014 04:46:14 +0000 (UTC) Received: from nm25-vm2.access.bullet.mail.bf1.yahoo.com (nm25-vm2.access.bullet.mail.bf1.yahoo.com [216.109.115.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 176962E3C for ; Fri, 27 Jun 2014 04:46:14 +0000 (UTC) Received: from [66.196.81.157] by nm25.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jun 2014 04:39:25 -0000 Received: from [98.139.221.156] by tm3.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jun 2014 04:39:25 -0000 Received: from [127.0.0.1] by smtp116.sbc.mail.bf1.yahoo.com with NNFMP; 27 Jun 2014 04:39:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1403843965; bh=RyOQt0xp7lvW9IE+S91v6q9dfNq8fAauIWdBW4/RUrU=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject; b=WbiRr3Oiu59acTvu9CaGAY9GvKeCSWW86nF5eLHQDvLCX5HO0mnaZK/cXvV75nRqcOe6W4A5aK5n3sBD+REXMCjLAFEGK+vlM+ocSS/r5VYr1pUy4D4byYRKfPhx1O8BxBNYifnrZ1eo+qYnPJzgdSYVocRM563ybDInyuKKly4= X-Yahoo-Newman-Id: 227363.20856.bm@smtp116.sbc.mail.bf1.yahoo.com Message-ID: <227363.20856.bm@smtp116.sbc.mail.bf1.yahoo.com> Date: Fri, 27 Jun 2014 04:39:25 +0000 (UTC) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 3bM09cgVM1menBickuQ8klYCs6tzWmHw7L7vBLSOFuBzsQT ICXURyFMuKjHt1B0w57Gs8UFQaix6HRhmXxlgDaeRVht2RIiUwAGsoFTQxwi Wztqg6xvdLIMPnjRubMME5xPYc_7qxrRpDUwKOyQstHPzpvMw5op0JaIRlbl KGa6qviuwQXHAM9PFPocirZo2Bl.wOPymbeiAJJ1P75xW7B0DtHBOWz12aKy tzPHSQmZ4caRHZNT7vmTH2lm4ZSMjBYug8Qc5YgZa5Xs3w99Ic3morbZH0fy 3vutsv1vyjTjcpBArtwDTCqo1w_q4vw2yaFwv1YDZh4QCAEd7Doi5C73b5Wr Ykde59tGDu6a5LHO7R9U8FRcUqJy4SmQbIyIi5PZbPNA9HaQ0GXKLid0xgaK hAYmkQpvv5mIWIpE3GUc_Bpppu3_OLQIUeBIh4yaNCEZh8CCNUEj1UDOhzJd CRsRxCsP1adnpvGCVGHvOcOedR8wEGEnJrKOEzgS3kQTuDHTh89PCXaaukHo FbSuSWh2.3hYZiGHJswHfNdLNx8puZOx5v0SuUZILQdYiasMZUnFq_EyZwzv 0_H_8MleJynbIKcJ0.v6XNd5qxY0E8jwSHjarhwU.vhWqBHOtk5ZR3P8yxhE aSVccwkY- X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@96.28.178.143 with plain [98.139.221.42]) by smtp116.sbc.mail.bf1.yahoo.com with SMTP; 27 Jun 2014 04:39:25 +0000 UTC From: "Thomas Mueller" To: freebsd-wireless@freebsd.org Subject: rsu wireless driver crapshoot Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2014 04:46:14 -0000 My Internet connection on this computer is very iffy at best, not running as I type this. Motherboard is MSI Z77 MPOWER. Ethernet is Realtek (re): good with NetBSD, Linux and Haiku, (Free,Open and DragonFly)BSD bug out. Only Internet connection for FreeBSD is Hiro H50191 USB-stick wireless adapter, chipset RTL8191SU, device rsu. Sometimes it connects. Running ifconfig (by itself), I get, whether connection is working ot not, lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 rsu0: flags=8843 metric 0 mtu 2290 options=1 ether 00:13:33:a2:86:f0 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:13:33:a2:86:f0 inet 192.168.0.102 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid Maclura_pomifera channel 8 (2447 MHz 11g) bssid a0:f3:c1:f9:39:7a country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 0 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS roaming MANUAL Looks good, but running host on a valid domain, such as host bluegrass.net gives me ;; connection timed out; no servers could be reached Even when the connection is successful, it can quit any time without warning, and only way I can tell is by trying to reach an internet domain. I feel like Cinderella, but she had the advantage of knowing that her coach would turn back to a pumpkin at exactly midnight. Internet connectivity problems are the same whether I run FreeBSD-current or 10.0-STABLE. FreeBSD < 10.0 offers no internet connectivity at all. Now I have to save this message, shutdown and boot into NetBSD to send it. I also use NetBSD to update src, ports and doc trees with subversion. Tom From owner-freebsd-wireless@FreeBSD.ORG Fri Jun 27 05:39:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1F8F8A2; Fri, 27 Jun 2014 05:39:24 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A695A2276; Fri, 27 Jun 2014 05:39:24 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A2A1B1FE028; Fri, 27 Jun 2014 07:39:22 +0200 (CEST) Message-ID: <53AD039F.2030806@selasky.org> Date: Fri, 27 Jun 2014 07:39:43 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-wireless@freebsd.org Subject: Re: rsu wireless driver crapshoot References: <227363.20856.bm@smtp116.sbc.mail.bf1.yahoo.com> In-Reply-To: <227363.20856.bm@smtp116.sbc.mail.bf1.yahoo.com> 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.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2014 05:39:25 -0000 On 06/27/14 06:39, Thomas Mueller wrote: > My Internet connection on this computer is very iffy at best, not running as I type this. > > Motherboard is MSI Z77 MPOWER. > > Ethernet is Realtek (re): good with NetBSD, Linux and Haiku, (Free,Open and DragonFly)BSD bug out. > > Only Internet connection for FreeBSD is Hiro H50191 USB-stick wireless adapter, chipset RTL8191SU, device rsu. > > Sometimes it connects. Running ifconfig (by itself), I get, whether connection is working ot not, > Hi, You can help us by sending an e-mail to the manufacturer to provide the programmers guide for this device so that we can make a proper driver. I understand your device does not work that great under FreeBSD. It is also possible for you look into the code and try and modify things, watch debug prints and so on and propose a patch. It is not that difficult. Another option is to buy a Raalink based WLAN dongle. See ural/run/rum drivers. They work much more reliably! Thank you! --HPS From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 30 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64200A02 for ; Mon, 30 Jun 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 429EC294B for ; Mon, 30 Jun 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5U80MDU006165 for ; Mon, 30 Jun 2014 09:00:22 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201406300800.s5U80MDU006165@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 30 Jun 2014 08:00:22 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 2 06:45:33 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD94DB35 for ; Wed, 2 Jul 2014 06:45:33 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4D172E58 for ; Wed, 2 Jul 2014 06:45:33 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s626jX4W004467 for ; Wed, 2 Jul 2014 07:45:33 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 184692] [iwi] [panic] kernel panic in iwi0 driver Date: Wed, 02 Jul 2014 06:45:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hsn@sendmail.cz X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 06:45:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184692 hsn@sendmail.cz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |DUPLICATE --- Comment #3 from hsn@sendmail.cz --- *** This bug has been marked as a duplicate of bug 185025 *** -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 2 06:45:33 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA637B36 for ; Wed, 2 Jul 2014 06:45:33 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D214A2E59 for ; Wed, 2 Jul 2014 06:45:33 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s626jXXV004471 for ; Wed, 2 Jul 2014 07:45:33 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 185025] [iwi] [panic] iwi driver panic on 10.0rc2 Date: Wed, 02 Jul 2014 06:45:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hsn@sendmail.cz X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 06:45:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185025 --- Comment #2 from hsn@sendmail.cz --- *** Bug 184692 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 5 22:52:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1EA539F for ; Sat, 5 Jul 2014 22:52:18 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8372C2695 for ; Sat, 5 Jul 2014 22:52:18 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id w7so2478576qcr.2 for ; Sat, 05 Jul 2014 15:52:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=B2q/YZNnAlCtOjnYjrxV4M02YfSvKI+Uy2ts8TY/xzw=; b=EGh4SliaRws0PyrleHs7/v8rJeSnUFnD1ZY7JHzqmZx9KvH680XrH0Mg+T0W0KHzeT M3Dl0Meqg9JzOgKSnK/hTZ5qd1vZZGbHWHg1yWfZB3iWhX9KPoDt0gBacCj523KLeije wo4c+lRlfMApysCLEe96Pg8EvWexgQxAW18DnoZhGI0RKHS4gRM59yzZRW/gD58sP1zI uSFzCUHEwW5G8gKSpU2WGItx5DR9XJjAEHjX4ST42Y2qcvtr4AVpbfO5swZS1e3aGMwa +D+FIxftTeDhhlSLQikFATnu968s9eOTwXNriNgFgcNfEq/rqSe9Zvq+BcJ4i6Yvfq6d 7YOA== MIME-Version: 1.0 X-Received: by 10.224.128.193 with SMTP id l1mr31799512qas.91.1404600737433; Sat, 05 Jul 2014 15:52:17 -0700 (PDT) Received: by 10.96.13.133 with HTTP; Sat, 5 Jul 2014 15:52:17 -0700 (PDT) In-Reply-To: References: Date: Sat, 5 Jul 2014 23:52:17 +0100 Message-ID: Subject: Fwd: Best wireless card for building 802.11n AP From: krad To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2014 22:52:18 -0000 Hi I have just got a DN2820FYKH to build an xbmc media center player. All that works fine, but it got me thinking that it would be a cool little box to replace my bsd router vm, which would allow me not to run my main machine 24x7. Ideally the DN2820FYKH would act as my main router, with all the related services and it would be my wireless AP as well. I have got AP working under linux fine, but I cant get freebsd to see the wifi card (i dont think its supported in current yet). Therefore I have two options, one wait until it is supported, or two, replace the mini pcie card for another supported 802.11n card. Last time I looked at running an freebsd AP over 802.11n, it was all a bit new and flaky. I was wondering if anyone can recommend any cards that are known to work well as a 802.11n AP, along with any other tips with regard to setting up 802.11n APs under freebsd. I have tried the latest freebsd-11 memstick and that didnt work, even after kldloading lots of iw type modules I think I have a spare ar9287 that may work in the box. Is this a reliable chipset for freebsd? k From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 5 23:05:02 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A01668E for ; Sat, 5 Jul 2014 23:05:02 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF88D275A for ; Sat, 5 Jul 2014 23:05:01 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id c9so2558537qcz.14 for ; Sat, 05 Jul 2014 16:05:01 -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=FPWUGYREmqaoPdYWqIEEHuKDQw6mVM6HfHI5w+DJTmE=; b=BLU9iEJ0wLVaekSNPeRUSlfGDRBOeEnBNbUjEeWM7z5+Hjmi2jLUxApKLkaffvamtQ lrnjY+doLOJNIunvwLDOeu7dHUxles7RzIUImrebcRrqIgZEb80n19doxgZW1sbaVTmr vCSICPJXd/P2mNo4E1eBtNVLtiF31GzrzDlAi5dsXVPvDRVtXgTRcyW3UUapWZdfuIP3 rK5gM3U550/qdCyY0WnYp6Tc1B16zKZaoZrJuiMNlQHfPr6FmLumQkrq1Rp6HK+JlAHL e0CbErMY71lpSAZPE6+agLGCcfo5fFLyRndDEhZb7Oiv1cIdeXv3Bikzc3GqY4v0t+pL hJpQ== MIME-Version: 1.0 X-Received: by 10.140.34.195 with SMTP id l61mr30515391qgl.87.1404601500871; Sat, 05 Jul 2014 16:05:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Sat, 5 Jul 2014 16:05:00 -0700 (PDT) In-Reply-To: References: Date: Sat, 5 Jul 2014 16:05:00 -0700 X-Google-Sender-Auth: VxVYc73gDsgojr7Up76jQd6HtHs Message-ID: Subject: Re: Best wireless card for building 802.11n AP From: Adrian Chadd To: krad Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2014 23:05:02 -0000 hi, the ar9287 in AP mode is supported fine on freebsd-11. -a On 5 July 2014 15:52, krad wrote: > Hi I have just got a DN2820FYKH to build an xbmc media center player. All > that works fine, but it got me thinking that it would be a cool little box > to replace my bsd router vm, which would allow me not to run my main > machine 24x7. Ideally the DN2820FYKH would act as my main router, with > all the related services and it would be my wireless AP as well. I have got > AP working under linux fine, but I cant get freebsd to see the wifi card (i > dont think its supported in current yet). Therefore I have two options, one > wait until it is supported, or two, replace the mini pcie card for another > supported 802.11n card. Last time I looked at running an freebsd AP > over 802.11n, it was all a bit new and flaky. I was wondering if > anyone can recommend any cards that are known to work well as a 802.11n > AP, along with any other tips with regard to setting up 802.11n APs under > freebsd. > > I have tried the latest freebsd-11 memstick and that didnt work, even after > kldloading lots of iw type modules > > I think I have a spare ar9287 that may work in the box. Is this a reliable > chipset for freebsd? > > k > _______________________________________________ > 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 Mon Jul 7 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B6A0FA6 for ; Mon, 7 Jul 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D3E525CC for ; Mon, 7 Jul 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6780LjL032423 for ; Mon, 7 Jul 2014 09:00:21 +0100 (BST) (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201407070800.s6780LjL032423@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 07 Jul 2014 08:00:21 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 12:41:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D1645AA for ; Mon, 7 Jul 2014 12:41:09 +0000 (UTC) Received: from erelay5.ox.registrar-servers.com (erelay5.ox.registrar-servers.com [192.64.117.65]) by mx1.freebsd.org (Postfix) with ESMTP id 075032106 for ; Mon, 7 Jul 2014 12:41:08 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id A46F72204E1C for ; Mon, 7 Jul 2014 12:41:07 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pYer5SKcO_gU for ; Mon, 7 Jul 2014 08:41:06 -0400 (EDT) Received: from imap10.ox.privateemail.com (imap10.ox.privateemail.com [192.64.116.221]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id A39DD2204E10 for ; Mon, 7 Jul 2014 08:41:06 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 6FE272400C7 for ; Mon, 7 Jul 2014 08:41:06 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id h68mCI7pKsbn for ; Mon, 7 Jul 2014 08:41:06 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 8E3602400C2 for ; Mon, 7 Jul 2014 08:41:05 -0400 (EDT) Date: Mon, 7 Jul 2014 14:40:56 +0200 From: Carlos Jacobo Puga Medina To: freebsd-wireless@freebsd.org Subject: TP-LINK TL-WN821N Message-Id: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 12:41:09 -0000 Hi people, Does anyone still work to porting the otus driver from OpenBSD? https://github.com/erikarn/otus/tree/master/otus Regards, -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 16:25:36 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F02B36F3; Mon, 7 Jul 2014 16:25:35 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0E2A2694; Mon, 7 Jul 2014 16:25:35 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id k15so3846903qaq.30 for ; Mon, 07 Jul 2014 09:25:34 -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=9IrPuMrMy+xqvMnhTZ+RvMG3GTpVjYfrG+cBjkSpsPc=; b=ATSgpl9CAXdalH3ZZiRR9+YbOp/lN+vxPL7oflmM4HBcnhFaXFzVQOPzDiQnRbfAAx 9Z5L/71cHbTHYGihHjweCvvOyWi0e6zpqhrsmmlDGMm20T2bCEUvf9OmhhMFMDvVM0n/ A/MiK8dSoECxS/xzGOqh5hHumUmnPZcZkikeUYxHGCiTLWTEDnQg9SZaVDZJG0fH8Zjo 4IpuEmpm/dDzw38GmkOZzkPElnabQMPPVpyAt1d3b4mmXAFj6lx+Wq+lDFmp1XpTX6+v hKVC/1y8elhdfhg6YYLKmcLImDlQrjHoRtkEER69cCwVGMmfcNb3IVHV8AnpSaJ/g7XG kPVA== MIME-Version: 1.0 X-Received: by 10.224.171.197 with SMTP id i5mr4892844qaz.55.1404750334800; Mon, 07 Jul 2014 09:25:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 09:25:34 -0700 (PDT) In-Reply-To: <20140707142538.GA43661@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> Date: Mon, 7 Jul 2014 09:25:34 -0700 X-Google-Sender-Auth: kOwey5S_-7DboajiEihuCL2Wk9Q Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 16:25:36 -0000 hi, That call is returning ENOMEM. I'm not sure why. It allocated an mbuf fine, but it couldn't allocate the DMA map. What's the output of "vmstat -z" ? I wonder if it's failing an allocation. -a On 7 July 2014 07:25, John Hay wrote: > Hi Guys, > > I'm further with getting my stuff working on the CAMBRIA xscale boards, > but now see this > > ath1: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > error when trying to configure a second or third atheros board. Below > is the script run with -x with its output. The same is working fine > on an Avila board. The Avila has 64M RAM and the CAMBRIA 128M. The > userlevel code is the same for both and in trying to see if it is > something missing in the kernel config, I have made a common kernel > config file with all the common AVILA and CAMBRIA configs and then > included that in a new AVILA and CAMBRIA config file. That gave the > same result. The output is from a 2 week old -current/head. > > ############################## > ~ # uname -a > FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r267954M: Fri Jun 27 14:49:04 SAST 2014 jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/SMALL-CAMBRIA arm > ~ # /root/do-wlans > + crflags='wlanmode adhoc' > + dbgval=0x20000500c > + ifconfig wlan0 create wlandev ath0 wlanmode adhoc > wlan0: Ethernet address: 00:80:48:4f:24:ea > + ifconfig wlan0 inet 10.0.1.1/24 channel 36 ssid ptabb bssid 05:05:ca:fe:ba:be > + sysctl dev.ath.1.debug=0x20000500c > dev.ath.1.debug: 0 -> 8589955084 > + ifconfig wlan1 create wlandev ath1 wlanmode adhoc > wlan1: Ethernet address: 00:80:48:4f:24:da > + ifconfig wlan1 inet 10.0.2.1/24 channel 40 ssid ptabb bssid 05:06:ca:fe:ba:be > ath1: ath_init: if_flags 0x8803 > ath1: ath_stop_locked: invalid 0 if_flags 0x8803 > ath1: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > ath1: ath_legacy_startrecv: ath_rxbuf_init failed 12 > ath1: unable to start recv logic > + sysctl dev.ath.1.debug=0 > dev.ath.1.debug: 8589955084 -> 0 > + sysctl dev.ath.2.debug=0x20000500c > dev.ath.2.debug: 0 -> 8589955084 > + ifconfig wlan2 create wlandev ath2 wlanmode adhoc > wlan2: Ethernet address: 00:21:a4:32:38:c2 > + ifconfig wlan2 inet 10.0.3.1/24 channel 1 ssid ptabb bssid 05:07:ca:fe:ba:be > ath2: ath_init: if_flags 0x8803 > ath2: ath_stop_locked: invalid 0 if_flags 0x8803 > ath2: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > ath2: ath_legacy_startrecv: ath_rxbuf_init failed 12 > ath2: unable to start recv logic > + sysctl dev.ath.2.debug=0 > dev.ath.2.debug: 8589955084 -> 0 > :~ # netstat -m > 182/328/510 mbufs in use (current/cache/total) > 64/192/256/2552 mbuf clusters in use (current/cache/total/max) > 64/189 mbuf+clusters out of packet secondary zone in use (current/cache) > 0/0/0/1275 4k (page size) jumbo clusters in use (current/cache/total/max) > 0/0/0/378 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/212 16k jumbo clusters in use (current/cache/total/max) > 173K/466K/639K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/3/1488 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > ############################## > > CAMBRIA config file > ############################## > include XSCALE-ARM > > ident SMALL-CAMBRIA > > include "../xscale/ixp425/std.ixp435" > > hints "CAMBRIA.hints" > > options IXP4XX_FLASH_SIZE=0x02000000 # stock 2358 comes w/ 32M > > device cambria_fled # Font Panel LED on I2C bus > device cambria_led # 8-LED latch > > device cambria_gpio # GPIO pins on J11 > > env "SMALL-AVILA.env" > ############################## > > AVILA config file > ############################## > include XSCALE-ARM > > ident SMALL-AVILA > > include "../xscale/ixp425/std.ixp425" > > hints "AVILA.hints" # Default places to look for devices. > > device avila_led > > device avila_gpio # GPIO pins on J8 > > env "SMALL-AVILA.env" > ############################## > > XSCALE-ARM config file > ############################## > include "../xscale/ixp425/std.avila" > options XSCALE_CACHE_READ_WRITE_ALLOCATE > makeoptions MODULES_OVERRIDE="" > > makeoptions CONF_CFLAGS=-mcpu=xscale > options HZ=100 > options DEVICE_POLLING > > options ROOTDEVNAME=\"ufs:ad0s1a\" > > options SCHED_4BSD # 4BSD scheduler > options INET # Legacy InterNETworking > options INET6 # InterNETworking > options GEOM_PART_BSD # BSD partition scheme > options GEOM_PART_MBR # MBR partition scheme > options TMPFS # Efficient memory filesystem > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > > options HWPMC_HOOKS > device hwpmc > > > device pci > device uart > > device ixpwdog # watchdog timer > device cfi # flash support > device cfid # flash disk support > device geom_redboot # redboot fis parser > > device iicbus > device iicbb > device iic > > device ixpiic # I2C bus glue > device ds1672 # DS1672 on I2C bus > device ad7418 # AD7418 on I2C bus > > > device gpio > device gpioled > > device ata > device avila_ata # Gateworks CF/IDE support > > device npe # Network Processing Engine > device npe_fw > device firmware > device qmgr # Q Manager (required by npe) > device mii # NB: required by npe > device ether > device bpf > > device loop > device if_bridge > > device md > device random # Entropy device > > device wlan # 802.11 support > options IEEE80211_DEBUG > options IEEE80211_SUPPORT_TDMA > options IEEE80211_SUPPORT_MESH > device wlan_wep # 802.11 WEP support > device wlan_ccmp # 802.11 CCMP support > device wlan_tkip # 802.11 TKIP support > device wlan_xauth > device wlan_acl > > device ath # Atheros NICs > device ath_pci # Atheros pci/cardbus glue > options ATH_DEBUG > options ATH_DIAGAPI > device ath_rate_sample # SampleRate tx rate control for ath > > options AH_DEBUG > options AH_PRIVATE_DIAG > device ath_ar5212 > device ath_rf2413 > device ath_rf2417 > device ath_rf2425 > device ath_rf5111 > device ath_rf5112 > device ath_rf5413 > device ath_ar5416 > options AH_SUPPORT_AR5416 > device ath_ar9160 > device ath_ar9280 > > device usb > options USB_EHCI_BIG_ENDIAN_DESC > device ohci > device ehci > device umass > device scbus # SCSI bus (required for ATA/SCSI) > device da # Direct Access (disks) > device pass # Passthrough device (direct ATA/SCSI access) > > > device gif > device tun > ############################## > > > Regards > > John > -- > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 16:48:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88D2BF02; Mon, 7 Jul 2014 16:48:18 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id D414C28B5; Mon, 7 Jul 2014 16:48:16 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 6FA68B84A; Mon, 7 Jul 2014 18:48:07 +0200 (SAST) Date: Mon, 7 Jul 2014 18:48:07 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140707164807.GA57227@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 16:48:18 -0000 On Mon, Jul 07, 2014 at 09:25:34AM -0700, Adrian Chadd wrote: > hi, > > That call is returning ENOMEM. I'm not sure why. It allocated an mbuf > fine, but it couldn't allocate the DMA map. > > What's the output of "vmstat -z" ? I wonder if it's failing an allocation. :~ # vmstat -z ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 192, 0, 107, 19, 107, 0, 0 UMA Zones: 280, 0, 107, 5, 107, 0, 0 UMA Slabs: 56, 0, 1798, 2, 19024, 0, 0 UMA RCntSlabs: 64, 0, 128, 61, 128, 0, 0 UMA Hash: 128, 0, 11, 20, 12, 0, 0 4 Bucket: 16, 0, 10, 494, 2039, 0, 0 6 Bucket: 24, 0, 0, 0, 0, 0, 0 8 Bucket: 32, 0, 4, 374, 161, 0, 0 12 Bucket: 48, 0, 2, 334, 4, 0, 0 16 Bucket: 64, 0, 16, 299, 924, 17, 0 32 Bucket: 128, 0, 7, 148, 197, 0, 0 64 Bucket: 256, 0, 19, 56, 76, 0, 0 128 Bucket: 512, 0, 15, 17, 49, 0, 0 256 Bucket: 1024, 0, 39, 9, 2671, 996, 0 vmem btag: 28, 0, 4521, 231, 4521, 32, 0 VM OBJECT: 160, 0, 1492, 108, 34553, 0, 0 RADIX NODE: 48, 30324, 2145, 459, 124628, 0, 0 MAP: 152, 0, 3, 75, 3, 0, 0 KMAP ENTRY: 80, 0, 4, 146, 4, 0, 0 MAP ENTRY: 80, 0, 412, 238, 102729, 0, 0 VMSPACE: 1264, 0, 16, 11, 2373, 0, 0 L2 Table: 1024, 0, 106, 65, 23026, 0, 0 L2 Table: 196, 0, 48, 92, 10774, 0, 0 PV ENTRY: 28, 229824, 7771, 3749, 1285591, 0, 0 fakepg: 80, 0, 0, 0, 0, 0, 0 mt_zone: 80, 0, 191, 59, 191, 0, 0 16: 16, 0, 4016, 268, 8966, 0, 0 32: 32, 0, 1946, 196, 36992, 0, 0 64: 64, 0, 3150, 189, 37458, 0, 0 128: 128, 0, 1186, 85, 12522, 0, 0 256: 256, 0, 307, 68, 839, 0, 0 512: 512, 0, 84, 4, 3756, 0, 0 1024: 1024, 0, 53, 15, 4190, 0, 0 2048: 2048, 0, 130, 10, 3500, 0, 0 4096: 4096, 0, 1094, 9, 3455, 0, 0 dma maps: 56, 0, 2004, 84, 2004, 0, 0 dma buffer 32: 32, 0, 0, 0, 0, 0, 0 dma buffer 64: 64, 0, 0, 0, 0, 0, 0 dma buffer 128: 128, 0, 2, 153, 2, 0, 0 dma buffer 256: 256, 0, 0, 0, 0, 0, 0 dma buffer 512: 512, 0, 0, 0, 0, 0, 0 dma buffer 1024: 1024, 0, 0, 0, 0, 0, 0 dma buffer 2048: 2048, 0, 0, 0, 0, 0, 0 dma buffer 4096: 4096, 0, 0, 0, 0, 0, 0 dma coherent 32: 32, 0, 0, 0, 0, 0, 0 dma coherent 64: 64, 0, 0, 0, 0, 0, 0 dma coherent 128: 128, 0, 0, 0, 0, 0, 0 dma coherent 256: 256, 0, 0, 0, 0, 0, 0 dma coherent 512: 512, 0, 0, 0, 0, 0, 0 dma coherent 1024: 1024, 0, 0, 0, 0, 0, 0 dma coherent 2048: 2048, 0, 0, 0, 0, 0, 0 dma coherent 4096: 4096, 0, 0, 0, 0, 0, 0 SLEEPQUEUE: 44, 0, 96, 219, 96, 0, 0 64 pcpu: 8, 0, 1883, 385, 1883, 0, 0 ptr pcpu: 4, 0, 0, 0, 0, 0, 0 Files: 64, 0, 74, 241, 16140, 0, 0 TURNSTILE: 72, 0, 96, 30, 96, 0, 0 rl_entry: 32, 0, 33, 345, 33, 0, 0 umtx pi: 52, 0, 0, 0, 0, 0, 0 PROC: 800, 0, 33, 22, 2390, 0, 0 THREAD: 800, 0, 87, 8, 87, 0, 0 cpuset: 40, 0, 56, 247, 56, 0, 0 mbuf_packet: 256, 16335, 64, 189, 175, 0, 0 mbuf: 256, 16335, 118, 139, 4155, 0, 0 mbuf_cluster: 2048, 2552, 253, 3, 253, 0, 0 mbuf_jumbo_page: 4096, 1275, 0, 0, 0, 0, 0 mbuf_jumbo_9k: 9216, 378, 0, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 212, 0, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0, 0, 0 sendfile_sync: 80, 0, 0, 0, 0, 0, 0 g_bio: 168, 0, 0, 144, 7360, 0, 0 ttyinq: 152, 0, 180, 28, 540, 0, 0 ttyoutq: 256, 0, 92, 43, 276, 0, 0 ata_request: 240, 0, 0, 64, 957, 0, 0 VNODE: 288, 0, 1224, 36, 1424, 0, 0 VNODEPOLL: 60, 0, 0, 0, 0, 0, 0 BUF TRIE: 48, 0, 36, 1476, 2371, 0, 0 NAMEI: 1024, 0, 0, 16, 54528, 0, 0 S VFS Cache: 72, 0, 1250, 150, 2945, 0, 0 STS VFS Cache: 116, 0, 0, 0, 0, 0, 0 L VFS Cache: 292, 0, 0, 0, 0, 0, 0 LTS VFS Cache: 336, 0, 0, 0, 0, 0, 0 procdesc: 76, 0, 0, 0, 0, 0, 0 pipe: 456, 0, 0, 32, 1349, 0, 0 Mountpoints: 688, 0, 4, 11, 4, 0, 0 ksiginfo: 80, 0, 43, 1007, 669, 0, 0 itimer: 256, 0, 1, 74, 1, 0, 0 bridge_rtnode: 36, 0, 0, 0, 0, 0, 0 KNOTE: 72, 0, 0, 0, 0, 0, 0 socket: 448, 3915, 50, 13, 1551, 0, 0 unpcb: 176, 3916, 10, 56, 170, 0, 0 ipq: 32, 126, 0, 0, 0, 0, 0 udp_inpcb: 256, 3915, 29, 46, 1128, 0, 0 udpcb: 12, 4032, 29, 475, 1128, 0, 0 tcp_inpcb: 256, 3915, 6, 69, 127, 0, 0 tcpcb: 776, 3915, 6, 9, 127, 0, 0 tcptw: 56, 792, 0, 288, 39, 0, 0 syncache: 124, 15360, 0, 128, 39, 0, 0 hostcache: 76, 15370, 0, 0, 0, 0, 0 sackhole: 20, 0, 0, 0, 0, 0, 0 udplite_inpcb: 256, 3915, 0, 0, 0, 0, 0 ripcb: 256, 3915, 1, 74, 118, 0, 0 rtentry: 108, 0, 28, 120, 28, 0, 0 selfd: 28, 0, 58, 230, 540800, 0, 0 SWAPMETA: 280, 15316, 0, 0, 0, 0, 0 FFS inode: 128, 0, 1203, 68, 1402, 0, 0 FFS1 dinode: 128, 0, 0, 0, 0, 0, 0 FFS2 dinode: 256, 0, 1203, 27, 1402, 0, 0 md0: 512, 0, 4211, 29, 4211, 0, 0 :~ # John > > > > -a > > > On 7 July 2014 07:25, John Hay wrote: > > Hi Guys, > > > > I'm further with getting my stuff working on the CAMBRIA xscale boards, > > but now see this > > > > ath1: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > > > error when trying to configure a second or third atheros board. Below > > is the script run with -x with its output. The same is working fine > > on an Avila board. The Avila has 64M RAM and the CAMBRIA 128M. The > > userlevel code is the same for both and in trying to see if it is > > something missing in the kernel config, I have made a common kernel > > config file with all the common AVILA and CAMBRIA configs and then > > included that in a new AVILA and CAMBRIA config file. That gave the > > same result. The output is from a 2 week old -current/head. > > > > ############################## > > ~ # uname -a > > FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r267954M: Fri Jun 27 14:49:04 SAST 2014 jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/SMALL-CAMBRIA arm > > ~ # /root/do-wlans > > + crflags='wlanmode adhoc' > > + dbgval=0x20000500c > > + ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > wlan0: Ethernet address: 00:80:48:4f:24:ea > > + ifconfig wlan0 inet 10.0.1.1/24 channel 36 ssid ptabb bssid 05:05:ca:fe:ba:be > > + sysctl dev.ath.1.debug=0x20000500c > > dev.ath.1.debug: 0 -> 8589955084 > > + ifconfig wlan1 create wlandev ath1 wlanmode adhoc > > wlan1: Ethernet address: 00:80:48:4f:24:da > > + ifconfig wlan1 inet 10.0.2.1/24 channel 40 ssid ptabb bssid 05:06:ca:fe:ba:be > > ath1: ath_init: if_flags 0x8803 > > ath1: ath_stop_locked: invalid 0 if_flags 0x8803 > > ath1: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > ath1: ath_legacy_startrecv: ath_rxbuf_init failed 12 > > ath1: unable to start recv logic > > + sysctl dev.ath.1.debug=0 > > dev.ath.1.debug: 8589955084 -> 0 > > + sysctl dev.ath.2.debug=0x20000500c > > dev.ath.2.debug: 0 -> 8589955084 > > + ifconfig wlan2 create wlandev ath2 wlanmode adhoc > > wlan2: Ethernet address: 00:21:a4:32:38:c2 > > + ifconfig wlan2 inet 10.0.3.1/24 channel 1 ssid ptabb bssid 05:07:ca:fe:ba:be > > ath2: ath_init: if_flags 0x8803 > > ath2: ath_stop_locked: invalid 0 if_flags 0x8803 > > ath2: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > ath2: ath_legacy_startrecv: ath_rxbuf_init failed 12 > > ath2: unable to start recv logic > > + sysctl dev.ath.2.debug=0 > > dev.ath.2.debug: 8589955084 -> 0 > > :~ # netstat -m > > 182/328/510 mbufs in use (current/cache/total) > > 64/192/256/2552 mbuf clusters in use (current/cache/total/max) > > 64/189 mbuf+clusters out of packet secondary zone in use (current/cache) > > 0/0/0/1275 4k (page size) jumbo clusters in use (current/cache/total/max) > > 0/0/0/378 9k jumbo clusters in use (current/cache/total/max) > > 0/0/0/212 16k jumbo clusters in use (current/cache/total/max) > > 173K/466K/639K bytes allocated to network (current/cache/total) > > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > > 0/3/1488 sfbufs in use (current/peak/max) > > 0 requests for sfbufs denied > > 0 requests for sfbufs delayed > > 0 requests for I/O initiated by sendfile > > ############################## > > > > CAMBRIA config file > > ############################## > > include XSCALE-ARM > > > > ident SMALL-CAMBRIA > > > > include "../xscale/ixp425/std.ixp435" > > > > hints "CAMBRIA.hints" > > > > options IXP4XX_FLASH_SIZE=0x02000000 # stock 2358 comes w/ 32M > > > > device cambria_fled # Font Panel LED on I2C bus > > device cambria_led # 8-LED latch > > > > device cambria_gpio # GPIO pins on J11 > > > > env "SMALL-AVILA.env" > > ############################## > > > > AVILA config file > > ############################## > > include XSCALE-ARM > > > > ident SMALL-AVILA > > > > include "../xscale/ixp425/std.ixp425" > > > > hints "AVILA.hints" # Default places to look for devices. > > > > device avila_led > > > > device avila_gpio # GPIO pins on J8 > > > > env "SMALL-AVILA.env" > > ############################## > > > > XSCALE-ARM config file > > ############################## > > include "../xscale/ixp425/std.avila" > > options XSCALE_CACHE_READ_WRITE_ALLOCATE > > makeoptions MODULES_OVERRIDE="" > > > > makeoptions CONF_CFLAGS=-mcpu=xscale > > options HZ=100 > > options DEVICE_POLLING > > > > options ROOTDEVNAME=\"ufs:ad0s1a\" > > > > options SCHED_4BSD # 4BSD scheduler > > options INET # Legacy InterNETworking > > options INET6 # InterNETworking > > options GEOM_PART_BSD # BSD partition scheme > > options GEOM_PART_MBR # MBR partition scheme > > options TMPFS # Efficient memory filesystem > > options FFS # Berkeley Fast Filesystem > > options SOFTUPDATES # Enable FFS soft updates support > > > > options HWPMC_HOOKS > > device hwpmc > > > > > > device pci > > device uart > > > > device ixpwdog # watchdog timer > > device cfi # flash support > > device cfid # flash disk support > > device geom_redboot # redboot fis parser > > > > device iicbus > > device iicbb > > device iic > > > > device ixpiic # I2C bus glue > > device ds1672 # DS1672 on I2C bus > > device ad7418 # AD7418 on I2C bus > > > > > > device gpio > > device gpioled > > > > device ata > > device avila_ata # Gateworks CF/IDE support > > > > device npe # Network Processing Engine > > device npe_fw > > device firmware > > device qmgr # Q Manager (required by npe) > > device mii # NB: required by npe > > device ether > > device bpf > > > > device loop > > device if_bridge > > > > device md > > device random # Entropy device > > > > device wlan # 802.11 support > > options IEEE80211_DEBUG > > options IEEE80211_SUPPORT_TDMA > > options IEEE80211_SUPPORT_MESH > > device wlan_wep # 802.11 WEP support > > device wlan_ccmp # 802.11 CCMP support > > device wlan_tkip # 802.11 TKIP support > > device wlan_xauth > > device wlan_acl > > > > device ath # Atheros NICs > > device ath_pci # Atheros pci/cardbus glue > > options ATH_DEBUG > > options ATH_DIAGAPI > > device ath_rate_sample # SampleRate tx rate control for ath > > > > options AH_DEBUG > > options AH_PRIVATE_DIAG > > device ath_ar5212 > > device ath_rf2413 > > device ath_rf2417 > > device ath_rf2425 > > device ath_rf5111 > > device ath_rf5112 > > device ath_rf5413 > > device ath_ar5416 > > options AH_SUPPORT_AR5416 > > device ath_ar9160 > > device ath_ar9280 > > > > device usb > > options USB_EHCI_BIG_ENDIAN_DESC > > device ohci > > device ehci > > device umass > > device scbus # SCSI bus (required for ATA/SCSI) > > device da # Direct Access (disks) > > device pass # Passthrough device (direct ATA/SCSI access) > > > > > > device gif > > device tun > > ############################## > > > > > > Regards > > > > John > > -- > > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za > > _______________________________________________ > > freebsd-embedded@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 17:13:00 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD6F87D7; Mon, 7 Jul 2014 17:13:00 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 995322B39; Mon, 7 Jul 2014 17:12:56 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1X4CTB-000Nwi-Ot; Mon, 07 Jul 2014 17:12:50 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s67HCkBT001210; Mon, 7 Jul 2014 11:12:46 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19kbGmYTrXdfK7dlbccaBrO Subject: Re: CAMBRIA and more than one atheros card From: Ian Lepore To: Adrian Chadd In-Reply-To: References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> Content-Type: text/plain; charset="us-ascii" Date: Mon, 07 Jul 2014 11:12:46 -0600 Message-ID: <1404753166.65432.10.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 17:13:01 -0000 On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: > hi, > > That call is returning ENOMEM. I'm not sure why. It allocated an mbuf > fine, but it couldn't allocate the DMA map. > > What's the output of "vmstat -z" ? I wonder if it's failing an allocation. > > > > -a Lack of bounce buffers is a posibility that won't show up in vmstat output. -- Ian > On 7 July 2014 07:25, John Hay wrote: > > Hi Guys, > > > > I'm further with getting my stuff working on the CAMBRIA xscale boards, > > but now see this > > > > ath1: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > > > error when trying to configure a second or third atheros board. Below > > is the script run with -x with its output. The same is working fine > > on an Avila board. The Avila has 64M RAM and the CAMBRIA 128M. The > > userlevel code is the same for both and in trying to see if it is > > something missing in the kernel config, I have made a common kernel > > config file with all the common AVILA and CAMBRIA configs and then > > included that in a new AVILA and CAMBRIA config file. That gave the > > same result. The output is from a 2 week old -current/head. > > > > ############################## > > ~ # uname -a > > FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r267954M: Fri Jun 27 14:49:04 SAST 2014 jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/SMALL-CAMBRIA arm > > ~ # /root/do-wlans > > + crflags='wlanmode adhoc' > > + dbgval=0x20000500c > > + ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > wlan0: Ethernet address: 00:80:48:4f:24:ea > > + ifconfig wlan0 inet 10.0.1.1/24 channel 36 ssid ptabb bssid 05:05:ca:fe:ba:be > > + sysctl dev.ath.1.debug=0x20000500c > > dev.ath.1.debug: 0 -> 8589955084 > > + ifconfig wlan1 create wlandev ath1 wlanmode adhoc > > wlan1: Ethernet address: 00:80:48:4f:24:da > > + ifconfig wlan1 inet 10.0.2.1/24 channel 40 ssid ptabb bssid 05:06:ca:fe:ba:be > > ath1: ath_init: if_flags 0x8803 > > ath1: ath_stop_locked: invalid 0 if_flags 0x8803 > > ath1: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > ath1: ath_legacy_startrecv: ath_rxbuf_init failed 12 > > ath1: unable to start recv logic > > + sysctl dev.ath.1.debug=0 > > dev.ath.1.debug: 8589955084 -> 0 > > + sysctl dev.ath.2.debug=0x20000500c > > dev.ath.2.debug: 0 -> 8589955084 > > + ifconfig wlan2 create wlandev ath2 wlanmode adhoc > > wlan2: Ethernet address: 00:21:a4:32:38:c2 > > + ifconfig wlan2 inet 10.0.3.1/24 channel 1 ssid ptabb bssid 05:07:ca:fe:ba:be > > ath2: ath_init: if_flags 0x8803 > > ath2: ath_stop_locked: invalid 0 if_flags 0x8803 > > ath2: ath_legacy_rxbuf_init: bus_dmamap_load_mbuf_sg failed; error 12 > > ath2: ath_legacy_startrecv: ath_rxbuf_init failed 12 > > ath2: unable to start recv logic > > + sysctl dev.ath.2.debug=0 > > dev.ath.2.debug: 8589955084 -> 0 > > :~ # netstat -m > > 182/328/510 mbufs in use (current/cache/total) > > 64/192/256/2552 mbuf clusters in use (current/cache/total/max) > > 64/189 mbuf+clusters out of packet secondary zone in use (current/cache) > > 0/0/0/1275 4k (page size) jumbo clusters in use (current/cache/total/max) > > 0/0/0/378 9k jumbo clusters in use (current/cache/total/max) > > 0/0/0/212 16k jumbo clusters in use (current/cache/total/max) > > 173K/466K/639K bytes allocated to network (current/cache/total) > > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > > 0/3/1488 sfbufs in use (current/peak/max) > > 0 requests for sfbufs denied > > 0 requests for sfbufs delayed > > 0 requests for I/O initiated by sendfile > > ############################## > > > > CAMBRIA config file > > ############################## > > include XSCALE-ARM > > > > ident SMALL-CAMBRIA > > > > include "../xscale/ixp425/std.ixp435" > > > > hints "CAMBRIA.hints" > > > > options IXP4XX_FLASH_SIZE=0x02000000 # stock 2358 comes w/ 32M > > > > device cambria_fled # Font Panel LED on I2C bus > > device cambria_led # 8-LED latch > > > > device cambria_gpio # GPIO pins on J11 > > > > env "SMALL-AVILA.env" > > ############################## > > > > AVILA config file > > ############################## > > include XSCALE-ARM > > > > ident SMALL-AVILA > > > > include "../xscale/ixp425/std.ixp425" > > > > hints "AVILA.hints" # Default places to look for devices. > > > > device avila_led > > > > device avila_gpio # GPIO pins on J8 > > > > env "SMALL-AVILA.env" > > ############################## > > > > XSCALE-ARM config file > > ############################## > > include "../xscale/ixp425/std.avila" > > options XSCALE_CACHE_READ_WRITE_ALLOCATE > > makeoptions MODULES_OVERRIDE="" > > > > makeoptions CONF_CFLAGS=-mcpu=xscale > > options HZ=100 > > options DEVICE_POLLING > > > > options ROOTDEVNAME=\"ufs:ad0s1a\" > > > > options SCHED_4BSD # 4BSD scheduler > > options INET # Legacy InterNETworking > > options INET6 # InterNETworking > > options GEOM_PART_BSD # BSD partition scheme > > options GEOM_PART_MBR # MBR partition scheme > > options TMPFS # Efficient memory filesystem > > options FFS # Berkeley Fast Filesystem > > options SOFTUPDATES # Enable FFS soft updates support > > > > options HWPMC_HOOKS > > device hwpmc > > > > > > device pci > > device uart > > > > device ixpwdog # watchdog timer > > device cfi # flash support > > device cfid # flash disk support > > device geom_redboot # redboot fis parser > > > > device iicbus > > device iicbb > > device iic > > > > device ixpiic # I2C bus glue > > device ds1672 # DS1672 on I2C bus > > device ad7418 # AD7418 on I2C bus > > > > > > device gpio > > device gpioled > > > > device ata > > device avila_ata # Gateworks CF/IDE support > > > > device npe # Network Processing Engine > > device npe_fw > > device firmware > > device qmgr # Q Manager (required by npe) > > device mii # NB: required by npe > > device ether > > device bpf > > > > device loop > > device if_bridge > > > > device md > > device random # Entropy device > > > > device wlan # 802.11 support > > options IEEE80211_DEBUG > > options IEEE80211_SUPPORT_TDMA > > options IEEE80211_SUPPORT_MESH > > device wlan_wep # 802.11 WEP support > > device wlan_ccmp # 802.11 CCMP support > > device wlan_tkip # 802.11 TKIP support > > device wlan_xauth > > device wlan_acl > > > > device ath # Atheros NICs > > device ath_pci # Atheros pci/cardbus glue > > options ATH_DEBUG > > options ATH_DIAGAPI > > device ath_rate_sample # SampleRate tx rate control for ath > > > > options AH_DEBUG > > options AH_PRIVATE_DIAG > > device ath_ar5212 > > device ath_rf2413 > > device ath_rf2417 > > device ath_rf2425 > > device ath_rf5111 > > device ath_rf5112 > > device ath_rf5413 > > device ath_ar5416 > > options AH_SUPPORT_AR5416 > > device ath_ar9160 > > device ath_ar9280 > > > > device usb > > options USB_EHCI_BIG_ENDIAN_DESC > > device ohci > > device ehci > > device umass > > device scbus # SCSI bus (required for ATA/SCSI) > > device da # Direct Access (disks) > > device pass # Passthrough device (direct ATA/SCSI access) > > > > > > device gif > > device tun > > ############################## > > > > > > Regards > > > > John > > -- > > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za > > _______________________________________________ > > freebsd-embedded@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:22:56 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5CE8DE5; Mon, 7 Jul 2014 18:22:56 +0000 (UTC) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 549642212; Mon, 7 Jul 2014 18:22:56 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id hw13so3883400qab.17 for ; Mon, 07 Jul 2014 11:22:55 -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=VFFzDAyccKE9VmMpgijzjHE/xU8+pF6Yw36tyaLuIBM=; b=LQ9rnRQI4xF0rLvPHsW4QnG+2XIq/fF9ipaJWQfkHs8sX1OGCnIXO/pYmqGmyw0ABb FOuhbAHV4yW+279G4cq7Pf32ptD/VDodj9Bk/owds3tIzWvaSoB7Fmy/1hqZGPNqFhp+ G/z/MG6J61P2zlmN0LsxbHFc47bc7CFZA1eZ/BNX8ara9rMaKplJ468WM0r+4Np+55G9 fzxHdFybpAMQQer01yHzxHAKWasaZsC7/cN9GoVue+ySsGGqAjHkH6WHMhuJdWX1yDKd Di4wuLpbISvJNK8PmGIi1qm0Bw8XZ4uILl6KXnxDZVv45Sb6m3mq/cf+U2a2Ll/1Amih zBTw== MIME-Version: 1.0 X-Received: by 10.224.16.200 with SMTP id p8mr51770950qaa.76.1404757366305; Mon, 07 Jul 2014 11:22:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 11:22:46 -0700 (PDT) In-Reply-To: <1404753166.65432.10.camel@revolution.hippie.lan> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> Date: Mon, 7 Jul 2014 11:22:46 -0700 X-Google-Sender-Auth: FRKgz7hVrOu2YAfyuJ8wcvtCLbc Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:22:56 -0000 On 7 July 2014 10:12, Ian Lepore wrote: > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: >> hi, >> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf >> fine, but it couldn't allocate the DMA map. >> >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. >> >> >> >> -a > > Lack of bounce buffers is a posibility that won't show up in vmstat > output. right, but there's a bunch of already failing vmstat entries. John - there's a vmscale parameter somewhere. Hiren had to drop it down for his APs to work in 64MB of RAM. I think it's vm.kmem_size_scale . What's it say for you? -a From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:23:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 859E2E4E for ; Mon, 7 Jul 2014 18:23:53 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 486032223 for ; Mon, 7 Jul 2014 18:23:53 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id q107so3961550qgd.33 for ; Mon, 07 Jul 2014 11:23:52 -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=nWSdXraRFP4vwvdi4eXWcmAFMlvENI56Ud4aMAxDQWU=; b=FYXdSr6z7A7f1K2qvj2MMIF80dxzj+0CPwgHCUCo8GX0s1fFGs6gJ8BE4PdSzkofc2 bLESkNkWwYGuV7lL94O2M+jhHG8/VnIgmQSiK/Db6NLbLLRLeupG+WcCvT9MPkd7O3S2 d31rnK3rryVHzJDULkDHWxZ/tv2u5KsVLMhH4sSeDXKAl2iJ/CL0OdCg46G9O+kQtUCW ddFvq5LOSWkvcvVqBVjgPTKuF7fgqhTgDjGJLKjMSNd8vyuhKEGMSVSMFW0z5o7Kkwyx CCoiWcr6OSWLhkIN+0vcstrJJoPrlUOjx872/XPVIoVLB0L+BXKsNne4BWSthk5d2Qvp XZQQ== MIME-Version: 1.0 X-Received: by 10.224.16.200 with SMTP id p8mr51782189qaa.76.1404757432444; Mon, 07 Jul 2014 11:23:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 11:23:52 -0700 (PDT) In-Reply-To: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> Date: Mon, 7 Jul 2014 11:23:52 -0700 X-Google-Sender-Auth: Ds8kKgkkaJMnclcb_ra-OSQjJmo Message-ID: Subject: Re: TP-LINK TL-WN821N From: Adrian Chadd To: Carlos Jacobo Puga Medina Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:23:53 -0000 On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote: > Hi people, > > Does anyone still work to porting the otus driver from OpenBSD? > > https://github.com/erikarn/otus/tree/master/otus Nope. I got stuck on trying to figure out how to correctly implement the synchronous/asynchronous message queues over USB - I haven't found a driver that 100% correctly implements that stuff so I have to hand craft it myself. Then I mostly lost interest. Sorry. -a From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:28:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E92291C3; Mon, 7 Jul 2014 18:28:17 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id 76890226E; Mon, 7 Jul 2014 18:28:17 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id CA011B843; Mon, 7 Jul 2014 20:28:14 +0200 (SAST) Date: Mon, 7 Jul 2014 20:28:14 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140707182814.GA75629@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:28:18 -0000 On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: > On 7 July 2014 10:12, Ian Lepore wrote: > > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: > >> hi, > >> > >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf > >> fine, but it couldn't allocate the DMA map. > >> > >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. > >> > >> > >> > >> -a > > > > Lack of bounce buffers is a posibility that won't show up in vmstat > > output. > > right, but there's a bunch of already failing vmstat entries. > > > John - there's a vmscale parameter somewhere. Hiren had to drop it > down for his APs to work in 64MB of RAM. I think it's > vm.kmem_size_scale . What's it say for you? > :~ # sysctl vm.kmem_size_scale vm.kmem_size_scale: 3 John -- John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:31:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 584EC341; Mon, 7 Jul 2014 18:31:05 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA2A322A8; Mon, 7 Jul 2014 18:31:04 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id w8so3878962qac.36 for ; Mon, 07 Jul 2014 11:31:04 -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=a5Djti8u6LpcWgz70K8P88vmU32CS9SerJD0ELfHsbM=; b=sVyMf8aQSNwV5CW+UvWaN6z6Sbsj4H2SmoqVl2DrpMQWtgJVE7N29XS67ycriFz+na dU6oTAKSy2YGn3uw46mp/s5V71NqF3IfDm3qI/CjDpe1vIZy3op5Xzk2wC+gtTIAwzc7 WF/FlhaABdl855VkztpdSHo7Rcxnzf4pomXPiA6DxEM/TD1Z6MKtjRxekwmSDf5hCeR6 wT2pHB8OA6fAyHyibpq562ZKSzT8JwMyDwQxagKys/fU/X+3FZaPotSYhlfLUA5RkUIQ kNY6/d5FQRvTqAY8IHOlTbiuJlPfFKA08vQomUqwCt0UuyOoGtLAFqNMqRyrp+FXYhVt cxlQ== MIME-Version: 1.0 X-Received: by 10.140.80.49 with SMTP id b46mr46919556qgd.102.1404757864164; Mon, 07 Jul 2014 11:31:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 11:31:04 -0700 (PDT) In-Reply-To: <20140707182814.GA75629@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> Date: Mon, 7 Jul 2014 11:31:04 -0700 X-Google-Sender-Auth: 1Rfsn0QtDVdof5grrqu6X4ssjFA Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:31:05 -0000 On 7 July 2014 11:28, John Hay wrote: > On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: >> On 7 July 2014 10:12, Ian Lepore wrote: >> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: >> >> hi, >> >> >> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf >> >> fine, but it couldn't allocate the DMA map. >> >> >> >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. >> >> >> >> >> >> >> >> -a >> > >> > Lack of bounce buffers is a posibility that won't show up in vmstat >> > output. >> >> right, but there's a bunch of already failing vmstat entries. >> >> >> John - there's a vmscale parameter somewhere. Hiren had to drop it >> down for his APs to work in 64MB of RAM. I think it's >> vm.kmem_size_scale . What's it say for you? >> > > :~ # sysctl vm.kmem_size_scale > vm.kmem_size_scale: 3 Ok. Search the archives for an email from Hiren titled "mbuf autotuning effect". TL;DR - set it to 1 and recompile. There's a kernel option somewhere to do exactly that. -a From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:46:50 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BF5D777; Mon, 7 Jul 2014 18:46:50 +0000 (UTC) Received: from erelay5.ox.registrar-servers.com (erelay5.ox.registrar-servers.com [192.64.117.65]) by mx1.freebsd.org (Postfix) with ESMTP id 15AC02438; Mon, 7 Jul 2014 18:46:49 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 286732204DE2; Mon, 7 Jul 2014 18:46:48 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IKX3jsEt2Nco; Mon, 7 Jul 2014 14:46:47 -0400 (EDT) Received: from imap10.ox.privateemail.com (imap10.ox.privateemail.com [192.64.116.221]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id E89112204BAE; Mon, 7 Jul 2014 14:46:46 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 977C52400C2; Mon, 7 Jul 2014 14:46:46 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id phoW33-RbH4b; Mon, 7 Jul 2014 14:46:46 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id C29A42400DA; Mon, 7 Jul 2014 14:46:45 -0400 (EDT) Date: Mon, 7 Jul 2014 20:46:36 +0200 From: Carlos Jacobo Puga Medina To: Adrian Chadd Subject: Re: TP-LINK TL-WN821N Message-Id: <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> In-Reply-To: References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:46:50 -0000 On Mon, 7 Jul 2014 11:23:52 -0700 Adrian Chadd wrote: > On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote: > > Hi people, > > > > Does anyone still work to porting the otus driver from OpenBSD? > > > > https://github.com/erikarn/otus/tree/master/otus > > Nope. I got stuck on trying to figure out how to correctly implement > the synchronous/asynchronous message queues over USB - I haven't found > a driver that 100% correctly implements that stuff so I have to hand > craft it myself. Then I mostly lost interest. > > Sorry. > > > > -a Thanks for your reply. I purchased this model so I'm interested in make it work on FreeBSD...where to start my contribution? -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:48:38 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 924B87B6 for ; Mon, 7 Jul 2014 18:48:38 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53700244D for ; Mon, 7 Jul 2014 18:48:38 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id l6so4276173qcy.15 for ; Mon, 07 Jul 2014 11:48:36 -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=9vPf43ZkxxX9Za9fReFtiwbN1SsQ2J+ETmtrh3PqUp8=; b=trq6NwCMOvHKTqtXMm6bXhzx8I4UZ5TjqBvH6ejO5Mdh81C1+ogQiY0zgXSdfoz9vO TTbjBDKSla+cw1LfZcZINAQHJuqZq4tTg2pvoO7LMzD0WSIcPHL6AurPEIzBN5l6LmSK Nq5D4ZJXMAMeI/RFxT9NV8SQAOsA5UgHWhkGvvnDMcbsLnnB0Now+QHg/jeW1noSsc3m 3kqV4ce4D86qtElU15yus+3onyU40f/tuZgtnyzNGTCQTeutVQNn88StFAbW04U60QWH FYIlegA5EWoaFv8s+udgZCF2z3TnSxsMgGRI0Xa5wMx1j8b347v3eqsmskEh9UAvWDoY 15zA== MIME-Version: 1.0 X-Received: by 10.140.89.18 with SMTP id u18mr6877675qgd.87.1404758916677; Mon, 07 Jul 2014 11:48:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 11:48:36 -0700 (PDT) In-Reply-To: <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> Date: Mon, 7 Jul 2014 11:48:36 -0700 X-Google-Sender-Auth: mNceghswqpIMETJf4BNHXo6Nzos Message-ID: Subject: Re: TP-LINK TL-WN821N From: Adrian Chadd To: Carlos Jacobo Puga Medina Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:48:38 -0000 I'd just look at porting over the openbsd driver. There's no 11n support in the openbsd code though! -a On 7 July 2014 11:46, Carlos Jacobo Puga Medina wrote: > On Mon, 7 Jul 2014 11:23:52 -0700 > Adrian Chadd wrote: > >> On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote: >> > Hi people, >> > >> > Does anyone still work to porting the otus driver from OpenBSD? >> > >> > https://github.com/erikarn/otus/tree/master/otus >> >> Nope. I got stuck on trying to figure out how to correctly implement >> the synchronous/asynchronous message queues over USB - I haven't found >> a driver that 100% correctly implements that stuff so I have to hand >> craft it myself. Then I mostly lost interest. >> >> Sorry. >> >> >> >> -a > > Thanks for your reply. I purchased this model so I'm interested in make it work on FreeBSD...where to start my contribution? > > -- > Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 18:59:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B23A7C31; Mon, 7 Jul 2014 18:59:04 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E01E2556; Mon, 7 Jul 2014 18:59:04 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id z60so4184105qgd.30 for ; Mon, 07 Jul 2014 11:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kacfo9qopojflT/zL+Jj89/QFL5ZFj6JZorZFUtVm/o=; b=0vrXRZcQpxVbFqh/df1pHa2heqwnJ0eqK3bWn6YFsyEX9hXUmWaH48MvJlClXl4G/v 99Vn2BLtvGBpTeNNbiPkQZFSGGSsE1VHABTcz70EiRE2P7qrFI/wJKlTAYAXhHzNyxTD Fy4vG8ss5/+QyzX72FcWVUoP13bngPlv6KgBew4AnOYYCku94EmzdJoWLinGQFWwIXPD +xo3ZDahCfqkttdK2wSxlMeNukoW7gcCrA8jU/YKKhXJNnixOTlu6BYstG5mjhGMUG/J +Jno32AZFx9lWpdbHIvr6mzo925F5RXa4DlsjQazPdoW/39CQ6Co8Xuip4vlzo/9dyCT rGbQ== MIME-Version: 1.0 X-Received: by 10.229.252.130 with SMTP id mw2mr49590856qcb.12.1404759543392; Mon, 07 Jul 2014 11:59:03 -0700 (PDT) Received: by 10.96.73.39 with HTTP; Mon, 7 Jul 2014 11:59:03 -0700 (PDT) In-Reply-To: References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> Date: Mon, 7 Jul 2014 11:59:03 -0700 Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: hiren panchasara To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 18:59:04 -0000 On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd wrote: > On 7 July 2014 11:28, John Hay wrote: >> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: >>> On 7 July 2014 10:12, Ian Lepore wrote: >>> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: >>> >> hi, >>> >> >>> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf >>> >> fine, but it couldn't allocate the DMA map. >>> >> >>> >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. >>> >> >>> >> >>> >> >>> >> -a >>> > >>> > Lack of bounce buffers is a posibility that won't show up in vmstat >>> > output. >>> >>> right, but there's a bunch of already failing vmstat entries. >>> >>> >>> John - there's a vmscale parameter somewhere. Hiren had to drop it >>> down for his APs to work in 64MB of RAM. I think it's >>> vm.kmem_size_scale . What's it say for you? >>> >> >> :~ # sysctl vm.kmem_size_scale >> vm.kmem_size_scale: 3 > > Ok. Search the archives for an email from Hiren titled "mbuf autotuning effect". > > TL;DR - set it to 1 and recompile. There's a kernel option somewhere > to do exactly that. Yes. http://lists.freebsd.org/pipermail/freebsd-mips/2013-September/003081.html I went through this for my tplink. John, can you show o/p of: sysctl -a | grep hw | grep mem and sysctl -a | grep maxmbuf Cheers, Hiren From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 19:10:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 12087199; Mon, 7 Jul 2014 19:10:47 +0000 (UTC) Received: from erelay5.ox.registrar-servers.com (erelay5.ox.registrar-servers.com [192.64.117.65]) by mx1.freebsd.org (Postfix) with ESMTP id DE11F265A; Mon, 7 Jul 2014 19:10:46 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 617472204DFD; Mon, 7 Jul 2014 19:10:46 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VYYjyrmNAAjE; Mon, 7 Jul 2014 15:10:45 -0400 (EDT) Received: from imap2.ox.privateemail.com (imap2.ox.privateemail.com [198.187.29.234]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 9F8972204AD7; Mon, 7 Jul 2014 15:10:45 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 4B6D78C0083; Mon, 7 Jul 2014 15:10:45 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap2.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap2.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qZQ8bbestfiX; Mon, 7 Jul 2014 15:10:45 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 6EA6C8C0081; Mon, 7 Jul 2014 15:10:44 -0400 (EDT) Date: Mon, 7 Jul 2014 21:10:35 +0200 From: Carlos Jacobo Puga Medina To: Adrian Chadd Subject: Re: TP-LINK TL-WN821N Message-Id: <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> In-Reply-To: References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 19:10:47 -0000 On Mon, 7 Jul 2014 11:48:36 -0700 Adrian Chadd wrote: > I'd just look at porting over the openbsd driver. There's no 11n > support in the openbsd code though! That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. What do you recommend to do? > > > -a > > > On 7 July 2014 11:46, Carlos Jacobo Puga Medina wrote: > > On Mon, 7 Jul 2014 11:23:52 -0700 > > Adrian Chadd wrote: > > > >> On 7 July 2014 05:40, Carlos Jacobo Puga Medina wrote: > >> > Hi people, > >> > > >> > Does anyone still work to porting the otus driver from OpenBSD? > >> > > >> > https://github.com/erikarn/otus/tree/master/otus > >> > >> Nope. I got stuck on trying to figure out how to correctly implement > >> the synchronous/asynchronous message queues over USB - I haven't found > >> a driver that 100% correctly implements that stuff so I have to hand > >> craft it myself. Then I mostly lost interest. > >> > >> Sorry. > >> > >> > >> > >> -a > > > > Thanks for your reply. I purchased this model so I'm interested in make it work on FreeBSD...where to start my contribution? > > > > -- > > Carlos Jacobo Puga Medina -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 19:16:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13A4127F for ; Mon, 7 Jul 2014 19:16:14 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7AEF2700 for ; Mon, 7 Jul 2014 19:16:13 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id i8so4252274qcq.34 for ; Mon, 07 Jul 2014 12:16:13 -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=5gjKH/LdxPFtdy3ebJgDjATAvMwKmdEEY1SFklqE2+U=; b=VZ0IpQHMP5glFwGlxrNrjHeg/EyHbEJhLY1L3vKMhzHec5yIHU2o077n0bFrQnsVIf 8YqWTLyr3ESRvhSP2DFyKKD2cOHthY9LExdRYEZLv81Wtk3Bf7l/RSQKIE0E5SPdYXfm KpZxsj9nyt0/DD88oHBzqlwshRD/AOikqgVAtDgJGpfc8BRyW0LlWNXGIGoxc8iTTKqn T3nC3NfsKgIqQXpj17a81nzKpJyk9ku3U3U7LT6eLDPyy1PN2StckH+mnG/ypjfB7rBM 36fPXer5wZOT/kgnA7x6yoTjiYAbCpmATY3ZYJcU1LTfJXc2NL6PghZfRmh1Jc2ymf2N wOfA== MIME-Version: 1.0 X-Received: by 10.229.44.65 with SMTP id z1mr49682473qce.7.1404760572968; Mon, 07 Jul 2014 12:16:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 12:16:12 -0700 (PDT) In-Reply-To: <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> Date: Mon, 7 Jul 2014 12:16:12 -0700 X-Google-Sender-Auth: 0xXMAciBM0kqv5EncbRLV61GK3w Message-ID: Subject: Re: TP-LINK TL-WN821N From: Adrian Chadd To: Carlos Jacobo Puga Medina Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 19:16:14 -0000 On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > On Mon, 7 Jul 2014 11:48:36 -0700 > Adrian Chadd wrote: > >> I'd just look at porting over the openbsd driver. There's no 11n >> support in the openbsd code though! > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > What do you recommend to do? I'd be happy if the driver showed up from OpenBSD. We can always try to add 11n support. I'm sorry, I don't have much else to say at the moment and as my day job is decidedly not wireless, I can't be much help. :( -a From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 19:26:54 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 715B869C; Mon, 7 Jul 2014 19:26:54 +0000 (UTC) Received: from erelay5.ox.registrar-servers.com (erelay5.ox.registrar-servers.com [192.64.117.65]) by mx1.freebsd.org (Postfix) with ESMTP id 4801C27E8; Mon, 7 Jul 2014 19:26:53 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id A3C8C2204987; Mon, 7 Jul 2014 19:26:53 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kV3YDwsgAZ-2; Mon, 7 Jul 2014 15:26:53 -0400 (EDT) Received: from imap11.ox.privateemail.com (imap11.ox.privateemail.com [192.64.116.222]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 167D0220173B; Mon, 7 Jul 2014 15:26:53 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id B97A58800E9; Mon, 7 Jul 2014 15:26:52 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap11.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap11.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9_lCsJOp6Lll; Mon, 7 Jul 2014 15:26:52 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id DF0058800CB; Mon, 7 Jul 2014 15:26:51 -0400 (EDT) Date: Mon, 7 Jul 2014 21:26:43 +0200 From: Carlos Jacobo Puga Medina To: Adrian Chadd Subject: Re: TP-LINK TL-WN821N Message-Id: <20140707212643.9ed05541055eff37b3ae48f1@fbsd.es> In-Reply-To: References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 19:26:54 -0000 On Mon, 7 Jul 2014 12:16:12 -0700 Adrian Chadd wrote: > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > On Mon, 7 Jul 2014 11:48:36 -0700 > > Adrian Chadd wrote: > > > >> I'd just look at porting over the openbsd driver. There's no 11n > >> support in the openbsd code though! > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > What do you recommend to do? > > I'd be happy if the driver showed up from OpenBSD. We can always try > to add 11n support. > > I'm sorry, I don't have much else to say at the moment and as my day > job is decidedly not wireless, I can't be much help. :( > > > -a OK, thanks for clearing things up, adrian@ -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 19:32:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46294AF3; Mon, 7 Jul 2014 19:32:55 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id C49AA28B0; Mon, 7 Jul 2014 19:32:54 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 52868B843; Mon, 7 Jul 2014 21:32:52 +0200 (SAST) Date: Mon, 7 Jul 2014 21:32:52 +0200 From: John Hay To: hiren panchasara Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140707193252.GA79553@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 19:32:55 -0000 On Mon, Jul 07, 2014 at 11:59:03AM -0700, hiren panchasara wrote: > On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd wrote: > > On 7 July 2014 11:28, John Hay wrote: > >> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: > >>> On 7 July 2014 10:12, Ian Lepore wrote: > >>> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: > >>> >> hi, > >>> >> > >>> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf > >>> >> fine, but it couldn't allocate the DMA map. > >>> >> > >>> >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. > >>> >> > >>> >> > >>> >> > >>> >> -a > >>> > > >>> > Lack of bounce buffers is a posibility that won't show up in vmstat > >>> > output. > >>> > >>> right, but there's a bunch of already failing vmstat entries. > >>> > >>> > >>> John - there's a vmscale parameter somewhere. Hiren had to drop it > >>> down for his APs to work in 64MB of RAM. I think it's > >>> vm.kmem_size_scale . What's it say for you? > >>> > >> > >> :~ # sysctl vm.kmem_size_scale > >> vm.kmem_size_scale: 3 > > > > Ok. Search the archives for an email from Hiren titled "mbuf autotuning effect". > > > > TL;DR - set it to 1 and recompile. There's a kernel option somewhere > > to do exactly that. > > Yes. http://lists.freebsd.org/pipermail/freebsd-mips/2013-September/003081.html > > I went through this for my tplink. > > John, can you show o/p of: > > sysctl -a | grep hw | grep mem > and > sysctl -a | grep maxmbuf I already compiled a new kernel with "options VM_KMEM_SIZE_SCALE=1" and the problems went away. :-) On the new kernel the output is: ########################## :~ # sysctl -a | grep hw | grep mem hw.physmem: 128196608 hw.usermem: 103845888 hw.realmem: 134213632 :~ # sysctl -a | grep maxmbuf kern.ipc.maxmbufmem: 62705664 ########################## I rebooted with the old kernel and its output is: ########################## :~ # sysctl -a | grep hw | grep mem hw.physmem: 128196608 hw.usermem: 104124416 hw.realmem: 134213632 :~ # sysctl -a | grep maxmbuf kern.ipc.maxmbufmem: 20901888 ########################## So for the heck of it, I ran my script again and this time it successfully configured the 3 atheros interfaces. ? How can that be? One other thing I also do not understand. I have an Avila (with 64M RAM, half of the CAMBRIA), also with 3 atheros cards and there it always works. But if "options VM_KMEM_SIZE_SCALE=1" keeps the problem away, then I'll leave that in my kernel. :-) Thanks for everyone that helped. John -- John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 7 19:43:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E6BCF9D; Mon, 7 Jul 2014 19:43:19 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D58029AE; Mon, 7 Jul 2014 19:43:18 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id s7so11151qap.32 for ; Mon, 07 Jul 2014 12:43:17 -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=Yf4etpaldGJyOg8kaS3wjl0sFACCt3/DCs6pYZYHH0Q=; b=WZFKxU6wfqcSse0DJahb5smr6rdVdoXhgiXxeHR4hA7l4+MtjXb/ub6F3fLrOcfQC8 g8WxQdJUvqzy3+95B+aeUPHj+dNhO28GWUQf5ChSAowYze+XjVqE+CM2iqv2fO/R04Pt hhjoZ6I1EOTVyAfs/aT31DBFJFQBKeFFQeNZ/fjDbAkc+r7PupaTujC8Th+FK83cizL8 2Oh1vTWBAV7SdNd2UmgrdgUEHCg6QHGjxJFY1Ybm5n+Qh/rP5LFL3OXktPJ4ysZWIe+3 rEO7cbBItPOWffMHhQZUrKJN6zYHHUrFFu/8zQjEufx5fxHFTjqXkLXuiv2ta/+7czuq DTOw== MIME-Version: 1.0 X-Received: by 10.140.47.48 with SMTP id l45mr48216555qga.24.1404762197753; Mon, 07 Jul 2014 12:43:17 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 7 Jul 2014 12:43:17 -0700 (PDT) In-Reply-To: <20140707193252.GA79553@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> Date: Mon, 7 Jul 2014 12:43:17 -0700 X-Google-Sender-Auth: DIMKQaCgAkMLktJoTFB5qjIMUwo Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , Ian Lepore , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 19:43:19 -0000 Sweet! Can you run the same commands above on the Avila board? Would you mind filing a PR to ensure we get that option into the relevant kernel(s) ? (I'm kinda tempted to suggest we auto-select the scaling factor at startup depending upon physical RAM .. ) -a On 7 July 2014 12:32, John Hay wrote: > On Mon, Jul 07, 2014 at 11:59:03AM -0700, hiren panchasara wrote: >> On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd wrote: >> > On 7 July 2014 11:28, John Hay wrote: >> >> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: >> >>> On 7 July 2014 10:12, Ian Lepore wrote: >> >>> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: >> >>> >> hi, >> >>> >> >> >>> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf >> >>> >> fine, but it couldn't allocate the DMA map. >> >>> >> >> >>> >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. >> >>> >> >> >>> >> >> >>> >> >> >>> >> -a >> >>> > >> >>> > Lack of bounce buffers is a posibility that won't show up in vmstat >> >>> > output. >> >>> >> >>> right, but there's a bunch of already failing vmstat entries. >> >>> >> >>> >> >>> John - there's a vmscale parameter somewhere. Hiren had to drop it >> >>> down for his APs to work in 64MB of RAM. I think it's >> >>> vm.kmem_size_scale . What's it say for you? >> >>> >> >> >> >> :~ # sysctl vm.kmem_size_scale >> >> vm.kmem_size_scale: 3 >> > >> > Ok. Search the archives for an email from Hiren titled "mbuf autotuning effect". >> > >> > TL;DR - set it to 1 and recompile. There's a kernel option somewhere >> > to do exactly that. >> >> Yes. http://lists.freebsd.org/pipermail/freebsd-mips/2013-September/003081.html >> >> I went through this for my tplink. >> >> John, can you show o/p of: >> >> sysctl -a | grep hw | grep mem >> and >> sysctl -a | grep maxmbuf > > I already compiled a new kernel with "options VM_KMEM_SIZE_SCALE=1" and > the problems went away. :-) On the new kernel the output is: > > ########################## > :~ # sysctl -a | grep hw | grep mem > hw.physmem: 128196608 > hw.usermem: 103845888 > hw.realmem: 134213632 > :~ # sysctl -a | grep maxmbuf > kern.ipc.maxmbufmem: 62705664 > ########################## > > I rebooted with the old kernel and its output is: > > ########################## > :~ # sysctl -a | grep hw | grep mem > hw.physmem: 128196608 > hw.usermem: 104124416 > hw.realmem: 134213632 > :~ # sysctl -a | grep maxmbuf > kern.ipc.maxmbufmem: 20901888 > ########################## > > So for the heck of it, I ran my script again and this time it successfully > configured the 3 atheros interfaces. ? How can that be? One other thing I > also do not understand. I have an Avila (with 64M RAM, half of the CAMBRIA), > also with 3 atheros cards and there it always works. > > But if "options VM_KMEM_SIZE_SCALE=1" keeps the problem away, then I'll > leave that in my kernel. :-) > > Thanks for everyone that helped. > > John > -- > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 8 02:23:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D218A6F6; Tue, 8 Jul 2014 02:23:10 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 714272D61; Tue, 8 Jul 2014 02:23:09 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s682MLjQ087897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 8 Jul 2014 10:22:22 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s682MLln087896; Tue, 8 Jul 2014 10:22:21 +0800 (CST) (envelope-from kevlo) Date: Tue, 8 Jul 2014 10:22:20 +0800 From: Kevin Lo To: Adrian Chadd Subject: Re: TP-LINK TL-WN821N Message-ID: <20140708022220.GA87876@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: Carlos Jacobo Puga Medina , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 02:23:10 -0000 On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote: > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > On Mon, 7 Jul 2014 11:48:36 -0700 > > Adrian Chadd wrote: > > > >> I'd just look at porting over the openbsd driver. There's no 11n > >> support in the openbsd code though! > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > What do you recommend to do? > > I'd be happy if the driver showed up from OpenBSD. We can always try > to add 11n support. > > I'm sorry, I don't have much else to say at the moment and as my day > job is decidedly not wireless, I can't be much help. :( I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with latest OpenBSD snapshot (2014/07/06). It seems to me that there's a problem with otus(4). dmesg: otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2 otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc ifconfig otus0 scan doesn't yield any result. # ifconfig otus0 scan otus0: flags=28802 mtu 1500 lladdr 00:22:b0:57:fc:dc priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid "" none # > -a Kevin From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 8 10:54:23 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F9303E7; Tue, 8 Jul 2014 10:54:23 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com (erelay1.ox.registrar-servers.com [192.64.117.126]) by mx1.freebsd.org (Postfix) with ESMTP id 04D1924FD; Tue, 8 Jul 2014 10:54:22 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id E67812204B4D; Tue, 8 Jul 2014 10:46:02 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dcKg7dRtC4FA; Tue, 8 Jul 2014 06:46:02 -0400 (EDT) Received: from imap2.ox.privateemail.com (imap2.ox.privateemail.com [198.187.29.234]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 256532204A80; Tue, 8 Jul 2014 06:46:02 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id A0E008C007D; Tue, 8 Jul 2014 06:46:01 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap2.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap2.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ogeYhxKFbF6o; Tue, 8 Jul 2014 06:46:01 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 87E988C007B; Tue, 8 Jul 2014 06:46:00 -0400 (EDT) Date: Tue, 8 Jul 2014 12:45:50 +0200 From: Carlos Jacobo Puga Medina To: Kevin Lo Subject: Re: TP-LINK TL-WN821N Message-Id: <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> In-Reply-To: <20140708022220.GA87876@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 10:54:23 -0000 On Tue, 8 Jul 2014 10:22:20 +0800 Kevin Lo wrote: > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote: > > > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > > On Mon, 7 Jul 2014 11:48:36 -0700 > > > Adrian Chadd wrote: > > > > > >> I'd just look at porting over the openbsd driver. There's no 11n > > >> support in the openbsd code though! > > > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > > > What do you recommend to do? > > > > I'd be happy if the driver showed up from OpenBSD. We can always try > > to add 11n support. > > > > I'm sorry, I don't have much else to say at the moment and as my day > > job is decidedly not wireless, I can't be much help. :( > > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with > latest OpenBSD snapshot (2014/07/06). It seems to me that there's a > problem with otus(4). > > dmesg: > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2 > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc > > ifconfig otus0 scan doesn't yield any result. > > # ifconfig otus0 scan > otus0: flags=28802 mtu 1500 > lladdr 00:22:b0:57:fc:dc > priority: 4 > groups: wlan > media: IEEE802.11 autoselect > status: no network > ieee80211: nwid "" > none > # > > > -a > > Kevin Hi, OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g mode for now. So this could be chew better if we work together with them. Anyway if you don't mind I'll send you some outputs from TL-WN821N. Regards, -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 8 16:54:42 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C7A931E; Tue, 8 Jul 2014 16:54:42 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id C9CC128AA; Tue, 8 Jul 2014 16:54:41 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id B3790B84A; Tue, 8 Jul 2014 18:54:38 +0200 (SAST) Date: Tue, 8 Jul 2014 18:54:38 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140708165438.GA83704@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , Ian Lepore , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 16:54:42 -0000 On Mon, Jul 07, 2014 at 12:43:17PM -0700, Adrian Chadd wrote: > Sweet! > > Can you run the same commands above on the Avila board? :~ # uname -a FreeBSD broken-2 11.0-CURRENT FreeBSD 11.0-CURRENT #74 r267954M: Fri Jun 27 14:40:34 SAST 2014 jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/SMALL-AVILA arm :~ # sysctl -a | grep hw | grep mem hw.physmem: 61087744 hw.usermem: 41558016 hw.realmem: 67104768 :~ # sysctl -a | grep maxmbuf kern.ipc.maxmbufmem: 9934848 I'm still confused that the Avila with half the RAM does not exhibit the same problem. > > Would you mind filing a PR to ensure we get that option into the > relevant kernel(s) ? Sure, give me a day or two. John > > (I'm kinda tempted to suggest we auto-select the scaling factor at > startup depending upon physical RAM .. ) > > > -a > > > On 7 July 2014 12:32, John Hay wrote: > > On Mon, Jul 07, 2014 at 11:59:03AM -0700, hiren panchasara wrote: > >> On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd wrote: > >> > On 7 July 2014 11:28, John Hay wrote: > >> >> On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: > >> >>> On 7 July 2014 10:12, Ian Lepore wrote: > >> >>> > On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: > >> >>> >> hi, > >> >>> >> > >> >>> >> That call is returning ENOMEM. I'm not sure why. It allocated an mbuf > >> >>> >> fine, but it couldn't allocate the DMA map. > >> >>> >> > >> >>> >> What's the output of "vmstat -z" ? I wonder if it's failing an allocation. > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> -a > >> >>> > > >> >>> > Lack of bounce buffers is a posibility that won't show up in vmstat > >> >>> > output. > >> >>> > >> >>> right, but there's a bunch of already failing vmstat entries. > >> >>> > >> >>> > >> >>> John - there's a vmscale parameter somewhere. Hiren had to drop it > >> >>> down for his APs to work in 64MB of RAM. I think it's > >> >>> vm.kmem_size_scale . What's it say for you? > >> >>> > >> >> > >> >> :~ # sysctl vm.kmem_size_scale > >> >> vm.kmem_size_scale: 3 > >> > > >> > Ok. Search the archives for an email from Hiren titled "mbuf autotuning effect". > >> > > >> > TL;DR - set it to 1 and recompile. There's a kernel option somewhere > >> > to do exactly that. > >> > >> Yes. http://lists.freebsd.org/pipermail/freebsd-mips/2013-September/003081.html > >> > >> I went through this for my tplink. > >> > >> John, can you show o/p of: > >> > >> sysctl -a | grep hw | grep mem > >> and > >> sysctl -a | grep maxmbuf > > > > I already compiled a new kernel with "options VM_KMEM_SIZE_SCALE=1" and > > the problems went away. :-) On the new kernel the output is: > > > > ########################## > > :~ # sysctl -a | grep hw | grep mem > > hw.physmem: 128196608 > > hw.usermem: 103845888 > > hw.realmem: 134213632 > > :~ # sysctl -a | grep maxmbuf > > kern.ipc.maxmbufmem: 62705664 > > ########################## > > > > I rebooted with the old kernel and its output is: > > > > ########################## > > :~ # sysctl -a | grep hw | grep mem > > hw.physmem: 128196608 > > hw.usermem: 104124416 > > hw.realmem: 134213632 > > :~ # sysctl -a | grep maxmbuf > > kern.ipc.maxmbufmem: 20901888 > > ########################## > > > > So for the heck of it, I ran my script again and this time it successfully > > configured the 3 atheros interfaces. ? How can that be? One other thing I > > also do not understand. I have an Avila (with 64M RAM, half of the CAMBRIA), > > also with 3 atheros cards and there it always works. > > > > But if "options VM_KMEM_SIZE_SCALE=1" keeps the problem away, then I'll > > leave that in my kernel. :-) > > > > Thanks for everyone that helped. > > > > John > > -- > > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 8 17:06:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E84B748; Tue, 8 Jul 2014 17:06:55 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC8A829BA; Tue, 8 Jul 2014 17:06:54 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id j5so5223882qga.37 for ; Tue, 08 Jul 2014 10:06:53 -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=mWJ3cQ+VW5dE/0zm2GWbmaJK4Ol7uAY+0BjkBqDhbSA=; b=uz7mdUK/JXPz5L5UNOJlI0zm3nJ34qgpoyl03WYZG/ULdZjpNEIkTJMjVLCjHn5Usn xIHxaavv2omXNtuGgW1NX4dgNR3PjE5Wsw9iqzNVrf1yqz2pJEmYG7HpC0ecfoGBHS4F AMdiTqlldIfyOWy0RjII3PyOOUsWaQO2NEUAFEJq45ZCUKMbBekuyQpt6mE0cz2esZav zSvFTPxIvyyH8sDz/mzJVLQtN6w9JC9RI7A58kvYkZBUHyMduicZ7HSlhortB4CTcpA0 f1qzAep8YGihLs4xAF5LFt2j6lNtFbGeGC0LfdJTZNONe+O7p0drJ9kb0cd1QqpXelHf geqA== MIME-Version: 1.0 X-Received: by 10.140.19.109 with SMTP id 100mr59080926qgg.80.1404839213829; Tue, 08 Jul 2014 10:06:53 -0700 (PDT) Received: by 10.96.73.39 with HTTP; Tue, 8 Jul 2014 10:06:53 -0700 (PDT) In-Reply-To: <20140708165438.GA83704@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> Date: Tue, 8 Jul 2014 10:06:53 -0700 Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: hiren panchasara To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 17:06:55 -0000 On Tue, Jul 8, 2014 at 9:54 AM, John Hay wrote: > On Mon, Jul 07, 2014 at 12:43:17PM -0700, Adrian Chadd wrote: >> Sweet! >> >> Can you run the same commands above on the Avila board? > > :~ # uname -a > FreeBSD broken-2 11.0-CURRENT FreeBSD 11.0-CURRENT #74 r267954M: Fri Jun 27 14:40:34 SAST 2014 jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/SMALL-AVILA arm > :~ # sysctl -a | grep hw | grep mem > hw.physmem: 61087744 > hw.usermem: 41558016 > hw.realmem: 67104768 > :~ # sysctl -a | grep maxmbuf > kern.ipc.maxmbufmem: 9934848 > > I'm still confused that the Avila with half the RAM does not exhibit the > same problem. Try to compare both KERNCONFs to see if you've anything special for Avila. (I assume that you are doing same things with both boards wrt your experimentation.) cheers, Hiren > >> >> Would you mind filing a PR to ensure we get that option into the >> relevant kernel(s) ? > > Sure, give me a day or two. > > John > From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 9 04:46:17 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E37160D; Wed, 9 Jul 2014 04:46:17 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id CF88B2EAF; Wed, 9 Jul 2014 04:46:16 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 71B86B84A; Wed, 9 Jul 2014 06:46:12 +0200 (SAST) Date: Wed, 9 Jul 2014 06:46:12 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140709044612.GA51378@zibbi.meraka.csir.co.za> References: <20140707142538.GA43661@zibbi.meraka.csir.co.za> <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140708165438.GA83704@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 04:46:17 -0000 Hi Guys, The problem is back / still there. I initially saw the problem during boot, with the interface configs in rc.conf, but because it is so mixed with the rest, I took it out and put it in the script, then after multi-user boot was finished, I did a login and ran the script, with the output I showed in the initial post. So I put the interface configs back into rc.conf and I'm seeing the same problem, here is a cut during boot: ############### Starting file system checks: /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) Mounting local file systems:. Writing entropy file:. Setting hostname: tst-cambria-11. wlan0: Ethernet address: 00:21:a4:35:70:42 wlan1: Ethernet address: 00:21:a4:35:6c:96 ath1: unable to start recv logic wlan2: Ethernet address: 00:21:a4:32:38:c2 ath2: unable to start recv logic ############### Looking at the vmstat -z output the 256 Bucket fail is much higher than if I let it boot to multiuser and then configured the interfaces. It was in the 6000, while now it is much higher: Without wlan configs in rc.conf, but configured afterwards: 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 vmem btag: 28, 0, 4496, 256, 4496, 32, 0 With wlan configs in rc.conf: 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 vmem btag: 28, 0, 4405, 59, 4405, 30, 0 Both of them boot from a ro compact-flash with md /etc and /var, but they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but that did not make a difference. So where do I look from here? Regards John -- John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 9 10:03:22 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53003963; Wed, 9 Jul 2014 10:03:22 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE1EF2974; Wed, 9 Jul 2014 10:03:21 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s69A2UhP006750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 9 Jul 2014 18:02:31 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s69A2TFW006749; Wed, 9 Jul 2014 18:02:29 +0800 (CST) (envelope-from kevlo) Date: Wed, 9 Jul 2014 18:02:29 +0800 From: Kevin Lo To: Carlos Jacobo Puga Medina Subject: Re: TP-LINK TL-WN821N Message-ID: <20140709100229.GA6733@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 10:03:22 -0000 On Tue, Jul 08, 2014 at 12:45:50PM +0200, Carlos Jacobo Puga Medina wrote: > > On Tue, 8 Jul 2014 10:22:20 +0800 > Kevin Lo wrote: > > > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote: > > > > > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > > > On Mon, 7 Jul 2014 11:48:36 -0700 > > > > Adrian Chadd wrote: > > > > > > > >> I'd just look at porting over the openbsd driver. There's no 11n > > > >> support in the openbsd code though! > > > > > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > > > > > What do you recommend to do? > > > > > > I'd be happy if the driver showed up from OpenBSD. We can always try > > > to add 11n support. > > > > > > I'm sorry, I don't have much else to say at the moment and as my day > > > job is decidedly not wireless, I can't be much help. :( > > > > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with > > latest OpenBSD snapshot (2014/07/06). It seems to me that there's a > > problem with otus(4). > > > > dmesg: > > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2 > > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc > > > > ifconfig otus0 scan doesn't yield any result. > > > > # ifconfig otus0 scan > > otus0: flags=28802 mtu 1500 > > lladdr 00:22:b0:57:fc:dc > > priority: 4 > > groups: wlan > > media: IEEE802.11 autoselect > > status: no network > > ieee80211: nwid "" > > none > > # > > > > > -a > > > > Kevin > > Hi, > > OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g mode for now. So this could be chew better if we work together with them. All OpenBSD wireless drivers don't support .11n yet. What I mean is that driver is not stable. At least for D-Link DWA-160 rev. A1. > Anyway if you don't mind I'll send you some outputs from TL-WN821N. No, I don't mind. :-) Thanks. > Regards, > -- > Carlos Jacobo Puga Medina Kevin From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 9 10:10:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8FC74BB4 for ; Wed, 9 Jul 2014 10:10:53 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 589CC2A21 for ; Wed, 9 Jul 2014 10:10:53 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8cc3:e5a9:fcf2:1e1c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 1898B4AC13 for ; Wed, 9 Jul 2014 14:10:50 +0400 (MSK) Date: Wed, 9 Jul 2014 14:10:43 +0400 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1457767975.20140709141043@serebryakov.spb.ru> To: freebsd-wireless@freebsd.org Subject: Any chances to have FreeBSD on TP-Link TL-MR3420 v2 (white one)? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 10:10:53 -0000 Hello, Freebsd-wireless. $subj? Or is it too small for FreeBSD AP + DHCPD + 3G Modem driver? Native firmware works not so well :( -- // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 9 13:42:44 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7257DD20; Wed, 9 Jul 2014 13:42:44 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com (erelay1.ox.registrar-servers.com [192.64.117.126]) by mx1.freebsd.org (Postfix) with ESMTP id 477A72ED7; Wed, 9 Jul 2014 13:42:43 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id D71032204BDE; Wed, 9 Jul 2014 13:42:37 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id TenGSmtwKUSl; Wed, 9 Jul 2014 09:42:36 -0400 (EDT) Received: from imap1.ox.privateemail.com (imap1.ox.privateemail.com [198.187.29.233]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id B803F2204BD1; Wed, 9 Jul 2014 09:42:36 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 50C6AB00085; Wed, 9 Jul 2014 09:42:36 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap1.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap1.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id avx4UQfc6Fkq; Wed, 9 Jul 2014 09:42:36 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 2478CB00081; Wed, 9 Jul 2014 09:42:34 -0400 (EDT) Date: Wed, 9 Jul 2014 15:42:23 +0200 From: Carlos Jacobo Puga Medina To: Kevin Lo Subject: Re: TP-LINK TL-WN821N Message-Id: <20140709154223.9623a93c2d458dc32339b554@fbsd.es> In-Reply-To: <20140709100229.GA6733@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> <20140709100229.GA6733@ns.kevlo.org> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 13:42:44 -0000 On Wed, 9 Jul 2014 18:02:29 +0800 Kevin Lo wrote: > On Tue, Jul 08, 2014 at 12:45:50PM +0200, Carlos Jacobo Puga Medina wrote: > > > > On Tue, 8 Jul 2014 10:22:20 +0800 > > Kevin Lo wrote: > > > > > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote: > > > > > > > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > > > > On Mon, 7 Jul 2014 11:48:36 -0700 > > > > > Adrian Chadd wrote: > > > > > > > > > >> I'd just look at porting over the openbsd driver. There's no 11n > > > > >> support in the openbsd code though! > > > > > > > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > > > > > > > What do you recommend to do? > > > > > > > > I'd be happy if the driver showed up from OpenBSD. We can always try > > > > to add 11n support. > > > > > > > > I'm sorry, I don't have much else to say at the moment and as my day > > > > job is decidedly not wireless, I can't be much help. :( > > > > > > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with > > > latest OpenBSD snapshot (2014/07/06). It seems to me that there's a > > > problem with otus(4). > > > > > > dmesg: > > > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2 > > > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc > > > > > > ifconfig otus0 scan doesn't yield any result. > > > > > > # ifconfig otus0 scan > > > otus0: flags=28802 mtu 1500 > > > lladdr 00:22:b0:57:fc:dc > > > priority: 4 > > > groups: wlan > > > media: IEEE802.11 autoselect > > > status: no network > > > ieee80211: nwid "" > > > none > > > # > > > > > > > -a > > > > > > Kevin > > > > Hi, > > > > OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g mode for now. So this could be chew better if we work together with them. > > All OpenBSD wireless drivers don't support .11n yet. > What I mean is that driver is not stable. At least for D-Link DWA-160 rev. A1. > > > Anyway if you don't mind I'll send you some outputs from TL-WN821N. > > No, I don't mind. :-) Thanks. > > > Regards, > > -- > > Carlos Jacobo Puga Medina > > Kevin I'm testing a TL-WN821N v4 device. # uname -a FreeBSD box.underbuild.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268070: Tue Jul 1 14:05:40 CEST 2014 root@box.underbuild.com:/usr/obj/usr/src/sys/PROD i386 # dmesg | grep urtwn0 urtwn0: on usbus2 urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R urtwn0: timeout waiting for firmware readiness # usbconfig -u 2 -a 3 dump_device_desc ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0bda idProduct = 0x8178 bcdDevice = 0x0200 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 # ifconfig urtwn0 urtwn0: flags=8803 metric 0 mtu 2290 ether 10:fe:ed:27:f6:5d nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated I noticed that wireless never goes up. Not much luck here, I get the error: urtwn0: timeout waiting for firmware readiness -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 9 15:39:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7941454B; Wed, 9 Jul 2014 15:39:47 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59B872B83; Wed, 9 Jul 2014 15:39:46 +0000 (UTC) Received: from [192.168.200.204] (c-50-131-5-126.hsd1.ca.comcast.net [50.131.5.126]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id D78A3193DD9; Wed, 9 Jul 2014 15:39:45 +0000 (UTC) Subject: Re: Any chances to have FreeBSD on TP-Link TL-MR3420 v2 (white one)? From: Sean Bruno Reply-To: sbruno@freebsd.org To: lev@FreeBSD.org In-Reply-To: <1457767975.20140709141043@serebryakov.spb.ru> References: <1457767975.20140709141043@serebryakov.spb.ru> Content-Type: text/plain; charset="us-ascii" Date: Wed, 09 Jul 2014 08:39:45 -0700 Message-ID: <1404920385.7725.2.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 15:39:47 -0000 On Wed, 2014-07-09 at 14:10 +0400, Lev Serebryakov wrote: > Hello, Freebsd-wireless. > > $subj? Or is it too small for FreeBSD AP + DHCPD + 3G Modem driver? > Native firmware works not so well :( > Looking at what wikidevi says, there's a good chance that you can get it working. https://wikidevi.com/wiki/TP-LINK_TL-MR3420_v2 Its atheros mips, AR9341 which means it can likely be made to boot. The 4M of flash however is super small, I haven't been able to squash a kernel/ramdisk to that size. (worked on the mr3020 a bit, and had to resort to a 4G usb disk for root). sean From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 10 04:02:36 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C2991DB3; Thu, 10 Jul 2014 04:02:36 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id ED4C32C50; Thu, 10 Jul 2014 04:02:35 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 8E9E6B842; Thu, 10 Jul 2014 06:02:27 +0200 (SAST) Date: Thu, 10 Jul 2014 06:02:27 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140710040227.GA73872@zibbi.meraka.csir.co.za> References: <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140709044612.GA51378@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 04:02:37 -0000 On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > Hi Guys, > > The problem is back / still there. I initially saw the problem during > boot, with the interface configs in rc.conf, but because it is so > mixed with the rest, I took it out and put it in the script, then > after multi-user boot was finished, I did a login and ran the script, > with the output I showed in the initial post. > > So I put the interface configs back into rc.conf and I'm seeing the > same problem, here is a cut during boot: > > ############### > Starting file system checks: > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > Mounting local file systems:. > Writing entropy file:. > Setting hostname: tst-cambria-11. > wlan0: Ethernet address: 00:21:a4:35:70:42 > wlan1: Ethernet address: 00:21:a4:35:6c:96 > ath1: unable to start recv logic > wlan2: Ethernet address: 00:21:a4:32:38:c2 > ath2: unable to start recv logic > ############### > > Looking at the vmstat -z output the 256 Bucket fail is much higher than > if I let it boot to multiuser and then configured the interfaces. It > was in the 6000, while now it is much higher: > > Without wlan configs in rc.conf, but configured afterwards: > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > > With wlan configs in rc.conf: > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > > Both of them boot from a ro compact-flash with md /etc and /var, but > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > that did not make a difference. > I forgot to add my rc.conf. Maybe that will give a clue? ############## hostname="tst-cambria-11" wlans_ath0="wlan0" create_args_wlan0="wlanmode adhoc country ZA" ifconfig_wlan0_ipv6="inet6 auto_linklocal" wlans_ath1="wlan1" create_args_wlan1="wlanmode adhoc country ZA" ifconfig_wlan1_ipv6="inet6 auto_linklocal" wlans_ath2="wlan2" create_args_wlan2="wlanmode adhoc country ZA" ifconfig_wlan2_ipv6="inet6 auto_linklocal" ifconfig_npe0_ipv6="inet6 auto_linklocal" ifconfig_wlan0="-bgscan channel 140 ssid mesh bssid 02:8c:ca:fe:ca:00" ifconfig_wlan1="-bgscan channel 136 ssid mesh bssid 02:88:ca:fe:ca:00" ifconfig_wlan2="-bgscan channel 13 ssid hotspot bssid 02:0d:ca:fe:ca:00" ipv6_prefix_wlan0="fd35:ac5b:b116:10" ipv6_prefix_wlan1="fd35:ac5b:b116:10" ipv6_prefix_wlan2="fd35:ac5b:b116:38f4" ipv4_addrs_wlan2="10.56.244.1/24" ipv6_prefix_npe0="fd35:ac5b:b116:ee99" ipv4_addrs_npe0="10.238.153.1/24" varsize=5120 olsr_enable="NO" sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" devd_enable="NO" hostid_enable="NO" mixer_enable="NO" casperd_enable="NO" ######################## I checked booting with the above rc.conf that fails the second and third wlan, even if I then login and ifconfig destroy the wlans and run my script to configure them, they still fail. So why would the creation and configuration of the wlan interfaces work if it is not done during the boot, but after multi-user is reached? Regards John -- John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 10 05:06:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43C19478; Thu, 10 Jul 2014 05:06:14 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D254E20D8; Thu, 10 Jul 2014 05:06:13 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s6A55QmT014455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Jul 2014 13:05:27 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s6A55O2x014454; Thu, 10 Jul 2014 13:05:24 +0800 (CST) (envelope-from kevlo) Date: Thu, 10 Jul 2014 13:05:24 +0800 From: Kevin Lo To: Carlos Jacobo Puga Medina Subject: Re: TP-LINK TL-WN821N Message-ID: <20140710050524.GA14437@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> <20140709100229.GA6733@ns.kevlo.org> <20140709154223.9623a93c2d458dc32339b554@fbsd.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140709154223.9623a93c2d458dc32339b554@fbsd.es> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 05:06:14 -0000 On Wed, Jul 09, 2014 at 03:42:23PM +0200, Carlos Jacobo Puga Medina wrote: > > On Wed, 9 Jul 2014 18:02:29 +0800 > Kevin Lo wrote: > > > On Tue, Jul 08, 2014 at 12:45:50PM +0200, Carlos Jacobo Puga Medina wrote: > > > > > > On Tue, 8 Jul 2014 10:22:20 +0800 > > > Kevin Lo wrote: > > > > > > > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote: > > > > > > > > > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > > > > > On Mon, 7 Jul 2014 11:48:36 -0700 > > > > > > Adrian Chadd wrote: > > > > > > > > > > > >> I'd just look at porting over the openbsd driver. There's no 11n > > > > > >> support in the openbsd code though! > > > > > > > > > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > > > > > > > > > What do you recommend to do? > > > > > > > > > > I'd be happy if the driver showed up from OpenBSD. We can always try > > > > > to add 11n support. > > > > > > > > > > I'm sorry, I don't have much else to say at the moment and as my day > > > > > job is decidedly not wireless, I can't be much help. :( > > > > > > > > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with > > > > latest OpenBSD snapshot (2014/07/06). It seems to me that there's a > > > > problem with otus(4). > > > > > > > > dmesg: > > > > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2 > > > > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc > > > > > > > > ifconfig otus0 scan doesn't yield any result. > > > > > > > > # ifconfig otus0 scan > > > > otus0: flags=28802 mtu 1500 > > > > lladdr 00:22:b0:57:fc:dc > > > > priority: 4 > > > > groups: wlan > > > > media: IEEE802.11 autoselect > > > > status: no network > > > > ieee80211: nwid "" > > > > none > > > > # > > > > > > > > > -a > > > > > > > > Kevin > > > > > > Hi, > > > > > > OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g mode for now. So this could be chew better if we work together with them. > > > > All OpenBSD wireless drivers don't support .11n yet. > > What I mean is that driver is not stable. At least for D-Link DWA-160 rev. A1. > > > > > Anyway if you don't mind I'll send you some outputs from TL-WN821N. > > > > No, I don't mind. :-) Thanks. > > > > > Regards, > > > -- > > > Carlos Jacobo Puga Medina > > > > Kevin > > I'm testing a TL-WN821N v4 device. Wait a minute. You mentioned OpenBSD otus(4), I thought we were talking about the Atheros AR9170 chipset, not the Realtek RTL8192CU chip. > # uname -a > FreeBSD box.underbuild.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268070: Tue Jul 1 14:05:40 CEST 2014 root@box.underbuild.com:/usr/obj/usr/src/sys/PROD i386 > > # dmesg | grep urtwn0 > urtwn0: on usbus2 > urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R > urtwn0: timeout waiting for firmware readiness > > # usbconfig -u 2 -a 3 dump_device_desc > ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0bda > idProduct = 0x8178 > bcdDevice = 0x0200 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > # ifconfig urtwn0 > urtwn0: flags=8803 metric 0 mtu 2290 > ether 10:fe:ed:27:f6:5d > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > > I noticed that wireless never goes up. Not much luck here, I get the error: > urtwn0: timeout waiting for firmware readiness Ok, I know where the problem lies. Please try this patch, thanks. Index: sys/dev/usb/wlan/if_urtwn.c =================================================================== --- sys/dev/usb/wlan/if_urtwn.c (revision 268479) +++ sys/dev/usb/wlan/if_urtwn.c (working copy) @@ -2281,9 +2281,6 @@ urtwn_fw_reset(struct urtwn_softc *sc) } /* Force 8051 reset. */ urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN); - urtwn_write_2(sc, R92C_SYS_FUNC_EN, - urtwn_read_2(sc, R92C_SYS_FUNC_EN) | - R92C_SYS_FUNC_EN_CPUEN); } static void @@ -2383,6 +2380,11 @@ urtwn_load_firmware(struct urtwn_softc *sc) urtwn_write_1(sc, R92C_MCUFWDL, 0); } + if (!(sc->chip & URTWN_CHIP_88E)) { + urtwn_write_2(sc, R92C_SYS_FUNC_EN, + urtwn_read_2(sc, R92C_SYS_FUNC_EN) | + R92C_SYS_FUNC_EN_CPUEN); + } urtwn_write_1(sc, R92C_MCUFWDL, urtwn_read_1(sc, R92C_MCUFWDL) | R92C_MCUFWDL_EN); urtwn_write_1(sc, R92C_MCUFWDL + 2, From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 10 07:14:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0089D8CE; Thu, 10 Jul 2014 07:13:59 +0000 (UTC) Received: from erelay6.ox.registrar-servers.com (erelay6.ox.registrar-servers.com [192.64.117.97]) by mx1.freebsd.org (Postfix) with ESMTP id C76472A56; Thu, 10 Jul 2014 07:13:59 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 85C10220502F; Thu, 10 Jul 2014 07:13:57 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Mqt_WwpnrC7N; Thu, 10 Jul 2014 03:13:56 -0400 (EDT) Received: from imap10.ox.privateemail.com (imap10.ox.privateemail.com [192.64.116.221]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 40BE32205027; Thu, 10 Jul 2014 03:13:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id D8D6A2400C2; Thu, 10 Jul 2014 03:13:55 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AB7gfhmmtiFS; Thu, 10 Jul 2014 03:13:55 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id CCD7C2400C3; Thu, 10 Jul 2014 03:13:54 -0400 (EDT) Date: Thu, 10 Jul 2014 09:13:42 +0200 From: Carlos Jacobo Puga Medina To: Kevin Lo Subject: Re: TP-LINK TL-WN821N Message-Id: <20140710091342.e769692dd5edf94bec3cbc61@fbsd.es> In-Reply-To: <20140710050524.GA14437@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> <20140709100229.GA6733@ns.kevlo.org> <20140709154223.9623a93c2d458dc32339b554@fbsd.es> <20140710050524.GA14437@ns.kevlo.org> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 07:14:00 -0000 On Thu, 10 Jul 2014 13:05:24 +0800 Kevin Lo wrote: > On Wed, Jul 09, 2014 at 03:42:23PM +0200, Carlos Jacobo Puga Medina wrote: > > > > On Wed, 9 Jul 2014 18:02:29 +0800 > > Kevin Lo wrote: > > > > > On Tue, Jul 08, 2014 at 12:45:50PM +0200, Carlos Jacobo Puga Medina wrote: > > > > > > > > On Tue, 8 Jul 2014 10:22:20 +0800 > > > > Kevin Lo wrote: > > > > > > > > > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote: > > > > > > > > > > > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina wrote: > > > > > > > On Mon, 7 Jul 2014 11:48:36 -0700 > > > > > > > Adrian Chadd wrote: > > > > > > > > > > > > > >> I'd just look at porting over the openbsd driver. There's no 11n > > > > > > >> support in the openbsd code though! > > > > > > > > > > > > > > That's bad, I hope that the 802.11n protocol will be implemented since it was released in 2009. > > > > > > > > > > > > > > What do you recommend to do? > > > > > > > > > > > > I'd be happy if the driver showed up from OpenBSD. We can always try > > > > > > to add 11n support. > > > > > > > > > > > > I'm sorry, I don't have much else to say at the moment and as my day > > > > > > job is decidedly not wireless, I can't be much help. :( > > > > > > > > > > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with > > > > > latest OpenBSD snapshot (2014/07/06). It seems to me that there's a > > > > > problem with otus(4). > > > > > > > > > > dmesg: > > > > > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2 > > > > > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc > > > > > > > > > > ifconfig otus0 scan doesn't yield any result. > > > > > > > > > > # ifconfig otus0 scan > > > > > otus0: flags=28802 mtu 1500 > > > > > lladdr 00:22:b0:57:fc:dc > > > > > priority: 4 > > > > > groups: wlan > > > > > media: IEEE802.11 autoselect > > > > > status: no network > > > > > ieee80211: nwid "" > > > > > none > > > > > # > > > > > > > > > > > -a > > > > > > > > > > Kevin > > > > > > > > Hi, > > > > > > > > OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g mode for now. So this could be chew better if we work together with them. > > > > > > All OpenBSD wireless drivers don't support .11n yet. > > > What I mean is that driver is not stable. At least for D-Link DWA-160 rev. A1. > > > > > > > Anyway if you don't mind I'll send you some outputs from TL-WN821N. > > > > > > No, I don't mind. :-) Thanks. > > > > > > > Regards, > > > > -- > > > > Carlos Jacobo Puga Medina > > > > > > Kevin > > > > I'm testing a TL-WN821N v4 device. > > Wait a minute. You mentioned OpenBSD otus(4), I thought we were talking > about the Atheros AR9170 chipset, not the Realtek RTL8192CU chip. Oops, I forgot mentioned that v4 use the Realtek RTL8192CU chipset. https://wikidevi.com/wiki/TP-LINK_TL-WN821N_v4 > > > # uname -a > > FreeBSD box.underbuild.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268070: Tue Jul 1 14:05:40 CEST 2014 root@box.underbuild.com:/usr/obj/usr/src/sys/PROD i386 > > > > # dmesg | grep urtwn0 > > urtwn0: on usbus2 > > urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R > > urtwn0: timeout waiting for firmware readiness > > > > # usbconfig -u 2 -a 3 dump_device_desc > > ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) > > > > bLength = 0x0012 > > bDescriptorType = 0x0001 > > bcdUSB = 0x0200 > > bDeviceClass = 0x0000 > > bDeviceSubClass = 0x0000 > > bDeviceProtocol = 0x0000 > > bMaxPacketSize0 = 0x0040 > > idVendor = 0x0bda > > idProduct = 0x8178 > > bcdDevice = 0x0200 > > iManufacturer = 0x0001 > > iProduct = 0x0002 > > iSerialNumber = 0x0003 > > bNumConfigurations = 0x0001 > > > > # ifconfig urtwn0 > > urtwn0: flags=8803 metric 0 mtu 2290 > > ether 10:fe:ed:27:f6:5d > > nd6 options=21 > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > status: associated > > > > I noticed that wireless never goes up. Not much luck here, I get the error: > > urtwn0: timeout waiting for firmware readiness > > Ok, I know where the problem lies. Please try this patch, thanks. > > Index: sys/dev/usb/wlan/if_urtwn.c > =================================================================== > --- sys/dev/usb/wlan/if_urtwn.c (revision 268479) > +++ sys/dev/usb/wlan/if_urtwn.c (working copy) > @@ -2281,9 +2281,6 @@ urtwn_fw_reset(struct urtwn_softc *sc) > } > /* Force 8051 reset. */ > urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN); > - urtwn_write_2(sc, R92C_SYS_FUNC_EN, > - urtwn_read_2(sc, R92C_SYS_FUNC_EN) | > - R92C_SYS_FUNC_EN_CPUEN); > } > > static void > @@ -2383,6 +2380,11 @@ urtwn_load_firmware(struct urtwn_softc *sc) > urtwn_write_1(sc, R92C_MCUFWDL, 0); > } > > + if (!(sc->chip & URTWN_CHIP_88E)) { > + urtwn_write_2(sc, R92C_SYS_FUNC_EN, > + urtwn_read_2(sc, R92C_SYS_FUNC_EN) | > + R92C_SYS_FUNC_EN_CPUEN); > + } > urtwn_write_1(sc, R92C_MCUFWDL, > urtwn_read_1(sc, R92C_MCUFWDL) | R92C_MCUFWDL_EN); > urtwn_write_1(sc, R92C_MCUFWDL + 2, I'm just rebuilding the kernel. -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 10 09:24:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5AFCC5AA; Thu, 10 Jul 2014 09:24:00 +0000 (UTC) Received: from erelay6.ox.registrar-servers.com (erelay6.ox.registrar-servers.com [192.64.117.97]) by mx1.freebsd.org (Postfix) with ESMTP id 2EACD2535; Thu, 10 Jul 2014 09:23:59 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 904BD2205082; Thu, 10 Jul 2014 09:23:58 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KuKcHmsNX_NK; Thu, 10 Jul 2014 05:23:57 -0400 (EDT) Received: from imap1.ox.privateemail.com (imap1.ox.privateemail.com [198.187.29.233]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id C4AA72205071; Thu, 10 Jul 2014 05:23:57 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 5C6FBB0007B; Thu, 10 Jul 2014 05:23:57 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap1.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap1.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HAjgvW2RErvq; Thu, 10 Jul 2014 05:23:57 -0400 (EDT) Received: from localhost (110.Red-83-40-60.dynamicIP.rima-tde.net [83.40.60.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id EABB8B00081; Thu, 10 Jul 2014 05:23:55 -0400 (EDT) Date: Thu, 10 Jul 2014 11:23:44 +0200 From: Carlos Jacobo Puga Medina To: Kevin Lo Subject: Re: TP-LINK TL-WN821N Message-Id: <20140710112344.86496b02b2d62197a1e467ba@fbsd.es> In-Reply-To: <20140710050524.GA14437@ns.kevlo.org> References: <20140707144056.351e26df0d1512c6fc48a954@fbsd.es> <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> <20140709100229.GA6733@ns.kevlo.org> <20140709154223.9623a93c2d458dc32339b554@fbsd.es> <20140710050524.GA14437@ns.kevlo.org> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 09:24:00 -0000 On Thu, 10 Jul 2014 13:05:24 +0800 Kevin Lo wrote: > Ok, I know where the problem lies. Please try this patch, thanks. > > Index: sys/dev/usb/wlan/if_urtwn.c > =================================================================== > --- sys/dev/usb/wlan/if_urtwn.c (revision 268479) > +++ sys/dev/usb/wlan/if_urtwn.c (working copy) > @@ -2281,9 +2281,6 @@ urtwn_fw_reset(struct urtwn_softc *sc) > } > /* Force 8051 reset. */ > urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN); > - urtwn_write_2(sc, R92C_SYS_FUNC_EN, > - urtwn_read_2(sc, R92C_SYS_FUNC_EN) | > - R92C_SYS_FUNC_EN_CPUEN); > } > > static void > @@ -2383,6 +2380,11 @@ urtwn_load_firmware(struct urtwn_softc *sc) > urtwn_write_1(sc, R92C_MCUFWDL, 0); > } > > + if (!(sc->chip & URTWN_CHIP_88E)) { > + urtwn_write_2(sc, R92C_SYS_FUNC_EN, > + urtwn_read_2(sc, R92C_SYS_FUNC_EN) | > + R92C_SYS_FUNC_EN_CPUEN); > + } > urtwn_write_1(sc, R92C_MCUFWDL, > urtwn_read_1(sc, R92C_MCUFWDL) | R92C_MCUFWDL_EN); > urtwn_write_1(sc, R92C_MCUFWDL + 2, > > I'm just rebuilding the kernel. It works! Thanks a lot for your help :) # ifconfig -v wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 10:fe:ed:27:f6:5d inet6 fe80::12fe:edff:fe27:f65d%wlan0 prefixlen 64 scopeid 0x4 inet 192.168.1.42 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=23 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid XXXXXXXXXX channel 11 (2462 MHz 11g) bssid f8:8e:85:c7:11:3d regdomain ETSI2 country ES anywhere -ecm authmode WPA -wps -tsn privacy ON deftxkey UNDEF TKIP 2:128-bit powersavemode OFF powersavesleep 100 txpower 30 txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7 11a ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 11b ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 11g ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 turboA ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 turboG ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 sturbo ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 11na ucast NONE mgmt 12 MCS mcast 12 MCS maxretry 6 11ng ucast NONE mgmt 2 MCS mcast 2 MCS maxretry 6 half ucast NONE mgmt 3 Mb/s mcast 3 Mb/s maxretry 6 quarter ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:11a rssi 7dBm rate 12 Mb/s roam:11b rssi 7dBm rate 1 Mb/s roam:11g rssi 7dBm rate 5 Mb/s roam:turboA rssi 7dBm rate 12 Mb/s roam:turboG rssi 7dBm rate 12 Mb/s roam:sturbo rssi 7dBm rate 12 Mb/s roam:11na rssi 7dBm MCS 1 roam:11ng rssi 7dBm MCS 1 roam:half rssi 7dBm rate 6 Mb/s roam:quarter rssi 7dBm rate 3 Mb/s -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 64k ampdudensity 8 -amsdu -shortgi htprotmode RTSCTS -puren -smps -rifs -wme -burst -dwds roaming MANUAL bintval 100 groups: wlan # usbconfig -u 2 -a 3 dump_device_desc ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0bda idProduct = 0x8178 bcdDevice = 0x0200 iManufacturer = 0x0001 <802.11n> iProduct = 0x0002 iSerialNumber = 0x0003 <00e04c000001> bNumConfigurations = 0x0001 # netstat -I urtwn0 Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll urtwn 2290 10:fe:ed:27:f6:5d 0 0 0 1055 0 0 Could you commit this little tweak to -HEAD? Regards, -- Carlos Jacobo Puga Medina From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 10 10:04:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E95D3ED; Thu, 10 Jul 2014 10:04:12 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B56B2889; Thu, 10 Jul 2014 10:04:10 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s6AA3IG7016441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 Jul 2014 18:03:19 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s6AA3InD016440; Thu, 10 Jul 2014 18:03:18 +0800 (CST) (envelope-from kevlo) Date: Thu, 10 Jul 2014 18:03:17 +0800 From: Kevin Lo To: Carlos Jacobo Puga Medina Subject: Re: TP-LINK TL-WN821N Message-ID: <20140710100317.GA16286@ns.kevlo.org> References: <20140707204636.50ae92cf9022cd13263932d3@fbsd.es> <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> <20140709100229.GA6733@ns.kevlo.org> <20140709154223.9623a93c2d458dc32339b554@fbsd.es> <20140710050524.GA14437@ns.kevlo.org> <20140710112344.86496b02b2d62197a1e467ba@fbsd.es> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20140710112344.86496b02b2d62197a1e467ba@fbsd.es> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 10:04:12 -0000 On Thu, Jul 10, 2014 at 11:23:44AM +0200, Carlos Jacobo Puga Medina wrote: > > On Thu, 10 Jul 2014 13:05:24 +0800 > Kevin Lo wrote: > > > Ok, I know where the problem lies. Please try this patch, thanks. > > > > Index: sys/dev/usb/wlan/if_urtwn.c > > =================================================================== > > --- sys/dev/usb/wlan/if_urtwn.c (revision 268479) > > +++ sys/dev/usb/wlan/if_urtwn.c (working copy) > > @@ -2281,9 +2281,6 @@ urtwn_fw_reset(struct urtwn_softc *sc) > > } > > /* Force 8051 reset. */ > > urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN); > > - urtwn_write_2(sc, R92C_SYS_FUNC_EN, > > - urtwn_read_2(sc, R92C_SYS_FUNC_EN) | > > - R92C_SYS_FUNC_EN_CPUEN); > > } > > > > static void > > @@ -2383,6 +2380,11 @@ urtwn_load_firmware(struct urtwn_softc *sc) > > urtwn_write_1(sc, R92C_MCUFWDL, 0); > > } > > > > + if (!(sc->chip & URTWN_CHIP_88E)) { > > + urtwn_write_2(sc, R92C_SYS_FUNC_EN, > > + urtwn_read_2(sc, R92C_SYS_FUNC_EN) | > > + R92C_SYS_FUNC_EN_CPUEN); > > + } > > urtwn_write_1(sc, R92C_MCUFWDL, > > urtwn_read_1(sc, R92C_MCUFWDL) | R92C_MCUFWDL_EN); > > urtwn_write_1(sc, R92C_MCUFWDL + 2, > > > > I'm just rebuilding the kernel. > > It works! Thanks a lot for your help :) Excellent, glad to hear it’s working well for you. > # ifconfig -v wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 10:fe:ed:27:f6:5d > inet6 fe80::12fe:edff:fe27:f65d%wlan0 prefixlen 64 scopeid 0x4 > inet 192.168.1.42 netmask 0xffffff00 broadcast 192.168.1.255 > nd6 options=23 > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g > status: associated > ssid XXXXXXXXXX channel 11 (2462 MHz 11g) bssid f8:8e:85:c7:11:3d > regdomain ETSI2 country ES anywhere -ecm authmode WPA -wps -tsn > privacy ON deftxkey UNDEF > TKIP 2:128-bit powersavemode OFF powersavesleep 100 txpower 30 > txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7 > 11a ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 > 11b ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 > 11g ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 > turboA ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 > turboG ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 > sturbo ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 > 11na ucast NONE mgmt 12 MCS mcast 12 MCS maxretry 6 > 11ng ucast NONE mgmt 2 MCS mcast 2 MCS maxretry 6 > half ucast NONE mgmt 3 Mb/s mcast 3 Mb/s maxretry 6 > quarter ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 > scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 > roam:11a rssi 7dBm rate 12 Mb/s > roam:11b rssi 7dBm rate 1 Mb/s > roam:11g rssi 7dBm rate 5 Mb/s > roam:turboA rssi 7dBm rate 12 Mb/s > roam:turboG rssi 7dBm rate 12 Mb/s > roam:sturbo rssi 7dBm rate 12 Mb/s > roam:11na rssi 7dBm MCS 1 > roam:11ng rssi 7dBm MCS 1 > roam:half rssi 7dBm rate 6 Mb/s > roam:quarter rssi 7dBm rate 3 Mb/s > -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 64k > ampdudensity 8 -amsdu -shortgi htprotmode RTSCTS -puren -smps -rifs > -wme -burst -dwds roaming MANUAL bintval 100 > groups: wlan > > # usbconfig -u 2 -a 3 dump_device_desc > ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0bda > idProduct = 0x8178 > bcdDevice = 0x0200 > iManufacturer = 0x0001 <802.11n> > iProduct = 0x0002 > iSerialNumber = 0x0003 <00e04c000001> > bNumConfigurations = 0x0001 > > # netstat -I urtwn0 > Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll > urtwn 2290 10:fe:ed:27:f6:5d 0 0 0 1055 0 0 > > Could you commit this little tweak to -HEAD? Committed as r268487, thanks. > Regards, > -- > Carlos Jacobo Puga Medina Kevin From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 08:00:23 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09B5DE33 for ; Mon, 14 Jul 2014 08:00:23 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DBC302A7E for ; Mon, 14 Jul 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6E80Mca045621 for ; Mon, 14 Jul 2014 08:00:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201407140800.s6E80Mca045621@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 14 Jul 2014 08:00:22 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 08:00:23 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 08:07:13 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D3DB1FB; Mon, 14 Jul 2014 08:07:13 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7A0202B46; Mon, 14 Jul 2014 08:07:12 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 7C057B842; Mon, 14 Jul 2014 10:07:08 +0200 (SAST) Date: Mon, 14 Jul 2014 10:07:08 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714080708.GA88464@zibbi.meraka.csir.co.za> References: <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140710040227.GA73872@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 08:07:13 -0000 On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: > On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > > Hi Guys, > > > > The problem is back / still there. I initially saw the problem during > > boot, with the interface configs in rc.conf, but because it is so > > mixed with the rest, I took it out and put it in the script, then > > after multi-user boot was finished, I did a login and ran the script, > > with the output I showed in the initial post. > > > > So I put the interface configs back into rc.conf and I'm seeing the > > same problem, here is a cut during boot: > > > > ############### > > Starting file system checks: > > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > > Mounting local file systems:. > > Writing entropy file:. > > Setting hostname: tst-cambria-11. > > wlan0: Ethernet address: 00:21:a4:35:70:42 > > wlan1: Ethernet address: 00:21:a4:35:6c:96 > > ath1: unable to start recv logic > > wlan2: Ethernet address: 00:21:a4:32:38:c2 > > ath2: unable to start recv logic > > ############### > > > > Looking at the vmstat -z output the 256 Bucket fail is much higher than > > if I let it boot to multiuser and then configured the interfaces. It > > was in the 6000, while now it is much higher: > > > > Without wlan configs in rc.conf, but configured afterwards: > > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > > > > With wlan configs in rc.conf: > > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > > > > Both of them boot from a ro compact-flash with md /etc and /var, but > > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > > that did not make a difference. > > Friday I power cycled the board and it came up without an error. All 3 atheros cards configured in rc.conf. So I left it on for the weekend and by this morning there was still no errors, so I rebooted it and again saw the "ath1: unable to start recv logic" message for ath1 and ath2. I power cycled it, but still get the error, so Friday was just lucky with some timing thing, maybe if the card receive while it is still configuring? Also if I leave the board booted in this state, ath0 also start to give problems: ################# ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ... ath0: device timeout ath0: ath_reset: unable to start recv logic ... ################# In anycase it seems that memory allocation problem. How do I figure out where it is? "netstat -m" does not seem to point to an error. The mbuf info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z that point to an alloc failure. How do I figure out where that is and how do I fix it or work around it? ################### tst-11-arm:~ # netstat -m 128/382/510 mbufs in use (current/cache/total) 127/129/256/7654 mbuf clusters in use (current/cache/total/max) 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) 286K/353K/639K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/3/1488 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile tst-11-arm:~ # vmstat -z | grep mbuf mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 mbuf: 256, 48990, 1, 256, 920, 0, 0 mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 tst-11-arm:~ # vmstat -z | grep Bucket 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 6 Bucket: 24, 0, 0, 0, 0, 0, 0 8 Bucket: 32, 0, 3, 375, 83, 0, 0 12 Bucket: 48, 0, 2, 334, 5, 0, 0 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 32 Bucket: 128, 0, 7, 148, 196, 0, 0 64 Bucket: 256, 0, 19, 56, 77, 0, 0 128 Bucket: 512, 0, 16, 16, 48, 0, 0 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 tst-11-arm:~ # ################### Regards John -- John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 16:48:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E85E536; Mon, 14 Jul 2014 16:48:58 +0000 (UTC) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9FFC2B42; Mon, 14 Jul 2014 16:48:57 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id f12so3340137qad.17 for ; Mon, 14 Jul 2014 09:48: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=Q4qqEWyB1SqUeUDPNnhWvHGrSccGQya7Le6zhkO/dvw=; b=da1mnTEvS8IzkYp/RmBgTX7f93VBUcmcxhPs4YgLUnqXnvaB1rZdK2QdPufpOWThUu wSMqdnM35rj53dkprVHqxoXRNx/nLP6lw2LcBi+iXm2kwyB0KBeH/HYpN5b98d+qlOTl 4GT9QVmy1+cRDVolPqSHpzuvrl1UKX/YL806fbY7GVNpGiugd7FbyXaZiJV6suX3Qzuu KmBU2HpSXxnbw5jSY8IizLqHItpJ8wxm4F+pJcq3sDwny/YDNrCEb3ZrGGjgK2Nb+mRr GQM2h6dqbL7PSbnpl3EYMGoGUfjIuQ3N3j2lzPhmAQtEgYUgBAdL/qpIbRY5NCxN9pms m5/A== MIME-Version: 1.0 X-Received: by 10.140.88.243 with SMTP id t106mr10457799qgd.12.1405356536961; Mon, 14 Jul 2014 09:48:56 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 14 Jul 2014 09:48:56 -0700 (PDT) In-Reply-To: <20140714080708.GA88464@zibbi.meraka.csir.co.za> References: <1404753166.65432.10.camel@revolution.hippie.lan> <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> Date: Mon, 14 Jul 2014 09:48:56 -0700 X-Google-Sender-Auth: oPmwykdbe53Z8kaZtKSrkB2pc4c Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 16:48:58 -0000 Hm, it could be some bus related stupidity. It's allocating 2k or 4k mbufs for the receive path because wifi frames are bigger than ethernet frames. If you're not seeing failures in 4k mbuf allocations then I'm not sure what it could be. I'll see about firing it up locally and checking. -a On 14 July 2014 01:07, John Hay wrote: > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: >> > Hi Guys, >> > >> > The problem is back / still there. I initially saw the problem during >> > boot, with the interface configs in rc.conf, but because it is so >> > mixed with the rest, I took it out and put it in the script, then >> > after multi-user boot was finished, I did a login and ran the script, >> > with the output I showed in the initial post. >> > >> > So I put the interface configs back into rc.conf and I'm seeing the >> > same problem, here is a cut during boot: >> > >> > ############### >> > Starting file system checks: >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) >> > Mounting local file systems:. >> > Writing entropy file:. >> > Setting hostname: tst-cambria-11. >> > wlan0: Ethernet address: 00:21:a4:35:70:42 >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 >> > ath1: unable to start recv logic >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 >> > ath2: unable to start recv logic >> > ############### >> > >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than >> > if I let it boot to multiuser and then configured the interfaces. It >> > was in the 6000, while now it is much higher: >> > >> > Without wlan configs in rc.conf, but configured afterwards: >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 >> > >> > With wlan configs in rc.conf: >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 >> > >> > Both of them boot from a ro compact-flash with md /etc and /var, but >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but >> > that did not make a difference. >> > > > Friday I power cycled the board and it came up without an error. All 3 > atheros cards configured in rc.conf. So I left it on for the weekend > and by this morning there was still no errors, so I rebooted it and > again saw the "ath1: unable to start recv logic" message for ath1 and > ath2. I power cycled it, but still get the error, so Friday was just > lucky with some timing thing, maybe if the card receive while it is > still configuring? Also if I leave the board booted in this state, > ath0 also start to give problems: > > ################# > ath0: ath_rx_proc: no mbuf! > ath0: ath_rx_proc: no mbuf! > ... > ath0: device timeout > ath0: ath_reset: unable to start recv logic > ... > ################# > > In anycase it seems that memory allocation problem. How do I figure out > where it is? "netstat -m" does not seem to point to an error. The mbuf > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z > that point to an alloc failure. How do I figure out where that is and > how do I fix it or work around it? > > ################### > tst-11-arm:~ # netstat -m > 128/382/510 mbufs in use (current/cache/total) > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) > 286K/353K/639K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/3/1488 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > tst-11-arm:~ # vmstat -z | grep mbuf > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 > mbuf: 256, 48990, 1, 256, 920, 0, 0 > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 > tst-11-arm:~ # vmstat -z | grep Bucket > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 > tst-11-arm:~ # > ################### > > Regards > > John > -- > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 18:42:11 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EEBDCA1F; Mon, 14 Jul 2014 18:42:11 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id F0675261F; Mon, 14 Jul 2014 18:42:10 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 2CA00B84A; Mon, 14 Jul 2014 20:42:09 +0200 (SAST) Date: Mon, 14 Jul 2014 20:42:09 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714184209.GA21922@zibbi.meraka.csir.co.za> References: <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 18:42:12 -0000 On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: > Hm, it could be some bus related stupidity. It's allocating 2k or 4k > mbufs for the receive path because wifi frames are bigger than > ethernet frames. If you're not seeing failures in 4k mbuf allocations > then I'm not sure what it could be. > > I'll see about firing it up locally and checking. I'm hunting a bit more and it looks like the fail is in the bounce pages. It looks like the calls look like this: ath_legacy_rxbuf_init() bus_dmamap_load_mbuf_sg() _bus_dmamap_load_buffer() _bus_dmamap_reserve_pages() reserve_bounce_pages() I have added a printf at the start of alloc_bounce_pages() and it seems that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, the first argument to alloc_bounce_pages(), common for the whole pci bus? The start of the boot, with my printf looks like this: #################### FreeBSD ARM (Gateworks Cambria) boot2 v0.4 - Default: /boot/kernel/kernel boot: Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S MALL-CAMBRIA arm gcc version 4.2.1 20070831 patched [FreeBSD] CPU: IXP435 rev 1 (ARMv5TE) (XScale core) Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled 32KB/32B 32-way instruction cache 32KB/32B 32-way write-back-locking data cache real memory = 134213632 (127 MB) avail memory = 124440576 (118 MB) random device not loaded; using insecure entropy wlan: mac acl policy registered random: initialized ixp0: ixp0: 37e7f pcib0: on ixp0 pci0: on pcib0 ath0: irq 28 at device 1.0 on pci0 alloc_bounce_pages: numpages 63 [ath] enabling AN_TOP2_FIXUP alloc_bounce_pages: numpages 1 ath0: AR9220 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 ath1: irq 27 at device 2.0 on pci0 [ath] enabling AN_TOP2_FIXUP ath1: AR9220 mac 128.2 RF5133 phy 13.0 ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 ath2: irq 26 at device 3.0 on pci0 ath2: AR5413 mac 10.5 RF5413 phy 6.1 ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 ixpclk0: on ixp0 #################### Interesting, with this boot, with the new kernel, the aths did not fail. Could the printf have changed something or was it just coincidence? With a reboot ath1 and ath2 failed again during configuration and a little while later ath0 started to complain: ath0: ath_rx_proc: no mbuf! John > > > > > -a > > On 14 July 2014 01:07, John Hay wrote: > > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: > >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > >> > Hi Guys, > >> > > >> > The problem is back / still there. I initially saw the problem during > >> > boot, with the interface configs in rc.conf, but because it is so > >> > mixed with the rest, I took it out and put it in the script, then > >> > after multi-user boot was finished, I did a login and ran the script, > >> > with the output I showed in the initial post. > >> > > >> > So I put the interface configs back into rc.conf and I'm seeing the > >> > same problem, here is a cut during boot: > >> > > >> > ############### > >> > Starting file system checks: > >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > >> > Mounting local file systems:. > >> > Writing entropy file:. > >> > Setting hostname: tst-cambria-11. > >> > wlan0: Ethernet address: 00:21:a4:35:70:42 > >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 > >> > ath1: unable to start recv logic > >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 > >> > ath2: unable to start recv logic > >> > ############### > >> > > >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than > >> > if I let it boot to multiuser and then configured the interfaces. It > >> > was in the 6000, while now it is much higher: > >> > > >> > Without wlan configs in rc.conf, but configured afterwards: > >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > >> > > >> > With wlan configs in rc.conf: > >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > >> > > >> > Both of them boot from a ro compact-flash with md /etc and /var, but > >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > >> > that did not make a difference. > >> > > > > > Friday I power cycled the board and it came up without an error. All 3 > > atheros cards configured in rc.conf. So I left it on for the weekend > > and by this morning there was still no errors, so I rebooted it and > > again saw the "ath1: unable to start recv logic" message for ath1 and > > ath2. I power cycled it, but still get the error, so Friday was just > > lucky with some timing thing, maybe if the card receive while it is > > still configuring? Also if I leave the board booted in this state, > > ath0 also start to give problems: > > > > ################# > > ath0: ath_rx_proc: no mbuf! > > ath0: ath_rx_proc: no mbuf! > > ... > > ath0: device timeout > > ath0: ath_reset: unable to start recv logic > > ... > > ################# > > > > In anycase it seems that memory allocation problem. How do I figure out > > where it is? "netstat -m" does not seem to point to an error. The mbuf > > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z > > that point to an alloc failure. How do I figure out where that is and > > how do I fix it or work around it? > > > > ################### > > tst-11-arm:~ # netstat -m > > 128/382/510 mbufs in use (current/cache/total) > > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) > > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) > > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) > > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) > > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) > > 286K/353K/639K bytes allocated to network (current/cache/total) > > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > > 0/3/1488 sfbufs in use (current/peak/max) > > 0 requests for sfbufs denied > > 0 requests for sfbufs delayed > > 0 requests for I/O initiated by sendfile > > tst-11-arm:~ # vmstat -z | grep mbuf > > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 > > mbuf: 256, 48990, 1, 256, 920, 0, 0 > > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 > > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 > > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 > > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 > > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 > > tst-11-arm:~ # vmstat -z | grep Bucket > > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 > > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 > > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 > > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 > > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 > > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 > > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 > > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 > > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 > > tst-11-arm:~ # > > ################### > > > > Regards > > > > John > > -- > > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 19:06:35 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CCB02AF5; Mon, 14 Jul 2014 19:06:35 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 65C002848; Mon, 14 Jul 2014 19:06:35 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id j7so2993646qaq.14 for ; Mon, 14 Jul 2014 12:06:34 -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=IUwaGjgsJCeZsMZFQTolpfnHG3K7fqyt0zLcPDwFNhc=; b=nTSBS4u7amBmARTbxm9s9qrj3UGqOsRpq5Lybq1e6e6OsV95A6Ky+PIDEYdECEXYYp SyiCdTvFqAcMNEbgpA4vuCMIWaU1v7S1mNu8/MzXQH4HZug0Fyu/tpFFNFHVTZ1nzws9 04/hkyGRaFYjhoyTld4z2BBWajSMwiKhpy6z6nxstqKkvMqZpyWQMxm782+qRTQTAmSa kxkr1XljbYoL2ahRALe3x5Nrfck3wZN/FfF8TEKPo0OZ88qE/CxIEnb+ogYiVz5YUgr5 1z4wCY+dIgFEKy/qa3kOr89/hNPk5WF0gMLR1wLH9Pz/ESDGcX7NtlvIZaY8ue0Z4hP8 C9Kw== MIME-Version: 1.0 X-Received: by 10.224.156.145 with SMTP id x17mr26850685qaw.49.1405364794585; Mon, 14 Jul 2014 12:06:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 14 Jul 2014 12:06:34 -0700 (PDT) In-Reply-To: <20140714184209.GA21922@zibbi.meraka.csir.co.za> References: <20140707182814.GA75629@zibbi.meraka.csir.co.za> <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> Date: Mon, 14 Jul 2014 12:06:34 -0700 X-Google-Sender-Auth: OfNwvasoQli-DBDn7C37kBdYGrU Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 19:06:35 -0000 .. why's it need bounce buffers? -a On 14 July 2014 11:42, John Hay wrote: > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k >> mbufs for the receive path because wifi frames are bigger than >> ethernet frames. If you're not seeing failures in 4k mbuf allocations >> then I'm not sure what it could be. >> >> I'll see about firing it up locally and checking. > > I'm hunting a bit more and it looks like the fail is in the bounce pages. > It looks like the calls look like this: > > ath_legacy_rxbuf_init() > bus_dmamap_load_mbuf_sg() > _bus_dmamap_load_buffer() > _bus_dmamap_reserve_pages() > reserve_bounce_pages() > > I have added a printf at the start of alloc_bounce_pages() and it seems > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, > the first argument to alloc_bounce_pages(), common for the whole pci bus? > > The start of the boot, with my printf looks like this: > > #################### > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 > - > Default: /boot/kernel/kernel > boot: > Copyright (c) 1992-2014 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S > MALL-CAMBRIA arm > gcc version 4.2.1 20070831 patched [FreeBSD] > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled > 32KB/32B 32-way instruction cache > 32KB/32B 32-way write-back-locking data cache > real memory = 134213632 (127 MB) > avail memory = 124440576 (118 MB) > random device not loaded; using insecure entropy > wlan: mac acl policy registered > random: initialized > ixp0: > ixp0: 37e7f > pcib0: on ixp0 > pci0: on pcib0 > ath0: irq 28 at device 1.0 on pci0 > alloc_bounce_pages: numpages 63 > [ath] enabling AN_TOP2_FIXUP > alloc_bounce_pages: numpages 1 > ath0: AR9220 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > ath1: irq 27 at device 2.0 on pci0 > [ath] enabling AN_TOP2_FIXUP > ath1: AR9220 mac 128.2 RF5133 phy 13.0 > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > ath2: irq 26 at device 3.0 on pci0 > ath2: AR5413 mac 10.5 RF5413 phy 6.1 > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 > ixpclk0: on ixp0 > #################### > > Interesting, with this boot, with the new kernel, the aths did not fail. > Could the printf have changed something or was it just coincidence? With > a reboot ath1 and ath2 failed again during configuration and a little > while later ath0 started to complain: > > ath0: ath_rx_proc: no mbuf! > > John > >> >> >> >> >> -a >> >> On 14 July 2014 01:07, John Hay wrote: >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: >> >> > Hi Guys, >> >> > >> >> > The problem is back / still there. I initially saw the problem during >> >> > boot, with the interface configs in rc.conf, but because it is so >> >> > mixed with the rest, I took it out and put it in the script, then >> >> > after multi-user boot was finished, I did a login and ran the script, >> >> > with the output I showed in the initial post. >> >> > >> >> > So I put the interface configs back into rc.conf and I'm seeing the >> >> > same problem, here is a cut during boot: >> >> > >> >> > ############### >> >> > Starting file system checks: >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) >> >> > Mounting local file systems:. >> >> > Writing entropy file:. >> >> > Setting hostname: tst-cambria-11. >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 >> >> > ath1: unable to start recv logic >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 >> >> > ath2: unable to start recv logic >> >> > ############### >> >> > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than >> >> > if I let it boot to multiuser and then configured the interfaces. It >> >> > was in the 6000, while now it is much higher: >> >> > >> >> > Without wlan configs in rc.conf, but configured afterwards: >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 >> >> > >> >> > With wlan configs in rc.conf: >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 >> >> > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but >> >> > that did not make a difference. >> >> > >> > >> > Friday I power cycled the board and it came up without an error. All 3 >> > atheros cards configured in rc.conf. So I left it on for the weekend >> > and by this morning there was still no errors, so I rebooted it and >> > again saw the "ath1: unable to start recv logic" message for ath1 and >> > ath2. I power cycled it, but still get the error, so Friday was just >> > lucky with some timing thing, maybe if the card receive while it is >> > still configuring? Also if I leave the board booted in this state, >> > ath0 also start to give problems: >> > >> > ################# >> > ath0: ath_rx_proc: no mbuf! >> > ath0: ath_rx_proc: no mbuf! >> > ... >> > ath0: device timeout >> > ath0: ath_reset: unable to start recv logic >> > ... >> > ################# >> > >> > In anycase it seems that memory allocation problem. How do I figure out >> > where it is? "netstat -m" does not seem to point to an error. The mbuf >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z >> > that point to an alloc failure. How do I figure out where that is and >> > how do I fix it or work around it? >> > >> > ################### >> > tst-11-arm:~ # netstat -m >> > 128/382/510 mbufs in use (current/cache/total) >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) >> > 286K/353K/639K bytes allocated to network (current/cache/total) >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >> > 0/3/1488 sfbufs in use (current/peak/max) >> > 0 requests for sfbufs denied >> > 0 requests for sfbufs delayed >> > 0 requests for I/O initiated by sendfile >> > tst-11-arm:~ # vmstat -z | grep mbuf >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 >> > tst-11-arm:~ # vmstat -z | grep Bucket >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 >> > tst-11-arm:~ # >> > ################### >> > >> > Regards >> > >> > John >> > -- >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 19:09:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A745BBD; Mon, 14 Jul 2014 19:09:49 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2DF9C286D; Mon, 14 Jul 2014 19:09:48 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id EACF3B842; Mon, 14 Jul 2014 21:09:46 +0200 (SAST) Date: Mon, 14 Jul 2014 21:09:46 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714190946.GA49930@zibbi.meraka.csir.co.za> References: <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 19:09:49 -0000 On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote: > .. why's it need bounce buffers? I found this: arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above must be bounced */ John > > > -a > > > On 14 July 2014 11:42, John Hay wrote: > > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: > >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k > >> mbufs for the receive path because wifi frames are bigger than > >> ethernet frames. If you're not seeing failures in 4k mbuf allocations > >> then I'm not sure what it could be. > >> > >> I'll see about firing it up locally and checking. > > > > I'm hunting a bit more and it looks like the fail is in the bounce pages. > > It looks like the calls look like this: > > > > ath_legacy_rxbuf_init() > > bus_dmamap_load_mbuf_sg() > > _bus_dmamap_load_buffer() > > _bus_dmamap_reserve_pages() > > reserve_bounce_pages() > > > > I have added a printf at the start of alloc_bounce_pages() and it seems > > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, > > the first argument to alloc_bounce_pages(), common for the whole pci bus? > > > > The start of the boot, with my printf looks like this: > > > > #################### > > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 > > - > > Default: /boot/kernel/kernel > > boot: > > Copyright (c) 1992-2014 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 > > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S > > MALL-CAMBRIA arm > > gcc version 4.2.1 20070831 patched [FreeBSD] > > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) > > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled > > 32KB/32B 32-way instruction cache > > 32KB/32B 32-way write-back-locking data cache > > real memory = 134213632 (127 MB) > > avail memory = 124440576 (118 MB) > > random device not loaded; using insecure entropy > > wlan: mac acl policy registered > > random: initialized > > ixp0: > > ixp0: 37e7f > > pcib0: on ixp0 > > pci0: on pcib0 > > ath0: irq 28 at device 1.0 on pci0 > > alloc_bounce_pages: numpages 63 > > [ath] enabling AN_TOP2_FIXUP > > alloc_bounce_pages: numpages 1 > > ath0: AR9220 mac 128.2 RF5133 phy 13.0 > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > ath1: irq 27 at device 2.0 on pci0 > > [ath] enabling AN_TOP2_FIXUP > > ath1: AR9220 mac 128.2 RF5133 phy 13.0 > > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > ath2: irq 26 at device 3.0 on pci0 > > ath2: AR5413 mac 10.5 RF5413 phy 6.1 > > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 > > ixpclk0: on ixp0 > > #################### > > > > Interesting, with this boot, with the new kernel, the aths did not fail. > > Could the printf have changed something or was it just coincidence? With > > a reboot ath1 and ath2 failed again during configuration and a little > > while later ath0 started to complain: > > > > ath0: ath_rx_proc: no mbuf! > > > > John > > > >> > >> > >> > >> > >> -a > >> > >> On 14 July 2014 01:07, John Hay wrote: > >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: > >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > >> >> > Hi Guys, > >> >> > > >> >> > The problem is back / still there. I initially saw the problem during > >> >> > boot, with the interface configs in rc.conf, but because it is so > >> >> > mixed with the rest, I took it out and put it in the script, then > >> >> > after multi-user boot was finished, I did a login and ran the script, > >> >> > with the output I showed in the initial post. > >> >> > > >> >> > So I put the interface configs back into rc.conf and I'm seeing the > >> >> > same problem, here is a cut during boot: > >> >> > > >> >> > ############### > >> >> > Starting file system checks: > >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > >> >> > Mounting local file systems:. > >> >> > Writing entropy file:. > >> >> > Setting hostname: tst-cambria-11. > >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 > >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 > >> >> > ath1: unable to start recv logic > >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 > >> >> > ath2: unable to start recv logic > >> >> > ############### > >> >> > > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than > >> >> > if I let it boot to multiuser and then configured the interfaces. It > >> >> > was in the 6000, while now it is much higher: > >> >> > > >> >> > Without wlan configs in rc.conf, but configured afterwards: > >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > >> >> > > >> >> > With wlan configs in rc.conf: > >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > >> >> > > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but > >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > >> >> > that did not make a difference. > >> >> > > >> > > >> > Friday I power cycled the board and it came up without an error. All 3 > >> > atheros cards configured in rc.conf. So I left it on for the weekend > >> > and by this morning there was still no errors, so I rebooted it and > >> > again saw the "ath1: unable to start recv logic" message for ath1 and > >> > ath2. I power cycled it, but still get the error, so Friday was just > >> > lucky with some timing thing, maybe if the card receive while it is > >> > still configuring? Also if I leave the board booted in this state, > >> > ath0 also start to give problems: > >> > > >> > ################# > >> > ath0: ath_rx_proc: no mbuf! > >> > ath0: ath_rx_proc: no mbuf! > >> > ... > >> > ath0: device timeout > >> > ath0: ath_reset: unable to start recv logic > >> > ... > >> > ################# > >> > > >> > In anycase it seems that memory allocation problem. How do I figure out > >> > where it is? "netstat -m" does not seem to point to an error. The mbuf > >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z > >> > that point to an alloc failure. How do I figure out where that is and > >> > how do I fix it or work around it? > >> > > >> > ################### > >> > tst-11-arm:~ # netstat -m > >> > 128/382/510 mbufs in use (current/cache/total) > >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) > >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) > >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) > >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) > >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) > >> > 286K/353K/639K bytes allocated to network (current/cache/total) > >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > >> > 0/3/1488 sfbufs in use (current/peak/max) > >> > 0 requests for sfbufs denied > >> > 0 requests for sfbufs delayed > >> > 0 requests for I/O initiated by sendfile > >> > tst-11-arm:~ # vmstat -z | grep mbuf > >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 > >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 > >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 > >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 > >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 > >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 > >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 > >> > tst-11-arm:~ # vmstat -z | grep Bucket > >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 > >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 > >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 > >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 > >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 > >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 > >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 > >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 > >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 > >> > tst-11-arm:~ # > >> > ################### > >> > > >> > Regards > >> > > >> > John > >> > -- > >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 19:14:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD665D9D; Mon, 14 Jul 2014 19:14:18 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id CB5E5290E; Mon, 14 Jul 2014 19:14:17 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 99205B84A; Mon, 14 Jul 2014 21:14:16 +0200 (SAST) Date: Mon, 14 Jul 2014 21:14:16 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714191416.GB49930@zibbi.meraka.csir.co.za> References: <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140714190946.GA49930@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 19:14:19 -0000 On Mon, Jul 14, 2014 at 09:09:46PM +0200, John Hay wrote: > On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote: > > .. why's it need bounce buffers? > > I found this: > arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above must be bounced */ I found a sysctl to show some bounce info. :-) On the boot that ath1 and ath2 failed during ifconfig and ath0 started to complain after a while: ##################### tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 64 hw.busdma.zone0.total_bpages: 64 hw.busdma.zone0.free_bpages: 0 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 64 hw.busdma.zone0.total_bounced: 1191 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 ##################### I then thought to down wlan0 to see if the page count changed, but do not know. :-) ##################### tst-11-arm:~ # ifconfig wlan0 down dev.ath.0.debug: 0 -> 8 /sbin/ifconfig.bin wlan0 down ath0: ath_stop_locked: invalid 0 if_flags 0x8802 Sleeping thread (tid 100019, pid 0) owns a non-sleepable lock panic: sleeping thread Uptime: 32m46s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... ##################### John > > John > > > > > > -a > > > > > > On 14 July 2014 11:42, John Hay wrote: > > > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: > > >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k > > >> mbufs for the receive path because wifi frames are bigger than > > >> ethernet frames. If you're not seeing failures in 4k mbuf allocations > > >> then I'm not sure what it could be. > > >> > > >> I'll see about firing it up locally and checking. > > > > > > I'm hunting a bit more and it looks like the fail is in the bounce pages. > > > It looks like the calls look like this: > > > > > > ath_legacy_rxbuf_init() > > > bus_dmamap_load_mbuf_sg() > > > _bus_dmamap_load_buffer() > > > _bus_dmamap_reserve_pages() > > > reserve_bounce_pages() > > > > > > I have added a printf at the start of alloc_bounce_pages() and it seems > > > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, > > > the first argument to alloc_bounce_pages(), common for the whole pci bus? > > > > > > The start of the boot, with my printf looks like this: > > > > > > #################### > > > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 > > > - > > > Default: /boot/kernel/kernel > > > boot: > > > Copyright (c) 1992-2014 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > The Regents of the University of California. All rights reserved. > > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 > > > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S > > > MALL-CAMBRIA arm > > > gcc version 4.2.1 20070831 patched [FreeBSD] > > > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) > > > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled > > > 32KB/32B 32-way instruction cache > > > 32KB/32B 32-way write-back-locking data cache > > > real memory = 134213632 (127 MB) > > > avail memory = 124440576 (118 MB) > > > random device not loaded; using insecure entropy > > > wlan: mac acl policy registered > > > random: initialized > > > ixp0: > > > ixp0: 37e7f > > > pcib0: on ixp0 > > > pci0: on pcib0 > > > ath0: irq 28 at device 1.0 on pci0 > > > alloc_bounce_pages: numpages 63 > > > [ath] enabling AN_TOP2_FIXUP > > > alloc_bounce_pages: numpages 1 > > > ath0: AR9220 mac 128.2 RF5133 phy 13.0 > > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > > ath1: irq 27 at device 2.0 on pci0 > > > [ath] enabling AN_TOP2_FIXUP > > > ath1: AR9220 mac 128.2 RF5133 phy 13.0 > > > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > > ath2: irq 26 at device 3.0 on pci0 > > > ath2: AR5413 mac 10.5 RF5413 phy 6.1 > > > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 > > > ixpclk0: on ixp0 > > > #################### > > > > > > Interesting, with this boot, with the new kernel, the aths did not fail. > > > Could the printf have changed something or was it just coincidence? With > > > a reboot ath1 and ath2 failed again during configuration and a little > > > while later ath0 started to complain: > > > > > > ath0: ath_rx_proc: no mbuf! > > > > > > John > > > > > >> > > >> > > >> > > >> > > >> -a > > >> > > >> On 14 July 2014 01:07, John Hay wrote: > > >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: > > >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > > >> >> > Hi Guys, > > >> >> > > > >> >> > The problem is back / still there. I initially saw the problem during > > >> >> > boot, with the interface configs in rc.conf, but because it is so > > >> >> > mixed with the rest, I took it out and put it in the script, then > > >> >> > after multi-user boot was finished, I did a login and ran the script, > > >> >> > with the output I showed in the initial post. > > >> >> > > > >> >> > So I put the interface configs back into rc.conf and I'm seeing the > > >> >> > same problem, here is a cut during boot: > > >> >> > > > >> >> > ############### > > >> >> > Starting file system checks: > > >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > > >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > > >> >> > Mounting local file systems:. > > >> >> > Writing entropy file:. > > >> >> > Setting hostname: tst-cambria-11. > > >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 > > >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 > > >> >> > ath1: unable to start recv logic > > >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 > > >> >> > ath2: unable to start recv logic > > >> >> > ############### > > >> >> > > > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than > > >> >> > if I let it boot to multiuser and then configured the interfaces. It > > >> >> > was in the 6000, while now it is much higher: > > >> >> > > > >> >> > Without wlan configs in rc.conf, but configured afterwards: > > >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > > >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > > >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > > >> >> > > > >> >> > With wlan configs in rc.conf: > > >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > > >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > > >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > > >> >> > > > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but > > >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > > >> >> > that did not make a difference. > > >> >> > > > >> > > > >> > Friday I power cycled the board and it came up without an error. All 3 > > >> > atheros cards configured in rc.conf. So I left it on for the weekend > > >> > and by this morning there was still no errors, so I rebooted it and > > >> > again saw the "ath1: unable to start recv logic" message for ath1 and > > >> > ath2. I power cycled it, but still get the error, so Friday was just > > >> > lucky with some timing thing, maybe if the card receive while it is > > >> > still configuring? Also if I leave the board booted in this state, > > >> > ath0 also start to give problems: > > >> > > > >> > ################# > > >> > ath0: ath_rx_proc: no mbuf! > > >> > ath0: ath_rx_proc: no mbuf! > > >> > ... > > >> > ath0: device timeout > > >> > ath0: ath_reset: unable to start recv logic > > >> > ... > > >> > ################# > > >> > > > >> > In anycase it seems that memory allocation problem. How do I figure out > > >> > where it is? "netstat -m" does not seem to point to an error. The mbuf > > >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z > > >> > that point to an alloc failure. How do I figure out where that is and > > >> > how do I fix it or work around it? > > >> > > > >> > ################### > > >> > tst-11-arm:~ # netstat -m > > >> > 128/382/510 mbufs in use (current/cache/total) > > >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) > > >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) > > >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) > > >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) > > >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) > > >> > 286K/353K/639K bytes allocated to network (current/cache/total) > > >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > > >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > > >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > > >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > > >> > 0/3/1488 sfbufs in use (current/peak/max) > > >> > 0 requests for sfbufs denied > > >> > 0 requests for sfbufs delayed > > >> > 0 requests for I/O initiated by sendfile > > >> > tst-11-arm:~ # vmstat -z | grep mbuf > > >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 > > >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 > > >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 > > >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 > > >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 > > >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 > > >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 > > >> > tst-11-arm:~ # vmstat -z | grep Bucket > > >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 > > >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 > > >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 > > >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 > > >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 > > >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 > > >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 > > >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 > > >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 > > >> > tst-11-arm:~ # > > >> > ################### > > >> > > > >> > Regards > > >> > > > >> > John > > >> > -- > > >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 19:23:49 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03D762FE; Mon, 14 Jul 2014 19:23:49 +0000 (UTC) Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 909A52A0D; Mon, 14 Jul 2014 19:23:48 +0000 (UTC) Received: by mail-qg0-f45.google.com with SMTP id f51so3796384qge.4 for ; Mon, 14 Jul 2014 12:23:47 -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=YCfhQ9+wcjnPl4MpcAv82V3mB94IHXnMUAdNCqjYzR0=; b=GR71SibUitfzu1ahGiH8PvFOvyOMT3gx94oPxJFqWriWmVQtzrDymS0Q5YNBcuwoP3 WMlQsgNJGwJOkCNJb+DJ8aIh5cgmHrsNkSpiE9nbGbOuiU2IPLTONQf2aTQ03H1FAll+ jfQtZ7vnt329LFSsL9s5EWMuQ5h8oF9jOWxJxE6xB4+v5qrceWP2Ak1+QewfOW7n/3ZQ 4WuGeTb5rpFt6xWAtNRNKZ+guw8lkN71vRs/BX5a9Z5WlEGpE3U5SBwH3C56pfRhlZGD SY6Gpk3SbbQzuXcJ0jtKT6A/7Z6WgtH3kcV9rTvOztZ0n+Ql19BQyCfFrF8AxyFaD8Bf JG5g== MIME-Version: 1.0 X-Received: by 10.224.71.198 with SMTP id i6mr25281287qaj.76.1405365827595; Mon, 14 Jul 2014 12:23:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 14 Jul 2014 12:23:47 -0700 (PDT) In-Reply-To: <20140714191416.GB49930@zibbi.meraka.csir.co.za> References: <20140707193252.GA79553@zibbi.meraka.csir.co.za> <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> <20140714191416.GB49930@zibbi.meraka.csir.co.za> Date: Mon, 14 Jul 2014 12:23:47 -0700 X-Google-Sender-Auth: DcSgoqDXjEoZRrWU9gZ3ew9JFJA Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 19:23:49 -0000 Ah, you're going to need more than 64 bounce pages. That's just not enough for all the mbufs the 11n support requires. It likely didn't show up in previous incarnations of this because pre-11n support had a much smaller pool of buffers in use. For doing 11n, there's hm, 256 TX and 256 RX buffers for each NIC? Or is it 512 and 512? It's something large like that. So assuming 512, that's 1024 * 4096 bytes each, so 4mbyte per NIC needed of bounce buffers. You could tweak ATH_TXBUF and ATH_RXBUF down to something like 128 TX and 128 RX, but you can't go much lower than that per NIC as an A-MPDU aggregate requires up to 64 buffers to transmit and/or receive and if you're not careful you'll actually overrun the RX FIFO and/or starve the TX code from having mbufs available to transmit with. -a On 14 July 2014 12:14, John Hay wrote: > On Mon, Jul 14, 2014 at 09:09:46PM +0200, John Hay wrote: >> On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote: >> > .. why's it need bounce buffers? >> >> I found this: >> arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above must be bounced */ > > I found a sysctl to show some bounce info. :-) > > On the boot that ath1 and ath2 failed during ifconfig and ath0 started > to complain after a while: > > ##################### > tst-11-arm:~ # sysctl hw.busdma > hw.busdma.total_bpages: 64 > hw.busdma.zone0.total_bpages: 64 > hw.busdma.zone0.free_bpages: 0 > hw.busdma.zone0.reserved_bpages: 0 > hw.busdma.zone0.active_bpages: 64 > hw.busdma.zone0.total_bounced: 1191 > hw.busdma.zone0.total_deferred: 0 > hw.busdma.zone0.lowaddr: 0x4000fff > hw.busdma.zone0.alignment: 4096 > ##################### > > I then thought to down wlan0 to see if the page count changed, but > do not know. :-) > > ##################### > tst-11-arm:~ # ifconfig wlan0 down > dev.ath.0.debug: 0 -> 8 > /sbin/ifconfig.bin wlan0 down > ath0: ath_stop_locked: invalid 0 if_flags 0x8802 > Sleeping thread (tid 100019, pid 0) owns a non-sleepable lock > panic: sleeping thread > Uptime: 32m46s > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > ##################### > > John > >> >> John >> > >> > >> > -a >> > >> > >> > On 14 July 2014 11:42, John Hay wrote: >> > > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: >> > >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k >> > >> mbufs for the receive path because wifi frames are bigger than >> > >> ethernet frames. If you're not seeing failures in 4k mbuf allocations >> > >> then I'm not sure what it could be. >> > >> >> > >> I'll see about firing it up locally and checking. >> > > >> > > I'm hunting a bit more and it looks like the fail is in the bounce pages. >> > > It looks like the calls look like this: >> > > >> > > ath_legacy_rxbuf_init() >> > > bus_dmamap_load_mbuf_sg() >> > > _bus_dmamap_load_buffer() >> > > _bus_dmamap_reserve_pages() >> > > reserve_bounce_pages() >> > > >> > > I have added a printf at the start of alloc_bounce_pages() and it seems >> > > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, >> > > the first argument to alloc_bounce_pages(), common for the whole pci bus? >> > > >> > > The start of the boot, with my printf looks like this: >> > > >> > > #################### >> > > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 >> > > - >> > > Default: /boot/kernel/kernel >> > > boot: >> > > Copyright (c) 1992-2014 The FreeBSD Project. >> > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> > > The Regents of the University of California. All rights reserved. >> > > FreeBSD is a registered trademark of The FreeBSD Foundation. >> > > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 >> > > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S >> > > MALL-CAMBRIA arm >> > > gcc version 4.2.1 20070831 patched [FreeBSD] >> > > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) >> > > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled >> > > 32KB/32B 32-way instruction cache >> > > 32KB/32B 32-way write-back-locking data cache >> > > real memory = 134213632 (127 MB) >> > > avail memory = 124440576 (118 MB) >> > > random device not loaded; using insecure entropy >> > > wlan: mac acl policy registered >> > > random: initialized >> > > ixp0: >> > > ixp0: 37e7f >> > > pcib0: on ixp0 >> > > pci0: on pcib0 >> > > ath0: irq 28 at device 1.0 on pci0 >> > > alloc_bounce_pages: numpages 63 >> > > [ath] enabling AN_TOP2_FIXUP >> > > alloc_bounce_pages: numpages 1 >> > > ath0: AR9220 mac 128.2 RF5133 phy 13.0 >> > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> > > ath1: irq 27 at device 2.0 on pci0 >> > > [ath] enabling AN_TOP2_FIXUP >> > > ath1: AR9220 mac 128.2 RF5133 phy 13.0 >> > > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> > > ath2: irq 26 at device 3.0 on pci0 >> > > ath2: AR5413 mac 10.5 RF5413 phy 6.1 >> > > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 >> > > ixpclk0: on ixp0 >> > > #################### >> > > >> > > Interesting, with this boot, with the new kernel, the aths did not fail. >> > > Could the printf have changed something or was it just coincidence? With >> > > a reboot ath1 and ath2 failed again during configuration and a little >> > > while later ath0 started to complain: >> > > >> > > ath0: ath_rx_proc: no mbuf! >> > > >> > > John >> > > >> > >> >> > >> >> > >> >> > >> >> > >> -a >> > >> >> > >> On 14 July 2014 01:07, John Hay wrote: >> > >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: >> > >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: >> > >> >> > Hi Guys, >> > >> >> > >> > >> >> > The problem is back / still there. I initially saw the problem during >> > >> >> > boot, with the interface configs in rc.conf, but because it is so >> > >> >> > mixed with the rest, I took it out and put it in the script, then >> > >> >> > after multi-user boot was finished, I did a login and ran the script, >> > >> >> > with the output I showed in the initial post. >> > >> >> > >> > >> >> > So I put the interface configs back into rc.conf and I'm seeing the >> > >> >> > same problem, here is a cut during boot: >> > >> >> > >> > >> >> > ############### >> > >> >> > Starting file system checks: >> > >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS >> > >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) >> > >> >> > Mounting local file systems:. >> > >> >> > Writing entropy file:. >> > >> >> > Setting hostname: tst-cambria-11. >> > >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 >> > >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 >> > >> >> > ath1: unable to start recv logic >> > >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 >> > >> >> > ath2: unable to start recv logic >> > >> >> > ############### >> > >> >> > >> > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than >> > >> >> > if I let it boot to multiuser and then configured the interfaces. It >> > >> >> > was in the 6000, while now it is much higher: >> > >> >> > >> > >> >> > Without wlan configs in rc.conf, but configured afterwards: >> > >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 >> > >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 >> > >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 >> > >> >> > >> > >> >> > With wlan configs in rc.conf: >> > >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 >> > >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 >> > >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 >> > >> >> > >> > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but >> > >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but >> > >> >> > that did not make a difference. >> > >> >> > >> > >> > >> > >> > Friday I power cycled the board and it came up without an error. All 3 >> > >> > atheros cards configured in rc.conf. So I left it on for the weekend >> > >> > and by this morning there was still no errors, so I rebooted it and >> > >> > again saw the "ath1: unable to start recv logic" message for ath1 and >> > >> > ath2. I power cycled it, but still get the error, so Friday was just >> > >> > lucky with some timing thing, maybe if the card receive while it is >> > >> > still configuring? Also if I leave the board booted in this state, >> > >> > ath0 also start to give problems: >> > >> > >> > >> > ################# >> > >> > ath0: ath_rx_proc: no mbuf! >> > >> > ath0: ath_rx_proc: no mbuf! >> > >> > ... >> > >> > ath0: device timeout >> > >> > ath0: ath_reset: unable to start recv logic >> > >> > ... >> > >> > ################# >> > >> > >> > >> > In anycase it seems that memory allocation problem. How do I figure out >> > >> > where it is? "netstat -m" does not seem to point to an error. The mbuf >> > >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z >> > >> > that point to an alloc failure. How do I figure out where that is and >> > >> > how do I fix it or work around it? >> > >> > >> > >> > ################### >> > >> > tst-11-arm:~ # netstat -m >> > >> > 128/382/510 mbufs in use (current/cache/total) >> > >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) >> > >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) >> > >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) >> > >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) >> > >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) >> > >> > 286K/353K/639K bytes allocated to network (current/cache/total) >> > >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) >> > >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) >> > >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) >> > >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >> > >> > 0/3/1488 sfbufs in use (current/peak/max) >> > >> > 0 requests for sfbufs denied >> > >> > 0 requests for sfbufs delayed >> > >> > 0 requests for I/O initiated by sendfile >> > >> > tst-11-arm:~ # vmstat -z | grep mbuf >> > >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 >> > >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 >> > >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 >> > >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 >> > >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 >> > >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 >> > >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 >> > >> > tst-11-arm:~ # vmstat -z | grep Bucket >> > >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 >> > >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 >> > >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 >> > >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 >> > >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 >> > >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 >> > >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 >> > >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 >> > >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 >> > >> > tst-11-arm:~ # >> > >> > ################### >> > >> > >> > >> > Regards >> > >> > >> > >> > John >> > >> > -- >> > >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 19:49:35 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5932A1D; Mon, 14 Jul 2014 19:49:35 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4A62BFC; Mon, 14 Jul 2014 19:49:34 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id E5EADB842; Mon, 14 Jul 2014 21:49:32 +0200 (SAST) Date: Mon, 14 Jul 2014 21:49:32 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714194932.GA51947@zibbi.meraka.csir.co.za> References: <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> <20140714191416.GB49930@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 19:49:36 -0000 On Mon, Jul 14, 2014 at 12:23:47PM -0700, Adrian Chadd wrote: > Ah, you're going to need more than 64 bounce pages. That's just not > enough for all the mbufs the 11n support requires. > > It likely didn't show up in previous incarnations of this because > pre-11n support had a much smaller pool of buffers in use. > > For doing 11n, there's hm, 256 TX and 256 RX buffers for each NIC? Or > is it 512 and 512? It's something large like that. So assuming 512, > that's 1024 * 4096 bytes each, so 4mbyte per NIC needed of bounce > buffers. > > You could tweak ATH_TXBUF and ATH_RXBUF down to something like 128 TX > and 128 RX, but you can't go much lower than that per NIC as an A-MPDU > aggregate requires up to 64 buffers to transmit and/or receive and if > you're not careful you'll actually overrun the RX FIFO and/or starve > the TX code from having mbufs available to transmit with. I don't mind up the bounce buffers, if that will help. I'll see how high I can go before it explode. :-) I guess one cannot easily use the RAM above 64M for ram disks and code and then not bouncing at all. :-/ I just had an ok boot, ie. all 3 aths came up without an error. So just after a login, the bounce stats looked like this: tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 64 hw.busdma.zone0.total_bpages: 64 hw.busdma.zone0.free_bpages: 57 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 7 hw.busdma.zone0.total_bounced: 525 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 The usage seems to slowly climb though. After 30 minutes it looks like this: tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 64 hw.busdma.zone0.total_bpages: 64 hw.busdma.zone0.free_bpages: 43 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 21 hw.busdma.zone0.total_bounced: 4713 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 The board is pretty idle, with no routing daemon or traffic except for the occasional broadcast and multicasts that arrive. John > > > -a > > > On 14 July 2014 12:14, John Hay wrote: > > On Mon, Jul 14, 2014 at 09:09:46PM +0200, John Hay wrote: > >> On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote: > >> > .. why's it need bounce buffers? > >> > >> I found this: > >> arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above must be bounced */ > > > > I found a sysctl to show some bounce info. :-) > > > > On the boot that ath1 and ath2 failed during ifconfig and ath0 started > > to complain after a while: > > > > ##################### > > tst-11-arm:~ # sysctl hw.busdma > > hw.busdma.total_bpages: 64 > > hw.busdma.zone0.total_bpages: 64 > > hw.busdma.zone0.free_bpages: 0 > > hw.busdma.zone0.reserved_bpages: 0 > > hw.busdma.zone0.active_bpages: 64 > > hw.busdma.zone0.total_bounced: 1191 > > hw.busdma.zone0.total_deferred: 0 > > hw.busdma.zone0.lowaddr: 0x4000fff > > hw.busdma.zone0.alignment: 4096 > > ##################### > > > > I then thought to down wlan0 to see if the page count changed, but > > do not know. :-) > > > > ##################### > > tst-11-arm:~ # ifconfig wlan0 down > > dev.ath.0.debug: 0 -> 8 > > /sbin/ifconfig.bin wlan0 down > > ath0: ath_stop_locked: invalid 0 if_flags 0x8802 > > Sleeping thread (tid 100019, pid 0) owns a non-sleepable lock > > panic: sleeping thread > > Uptime: 32m46s > > Automatic reboot in 15 seconds - press a key on the console to abort > > Rebooting... > > ##################### > > > > John > > > >> > >> John > >> > > >> > > >> > -a > >> > > >> > > >> > On 14 July 2014 11:42, John Hay wrote: > >> > > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: > >> > >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k > >> > >> mbufs for the receive path because wifi frames are bigger than > >> > >> ethernet frames. If you're not seeing failures in 4k mbuf allocations > >> > >> then I'm not sure what it could be. > >> > >> > >> > >> I'll see about firing it up locally and checking. > >> > > > >> > > I'm hunting a bit more and it looks like the fail is in the bounce pages. > >> > > It looks like the calls look like this: > >> > > > >> > > ath_legacy_rxbuf_init() > >> > > bus_dmamap_load_mbuf_sg() > >> > > _bus_dmamap_load_buffer() > >> > > _bus_dmamap_reserve_pages() > >> > > reserve_bounce_pages() > >> > > > >> > > I have added a printf at the start of alloc_bounce_pages() and it seems > >> > > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, > >> > > the first argument to alloc_bounce_pages(), common for the whole pci bus? > >> > > > >> > > The start of the boot, with my printf looks like this: > >> > > > >> > > #################### > >> > > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 > >> > > - > >> > > Default: /boot/kernel/kernel > >> > > boot: > >> > > Copyright (c) 1992-2014 The FreeBSD Project. > >> > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > >> > > The Regents of the University of California. All rights reserved. > >> > > FreeBSD is a registered trademark of The FreeBSD Foundation. > >> > > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 > >> > > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S > >> > > MALL-CAMBRIA arm > >> > > gcc version 4.2.1 20070831 patched [FreeBSD] > >> > > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) > >> > > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled > >> > > 32KB/32B 32-way instruction cache > >> > > 32KB/32B 32-way write-back-locking data cache > >> > > real memory = 134213632 (127 MB) > >> > > avail memory = 124440576 (118 MB) > >> > > random device not loaded; using insecure entropy > >> > > wlan: mac acl policy registered > >> > > random: initialized > >> > > ixp0: > >> > > ixp0: 37e7f > >> > > pcib0: on ixp0 > >> > > pci0: on pcib0 > >> > > ath0: irq 28 at device 1.0 on pci0 > >> > > alloc_bounce_pages: numpages 63 > >> > > [ath] enabling AN_TOP2_FIXUP > >> > > alloc_bounce_pages: numpages 1 > >> > > ath0: AR9220 mac 128.2 RF5133 phy 13.0 > >> > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > >> > > ath1: irq 27 at device 2.0 on pci0 > >> > > [ath] enabling AN_TOP2_FIXUP > >> > > ath1: AR9220 mac 128.2 RF5133 phy 13.0 > >> > > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > >> > > ath2: irq 26 at device 3.0 on pci0 > >> > > ath2: AR5413 mac 10.5 RF5413 phy 6.1 > >> > > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 > >> > > ixpclk0: on ixp0 > >> > > #################### > >> > > > >> > > Interesting, with this boot, with the new kernel, the aths did not fail. > >> > > Could the printf have changed something or was it just coincidence? With > >> > > a reboot ath1 and ath2 failed again during configuration and a little > >> > > while later ath0 started to complain: > >> > > > >> > > ath0: ath_rx_proc: no mbuf! > >> > > > >> > > John > >> > > > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> -a > >> > >> > >> > >> On 14 July 2014 01:07, John Hay wrote: > >> > >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: > >> > >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > >> > >> >> > Hi Guys, > >> > >> >> > > >> > >> >> > The problem is back / still there. I initially saw the problem during > >> > >> >> > boot, with the interface configs in rc.conf, but because it is so > >> > >> >> > mixed with the rest, I took it out and put it in the script, then > >> > >> >> > after multi-user boot was finished, I did a login and ran the script, > >> > >> >> > with the output I showed in the initial post. > >> > >> >> > > >> > >> >> > So I put the interface configs back into rc.conf and I'm seeing the > >> > >> >> > same problem, here is a cut during boot: > >> > >> >> > > >> > >> >> > ############### > >> > >> >> > Starting file system checks: > >> > >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > >> > >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > >> > >> >> > Mounting local file systems:. > >> > >> >> > Writing entropy file:. > >> > >> >> > Setting hostname: tst-cambria-11. > >> > >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 > >> > >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 > >> > >> >> > ath1: unable to start recv logic > >> > >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 > >> > >> >> > ath2: unable to start recv logic > >> > >> >> > ############### > >> > >> >> > > >> > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than > >> > >> >> > if I let it boot to multiuser and then configured the interfaces. It > >> > >> >> > was in the 6000, while now it is much higher: > >> > >> >> > > >> > >> >> > Without wlan configs in rc.conf, but configured afterwards: > >> > >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > >> > >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > >> > >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > >> > >> >> > > >> > >> >> > With wlan configs in rc.conf: > >> > >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > >> > >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > >> > >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > >> > >> >> > > >> > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but > >> > >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > >> > >> >> > that did not make a difference. > >> > >> >> > > >> > >> > > >> > >> > Friday I power cycled the board and it came up without an error. All 3 > >> > >> > atheros cards configured in rc.conf. So I left it on for the weekend > >> > >> > and by this morning there was still no errors, so I rebooted it and > >> > >> > again saw the "ath1: unable to start recv logic" message for ath1 and > >> > >> > ath2. I power cycled it, but still get the error, so Friday was just > >> > >> > lucky with some timing thing, maybe if the card receive while it is > >> > >> > still configuring? Also if I leave the board booted in this state, > >> > >> > ath0 also start to give problems: > >> > >> > > >> > >> > ################# > >> > >> > ath0: ath_rx_proc: no mbuf! > >> > >> > ath0: ath_rx_proc: no mbuf! > >> > >> > ... > >> > >> > ath0: device timeout > >> > >> > ath0: ath_reset: unable to start recv logic > >> > >> > ... > >> > >> > ################# > >> > >> > > >> > >> > In anycase it seems that memory allocation problem. How do I figure out > >> > >> > where it is? "netstat -m" does not seem to point to an error. The mbuf > >> > >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z > >> > >> > that point to an alloc failure. How do I figure out where that is and > >> > >> > how do I fix it or work around it? > >> > >> > > >> > >> > ################### > >> > >> > tst-11-arm:~ # netstat -m > >> > >> > 128/382/510 mbufs in use (current/cache/total) > >> > >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) > >> > >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) > >> > >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) > >> > >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) > >> > >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) > >> > >> > 286K/353K/639K bytes allocated to network (current/cache/total) > >> > >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > >> > >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > >> > >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > >> > >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > >> > >> > 0/3/1488 sfbufs in use (current/peak/max) > >> > >> > 0 requests for sfbufs denied > >> > >> > 0 requests for sfbufs delayed > >> > >> > 0 requests for I/O initiated by sendfile > >> > >> > tst-11-arm:~ # vmstat -z | grep mbuf > >> > >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 > >> > >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 > >> > >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 > >> > >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 > >> > >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 > >> > >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 > >> > >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 > >> > >> > tst-11-arm:~ # vmstat -z | grep Bucket > >> > >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 > >> > >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 > >> > >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 > >> > >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 > >> > >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 > >> > >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 > >> > >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 > >> > >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 > >> > >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 > >> > >> > tst-11-arm:~ # > >> > >> > ################### > >> > >> > > >> > >> > Regards > >> > >> > > >> > >> > John > >> > >> > -- > >> > >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 19:55:20 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78BA7AB8; Mon, 14 Jul 2014 19:55:20 +0000 (UTC) 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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 112FF2C94; Mon, 14 Jul 2014 19:55:20 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id j7so3046579qaq.14 for ; Mon, 14 Jul 2014 12:55:19 -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=Twoig2LCFUVsGqc/gfRFb7hex0qgBtuQIt9AMUprsFI=; b=l/ZIF+ftwjDzWdSJdaAtrCFLhKQorsT7K9xK0ZRlU25OxHu7+fZ+nryaUvGY9vGZ/q zeo4erKcD/EDlV0SMmiOVOArcAkirRwQ0QJVG19KHyomTXa9WK5Li9OaniIkx0pVcPJM c8H9+rp8y8L8ctmQRzUFQy+jKLLLDg0axwJwmBrUK1wK2uPtY0Wol6n4QKStzZWpcykp e8MmpUlrV84u87hi60H0ekAnra/DxLRqKbvCCYm+gtEDeiMtZdVqM+RJlC3J8r4E9BEi MR87TAxx4J1Q8GLnw00fMhyvQJMN09mKS9YFp39VifLmeX44ftuNT2nGNahI0nzY/tsG /xmw== MIME-Version: 1.0 X-Received: by 10.140.80.19 with SMTP id b19mr26900617qgd.102.1405367719244; Mon, 14 Jul 2014 12:55:19 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 14 Jul 2014 12:55:19 -0700 (PDT) In-Reply-To: <20140714194932.GA51947@zibbi.meraka.csir.co.za> References: <20140708165438.GA83704@zibbi.meraka.csir.co.za> <20140709044612.GA51378@zibbi.meraka.csir.co.za> <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> <20140714191416.GB49930@zibbi.meraka.csir.co.za> <20140714194932.GA51947@zibbi.meraka.csir.co.za> Date: Mon, 14 Jul 2014 12:55:19 -0700 X-Google-Sender-Auth: gyHjRAXOSsMZ7UJwmRvEyu8VhBk Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 19:55:20 -0000 Right. What's the output of hw.ath ? -a On 14 July 2014 12:49, John Hay wrote: > On Mon, Jul 14, 2014 at 12:23:47PM -0700, Adrian Chadd wrote: >> Ah, you're going to need more than 64 bounce pages. That's just not >> enough for all the mbufs the 11n support requires. >> >> It likely didn't show up in previous incarnations of this because >> pre-11n support had a much smaller pool of buffers in use. >> >> For doing 11n, there's hm, 256 TX and 256 RX buffers for each NIC? Or >> is it 512 and 512? It's something large like that. So assuming 512, >> that's 1024 * 4096 bytes each, so 4mbyte per NIC needed of bounce >> buffers. >> >> You could tweak ATH_TXBUF and ATH_RXBUF down to something like 128 TX >> and 128 RX, but you can't go much lower than that per NIC as an A-MPDU >> aggregate requires up to 64 buffers to transmit and/or receive and if >> you're not careful you'll actually overrun the RX FIFO and/or starve >> the TX code from having mbufs available to transmit with. > > I don't mind up the bounce buffers, if that will help. I'll see how > high I can go before it explode. :-) I guess one cannot easily use > the RAM above 64M for ram disks and code and then not bouncing at > all. :-/ > > I just had an ok boot, ie. all 3 aths came up without an error. So > just after a login, the bounce stats looked like this: > > tst-11-arm:~ # sysctl hw.busdma > hw.busdma.total_bpages: 64 > hw.busdma.zone0.total_bpages: 64 > hw.busdma.zone0.free_bpages: 57 > hw.busdma.zone0.reserved_bpages: 0 > hw.busdma.zone0.active_bpages: 7 > hw.busdma.zone0.total_bounced: 525 > hw.busdma.zone0.total_deferred: 0 > hw.busdma.zone0.lowaddr: 0x4000fff > hw.busdma.zone0.alignment: 4096 > > The usage seems to slowly climb though. After 30 minutes it looks like > this: > > tst-11-arm:~ # sysctl hw.busdma > hw.busdma.total_bpages: 64 > hw.busdma.zone0.total_bpages: 64 > hw.busdma.zone0.free_bpages: 43 > hw.busdma.zone0.reserved_bpages: 0 > hw.busdma.zone0.active_bpages: 21 > hw.busdma.zone0.total_bounced: 4713 > hw.busdma.zone0.total_deferred: 0 > hw.busdma.zone0.lowaddr: 0x4000fff > hw.busdma.zone0.alignment: 4096 > > The board is pretty idle, with no routing daemon or traffic except for > the occasional broadcast and multicasts that arrive. > > John > >> >> >> -a >> >> >> On 14 July 2014 12:14, John Hay wrote: >> > On Mon, Jul 14, 2014 at 09:09:46PM +0200, John Hay wrote: >> >> On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote: >> >> > .. why's it need bounce buffers? >> >> >> >> I found this: >> >> arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above must be bounced */ >> > >> > I found a sysctl to show some bounce info. :-) >> > >> > On the boot that ath1 and ath2 failed during ifconfig and ath0 started >> > to complain after a while: >> > >> > ##################### >> > tst-11-arm:~ # sysctl hw.busdma >> > hw.busdma.total_bpages: 64 >> > hw.busdma.zone0.total_bpages: 64 >> > hw.busdma.zone0.free_bpages: 0 >> > hw.busdma.zone0.reserved_bpages: 0 >> > hw.busdma.zone0.active_bpages: 64 >> > hw.busdma.zone0.total_bounced: 1191 >> > hw.busdma.zone0.total_deferred: 0 >> > hw.busdma.zone0.lowaddr: 0x4000fff >> > hw.busdma.zone0.alignment: 4096 >> > ##################### >> > >> > I then thought to down wlan0 to see if the page count changed, but >> > do not know. :-) >> > >> > ##################### >> > tst-11-arm:~ # ifconfig wlan0 down >> > dev.ath.0.debug: 0 -> 8 >> > /sbin/ifconfig.bin wlan0 down >> > ath0: ath_stop_locked: invalid 0 if_flags 0x8802 >> > Sleeping thread (tid 100019, pid 0) owns a non-sleepable lock >> > panic: sleeping thread >> > Uptime: 32m46s >> > Automatic reboot in 15 seconds - press a key on the console to abort >> > Rebooting... >> > ##################### >> > >> > John >> > >> >> >> >> John >> >> > >> >> > >> >> > -a >> >> > >> >> > >> >> > On 14 July 2014 11:42, John Hay wrote: >> >> > > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: >> >> > >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k >> >> > >> mbufs for the receive path because wifi frames are bigger than >> >> > >> ethernet frames. If you're not seeing failures in 4k mbuf allocations >> >> > >> then I'm not sure what it could be. >> >> > >> >> >> > >> I'll see about firing it up locally and checking. >> >> > > >> >> > > I'm hunting a bit more and it looks like the fail is in the bounce pages. >> >> > > It looks like the calls look like this: >> >> > > >> >> > > ath_legacy_rxbuf_init() >> >> > > bus_dmamap_load_mbuf_sg() >> >> > > _bus_dmamap_load_buffer() >> >> > > _bus_dmamap_reserve_pages() >> >> > > reserve_bounce_pages() >> >> > > >> >> > > I have added a printf at the start of alloc_bounce_pages() and it seems >> >> > > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, >> >> > > the first argument to alloc_bounce_pages(), common for the whole pci bus? >> >> > > >> >> > > The start of the boot, with my printf looks like this: >> >> > > >> >> > > #################### >> >> > > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 >> >> > > - >> >> > > Default: /boot/kernel/kernel >> >> > > boot: >> >> > > Copyright (c) 1992-2014 The FreeBSD Project. >> >> > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> >> > > The Regents of the University of California. All rights reserved. >> >> > > FreeBSD is a registered trademark of The FreeBSD Foundation. >> >> > > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 >> >> > > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S >> >> > > MALL-CAMBRIA arm >> >> > > gcc version 4.2.1 20070831 patched [FreeBSD] >> >> > > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) >> >> > > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled >> >> > > 32KB/32B 32-way instruction cache >> >> > > 32KB/32B 32-way write-back-locking data cache >> >> > > real memory = 134213632 (127 MB) >> >> > > avail memory = 124440576 (118 MB) >> >> > > random device not loaded; using insecure entropy >> >> > > wlan: mac acl policy registered >> >> > > random: initialized >> >> > > ixp0: >> >> > > ixp0: 37e7f >> >> > > pcib0: on ixp0 >> >> > > pci0: on pcib0 >> >> > > ath0: irq 28 at device 1.0 on pci0 >> >> > > alloc_bounce_pages: numpages 63 >> >> > > [ath] enabling AN_TOP2_FIXUP >> >> > > alloc_bounce_pages: numpages 1 >> >> > > ath0: AR9220 mac 128.2 RF5133 phy 13.0 >> >> > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> >> > > ath1: irq 27 at device 2.0 on pci0 >> >> > > [ath] enabling AN_TOP2_FIXUP >> >> > > ath1: AR9220 mac 128.2 RF5133 phy 13.0 >> >> > > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> >> > > ath2: irq 26 at device 3.0 on pci0 >> >> > > ath2: AR5413 mac 10.5 RF5413 phy 6.1 >> >> > > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 >> >> > > ixpclk0: on ixp0 >> >> > > #################### >> >> > > >> >> > > Interesting, with this boot, with the new kernel, the aths did not fail. >> >> > > Could the printf have changed something or was it just coincidence? With >> >> > > a reboot ath1 and ath2 failed again during configuration and a little >> >> > > while later ath0 started to complain: >> >> > > >> >> > > ath0: ath_rx_proc: no mbuf! >> >> > > >> >> > > John >> >> > > >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> -a >> >> > >> >> >> > >> On 14 July 2014 01:07, John Hay wrote: >> >> > >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: >> >> > >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: >> >> > >> >> > Hi Guys, >> >> > >> >> > >> >> > >> >> > The problem is back / still there. I initially saw the problem during >> >> > >> >> > boot, with the interface configs in rc.conf, but because it is so >> >> > >> >> > mixed with the rest, I took it out and put it in the script, then >> >> > >> >> > after multi-user boot was finished, I did a login and ran the script, >> >> > >> >> > with the output I showed in the initial post. >> >> > >> >> > >> >> > >> >> > So I put the interface configs back into rc.conf and I'm seeing the >> >> > >> >> > same problem, here is a cut during boot: >> >> > >> >> > >> >> > >> >> > ############### >> >> > >> >> > Starting file system checks: >> >> > >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS >> >> > >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) >> >> > >> >> > Mounting local file systems:. >> >> > >> >> > Writing entropy file:. >> >> > >> >> > Setting hostname: tst-cambria-11. >> >> > >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 >> >> > >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 >> >> > >> >> > ath1: unable to start recv logic >> >> > >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 >> >> > >> >> > ath2: unable to start recv logic >> >> > >> >> > ############### >> >> > >> >> > >> >> > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than >> >> > >> >> > if I let it boot to multiuser and then configured the interfaces. It >> >> > >> >> > was in the 6000, while now it is much higher: >> >> > >> >> > >> >> > >> >> > Without wlan configs in rc.conf, but configured afterwards: >> >> > >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 >> >> > >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 >> >> > >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 >> >> > >> >> > >> >> > >> >> > With wlan configs in rc.conf: >> >> > >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 >> >> > >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 >> >> > >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 >> >> > >> >> > >> >> > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but >> >> > >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but >> >> > >> >> > that did not make a difference. >> >> > >> >> > >> >> > >> > >> >> > >> > Friday I power cycled the board and it came up without an error. All 3 >> >> > >> > atheros cards configured in rc.conf. So I left it on for the weekend >> >> > >> > and by this morning there was still no errors, so I rebooted it and >> >> > >> > again saw the "ath1: unable to start recv logic" message for ath1 and >> >> > >> > ath2. I power cycled it, but still get the error, so Friday was just >> >> > >> > lucky with some timing thing, maybe if the card receive while it is >> >> > >> > still configuring? Also if I leave the board booted in this state, >> >> > >> > ath0 also start to give problems: >> >> > >> > >> >> > >> > ################# >> >> > >> > ath0: ath_rx_proc: no mbuf! >> >> > >> > ath0: ath_rx_proc: no mbuf! >> >> > >> > ... >> >> > >> > ath0: device timeout >> >> > >> > ath0: ath_reset: unable to start recv logic >> >> > >> > ... >> >> > >> > ################# >> >> > >> > >> >> > >> > In anycase it seems that memory allocation problem. How do I figure out >> >> > >> > where it is? "netstat -m" does not seem to point to an error. The mbuf >> >> > >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z >> >> > >> > that point to an alloc failure. How do I figure out where that is and >> >> > >> > how do I fix it or work around it? >> >> > >> > >> >> > >> > ################### >> >> > >> > tst-11-arm:~ # netstat -m >> >> > >> > 128/382/510 mbufs in use (current/cache/total) >> >> > >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) >> >> > >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) >> >> > >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) >> >> > >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) >> >> > >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) >> >> > >> > 286K/353K/639K bytes allocated to network (current/cache/total) >> >> > >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) >> >> > >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) >> >> > >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) >> >> > >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >> >> > >> > 0/3/1488 sfbufs in use (current/peak/max) >> >> > >> > 0 requests for sfbufs denied >> >> > >> > 0 requests for sfbufs delayed >> >> > >> > 0 requests for I/O initiated by sendfile >> >> > >> > tst-11-arm:~ # vmstat -z | grep mbuf >> >> > >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 >> >> > >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 >> >> > >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 >> >> > >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 >> >> > >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 >> >> > >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 >> >> > >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 >> >> > >> > tst-11-arm:~ # vmstat -z | grep Bucket >> >> > >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 >> >> > >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 >> >> > >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 >> >> > >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 >> >> > >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 >> >> > >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 >> >> > >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 >> >> > >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 >> >> > >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 >> >> > >> > tst-11-arm:~ # >> >> > >> > ################### >> >> > >> > >> >> > >> > Regards >> >> > >> > >> >> > >> > John >> >> > >> > -- >> >> > >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org >> >> _______________________________________________ >> >> freebsd-wireless@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 20:00:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C7CAC11; Mon, 14 Jul 2014 20:00:18 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 1DB4A2CED; Mon, 14 Jul 2014 20:00:17 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id E5772B842; Mon, 14 Jul 2014 22:00:15 +0200 (SAST) Date: Mon, 14 Jul 2014 22:00:15 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714200015.GA54311@zibbi.meraka.csir.co.za> References: <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> <20140714191416.GB49930@zibbi.meraka.csir.co.za> <20140714194932.GA51947@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 20:00:18 -0000 On Mon, Jul 14, 2014 at 12:55:19PM -0700, Adrian Chadd wrote: > Right. What's the output of hw.ath ? tst-11-arm:~ # sysctl hw.ath hw.ath.bstuck: 4 hw.ath.txbuf_mgmt: 32 hw.ath.txbuf: 200 hw.ath.rxbuf: 40 hw.ath.anical: 100 hw.ath.resetcal: 1200 hw.ath.shortcal: 100 hw.ath.longcal: 30 hw.ath.debug: 0 hw.ath.hal.debug: 0 All 3 interfaces are in adhoc mode if it makes a difference. John > > > -a > > > On 14 July 2014 12:49, John Hay wrote: > > On Mon, Jul 14, 2014 at 12:23:47PM -0700, Adrian Chadd wrote: > >> Ah, you're going to need more than 64 bounce pages. That's just not > >> enough for all the mbufs the 11n support requires. > >> > >> It likely didn't show up in previous incarnations of this because > >> pre-11n support had a much smaller pool of buffers in use. > >> > >> For doing 11n, there's hm, 256 TX and 256 RX buffers for each NIC? Or > >> is it 512 and 512? It's something large like that. So assuming 512, > >> that's 1024 * 4096 bytes each, so 4mbyte per NIC needed of bounce > >> buffers. > >> > >> You could tweak ATH_TXBUF and ATH_RXBUF down to something like 128 TX > >> and 128 RX, but you can't go much lower than that per NIC as an A-MPDU > >> aggregate requires up to 64 buffers to transmit and/or receive and if > >> you're not careful you'll actually overrun the RX FIFO and/or starve > >> the TX code from having mbufs available to transmit with. > > > > I don't mind up the bounce buffers, if that will help. I'll see how > > high I can go before it explode. :-) I guess one cannot easily use > > the RAM above 64M for ram disks and code and then not bouncing at > > all. :-/ > > > > I just had an ok boot, ie. all 3 aths came up without an error. So > > just after a login, the bounce stats looked like this: > > > > tst-11-arm:~ # sysctl hw.busdma > > hw.busdma.total_bpages: 64 > > hw.busdma.zone0.total_bpages: 64 > > hw.busdma.zone0.free_bpages: 57 > > hw.busdma.zone0.reserved_bpages: 0 > > hw.busdma.zone0.active_bpages: 7 > > hw.busdma.zone0.total_bounced: 525 > > hw.busdma.zone0.total_deferred: 0 > > hw.busdma.zone0.lowaddr: 0x4000fff > > hw.busdma.zone0.alignment: 4096 > > > > The usage seems to slowly climb though. After 30 minutes it looks like > > this: > > > > tst-11-arm:~ # sysctl hw.busdma > > hw.busdma.total_bpages: 64 > > hw.busdma.zone0.total_bpages: 64 > > hw.busdma.zone0.free_bpages: 43 > > hw.busdma.zone0.reserved_bpages: 0 > > hw.busdma.zone0.active_bpages: 21 > > hw.busdma.zone0.total_bounced: 4713 > > hw.busdma.zone0.total_deferred: 0 > > hw.busdma.zone0.lowaddr: 0x4000fff > > hw.busdma.zone0.alignment: 4096 > > > > The board is pretty idle, with no routing daemon or traffic except for > > the occasional broadcast and multicasts that arrive. > > > > John > > > >> > >> > >> -a > >> > >> > >> On 14 July 2014 12:14, John Hay wrote: > >> > On Mon, Jul 14, 2014 at 09:09:46PM +0200, John Hay wrote: > >> >> On Mon, Jul 14, 2014 at 12:06:34PM -0700, Adrian Chadd wrote: > >> >> > .. why's it need bounce buffers? > >> >> > >> >> I found this: > >> >> arm/xscale/ixp425/ixp425_pci.c: /* NB: PCI dma window is 64M so anything above must be bounced */ > >> > > >> > I found a sysctl to show some bounce info. :-) > >> > > >> > On the boot that ath1 and ath2 failed during ifconfig and ath0 started > >> > to complain after a while: > >> > > >> > ##################### > >> > tst-11-arm:~ # sysctl hw.busdma > >> > hw.busdma.total_bpages: 64 > >> > hw.busdma.zone0.total_bpages: 64 > >> > hw.busdma.zone0.free_bpages: 0 > >> > hw.busdma.zone0.reserved_bpages: 0 > >> > hw.busdma.zone0.active_bpages: 64 > >> > hw.busdma.zone0.total_bounced: 1191 > >> > hw.busdma.zone0.total_deferred: 0 > >> > hw.busdma.zone0.lowaddr: 0x4000fff > >> > hw.busdma.zone0.alignment: 4096 > >> > ##################### > >> > > >> > I then thought to down wlan0 to see if the page count changed, but > >> > do not know. :-) > >> > > >> > ##################### > >> > tst-11-arm:~ # ifconfig wlan0 down > >> > dev.ath.0.debug: 0 -> 8 > >> > /sbin/ifconfig.bin wlan0 down > >> > ath0: ath_stop_locked: invalid 0 if_flags 0x8802 > >> > Sleeping thread (tid 100019, pid 0) owns a non-sleepable lock > >> > panic: sleeping thread > >> > Uptime: 32m46s > >> > Automatic reboot in 15 seconds - press a key on the console to abort > >> > Rebooting... > >> > ##################### > >> > > >> > John > >> > > >> >> > >> >> John > >> >> > > >> >> > > >> >> > -a > >> >> > > >> >> > > >> >> > On 14 July 2014 11:42, John Hay wrote: > >> >> > > On Mon, Jul 14, 2014 at 09:48:56AM -0700, Adrian Chadd wrote: > >> >> > >> Hm, it could be some bus related stupidity. It's allocating 2k or 4k > >> >> > >> mbufs for the receive path because wifi frames are bigger than > >> >> > >> ethernet frames. If you're not seeing failures in 4k mbuf allocations > >> >> > >> then I'm not sure what it could be. > >> >> > >> > >> >> > >> I'll see about firing it up locally and checking. > >> >> > > > >> >> > > I'm hunting a bit more and it looks like the fail is in the bounce pages. > >> >> > > It looks like the calls look like this: > >> >> > > > >> >> > > ath_legacy_rxbuf_init() > >> >> > > bus_dmamap_load_mbuf_sg() > >> >> > > _bus_dmamap_load_buffer() > >> >> > > _bus_dmamap_reserve_pages() > >> >> > > reserve_bounce_pages() > >> >> > > > >> >> > > I have added a printf at the start of alloc_bounce_pages() and it seems > >> >> > > that it is only called (twice) when ath0 is probed. Is bus_dma_tag_t dmat, > >> >> > > the first argument to alloc_bounce_pages(), common for the whole pci bus? > >> >> > > > >> >> > > The start of the boot, with my printf looks like this: > >> >> > > > >> >> > > #################### > >> >> > > FreeBSD ARM (Gateworks Cambria) boot2 v0.4 > >> >> > > - > >> >> > > Default: /boot/kernel/kernel > >> >> > > boot: > >> >> > > Copyright (c) 1992-2014 The FreeBSD Project. > >> >> > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > >> >> > > The Regents of the University of California. All rights reserved. > >> >> > > FreeBSD is a registered trademark of The FreeBSD Foundation. > >> >> > > FreeBSD 11.0-CURRENT #9 r268502M: Mon Jul 14 15:30:15 SAST 2014 > >> >> > > jhay@dolphin.meraka.csir.co.za:/usr/obj/arm.armeb/snaps/arm/11-tst/src/sys/S > >> >> > > MALL-CAMBRIA arm > >> >> > > gcc version 4.2.1 20070831 patched [FreeBSD] > >> >> > > CPU: IXP435 rev 1 (ARMv5TE) (XScale core) > >> >> > > Big-endian DC enabled IC enabled WB enabled LABT branch prediction enabled > >> >> > > 32KB/32B 32-way instruction cache > >> >> > > 32KB/32B 32-way write-back-locking data cache > >> >> > > real memory = 134213632 (127 MB) > >> >> > > avail memory = 124440576 (118 MB) > >> >> > > random device not loaded; using insecure entropy > >> >> > > wlan: mac acl policy registered > >> >> > > random: initialized > >> >> > > ixp0: > >> >> > > ixp0: 37e7f > >> >> > > pcib0: on ixp0 > >> >> > > pci0: on pcib0 > >> >> > > ath0: irq 28 at device 1.0 on pci0 > >> >> > > alloc_bounce_pages: numpages 63 > >> >> > > [ath] enabling AN_TOP2_FIXUP > >> >> > > alloc_bounce_pages: numpages 1 > >> >> > > ath0: AR9220 mac 128.2 RF5133 phy 13.0 > >> >> > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > >> >> > > ath1: irq 27 at device 2.0 on pci0 > >> >> > > [ath] enabling AN_TOP2_FIXUP > >> >> > > ath1: AR9220 mac 128.2 RF5133 phy 13.0 > >> >> > > ath1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > >> >> > > ath2: irq 26 at device 3.0 on pci0 > >> >> > > ath2: AR5413 mac 10.5 RF5413 phy 6.1 > >> >> > > ath2: 2GHz radio: 0x0000; 5GHz radio: 0x0063 > >> >> > > ixpclk0: on ixp0 > >> >> > > #################### > >> >> > > > >> >> > > Interesting, with this boot, with the new kernel, the aths did not fail. > >> >> > > Could the printf have changed something or was it just coincidence? With > >> >> > > a reboot ath1 and ath2 failed again during configuration and a little > >> >> > > while later ath0 started to complain: > >> >> > > > >> >> > > ath0: ath_rx_proc: no mbuf! > >> >> > > > >> >> > > John > >> >> > > > >> >> > >> > >> >> > >> > >> >> > >> > >> >> > >> > >> >> > >> -a > >> >> > >> > >> >> > >> On 14 July 2014 01:07, John Hay wrote: > >> >> > >> > On Thu, Jul 10, 2014 at 06:02:27AM +0200, John Hay wrote: > >> >> > >> >> On Wed, Jul 09, 2014 at 06:46:12AM +0200, John Hay wrote: > >> >> > >> >> > Hi Guys, > >> >> > >> >> > > >> >> > >> >> > The problem is back / still there. I initially saw the problem during > >> >> > >> >> > boot, with the interface configs in rc.conf, but because it is so > >> >> > >> >> > mixed with the rest, I took it out and put it in the script, then > >> >> > >> >> > after multi-user boot was finished, I did a login and ran the script, > >> >> > >> >> > with the output I showed in the initial post. > >> >> > >> >> > > >> >> > >> >> > So I put the interface configs back into rc.conf and I'm seeing the > >> >> > >> >> > same problem, here is a cut during boot: > >> >> > >> >> > > >> >> > >> >> > ############### > >> >> > >> >> > Starting file system checks: > >> >> > >> >> > /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > >> >> > >> >> > /dev/ad0s1a: clean, 93385 free (33 frags, 11669 blocks, 0.0% fragmentation) > >> >> > >> >> > Mounting local file systems:. > >> >> > >> >> > Writing entropy file:. > >> >> > >> >> > Setting hostname: tst-cambria-11. > >> >> > >> >> > wlan0: Ethernet address: 00:21:a4:35:70:42 > >> >> > >> >> > wlan1: Ethernet address: 00:21:a4:35:6c:96 > >> >> > >> >> > ath1: unable to start recv logic > >> >> > >> >> > wlan2: Ethernet address: 00:21:a4:32:38:c2 > >> >> > >> >> > ath2: unable to start recv logic > >> >> > >> >> > ############### > >> >> > >> >> > > >> >> > >> >> > Looking at the vmstat -z output the 256 Bucket fail is much higher than > >> >> > >> >> > if I let it boot to multiuser and then configured the interfaces. It > >> >> > >> >> > was in the 6000, while now it is much higher: > >> >> > >> >> > > >> >> > >> >> > Without wlan configs in rc.conf, but configured afterwards: > >> >> > >> >> > 16 Bucket: 64, 0, 15, 300, 3139, 16, 0 > >> >> > >> >> > 256 Bucket: 1024, 0, 31, 1, 592,6062, 0 > >> >> > >> >> > vmem btag: 28, 0, 4496, 256, 4496, 32, 0 > >> >> > >> >> > > >> >> > >> >> > With wlan configs in rc.conf: > >> >> > >> >> > 16 Bucket: 64, 0, 16, 299, 8611, 16, 0 > >> >> > >> >> > 256 Bucket: 1024, 0, 26, 6, 773,16928, 0 > >> >> > >> >> > vmem btag: 28, 0, 4405, 59, 4405, 30, 0 > >> >> > >> >> > > >> >> > >> >> > Both of them boot from a ro compact-flash with md /etc and /var, but > >> >> > >> >> > they are small 4.3M and 2.1M. I have hacked in the use of tmpfs, but > >> >> > >> >> > that did not make a difference. > >> >> > >> >> > > >> >> > >> > > >> >> > >> > Friday I power cycled the board and it came up without an error. All 3 > >> >> > >> > atheros cards configured in rc.conf. So I left it on for the weekend > >> >> > >> > and by this morning there was still no errors, so I rebooted it and > >> >> > >> > again saw the "ath1: unable to start recv logic" message for ath1 and > >> >> > >> > ath2. I power cycled it, but still get the error, so Friday was just > >> >> > >> > lucky with some timing thing, maybe if the card receive while it is > >> >> > >> > still configuring? Also if I leave the board booted in this state, > >> >> > >> > ath0 also start to give problems: > >> >> > >> > > >> >> > >> > ################# > >> >> > >> > ath0: ath_rx_proc: no mbuf! > >> >> > >> > ath0: ath_rx_proc: no mbuf! > >> >> > >> > ... > >> >> > >> > ath0: device timeout > >> >> > >> > ath0: ath_reset: unable to start recv logic > >> >> > >> > ... > >> >> > >> > ################# > >> >> > >> > > >> >> > >> > In anycase it seems that memory allocation problem. How do I figure out > >> >> > >> > where it is? "netstat -m" does not seem to point to an error. The mbuf > >> >> > >> > info in vmstat -z also look ok. It is only "256 Bucket" in vmstat -z > >> >> > >> > that point to an alloc failure. How do I figure out where that is and > >> >> > >> > how do I fix it or work around it? > >> >> > >> > > >> >> > >> > ################### > >> >> > >> > tst-11-arm:~ # netstat -m > >> >> > >> > 128/382/510 mbufs in use (current/cache/total) > >> >> > >> > 127/129/256/7654 mbuf clusters in use (current/cache/total/max) > >> >> > >> > 127/126 mbuf+clusters out of packet secondary zone in use (current/cache) > >> >> > >> > 0/0/0/3827 4k (page size) jumbo clusters in use (current/cache/total/max) > >> >> > >> > 0/0/0/1134 9k jumbo clusters in use (current/cache/total/max) > >> >> > >> > 0/0/0/637 16k jumbo clusters in use (current/cache/total/max) > >> >> > >> > 286K/353K/639K bytes allocated to network (current/cache/total) > >> >> > >> > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > >> >> > >> > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > >> >> > >> > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > >> >> > >> > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > >> >> > >> > 0/3/1488 sfbufs in use (current/peak/max) > >> >> > >> > 0 requests for sfbufs denied > >> >> > >> > 0 requests for sfbufs delayed > >> >> > >> > 0 requests for I/O initiated by sendfile > >> >> > >> > tst-11-arm:~ # vmstat -z | grep mbuf > >> >> > >> > mbuf_packet: 256, 48990, 127, 126, 2294, 0, 0 > >> >> > >> > mbuf: 256, 48990, 1, 256, 920, 0, 0 > >> >> > >> > mbuf_cluster: 2048, 7654, 253, 3, 253, 0, 0 > >> >> > >> > mbuf_jumbo_page: 4096, 3827, 0, 0, 0, 0, 0 > >> >> > >> > mbuf_jumbo_9k: 9216, 1134, 0, 0, 0, 0, 0 > >> >> > >> > mbuf_jumbo_16k: 16384, 637, 0, 0, 0, 0, 0 > >> >> > >> > mbuf_ext_refcnt: 4, 0, 0, 504, 1, 0, 0 > >> >> > >> > tst-11-arm:~ # vmstat -z | grep Bucket > >> >> > >> > 4 Bucket: 16, 0, 7, 497, 1565, 0, 0 > >> >> > >> > 6 Bucket: 24, 0, 0, 0, 0, 0, 0 > >> >> > >> > 8 Bucket: 32, 0, 3, 375, 83, 0, 0 > >> >> > >> > 12 Bucket: 48, 0, 2, 334, 5, 0, 0 > >> >> > >> > 16 Bucket: 64, 0, 14, 301, 43687, 16, 0 > >> >> > >> > 32 Bucket: 128, 0, 7, 148, 196, 0, 0 > >> >> > >> > 64 Bucket: 256, 0, 19, 56, 77, 0, 0 > >> >> > >> > 128 Bucket: 512, 0, 16, 16, 48, 0, 0 > >> >> > >> > 256 Bucket: 1024, 0, 29, 3, 1521,86738, 0 > >> >> > >> > tst-11-arm:~ # > >> >> > >> > ################### > >> >> > >> > > >> >> > >> > Regards > >> >> > >> > > >> >> > >> > John > >> >> > >> > -- > >> >> > >> > John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za / jhay@FreeBSD.org > >> >> _______________________________________________ > >> >> freebsd-wireless@freebsd.org mailing list > >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 20:02:04 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB880C83; Mon, 14 Jul 2014 20:02:04 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53AF92D6C; Mon, 14 Jul 2014 20:02:04 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id c9so4179694qcz.1 for ; Mon, 14 Jul 2014 13:02:03 -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=DFUSNSjql9mNhPSJOYoJdhGf3esdmJDBc+NYWi9bwwE=; b=rtLEe53ONSBhydrwK6Mu5X5B+kljynuyFYGbR78zIaMKV+Fi/ZA/aZtImhCOy/lsV/ caQzVvIissdsyvffXa3562VlKTJZjoDjE4k6+xJLhg1uMyeR9fNb2g3DJoaNTBE2y6Zx KaB1JcljK3pAUASQHAGtGO1RFRshWfCJp8qSlIVFvcxoZo/lFnyS+kp63sd9a1kOjHvo /vZEODlrJ197rSTa2oZVyXpExhqZJ8+Y3tkA0lEFEUM5A3kF7WUzqPUB1soRcALfXeWn kkFomLrAMLcK/0XyRKUDiV7sJOylkVnfn+bXEqbLBq5xC9dmhrs+n2RpDAkW2w9Tcdm0 PakA== MIME-Version: 1.0 X-Received: by 10.224.156.145 with SMTP id x17mr27345963qaw.49.1405368123517; Mon, 14 Jul 2014 13:02:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.202.193 with HTTP; Mon, 14 Jul 2014 13:02:03 -0700 (PDT) In-Reply-To: <20140714200015.GA54311@zibbi.meraka.csir.co.za> References: <20140710040227.GA73872@zibbi.meraka.csir.co.za> <20140714080708.GA88464@zibbi.meraka.csir.co.za> <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> <20140714191416.GB49930@zibbi.meraka.csir.co.za> <20140714194932.GA51947@zibbi.meraka.csir.co.za> <20140714200015.GA54311@zibbi.meraka.csir.co.za> Date: Mon, 14 Jul 2014 13:02:03 -0700 X-Google-Sender-Auth: OUHqmVDJ6wF7oM0YhWnEZZzOWJ0 Message-ID: Subject: Re: CAMBRIA and more than one atheros card From: Adrian Chadd To: John Hay Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 20:02:04 -0000 On 14 July 2014 13:00, John Hay wrote: > On Mon, Jul 14, 2014 at 12:55:19PM -0700, Adrian Chadd wrote: >> Right. What's the output of hw.ath ? > > tst-11-arm:~ # sysctl hw.ath > hw.ath.bstuck: 4 > hw.ath.txbuf_mgmt: 32 > hw.ath.txbuf: 200 > hw.ath.rxbuf: 40 > hw.ath.anical: 100 > hw.ath.resetcal: 1200 > hw.ath.shortcal: 100 > hw.ath.longcal: 30 > hw.ath.debug: 0 > hw.ath.hal.debug: 0 > > All 3 interfaces are in adhoc mode if it makes a difference. Ah, you're not even using it in 11n mode. Ok. Well, that's 72 mbufs allocated, and up to 200 more being allocated during transmit. Then there's the handful of pages being used for DMA descriptors. So yeah, over time that may become a problem. Try doubling the number of bounce buffers available and see what happens. -a From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 14 20:37:16 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CC665EB6; Mon, 14 Jul 2014 20:37:16 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [146.64.24.58]) by mx1.freebsd.org (Postfix) with ESMTP id 033882107; Mon, 14 Jul 2014 20:37:15 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id E3C3CB842; Mon, 14 Jul 2014 22:37:07 +0200 (SAST) Date: Mon, 14 Jul 2014 22:37:07 +0200 From: John Hay To: Adrian Chadd Subject: Re: CAMBRIA and more than one atheros card Message-ID: <20140714203707.GB54311@zibbi.meraka.csir.co.za> References: <20140714184209.GA21922@zibbi.meraka.csir.co.za> <20140714190946.GA49930@zibbi.meraka.csir.co.za> <20140714191416.GB49930@zibbi.meraka.csir.co.za> <20140714194932.GA51947@zibbi.meraka.csir.co.za> <20140714200015.GA54311@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , "freebsd-embedded@freebsd.org" , Ian Lepore X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 20:37:17 -0000 On Mon, Jul 14, 2014 at 01:02:03PM -0700, Adrian Chadd wrote: > On 14 July 2014 13:00, John Hay wrote: > > On Mon, Jul 14, 2014 at 12:55:19PM -0700, Adrian Chadd wrote: > >> Right. What's the output of hw.ath ? > > > > tst-11-arm:~ # sysctl hw.ath > > hw.ath.bstuck: 4 > > hw.ath.txbuf_mgmt: 32 > > hw.ath.txbuf: 200 > > hw.ath.rxbuf: 40 > > hw.ath.anical: 100 > > hw.ath.resetcal: 1200 > > hw.ath.shortcal: 100 > > hw.ath.longcal: 30 > > hw.ath.debug: 0 > > hw.ath.hal.debug: 0 > > > > All 3 interfaces are in adhoc mode if it makes a difference. > > Ah, you're not even using it in 11n mode. Ok. > > Well, that's 72 mbufs allocated, and up to 200 more being allocated > during transmit. Then there's the handful of pages being used for DMA > descriptors. So yeah, over time that may become a problem. > > Try doubling the number of bounce buffers available and see what happens. The first boot looks good, all 3 aths came up. Bounce buffers just after login: tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 128 hw.busdma.zone0.total_bpages: 128 hw.busdma.zone0.free_bpages: 128 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 0 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 It stayed like that for about 6-7 minutes, then looked like this: tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 128 hw.busdma.zone0.total_bpages: 128 hw.busdma.zone0.free_bpages: 126 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 2 hw.busdma.zone0.total_bounced: 208 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 After 13 minutes: tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 128 hw.busdma.zone0.total_bpages: 128 hw.busdma.zone0.free_bpages: 124 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 4 hw.busdma.zone0.total_bounced: 667 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 After 26 minutes: tst-11-arm:~ # sysctl hw.busdma hw.busdma.total_bpages: 128 hw.busdma.zone0.total_bpages: 128 hw.busdma.zone0.free_bpages: 121 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 7 hw.busdma.zone0.total_bounced: 2433 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x4000fff hw.busdma.zone0.alignment: 4096 Great! At last it seems like we are making progress. I'll leave it till the morning and then do a few reboots and then some traffic. One question, should the active bounce pages keep growing or stabilize somewhere? How do I know if I have to few or if there is a leak? Thanks Adrian for your help. John -- John Hay -- jhay@meraka.csir.co.za / jhay@meraka.org.za