From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 14 21:01:49 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8EFF1C6 for ; Sun, 14 Jul 2013 21:01:49 +0000 (UTC) (envelope-from thinker.lp@gmail.com) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id 7732F62C for ; Sun, 14 Jul 2013 21:01:49 +0000 (UTC) Received: by mail-la0-f49.google.com with SMTP id ea20so8790346lab.22 for ; Sun, 14 Jul 2013 14:01:48 -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=JSwO7gIhyBojGFcB23WGI4gHMgs2fgSGQPp4UKSAliQ=; b=bnw6fqOrtPqcS4Hv/5rSnKn0VYwwLf5Y73CJoJzOAjYV8bhLMuKiV1Ye3wWryC+rP0 uRPx1Vj8fSv/PmL7HOnyhAhD52tK8Tj3n/hqF9Kj+4mUgLanU4VU75T63Ns7ac9isrqr sUGRqhnM0gECNSuBTbFb+E2wJaAnToGf1QVk90kkIZmAqNE5StYtSKizBarAU297xgTx PSrZ031G0/BkjJVOEbxJ7+IbVm6WeOMCHca0CE51lr10e46udzaiuDkjPf/whUPrReuo 3Kx6Lo05iL9vuSdvyIj0SEeyM7hxMsgvyn9TjrkqLYllKtjdTqZyjqVF4lTSwf6unoTQ i95w== MIME-Version: 1.0 X-Received: by 10.152.19.40 with SMTP id b8mr23213853lae.34.1373835707933; Sun, 14 Jul 2013 14:01:47 -0700 (PDT) Received: by 10.114.176.35 with HTTP; Sun, 14 Jul 2013 14:01:47 -0700 (PDT) Date: Mon, 15 Jul 2013 00:01:47 +0300 Message-ID: Subject: Atheros 9287 From: Jonas Liepuonius To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 21:01:50 -0000 Hello, I recently installed FreeBSD 9.1 and having some problems with wifi. Someone from the FreeBSD forums suggested that I write in here. So basically my problem is that after establishing connection with my wireless router and let's say download files for a port, the network hangs after a few seconds. Once that happens seems that almost none traffic comes through. The odd thing happens that when wireless hangs I can't access my SSH over a cable which shouldn't be affected by wifi. I'm using an Atheros 9287 chip, with WPA2-PSK AES encryption. From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 14 22:32:28 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6625A5C7 for ; Sun, 14 Jul 2013 22:32:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by mx1.freebsd.org (Postfix) with ESMTP id F2046315 for ; Sun, 14 Jul 2013 22:32:27 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id k10so2256870wiv.1 for ; Sun, 14 Jul 2013 15:32: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=OhBldRg/1x0ruq5slLpAmUz5pG8wbfKz1QhNQcyABgw=; b=SjhCoZmx+8tkt363zabh0UDEAIzt5oziuMCoQ+lWpLemgRDNv/GAAVz0+5Q3E5KmK/ OelYQWpUV8FayZaXbYAU2Ptq8Jcb8AUMwHASTKyw9V/voOB5nJ5TFPTXFwPVgbmlTcMw 8TKWGoixoN5jjAB3W/xNVCW5CD7cfvYsKhrIEd9tdTw2rDW0B4C9pVys98vw6et50yF/ o2NseF+VLwpY2Duh2aHBlBkDfDrYwxFDdvRlSO8qnTAFqGnpg9r5bHd1TTFJvXf4uLoN UAbNVNPnyHhdU4nVu2iPCjMz8ouTeCgokc7cuRUUj//BclNY1MuPugR6nWUkFR495EDZ PllA== MIME-Version: 1.0 X-Received: by 10.180.14.105 with SMTP id o9mr732882wic.30.1373841146946; Sun, 14 Jul 2013 15:32:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Sun, 14 Jul 2013 15:32:26 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Jul 2013 15:32:26 -0700 X-Google-Sender-Auth: UfZ0niAbGr6fHOtWqsoNv8261yw Message-ID: Subject: Re: Atheros 9287 From: Adrian Chadd To: Jonas Liepuonius Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 22:32:28 -0000 Hi, Is it negotiating 11n? If so, you should turn it off. 11n and ath(4) is only usable on 10. -adiran On 14 July 2013 14:01, Jonas Liepuonius wrote: > Hello, > > I recently installed FreeBSD 9.1 and having some problems with wifi. > Someone from the FreeBSD forums suggested that I write in here. So > basically my problem is that after establishing connection with my wireless > router and let's say download files for a port, the network hangs after a > few seconds. Once that happens seems that almost none traffic comes > through. The odd thing happens that when wireless hangs I can't access my > SSH over a cable which shouldn't be affected by wifi. > > I'm using an Atheros 9287 chip, with WPA2-PSK AES encryption. > _______________________________________________ > 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 15 04:13:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4396DE68 for ; Mon, 15 Jul 2013 04:13:27 +0000 (UTC) (envelope-from ghw@7axu.com) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) by mx1.freebsd.org (Postfix) with ESMTP id C13A56EB for ; Mon, 15 Jul 2013 04:13:25 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id w59so9607860wes.38 for ; Sun, 14 Jul 2013 21:13:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=yyqPN0HNEwV7pT8D2Vq9oTzV6+PanGI/n/C2t84oCTY=; b=oaoD/46dM+oihcsURgAiRuYf68wm9YSr99u27S2zr8PcO3EfF52IC6d4+ZoF7v3gbg lIVV5ZfO89XWuAWBVw9ShokGYCWGhM2/vdWu17Avn3h+fSjOFtEPgv4fk9QA/cxljQJ1 XkmTdu7q39QVrA3TRBa4BYsquzeSiYoo3KnUQy/v18NCf6G1kWJjF+8q+88yu5m0TIc7 9RakUe5Fa3pmKvNi54ENY+pG7UHj9Im3vmHVbIzD8qdy2wD9cGE4fHSXnAyFkbFrlj1W J0gkvIvzYHG0GRrciMpwWcVDtHRGr6hgLM3mdUFJ6YX50T3cGO9RgD3Ji13QzKMB6nTB DHCw== X-Received: by 10.180.185.148 with SMTP id fc20mr7732248wic.0.1373861598824; Sun, 14 Jul 2013 21:13:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.93.34 with HTTP; Sun, 14 Jul 2013 21:12:38 -0700 (PDT) X-Originating-IP: [124.160.63.202] From: XiaoQI Ge Date: Mon, 15 Jul 2013 12:12:38 +0800 Message-ID: Subject: My WLI-UC-GNM up crash To: freebsd-wireless@freebsd.org, freebsd-arm X-Gm-Message-State: ALoCoQk46KzUdy/qNXEVHOwnPhDc5vnutqH/lLkKcm0zFxOYtvvMtB8t6iNU6rTxWRxPU95Nnles Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 04:13:27 -0000 My WLI-UC-GNM ifconfig up when collapsed, I do not know how to solve root@FreeBSD:~ # ifconfig wlan create wlandev run0 wlan0: Ethernet address: 10:6f:3f:2b:fd:6d wlan0 root@FreeBSD:~ # ifconfig lo0: flags=3D8049 metric 0 mtu 16384 options=3D600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=3D21 run0: flags=3D8802 metric 0 mtu 2290 ether 10:6f:3f:2b:fd:6d nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier wlan0: flags=3D8802 metric 0 mtu 1500 ether 10:6f:3f:2b:fd:6d nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11b) country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 wme bintval 0 root@FreeBSD:~ # dhclient wlan0 wlan0: no link .............. giving up root@FreeBSD:~ # pciconf -lv pciconf: /dev/pci: No such file or directory root@FreeBSD:~ # ifconfig wlan0 up scan run0: firmware RT2870 ver. 0.236 loaded root@FreeBSD:~ # Fatal kernel mode data abort: 'Alignment Fault 1' trapframe: 0xde177d68 FSR=3D00000801, FAR=3Dc24b3faf, spsr=3D00000013 r0 =3Dc24b7000, r1 =3Dc24b3faf, r2 =3Dc24b720c, r3 =3D0000096c r4 =3D80003eaf, r5 =3Dc249c800, r6 =3Dc24b7024, r7 =3Dc0760898 r8 =3Dc24b7000, r9 =3D00000014, r10=3Dc055851d, r11=3Dde177e18 r12=3D0000002e, ssp=3Dde177db4, slr=3D00000000, pc =3Dc04072d4 [ thread pid 0 tid 100038 ] Stopped at ieee80211_radiotap_chan_change+0x94: strh r3, [r1] db> bt Tracing pid 0 tid 100038 td 0xc232a620 _end() at 0xde177a90 scp=3D0xde177a90 rlv=3D0xc04f5e48 (db_trace_thread+0x34) rsp=3D0xde177a74 rfp=3D0xc05b8750 Bad frame pointer: 0xc05b8750 db> =3D =E2=80=8B=3Ddmesg=3D=3D sun4i#go 0x40200100 ## Starting application at 0x40200100 ... KDB: debugger backends: ddb KDB: current backend: ddb 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 10.0-CURRENT #1: Sat Jul 13 23:09:25 CST 2013 root@FreeBSD.7axu.com:/usr/obj/armv6/arm.arm/usr/src/sys/CB1G arm FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 WARNING: WITNESS option enabled, expect reduced performance. CPU: Cortex A8-r3 rev 2 (Cortex-A core) Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext WB disabled EABT branch prediction enabled LoUU:2 LoC:2 LoUIS:1 Cache level 1: 32KB/64B 4-way data cache WT WB Read-Alloc 32KB/64B 4-way instruction cache Read-Alloc Cache level 2: 256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc real memory =3D 536870912 (512 MB) avail memory =3D 513032192 (489 MB) random device not loaded; using insecure entropy simplebus0: on fdtbus0 aintc0: mem 0x1c20400-0x1c207ff on simplebus0 a10_ccm0: mem 0x1c20000-0x1c203ff on simplebus0 a10_timer0: mem 0x1c20c00-0x1c20c8f irq 22 on simplebus0 Event timer "a10_timer Eventtimer" frequency 24000000 Hz quality 1000 Timecounter "a10_timer timer0" frequency 24000000 Hz quality 1000 a10wd0: mem 0x1c20c90-0x1c20c97 on simplebus0 gpio0: mem 0x1c20800-0x1c20bff irq 28 on simplebus0 gpioc0: on gpio0 gpiobus0: on gpio0 ehci0: mem 0x1c14000-0x1c14fff irq 39 on simplebus0 usbus0: EHCI version 1.0 usbus0 on ehci0 ehci1: mem 0x1c1c000-0x1c1cfff irq 40 on simplebus0 usbus1: EHCI version 1.0 usbus1 on ehci1 uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 1 on simplebus0 uart0: console (115200,n,8,1) Timecounters tick every 10.000 msec usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 WARNING: WITNESS option enabled, expect reduced performance. Root mount waiting for: usbus1 usbus0 ugen1.1: at usbus1 uhub0: on usbus= 1 ugen0.1: at usbus0 uhub1: on usbus= 0 uhub0: 1 port with 1 removable, self powered uhub1: 1 port with 1 removable, self powered Root mount waiting for: usbus1 usbus0 Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 run0: <1.0> on usbus0 run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 10:6f:3f:2b:fd :6d Root mount waiting for: usbus1 ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0x0100 umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 7722MB (15814656 512 byte sectors: 255H 63S/T 984C) da0: quirks=3D0x2 Trying to mount root from ufs:/dev/da0s2 []... mountroot: waiting for device /dev/da0s2 ... WARNING: / was not properly dismounted WARNING: /: mount pending error: blocks 0 files 8 warning: no time-of-day clock registered, system time will not be set accurately lock order reversal: 1st 0xc22d1598 pmap (pmap) @ /usr/src/sys/arm/arm/pmap-v6.c:2990 2nd 0xc075e980 pmap pv global (pmap pv global) @ /usr/src/sys/arm/arm/pmap-v6.c :695 KDB: stack backtrace: _end() at 0xdbd05c30 scp=3D0xdbd05c30 rlv=3D0xc04f6064 (db_trace_self+0x14) rsp=3D0xdbd05b18 rfp=3D0xc2193380 Bad frame pointer: 0xc2193380 lock order reversal: 1st 0xc22d10b4 pmap (pmap) @ /usr/src/sys/arm/arm/pmap-v6.c:2990 2nd 0xc08530f0 vm map (system) (vm map (system)) @ /usr/src/sys/vm/vm_kern.c:42 = 8 KDB: stack backtrace: _end() at 0xde185aa4 scp=3D0xde185aa4 rlv=3D0xc04f6064 (db_trace_self+0x14) rsp=3D0xde185988 rfp=3D0xc21930a8 Bad frame pointer: 0xc21930a8 Setting hostuuid: a91f5d90-ebd4-11e2-83d9-63219f70abff. Setting hostid: 0x3599dde5. No suitable dump device was found. Entropy harvesting: interrupts ethernet point_to_pointsha256: /kernel: No such f ile or directory kickstart. Starting file system checks: =E2=80=8B From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 15 08:39:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4730D609; Mon, 15 Jul 2013 08:39:09 +0000 (UTC) (envelope-from hans.petter.selasky@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id CAA198D8; Mon, 15 Jul 2013 08:39:08 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id DD87B7A1E9; Mon, 15 Jul 2013 10:39:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id BB42B8EEA10; Mon, 15 Jul 2013 10:39:02 +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 aqRkxwMI3ACC; Mon, 15 Jul 2013 10:39:02 +0200 (CEST) Received: from mail.lockless.no (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 2B3D98EEA0E; Mon, 15 Jul 2013 10:39:02 +0200 (CEST) Subject: RE: My WLI-UC-GNM up crash From: =?utf-8?Q?Hans_Petter_Selasky?= To: =?utf-8?Q?XiaoQI_Ge?= , =?utf-8?Q?freebsd-wireless=40?= =?utf-8?Q?freebsd=2Eorg?= , =?utf-8?Q?freebsd-arm?= Date: Mon, 15 Jul 2013 10:39:02 +0200 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_CkXUz0pylDulQXFqJkqWrROmt5H+I2BbQMAIJDeGsqsB5Ly8" In-Reply-To: References: X-Priority: 3 (Normal) X-Mailer: Zarafa 7.1.4-41394 Message-Id: X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 08:39:09 -0000 This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_CkXUz0pylDulQXFqJkqWrROmt5H+I2BbQMAIJDeGsqsB5Ly8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, Can you try the attached patch? --HPS --=_CkXUz0pylDulQXFqJkqWrROmt5H+I2BbQMAIJDeGsqsB5Ly8 Content-Type: text/x-patch; name=radiotap_alignment.diff Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=radiotap_alignment.diff ZGlmZiAtLWdpdCBhL3N5cy9uZXQ4MDIxMS9pZWVlODAyMTFfcmFkaW90YXAuaCBiL3N5cy9u ZXQ4MDIxMS9pZWVlODAyMTFfcmFkaW90YXAuaAppbmRleCBiOGE4YjUxLi5jMTk5ZDQ4IDEw MDY0NAotLS0gYS9zeXMvbmV0ODAyMTEvaWVlZTgwMjExX3JhZGlvdGFwLmgKKysrIGIvc3lz L25ldDgwMjExL2llZWU4MDIxMV9yYWRpb3RhcC5oCkBAIC03OCw3ICs3OCw3IEBAIHN0cnVj dCBpZWVlODAyMTFfcmFkaW90YXBfaGVhZGVyIHsKIAkJCQkJICogQWRkaXRpb25hbCBleHRl bnNpb25zIGFyZSBtYWRlCiAJCQkJCSAqIGJ5IHNldHRpbmcgYml0IDMxLgogCQkJCQkgKi8K LX0gX19wYWNrZWQ7Cit9IF9fcGFja2VkIF9fYWxpZ25lZCg0KTsKIAogLyoKICAqIE5hbWUg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBEYXRhIHR5cGUgICAgICAgVW5pdHMK --=_CkXUz0pylDulQXFqJkqWrROmt5H+I2BbQMAIJDeGsqsB5Ly8-- From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 15 08:45:46 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 644DC748; Mon, 15 Jul 2013 08:45:46 +0000 (UTC) (envelope-from hans.petter.selasky@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 21862917; Mon, 15 Jul 2013 08:45:45 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id 11D407A1DB; Mon, 15 Jul 2013 10:45:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id EB79C8EEA14; Mon, 15 Jul 2013 10:45:46 +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 tRRQlIwkH04Y; Mon, 15 Jul 2013 10:45:46 +0200 (CEST) Received: from mail.lockless.no (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 42C458E1198; Mon, 15 Jul 2013 10:45:46 +0200 (CEST) Subject: RE: My WLI-UC-GNM up crash From: =?utf-8?Q?Hans_Petter_Selasky?= To: =?utf-8?Q?XiaoQI_Ge?= , =?utf-8?Q?freebsd-wireless=40?= =?utf-8?Q?freebsd=2Eorg?= , =?utf-8?Q?freebsd-arm?= Date: Mon, 15 Jul 2013 10:45:46 +0200 Mime-Version: 1.0 In-Reply-To: References: X-Priority: 3 (Normal) X-Mailer: Zarafa 7.1.4-41394 Message-Id: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 08:45:46 -0000 Can you tell us which compiler you used to build your image? --HPS From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 15 09:06:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D0026EE0 for ; Mon, 15 Jul 2013 09:06:13 +0000 (UTC) (envelope-from ghw@7axu.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 692039F2 for ; Mon, 15 Jul 2013 09:06:12 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id p60so9987146wes.13 for ; Mon, 15 Jul 2013 02:06:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=RIH7j9MOlFTM/CxbuzbEZWEN7zwBglp2FxrUGtce2f4=; b=EWVB84FuJ1b7XrV4JmljcyizYd8SLbKAF/UYeVOJ+kgkG9WsHZJWjSho98UqTajX5c rDGNG0r5GcUQc+43+zIUgo8ZKXLeP729qMA+tQzvm9nNytbbIfz0AZ6qblpvVptHIK6k NiyjQzNuLXeu2/1PBb3ZNWC3raIyKsM4CJaaXe9z51HonqokuSEszUPzL9dxqOXFEhvp J3eOx67WrbBMruHnQ71/Um1ejr8tMvcdEMP39CAEIRGZYLHqsdsJxK6FsOjDqL/RgQrZ qiWrHwX2+cgyabEUFfLN+BmSrQ4KKoDu6czXE7pnOG6+KghNw+3BRXvVR4X/NIX1d+QA UgAw== X-Received: by 10.180.185.148 with SMTP id fc20mr8342216wic.0.1373879165675; Mon, 15 Jul 2013 02:06:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.93.34 with HTTP; Mon, 15 Jul 2013 02:05:25 -0700 (PDT) X-Originating-IP: [54.249.112.206] In-Reply-To: References: From: XiaoQI Ge Date: Mon, 15 Jul 2013 17:05:25 +0800 Message-ID: Subject: Re: My WLI-UC-GNM up crash To: Hans Petter Selasky X-Gm-Message-State: ALoCoQk/mxp6y6Cx/6kl+eaktzyltjp38PA7+iQDI2ZVhMMZkrlA+hn5cYYa0BGYAbW4G4oLX6fJ Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-arm , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 09:06:14 -0000 Tomorrow I'll try Is the clang compiler content in make.conf WITH_LIBCPLUSPLUS=yes NO_WERROR= WERROR= Using what command to compile the make TARGET_ARCH=arm WITH_FDT=yes MALLOC_PRODUCTION=yes kernel-toolchain make TARGET_ARCH=arm TARGET_CPUTYPE=armv6 KERNCONF=CB1G WITH_FDT=yes MALLOC_PRODUCTION=yes buildkernel -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/15 Hans Petter Selasky > ** > > Can you tell us which compiler you used to build your image? > > --HPS > > From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 15 09:17:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F0B31388; Mon, 15 Jul 2013 09:17:02 +0000 (UTC) (envelope-from Daan@vitsch.nl) Received: from Prakkezator.VEHosting.nl (Prakkezator6.VEHosting.nl [IPv6:2001:1af8:2100:b020::142]) by mx1.freebsd.org (Postfix) with ESMTP id 781C9A77; Mon, 15 Jul 2013 09:17:02 +0000 (UTC) Received: from [192.168.72.13] (124-54.bbned.dsl.internl.net [92.254.54.124]) (authenticated bits=0) by Prakkezator.VEHosting.nl (8.14.2/8.14.2) with ESMTP id r6F9GufA024374; Mon, 15 Jul 2013 11:16:59 +0200 (CEST) (envelope-from Daan@vitsch.nl) From: Daan Vreeken Organization: Daan - Vitsch Electronics To: XiaoQI Ge Subject: Re: My WLI-UC-GNM up crash Date: Mon, 15 Jul 2013 11:16:56 +0200 User-Agent: KMail/1.9.10 References: <1373862086-4117502624.6281ab47ee@bliksem.vehosting.nl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201307151116.56954.Daan@vitsch.nl> x-ve-auth-version: mi-1.1.7 2011-02-21 - Copyright (c) 2008, 2011 - Daan Vreeken - VEHosting x-ve-auth: authenticated as 'pa4dan' on Prakkezator.VEHosting.nl Cc: freebsd-arm@freebsd.org, freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 09:17:03 -0000 Hi XiaoQI Ge, On Monday 15 July 2013 06:12:38 XiaoQI Ge wrote: > My WLI-UC-GNM ifconfig up when collapsed, > I do not know how to solve > > > root@FreeBSD:~ # ifconfig wlan create wlandev run0 > wlan0: Ethernet address: 10:6f:3f:2b:fd:6d > wlan0 > root@FreeBSD:~ # ifconfig > 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 > run0: flags=8802 metric 0 mtu 2290 > ether 10:6f:3f:2b:fd:6d > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > wlan0: flags=8802 metric 0 mtu 1500 > ether 10:6f:3f:2b:fd:6d > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 MHz 11b) > country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 > wme bintval 0 > root@FreeBSD:~ # dhclient wlan0 > wlan0: no link .............. giving up > root@FreeBSD:~ # pciconf -lv > pciconf: /dev/pci: No such file or directory > root@FreeBSD:~ # ifconfig wlan0 up scan > run0: firmware RT2870 ver. 0.236 loaded > root@FreeBSD:~ # Fatal kernel mode data abort: 'Alignment Fault 1' > trapframe: 0xde177d68 > FSR=00000801, FAR=c24b3faf, spsr=00000013 > r0 =c24b7000, r1 =c24b3faf, r2 =c24b720c, r3 =0000096c > r4 =80003eaf, r5 =c249c800, r6 =c24b7024, r7 =c0760898 > r8 =c24b7000, r9 =00000014, r10=c055851d, r11=de177e18 > r12=0000002e, ssp=de177db4, slr=00000000, pc =c04072d4 > > [ thread pid 0 tid 100038 ] > Stopped at ieee80211_radiotap_chan_change+0x94: strh r3, [r1] > db> bt > Tracing pid 0 tid 100038 td 0xc232a620 > _end() at 0xde177a90 > scp=0xde177a90 rlv=0xc04f5e48 (db_trace_thread+0x34) > rsp=0xde177a74 rfp=0xc05b8750 > Bad frame pointer: 0xc05b8750 > db> Please see the patches I posted here : http://www.freebsd.org/cgi/query-pr.cgi?pr=arm%2F179532&cat= I think they may solve your problem. Regards, -- Ing. Daan Vreeken Vitsch Electronics http://Vitsch.nl/ http://VitschVPN.nl/ tel: +31-(0)40-7113051 KvK nr: 17174380 -- Machines en netwerken op afstand beheren? Vitsch VPN oplossing! Kijk voor meer informatie op: http://www.VitschVPN.nl/ From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 15 11:06:53 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CDE87FC3 for ; Mon, 15 Jul 2013 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B36DFFD8 for ; Mon, 15 Jul 2013 11:06:53 +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 r6FB6rIG084651 for ; Mon, 15 Jul 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6FB6r7d084647 for freebsd-wireless@FreeBSD.org; Mon, 15 Jul 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Jul 2013 11:06:53 GMT Message-Id: <201307151106.r6FB6r7d084647@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 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/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 172 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 15 20:30:04 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9A7657E9; Mon, 15 Jul 2013 20:30:04 +0000 (UTC) (envelope-from l.yotov@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 31116945; Mon, 15 Jul 2013 20:30:04 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l10so6520264qcy.4 for ; Mon, 15 Jul 2013 13:30: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=ry19AyIDr+nXEB/rbW6df68TP9I+6mAuIcBWltp+EkM=; b=dwumhrL0sSCr2pXKc2MHYYQPvzr0KVsH3rH+KnbG0tanx7vyR0rXtXJn6etS81oyKE Z4kQ9W5ny/vNKmlMpIxQlVjwkxLnuqPrELxcnqdaP+QwW8tDoaTRBd5UQ0ROsXnz/hgW xyEAhQ1EOH3693lTPbpQFAl4/MjmuonX1NvOh1SzcBzXHQsoLHu5rSEYKo/JHyutzDKO 26oD/PcUqy81utZL/Y+k9oR3K/XeGkYW8Q5zbZn5siU+dK0zF4FbwW676dH9kxjVr292 YrTq/9cgvjvfqGwnJFocVvz6goc3ixePbATbQUt3TtdZX4wAw0A43CsfE2hnOMaOz1/T CbvQ== MIME-Version: 1.0 X-Received: by 10.224.13.202 with SMTP id d10mr56255629qaa.19.1373920203731; Mon, 15 Jul 2013 13:30:03 -0700 (PDT) Received: by 10.224.58.143 with HTTP; Mon, 15 Jul 2013 13:30:03 -0700 (PDT) In-Reply-To: <51C8AE67.7040801@unsane.co.uk> References: <51C8AE67.7040801@unsane.co.uk> Date: Mon, 15 Jul 2013 23:30:03 +0300 Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Lyubomir Yotov To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 20:30:04 -0000 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 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 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 wrote: > >>> Hello Adrian, > >>> > >>> Do you have any feedback on the matter? > >>> > >>> Regards, > >>> > >>> Lyubomir > >>> > >>> > >>> On 13 June 2013 10:09, Lyubomir Yotov 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 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 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 wrote: > >>>>>>> Can you please paste the vmstat -i output? > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> adrian > >>>>>>> > >>>>>>> On 9 June 2013 06:53, Lyubomir Yotov 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 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 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 Tue Jul 16 08:51:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 56AE5AB4; Tue, 16 Jul 2013 08:51:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by mx1.freebsd.org (Postfix) with ESMTP id 9266782D; Tue, 16 Jul 2013 08:51:24 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b12so349482wgh.19 for ; Tue, 16 Jul 2013 01:51:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nvU0OzUb4c99+KNDCmNLU2CObQVHBaRRlPPa6Qk0hy0=; b=X03fbpKv7GtNfNaeFi8k0MXcMsG1vsc5PvFZEEcYumzMwabvl0gLiV2CchoaMCeSTk 2K/8T9n2uatETo8xFwiaRJqYe7DLH8IGMFJRoYkvyLd+cGoCTwTVUqdRhJ9SnY483yhf i7C20nJQk8y4NzODMAVup+5B55czI79KV3To528ujU5uavXr/jhDUwwHGSc5ypjR27Cm SSRK52AiDBLmJx/ttFz9jZZA+fArSwvRK0vmcocJlRNxDRZACqydwrVSbeJCfiRQGBVg UbhqHH1sVvvdmgXGRMZeOPA1vjMt95llK+6RldkeCWvGnwfPff9jPq5sXq/F3bi+cVnp NcBw== MIME-Version: 1.0 X-Received: by 10.194.11.72 with SMTP id o8mr436273wjb.0.1373964683620; Tue, 16 Jul 2013 01:51:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Tue, 16 Jul 2013 01:51:23 -0700 (PDT) In-Reply-To: References: <51C8AE67.7040801@unsane.co.uk> Date: Tue, 16 Jul 2013 01:51:23 -0700 X-Google-Sender-Auth: TDV1w6qlHUyst-INzUfNqaRYiBw Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Adrian Chadd To: Lyubomir Yotov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 08:51:25 -0000 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 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 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 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 wrote: >> >>> Hello Adrian, >> >>> >> >>> Do you have any feedback on the matter? >> >>> >> >>> Regards, >> >>> >> >>> Lyubomir >> >>> >> >>> >> >>> On 13 June 2013 10:09, Lyubomir Yotov 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 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 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 wrote: >> >>>>>>> Can you please paste the vmstat -i output? >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> adrian >> >>>>>>> >> >>>>>>> On 9 June 2013 06:53, Lyubomir Yotov 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 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 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 Wed Jul 17 07:00:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 49262FA4 for ; Wed, 17 Jul 2013 07:00:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id C7DFC96D for ; Wed, 17 Jul 2013 07:00:39 +0000 (UTC) Received: by mail-we0-f172.google.com with SMTP id q56so1414326wes.17 for ; Wed, 17 Jul 2013 00:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=+4emJsHjA/jfi/Dp6/T8gANpwPf2DV5R+R75HSQlQew=; b=QWfIVH9dCWtRfIHC6OVtksvtXxovxdJSj7uhe4CW3GYG+9LwhueDfO5prrkbhonjpc DeJJvm0H6c8+AwfyjQxYrH4WRMtX0ZRn1tGJLV8XXzkHluKOogFCxBupaskbfpyEJHkh KBoJn8M+HO87FpDirifkHEwO6bry6/60uwRXTf76mR9F5O9YKOlum+iQH8zVzG5sr5NI W1iWYWJCIcoGsjlGEuEHp/TB2xRaDOmrVrGc8LwhNEdhR0D8QhZsdfka1cqtsiVU1DBS 6omuoN9EvSWcyq+qe3YtHomxK+gc8jujbBuLCo98+lzISkKp+qkVFfpa1+A/bXJopl4h EGlQ== MIME-Version: 1.0 X-Received: by 10.194.63.229 with SMTP id j5mr3645228wjs.79.1374044438837; Wed, 17 Jul 2013 00:00:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Wed, 17 Jul 2013 00:00:38 -0700 (PDT) In-Reply-To: References: <608F1F43-59F3-456D-A725-B36C2F9C2E75@gmail.com> Date: Wed, 17 Jul 2013 00:00:38 -0700 X-Google-Sender-Auth: TV7x8oFN4tmxtBZyqy3StmJaUH4 Message-ID: Subject: Re: great interest in the net80211 rate control API extension project in the wireless section of FreeBSD's GSoC 2013 idea list From: Adrian Chadd To: Chenchong Qin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 07:00:40 -0000 Hi, >From now on, would you mind cc'ing freebsd-wireless@freebsd.org on discussions about this? I'd prefer to have this discussion in public so everyone can benefit! On 16 July 2013 20:28, Chenchong Qin wrote: > Hi! > > I've read your change to ieee80211_[phy amrr] and commited some code to my > soc repo. Cool! > For pre-802.11n, if rts/cts flag is set on retry 0, retries 1, 2, 3 can't be > used. And if rts/cts flag is not set on retry 0, we take it as a > non-protected rate series, rts/cts of retries 1, 2, 3 is useless neither. Right. This is specific to the Atheros hardware that supports this kind of multi-rate retry. > So, for non-11n scenario, I clear rts/cts flag of retries 1, 2, 3 and if > retry 0 enable rts/cts, blank tries 1, 2, 3. Is this logic resonable? Right. Well, what I think it should be is some kind of hardware capability that the chip tells the rate control code when it initialises. Ie; * I support multi-rate retry; * I support RTS for all rate retries (defaulting to the non-11n behaviour of _EITHER_ multi-rate retry + no RTSCTS, _OR_ single rate try + RTS/CTS > As for the 11n stuff for rate control, it seems to happen after lookup of > rates. Functions in if_ath_tx_ht.c, ie. ath_tx_rate_fill_rcflags and > ath_buf_set_rate, are called after ath_tx_do_ratelookup. Are we going to > implement all the same thing in one ieee80211_ratectrl_ functioin, or > sepreate functions? Well, what do you think? You're the one tinkering with this. :) Note that I've done it in a few places; * I do the rate lookup from ath_rate; * I then copy that into an ath_rc_series array; * I then "fix" the rate series up with 11n options - based purely on the negotiated parameters; * I convert the ath_rc_series into the HAL series, turning these options into hardware specific flags. Now, this means: * if it's a HT40 AP and STA, I always transmit HT40 - even though I could in theory choose to transmit HT20; * if the AP/STA support STBC, I always transmit STBC for MCS 0-7, but I in theory could choose not to; * If the AP/STA support short-GI, I always transmit it, even if I may choose not to; * etc. I did that because it's simple. But it may be that we should leave that up to the rate control module. It may decide to try transmitting HT20 only frames even though both sides are HT40. What do you think? -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 17 17:42:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0B127F2A for ; Wed, 17 Jul 2013 17:42:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 9E16BFAA for ; Wed, 17 Jul 2013 17:42:26 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id p60so2095958wes.27 for ; Wed, 17 Jul 2013 10:42:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=plhAIPpRGkrRtI37zFAdykczZCbKRLoGSt/88dIXOXI=; b=t/SXiO+xaXX0UvHt37z/6Rc016dI9l6GmDvGt3SrWhDZq/Wz/Kbi1YnUMjnsv00WQL z+NbwY5GkRpSdb49m5jVeRy7miZA75NMzLJXDeX/5b/2t073/VEZs2uIag1aRlhhZcUl Nq9Z4lrOkIsDQtB00JgHj2W9Xhj8zx03GMZsmq2bQ3Of0atZ/zfx7aUwkPaj8vMO2jrk tFg2lSjjFWEklnyXfiWeA9Y5epFId4d2lsBcEOibj3tDc3FonCp6BP6HfJsWlyvPxF7Z T0bVrDsV0lYoMLl9Lh9PYGQ9r0s2owsk3TrrTZZj/o4MphCzrHzf3N2sqzWR5ljk8AAx FNOw== MIME-Version: 1.0 X-Received: by 10.180.185.148 with SMTP id fc20mr5588306wic.0.1374082945636; Wed, 17 Jul 2013 10:42:25 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Wed, 17 Jul 2013 10:42:25 -0700 (PDT) Date: Wed, 17 Jul 2013 10:42:25 -0700 X-Google-Sender-Auth: biTIflsUdYgQabLLz2EYa0Uli84 Message-ID: Subject: So, which IEEE<->Frequency mappings should we be all using? From: Adrian Chadd To: freebsd-wireless@freebsd.org, linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 17:42:27 -0000 Hi all, I've been increasingly asked to bring up FreeBSD on "other" bands. * 420MHz * 700MHz * 900MHz (which we already have, due to history); * 3.6GHz * 4.9GHz I'd also like to support half and quarter width channels on these frequencies. If I use the 2GHz channel mapping method, I end up with a very restricted channel set and it definitely has no "gaps" for 5/10MHz increments. Now, what I'd like to do is figure out some sane, shared method of translating channel frequencies to IEEE numbers and back. That way the BSDs and Linux (and maybe commercial stacks; I dunno what they do) can have some sane chance of interoperating. So: Is there some standardised or semi-standardised channel mapping method? Or should we invent one? -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 17 20:06:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8BDC289; Wed, 17 Jul 2013 20:06:52 +0000 (UTC) (envelope-from l.yotov@gmail.com) Received: from mail-qe0-x234.google.com (mail-qe0-x234.google.com [IPv6:2607:f8b0:400d:c02::234]) by mx1.freebsd.org (Postfix) with ESMTP id 7EC7C898; Wed, 17 Jul 2013 20:06:52 +0000 (UTC) Received: by mail-qe0-f52.google.com with SMTP id i11so1387236qej.11 for ; Wed, 17 Jul 2013 13:06: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=s4tXHb9ThARXcnZh5c4+oMDOCGgKbh9mwQZ7oWvX0NI=; b=GsPbz2+DjNOrp7/pAqALwg1wlfzmSIgJstc5GazkfDJUt0JkexzJJGYfU+dm9HUm8u hI20J2M8CUyxHAz/9fCMIhE06/tboEAuFjB3FMkFPBp5mVfrA4b9ZpQhNMVx3gwp3iaQ pBzoMWwZXJtRyK29sZpVlTRFtVr9j381uEKrty+yP+phebysaJlqZMuKg8dyzyIzUrXb CjmniVjwp2mdvo8vOvMYMdHA+DhgxbDefest4bY7M33b2Q6bxwan7IkKb1tC4iYnD0JQ KOaArn5Dt9wRChHaqgVUUcoApEXPLSgfVpt/uqFdEoaxpeCl74uewkBcP7M6bEg9KvkO XflQ== MIME-Version: 1.0 X-Received: by 10.224.67.202 with SMTP id s10mr10459934qai.66.1374091612040; Wed, 17 Jul 2013 13:06:52 -0700 (PDT) Received: by 10.224.58.143 with HTTP; Wed, 17 Jul 2013 13:06:51 -0700 (PDT) In-Reply-To: References: <51C8AE67.7040801@unsane.co.uk> Date: Wed, 17 Jul 2013 23:06:51 +0300 Message-ID: Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows From: Lyubomir Yotov To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 20:06:53 -0000 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 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 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 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 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 wrote: >>> >>> Hello Adrian, >>> >>> >>> >>> Do you have any feedback on the matter? >>> >>> >>> >>> Regards, >>> >>> >>> >>> Lyubomir >>> >>> >>> >>> >>> >>> On 13 June 2013 10:09, Lyubomir Yotov 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 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 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 wrote: >>> >>>>>>> Can you please paste the vmstat -i output? >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> adrian >>> >>>>>>> >>> >>>>>>> On 9 June 2013 06:53, Lyubomir Yotov 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 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 >>> 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 Thu Jul 18 01:00:04 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BEFC67B9; Thu, 18 Jul 2013 01:00:04 +0000 (UTC) (envelope-from prvs=904cb4ac1=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id 793608C0; Thu, 18 Jul 2013 01:00:03 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.89,689,1367985600"; d="scan'208";a="109844996" Received: from cipt0175.nam.ci.root ([10.132.108.175]) by cooperlighting-sw.cooperlighting.com with ESMTP; 17 Jul 2013 20:58:56 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0175.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Wed, 17 Jul 2013 20:58:56 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: So, which IEEE<->Frequency mappings should we be all using? Date: Thu, 18 Jul 2013 08:58:42 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC1316089BB77C@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: So, which IEEE<->Frequency mappings should we be all using? Thread-Index: Ac6DFQeT16cT2tecRkmiNvvXIr78wgANSogA References: From: "Wright, Brett" To: "Adrian Chadd" , , X-OriginalArrivalTime: 18 Jul 2013 00:58:56.0071 (UTC) FILETIME=[FAA01D70:01CE8351] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 01:00:04 -0000 > -----Original Message----- > From: owner-freebsd-wireless@freebsd.org [mailto:owner-freebsd- > wireless@freebsd.org] On Behalf Of Adrian Chadd > Sent: Thursday, 18 July 2013 3:42 AM > To: freebsd-wireless@freebsd.org; linux-wireless@vger.kernel.org > Subject: So, which IEEE<->Frequency mappings should we be all using? >=20 > Hi all, >=20 > I've been increasingly asked to bring up FreeBSD on "other" bands. >=20 > * 420MHz > * 700MHz > * 900MHz (which we already have, due to history); > * 3.6GHz > * 4.9GHz >=20 > I'd also like to support half and quarter width channels on these frequencies. > If I use the 2GHz channel mapping method, I end up with a very restricted > channel set and it definitely has no "gaps" for 5/10MHz increments. >=20 > Now, what I'd like to do is figure out some sane, shared method of > translating channel frequencies to IEEE numbers and back. That way the BSDs > and Linux (and maybe commercial stacks; I dunno what they do) can have > some sane chance of interoperating. >=20 > So: Is there some standardised or semi-standardised channel mapping > method? Or should we invent one? >=20 >=20 > -adrian Hi Adrian, I wanted to make similar changes to madwifi some years ago, and as there was no standard I invented one. This likely won't align with your requirements, but share some details below in case it may help. The approach I took was that the ieee channel numbers should overlap for the different frequency bands, as there are a huge number of different channels once you include all bands + 5, 10, 20, (and maybe 40) channel widths (not such a big deal since no manufacturers seem to offer a radio that supports more than one of the lower frequency bands on one board). This way the 20MHz channel numbers were unchanged for all bands (as they report as 2.4GHz band anyway), and the 5 and 10 MHz widths I mapped above channel 14 using mapgsm() and ath_hal_mhz2ieee(), plus other additions like unmapgsm, etc. To cut a long story short I ended up with channels 1-14 for 20MHz, 21-34 for 5MHz, and 41-54 for 10MHz. From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 10:42:59 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 205C9675 for ; Thu, 18 Jul 2013 10:42:59 +0000 (UTC) (envelope-from sirok@mail.ru) Received: from fallback2.mail.ru (fallback2.mail.ru [94.100.176.87]) by mx1.freebsd.org (Postfix) with ESMTP id 719B965B for ; Thu, 18 Jul 2013 10:42:58 +0000 (UTC) Received: from f394.i.mail.ru (f394.i.mail.ru [185.5.136.65]) by fallback2.mail.ru (mPOP.Fallback_MX) with ESMTP id 2DD54E49DDFB for ; Thu, 18 Jul 2013 14:39:17 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=60Slw+pWZJwYijLJtujtYCDhWFCCgLzMuSEuzG6by+Q=; b=kCDzD11SpaqL06l6oTeU1ljR5lxeatp/9nXTga2zT4T6E78c49WJcKrMCz1Wf1TjPdKSnbyV0QS6TqUROFhfAwsjHXS+Y7gO3ufYDa0l9e8cvhDVUnqGOvuhjUF0OEXCxckPXyVljszT+WPyVaiiuYO+NA/jFv/K/ygMVHVC6JE=; Received: from mail by f394.i.mail.ru with local (envelope-from ) id 1Uzlc5-0001ke-KH for freebsd-wireless@freebsd.org; Thu, 18 Jul 2013 14:39:09 +0400 Received: from [85.26.144.211] by e.mail.ru with HTTP; Thu, 18 Jul 2013 14:39:09 +0400 From: =?UTF-8?B?c2lyb2s=?= To: freebsd-wireless@freebsd.org Subject: =?UTF-8?B?QVI5Mjg3IGludGVycnVwdCByYXRl?= Mime-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [85.26.144.211] Date: Thu, 18 Jul 2013 14:39:09 +0400 X-Priority: 3 (Normal) Message-ID: <1374143949.434105019@f394.i.mail.ru> X-Mras: Ok Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?UTF-8?B?c2lyb2s=?= List-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, 18 Jul 2013 10:42:59 -0000 IEhpIQoKYXRoMDogPEF0aGVyb3MgOTI4Nz4gbWVtIDB4ZmU1MDAwMDAtMHhmZTUwZmZmZiBpcnEg MTYgYXQgZGV2aWNlIDAuMCBvbiBwY2kxCmF0aDA6IFtIVF0gZW5hYmxpbmcgSFQgbW9kZXMKYXRo MDogW0hUXSBlbmFibGluZyBzaG9ydC1HSSBpbiAyME1IeiBtb2RlCmF0aDA6IFtIVF0gMSBzdHJl YW0gU1RCQyByZWNlaXZlIGVuYWJsZWQKYXRoMDogW0hUXSAxIHN0cmVhbSBTVEJDIHRyYW5zbWl0 IGVuYWJsZWQKYXRoMDogW0hUXSAyIFJYIHN0cmVhbXM7IDIgVFggc3RyZWFtcwphdGgwOiBBUjky ODcgbWFjIDM4NC4yIFJGNTEzMyBwaHkgMTUuMTUKYXRoMDogMkdIeiByYWRpbzogMHgwMDAwOyA1 R0h6IHJhZGlvOiAweDAwYzAKCmF0aDA6IGZsYWdzPTg4NDM8VVAsQlJPQURDQVNULFJVTk5JTkcs U0lNUExFWCxNVUxUSUNBU1Q+IG1ldHJpYyAwIG10dSAyMjkwCsKgwqDCoMKgwqDCoMKgIGV0aGVy IDIwOjdjOjhmOnh4Onh4Onh4CsKgwqDCoMKgwqDCoMKgIG5kNiBvcHRpb25zPTI5PFBFUkZPUk1O VUQsSUZESVNBQkxFRCxBVVRPX0xJTktMT0NBTD4KwqDCoMKgwqDCoMKgwqAgbWVkaWE6IElFRUUg ODAyLjExIFdpcmVsZXNzIEV0aGVybmV0IGF1dG9zZWxlY3QgbW9kZSAxMW5nIDxob3N0YXA+CsKg wqDCoMKgwqDCoMKgIHN0YXR1czogcnVubmluZwoKd2xhbjA6IGZsYWdzPTg4NDM8VVAsQlJPQURD QVNULFJVTk5JTkcsU0lNUExFWCxNVUxUSUNBU1Q+IG1ldHJpYyAwIG10dSAxNTAwCsKgwqDCoMKg wqDCoMKgIGV0aGVyIDIwOjdjOjhmOnh4Onh4Onh4CsKgwqDCoMKgwqDCoMKgIGluZXQgMTkyLjE2 OC54LjEgbmV0bWFzayAweGZmZmZmZjAwIGJyb2FkY2FzdCAxOTIuMTY4LnguMjU1CsKgwqDCoMKg wqDCoMKgIGluZXQ2IGZlODA6Onh4eHh4JXdsYW4wIHByZWZpeGxlbiA2NCBzY29wZWlkIDB4MTMK wqDCoMKgwqDCoMKgwqAgaW5ldDYgeHh4eHg6OjEgcHJlZml4bGVuIDY0CsKgwqDCoMKgwqDCoMKg IG5kNiBvcHRpb25zPTIxPFBFUkZPUk1OVUQsQVVUT19MSU5LTE9DQUw+CsKgwqDCoMKgwqDCoMKg IG1lZGlhOiBJRUVFIDgwMi4xMSBXaXJlbGVzcyBFdGhlcm5ldCBhdXRvc2VsZWN0IG1vZGUgMTFu ZyA8aG9zdGFwPgrCoMKgwqDCoMKgwqDCoCBzdGF0dXM6IHJ1bm5pbmcKwqDCoMKgwqDCoMKgwqAg c3NpZCBYWFhYWCBjaGFubmVsIDYgKDI0MzcgTUh6IDExZyBodC80MCspIGJzc2lkIDIwOjdjOjhm Onh4Onh4Onh4CsKgwqDCoMKgwqDCoMKgIHJlZ2RvbWFpbiBOT05FIGNvdW50cnkgUlUgaW5kb29y IGVjbSBhdXRobW9kZSBXUEEyLzgwMi4xMWkKwqDCoMKgwqDCoMKgwqAgcHJpdmFjeSBNSVhFRCBk ZWZ0eGtleSAyIEFFUy1DQ00gMjoxMjgtYml0IEFFUy1DQ00gMzoxMjgtYml0CsKgwqDCoMKgwqDC oMKgIHR4cG93ZXIgMjAgc2NhbnZhbGlkIDYwIHByb3Rtb2RlIENUUyBhbXBkdWxpbWl0IDY0ayBh bXBkdWRlbnNpdHkgOArCoMKgwqDCoMKgwqDCoCBzaG9ydGdpIHdtZSBidXJzdCBkdGltcGVyaW9k IDEgLWRmcwoKUHJvYmxlbSBkZXNjcmlwdGlvbgoKSnVzdCBhZnRlciByZWJvb3Qgdm1zdGF0IC1p IHNob3dzIGFib3V0IDYwIGludGVycnVwdHMvc2VjCmlycTE2OiBhdGgwwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA0MDU1OMKgwqDCoMKgwqDCoMKgwqAgNjYK CkJ1dCBhZnRlciBzb21lIHRpbWUgKGEgZmV3IGhvdXJzIEkgdGhpbmspIGlycSByYXRlIHN0YXJ0 cyB0byByaXNlIHNsb3dseS4KQWZ0ZXIgfiAyMyBob3VyczoKaXJxMTY6IGF0aDDCoMKgwqDCoMKg wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDEyMDg2NjAwMDY5wqDCoMKgwqAgMTQ2ODQ1CkFmdGVy IDIzaCs1IG1pbnV0ZXM6CmlycTE2OiBhdGgwwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoCAxMjE1NDE5ODExNMKgwqDCoMKgIDE0NzEzMQpBYm91dCAxMCBtaW51dGVzIGxhdGVyOgpp cnExNjogYXRoMMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgMTIzMDc4NTQ1NjnC oMKgwqDCoCAxNDc3NzEKTm93OgppcnExNjogYXRoMMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg wqDCoMKgwqAgMTQwODkxNDE5NTHCoMKgwqDCoCAxNTQ0OTIKCkFuZCBzbyBvbiB1cCB0byBhYm91 dCAyODAwMDAvc2VjLiBBUCBtb2RlIHN0b3BzIGZ1bmN0aW9uaW5nIGF0IHNvbWUgcG9pbnQuCkl0 J3MgYSBwcmV0dHkgb2xkIHByb2JsZW0uIEhvd2V2ZXIgb24gb2xkZXIgcmV2cyBpcnEgZ29lcyBo aWdoIGltbWVkaWF0ZWx5IGFmdGVyIGJvb3QsIGV2ZW4gaWYgYXRoIGlzIG5vdCBjb25maWd1cmVk IGF0IGFsbC4KCkhFQUQgcmV2IDI1MzQxMgoKVGhhbmsgeW91IQoKLS0= From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 15:57:50 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3FC7967C for ; Thu, 18 Jul 2013 15:57:50 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [88.198.45.5]) by mx1.freebsd.org (Postfix) with ESMTP id B7B417FE for ; Thu, 18 Jul 2013 15:57:49 +0000 (UTC) Received: from pintail.NGC004 (78-1-125-145.adsl.net.t-com.hr [78.1.125.145]) by crane.smokva.net (Postfix) with ESMTPSA id 9B7F2106970F for ; Thu, 18 Jul 2013 17:52:02 +0200 (CEST) Date: Thu, 18 Jul 2013 17:52:00 +0200 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: high latency due to distant clients Message-ID: <20130718155200.GA381@pintail.NGC004> Mail-Followup-To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21+67 (d414971f0c48) (2011-07-01) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 15:57:50 -0000 Hi, for several years now, I've been running an ALIX-AP with a CM9 Atheros 5212 card. The AP covers a whole house which has about 6 flats and the average amount of active clients ranges from 10 to 15. Recently I noticed high latency when pinging the AP itself which happens when distant clients (who knows where around the house---could be inside or outside) seem to cause "longs" (long on-chip tx retries) and/or "xretries" (tx failed 'cuz too many retries). The Rate, when talking to these distant clients, is usually below 11M (sometimes as low as 1M) which is consistent with their low RSSI values the AP is reporting. With high latency I mean continuous bursts of 500-1000ms instead of 0.5ms so I wonder if this is normal. The software is slightly out of date and athstats is not completely in sync with the kernel i'm using (therefore its not reporting some values): # uname -a FreeBSD parrot.NGC004 8.1-RC2 FreeBSD 8.1-RC2 #2: Thu Aug 16 21:13:54 CEST 2012 # athstats -i ath0 athstats: ath0: Invalid argument athstats: ath0: Invalid argument 3181606 data frames transmit 45659 tx frames with an alternate rate 568149 long on-chip tx retries 19091 tx failed 'cuz too many retries 0M current transmit rate 25 tx stopped 'cuz no xmit buffer 20922 tx frames with no ack marked 3039151 tx frames with short preamble 362335 rx failed 'cuz of bad CRC 1181 rx failed 'cuz of PHY err 315 OFDM restart 866 CCK restart 2 TDMA slot timing updates -0/+0 TDMA slot adjust (usecs, smoothed) 26135 TDMA tx failed 'cuz ACK required -74 rx noise floor 3070927 tx frames through raw api 6299685 fast frames received 1328215 fast frames flushed from staging q 20835 ANI decrease noise immunity 6593 ANI increased spur immunity 121582 ANI decrease spur immunity 160 ANI decreased first step level 2 cumulative OFDM phy error count 2 RTS without CTS 1360093 beacons received Antenna profile: Any ideas on how to avoid that? Of course I could buy better antennas but it seems that, generally speaking, this shouldn't happen. Thanks, Petar Bogdanovic From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 15:59:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A5E276C6 for ; Thu, 18 Jul 2013 15:59:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 43F51810 for ; Thu, 18 Jul 2013 15:59:30 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id c10so6836199wiw.5 for ; Thu, 18 Jul 2013 08:59: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 :x-google-sender-auth:message-id:subject:from:to:content-type; bh=SAWavVkG+IpwN1GThQSHmwW1lwMapvyfobDPRlWeP7U=; b=XQbPxulFLA6TCxQPeOu592BCys5aUZwMDCSxKrnvGetS+aFWXKRIgoiJO6nkUxjAkv QQik2PdUmjBkEojRG+sqqgY/YiB2bmRdCEn7He4oNEsSQQKCPEjCTjpA4HiqWdepAesE ZKWPbHFDEADE9Xnm0QBCYtRu5/9T2AJwQGISWvj+NfuRk1QSiqUTKXdvypcXmpmsRXoV 1cwS4gZ9r60rqZnLOzucy4V2bjLb/sOnZJFuXZsdE8ojx5rzyQkeKvzinaUOd880hSG8 jA8U/hBqw6SUkS9t041Z4wKlKKeSCenVCYn9XalEkYvCKvlQ8gsCxQCwyz+pwKaRVCLe +HGw== MIME-Version: 1.0 X-Received: by 10.194.63.229 with SMTP id j5mr8865513wjs.79.1374163169453; Thu, 18 Jul 2013 08:59:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 18 Jul 2013 08:59:29 -0700 (PDT) In-Reply-To: <20130718155200.GA381@pintail.NGC004> References: <20130718155200.GA381@pintail.NGC004> Date: Thu, 18 Jul 2013 08:59:29 -0700 X-Google-Sender-Auth: RQHLGv8LNCwxTbtXkNM9K2t6Je8 Message-ID: Subject: Re: high latency due to distant clients From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 15:59:30 -0000 Hi, I think I fixed this in -HEAD. -adrian On 18 July 2013 08:52, Petar Bogdanovic wrote: > Hi, > > for several years now, I've been running an ALIX-AP with a CM9 Atheros > 5212 card. The AP covers a whole house which has about 6 flats and the > average amount of active clients ranges from 10 to 15. > > Recently I noticed high latency when pinging the AP itself which happens > when distant clients (who knows where around the house---could be inside > or outside) seem to cause "longs" (long on-chip tx retries) and/or > "xretries" (tx failed 'cuz too many retries). > > The Rate, when talking to these distant clients, is usually below 11M > (sometimes as low as 1M) which is consistent with their low RSSI values > the AP is reporting. > > With high latency I mean continuous bursts of 500-1000ms instead of > 0.5ms so I wonder if this is normal. > > The software is slightly out of date and athstats is not completely in > sync with the kernel i'm using (therefore its not reporting some values): > > # uname -a > FreeBSD parrot.NGC004 8.1-RC2 FreeBSD 8.1-RC2 #2: Thu Aug 16 21:13:54 CEST 2012 > > # athstats -i ath0 > athstats: ath0: Invalid argument > athstats: ath0: Invalid argument > 3181606 data frames transmit > 45659 tx frames with an alternate rate > 568149 long on-chip tx retries > 19091 tx failed 'cuz too many retries > 0M current transmit rate > 25 tx stopped 'cuz no xmit buffer > 20922 tx frames with no ack marked > 3039151 tx frames with short preamble > 362335 rx failed 'cuz of bad CRC > 1181 rx failed 'cuz of PHY err > 315 OFDM restart > 866 CCK restart > 2 TDMA slot timing updates > -0/+0 TDMA slot adjust (usecs, smoothed) > 26135 TDMA tx failed 'cuz ACK required > -74 rx noise floor > 3070927 tx frames through raw api > 6299685 fast frames received > 1328215 fast frames flushed from staging q > 20835 ANI decrease noise immunity > 6593 ANI increased spur immunity > 121582 ANI decrease spur immunity > 160 ANI decreased first step level > 2 cumulative OFDM phy error count > 2 RTS without CTS > 1360093 beacons received > Antenna profile: > > Any ideas on how to avoid that? Of course I could buy better antennas > but it seems that, generally speaking, this shouldn't happen. > > Thanks, > > Petar Bogdanovic > _______________________________________________ > 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 Jul 18 16:04:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EB009944 for ; Thu, 18 Jul 2013 16:04:40 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [88.198.45.5]) by mx1.freebsd.org (Postfix) with ESMTP id B1CE7853 for ; Thu, 18 Jul 2013 16:04:40 +0000 (UTC) Received: from pintail.NGC004 (78-1-125-145.adsl.net.t-com.hr [78.1.125.145]) by crane.smokva.net (Postfix) with ESMTPSA id 4B0B1106970F for ; Thu, 18 Jul 2013 18:04:39 +0200 (CEST) Date: Thu, 18 Jul 2013 18:04:37 +0200 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: Re: high latency due to distant clients Message-ID: <20130718160436.GB381@pintail.NGC004> Mail-Followup-To: freebsd-wireless@freebsd.org References: <20130718155200.GA381@pintail.NGC004> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+67 (d414971f0c48) (2011-07-01) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 16:04:41 -0000 On Thu, Jul 18, 2013 at 08:59:29AM -0700, Adrian Chadd wrote: > > I think I fixed this in -HEAD. Uh-oh, great! Will that change reach a stable release anytime soon? And--out of naive curiosity--what was the problem? Thanks, Petar Bogdanovic From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 16:21:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2E16EF95 for ; Thu, 18 Jul 2013 16:21:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) by mx1.freebsd.org (Postfix) with ESMTP id BF0B9951 for ; Thu, 18 Jul 2013 16:21:56 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id y10so3068038wgg.8 for ; Thu, 18 Jul 2013 09:21: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Y3cq3MOfcRriFqc4MpBXMn1y/zI8WGW1gzOJ/ISU3eY=; b=pLrphgaYdAhKIDDNGHvBEneQmxCYcY+S4GsOYnp9G/7Sb9r6AEcg4yYTGUPsiykQmb rls4qWNXtE444m+FIrxYKQ+eiQr13RHdaB2/414VTGJlVKrquK4Oq5K9bRg/xWBGBOrl OsfGRauH4B7r3P80Ay2XRyIABfqZjQtAryQuovwYJoMRwCBIHX0Fk8fs6iFmHrQbAmoC MwA6sqMqxm0MEI8F5PUEqw7BLymJco3yKLyYwDWhpyfBSID7rBTz7A1zKzlt+7VBwPBi qB/NUy8bqWQYR9lXi7YhHyXNUZV6bZhelgtAJKSrnXnTEbFONUjkiwHkkS6XOqeIQuFo TQ6g== MIME-Version: 1.0 X-Received: by 10.194.240.201 with SMTP id wc9mr9236680wjc.1.1374164515733; Thu, 18 Jul 2013 09:21:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 18 Jul 2013 09:21:55 -0700 (PDT) In-Reply-To: <1374143949.434105019@f394.i.mail.ru> References: <1374143949.434105019@f394.i.mail.ru> Date: Thu, 18 Jul 2013 09:21:55 -0700 X-Google-Sender-Auth: SPpIbqfgGsRvbE6WswoI8jhHgYk Message-ID: Subject: Re: AR9287 interrupt rate From: Adrian Chadd To: sirok Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 16:21:57 -0000 Hm, I wonder what interrupt it is. Add 'options AH_INTERRUPT_DEBUGGING' and rebuild. Then after it happens, post the output of 'sysctl dev.ath.0' -adrian On 18 July 2013 03:39, sirok wrote: > Hi! > > ath0: mem 0xfe500000-0xfe50ffff irq 16 at device 0.0 on pci1 > ath0: [HT] enabling HT modes > ath0: [HT] enabling short-GI in 20MHz mode > ath0: [HT] 1 stream STBC receive enabled > ath0: [HT] 1 stream STBC transmit enabled > ath0: [HT] 2 RX streams; 2 TX streams > ath0: AR9287 mac 384.2 RF5133 phy 15.15 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > ath0: flags=8843 metric 0 mtu 2290 > ether 20:7c:8f:xx:xx:xx > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running > > wlan0: flags=8843 metric 0 mtu 1500 > ether 20:7c:8f:xx:xx:xx > inet 192.168.x.1 netmask 0xffffff00 broadcast 192.168.x.255 > inet6 fe80::xxxxx%wlan0 prefixlen 64 scopeid 0x13 > inet6 xxxxx::1 prefixlen 64 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running > ssid XXXXX channel 6 (2437 MHz 11g ht/40+) bssid 20:7c:8f:xx:xx:xx > regdomain NONE country RU indoor ecm authmode WPA2/802.11i > privacy MIXED deftxkey 2 AES-CCM 2:128-bit AES-CCM 3:128-bit > txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 > shortgi wme burst dtimperiod 1 -dfs > > Problem description > > Just after reboot vmstat -i shows about 60 interrupts/sec > irq16: ath0 40558 66 > > But after some time (a few hours I think) irq rate starts to rise slowly. > After ~ 23 hours: > irq16: ath0 12086600069 146845 > After 23h+5 minutes: > irq16: ath0 12154198114 147131 > About 10 minutes later: > irq16: ath0 12307854569 147771 > Now: > irq16: ath0 14089141951 154492 > > And so on up to about 280000/sec. AP mode stops functioning at some point. > It's a pretty old problem. However on older revs irq goes high immediately after boot, even if ath is not configured at all. > > HEAD rev 253412 > > Thank you! > > -- > _______________________________________________ > 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 Jul 18 16:25:21 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86C54CD for ; Thu, 18 Jul 2013 16:25:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 23A73995 for ; Thu, 18 Jul 2013 16:25:20 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id w57so3139452wes.29 for ; Thu, 18 Jul 2013 09:25: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 :x-google-sender-auth:message-id:subject:from:to:content-type; bh=F7N+IkLJqr/gJUU0kvPZKkzuIis3HwSWGO6CiAz5UfU=; b=LgT5cynXtb4d3GPDSl4WgYCrTBCsQqPIsgrYo/NbXsGbU+NJdS6HhPVG3ZOMv0mBrW +emheGY0ftkTfXZbGKSZ/pyEOZdAqHJysBBVxMPrPHhF44H1z3WQYaT0KstjBejpdXTL Arq9pBwChD/ROUF+PyJOlxm8mBaSxLTK8XHsIh754/tHv3YHekE/K7Mv9O6lp64pkB7Z 4PU3wTYz88yEhrKwMTMKsNdfjeOLpBXqNx+2+0L12szbkiViru3XlU+ENFiKyiRmKVvu Xp5QhYjKf9pvPgamj9YbhFdeE6DSXTjDYaeyfUdNXtD/uaCV8vCeE7044Y3oKvrWTRxc YZ8Q== MIME-Version: 1.0 X-Received: by 10.180.160.165 with SMTP id xl5mr19816951wib.46.1374164719417; Thu, 18 Jul 2013 09:25:19 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 18 Jul 2013 09:25:19 -0700 (PDT) In-Reply-To: <20130718160436.GB381@pintail.NGC004> References: <20130718155200.GA381@pintail.NGC004> <20130718160436.GB381@pintail.NGC004> Date: Thu, 18 Jul 2013 09:25:19 -0700 X-Google-Sender-Auth: U_RbhaTLaPOpcQx9JqGexv_SeqA Message-ID: Subject: Re: high latency due to distant clients From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 16:25:21 -0000 On 18 July 2013 09:04, Petar Bogdanovic wrote: > On Thu, Jul 18, 2013 at 08:59:29AM -0700, Adrian Chadd wrote: >> >> I think I fixed this in -HEAD. > > Uh-oh, great! Will that change reach a stable release anytime soon? When 10.0 is stable, yup. :) > And--out of naive curiosity--what was the problem? The ath driver before 11n support went in would just fill the hardware TX queue with frames. There's no per-station queue or any kind of fair queuing. So if you fill the TX queue in the driver with frames to a far away station, it'll block all frames to other stations whilst they're transmitted and retransmitted. When I introduced 11n support, I added per-station and per-traffic-class queues in the driver as part of A-MPDU support. I software queue almost everything first and then schedule frames to the hardware from these software queued frames. This has the side effect of making it fairer between multiple stations, especially if one of them is far away. It will only schedule a small number of frames to each station before going to another station, rather than possibly being backed up with 128 frames just to a single destination. Now, it's likely there's more work that can be done to improve that behaviour with slow, far away clients. The framework is there in -HEAD. I've just not sat down and made it work. So if you update to -HEAD and you still have problems, we can tweak things and experiment. From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 17:19:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EF68998 for ; Thu, 18 Jul 2013 17:19:57 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [88.198.45.5]) by mx1.freebsd.org (Postfix) with ESMTP id 6ED59C38 for ; Thu, 18 Jul 2013 17:19:56 +0000 (UTC) Received: from pintail.NGC004 (78-1-125-145.adsl.net.t-com.hr [78.1.125.145]) by crane.smokva.net (Postfix) with ESMTPSA id 0EEC9106970F for ; Thu, 18 Jul 2013 19:19:51 +0200 (CEST) Date: Thu, 18 Jul 2013 19:19:45 +0200 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: Re: high latency due to distant clients Message-ID: <20130718171945.GA6817@pintail.NGC004> Mail-Followup-To: freebsd-wireless@freebsd.org References: <20130718155200.GA381@pintail.NGC004> <20130718160436.GB381@pintail.NGC004> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+67 (d414971f0c48) (2011-07-01) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 17:19:58 -0000 On Thu, Jul 18, 2013 at 09:25:19AM -0700, Adrian Chadd wrote: > On 18 July 2013 09:04, Petar Bogdanovic wrote: > > On Thu, Jul 18, 2013 at 08:59:29AM -0700, Adrian Chadd wrote: > >> > >> I think I fixed this in -HEAD. > > > > Uh-oh, great! Will that change reach a stable release anytime soon? > > When 10.0 is stable, yup. :) > > > And--out of naive curiosity--what was the problem? > > The ath driver before 11n support went in would just fill the hardware > TX queue with frames. There's no per-station queue or any kind of fair > queuing. So if you fill the TX queue in the driver with frames to a > far away station, it'll block all frames to other stations whilst > they're transmitted and retransmitted. > > When I introduced 11n support, I added per-station and > per-traffic-class queues in the driver as part of A-MPDU support. I > software queue almost everything first and then schedule frames to the > hardware from these software queued frames. This has the side effect > of making it fairer between multiple stations, especially if one of > them is far away. It will only schedule a small number of frames to > each station before going to another station, rather than possibly > being backed up with 128 frames just to a single destination. > > Now, it's likely there's more work that can be done to improve that > behaviour with slow, far away clients. The framework is there in > -HEAD. I've just not sat down and made it work. So if you update to > -HEAD and you still have problems, we can tweak things and experiment. Thanks for the nice and comprehensive explanation! I'll prepare the upgrade during the next couple of weeks and report back. It will probably be 9.1 userland and HEAD kernel (that approach worked well in the past). Petar Bogdanovic From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 17:22:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 03A04282 for ; Thu, 18 Jul 2013 17:22:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 943E0C5A for ; Thu, 18 Jul 2013 17:22:51 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id c11so3119392wgh.25 for ; Thu, 18 Jul 2013 10:22: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 :x-google-sender-auth:message-id:subject:from:to:content-type; bh=2aYhx7IgqIPPn7V5DG6dlpnJHKgXICcOi4vbaWBVBa4=; b=Utf7ch+C/5PclzwWaOSpCbSXCC7+++/JORzKQ2L1vU64FBtDG6aAglaGk1KjB/Qrd7 xeRcW5j7c8A24tnr4tv2ET7E9dH9J358+tyRuQmsDTmecK+DNRRVr59yB79LcZyatvoB 4jihtxCTDSRtgNUeRVYhHBDnfi2AWAY0JDtx/e7bzrkbByafEH4UqSMbM779ux3y69fa xueAlMIHrdfmEQYSvaPUGIw0xRrDqAy135sQuXBzFcuM1hxa5JF5N7Gd0GXTqmg77jCJ iGaPV5z7khawAtFjK1xDauX5QG8j/4KoCO6wRMj7vUQOEJrSVxtg2OORhbc5RJmVHU96 CCMQ== MIME-Version: 1.0 X-Received: by 10.180.185.148 with SMTP id fc20mr9019170wic.0.1374168170722; Thu, 18 Jul 2013 10:22:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 18 Jul 2013 10:22:50 -0700 (PDT) In-Reply-To: <20130718171945.GA6817@pintail.NGC004> References: <20130718155200.GA381@pintail.NGC004> <20130718160436.GB381@pintail.NGC004> <20130718171945.GA6817@pintail.NGC004> Date: Thu, 18 Jul 2013 10:22:50 -0700 X-Google-Sender-Auth: 2KB5d_ffJu1hS9n5Nw_RwIV7ors Message-ID: Subject: Re: high latency due to distant clients From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 17:22:52 -0000 I really do suggest -HEAD everything. -adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 22:36:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 093CFEDA for ; Thu, 18 Jul 2013 22:36:06 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id C7F53D19 for ; Thu, 18 Jul 2013 22:36:05 +0000 (UTC) Received: from [10.10.1.32] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id r6IMV02k040562 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 18 Jul 2013 18:31:00 -0400 (EDT) (envelope-from lists@jnielsen.net) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: high latency due to distant clients From: John Nielsen In-Reply-To: <20130718171945.GA6817@pintail.NGC004> Date: Thu, 18 Jul 2013 16:31:10 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9A1C017F-E982-4317-B92F-4B2D494A3081@jnielsen.net> References: <20130718155200.GA381@pintail.NGC004> <20130718160436.GB381@pintail.NGC004> <20130718171945.GA6817@pintail.NGC004> To: Petar Bogdanovic X-Mailer: Apple Mail (2.1508) X-DCC-Etherboy-Metrics: ns1.jnielsen.net 1002; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 22:36:06 -0000 On Jul 18, 2013, at 11:22 AM, Adrian Chadd wrote: > On Jul 18, 2013, at 11:19 AM, Petar Bogdanovic = wrote: >=20 >> On Thu, Jul 18, 2013 at 09:25:19AM -0700, Adrian Chadd wrote: >>> On 18 July 2013 09:04, Petar Bogdanovic wrote: >>>> On Thu, Jul 18, 2013 at 08:59:29AM -0700, Adrian Chadd wrote: >>>>>=20 >>>>> I think I fixed this in -HEAD. >>>>=20 >>>> Uh-oh, great! Will that change reach a stable release anytime = soon? >>>=20 >>> When 10.0 is stable, yup. :) >>>=20 >>>> And--out of naive curiosity--what was the problem? >>>=20 >>> The ath driver before 11n support went in would just fill the = hardware >>> TX queue with frames. There's no per-station queue or any kind of = fair >>> queuing. So if you fill the TX queue in the driver with frames to a >>> far away station, it'll block all frames to other stations whilst >>> they're transmitted and retransmitted. >>>=20 >>> When I introduced 11n support, I added per-station and >>> per-traffic-class queues in the driver as part of A-MPDU support. I >>> software queue almost everything first and then schedule frames to = the >>> hardware from these software queued frames. This has the side effect >>> of making it fairer between multiple stations, especially if one of >>> them is far away. It will only schedule a small number of frames to >>> each station before going to another station, rather than possibly >>> being backed up with 128 frames just to a single destination. >>>=20 >>> Now, it's likely there's more work that can be done to improve that >>> behaviour with slow, far away clients. The framework is there in >>> -HEAD. I've just not sat down and made it work. So if you update to >>> -HEAD and you still have problems, we can tweak things and = experiment. >>=20 >> Thanks for the nice and comprehensive explanation! >>=20 >> I'll prepare the upgrade during the next couple of weeks and report >> back. It will probably be 9.1 userland and HEAD kernel (that = approach >> worked well in the past). >=20 > I really do suggest -HEAD everything. If it makes you feel any better, I've been running -HEAD (with = semi-regular updates) on my ALIX AP for a while without any trouble. Of = course, I do the builds on another box... I'm happy to share make = settings, etc if that would be useful. JN From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 22:48:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6109D220 for ; Thu, 18 Jul 2013 22:48:52 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [88.198.45.5]) by mx1.freebsd.org (Postfix) with ESMTP id 25556DA3 for ; Thu, 18 Jul 2013 22:48:51 +0000 (UTC) Received: from pintail.NGC004 (78-1-125-145.adsl.net.t-com.hr [78.1.125.145]) by crane.smokva.net (Postfix) with ESMTPSA id 57D48106970F for ; Fri, 19 Jul 2013 00:48:50 +0200 (CEST) Date: Fri, 19 Jul 2013 00:48:48 +0200 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: Re: high latency due to distant clients Message-ID: <20130718224848.GA1978@pintail.NGC004> Mail-Followup-To: freebsd-wireless@freebsd.org References: <20130718155200.GA381@pintail.NGC004> <20130718160436.GB381@pintail.NGC004> <20130718171945.GA6817@pintail.NGC004> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+67 (d414971f0c48) (2011-07-01) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 22:48:52 -0000 On Thu, Jul 18, 2013 at 10:22:50AM -0700, Adrian Chadd wrote: > I really do suggest -HEAD everything. Ok, will do. From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 18 22:55:35 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 41F4D45E for ; Thu, 18 Jul 2013 22:55:35 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [88.198.45.5]) by mx1.freebsd.org (Postfix) with ESMTP id 961E8DEB for ; Thu, 18 Jul 2013 22:55:34 +0000 (UTC) Received: from pintail.NGC004 (78-1-125-145.adsl.net.t-com.hr [78.1.125.145]) by crane.smokva.net (Postfix) with ESMTPSA id 5548C106970F for ; Fri, 19 Jul 2013 00:55:32 +0200 (CEST) Date: Fri, 19 Jul 2013 00:55:30 +0200 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: Re: high latency due to distant clients Message-ID: <20130718225530.GA1326@pintail.NGC004> Mail-Followup-To: freebsd-wireless@freebsd.org References: <20130718155200.GA381@pintail.NGC004> <20130718160436.GB381@pintail.NGC004> <20130718171945.GA6817@pintail.NGC004> <9A1C017F-E982-4317-B92F-4B2D494A3081@jnielsen.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <9A1C017F-E982-4317-B92F-4B2D494A3081@jnielsen.net> User-Agent: Mutt/1.5.21+67 (d414971f0c48) (2011-07-01) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 22:55:35 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jul 18, 2013 at 04:31:10PM -0600, John Nielsen wrote: > > If it makes you feel any better, I've been running -HEAD (with > semi-regular updates) on my ALIX AP for a while without any trouble. > Of course, I do the builds on another box... I'm happy to share make > settings, etc if that would be useful. Your kernel configuration would be interesting. Mine is attached. I think it's a modified version from http://m0n0.ch/wall/. Petar Bogdanovic --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=ALIX machine i386 cpu I586_CPU ident ALIX makeoptions MODULES_OVERRIDE="" options HZ=1000 options CONSPEED=38400 options CPU_GEODE hints "ALIX.hints" options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options TMPFS # Efficient memory file system options MD_ROOT # MD is a potential root device options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options NO_SWAPPING options DEVICE_POLLING device apic # I/O APIC # Bus support. device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device uart # Generic UART driver # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device vr # VIA Rhine, Rhine II # Wireless NIC cards device wlan # 802.11 support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm device wlan_xauth # 802.11 external authenticator support device wlan_acl device ath device ath_pci # Atheros pci/cardbus glue device ath_hal # Atheros HAL (includes binary component) device ath_rate_sample # SampleRate rate control for the ath driver options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel device tap # Ethernet tunnel device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device if_bridge # Bridge interface device vlan # VLAN support (needs miibus) device bpf # Berkeley packet filter device pf # PF OpenBSD packet-filter firewall device pflog # logging support interface for PF #device pfsync # synchronization interface for PF options ALTQ options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Detection options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing #options ALTQ_NOPCC # Required if the TSC is unusable options NETGRAPH # netgraph(4) system options NETGRAPH_ASYNC options NETGRAPH_BPF options NETGRAPH_ETHER options NETGRAPH_IFACE options NETGRAPH_KSOCKET options NETGRAPH_L2TP options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_PPP options NETGRAPH_PPPOE options NETGRAPH_PPTPGRE options NETGRAPH_SOCKET options NETGRAPH_TCPMSS options NETGRAPH_TEE options NETGRAPH_UI options NETGRAPH_VJC device crypto device cryptodev device hifn --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ALIX.hints" # $FreeBSD: src/sys/i386/conf/GENERIC.hints,v 1.16 2006/05/17 21:25:22 marius Exp $ hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.ata.0.at="isa" hint.ata.0.port="0x1F0" hint.ata.0.irq="14" hint.ata.1.at="isa" hint.ata.1.port="0x170" hint.ata.1.irq="15" hint.adv.0.at="isa" hint.adv.0.disabled="1" hint.bt.0.at="isa" hint.bt.0.disabled="1" hint.aha.0.at="isa" hint.aha.0.disabled="1" hint.aic.0.at="isa" hint.aic.0.disabled="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.vga.0.at="isa" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.vt.0.at="isa" hint.vt.0.disabled="1" hint.apm.0.disabled="1" hint.apm.0.flags="0x20" hint.uart.0.at="isa" hint.uart.0.port="0x3F8" hint.uart.0.flags="0x10" hint.uart.0.irq="4" hint.uart.1.at="isa" hint.uart.1.port="0x2F8" hint.uart.1.irq="3" hint.uart.2.at="isa" hint.uart.2.disabled="1" hint.uart.2.port="0x3E8" hint.uart.2.irq="5" hint.uart.3.at="isa" hint.uart.3.disabled="1" hint.uart.3.port="0x2E8" hint.uart.3.irq="9" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.ed.0.at="isa" hint.ed.0.disabled="1" hint.ed.0.port="0x280" hint.ed.0.irq="10" hint.ed.0.maddr="0xd8000" hint.cs.0.at="isa" hint.cs.0.disabled="1" hint.cs.0.port="0x300" hint.sn.0.at="isa" hint.sn.0.disabled="1" hint.sn.0.port="0x300" hint.sn.0.irq="10" hint.ie.0.at="isa" hint.ie.0.disabled="1" hint.ie.0.port="0x300" hint.ie.0.irq="10" hint.ie.0.maddr="0xd0000" hint.fe.0.at="isa" hint.fe.0.disabled="1" hint.fe.0.port="0x300" hint.le.0.at="isa" hint.le.0.disabled="1" hint.le.0.port="0x280" hint.le.0.irq="10" hint.le.0.drq="0" --ZGiS0Q5IWpPtfppv-- From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 06:53:31 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 369E4A72 for ; Fri, 19 Jul 2013 06:53:31 +0000 (UTC) (envelope-from sirok@mail.ru) Received: from fallback4.mail.ru (fallback4.mail.ru [94.100.176.42]) by mx1.freebsd.org (Postfix) with ESMTP id 032AF370 for ; Fri, 19 Jul 2013 06:53:29 +0000 (UTC) Received: from f286.mail.ru (f286.mail.ru [217.69.128.253]) by fallback4.mail.ru (mPOP.Fallback_MX) with ESMTP id DFF7714C3EB for ; Fri, 19 Jul 2013 10:53:27 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=References:In-Reply-To:Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=z1F94UyCb7kyRtSm8T6QlHymv16k+pDg+YZZKGHXkHQ=; b=p54uVkyZG6Vxd+cP5URUHurz4Ma9joYnadYlhYCjY43Bjsgvg+5non7frTUQOniMFFg1wWTHbTh+BwqDQLGz+1zY5/08h8Dik9D4wlWTXkPSD1KPrLQs3dwaN9aTMb/jroq6lkIjBfsHk0L1D9dJQe5iBUgA08MQ2xd764nrhh0=; Received: from mail by f286.mail.ru with local (envelope-from ) id 1V04Z6-0004C7-Bx for freebsd-wireless@freebsd.org; Fri, 19 Jul 2013 10:53:20 +0400 Received: from [85.26.144.211] by e.mail.ru with HTTP; Fri, 19 Jul 2013 10:53:20 +0400 From: =?UTF-8?B?c2lyb2s=?= To: freebsd-wireless@freebsd.org Subject: =?UTF-8?B?QVI5Mjg3IGludGVycnVwdCByYXRl?= Mime-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [85.26.144.211] Date: Fri, 19 Jul 2013 10:53:20 +0400 X-Priority: 3 (Normal) Message-ID: <1374216800.193539560@f286.mail.ru> X-Spam: Not detected X-Mras: Ok In-Reply-To: References: <1374143949.434105019@f394.i.mail.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?UTF-8?B?c2lyb2s=?= List-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, 19 Jul 2013 06:53:31 -0000 IEhpLCBBZHJpYW4KClRoYW5rIHlvdSBmb3IgeW91ciBoZWxwCgp2bXN0YXQgLWkKaW50ZXJydXB0 wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgdG90YWzC oMKgwqDCoMKgwqAgcmF0ZQppcnExNjogYXRoMMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoCA1NzA1ODg0NjQxwqDCoMKgwqAgMTY5ODc4CmlycTIzOiBlaGNpMCBlaGNpMcKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDY4NDk0wqDCoMKgwqDCoMKgwqDCoMKgIDIKY3B1 MDp0aW1lcsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCAzOTY4NDgz McKgwqDCoMKgwqDCoCAxMTgxCmlycTI2NDogcmUwwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgIDE2MTM1NjXCoMKgwqDCoMKgwqDCoMKgIDQ4CmlycTI2NjogYWhjaTDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDMwNTA5NMKgwqDCoMKgwqDC oMKgwqDCoCA5CmNwdTE6dGltZXLCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqAgMzAzMjE2NTnCoMKgwqDCoMKgwqDCoCA5MDIKVG90YWzCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgNTc3Nzg3ODI4NMKgwqDCoMKgIDE3MjAyMgoK dXB0aW1lIC0gOToyMQoKc3lzY3RsIGRldi5hdGguMCAtCmRldi5hdGguMC4lZGVzYzogQXRoZXJv cyA5Mjg3CmRldi5hdGguMC4lZHJpdmVyOiBhdGgKZGV2LmF0aC4wLiVsb2NhdGlvbjogc2xvdD0w IGZ1bmN0aW9uPTAKZGV2LmF0aC4wLiVwbnBpbmZvOiB2ZW5kb3I9MHgxNjhjIGRldmljZT0weDAw MmUgc3VidmVuZG9yPTB4MWEzMiBzdWJkZXZpY2U9MHgwMzA5IGNsYXNzPTB4MDI4MDAwCmRldi5h dGguMC4lcGFyZW50OiBwY2kxCmRldi5hdGguMC5zbW9vdGhpbmdfcmF0ZTogNzUKZGV2LmF0aC4w LnNhbXBsZV9yYXRlOiAxMApkZXYuYXRoLjAuc2FtcGxlX3N0YXRzOiAwCmRldi5hdGguMC5jb3Vu dHJ5Y29kZTogMApkZXYuYXRoLjAucmVnZG9tYWluOiAxMDEKZGV2LmF0aC4wLnNsb3R0aW1lOiA5 CmRldi5hdGguMC5hY2t0aW1lb3V0OiA2NApkZXYuYXRoLjAuY3RzdGltZW91dDogNDgKZGV2LmF0 aC4wLnNvZnRsZWQ6IDAKZGV2LmF0aC4wLmxlZHBpbjogMApkZXYuYXRoLjAubGVkb246IDAKZGV2 LmF0aC4wLmxlZGlkbGU6IDI3MDAKZGV2LmF0aC4wLmhhcmRsZWQ6IDAKZGV2LmF0aC4wLmxlZF9u ZXRfcGluOiAtMQpkZXYuYXRoLjAubGVkX3B3cl9waW46IC0xCmRldi5hdGguMC50eGFudGVubmE6 IDAKZGV2LmF0aC4wLnJ4YW50ZW5uYTogMQpkZXYuYXRoLjAudHhpbnRycGVyaW9kOiA1CmRldi5h dGguMC5kaWFnOiAwCmRldi5hdGguMC50cHNjYWxlOiAwCmRldi5hdGguMC50cGM6IDAKZGV2LmF0 aC4wLnRwYWNrOiA2MwpkZXYuYXRoLjAudHBjdHM6IDYzCmRldi5hdGguMC50eGFnZzogMApkZXYu YXRoLjAuZm9yY2Vic3R1Y2s6IDAKZGV2LmF0aC4wLmhhbmdjaGVjazogMApkZXYuYXRoLjAuaW50 bWl0OiAxCmRldi5hdGguMC5tb25wYXNzOiAyNApkZXYuYXRoLjAuaHdxX2xpbWl0X25vbmFnZ3I6 IDMyCmRldi5hdGguMC5od3FfbGltaXRfYWdncjogMgpkZXYuYXRoLjAudGlkX2h3cV9sbzogMgpk ZXYuYXRoLjAudGlkX2h3cV9oaTogNApkZXYuYXRoLjAuYWdncl9saW1pdDogNjU1MzAKZGV2LmF0 aC4wLnJ0c19hZ2dyX2xpbWl0OiA2NTUzNgpkZXYuYXRoLjAuZGVsaW1fbWluX3BhZDogMApkZXYu YXRoLjAudHhxX2RhdGFfbWluZnJlZTogMTAKZGV2LmF0aC4wLnR4cV9tY2FzdHFfbWF4ZGVwdGg6 IDUxMgpkZXYuYXRoLjAudHhxX25vZGVfbWF4ZGVwdGg6IDEyOApkZXYuYXRoLjAuY2xlYXJfc3Rh dHM6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF93YXRjaGRvZzogMApkZXYuYXRoLjAuc3RhdHMuYXN0 X2hhcmR3YXJlOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfYm1pc3M6IDAKZGV2LmF0aC4wLnN0YXRz LmFzdF9ibWlzc19waGFudG9tOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfYnN0dWNrOiAxNApkZXYu YXRoLjAuc3RhdHMuYXN0X3J4b3JuOiAwCmRldi5hdGguMC5zdGF0cy5hc3Rfcnhlb2w6IDAKZGV2 LmF0aC4wLnN0YXRzLmFzdF90eHVybjogMApkZXYuYXRoLjAuc3RhdHMuYXN0X21pYjogMApkZXYu YXRoLjAuc3RhdHMuYXN0X2ludHJjb2FsOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfcGFja2V0 czogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X21nbXQ6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF90 eF9kaXNjYXJkOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfcXN0b3A6IDAKZGV2LmF0aC4wLnN0 YXRzLmFzdF90eF9lbmNhcDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X25vbm9kZTogMApkZXYu YXRoLjAuc3RhdHMuYXN0X3R4X25vbWJ1ZjogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X25vbWNs OiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfbGluZWFyOiAwCmRldi5hdGguMC5zdGF0cy5hc3Rf dHhfbm9kYXRhOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfYnVzZG1hOiAwCmRldi5hdGguMC5z dGF0cy5hc3RfdHhfeHJldHJpZXM6IDIzMwpkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X2ZpZm9lcnI6 IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF90eF9maWx0ZXJlZDogMApkZXYuYXRoLjAuc3RhdHMuYXN0 X3R4X3Nob3J0cmV0cnk6IDIyMTI5CmRldi5hdGguMC5zdGF0cy5hc3RfdHhfbG9uZ3JldHJ5OiAx Njk0NwpkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X2JhZHJhdGU6IDAKZGV2LmF0aC4wLnN0YXRzLmFz dF90eF9ub2FjazogMTM2MQpkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X3J0czogMApkZXYuYXRoLjAu c3RhdHMuYXN0X3R4X2N0czogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X3Nob3J0cHJlOiA1NDIy MzE3CmRldi5hdGguMC5zdGF0cy5hc3RfdHhfYWx0cmF0ZTogNjgKZGV2LmF0aC4wLnN0YXRzLmFz dF90eF9wcm90ZWN0OiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfY3RzYnVyc3Q6IDAKZGV2LmF0 aC4wLnN0YXRzLmFzdF90eF9jdHNleHQ6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9yeF9ub21idWY6 IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9yeF9idXNkbWE6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9y eF9vcm46IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9yeF9jcmNlcnI6IDI4MzAzCmRldi5hdGguMC5z dGF0cy5hc3RfcnhfZmlmb2VycjogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3J4X2JhZGNyeXB0OiAw CmRldi5hdGguMC5zdGF0cy5hc3RfcnhfYmFkbWljOiAwCmRldi5hdGguMC5zdGF0cy5hc3Rfcnhf cGh5ZXJyOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfcnhfdG9vc2hvcnQ6IDAKZGV2LmF0aC4wLnN0 YXRzLmFzdF9yeF90b29iaWc6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9yeF9wYWNrZXRzOiAwCmRl di5hdGguMC5zdGF0cy5hc3RfcnhfbWd0OiAwCmRldi5hdGguMC5zdGF0cy5hc3RfcnhfY3RsOiAw CmRldi5hdGguMC5zdGF0cy5hc3RfYmVfeG1pdDogMzI3NDQ2CmRldi5hdGguMC5zdGF0cy5hc3Rf YmVfbm9tYnVmOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfcGVyX2NhbDogMTExOApkZXYuYXRoLjAu c3RhdHMuYXN0X3Blcl9jYWxmYWlsOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfcGVyX3JmZ2Fpbjog MApkZXYuYXRoLjAuc3RhdHMuYXN0X3JhdGVfY2FsbHM6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9y YXRlX3JhaXNlOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfcmF0ZV9kcm9wOiAwCmRldi5hdGguMC5z dGF0cy5hc3RfYW50X2RlZnN3aXRjaDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X2FudF90eHN3aXRj aDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X2NhYnFfeG1pdDogMApkZXYuYXRoLjAuc3RhdHMuYXN0 X2NhYnFfYnVzeTogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X3JhdzogMTA1NgpkZXYuYXRoLjAu c3RhdHMuYXN0X2ZmX3R4b2s6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF9mZl90eGVycjogMApkZXYu YXRoLjAuc3RhdHMuYXN0X2ZmX3J4OiAwCmRldi5hdGguMC5zdGF0cy5hc3RfZmZfZmx1c2g6IDAK ZGV2LmF0aC4wLnN0YXRzLmFzdF90eF9xZnVsbDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X25v YnVmOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdGRtYV91cGRhdGU6IDAKZGV2LmF0aC4wLnN0YXRz LmFzdF90ZG1hX3RpbWVyczogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3RkbWFfdHNmOiAwCmRldi5h dGguMC5zdGF0cy5hc3RfdGRtYV9hY2s6IDAKZGV2LmF0aC4wLnN0YXRzLmFzdF90eF9yYXdfZmFp bDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X25vZnJhZzogMApkZXYuYXRoLjAuc3RhdHMuYXN0 X2JlX21pc3NlZDogMzI0CmRldi5hdGguMC5zdGF0cy5hc3RfYW5pX2NhbDogMzM1MzIxCmRldi5h dGguMC5zdGF0cy5hc3RfcnhfYWdnOiAzMzI1OTUKZGV2LmF0aC4wLnN0YXRzLmFzdF9yeF9oYWxm Z2k6IDQ5MTA1CmRldi5hdGguMC5zdGF0cy5hc3RfcnhfMjA0MDogNDU4NzM1CmRldi5hdGguMC5z dGF0cy5hc3RfcnhfcHJlX2NyY19lcnI6IDEwNjE4CmRldi5hdGguMC5zdGF0cy5hc3RfcnhfcG9z dF9jcmNfZXJyOiAyMDYKZGV2LmF0aC4wLnN0YXRzLmFzdF9yeF9kZWNyeXB0X2J1c3lfZXJyOiAw CmRldi5hdGguMC5zdGF0cy5hc3RfcnhfaGlfcnhfY2hhaW46IDAKZGV2LmF0aC4wLnN0YXRzLmFz dF90eF9odHByb3RlY3Q6IDgxOTE4NgpkZXYuYXRoLjAuc3RhdHMuYXN0X3J4X2hpdHF1ZXVlZW5k OiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfdGltZW91dDogMApkZXYuYXRoLjAuc3RhdHMuYXN0 X3R4X2NzdDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X3h0eG9wOiAwCmRldi5hdGguMC5zdGF0 cy5hc3RfdHhfdGltZXJleHBpcmVkOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfZGVzY2NmZ2Vy cjogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X3N3cmV0cmllczogMTk0MDUKZGV2LmF0aC4wLnN0 YXRzLmFzdF90eF9zd3JldHJ5bWF4OiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfZGF0YV91bmRl cnJ1bjogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X2RlbGltX3VuZGVycnVuOiAwCmRldi5hdGgu MC5zdGF0cy5hc3RfdHhfYWdncl9mYWlsYWxsOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfYWdn cl9vazogNTE3OTkzMgpkZXYuYXRoLjAuc3RhdHMuYXN0X3R4X2FnZ3JfZmFpbDogMTk0MDUKZGV2 LmF0aC4wLnN0YXRzLmFzdF9yeF9pbnRyOiA1MDU5NzEKZGV2LmF0aC4wLnN0YXRzLmFzdF90eF9p bnRyOiA3MzExMDEKZGV2LmF0aC4wLnN0YXRzLmFzdF90eF9tY2FzdHFfb3ZlcmZsb3c6IDAKZGV2 LmF0aC4wLnN0YXRzLmFzdF9yeF9rZXltaXNzOiAwCmRldi5hdGguMC5zdGF0cy5hc3RfdHhfc3dm aWx0ZXJlZDogMApkZXYuYXRoLjAuc3RhdHMuYXN0X3J4X3N0YmM6IDMxMDQKZGV2LmF0aC4wLnN0 YXRzLnJ4X3BoeV9lcnIuMDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xOiAwCmRldi5h dGguMC5zdGF0cy5yeF9waHlfZXJyLjI6IDAKZGV2LmF0aC4wLnN0YXRzLnJ4X3BoeV9lcnIuMzog MApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40OiAwCmRldi5hdGguMC5zdGF0cy5yeF9waHlf ZXJyLjU6IDAKZGV2LmF0aC4wLnN0YXRzLnJ4X3BoeV9lcnIuNjogMApkZXYuYXRoLjAuc3RhdHMu cnhfcGh5X2Vyci43OiAwCmRldi5hdGguMC5zdGF0cy5yeF9waHlfZXJyLjg6IDAKZGV2LmF0aC4w LnN0YXRzLnJ4X3BoeV9lcnIuOTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xMDogMApk ZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xMTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vy ci4xMjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xMzogMApkZXYuYXRoLjAuc3RhdHMu cnhfcGh5X2Vyci4xNDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xNTogMApkZXYuYXRo LjAuc3RhdHMucnhfcGh5X2Vyci4xNjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xNzog MApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4xODogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5 X2Vyci4xOTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4yMDogMApkZXYuYXRoLjAuc3Rh dHMucnhfcGh5X2Vyci4yMTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4yMjogMApkZXYu YXRoLjAuc3RhdHMucnhfcGh5X2Vyci4yMzogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4y NDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4yNTogMApkZXYuYXRoLjAuc3RhdHMucnhf cGh5X2Vyci4yNjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4yNzogMApkZXYuYXRoLjAu c3RhdHMucnhfcGh5X2Vyci4yODogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4yOTogMApk ZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4zMDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vy ci4zMTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4zMjogMApkZXYuYXRoLjAuc3RhdHMu cnhfcGh5X2Vyci4zMzogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4zNDogMApkZXYuYXRo LjAuc3RhdHMucnhfcGh5X2Vyci4zNTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4zNjog MApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4zNzogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5 X2Vyci4zODogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci4zOTogMApkZXYuYXRoLjAuc3Rh dHMucnhfcGh5X2Vyci40MDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40MTogMApkZXYu YXRoLjAuc3RhdHMucnhfcGh5X2Vyci40MjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40 MzogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40NDogMApkZXYuYXRoLjAuc3RhdHMucnhf cGh5X2Vyci40NTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40NjogMApkZXYuYXRoLjAu c3RhdHMucnhfcGh5X2Vyci40NzogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40ODogMApk ZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci40OTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vy ci41MDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci41MTogMApkZXYuYXRoLjAuc3RhdHMu cnhfcGh5X2Vyci41MjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci41MzogMApkZXYuYXRo LjAuc3RhdHMucnhfcGh5X2Vyci41NDogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci41NTog MApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci41NjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5 X2Vyci41NzogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci41ODogMApkZXYuYXRoLjAuc3Rh dHMucnhfcGh5X2Vyci41OTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci42MDogMApkZXYu YXRoLjAuc3RhdHMucnhfcGh5X2Vyci42MTogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci42 MjogMApkZXYuYXRoLjAuc3RhdHMucnhfcGh5X2Vyci42MzogMApkZXYuYXRoLjAuc3RhdHMuc3lu Y19pbnRyLjA6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci4xOiAwCmRldi5hdGguMC5zdGF0 cy5zeW5jX2ludHIuMjogMApkZXYuYXRoLjAuc3RhdHMuc3luY19pbnRyLjM6IDAKZGV2LmF0aC4w LnN0YXRzLnN5bmNfaW50ci40OiAwCmRldi5hdGguMC5zdGF0cy5zeW5jX2ludHIuNTogMApkZXYu YXRoLjAuc3RhdHMuc3luY19pbnRyLjY6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci43OiAw CmRldi5hdGguMC5zdGF0cy5zeW5jX2ludHIuODogMApkZXYuYXRoLjAuc3RhdHMuc3luY19pbnRy Ljk6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci4xMDogMApkZXYuYXRoLjAuc3RhdHMuc3lu Y19pbnRyLjExOiAwCmRldi5hdGguMC5zdGF0cy5zeW5jX2ludHIuMTI6IDAKZGV2LmF0aC4wLnN0 YXRzLnN5bmNfaW50ci4xMzogMApkZXYuYXRoLjAuc3RhdHMuc3luY19pbnRyLjE0OiAwCmRldi5h dGguMC5zdGF0cy5zeW5jX2ludHIuMTU6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci4xNjog MApkZXYuYXRoLjAuc3RhdHMuc3luY19pbnRyLjE3OiAwCmRldi5hdGguMC5zdGF0cy5zeW5jX2lu dHIuMTg6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci4xOTogMApkZXYuYXRoLjAuc3RhdHMu c3luY19pbnRyLjIwOiAwCmRldi5hdGguMC5zdGF0cy5zeW5jX2ludHIuMjE6IDAKZGV2LmF0aC4w LnN0YXRzLnN5bmNfaW50ci4yMjogMApkZXYuYXRoLjAuc3RhdHMuc3luY19pbnRyLjIzOiAwCmRl di5hdGguMC5zdGF0cy5zeW5jX2ludHIuMjQ6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci4y NTogMApkZXYuYXRoLjAuc3RhdHMuc3luY19pbnRyLjI2OiAwCmRldi5hdGguMC5zdGF0cy5zeW5j X2ludHIuMjc6IDAKZGV2LmF0aC4wLnN0YXRzLnN5bmNfaW50ci4yODogMApkZXYuYXRoLjAuc3Rh dHMuc3luY19pbnRyLjI5OiAwCmRldi5hdGguMC5zdGF0cy5zeW5jX2ludHIuMzA6IDAKZGV2LmF0 aC4wLnN0YXRzLnN5bmNfaW50ci4zMTogMApkZXYuYXRoLjAuaGFsLmRlYnVnOiAwCmRldi5hdGgu MC5oYWwuYXI1NDE2X2JpYXNhZGo6IDAKZGV2LmF0aC4wLmhhbC5kbWFfYnJ0OiAyCmRldi5hdGgu MC5oYWwuc3dfYnJ0OiAxMApkZXYuYXRoLjAuaGFsLnN3YmFfYmFja29mZjogMApkZXYuYXRoLjAu aGFsLmZvcmNlX2Z1bGxfcmVzZXQ6IDAKZGV2LmF0aC4wLmhhbC5zZXJpYWxpc2VfcmVnX3dhcjog MAoKCgo+SG0sIEkgd29uZGVyIHdoYXQgaW50ZXJydXB0IGl0IGlzLgo+Cj5BZGQgJ29wdGlvbnMg QUhfSU5URVJSVVBUX0RFQlVHR0lORycgYW5kIHJlYnVpbGQuIFRoZW4gYWZ0ZXIgaXQKPmhhcHBl bnMsIHBvc3QgdGhlIG91dHB1dCBvZiAnc3lzY3RsIGRldi5hdGguMCcKPgo+Cj4KPgo+LWFkcmlh bgo+Cj5PbiAxOCBKdWx5IDIwMTMgMDM6MzksIHNpcm9rIDwgc2lyb2tAbWFpbC5ydSA+IHdyb3Rl Ogo+PiAgSGkhCj4+Cj4+IGF0aDA6IDxBdGhlcm9zIDkyODc+IG1lbSAweGZlNTAwMDAwLTB4ZmU1 MGZmZmYgaXJxIDE2IGF0IGRldmljZSAwLjAgb24gcGNpMQo+PiBhdGgwOiBbSFRdIGVuYWJsaW5n IEhUIG1vZGVzCj4+IGF0aDA6IFtIVF0gZW5hYmxpbmcgc2hvcnQtR0kgaW4gMjBNSHogbW9kZQo+ PiBhdGgwOiBbSFRdIDEgc3RyZWFtIFNUQkMgcmVjZWl2ZSBlbmFibGVkCj4+IGF0aDA6IFtIVF0g MSBzdHJlYW0gU1RCQyB0cmFuc21pdCBlbmFibGVkCj4+IGF0aDA6IFtIVF0gMiBSWCBzdHJlYW1z OyAyIFRYIHN0cmVhbXMKPj4gYXRoMDogQVI5Mjg3IG1hYyAzODQuMiBSRjUxMzMgcGh5IDE1LjE1 Cj4+IGF0aDA6IDJHSHogcmFkaW86IDB4MDAwMDsgNUdIeiByYWRpbzogMHgwMGMwCgotLQo= From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 06:56:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 03699AB2 for ; Fri, 19 Jul 2013 06:56:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 94911378 for ; Fri, 19 Jul 2013 06:56:05 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id l18so3683651wgh.14 for ; Thu, 18 Jul 2013 23:56: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0Ug9w5HAufvtdudEWJkP0AN5jRJQLOiHvGPJE+W7egA=; b=o+ONrW+fAyIvOssrdZ1Lfq/hkDIVMUvfT4c0+Gyw212L4qEdQ/UaalLdYPdr/MtZ3P 7RJixhRGF5z2a/U374SSUzv4sS4MoSZvdOToaZZOloELb3wqNYfnA7X7nkCTOspB+4q1 TZ4iN2Jc3a6H5gHJBrNmZqPZfUz4+2/FHNVEgjG52v2Pu58qIzddhu5ufZ3LJBYZSYQk 40cwA2sLO7LDiXg3Cdq+jvUbEyPd+DlQrtLFEXXKnFXi9VyDMPzClmznUDn4CZysrHGb w6FUYhn4Ex+RyNpjW6TP7tBP1RunT3VA9a6AIPvIrxt5DIl4IDhhwpWJ4t5P9AZmLEM6 A0gA== MIME-Version: 1.0 X-Received: by 10.194.63.229 with SMTP id j5mr10747398wjs.79.1374216964810; Thu, 18 Jul 2013 23:56:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 18 Jul 2013 23:56:04 -0700 (PDT) In-Reply-To: <1374216800.193539560@f286.mail.ru> References: <1374143949.434105019@f394.i.mail.ru> <1374216800.193539560@f286.mail.ru> Date: Thu, 18 Jul 2013 23:56:04 -0700 X-Google-Sender-Auth: sHhJltma8MxYr7vkoyKepLXM4Oc Message-ID: Subject: Re: AR9287 interrupt rate From: Adrian Chadd To: sirok Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 06:56:06 -0000 Hi, Did you add the interrupt mitigation option (I think it's AH_AR5416_INTERRUPT_MITIGATION) in your kernel? -adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 07:14:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D45B3273 for ; Fri, 19 Jul 2013 07:14:22 +0000 (UTC) (envelope-from sirok@mail.ru) Received: from f335.i.mail.ru (f335.mail.ru [217.69.140.231]) by mx1.freebsd.org (Postfix) with ESMTP id 8BCDD61E for ; Fri, 19 Jul 2013 07:14:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=References:Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=oSY/M45crvvP2EB4YNqOVmE8od0ydZ6rfAPPNz6071I=; b=gGTxWKTUE0MRlPwfJKT+HH7qqZNCpA+NpDoj8Bvbvr/zJOioira7nuP7vo6TY7mCWRvX8+5+bLo+jFb769QqfhvpGxhYTVy+jf3Ii6WJKP97jP9GuP3IBoW++1UpdWqM9Q6GKwfYko9Q8UZXfuy7OmRTq666H2I62xO9ztb8Hgk=; Received: from mail by f335.i.mail.ru with local (envelope-from ) id 1V04tQ-0001EH-Gk for freebsd-wireless@freebsd.org; Fri, 19 Jul 2013 11:14:20 +0400 Received: from [85.26.144.211] by e.mail.ru with HTTP; Fri, 19 Jul 2013 11:14:20 +0400 From: =?UTF-8?B?c2lyb2s=?= To: =?UTF-8?B?ZnJlZWJzZC13aXJlbGVzcw==?= Subject: =?UTF-8?B?QVI5Mjg3IGludGVycnVwdCByYXRl?= Mime-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [85.26.144.211] Date: Fri, 19 Jul 2013 11:14:20 +0400 X-Priority: 3 (Normal) Message-ID: <1374218060.561581929@f335.i.mail.ru> X-Mras: Ok References: <1374143949.434105019@f394.i.mail.ru> <1374216800.193539560@f286.mail.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?UTF-8?B?c2lyb2s=?= List-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, 19 Jul 2013 07:14:22 -0000 IEl0J3MgYWxtb3N0IEdFTkVSSUMga2VybmVsIHdpdGggdmVyeSBzbGlnaHQgZGlmZmVyZW5jZXMg cmVsYXRlZCB0byBuZXR3b3JrIChmaXJld2FsbCwgaXBzZWMpLgpUaGVyZWZvcmUsIHllcywgSSBk aWQuCgoKZGV2aWNlwqDCoMKgwqDCoMKgwqDCoMKgIGF0aMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oCAjIEF0aGVyb3MgTklDcwpkZXZpY2XCoMKgwqDCoMKgwqDCoMKgwqAgYXRoX3BjacKgwqDCoMKg wqDCoMKgwqAgIyBBdGhlcm9zIHBjaS9jYXJkYnVzIGdsdWUKZGV2aWNlwqDCoMKgwqDCoMKgwqDC oMKgIGF0aF9oYWzCoMKgwqDCoMKgwqDCoMKgICMgcGNpL2NhcmRidXMgY2hpcCBzdXBwb3J0Cm9w dGlvbnPCoMKgwqDCoMKgwqDCoMKgIEFIX1NVUFBPUlRfQVI1NDE2wqDCoMKgwqDCoMKgICMgZW5h YmxlIEFSNTQxNiB0eC9yeCBkZXNjcmlwdG9ycwpvcHRpb25zwqDCoMKgwqDCoMKgwqDCoCBBSF9B UjU0MTZfSU5URVJSVVBUX01JVElHQVRJT07CoCAjIEFSNTQxNiBpbnRlcnJ1cHQgbWl0aWdhdGlv bgpvcHRpb25zwqDCoMKgwqDCoMKgwqDCoCBBVEhfRU5BQkxFXzExTsKgICMgRW5hYmxlIDgwMi4x MW4gc3VwcG9ydCBmb3IgQVI1NDE2IGFuZCBsYXRlcgpkZXZpY2XCoMKgwqDCoMKgwqDCoMKgwqAg YXRoX3JhdGVfc2FtcGxlICMgU2FtcGxlUmF0ZSB0eCByYXRlIGNvbnRyb2wgZm9yIGF0aAouLi4K b3B0aW9uc8KgwqDCoMKgwqDCoMKgwqAgQUhfSU5URVJSVVBUX0RFQlVHR0lORwoKCgo+SGksCj4K PkRpZCB5b3UgYWRkIHRoZSBpbnRlcnJ1cHQgbWl0aWdhdGlvbiBvcHRpb24gKEkgdGhpbmsgaXQn cwo+QUhfQVI1NDE2X0lOVEVSUlVQVF9NSVRJR0FUSU9OKSBpbiB5b3VyIGtlcm5lbD8KPgo+Cj4t YWRyaWFuCgoKLS0K From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 07:20:36 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4C12338E for ; Fri, 19 Jul 2013 07:20:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id DDA7E658 for ; Fri, 19 Jul 2013 07:20:35 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id p60so3729654wes.27 for ; Fri, 19 Jul 2013 00:20: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=eYCdkIkE4bYyCPQh0mgYwjqxCv9U+4rHz1GOwyJkmgI=; b=lJD3Kd8V4Oe8dJWHydxSEJXdyz+SgnEZo5aSebJKS1SC09+jSzev6RF+N+kZ7lX5V8 2U0HETRy/7fDTQASYHebyO3apgS+ugMejGu0PMmSufg7fW7ZLAQeUXQ45jwgWo3wyV62 3G+iQgOsXqe+clQxq9r38kYeIS3bJ6eKomvApJxKngfVWHiGEE7i2kgs7uXgF05Gyj1R fwU3GKLcbNT54Drw6+rtumW2dVS5or0G5dqNuaZfKhiK1t9KqJCAhcFuYLMZv2Ny1ZKe ZRsmDYMhga9VtfB+Hw+fHYHANoZ7ISAqmKBafr6QbKxvxiQjSbShl9IGUhwfB0cdOERQ Lf4Q== MIME-Version: 1.0 X-Received: by 10.180.14.105 with SMTP id o9mr15466870wic.30.1374218435076; Fri, 19 Jul 2013 00:20:35 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Fri, 19 Jul 2013 00:20:35 -0700 (PDT) In-Reply-To: <1374218060.561581929@f335.i.mail.ru> References: <1374143949.434105019@f394.i.mail.ru> <1374216800.193539560@f286.mail.ru> <1374218060.561581929@f335.i.mail.ru> Date: Fri, 19 Jul 2013 00:20:35 -0700 X-Google-Sender-Auth: CbMtXIoJrmN2_aEaorFCwih4IT4 Message-ID: Subject: Re: AR9287 interrupt rate From: Adrian Chadd To: sirok Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 07:20:36 -0000 Hm, then I'm at a loss :( -adrian On 19 July 2013 00:14, sirok wrote: > It's almost GENERIC kernel with very slight differences related to network (firewall, ipsec). > Therefore, yes, I did. > > > device ath # Atheros NICs > device ath_pci # Atheros pci/cardbus glue > device ath_hal # pci/cardbus chip support > options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors > options AH_AR5416_INTERRUPT_MITIGATION # AR5416 interrupt mitigation > options ATH_ENABLE_11N # Enable 802.11n support for AR5416 and later > device ath_rate_sample # SampleRate tx rate control for ath > ... > options AH_INTERRUPT_DEBUGGING > > > >>Hi, >> >>Did you add the interrupt mitigation option (I think it's >>AH_AR5416_INTERRUPT_MITIGATION) in your kernel? >> >> >>-adrian > > > -- > _______________________________________________ > 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 Jul 19 08:43:43 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B7F1E6B4; Fri, 19 Jul 2013 08:43:43 +0000 (UTC) (envelope-from sirok@mail.ru) Received: from fallback8.mail.ru (fallback8.mail.ru [94.100.176.136]) by mx1.freebsd.org (Postfix) with ESMTP id 14D2E9EA; Fri, 19 Jul 2013 08:43:42 +0000 (UTC) Received: from f164.mail.ru (f164.mail.ru [94.100.178.83]) by fallback8.mail.ru (mPOP.Fallback_MX) with ESMTP id 15C6E34F489A; Fri, 19 Jul 2013 12:41:37 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=References:In-Reply-To:Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:Cc:To:From; bh=QFnDxjnWPhZdpsxTWWADsWUDsIIHqKkRiGXZSzqiLn4=; b=T6PfOsqUh9+Ut8z2LIGFEeirXRDcOerHBM9WUwV3omdDwj48ndJt1BsSaC5hrhM60XybQeWRPiLsCFsY+nE4BEm6s5oQmii/fSqpy7WU3fbA3chH/+ZSSfdooIOa6ghRMNumDdETLK27csXeh9qAxjRD7XOU9nyGbvN+Y88vGU8=; Received: from mail by f164.mail.ru with local (envelope-from ) id 1V06Fm-0003dO-6S; Fri, 19 Jul 2013 12:41:30 +0400 Received: from [85.26.144.211] by e.mail.ru with HTTP; Fri, 19 Jul 2013 12:41:30 +0400 From: =?UTF-8?B?c2lyb2s=?= To: =?UTF-8?B?ZnJlZWJzZC13aXJlbGVzcw==?= Subject: =?UTF-8?B?UmVbMl06IEFSOTI4NyBpbnRlcnJ1cHQgcmF0ZQ==?= Mime-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [85.26.144.211] Date: Fri, 19 Jul 2013 12:41:30 +0400 X-Priority: 3 (Normal) Message-ID: <1374223290.633625586@f164.mail.ru> X-Spam: Not detected X-Mras: Ok In-Reply-To: References: <1374143949.434105019@f394.i.mail.ru> <1374218060.561581929@f335.i.mail.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: =?UTF-8?B?c2lyb2s=?= List-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, 19 Jul 2013 08:43:43 -0000 IFRoYXQncyBzYWQgOi0pCkkgaGF2ZSBhIHJlYWxseSBiYWQgbHVjayB3aXRoIGZyZWVic2Qgd2ly ZWxlc3MgZm9yIG1hbnkgeWVhcnMuIFNvIEknbSB0aGUgYmVzdCBvbmUgdG8gdGVzdC4KSW4gdGhh dCBjYXNlIEkgd2lsbCB0cnkgYSBkaWZmZXJlbnQgY2FyZCAoSSBhbHNvIGhhdmUgdGhlIEFSOTU5 MCwgQVI5Mjg1IGFuZCBldmVuIHNvbWUgbW9yZSksIGRpZmZlcmVudCBzeXN0ZW0gKG1vdGhlcmJv YXJkKSwgZGlmZmVyZW50IE9TIChMaW51eCkgdG8gc2VlIHdoZXJlIGlzIHRoZSBwcm9ibGVtIGJ5 IGV4Y2x1c2lvbi4KSSB3b3VsZCBhcHByZWNpYXRlIGFueSBpZGVhcy4KClRoYW5rIHlvdQoKPkht LCB0aGVuIEknbSBhdCBhIGxvc3MgOigKPgo+Cj4tYWRyaWFuCj4KPk9uIDE5IEp1bHkgMjAxMyAw MDoxNCwgc2lyb2sgPCBzaXJva0BtYWlsLnJ1ID4gd3JvdGU6Cj4+ICBJdCdzIGFsbW9zdCBHRU5F UklDIGtlcm5lbCB3aXRoIHZlcnkgc2xpZ2h0IGRpZmZlcmVuY2VzIHJlbGF0ZWQgdG8gbmV0d29y ayAoZmlyZXdhbGwsIGlwc2VjKS4KPj4gVGhlcmVmb3JlLCB5ZXMsIEkgZGlkLgo+Pgo+Pgo+PiBk ZXZpY2UgICAgICAgICAgYXRoICAgICAgICAgICAgICMgQXRoZXJvcyBOSUNzCj4+IGRldmljZSAg ICAgICAgICBhdGhfcGNpICAgICAgICAgIyBBdGhlcm9zIHBjaS9jYXJkYnVzIGdsdWUKPj4gZGV2 aWNlICAgICAgICAgIGF0aF9oYWwgICAgICAgICAjIHBjaS9jYXJkYnVzIGNoaXAgc3VwcG9ydAo+ PiBvcHRpb25zICAgICAgICAgQUhfU1VQUE9SVF9BUjU0MTYgICAgICAgIyBlbmFibGUgQVI1NDE2 IHR4L3J4IGRlc2NyaXB0b3JzCj4+IG9wdGlvbnMgICAgICAgICBBSF9BUjU0MTZfSU5URVJSVVBU X01JVElHQVRJT04gICMgQVI1NDE2IGludGVycnVwdCBtaXRpZ2F0aW9uCj4+IG9wdGlvbnMgICAg ICAgICBBVEhfRU5BQkxFXzExTiAgIyBFbmFibGUgODAyLjExbiBzdXBwb3J0IGZvciBBUjU0MTYg YW5kIGxhdGVyCj4+IGRldmljZSAgICAgICAgICBhdGhfcmF0ZV9zYW1wbGUgIyBTYW1wbGVSYXRl IHR4IHJhdGUgY29udHJvbCBmb3IgYXRoCj4+IC4uLgo+PiBvcHRpb25zICAgICAgICAgQUhfSU5U RVJSVVBUX0RFQlVHR0lORwo+Pgo+Pgo+Pgo+Pj5IaSwKPj4+Cj4+PkRpZCB5b3UgYWRkIHRoZSBp bnRlcnJ1cHQgbWl0aWdhdGlvbiBvcHRpb24gKEkgdGhpbmsgaXQncwo+Pj5BSF9BUjU0MTZfSU5U RVJSVVBUX01JVElHQVRJT04pIGluIHlvdXIga2VybmVsPwo+Pj4KPj4+Cj4+Pi1hZHJpYW4KPj4K Pj4KPj4gLS0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KPj4gIGZyZWVic2Qtd2lyZWxlc3NAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0Cj4+ICBodHRw Oi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXdpcmVsZXNzCj4+ IFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLXdpcmVsZXNzLXVuc3Vi c2NyaWJlQGZyZWVic2Qub3JnIgoKCi0tCg== From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 20:49:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 54BEA81B for ; Fri, 19 Jul 2013 20:49:55 +0000 (UTC) (envelope-from mark_moes@hotmail.com) Received: from dub0-omc1-s5.dub0.hotmail.com (dub0-omc1-s5.dub0.hotmail.com [157.55.0.204]) by mx1.freebsd.org (Postfix) with ESMTP id EEAE0BF for ; Fri, 19 Jul 2013 20:49:54 +0000 (UTC) Received: from DUB119-W51 ([157.55.0.238]) by dub0-omc1-s5.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 19 Jul 2013 13:48:46 -0700 X-TMN: [9LmxbxFk/YRDbKSqL+KgDPfM0G8PsIZu] X-Originating-Email: [mark_moes@hotmail.com] Message-ID: From: Mark Moes To: "freebsd-wireless@freebsd.org" Subject: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection Date: Fri, 19 Jul 2013 22:48:47 +0200 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 19 Jul 2013 20:48:46.0732 (UTC) FILETIME=[5D303CC0:01CE84C1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 20:49:55 -0000 Hi all! Having just posted opened a thread about this on the FreeBSD forum=2C I'll = more or less copy/paste that post in this mail. Thread: http://forums.freeb= sd.org/showthread.php?p=3D227470 - - - I have the "Alfa AWUS036h 802.11 b/g Long-Range USB Adapter" connected to m= y laptop which is running a FreeBSD 8.1 installation. The adapter is widely= used for injecting wireless frames=2C which is my objective as well. I have set it up to use the urtw(4) driver (manpage) by loading the module = at boot time. The output of `dmesg | grep urtw` is as follows: urtw0: on usbus7 urtw0: unknown RTL8187L type: 0x8000000 urtw0: rtl8187l rf rtl8225u hwrev none That looks kinda strange=2C but the adapter works and I am able to successf= ully create a wlan0 interface and connect to my WPA2 secured network. However=2C if I want to create a wlan0 interface (after destroying the prev= ious one) that is usable for packet injection=2C this is what I get. `ifconfig wlan create wlandev urtw0 wlanmode ahdemo` urtw0: AHDEMO mode not supported # <-- this line is colored white as oppose= d to normal gray ifconfig: SIOCIFCREATE2: Operation not supported Is this mode simply not (yet) supported? Cheers=2C Mark / asfdg = From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 21:41:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A53AE67E for ; Fri, 19 Jul 2013 21:41:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) by mx1.freebsd.org (Postfix) with ESMTP id 6CD6E2A1 for ; Fri, 19 Jul 2013 21:41:26 +0000 (UTC) Received: by mail-qe0-f48.google.com with SMTP id 2so2663963qea.7 for ; Fri, 19 Jul 2013 14:41:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=yQZfdwqXagHceTDn6uMNQ8FvGbl1lWmx2kVyi/jTS3E=; b=E++5fLQrsmPY10vUGWZpNLyLE/5azECuMdPHsNhRPHrte0vyHj/9UkIR91y7LbSCt9 u9VxVl51/TcIRv6+gSOTpXSvuNGrFah0+UwF6da+k3YeFawdLq1oO/gncvueHHhWNvsA HfuLGjnxZGKHmpb7cp4ChkLIh3GlrzQZsyqZ4Rcfva3I1b0PfW3QBuMEzEu7iMPVaP97 ENPEgLAgNineo4Ax49N0zitEu8l/uFd15ykqunNgeRigVzXbNGRiJnuu5wvhFZXLxCv9 goUq7Fz1SM5CxM/5Ggt7AVxCP6wxwSU3L16JYMfTJNwdohBhchxLYqtRgfyMkcVtDi0i ToFQ== MIME-Version: 1.0 X-Received: by 10.49.107.201 with SMTP id he9mr19537505qeb.74.1374270085981; Fri, 19 Jul 2013 14:41:25 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Fri, 19 Jul 2013 14:41:25 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jul 2013 14:41:25 -0700 X-Google-Sender-Auth: 8k6fgVQeihfgcbj8c9JawE7HcH0 Message-ID: Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection From: Adrian Chadd To: Mark Moes Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 21:41:26 -0000 Hi, * Please update to -HEAD first; I'd like to fix packet injection mode (which means making ahdemo mode) but I'd like to do this in -HEAD. * I don't know if the hardware supports raw frame injection. Maybe it does but the driver hasn't been updated yet. -adrian On 19 July 2013 13:48, Mark Moes wrote: > Hi all! > > Having just posted opened a thread about this on the FreeBSD forum, I'll more or less copy/paste that post in this mail. Thread: http://forums.freebsd.org/showthread.php?p=227470 > - - - > > I have the "Alfa AWUS036h 802.11 b/g Long-Range USB Adapter" connected to my laptop which is running a FreeBSD 8.1 installation. The adapter is widely used for injecting wireless frames, which is my objective as well. > > I have set it up to use the urtw(4) driver (manpage) by loading the module at boot time. > > The output of `dmesg | grep urtw` is as follows: > > urtw0: on usbus7 > urtw0: unknown RTL8187L type: 0x8000000 > urtw0: rtl8187l rf rtl8225u hwrev none > > > That looks kinda strange, but the adapter works and I am able to successfully create a wlan0 interface and connect to my WPA2 secured network. > However, if I want to create a wlan0 interface (after destroying the previous one) that is usable for packet injection, this is what I get. > > `ifconfig wlan create wlandev urtw0 wlanmode ahdemo` > > urtw0: AHDEMO mode not supported # <-- this line is colored white as opposed to normal gray > ifconfig: SIOCIFCREATE2: Operation not supported > > > Is this mode simply not (yet) supported? > > > Cheers, > > Mark / asfdg > > _______________________________________________ > 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 Jul 19 22:17:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8A56AA42 for ; Fri, 19 Jul 2013 22:17:40 +0000 (UTC) (envelope-from mark_moes@hotmail.com) Received: from dub0-omc1-s8.dub0.hotmail.com (dub0-omc1-s8.dub0.hotmail.com [157.55.0.207]) by mx1.freebsd.org (Postfix) with ESMTP id 310B33D2 for ; Fri, 19 Jul 2013 22:17:39 +0000 (UTC) Received: from DUB119-W14 ([157.55.0.237]) by dub0-omc1-s8.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 19 Jul 2013 15:16:32 -0700 X-TMN: [NL+TJtM152K3BcO3VQLNp+suisM2/cRn] X-Originating-Email: [mark_moes@hotmail.com] Message-ID: From: Mark Moes To: "freebsd-wireless@freebsd.org" Subject: RE: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection Date: Sat, 20 Jul 2013 00:16:32 +0200 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 19 Jul 2013 22:16:32.0860 (UTC) FILETIME=[A00B99C0:01CE84CD] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 22:17:40 -0000 Hi=2C I understand you want to fix it in 9.1. The reason that I was using 8.1 is = that I want to see how injection works there=2C to then somehow clone this = to a distribution based on 8.1 which does not support injection. But I can = install 9.1 alongside to test an updated driver in the future for sure. The hardware is capable of injection=2C listed at the aircrack-ng website a= s a recommendation etc. http://www.aircrack-ng.org/doku.php?id=3Dcompatibility_drivers=20 http://softwaregeneration.org/alfa-network-awus036h-wifi/=20 Is it complicated to add ahdemo support? Mark > Date: Fri=2C 19 Jul 2013 14:41:25 -0700 > Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for i= njection > From: adrian@freebsd.org > To: mark_moes@hotmail.com > CC: freebsd-wireless@freebsd.org >=20 > Hi=2C >=20 > * Please update to -HEAD first=3B I'd like to fix packet injection mode > (which means making ahdemo mode) but I'd like to do this in -HEAD. > * I don't know if the hardware supports raw frame injection. Maybe it > does but the driver hasn't been updated yet. >=20 >=20 >=20 > -adrian >=20 > On 19 July 2013 13:48=2C Mark Moes wrote: > > Hi all! > > > > Having just posted opened a thread about this on the FreeBSD forum=2C I= 'll more or less copy/paste that post in this mail. Thread: http://forums.f= reebsd.org/showthread.php?p=3D227470 > > - - - > > > > I have the "Alfa AWUS036h 802.11 b/g Long-Range USB Adapter" connected = to my laptop which is running a FreeBSD 8.1 installation. The adapter is wi= dely used for injecting wireless frames=2C which is my objective as well. > > > > I have set it up to use the urtw(4) driver (manpage) by loading the mod= ule at boot time. > > > > The output of `dmesg | grep urtw` is as follows: > > > > urtw0: on usbus7 > > urtw0: unknown RTL8187L type: 0x8000000 > > urtw0: rtl8187l rf rtl8225u hwrev none > > > > > > That looks kinda strange=2C but the adapter works and I am able to succ= essfully create a wlan0 interface and connect to my WPA2 secured network. > > However=2C if I want to create a wlan0 interface (after destroying the = previous one) that is usable for packet injection=2C this is what I get. > > > > `ifconfig wlan create wlandev urtw0 wlanmode ahdemo` > > > > urtw0: AHDEMO mode not supported # <-- this line is colored white as op= posed to normal gray > > ifconfig: SIOCIFCREATE2: Operation not supported > > > > > > Is this mode simply not (yet) supported? > > > > > > Cheers=2C > > > > Mark / asfdg > > > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe=2C send any mail to "freebsd-wireless-unsubscribe@freebs= d.org" = From owner-freebsd-wireless@FreeBSD.ORG Fri Jul 19 22:20:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 72A4CA7C for ; Fri, 19 Jul 2013 22:20:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 36B873E2 for ; Fri, 19 Jul 2013 22:20:30 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id n1so2594489qcw.16 for ; Fri, 19 Jul 2013 15:20: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hasSrB7FwUZ5hOEZzT6e+BDWgOdMC0D9PDRKTtoh4Hg=; b=POlUq+se4NCA2VSxTn5Knobo96zKRCnqmqLlawdZ4dSSnv/LtfdxLIyPO2s6NZdLT2 gf7obU2XlOnu2Pxib6rSDzxfiu5VSkNsuiXp96A4pUXQ6H/dVmbogmpEio1qrCyNP92E K0tlUwcVz3O1YLysHQn2JiOCcZl44W0nbicGN3mEeRsom2sir9ePMiJsU0D74xjziDZr Jjp8sk8iWy/BoSFD/mRnAQbEhU4l8Ol93qnoxTfYRwojo0fOdlGl9uVfztS9+6RL19ft BJenstcsR+CIFQSukaCxP+lzGUpbgFWDeYX1spH8zGKWny0HJPg192Y/YB6Vm6GY8LdN ynig== MIME-Version: 1.0 X-Received: by 10.229.163.4 with SMTP id y4mr4615433qcx.4.1374272419974; Fri, 19 Jul 2013 15:20:19 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Fri, 19 Jul 2013 15:20:19 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jul 2013 15:20:19 -0700 X-Google-Sender-Auth: 5UII04hXTK8chYQgFUJ4vggyDS0 Message-ID: Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection From: Adrian Chadd To: Mark Moes 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.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 22:20:30 -0000 Right, but someone has to go and teach the driver the bits needed to do raw frame injection. I don't unfortunately have the time to fix the driver(s) to support this. I'll fix it for ath(4) and make it work for 11n, then fix whatever odd crap comes up in the net80211 stack. But someone else has to pick up the driver. :P -adrian On 19 July 2013 15:16, Mark Moes wrote: > Hi, > > > I understand you want to fix it in 9.1. The reason that I was using 8.1 i= s that I want to see how injection works there, to then somehow clone this = to a distribution based on 8.1 which does not support injection. But I can = install 9.1 alongside to test an updated driver in the future for sure. > > The hardware is capable of injection, listed at the aircrack-ng website a= s a recommendation etc. > http://www.aircrack-ng.org/doku.php?id=3Dcompatibility_drivers > http://softwaregeneration.org/alfa-network-awus036h-wifi/ > > Is it complicated to add ahdemo support? > > > Mark > >> Date: Fri, 19 Jul 2013 14:41:25 -0700 >> Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for = injection >> From: adrian@freebsd.org >> To: mark_moes@hotmail.com >> CC: freebsd-wireless@freebsd.org >> >> Hi, >> >> * Please update to -HEAD first; I'd like to fix packet injection mode >> (which means making ahdemo mode) but I'd like to do this in -HEAD. >> * I don't know if the hardware supports raw frame injection. Maybe it >> does but the driver hasn't been updated yet. >> >> >> >> -adrian >> >> On 19 July 2013 13:48, Mark Moes wrote: >> > Hi all! >> > >> > Having just posted opened a thread about this on the FreeBSD forum, I'= ll more or less copy/paste that post in this mail. Thread: http://forums.fr= eebsd.org/showthread.php?p=3D227470 >> > - - - >> > >> > I have the "Alfa AWUS036h 802.11 b/g Long-Range USB Adapter" connected= to my laptop which is running a FreeBSD 8.1 installation. The adapter is w= idely used for injecting wireless frames, which is my objective as well. >> > >> > I have set it up to use the urtw(4) driver (manpage) by loading the mo= dule at boot time. >> > >> > The output of `dmesg | grep urtw` is as follows: >> > >> > urtw0: on usbus7 >> > urtw0: unknown RTL8187L type: 0x8000000 >> > urtw0: rtl8187l rf rtl8225u hwrev none >> > >> > >> > That looks kinda strange, but the adapter works and I am able to succe= ssfully create a wlan0 interface and connect to my WPA2 secured network. >> > However, if I want to create a wlan0 interface (after destroying the p= revious one) that is usable for packet injection, this is what I get. >> > >> > `ifconfig wlan create wlandev urtw0 wlanmode ahdemo` >> > >> > urtw0: AHDEMO mode not supported # <-- this line is colored white as o= pposed to normal gray >> > ifconfig: SIOCIFCREATE2: Operation not supported >> > >> > >> > Is this mode simply not (yet) supported? >> > >> > >> > Cheers, >> > >> > Mark / asfdg >> > >> > _______________________________________________ >> > freebsd-wireless@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd= .org" > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 02:53:38 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E5162292; Sat, 20 Jul 2013 02:53:37 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by mx1.freebsd.org (Postfix) with ESMTP id A5B18D06; Sat, 20 Jul 2013 02:53:37 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id k14so6880556oag.40 for ; Fri, 19 Jul 2013 19:53:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HR44hKnYmE7NoeY1t08ezAWmJC01DLHuAGzrktFxXms=; b=qXKyyKLhf0E0W3FAJUvvHdH/FkgfuIGc6Sfn7U3gjZMFgLGQIZ/caIknuDOtnGR7Q7 nBZBQuIDAfp/ZUHSDwl0np3BRcX0PxGY0G8BBk2zfuw1q9wf/2FfwChgHKh0XbG60Y4B 7z+RtSQkUJwnPTJFc+gTq9yVVtv+0ya8fb0JXFDp7B5WfwFnPyYRGWpvcwOzqg3w53CI 6BfZokcBIfCqNPqo0Ld/tzl5vKY0dDmO+wE75C9cw+N1qDIB+Bf/JctJ+hiAq4N5FsDM 1VFt0wHagsvMiOcMPqyafKdz693G0nHQ5WjDzhu68FDqNDqxDVRxXoM5dBpOHVWCLeGX Difw== MIME-Version: 1.0 X-Received: by 10.60.145.173 with SMTP id sv13mr20076581oeb.63.1374288817225; Fri, 19 Jul 2013 19:53:37 -0700 (PDT) Received: by 10.76.90.197 with HTTP; Fri, 19 Jul 2013 19:53:37 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jul 2013 22:53:37 -0400 Message-ID: Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection From: Outback Dingo To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 02:53:38 -0000 On Fri, Jul 19, 2013 at 6:20 PM, Adrian Chadd wrote: > Right, but someone has to go and teach the driver the bits needed to > do raw frame injection. > > I don't unfortunately have the time to fix the driver(s) to support > this. I'll fix it for ath(4) and make it work for 11n, then fix > whatever odd crap comes up in the net80211 stack. But someone else has > to pick up the driver. :P > > > So wait, are you stating FreeBSD supports packet injection in monitor mode on ath5k/ath9k chips now?? > > -adrian > > On 19 July 2013 15:16, Mark Moes wrote: > > Hi, > > > > > > I understand you want to fix it in 9.1. The reason that I was using 8.1 > is that I want to see how injection works there, to then somehow clone this > to a distribution based on 8.1 which does not support injection. But I can > install 9.1 alongside to test an updated driver in the future for sure. > > > > The hardware is capable of injection, listed at the aircrack-ng website > as a recommendation etc. > > http://www.aircrack-ng.org/doku.php?id=compatibility_drivers > > http://softwaregeneration.org/alfa-network-awus036h-wifi/ > > > > Is it complicated to add ahdemo support? > > > > > > Mark > > > >> Date: Fri, 19 Jul 2013 14:41:25 -0700 > >> Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for > injection > >> From: adrian@freebsd.org > >> To: mark_moes@hotmail.com > >> CC: freebsd-wireless@freebsd.org > >> > >> Hi, > >> > >> * Please update to -HEAD first; I'd like to fix packet injection mode > >> (which means making ahdemo mode) but I'd like to do this in -HEAD. > >> * I don't know if the hardware supports raw frame injection. Maybe it > >> does but the driver hasn't been updated yet. > >> > >> > >> > >> -adrian > >> > >> On 19 July 2013 13:48, Mark Moes wrote: > >> > Hi all! > >> > > >> > Having just posted opened a thread about this on the FreeBSD forum, > I'll more or less copy/paste that post in this mail. Thread: > http://forums.freebsd.org/showthread.php?p=227470 > >> > - - - > >> > > >> > I have the "Alfa AWUS036h 802.11 b/g Long-Range USB Adapter" > connected to my laptop which is running a FreeBSD 8.1 installation. The > adapter is widely used for injecting wireless frames, which is my objective > as well. > >> > > >> > I have set it up to use the urtw(4) driver (manpage) by loading the > module at boot time. > >> > > >> > The output of `dmesg | grep urtw` is as follows: > >> > > >> > urtw0: 2> on usbus7 > >> > urtw0: unknown RTL8187L type: 0x8000000 > >> > urtw0: rtl8187l rf rtl8225u hwrev none > >> > > >> > > >> > That looks kinda strange, but the adapter works and I am able to > successfully create a wlan0 interface and connect to my WPA2 secured > network. > >> > However, if I want to create a wlan0 interface (after destroying the > previous one) that is usable for packet injection, this is what I get. > >> > > >> > `ifconfig wlan create wlandev urtw0 wlanmode ahdemo` > >> > > >> > urtw0: AHDEMO mode not supported # <-- this line is colored white as > opposed to normal gray > >> > ifconfig: SIOCIFCREATE2: Operation not supported > >> > > >> > > >> > Is this mode simply not (yet) supported? > >> > > >> > > >> > Cheers, > >> > > >> > Mark / asfdg > >> > > >> > _______________________________________________ > >> > 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" > _______________________________________________ > 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 Jul 20 02:55:03 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 62A202AB for ; Sat, 20 Jul 2013 02:55:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by mx1.freebsd.org (Postfix) with ESMTP id 26DD8D0C for ; Sat, 20 Jul 2013 02:55:03 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id bv4so242033qab.6 for ; Fri, 19 Jul 2013 19:55:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UWqwlSpLb/WdCmsejZM5TTPhbic3olCeDm+GwMlRHWs=; b=ZVEOlOi71C5HMGLvXNUNafOPXEt1sn+WsYTotPjoIdXwqA5J41ATVE9AkJWw7IV6tD cJMJur2S+CsuIi1kN1rZlvCYtH8AEJlfORRG7MUkmHkkTsOvayB0Z8NphagB7ZGeEX4j /11cGjPmKbQfDBFTnsRnbExC2TsM35J3cJh5NKENo1Qw59J2X5Nu46vkHI+yWnrgUW1A OMB2wKIGyI7HfYsG28vlR1QFpQzJPEuMdOkO6ZUWDFYMyuIjtMkcwEynj6JjCbybc5ay eVNiSNDlDGY2e/BVU9CNLLHZNXoMGhN1q6ItDW3/M239frYTUnb0Z6feyVxBXxzde6Zh AJuA== MIME-Version: 1.0 X-Received: by 10.49.98.196 with SMTP id ek4mr20368895qeb.8.1374288902439; Fri, 19 Jul 2013 19:55:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Fri, 19 Jul 2013 19:55:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jul 2013 19:55:02 -0700 X-Google-Sender-Auth: GC_4_BiHAE9XX_fM4lRD2dDmnJs Message-ID: Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection From: Adrian Chadd To: Outback Dingo Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 02:55:03 -0000 It's always supported packet injection for ath(4), in ahdemo. It's just fiddling and easily broken. It also absolutely doesn't work for 11n traffic. However, I've never, ever tested it so I can't say whether it's currently _functional_. :-P -adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 11:27:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4FA8D87B; Sat, 20 Jul 2013 11:27:24 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id 0F01DE0E; Sat, 20 Jul 2013 11:27:23 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 2A6086A6003; Sat, 20 Jul 2013 13:27:22 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id r6KBRLVY017018; Sat, 20 Jul 2013 13:27:21 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id r6KBRLUA016162; Sat, 20 Jul 2013 13:27:21 +0200 (CEST) (envelope-from lars) Date: Sat, 20 Jul 2013 13:27:21 +0200 From: Lars Engels To: Adrian Chadd Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection Message-ID: <20130720112721.GG59101@e-new.0x20.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m0vRWufqUC70IDnR" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.4-RELEASE 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.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 11:27:24 -0000 --m0vRWufqUC70IDnR Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 19, 2013 at 07:55:02PM -0700, Adrian Chadd wrote: > It's always supported packet injection for ath(4), in ahdemo. It's > just fiddling and easily broken. It also absolutely doesn't work for > 11n traffic. >=20 > However, I've never, ever tested it so I can't say whether it's > currently _functional_. :-P >=20 What about this patch? https://forums.freebsd.org/showpost.php?p=3D64309&postcount=3D4 --m0vRWufqUC70IDnR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlHqdBkACgkQKc512sD3afjy2QCfcRrWnInsopJVwbQ0BAYf69ir +N8AnRkJIBE3jfAUZF+wHyqf09s+dFKt =egji -----END PGP SIGNATURE----- --m0vRWufqUC70IDnR-- From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 13:47:23 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 34B8F1BE; Sat, 20 Jul 2013 13:47:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id F05C925F; Sat, 20 Jul 2013 13:47:22 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id 13so332267iea.17 for ; Sat, 20 Jul 2013 06:47:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:to:cc:reply-to:subject:in-reply-to:x-mailer :mime-version:content-type; bh=Ej15j8yZfUwf9K9cGecVoEuCwTFiur3L/gjibMn9dSE=; b=xl83oLSy+w4OA+aV5UDOeoVPyKiMcn7pVUZ7dvWJb3pUPg3+7DFBrYZMxcFAFVbegb hDiFJPwfOkUpHeOVyhI7TRHpgGYM9TeVonQSihBoqINwQjusMn+3ukIff56RB2mK8otN aXZYkjVIOmkixOsyVnVEw8/ye1v5OmIFueuDj6R3O6kwoFLxmtOOqQhgG95t080EeJUq 5Lm+3x24t5sYMWZwLqeVDvLP1TwRl2Rg5/o3veFs+OvEUJHxzn63kRQqF2RuytOOmto/ clc1ht/k2p+PNVJ3aC6QzRCIes9LeDy7Ink+vcEZZQspan2Brf2b2Nl5AOcjz7MpoVQs 9hMQ== X-Received: by 10.42.132.134 with SMTP id d6mr13253646ict.50.1374328042715; Sat, 20 Jul 2013 06:47:22 -0700 (PDT) Received: from www.palm.com ([32.139.7.60]) by mx.google.com with ESMTPSA id n8sm44940291igk.7.2013.07.20.06.47.18 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 20 Jul 2013 06:47:21 -0700 (PDT) Message-ID: <51ea94e9.4827320a.603d.ffffb103@mx.google.com> Date: Sat, 20 Jul 2013 09:47:15 -0400 From: "Adrian Chadd" To: "Lars Engels" , "Adrian Chadd" , "Adrian Chadd" Subject: Re: Alfa AWUS036H WiFi - driver not supporting AHDEMO mode for injection In-Reply-To: <20130720112721.GG59101@e-new.0x20.net> X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd List-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, 20 Jul 2013 13:47:23 -0000 No. You're supposed to use ahdemo mode for injection, not monitor mode. Don't ask me why, I didn't write this stuff. :) -adrian Sent from my Palm Pre on AT&T On Jul 20, 2013 7:27 AM, Lars Engels <lars.engels@0x20.net> wrote:=20 On Fri, Jul 19, 2013 at 07:55:02PM -0700, Adrian Chadd wrote: > It's always supported packet injection for ath(4), in ahdemo. It's > just fiddling and easily broken. It also absolutely doesn't work for > 11n traffic. >=20 > However, I've never, ever tested it so I can't say whether it's > currently _functional_. :-P >=20 What about this patch? https://forums.freebsd.org/showpost.php?p=3D64309&postcount=3D4 From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 14:18:19 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 38A6762F; Sat, 20 Jul 2013 14:18:19 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id C42AB330; Sat, 20 Jul 2013 14:18:18 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id 48B86D1B; Sat, 20 Jul 2013 16:18:15 +0200 (CEST) From: "Cedric GROSS" To: , Subject: IWN Review Date: Sat, 20 Jul 2013 16:18:09 +0200 Message-ID: <006a01ce8553$f81d4290$e857c7b0$@info> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6FU/YKo4niZDhvQLOpAiYNZxJ+yw== Content-Language: fr Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 14:18:19 -0000 Hello dear all, I'm please to announce that I completed my work on IWN. My version available here https://github.com/KreizIT/FreeBSD-IWN include improvement issued by seanbruno (https://github.com/seanbruno/freebsd-iwl) but also mine to support centrino N 2230 NIC (it's my NIC) I set up a new parameters system which more sensitive. I port back all NIC parameters to this new system. I hope that I haven't do some mistake. So I'll be really please if Intel's NIC owner could check my work and let me know. By the way, if commiters would include my work, please do. Cheers Cedric From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 14:28:56 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 016C46F8; Sat, 20 Jul 2013 14:28:55 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 6A49A36C; Sat, 20 Jul 2013 14:28:55 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id z11so4615300wgg.34 for ; Sat, 20 Jul 2013 07:28:54 -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=M3VWY5KTrEuGIWo149WEH458Wm8rCbR1fMmcHCmTLu8=; b=wZ5FWDX0MtbrpM4VMgm58ZZ7ou4jU9PHqWZt/xfi9B+0UDq0ofn05EZ3Yx5TukqYLu 7tOkJ03j7kQL28YkvQQXx0ZGuLftiICzqI21AMnEC1ovc6QhiNmPKIEFSmzk2m+P9SWo N8dc0i3skFS83kg+F+xJZlvPmDM2mS7LecDLUT+Ooc5X2d1AG4FyLLsx+Kz4dUu/rv/H ZYrvbRchzyUrZDTww0z1LhrAhJve5k5AIbxjfaAJZ6uUjmEg0d/5vRDVzujrvoURtd9T +3PEHyfdEwxFfBO90JtH9lrAv+iVv0/2TAS0JQqjje5GFOU6cgOIwKfns/MgYUr6Y+0x Tffw== MIME-Version: 1.0 X-Received: by 10.194.234.100 with SMTP id ud4mr14887418wjc.44.1374330534276; Sat, 20 Jul 2013 07:28:54 -0700 (PDT) Received: by 10.194.240.132 with HTTP; Sat, 20 Jul 2013 07:28:54 -0700 (PDT) In-Reply-To: <006a01ce8553$f81d4290$e857c7b0$@info> References: <006a01ce8553$f81d4290$e857c7b0$@info> Date: Sat, 20 Jul 2013 18:28:54 +0400 Message-ID: Subject: Re: IWN Review From: Andrey Fesenko To: Cedric GROSS Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 14:28:56 -0000 On Sat, Jul 20, 2013 at 6:18 PM, Cedric GROSS wrote: > Hello dear all, > > > > I'm please to announce that I completed my work on IWN. > > > > My version available here https://github.com/KreizIT/FreeBSD-IWN include > improvement issued by seanbruno (https://github.com/seanbruno/freebsd-iwl) > but also mine to support centrino N 2230 NIC (it's my NIC) > > > > I set up a new parameters system which more sensitive. I port back all NIC > parameters to this new system. I hope that I haven't do some mistake. > > So I'll be really please if Intel's NIC owner could check my work and let me > know. > > > > By the way, if commiters would include my work, please do. > > > > Cheers > > Cedric > > > Great news, whether the driver supports n-mode? From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 15:30:35 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 04B18B2D; Sat, 20 Jul 2013 15:30:35 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id C57A1847; Sat, 20 Jul 2013 15:30:34 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id E8251D4C; Sat, 20 Jul 2013 17:30:33 +0200 (CEST) From: "Cedric GROSS" To: "'Andrey Fesenko'" References: <006a01ce8553$f81d4290$e857c7b0$@info> In-Reply-To: Subject: RE: IWN Review Date: Sat, 20 Jul 2013 17:30:28 +0200 Message-ID: <007e01ce855e$11ae78f0$350b6ad0$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6FVXo/IwTehlyERgmeyttsgnxnaAAB7QJw Content-Language: fr Cc: freebsd-wireless@freebsd.org, freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 15:30:35 -0000 > De : Andrey Fesenko [mailto:f0andrey@gmail.com] > Envoy=C3=A9 : samedi 20 juillet 2013 16:29 > =C3=80 : Cedric GROSS > Cc : freebsd-wireless@freebsd.org; freebsd-drivers@freebsd.org >=20 > On Sat, Jul 20, 2013 at 6:18 PM, Cedric GROSS wrote: > > Hello dear all, > > > > > > > > I'm please to announce that I completed my work on IWN. > > > > > > > > My version available here https://github.com/KreizIT/FreeBSD-IWN > > include improvement issued by seanbruno > > (https://github.com/seanbruno/freebsd-iwl) > > but also mine to support centrino N 2230 NIC (it's my NIC) > > > > > > > > I set up a new parameters system which more sensitive. I port back > all > > NIC parameters to this new system. I hope that I haven't do some > mistake. > > > > So I'll be really please if Intel's NIC owner could check my work = and > > let me know. > > > > > > > > By the way, if commiters would include my work, please do. > > > > > > > > Cheers > > > > Cedric > > > > > > >=20 > Great news, whether the driver supports n-mode? What do you mean by 'n-mode' ? 802.11n mode ?=20 If so, answer is yes : #dmesg |grep iwn0 iwn0: mem 0xf7c00000-0xf7c01fff irq 18 = at device 0.0 on pci4 #ifconfig wlan0 wlan0: flags=3D8843 metric 0 mtu = 1500 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11ng status: associated ssid FreeWifi channel 5 (2432 MHz 11g ht/20)=20 Cedric From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 15:42:42 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C8672D4E; Sat, 20 Jul 2013 15:42:42 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 3DDCE8E9; Sat, 20 Jul 2013 15:42:42 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id w57so4823515wes.29 for ; Sat, 20 Jul 2013 08:42:41 -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=bolT2whUQmRt1V6hlRMhRv59w5etEE6DaGAE2TVOLLk=; b=FrYh9RwNlMCVQdClfEfIUG3N7KANkE2DeCvjddU0qFDLeRtn07W2rMfJGt1Ew6+4xA W6fxxPCWATIdpb4mhyQecYuYwNSQ+JgH+01y+4H74nNquFB54pIvRgK1zYf1Cw5zGFaN LnPi616XfZd8lMIWxT/vkEh21aOk3W/WaqIZHWovvib3uWqL90c7pR/LHjvahOTWV6n2 /ZDXGI7VPZ09x1WuYpPCvh4Ki7r6Ohcwk+U+MQYd03Dh64XiRyhnFGzA2pFW1nzvCyxF dhRLoUBUqQ2keZYAm8Bj/JaJd42sYzRA97LyICS1R9fAoBnHm6pbINeZgDpLqcyhPTFn H2SA== MIME-Version: 1.0 X-Received: by 10.194.1.226 with SMTP id 2mr4314336wjp.91.1374334961314; Sat, 20 Jul 2013 08:42:41 -0700 (PDT) Received: by 10.194.240.132 with HTTP; Sat, 20 Jul 2013 08:42:41 -0700 (PDT) In-Reply-To: <007e01ce855e$11ae78f0$350b6ad0$@info> References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> Date: Sat, 20 Jul 2013 19:42:41 +0400 Message-ID: Subject: Re: IWN Review From: Andrey Fesenko To: Cedric GROSS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" , freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 15:42:42 -0000 On Sat, Jul 20, 2013 at 7:30 PM, Cedric GROSS wrote: >> De : Andrey Fesenko [mailto:f0andrey@gmail.com] >> Envoy=C3=A9 : samedi 20 juillet 2013 16:29 >> =C3=80 : Cedric GROSS >> Cc : freebsd-wireless@freebsd.org; freebsd-drivers@freebsd.org >> >> On Sat, Jul 20, 2013 at 6:18 PM, Cedric GROSS wrote: >> > Hello dear all, >> > >> > >> > >> > I'm please to announce that I completed my work on IWN. >> > >> > >> > >> > My version available here https://github.com/KreizIT/FreeBSD-IWN >> > include improvement issued by seanbruno >> > (https://github.com/seanbruno/freebsd-iwl) >> > but also mine to support centrino N 2230 NIC (it's my NIC) >> > >> > >> > >> > I set up a new parameters system which more sensitive. I port back >> all >> > NIC parameters to this new system. I hope that I haven't do some >> mistake. >> > >> > So I'll be really please if Intel's NIC owner could check my work and >> > let me know. >> > >> > >> > >> > By the way, if commiters would include my work, please do. >> > >> > >> > >> > Cheers >> > >> > Cedric >> > >> > >> > >> >> Great news, whether the driver supports n-mode? > > What do you mean by 'n-mode' ? 802.11n mode ? > If so, answer is yes : > > #dmesg |grep iwn0 > iwn0: mem 0xf7c00000-0xf7c01fff irq 18 a= t device 0.0 on pci4 > #ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11ng > status: associated > ssid FreeWifi channel 5 (2432 MHz 11g ht/20) > Cedric > Nice, ht/40 support to? Do you plan to support other cards Intel 6235 and supporting more than one range (5GHz)? I think whether to change AR9285 base card or not :) From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 15:51:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 85430EE9; Sat, 20 Jul 2013 15:51:08 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 48C1995D; Sat, 20 Jul 2013 15:51:07 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c43b:a26c:57b2:c3a3]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id B9C084AC58; Sat, 20 Jul 2013 19:51:00 +0400 (MSK) Date: Sat, 20 Jul 2013 19:50:52 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1408980007.20130720195052@serebryakov.spb.ru> To: Andrey Fesenko Subject: Re: IWN Review In-Reply-To: References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" , freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 15:51:08 -0000 Hello, Andrey. You wrote 20 =D0=B8=D1=8E=D0=BB=D1=8F 2013 =D0=B3., 19:42:41: AF> I think whether to change AR9285 base card or not :) Atheros is better. And, yes, Intel doesn't support host AP mode. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 15:54:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3E7FEF5A; Sat, 20 Jul 2013 15:54:15 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [178.32.219.166]) by mx1.freebsd.org (Postfix) with ESMTP id 08E9697A; Sat, 20 Jul 2013 15:54:14 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id B5C23D76; Sat, 20 Jul 2013 17:54:07 +0200 (CEST) From: "Cedric GROSS" To: "'Andrey Fesenko'" References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> In-Reply-To: Subject: RE: IWN Review Date: Sat, 20 Jul 2013 17:54:01 +0200 Message-ID: <008101ce8561$5c618560$15249020$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6FX8jxBI8+AjLWS32XwHaqeya5/QAAIsOQ Content-Language: fr Cc: freebsd-wireless@freebsd.org, freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 15:54:15 -0000 > De : Andrey Fesenko [mailto:f0andrey@gmail.com] [...] > >> > >> Great news, whether the driver supports n-mode? > > > > What do you mean by 'n-mode' ? 802.11n mode ? > > If so, answer is yes : > > > > #dmesg |grep iwn0 > > iwn0: mem 0xf7c00000-0xf7c01fff irq > > 18 at device 0.0 on pci4 #ifconfig wlan0 > > wlan0: flags=3D8843 metric 0 > mtu 1500 > > nd6 options=3D29 > > media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11ng > > status: associated > > ssid FreeWifi channel 5 (2432 MHz 11g ht/20) Cedric > > >=20 > Nice, ht/40 support to? I don't know. I'm too noob in iwn to say that. I let someone else = answer. > Do you plan to support other cards Intel 6235 and supporting more than > one range (5GHz)? 6235 is already supported by my version. I just wait for a friend to = test it but it should be ok. For other range, as for ht/40, I'm not enough expert for doing that, = sorry. >=20 > I think whether to change AR9285 base card or not :) -- Cedric From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 21:42:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D433620A; Sat, 20 Jul 2013 21:42:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 88345680; Sat, 20 Jul 2013 21:42:06 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id w7so3079930qeb.18 for ; Sat, 20 Jul 2013 14:42: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xVG+ex6RpXcgarpyb3COd4cGfZlYmhp5GaUvYlpjvgc=; b=PQdDPNfiSvnJoKFgxX8YHz2H4qcNGVDEBObYDSBgwW0u3Bt5dEJN9U5VbLNg2H6vS0 LzI6T9CpWJPOM8hVZD3qLmfyo/Wy7ZJeW+DO9BNHQYg+9q43I9JNnSvZ1Q4nPeQhBdPF /47lQeAUg7Nw4qNFhCqsDPJCUqDBiVJp6flP+nPQ42uwqmyb4L8+Iy8BUZ+hHggdj1/r j78Pcsc291G0KAwiAFpVb9tiLpicXeyhWK5uFc44fYFxR9xCsd58bKqJDpahUW8D01xY mNAeThhi99gmv31eXm13YxzPW7tvHZVuaUVIBAb0LfbV27kFFgWhjDA15lnAoNADPXwO 5bkA== MIME-Version: 1.0 X-Received: by 10.224.13.19 with SMTP id z19mr25599982qaz.12.1374356526077; Sat, 20 Jul 2013 14:42:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Sat, 20 Jul 2013 14:42:05 -0700 (PDT) In-Reply-To: <008101ce8561$5c618560$15249020$@info> References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> <008101ce8561$5c618560$15249020$@info> Date: Sat, 20 Jul 2013 14:42:05 -0700 X-Google-Sender-Auth: AW47QnMcuXJkkuqSJechET4XnPE Message-ID: Subject: Re: IWN Review From: Adrian Chadd To: Cedric GROSS Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 21:42:06 -0000 Hi! This is great news! Are you able to merge this into the iwn driver? Is it feasible? I'd rather not have two drivers in the tree for the same family of NICs. Thanks! -adrian On 20 July 2013 08:54, Cedric GROSS wrote: > > >> De : Andrey Fesenko [mailto:f0andrey@gmail.com] > [...] >> >> >> >> Great news, whether the driver supports n-mode? >> > >> > What do you mean by 'n-mode' ? 802.11n mode ? >> > If so, answer is yes : >> > >> > #dmesg |grep iwn0 >> > iwn0: mem 0xf7c00000-0xf7c01fff irq >> > 18 at device 0.0 on pci4 #ifconfig wlan0 >> > wlan0: flags=8843 metric 0 >> mtu 1500 >> > nd6 options=29 >> > media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11ng >> > status: associated >> > ssid FreeWifi channel 5 (2432 MHz 11g ht/20) Cedric >> > >> >> Nice, ht/40 support to? > > I don't know. I'm too noob in iwn to say that. I let someone else answer. >> Do you plan to support other cards Intel 6235 and supporting more than >> one range (5GHz)? > 6235 is already supported by my version. I just wait for a friend to test it but it should be ok. > > For other range, as for ht/40, I'm not enough expert for doing that, sorry. > >> >> I think whether to change AR9285 base card or not :) > -- > Cedric > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 22:53:11 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 74302ED7; Sat, 20 Jul 2013 22:53:11 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [178.32.219.166]) by mx1.freebsd.org (Postfix) with ESMTP id 3E1BD8DC; Sat, 20 Jul 2013 22:53:10 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id 83C2BDB3; Sun, 21 Jul 2013 00:53:09 +0200 (CEST) From: "Cedric GROSS" To: "'Adrian Chadd'" References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> <008101ce8561$5c618560$15249020$@info> In-Reply-To: Subject: RE: IWN Review Date: Sun, 21 Jul 2013 00:53:02 +0200 Message-ID: <000001ce859b$e50b9650$af22c2f0$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6Fkf9IGHHlaaQuTWWmomC81NgLkgACX3iQ Content-Language: fr Cc: freebsd-wireless@freebsd.org, freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 22:53:11 -0000 > De=A0: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] De la = part de Adrian Chadd > Envoy=E9=A0: samedi 20 juillet 2013 23:42 >=20 > Hi! >=20 > This is great news! >=20 > Are you able to merge this into the iwn driver? Is it feasible? I'd > rather not have two drivers in the tree for the same family of NICs. It's already IWN. But may be do you prefer a diff ? Cedric >=20 > Thanks! >=20 >=20 >=20 > -adrian >=20 From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 22:54:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D0B7AF25; Sat, 20 Jul 2013 22:54:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) by mx1.freebsd.org (Postfix) with ESMTP id 709958EA; Sat, 20 Jul 2013 22:54:39 +0000 (UTC) Received: by mail-qe0-f48.google.com with SMTP id 2so3088725qea.35 for ; Sat, 20 Jul 2013 15:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=eamopEPbEX9WkZUERYJJh+eGX7NZiiMOvKem6svseCg=; b=DM14j4mSuC/txJfBJIiu6skG3vXh1SBAza9YtwbCHG+gI84QOtmI4bxpIMQ4oqnY1q ohxmhnq/Vf8dkMxa24QgC32GJnTvDN8vZr/kdI+oFxmFmkGcmMi45hqtRhKCbqYhRbin fmS5Me7Ncu8ZeIjcqGODTJQ0tB0IZbD6DYVxZEjTi8sBnJ/NLA3CbbJeEOJE9CZIHEDy sRZpKShAbwhboBkOpTgt1lhJRZebaasq44ipkYjpOEp79wnzhf8XZEEzj0BvlnQ0QDIA vAeYUXt9NAYK+6+WT3gxqG3VsKGF9yWB52XLF+lFMcMZq7A/AxsILmIo4gNYUj+ISiPu ng0A== MIME-Version: 1.0 X-Received: by 10.224.223.202 with SMTP id il10mr13154273qab.87.1374360878894; Sat, 20 Jul 2013 15:54:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Sat, 20 Jul 2013 15:54:38 -0700 (PDT) In-Reply-To: <000001ce859b$e50b9650$af22c2f0$@info> References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> <008101ce8561$5c618560$15249020$@info> <000001ce859b$e50b9650$af22c2f0$@info> Date: Sat, 20 Jul 2013 15:54:38 -0700 X-Google-Sender-Auth: 2HcPsTGxusjbk6if5uNZ9VDtoZw Message-ID: Subject: Re: IWN Review From: Adrian Chadd To: Cedric GROSS Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" , "freebsd-drivers@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 22:54:40 -0000 yup! against -HEAD would be great! -adrian On Saturday, July 20, 2013, Cedric GROSS wrote: > > De : adrian.chadd@gmail.com [mailto: > adrian.chadd@gmail.com ] De la part de > Adrian Chadd > > Envoy=E9 : samedi 20 juillet 2013 23:42 > > > > Hi! > > > > This is great news! > > > > Are you able to merge this into the iwn driver? Is it feasible? I'd > > rather not have two drivers in the tree for the same family of NICs. > > It's already IWN. But may be do you prefer a diff ? > > Cedric > > > > > Thanks! > > > > > > > > -adrian > > > > From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 20 23:43:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 831BE321; Sat, 20 Jul 2013 23:43:06 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id E7E0B9FD; Sat, 20 Jul 2013 23:43:05 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id 1642BDD9; Sun, 21 Jul 2013 01:43:04 +0200 (CEST) From: "Cedric GROSS" To: "'Adrian Chadd'" References: <006a01ce8553$f81d4290$e857c7b0$@info> <007e01ce855e$11ae78f0$350b6ad0$@info> <008101ce8561$5c618560$15249020$@info> <000001ce859b$e50b9650$af22c2f0$@info> In-Reply-To: Subject: RE: IWN Review Date: Sun, 21 Jul 2013 01:42:57 +0200 Message-ID: <001901ce85a2$de9b29f0$9bd17dd0$@info> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6FnCFG3jIs8N9aSoeU/fEiTtTz4gABpCrA Content-Language: fr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, freebsd-drivers@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 23:43:06 -0000 Diff sent to you Adrian. =20 De : adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] De la part = de Adrian Chadd Envoy=E9 : dimanche 21 juillet 2013 00:55 =C0 : Cedric GROSS Cc : Adrian Chadd; freebsd-wireless@freebsd.org; = freebsd-drivers@freebsd.org Objet : Re: IWN Review =20 yup! against -HEAD would be great! =20 =20 =20 -adrian On Saturday, July 20, 2013, Cedric GROSS wrote: > De : adrian.chadd@gmail.com = [mailto:adrian.chadd@gmail.com ] De la part de Adrian Chadd > Envoy=E9 : samedi 20 juillet 2013 23:42 > > Hi! > > This is great news! > > Are you able to merge this into the iwn driver? Is it feasible? I'd > rather not have two drivers in the tree for the same family of NICs. It's already IWN. But may be do you prefer a diff ? Cedric > > Thanks! > > > > -adrian >