From owner-freebsd-wireless@FreeBSD.ORG Sun Jun 23 14:12:02 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 B30EDD4A; Sun, 23 Jun 2013 14:12:02 +0000 (UTC) (envelope-from gprspb@mail.ru) Received: from smtp20.mail.ru (smtp20.mail.ru [94.100.176.173]) by mx1.freebsd.org (Postfix) with ESMTP id CE0641E2F; Sun, 23 Jun 2013 14:12:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=m0PpQotrNGLdlLYgKHvQehgp8DEYNztLGR8LSjYuujA=; b=t030zUZOMzv0R9eTWIs1ce5Id9u9Qsc6GgA194sGyfJr6LwXyjoJV0P/81A/1BJ0ni5WHf49xw9/GjrGKks3s21p3hQlOM0oqR1Px3f+0s4SGkDloo+jgU1y5oVfwgl8b6bwsrtx3dyNxXW0w4PFgzALssI4l3zuTyDX8CQtZUQ=; Received: from [93.185.182.46] (port=37492 helo=gpr.nnz-home.ru) by smtp20.mail.ru with esmtpa (envelope-from ) id 1Uql1F-00007n-Dl; Sun, 23 Jun 2013 18:11:53 +0400 Received: from gpr by gpr.nnz-home.ru with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Uql15-0000Fk-2l; Sun, 23 Jun 2013 18:11:43 +0400 Date: Sun, 23 Jun 2013 18:11:42 +0400 From: Gennady Proskurin To: Adrian Chadd Subject: Re: svn commit: r251741 - head/sys/contrib/dev/ath/ath_hal/ar9300 Message-ID: <20130623141142.GA965@gpr.nnz-home.ru> References: <20130619082855.GC985@gpr.nnz-home.ru> <20130619091310.GD985@gpr.nnz-home.ru> <20130620072418.GA987@gpr.nnz-home.ru> <20130620144834.GA913@gpr.nnz-home.ru> <20130621103812.GA3683@gpr.nnz-home.ru> <20130622154745.GA1407@gpr.nnz-home.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam: Not detected X-Mras: Ok Cc: Gennady Proskurin , 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, 23 Jun 2013 14:12:02 -0000 It works with any channel except 1 (I tested 1-6). channel 1 - "stuck beacon" and so on, all the symptoms I wrote about channel 2-6 - no "stuck beacon" messages, and it just works I don't understand what the channels are, I think it somehow connected with frequency. I just googled about this workaround and it works for me. On Sat, Jun 22, 2013 at 09:58:44AM -0700, Adrian Chadd wrote: > Interesting. So it was finding other channels and those were the problem? > > If you set a channel to something else (say, 4), what happens? > > > > > adrian > > On 22 June 2013 08:47, Gennady Proskurin wrote: > > I added "channel 6" to wlan ifconfig, and now all works (with fresh HEAD r252061) > > > > On Fri, Jun 21, 2013 at 02:38:12PM +0400, Gennady Proskurin wrote: > >> I recompiled and rebooted kernel and all modules to r250662 (last revision > >> before r250665). This is remote host, I cannot tell whether wifi actually works > >> or not, but I see no changes - high system load (~30%) and a lot of "stuck > >> beacon" messages. I think it doesn't work. > >> > >> I do not understand what you mean by trying r250665, I tried r251541 (which > >> includes r250665 changes), it does not work. > >> > >> On Thu, Jun 20, 2013 at 12:33:28PM -0700, Adrian Chadd wrote: > >> > Well, try rebooting with -HEAD a few times. > >> > > >> > Also, try r250665 (my first set of patches that enabled better ps-poll > >> > support) and r250664 (the revision beforehand.) See if you can > >> > reproduce the issues with that. > >> > > >> > I have a sneaking suspicion that doing more aggressive power save > >> > handling in hostap mode is causing issues but I haven't yet narrowed > >> > it down. > >> > > >> > > >> > > >> > adrian > >> > > >> > > >> > On 20 June 2013 07:48, Gennady Proskurin wrote: > >> > > I reverted kernel and world to r251541 and card does not work. So, bug is not > >> > > caused by source changes. > >> > > > >> > > On Thu, Jun 20, 2013 at 11:24:18AM +0400, Gennady Proskurin wrote: > >> > >> I have strange results. Finally, I reverted kernel and all the modules to old > >> > >> "working" revision r251541 (just renamed kernel.old to kernel), and my ath card > >> > >> does not work. All userspace world is from r251945. > >> > >> I see the same errors "ath0: stuck beacon; resetting (bmiss count 4)". > >> > >> > >> > >> I doubt it has something to do with changes after r251541, may be my card has > >> > >> some problems. I remember, a few months ago, when I installed it, it had the > >> > >> same problems, which were magically solved after few reboots and upgrades, then > >> > >> my card worked without problems for a few months, surviving weekly upgrades and > >> > >> reboots. > >> > >> > >> > >> Now I recompiling world back to r251541 to be completely sure that it has > >> > >> nothing to do with source changes. > >> > >> > >> > >> CPU usage from top follows: > >> > >> CPU: 0.0% user, 0.0% nice, 35.4% system, 0.0% interrupt, 64.6% idle > >> > >> 0 root -92 0 0K 2496K - 3:11 34.28% kernel{ath0 taskq} > >> > >> 11 root -92 - 0K 288K WAIT 0:00 0.00% intr{irq19: ath0} > >> > >> 0 root -92 0 0K 2496K - 0:00 0.00% kernel{ath0 net80211 ta} > >> > >> > >> > >> As you see almost all system load is ath0 taskq > >> > >> > >> > >> May be my card is somewhat "broken", or require some magic in driver, but > >> > >> sometimes it can work reliably, and I'll be glad to participate in debugging > >> > >> this case. > >> > >> > >> > >> On Wed, Jun 19, 2013 at 08:49:10AM -0700, Adrian Chadd wrote: > >> > >> > Hi! > >> > >> > > >> > >> > I'd rather you recompile the whole kernel, in case it's actually a > >> > >> > problem elsewhere. > >> > >> > > >> > >> > Thanks, > >> > >> > > >> > >> > > >> > >> > > >> > >> > adrian > >> > >> > > >> > >> > On 19 June 2013 02:13, Gennady Proskurin wrote: > >> > >> > > I filled pr kern/179709 > >> > >> > > > >> > >> > > I'll try to bisect repo in r251541-r251945 interval and try different revisions > >> > >> > > to narrow down a problem when I have time. I hope, tomorrow I'll have some > >> > >> > > results. > >> > >> > > > >> > >> > > Is it sufficient to just recompile kernel, if_ath and if_ath_pci modules? > >> > >> > > > >> > >> > > % kldstat | egrep 'ath|wlan' > >> > >> > > 11 1 0xffffffff80e12000 d07 if_ath_pci.ko > >> > >> > > 12 6 0xffffffff80e13000 37059 wlan.ko > >> > >> > > 13 1 0xffffffff80e4b000 c9b85 if_ath.ko > >> > >> > > 16 1 0xffffffff80f3c000 23b wlan_xauth.ko > >> > >> > > 17 1 0xffffffff80f3d000 e7b wlan_wep.ko > >> > >> > > 18 1 0xffffffff80f3e000 1def wlan_tkip.ko > >> > >> > > 19 1 0xffffffff80f40000 4b8d wlan_ccmp.ko > >> > >> > > > >> > >> > > On Wed, Jun 19, 2013 at 01:35:58AM -0700, Adrian Chadd wrote: > >> > >> > >> Hi, > >> > >> > >> > >> > >> > >> 251541 is recent, AND it's _after_ the power save queue changes. > >> > >> > >> > >> > >> > >> The only revisions that are changes to sys/dev/ath are: > >> > >> > >> > >> > >> > >> r251606 > >> > >> > >> r251643 > >> > >> > >> r251655 > >> > >> > >> r251656 > >> > >> > >> r251730 > >> > >> > >> r251742 > >> > >> > >> > >> > >> > >> > >> > >> > >> .. and these are all bluetooth coexistence changes for _another_ chip. > >> > >> > >> > >> > >> > >> Can you try these and see which work and which don't? > >> > >> > >> > >> > >> > >> The other thing to keep in mind - it may be an issue somewhere else in > >> > >> > >> the kernel rather than a sys/dev/ath driver issue. But let's narrow it > >> > >> > >> down to the above list first, then we can try narrowing it down > >> > >> > >> further. > >> > >> > >> > >> > >> > >> Thanks! > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> adrian > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> On 19 June 2013 01:28, Gennady Proskurin wrote: > >> > >> > >> > Previous working revision was r251541 > >> > >> > >> > So: > >> > >> > >> > r251541 works > >> > >> > >> > r251945 does not work > >> > >> > >> > > >> > >> > >> > On Wed, Jun 19, 2013 at 01:07:04AM -0700, Adrian Chadd wrote: > >> > >> > >> >> Hi! > >> > >> > >> >> > >> > >> > >> >> Great! It looks like you definitely hit this more often than i do! > >> > >> > >> >> > >> > >> > >> >> Can you tell me which revision @ 8 june you were at? or go back to > >> > >> > >> >> something on 8-june, verify it works, then tell me which revision? > >> > >> > >> >> > >> > >> > >> >> Let's fix this ASAP! > >> > >> > >> >> > >> > >> > >> >> Thanks! > >> > >> > >> >> > >> > >> > >> >> > >> > >> > >> >> > >> > >> > >> >> adrian > >> > >> > >> >> > >> > >> > >> >> On 19 June 2013 00:28, Gennady Proskurin wrote: > >> > >> > >> >> > Replying to random ath commit. > >> > >> > >> >> > > >> > >> > >> >> > Now my ath wireless device does not work. It was broken some time after 8 Jun > >> > >> > >> >> > (after my last update at 8 Jun it worked, now after today's update to r251945 > >> > >> > >> >> > it does not). > >> > >> > >> >> > > >> > >> > >> >> > It spams log and console with messages: > >> > >> > >> >> > > >> > >> > >> >> > Jun 19 10:04:27 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:04:58 gpr last message repeated 101 times > >> > >> > >> >> > Jun 19 10:05:42 gpr last message repeated 143 times > >> > >> > >> >> > Jun 19 10:05:42 gpr kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing > >> > >> > >> >> > Jun 19 10:05:42 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:05:47 gpr last message repeated 11 times > >> > >> > >> >> > Jun 19 10:05:47 gpr kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing > >> > >> > >> >> > Jun 19 10:05:47 gpr kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing > >> > >> > >> >> > Jun 19 10:05:47 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:05:53 gpr last message repeated 19 times > >> > >> > >> >> > ... > >> > >> > >> >> > Jun 19 10:06:20 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:06:21 gpr last message repeated 4 times > >> > >> > >> >> > Jun 19 10:06:22 gpr kernel: ath0: ath_tx_should_swq_frame: f0:4f:7c:fc:b3:22: Node is asleep; sending mgmt (type=0, subtype=176) > >> > >> > >> >> > Jun 19 10:06:22 gpr kernel: ath0: ath_tx_should_swq_frame: f0:4f:7c:fc:b3:22: Node is asleep; sending mgmt (type=0, subtype=176) > >> > >> > >> >> > Jun 19 10:06:22 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:06:23 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:06:23 gpr kernel: ath0: ath_tx_node_wakeup: an=0xffffff8002322000: node was already awake > >> > >> > >> >> > Jun 19 10:06:24 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > Jun 19 10:06:25 gpr kernel: ath0: stuck beacon; resetting (bmiss count 4) > >> > >> > >> >> > > >> > >> > >> >> > > >> > >> > >> >> > # uname -a > >> > >> > >> >> > FreeBSD gpr.nnz-home.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r251945+1330981: > >> > >> > >> >> > Wed Jun 19 08:09:32 MSK 2013 > >> > >> > >> >> > gpr@gpr.nnz-home.ru:/usr/obj/usr/src/freebsd-head/sys/GPR amd64 > >> > >> > >> >> > > >> > >> > >> >> > Boot log device info: > >> > >> > >> >> > Jun 19 10:04:18 gpr kernel: ath0: mem 0xfbdf0000-0xfbdfffff irq 19 at device 10.0 on pci0 > >> > >> > >> >> > Jun 19 10:04:18 gpr kernel: ath0: AR2413 mac 7.9 RF2413 phy 4.5 > >> > >> > >> >> > Jun 19 10:04:18 gpr kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0056 > >> > >> > >> >> > > >> > >> > >> >> > # pciconf -lv > >> > >> > >> >> > ath0@pci0:0:10:0: class=0x020000 card=0x2051168c chip=0x0013168c rev=0x01 hdr=0x00 > >> > >> > >> >> > vendor = 'Atheros Communications Inc.' > >> > >> > >> >> > device = 'AR5212/AR5213 Wireless Network Adapter' > >> > >> > >> >> > class = network > >> > >> > >> >> > subclass = ethernet > >> > >> > >> >> > > >> > >> > >> >> > # rc.conf > >> > >> > >> >> > wlans_ath0="wlan0" > >> > >> > >> >> > create_args_wlan0="wlandev ath0 wlanmode hostap" > >> > >> > >> >> > ifconfig_wlan0="10.X.X.X/24" > >> > >> > >> >> > hostapd_enable="YES" > >> > >> > >> >> > > >> > >> > >> >> > I can do additional tests or submit more info, if necessary. > >> > >> > >> >> > > >> > >> > >> >> > On Fri, Jun 14, 2013 at 08:15:28AM +0000, Adrian Chadd wrote: > >> > >> > >> >> >> Author: adrian > >> > >> > >> >> >> Date: Fri Jun 14 08:15:28 2013 > >> > >> > >> >> >> New Revision: 251741 > >> > >> > >> >> >> URL: http://svnweb.freebsd.org/changeset/base/251741 > >> > >> > >> >> >> > >> > >> > >> >> >> Log: > >> > >> > >> >> >> The AR9300 HAL uses this config to program AR_PHY_SWITCH_COM_2 on AR9485 > >> > >> > >> >> >> NICs which have bluetooth coexistence enabled. > >> > >> > >> >> >> > >> > >> > >> >> >> The WB225 NIC has the common antenna switch configuration set to 0x0 which > >> > >> > >> >> >> disables all external switch bit setting. This obviously won't work when > >> > >> > >> >> >> doing coexistence. > >> > >> > >> >> >> > >> > >> > >> >> >> This value is a magic value from the windows .inf files. It _looks_ right > >> > >> > >> >> >> but I haven't yet verified it - unfortunately my AR9285+AR3012 BT combo > >> > >> > >> >> >> has an earlier BT device which doesn't actually _have_ firmware on it. > >> > >> > >> >> >> So I have to fix ath3kfw to handle loading in firmware into the newer > >> > >> > >> >> >> NICs before I can finish testing this. > >> > >> > >> >> >> > >> > >> > >> >> >> This may not hold true for CUS198, which is another custom AR9485 board. > >> > >> > >> >> >> > >> > >> > >> >> >> Modified: > >> > >> > >> >> >> head/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_freebsd.c > >> > >> > >> >> >> > >> > >> > >> >> >> Modified: head/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_freebsd.c > >> > >> > >> >> >> ============================================================================== > >> > >> > >> >> >> --- head/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_freebsd.c Fri Jun 14 08:13:21 2013 (r251740) > >> > >> > >> >> >> +++ head/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_freebsd.c Fri Jun 14 08:15:28 2013 (r251741) > >> > >> > >> >> >> @@ -249,6 +249,9 @@ ar9300_attach_freebsd_ops(struct ath_hal > >> > >> > >> >> >> /* LNA diversity functions */ > >> > >> > >> >> >> ah->ah_divLnaConfGet = ar9300_ant_div_comb_get_config; > >> > >> > >> >> >> ah->ah_divLnaConfSet = ar9300_ant_div_comb_set_config; > >> > >> > >> >> >> + > >> > >> > >> >> >> + /* Setup HAL configuration defaults */ > >> > >> > >> >> >> + ah->ah_config.ath_hal_ant_ctrl_comm2g_switch_enable = 0x000bbb88; > >> > >> > >> >> >> } > >> > >> > >> >> >> > >> > >> > >> >> >> HAL_BOOL > >> > >> > >> >> >> _______________________________________________ > >> > >> > >> >> >> svn-src-head@freebsd.org mailing list > >> > >> > >> >> >> http://lists.freebsd.org/mailman/listinfo/svn-src-head > >> > >> > >> >> >> To unsubscribe, send any mail to "svn-src-head-unsubscribe@freebsd.org" > >> > >> > >> >> >> > >> > >> > >> >> > >> > >> > >> > >> > >> > > >> > >> > >> > > >> > From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 08:10:02 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9AA4F386 for ; Mon, 24 Jun 2013 08:10:02 +0000 (UTC) (envelope-from gnats@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 8CE9715D9 for ; Mon, 24 Jun 2013 08:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5O8A1uX062290 for ; Mon, 24 Jun 2013 08:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5O8A1vh062289; Mon, 24 Jun 2013 08:10:01 GMT (envelope-from gnats) Date: Mon, 24 Jun 2013 08:10:01 GMT Message-Id: <201306240810.r5O8A1vh062289@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Anton Shterenlikht Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Anton Shterenlikht List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jun 2013 08:10:02 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: Anton Shterenlikht To: bug-followup@freebsd.org Cc: Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Mon, 24 Jun 2013 09:07:42 +0100 (BST) This problem still persists in r252033: iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DA000018B8 time = 200035 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=2 queued=1 tx ring 4: qid=4 cur=67 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=5 NVRM: GPU at 0000:01:00: GPU-a1a1491c-c546-eda9-3b1f-54ec998e9441 ifa_del_loopback_route: deletion failed: 48 wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: link state changed to UP wlan0: link state changed to DOWN iwn0: device timeout iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DA000018B8 time = 200035 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=2 queued=1 tx ring 4: qid=4 cur=67 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=22 ifa_del_loopback_route: deletion failed: 48 wlan0: Ethernet address: 00:21:5c:50:68:c3 iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000202030000 branch link = 0x00005CEE000004C2 interrupt link = 0x000006DE00007386 time = 220366 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=4 queued=0 tx ring 4: qid=4 cur=97 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=42 ifa_del_loopback_route: deletion failed: 48 wlan0: Ethernet address: 00:21:5c:50:68:c3 etc. From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 11:06: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 8F28217B for ; Mon, 24 Jun 2013 11:06:56 +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 7DE271DE1 for ; Mon, 24 Jun 2013 11:06:56 +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 r5OB6uAt001190 for ; Mon, 24 Jun 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5OB6uQ1001188 for freebsd-wireless@FreeBSD.org; Mon, 24 Jun 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Jun 2013 11:06:56 GMT Message-Id: <201306241106.r5OB6uQ1001188@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, 24 Jun 2013 11:06:56 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/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/175870 wireless [iwn] /etc/rc.d/netif restart cause system crash 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 173 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 16:57:44 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 9181F39D for ; Mon, 24 Jun 2013 16:57:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) by mx1.freebsd.org (Postfix) with ESMTP id 54A4C124E for ; Mon, 24 Jun 2013 16:57:44 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id n1so6458214qcx.36 for ; Mon, 24 Jun 2013 09:57:43 -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=FnL8GNBH3lVdF8xcvyOTLLIDVkVRP6wV5fK0yPePMe8=; b=o8Wyu7MYihNVSGa52aHkNpbW8Srvqng32ffMoS/C40mEGPu9eIe1SY+598HI2nAQZm xDzvAMIlt8XeLuM6+BwyKaXJm/IlrhlUgVLBZ1WUYfajFdVybzM33PR3dQqjlXN5xCwm 6hsAeqCawRvulrQzfSDTmau34LOXgfIdPpuVTCA383fQLNy+xGW2izgc2kxjRbcTi4bq ZNspoM27z43JTPdU2cUEzgpjUhtrLBdug+MyZhcRmRJ8hLosldvoVaZgq91JgLAWiIIf xySheHB3O4+gnto2KVrqUA0I9/DR0OBg52raeHjwjC4gISouq189hJtKHHPfHUvhhXb4 Sp8w== MIME-Version: 1.0 X-Received: by 10.49.107.201 with SMTP id he9mr19610352qeb.74.1372093063897; Mon, 24 Jun 2013 09:57:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Mon, 24 Jun 2013 09:57:43 -0700 (PDT) In-Reply-To: <20130623141142.GA965@gpr.nnz-home.ru> References: <20130619082855.GC985@gpr.nnz-home.ru> <20130619091310.GD985@gpr.nnz-home.ru> <20130620072418.GA987@gpr.nnz-home.ru> <20130620144834.GA913@gpr.nnz-home.ru> <20130621103812.GA3683@gpr.nnz-home.ru> <20130622154745.GA1407@gpr.nnz-home.ru> <20130623141142.GA965@gpr.nnz-home.ru> Date: Mon, 24 Jun 2013 09:57:43 -0700 X-Google-Sender-Auth: Xjy-ipRrOLFE5vrySqx7ubkgptE Message-ID: Subject: Re: svn commit: r251741 - head/sys/contrib/dev/ath/ath_hal/ar9300 From: Adrian Chadd To: Gennady Proskurin 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: Mon, 24 Jun 2013 16:57:44 -0000 On 23 June 2013 07:11, Gennady Proskurin wrote: > It works with any channel except 1 (I tested 1-6). > channel 1 - "stuck beacon" and so on, all the symptoms I wrote about > channel 2-6 - no "stuck beacon" messages, and it just works > > I don't understand what the channels are, I think it somehow connected with > frequency. I just googled about this workaround and it works for me. Channels are just a representation of the frequency. Anyway - would you mind trying an earlier kernel (the one I mentioned previously - before the pspoll changes) on channel 1 and see if it reacts as badly? Thanks! adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 17:21: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 ACA49AB9; Mon, 24 Jun 2013 17:21:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 5D4E11338; Mon, 24 Jun 2013 17:21:06 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id j8so2416086qah.3 for ; Mon, 24 Jun 2013 10:21:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PElbK9rmZB1sEnuTijV8wQ2UMEyRpffbhmN5BzQSchE=; b=nTpFDyMeazSLPJ+bdIh4VMP4s0n478tdTM2koTaZ3h078kLeCugUKc0Ba33TZubM1M ntecuYNnH2CB82q5DVazbQqFzbs704ggNTDthU3T/7wSOMP8KY+7EFSsKYg6g5EeeEm9 A//FBo3BXEBvR1CAxfdf+r3ua0pqZ9itGX28IY7zkhGpsqw+EPVvF5s+byg8evDcqKMC GheGCKVklzwHHmfX84iIYO74IRGpv3BpX+H5O+B5YGYRaydQZqWGBKWNg6Ax/jhlO+c/ /mlKDldPi/xe6qy3WIhTkiYOv6kGfobZMfvYuLIi0umL91hq0RnuOyxDbkc6EXX/JM5e AKcQ== MIME-Version: 1.0 X-Received: by 10.229.204.131 with SMTP id fm3mr4522406qcb.15.1372094465785; Mon, 24 Jun 2013 10:21:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Mon, 24 Jun 2013 10:21:05 -0700 (PDT) In-Reply-To: References: Date: Mon, 24 Jun 2013 10:21:05 -0700 X-Google-Sender-Auth: RbrKpWix3koI2MHJAchviyixSRI 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 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, 24 Jun 2013 17:21:06 -0000 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" >>>>> > >>>>> > >>>> >>>> >>> >> > From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 18:10:01 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C7B6460E for ; Mon, 24 Jun 2013 18:10:01 +0000 (UTC) (envelope-from gnats@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 9FC4016FD for ; Mon, 24 Jun 2013 18:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5OIA1no084885 for ; Mon, 24 Jun 2013 18:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5OIA1jD084884; Mon, 24 Jun 2013 18:10:01 GMT (envelope-from gnats) Date: Mon, 24 Jun 2013 18:10:01 GMT Message-Id: <201306241810.r5OIA1jD084884@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: hiren panchasara Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hiren panchasara List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jun 2013 18:10:01 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: hiren panchasara To: bug-followup@FreeBSD.org, mexas@bristol.ac.uk Cc: Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Mon, 24 Jun 2013 11:09:18 -0700 Assuming you have 4965 chipset, this seems to be some weird firmware error. I see many users (including linux) reporting similar issues but could not find any definitive solution. At most you can try getting the latest firmware for your chipset and try it out. Probably from http://wireless.kernel.org/en/users/Drivers/iwlegacy Good luck, Hiren From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 20:01:37 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 A76AF640; Mon, 24 Jun 2013 20:01:37 +0000 (UTC) (envelope-from l.yotov@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by mx1.freebsd.org (Postfix) with ESMTP id 44A9F1CD1; Mon, 24 Jun 2013 20:01:37 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id hu16so35803qab.15 for ; Mon, 24 Jun 2013 13:01:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gSJwCmIephgnIyKacWZ0jCwln4QMS6y0KrBY12ahTEc=; b=XUpElSvlLc0sxhr10sVtUe4VAemCTTc8yk5FzIUwnmUcdXuIpALHwMYmyGgjc/IMNo RjxXNmIt3RPpAuRo+4Q8/4KbXU+X58XW41j6ODqnx7OCptuLqgk5GIFOdXLkpyrY0Oqa /Wjaz2HuSO91TNIke7d1nCLnoJsTRV9BAmdHRotXmcG7MO3qKvPvUp+S/zL4S0zao2oE UUIQo8d1JY1hy/trKUyQjda5sIZ2dxCLBalUOHzdccmxJRXsHIRzs8MOn/Aah4GFpkvb KgaxHKcSMdKoy4o5jLlEvREvX79ihwYIr4ONkL283MI/UedOP5HB/R+fSm6n3CUQ57/L 3RiA== MIME-Version: 1.0 X-Received: by 10.224.148.19 with SMTP id n19mr28369806qav.66.1372104096150; Mon, 24 Jun 2013 13:01:36 -0700 (PDT) Received: by 10.224.98.147 with HTTP; Mon, 24 Jun 2013 13:01:36 -0700 (PDT) In-Reply-To: References: Date: Mon, 24 Jun 2013 23:01:36 +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, 24 Jun 2013 20:01:37 -0000 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" > >>>>> > > >>>>> > > >>>> > >>>> > >>> > >> > > > From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 24 20:39: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 E1ABDB06; Mon, 24 Jun 2013 20:39:06 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 665251EB9; Mon, 24 Jun 2013 20:39:06 +0000 (UTC) Received: from vincemacbook.unsane.co.uk (vincemacbook.unsane.co.uk [10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.7/8.14.6) with ESMTP id r5OKd3sM007083 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 24 Jun 2013 21:39:04 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <51C8AE67.7040801@unsane.co.uk> Date: Mon, 24 Jun 2013 21:39:03 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Lyubomir Yotov Subject: Re: Thinkpad T60 with Atheros working only after restart from Windows References: In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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, 24 Jun 2013 20:39:07 -0000 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 Jun 25 06:46:39 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 AC487907; Tue, 25 Jun 2013 06:46:39 +0000 (UTC) (envelope-from gprspb@mail.ru) Received: from smtp28.mail.ru (smtp28.mail.ru [94.100.176.181]) by mx1.freebsd.org (Postfix) with ESMTP id 27B5216D4; Tue, 25 Jun 2013 06:46:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=RsXkNMkrE1RPt+AvYWZf4OHZinBqzdxWfVLn99kPbFw=; b=F8TC9cEqhuaqmsmtGWYxk2o1SCY3MG4i5zzXIP2Tyfs7oKe57CFXPpEisnqydz/f1poZvtbxa6DNaro6F8/gYRzrj9NilCSc+R6z5v3tYCrF0I4ib842FfX0gyfGA9GVNFSHBrjhL5yV78QP+94NoEbI5e8gNSo010WOCsmSuVw=; Received: from [93.185.182.46] (port=27732 helo=gpr.nnz-home.ru) by smtp28.mail.ru with esmtpa (envelope-from ) id 1UrN1M-00031E-BH; Tue, 25 Jun 2013 10:46:32 +0400 Received: from gpr by gpr.nnz-home.ru with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UrN1F-0000uQ-QS; Tue, 25 Jun 2013 10:46:25 +0400 Date: Tue, 25 Jun 2013 10:46:25 +0400 From: Gennady Proskurin To: Adrian Chadd Subject: Re: svn commit: r251741 - head/sys/contrib/dev/ath/ath_hal/ar9300 Message-ID: <20130625064625.GC1985@gpr.nnz-home.ru> References: <20130619091310.GD985@gpr.nnz-home.ru> <20130620072418.GA987@gpr.nnz-home.ru> <20130620144834.GA913@gpr.nnz-home.ru> <20130621103812.GA3683@gpr.nnz-home.ru> <20130622154745.GA1407@gpr.nnz-home.ru> <20130623141142.GA965@gpr.nnz-home.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam: Not detected X-Mras: Ok Cc: Gennady Proskurin , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 06:46:39 -0000 pspoll changes are in r250665, if I undersand correctly I tried r250662 withhout changing channel (1 by default), and it didn't work, I wrote about it in earlier messages. On Mon, Jun 24, 2013 at 09:57:43AM -0700, Adrian Chadd wrote: > On 23 June 2013 07:11, Gennady Proskurin wrote: > > It works with any channel except 1 (I tested 1-6). > > channel 1 - "stuck beacon" and so on, all the symptoms I wrote about > > channel 2-6 - no "stuck beacon" messages, and it just works > > > > I don't understand what the channels are, I think it somehow connected with > > frequency. I just googled about this workaround and it works for me. > > Channels are just a representation of the frequency. > > Anyway - would you mind trying an earlier kernel (the one I mentioned > previously - before the pspoll changes) on channel 1 and see if it > reacts as badly? > > Thanks! > > > > adrian > From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 25 11:50:02 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 577DF62E for ; Tue, 25 Jun 2013 11:50:02 +0000 (UTC) (envelope-from gnats@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 48BB31615 for ; Tue, 25 Jun 2013 11:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5PBo1cb050344 for ; Tue, 25 Jun 2013 11:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5PBo1L8050342; Tue, 25 Jun 2013 11:50:01 GMT (envelope-from gnats) Date: Tue, 25 Jun 2013 11:50:01 GMT Message-Id: <201306251150.r5PBo1L8050342@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Anton Shterenlikht Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Anton Shterenlikht List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 11:50:02 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: Anton Shterenlikht To: bug-followup@FreeBSD.org, hiren@FreeBSD.org, mexas@bristol.ac.uk Cc: Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Tue, 25 Jun 2013 12:48:16 +0100 (BST) From hiren.panchasara@gmail.com Mon Jun 24 19:31:55 2013 Assuming you have 4965 chipset, yes, I do: iwn0@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' class = network iwn0: mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 and I have: device iwn # Intel 4965/1000/5000/6000 wireless NICs. device iwn4965fw in the kernel config. this seems to be some weird firmware error. I see many users (including linux) reporting similar issues but could not find any definitive solution. At most you can try getting the latest firmware for your chipset and try it out. Probably from http://wireless.kernel.org/en/users/Drivers/iwlegacy # cat /usr/src/sys/modules/iwnfw/iwn4965/Makefile # $FreeBSD: head/sys/modules/iwnfw/iwn4965/Makefile 201209 2009-12-29 19:47:34Z rpaulo $ KMOD= iwn4965fw IMG= iwlwifi-4965-228.61.2.24 .include # According to your link, this is the latest version. However, there is a question mark (?) against it. I don't know what it means, perhaps that they are not sure if it works correctly. I wonder if an earlier version should be used instead? Thanks Anton From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 25 16:00:01 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CF71A977 for ; Tue, 25 Jun 2013 16:00:01 +0000 (UTC) (envelope-from gnats@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 C291E15E1 for ; Tue, 25 Jun 2013 16:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5PG01AG000460 for ; Tue, 25 Jun 2013 16:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5PG010l000459; Tue, 25 Jun 2013 16:00:01 GMT (envelope-from gnats) Date: Tue, 25 Jun 2013 16:00:01 GMT Message-Id: <201306251600.r5PG010l000459@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: hiren panchasara Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hiren panchasara List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 16:00:01 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: hiren panchasara To: mexas Cc: bug-followup@freebsd.org Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Tue, 25 Jun 2013 08:52:43 -0700 On Tue, Jun 25, 2013 at 4:48 AM, Anton Shterenlikht wrote: > From hiren.panchasara@gmail.com Mon Jun 24 19:31:55 2013 > > Assuming you have 4965 chipset, > > yes, I do: > > iwn0@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' > class = network > > iwn0: mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 > > and I have: > > device iwn # Intel 4965/1000/5000/6000 wireless NICs. > device iwn4965fw > > in the kernel config. > > this seems to be some weird firmware > error. I see many users (including linux) reporting similar issues but > could not find any definitive solution. > > At most you can try getting the latest firmware for your chipset and try it out. > Probably from http://wireless.kernel.org/en/users/Drivers/iwlegacy > > # cat /usr/src/sys/modules/iwnfw/iwn4965/Makefile > # $FreeBSD: head/sys/modules/iwnfw/iwn4965/Makefile 201209 2009-12-29 19:47:34Z rpaulo $ > > KMOD= iwn4965fw > IMG= iwlwifi-4965-228.61.2.24 > > .include > # > > According to your link, this is the latest version. > However, there is a question mark (?) against it. > I don't know what it means, perhaps that they are > not sure if it works correctly. > I wonder if an earlier version should be used instead? Yeah, no harm in trying. :-) cheers, Hiren > > Thanks > > Anton > > From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 25 20:01: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 99A67158 for ; Tue, 25 Jun 2013 20:01:59 +0000 (UTC) (envelope-from ion2910@yahoo.com) Received: from nm13-vm0.bullet.mail.ird.yahoo.com (nm13-vm0.bullet.mail.ird.yahoo.com [77.238.189.195]) by mx1.freebsd.org (Postfix) with SMTP id D298811EC for ; Tue, 25 Jun 2013 20:01:58 +0000 (UTC) Received: from [77.238.189.227] by nm13.bullet.mail.ird.yahoo.com with NNFMP; 25 Jun 2013 20:01:57 -0000 Received: from [212.82.98.71] by tm16.bullet.mail.ird.yahoo.com with NNFMP; 25 Jun 2013 20:01:57 -0000 Received: from [127.0.0.1] by omp1008.mail.ir2.yahoo.com with NNFMP; 25 Jun 2013 20:01:57 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 151238.60118.bm@omp1008.mail.ir2.yahoo.com Received: (qmail 68735 invoked by uid 60001); 25 Jun 2013 20:01:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1372190517; bh=YWRtieGC3q0cj0bTlWX4dyrrVglsrdE14qf9YNmm8q4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=S/M7XaRf68E3Cwl801pruqK/ividJ2xkdugGD2hqIjzOR9Wscr9509UXswh/iVzHvFjDoCS8W6gZUIsVQIECuIBiFHaQ5cx24wf3uHW4W2ULQnGgUaRQ3PQarRcAbqtmy0FERi0sCOSdhfyRBhjk6Xtths2O2EinONVcnviHkig= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=R7+Q/JZOYMBbe0mXwWJSP69IdZVXuVjntmwuZmN54PEWC+9bfTYoifZWoh+MvRBIojfoYrIUiGUWu/lDIK5dPSMsNmbMgmAtBlcI+Gc0523oBSwvOv8ek6gVhO0p8db7zBh1dN4FCsdERxEit31mGUfebr4RiBRCOBH8d0XOpOw=; X-YMail-OSG: L9Ex_DYVM1me3VNNjoBK1rdNRISkwDO30.FMhJzK73ulHAT SAhtEHhA6QEizIB9l4tezSRt03IDJ3KeeX2BuFx7ixazdLhBY1ELtsFb7XDM vRv.UrofaUWU_2S8Ybi0UlX06kdVBjm1GuI6VQucvq1wbhKPfG4hY7.rwGYJ CmwXvzqKqTnNW_H3ZWNQbilvZTQgR9UKKKr0ffkHUkAWvuCDll41_RkuPwcI 3_AkElQeaFBLm9PwpsADjMtC2P4vs5n3rnSf5KWxQhCPZqbtU7jVHo_x7aY4 0mdz33AlETix1Hx3z5i0ECTANJfOWy2SwvvsytRUrTb5301wPadHbhZBv_XU ShzliGwpKnoXFPimgfjWFLVuxXhgAkK0i2x_34IhCy.UvvEs_zyfXcCKFWZq MQBpSyn06UxVKFk5wvrAV.xVvgpQSsLT4m6alF32jF4J2dPRXe3jDtFAWrLY L81FWT8mPxg2ry07Qo2iPoWaCKYVU11aHdeNTbg7eAwe1QNnYyQ8GGnL8cJ5 aGX2VlXz_ZJYxtsufq_O0Dww- Received: from [80.97.10.110] by web28903.mail.ir2.yahoo.com via HTTP; Tue, 25 Jun 2013 21:01:56 BST X-Rocket-MIMEInfo: 002.001, SGVsbG8sIAoKSSd2ZSBzb21lIGlzc3VlcyB0byBzZXQgdXAgSW50ZWwoUilDZW50cmlubyhSKVdpcmVsZXNzLU4gMjIwMCBjYXJkIAp3aXRoIEZyZWVCU0QgOS4xIFJFTEVBU0UgKGFtZDY0KS4gQWxzbywgSSd2ZSBjaGVja2VkIGluIHRoZSBoYXJkd2FyZSAKY29tcGF0aWJpbGl0eSBmb3IgdGhpcyByZWxlYXNlIGFuZCB0aGUgaXdpLCBpd24gZHJpdmVyIGRvZXMgbm90IHN1cHBvcnQgdGhpcyBXaUZpIGNhcmQuIAoKCkkgd291bGQgbGlrZSB0byBrbm93IGlmIGluIHRoZSBuZXh0IGZ1dHVyZSB3aWxsIGJlIGkBMAEBAQE- X-Mailer: YahooMailWebService/0.8.148.554 Message-ID: <1372190516.56010.YahooMailNeo@web28903.mail.ir2.yahoo.com> Date: Tue, 25 Jun 2013 21:01:56 +0100 (BST) From: Harea Ion Subject: Intel Wireless-N 2200@Driver To: "freebsd-wireless@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Harea Ion List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 20:01:59 -0000 Hello, I've some issues to set up Intel(R)Centrino(R)Wireless-N 2200 card with FreeBSD 9.1 RELEASE (amd64). Also, I've checked in the hardware compatibility for this release and the iwi, iwn driver does not support this WiFi card. I would like to know if in the next future will be implemented a FreeBSD driver for this Wireless card. Until the driver will be ported to FreeBSD, I would like to use it with NDIS wrapper. For this I need the .sys and .inf files(or maybe another files) from the Windows driver. Could you please inform me where I can get those files? Thanks & Regards, From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 25 20:45:05 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 B4A25B7E for ; Tue, 25 Jun 2013 20:45:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by mx1.freebsd.org (Postfix) with ESMTP id 7BAED1642 for ; Tue, 25 Jun 2013 20:45:05 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id e10so7649920qcy.13 for ; Tue, 25 Jun 2013 13:45:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=BN95KAlItxc9Bxo8HA8IeLMqF78mBcF4MxlrJUarNrU=; b=rZKVs5hMuiBmlG+8XRXq230kBxCZ6NDFhwL1jqUTIbBmcoDJBGPkP3nDPWtq2xpafI 5g+xbW1OYCmqllvTabVowQE0GYt4rxAQdyP1OdtI147rlE1jP17q5lpMJTcWzySpwjgk V0QrdaLf1AbD5sCaxPWzYsf5EN8Og7SSRaYH8ONBg4GIwr6wTj2TOdJiqhpFEOSpLZzE apMsfd7jiwQglICs1jx/4EwAyui4SHe/dp6hLWFSbh8HZx1LCNChyfq6Bufoqvtn+YVI i3O5YCfMSJHcF3lYVrc7U+G1uACekOyyFHl8Njes3Kh04IckAb9AjMnljNS8tcyn9Hnw SlHQ== MIME-Version: 1.0 X-Received: by 10.49.107.201 with SMTP id he9mr770575qeb.74.1372193105059; Tue, 25 Jun 2013 13:45:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Tue, 25 Jun 2013 13:45:05 -0700 (PDT) In-Reply-To: <1372190516.56010.YahooMailNeo@web28903.mail.ir2.yahoo.com> References: <1372190516.56010.YahooMailNeo@web28903.mail.ir2.yahoo.com> Date: Tue, 25 Jun 2013 13:45:05 -0700 X-Google-Sender-Auth: n9Jzcvb7i6ON1bNRIFEA6xwDSMc Message-ID: Subject: Re: Intel Wireless-N 2200@Driver From: Adrian Chadd To: Harea Ion 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: Tue, 25 Jun 2013 20:45:05 -0000 Hi, There's some hacking being done on a freebsd-head driver. I'm not sure what the current state is, except that people are definitely trying to make it work. Thanks! -adrian On 25 June 2013 13:01, Harea Ion wrote: > Hello, > > I've some issues to set up Intel(R)Centrino(R)Wireless-N 2200 card > with FreeBSD 9.1 RELEASE (amd64). Also, I've checked in the hardware > compatibility for this release and the iwi, iwn driver does not support this WiFi card. > > > I would like to know if in the next future will be implemented a FreeBSD driver for this Wireless card. > > Until the driver will be ported to FreeBSD, I would like to use it with NDIS wrapper. For this I need the .sys and .inf files(or maybe another files) from the Windows driver. Could you please inform me where I can get those files? > > Thanks & Regards, > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 25 21:18: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 05ABC63A for ; Tue, 25 Jun 2013 21:18:35 +0000 (UTC) (envelope-from ion2910@yahoo.com) Received: from nm3.bullet.mail.ird.yahoo.com (nm3.bullet.mail.ird.yahoo.com [77.238.189.60]) by mx1.freebsd.org (Postfix) with ESMTP id EB17217DA for ; Tue, 25 Jun 2013 21:18:33 +0000 (UTC) Received: from [77.238.189.238] by nm3.bullet.mail.ird.yahoo.com with NNFMP; 25 Jun 2013 21:18:27 -0000 Received: from [212.82.98.113] by tm19.bullet.mail.ird.yahoo.com with NNFMP; 25 Jun 2013 21:18:27 -0000 Received: from [127.0.0.1] by omp1050.mail.ir2.yahoo.com with NNFMP; 25 Jun 2013 21:18:27 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 571397.47688.bm@omp1050.mail.ir2.yahoo.com Received: (qmail 43126 invoked by uid 60001); 25 Jun 2013 21:18:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1372195107; bh=cwJEtQuA6f6SvKyJ3jIW/Bk4aXyHlXNdlwhQ9c4asw0=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=DXiaLmdzRwKJlGh/JH+U7d+JlPBH26k8eyEXbGecERrKwbSnwNokuCzTSIkfDsGrbwSFavOHgv2YEQyzPeWrAo7PzR9F2Xfzx/NCKfl2zq+0iNN5OS0GedBZkeWFnuaAWI8UXtyFyNrKuCGZ5b9lid1/FccloC4bGDk10VpYHpU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=iADwXXLHsic6Dqu8J17Um/rzreCE9RoUYSiq014vaf6YUJpLXegHWXhve+KdKRBI2gNr+7tgOa3YTGAwKR46SrRZmLMJKMyBgCOutzUlyoF41HGCIC14xaANgg9qT/BHl0heuAeVVvI0vqDCqen059IkA9JJyQybaZh3NALsvr8=; X-YMail-OSG: YeQrUesVM1ndqy5CMdYhScENHhHsorJLshn5iV3hL8V_mzw Xhkiyp84N.Jq1QrxG5K5QsjaQs7IPyLGPwQ3RBvTRJnqSYu3Dvo4m4hJGn35 LB7Ethe6apS9eS2pUwj0Vs2E7OQg.r01WUY_f.8wmML6PAYBF9Rd86Pjn.Bx DDsodH6Jy9yfPN8myA.GI296UgZ4k8yftbagWS6SnZgsItKBoB12QfB7UtMU mwHcUIWs4AHFpPEuweZVAIN3r4PIIlaxMrR2TZvwAyYp3X00BgKjF3zkBqck AVK68IQVStROBiB5kPB08FDguxXF2iWZegWBz5kgJy.zHf22bqdEqOTF7NiL IH1XTh3XpW4RwDrW9j3rHaAX2i2slIjt_028kBobOct7oLPcit0TeZ8i6wLq VKiOWS4EKeU9J90fXS7bz09135uplACfyk00RPm9y810muZDoNqIRmLcCPQi Iewato4LcyGsSOcwY6r21RXo1bAY4ApX8bSDqP82VpRurv8NfeVB8nTxqLd9 ayCoa8EPyZkEjg7PLPe28i3yDCA7K_mh3aJvZnoHI90a4Ww-- Received: from [80.97.10.110] by web28903.mail.ir2.yahoo.com via HTTP; Tue, 25 Jun 2013 22:18:26 BST X-Rocket-MIMEInfo: 002.001, SGkgQWRyaWFuLApUaGFua3MgZm9yIHlvdXIgcmVwbHkuRGVmaW5pdGVseSB0aGVyZSBhcmUgZ29vZCBuZXdzIHRvIGhlYXIgdGhhdCBzb21lIHBlb3BsZSBhcmUgd29ya2luZyB0byBmaWd1cmUgaXQgb3V0LgpDb3VsZCB5b3Uga2VlcCBtZSBpbmZvcm1lZCB3aGVuIHRoZSB3aXJlbGVzcyBGcmVlQlNEIGRyaXZlciB3aXRoIHN1cHBvcnQgZm9yIHRoaXMgV2lGaSBjYXJkIHdpbGwgYmUgcmVsZWFzZWQ_CgpNZWFud2hpbGUsIHRoZSBORElTIHdyYXBwZXIgY291bGQgYmUgYSB0ZW1wb3Jhcnkgc29sdXRpb24_CgoBMAEBAQE- X-Mailer: YahooMailWebService/0.8.148.554 References: <1372190516.56010.YahooMailNeo@web28903.mail.ir2.yahoo.com> Message-ID: <1372195106.42625.YahooMailNeo@web28903.mail.ir2.yahoo.com> Date: Tue, 25 Jun 2013 22:18:26 +0100 (BST) From: Harea Ion Subject: Re: Intel Wireless-N 2200@Driver To: Adrian Chadd In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Harea Ion List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 21:18:35 -0000 Hi Adrian, Thanks for your reply.Definitely there are good news to hear that some people are working to figure it out. Could you keep me informed when the wireless FreeBSD driver with support for this WiFi card will be released? Meanwhile, the NDIS wrapper could be a temporary solution? Thanks, Ion Harea ________________________________ From: Adrian Chadd To: Harea Ion Cc: "freebsd-wireless@freebsd.org" Sent: Tuesday, June 25, 2013 11:45 PM Subject: Re: Intel Wireless-N 2200@Driver Hi, There's some hacking being done on a freebsd-head driver. I'm not sure what the current state is, except that people are definitely trying to make it work. Thanks! -adrian On 25 June 2013 13:01, Harea Ion wrote: > Hello, > > I've some issues to set up Intel(R)Centrino(R)Wireless-N 2200 card > with FreeBSD 9.1 RELEASE (amd64). Also, I've checked in the hardware > compatibility for this release and the iwi, iwn driver does not support this WiFi card. > > > I would like to know if in the next future will be implemented a FreeBSD driver for this Wireless card. > > Until the driver will be ported to FreeBSD, I would like to use it with NDIS wrapper. For this I need the .sys and .inf files(or maybe another files) from the Windows driver. Could you please inform me where I can get those files? > > Thanks & Regards, > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 25 21:22:01 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 4ED3C77A for ; Tue, 25 Jun 2013 21:22:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x229.google.com (mail-qe0-x229.google.com [IPv6:2607:f8b0:400d:c02::229]) by mx1.freebsd.org (Postfix) with ESMTP id 14B98180D for ; Tue, 25 Jun 2013 21:22:01 +0000 (UTC) Received: by mail-qe0-f41.google.com with SMTP id b4so750284qen.28 for ; Tue, 25 Jun 2013 14:22:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=v9ROJyl4wDNiL3GKgmKQtrjgEBsp4P3QZ3HeMk0zico=; b=CfN4s9WQuMz6TbW96TG3Q1qW0iTNlZ4wMJmQ2pRI+UASEeNwykNZ8MnrrjthTSvF2X qMNsIm3d8hy2dNApjwM8yYgNxYFJtC57wQJILj2GaxWsrWZNly6OJfLXfyOaF2pujAf6 JE7Vix1fn1EGieDwfd1bTtQah44RGQKvfHDs12mVPtuC2nL2rAyQTrtSBF/LzdjzLjAR lsvGqtQxkQvHszH2LJmTzSLe/RcuBcCfSS5Lg7spiJWp3aEsumPZzldeyv1qFZvHGETo xy/RAuzkDhUZg/vaF4f+rlgH96BoCnXa67fAkPxrgxhUUDxz6EdVulcbr3EWleUGBtk/ Beow== MIME-Version: 1.0 X-Received: by 10.49.117.195 with SMTP id kg3mr913371qeb.68.1372195320595; Tue, 25 Jun 2013 14:22:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Tue, 25 Jun 2013 14:22:00 -0700 (PDT) In-Reply-To: <1372195106.42625.YahooMailNeo@web28903.mail.ir2.yahoo.com> References: <1372190516.56010.YahooMailNeo@web28903.mail.ir2.yahoo.com> <1372195106.42625.YahooMailNeo@web28903.mail.ir2.yahoo.com> Date: Tue, 25 Jun 2013 14:22:00 -0700 X-Google-Sender-Auth: oa0Rn6s8_P0Z9OBcTppv6JFhnNM Message-ID: Subject: Re: Intel Wireless-N 2200@Driver From: Adrian Chadd To: Harea Ion 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: Tue, 25 Jun 2013 21:22:01 -0000 On 25 June 2013 14:18, Harea Ion wrote: > Hi Adrian, > > Thanks for your reply. Definitely there are good news to hear that some > people are working to figure it out. > Could you keep me informed when the wireless FreeBSD driver with support for > this WiFi card will be released? I'm sure the results will be posted to -wireless :-0 > Meanwhile, the NDIS wrapper could be a temporary solution? I've not played with the ndis wrapper at all and I really don't want to hack on it :-) Thanks! adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 26 06:08: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 A6C3F779; Wed, 26 Jun 2013 06:08:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 5F5451FD8; Wed, 26 Jun 2013 06:08:06 +0000 (UTC) Received: by mail-qe0-f43.google.com with SMTP id q19so848355qeb.30 for ; Tue, 25 Jun 2013 23:08:05 -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:cc:content-type; bh=B0Hb6VafK9etzSjpM/Ia31pli+EigDI0dZ7khAQcaV0=; b=qufzh3MpubwGG5IfEInZQXwvYiogtIkDQQIwkLHc2SjTSJmG/aLZPrRgwVfNMgG4T8 +OOxVDCSulDbKSvGFiDicT5OKXIXOTLstnXNzkdFDsritl0SrAbNuWVW1xOuRyYvQQgY ldxnMCJvDxHfx+KiKor+71NaphhQRghw9xgSEnzMRLA7t+ea/7km2wURqBq21k3SEWZi twwoutqW7dfYF5YxCN0LPSnEsVAqaq9LNley2/UXwzaciDg38o/Wa5K9QLEmbTaIf23b Zwk9edrEgKliUIy6Gfn9obSKuUluu+4ICdLPFksYG4MprLTmWfVICW2DvojzuTqKb3gO HHEQ== MIME-Version: 1.0 X-Received: by 10.224.190.137 with SMTP id di9mr3375314qab.95.1372226885913; Tue, 25 Jun 2013 23:08:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.214.7 with HTTP; Tue, 25 Jun 2013 23:08:05 -0700 (PDT) Date: Tue, 25 Jun 2013 23:08:05 -0700 X-Google-Sender-Auth: bubwzSND5kiT9P3nOxoernn6oEU Message-ID: Subject: -HEAD has (what seems to be) working AR933x SoC support; Carambola 2 board now works! From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 06:08:06 -0000 Hi, I've finally brought up wifi on the Carambola 2 board. It's an AR9330 SoC with 10/100 ethernet, 64MB RAM, 16MB flash, 1x1 2GHz 11n wifi. It's perfect for embedding into projects to wifi enable them. It should also make for an awesome cheap 802.11s device. The details and instructions are here: http://code.google.com/p/freebsd-wifi-build/wiki/Carambola2 Seriously cool stuff. It turns out that bringing up the QCA HAL was really easy on this board - the support is already there! I just needed to hack at the AHB bus glue that I wrote and make sure that the QCA HAL flash EEPROM code understood what I was doing. Woot! Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 26 13:43: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 D598AD62 for ; Wed, 26 Jun 2013 13:43:21 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by mx1.freebsd.org (Postfix) with ESMTP id 450151807 for ; Wed, 26 Jun 2013 13:43:21 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id c10so8219952qcz.14 for ; Wed, 26 Jun 2013 06:43:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=Hnwle1e2SpMN0Jb7YE7ZngorjLErGfq9Ai7rNBdQow0=; b=VdmVACFLhj6epOOD0dm+yBV67TfCdV7GUxyQgf942Ask+OUZxIxmvL4Q+7xl80Kzp+ xMEMt0OBC2mptusBZJIStfyGJmPLfvUQK53rdM4uvI1Ww2bq7/cOJN6XJkmYF+lOPpMq qVb34EsGzBFdbLU8ER1W+V5P1zvSa7rWIHsCp5z1ajmnqbMOJoaLdjP+3j/cF7rTB31P VRjcF89yV/7A4cbsZmEKGKa3ZPWIYU9WA1cgPrXeQFAodxEtfiYOSee4YlpwJ1NaTwup RuvqpgW217eAOBF6hafO3U8pxA85h8te+m6iz/pLoh5tsdBGunmwwMsK5ZYFod3Pn5Bf Wwjw== MIME-Version: 1.0 X-Received: by 10.224.190.137 with SMTP id di9mr5312195qab.95.1372254200844; Wed, 26 Jun 2013 06:43:20 -0700 (PDT) Received: by 10.49.106.1 with HTTP; Wed, 26 Jun 2013 06:43:20 -0700 (PDT) In-Reply-To: References: Date: Wed, 26 Jun 2013 21:43:20 +0800 Message-ID: Subject: Re: -HEAD has (what seems to be) working AR933x SoC support; Carambola 2 board now works! From: Alie Tan To: Adrian Chadd X-Gm-Message-State: ALoCoQnqE4g/ggn2d0Ic6jjQtj/057NEOW+uIojGqYnvNkbDayvrIVzEf6PH/nVn9tYX1lxFZLGy Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-wireless@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 13:43:21 -0000 On Wed, Jun 26, 2013 at 2:08 PM, Adrian Chadd wrote: > Hi, > > I've finally brought up wifi on the Carambola 2 board. > > It's an AR9330 SoC with 10/100 ethernet, 64MB RAM, 16MB flash, 1x1 > 2GHz 11n wifi. It's perfect for embedding into projects to wifi enable > them. It should also make for an awesome cheap 802.11s device. > Awesome stuff Adrian! How is FreeBSD performance on Carambola2? What do you have btw, is it Cambola2 soldered version? > > The details and instructions are here: > > http://code.google.com/p/freebsd-wifi-build/wiki/Carambola2 > > Seriously cool stuff. > > It turns out that bringing up the QCA HAL was really easy on this > board - the support is already there! I just needed to hack at the AHB > bus glue that I wrote and make sure that the QCA HAL flash EEPROM code > understood what I was doing. Woot! > > > > Adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 26 17:25: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 ABD38610 for ; Wed, 26 Jun 2013 17:25:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id 64423110C for ; Wed, 26 Jun 2013 17:25:56 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id a1so8362815qcx.39 for ; Wed, 26 Jun 2013 10:25:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=opY24lOufdLW8c9QnDl/5bl34V+2RmQFwHrmV09hkJY=; b=dNOKei1ru/ZRVakoDhpXVJTQVrsMxR8ipqxS1/RSbKWnX2MqFAXut7zLweTANnUCGY 2ezTXiniYcTCqCHwSO18rpnr7l7TxymwO630fwO/NgmkHwdrTRzdMdWqsBhNFl0Nvhxm SnhZCe6Djc3Enso8hCnvAOb4scSF0i/4oqgZkd/FF2dJoKZSj0+qIXmSJpZ+p1dlkXjP Oz0NedsWmVFKCk4iOiyIV4IgZ136/+wQL5Rw8KMy6QO3N3ZbdylKo5kt3kFp+AC9mzpH qv/dRzuMIw35/LFPhDS7G2XSlX5sIWlC/G0WK85eE1oFdf4wyV125OXQDNa5LAnJ7c4X 1eqQ== MIME-Version: 1.0 X-Received: by 10.49.127.4 with SMTP id nc4mr6076184qeb.41.1372267555946; Wed, 26 Jun 2013 10:25:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.214.7 with HTTP; Wed, 26 Jun 2013 10:25:55 -0700 (PDT) In-Reply-To: References: <608F1F43-59F3-456D-A725-B36C2F9C2E75@gmail.com> Date: Wed, 26 Jun 2013 10:25:55 -0700 X-Google-Sender-Auth: 9Lxeuhf-MpqJXXccTSITUsmyfQk 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, 26 Jun 2013 17:25:56 -0000 Hi! I'm going to cc freebsd-wireless@ because I think it's a good idea to keep the community in the loop with what's needed for the rate control APi improvements. On 26 June 2013 09:46, Chenchong Qin wrote: > Hi, > > First, sorry for not contact you in these days. It's fine! > I've browsed freebsd's wifi stack and the mac80211. After walking through > the whole stack, I found the rate control is done just before the frame's > handoff to hw (as for the case of ath)... Right. It's done like that in all the wifi stacks that you see. > There is a simple rate control api in net80211, but the ath driver also > contains a rate control api and implementations of rate control algorithms. > And, it seems that ath doesn't use net80211's rate control api. So, how we > handle the relationship of these 2 apis? Enable one & disable the other or > something else? The eventual goal is to deprecate the ath_rate stuff and migrate it all to net80211. That way everything can share the same rate control code for all drivers. > Now I'm trying to add multiple rate attempts support to net80211's rate > control api. Whether I should do the rate control in net80211 and disable > the ath's rate control stuff? Well, you don't have to do that just yet. Just look at listing all the extra work that the ath_rate API does and the TX code in if_ath_tx_ht.c does based on the decisions from the rate control code. Once you have a good idea of what's going on, it's then a question of implementing those same features in net80211's rate control code, but making them optional. For example, the first thing I'd do is modify the net80211 rate control code to do multi-rate table stuff, rather than returning a single rate table entry. Support up to say 4 rate table entries. When the driver creates the rate control module instance for use, it will have to say "hey, I support up to 4 rate retries". Some drivers only support one. Some support 2. The AR5210/AR5211 support 1, the AR5212 and later support 4. The next thing I'd do is look at what options are available for each rate. For the AR5212, you can only do RTS/CTS with a single rate attempt. Ie, you can't do multi-rate retry in hardware _and_ RTS/CTS. Thus, with RTS/CTS you have to only do one rate attempt. For the AR5416 and later, you can change the RTS/CTS flags per rate attempt. So you'd have to capture that. That's the really big thing. Once you've implemented that in the net80211 rate control code we can easily smash it into a couple of drivers and test it out. We can then work on 11n stuff _after_ that. 11n isn't that scary; it's just more options. But the really tricky bit is the muti-rate retry scheme. > > Besides, lots of big structs and driver related things that I'm unfamiliar > with make me feel the stuffs are complicated. Do you have some futher > references for me? Not really. I suggest you create a document and note what you've found thus far, so we can _write_ this reference. You've already reviewed it, so it's partially done! Thanks! Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 27 02:10:01 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CD44CF41 for ; Thu, 27 Jun 2013 02:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A5E521CF4 for ; Thu, 27 Jun 2013 02:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5R2A1Fe085653 for ; Thu, 27 Jun 2013 02:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5R2A1De085652; Thu, 27 Jun 2013 02:10:01 GMT (envelope-from gnats) Date: Thu, 27 Jun 2013 02:10:01 GMT Message-Id: <201306270210.r5R2A1De085652@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Anton Shterenlikht Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Anton Shterenlikht List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 02:10:01 -0000 The following reply was made to PR kern/176104; it has been noted by GNATS. From: Anton Shterenlikht To: bug-followup@freebsd.org Cc: Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Tue, 25 Jun 2013 14:28:51 +0100 (BST) One thing I noticed is that this problem occurs more often when running on battery, and less frequently when running from mains. Could this be related to some energy saving code? From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 27 04:20: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 CBFBD896 for ; Thu, 27 Jun 2013 04:20:38 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) by mx1.freebsd.org (Postfix) with ESMTP id 684E715E6 for ; Thu, 27 Jun 2013 04:20:38 +0000 (UTC) Received: by mail-ee0-f52.google.com with SMTP id c50so109192eek.25 for ; Wed, 26 Jun 2013 21:20: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=s6LoGC003fQnheHm1xAvK4CzPx93v8baKTofBQYkVSs=; b=uiNrC6rpTGpQGWqsU2Db+3ERnaWmP5cxaXi6tgzZ8oxYimSRO/Z1do8pXDYQ7SWQjZ ZDlW4JUo6blJXoyQ8YZEZgQkAIGOvaZD7zX20lUqA/D6uHqOGi8q+jjk+3ZA4jpMBXXN B1DAxxkZP77oIfInxCfHCWes5dwHMV8Zp0ZeqJNcN43S9Ia7M6qgbENdo4W5xqZ61OQe 8jzM7AEZomBUN/mgtcYAY/RnvnljXTZ5Dt/MHHZE1qKIEssQaTs/25eYt56aJQ01eFQB 4fERIL5ZZaMaItifWxr/1dAPnNieMIy1PjGfCVk2qbLNpQ2kEoZn765hXyQU8BuZXxli kk6Q== MIME-Version: 1.0 X-Received: by 10.15.55.199 with SMTP id v47mr6863266eew.41.1372306837625; Wed, 26 Jun 2013 21:20:37 -0700 (PDT) Received: by 10.14.119.203 with HTTP; Wed, 26 Jun 2013 21:20:37 -0700 (PDT) In-Reply-To: <201306270210.r5R2A1De085652@freefall.freebsd.org> References: <201306270210.r5R2A1De085652@freefall.freebsd.org> Date: Wed, 26 Jun 2013 21:20:37 -0700 Message-ID: Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error From: hiren panchasara To: Anton Shterenlikht Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 04:20:38 -0000 On Wed, Jun 26, 2013 at 7:10 PM, Anton Shterenlikht wrote: > The following reply was made to PR kern/176104; it has been noted by GNATS. > > From: Anton Shterenlikht > To: bug-followup@freebsd.org > Cc: > Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error > Date: Tue, 25 Jun 2013 14:28:51 +0100 (BST) > > One thing I noticed is that this problem occurs > more often when running on battery, and less > frequently when running from mains. Could this > be related to some energy saving code? AFAIK, no. Hiren > _______________________________________________ > 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 Jun 29 16:33:18 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87CE529E; Sat, 29 Jun 2013 16:33:18 +0000 (UTC) (envelope-from linimon@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 60F171C7E; Sat, 29 Jun 2013 16:33:18 +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 r5TGXIqC084456; Sat, 29 Jun 2013 16:33:18 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5TGXIYW084455; Sat, 29 Jun 2013 16:33:18 GMT (envelope-from linimon) Date: Sat, 29 Jun 2013 16:33:18 GMT Message-Id: <201306291633.r5TGXIYW084455@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/180094: [iwn] Incorrect id for Intel Centrino Wireless-N 130 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, 29 Jun 2013 16:33:18 -0000 Synopsis: [iwn] Incorrect id for Intel Centrino Wireless-N 130 Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jun 29 16:32:52 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=180094 From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 29 18:10:01 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 730A091D for ; Sat, 29 Jun 2013 18:10:01 +0000 (UTC) (envelope-from gnats@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 64E601F12 for ; Sat, 29 Jun 2013 18:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5TIA1V9002111 for ; Sat, 29 Jun 2013 18:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5TIA1NU002110; Sat, 29 Jun 2013 18:10:01 GMT (envelope-from gnats) Date: Sat, 29 Jun 2013 18:10:01 GMT Message-Id: <201306291810.r5TIA1NU002110@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: hiren panchasara Subject: Re: kern/180094: [iwn] Incorrect id for Intel Centrino Wireless-N 130 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hiren panchasara List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jun 2013 18:10:01 -0000 The following reply was made to PR kern/180094; it has been noted by GNATS. From: hiren panchasara To: Cedric Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/180094: [iwn] Incorrect id for Intel Centrino Wireless-N 130 Date: Sat, 29 Jun 2013 11:00:59 -0700 On Sat, Jun 29, 2013 at 8:52 AM, Cedric wrote: > >>Number: 180094 >>Category: kern >>Synopsis: [iwn] Incorrect id for Intel Centrino Wireless-N 130 >>Confidential: no >>Severity: non-critical >>Priority: low >>Responsible: freebsd-bugs >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Sat Jun 29 16:00:00 UTC 2013 >>Closed-Date: >>Last-Modified: >>Originator: Cedric >>Release: 9.1-release-p4 >>Organization: >>Environment: > FreeBSD Test.RP614v4 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0 r252335: Fri Jun 28 19:04:30 CEST 2013 > root@Test.RP614v4:/usr/obj/amd64.amd64/usr/src/sys/GENERIC amd64 >>Description: > iwn_ident_table indicate a wrong id for Intel Centrino Wireless-N 130. > > In /head/sys/dev/iwn/if_iwn.c : > { 0x8086, 0x0887, "Intel Centrino Wireless-N 130" } > > 0x0887 is wrong. Must be 0x0897. > Cf. : http://pci-ids.ucw.cz/read/PC/8086 Looks correct. Will patch it. Thanks, Hiren > > >>How-To-Repeat: > >>Fix: > > >>Release-Note: >>Audit-Trail: >>Unformatted: > _______________________________________________ > freebsd-bugs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 29 19:24:24 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7D0BD56B; Sat, 29 Jun 2013 19:24:24 +0000 (UTC) (envelope-from hiren@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 56459117C; Sat, 29 Jun 2013 19:24:24 +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 r5TJOO7E017805; Sat, 29 Jun 2013 19:24:24 GMT (envelope-from hiren@freefall.freebsd.org) Received: (from hiren@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5TJOO1r017804; Sat, 29 Jun 2013 19:24:24 GMT (envelope-from hiren) Date: Sat, 29 Jun 2013 19:24:24 GMT Message-Id: <201306291924.r5TJOO1r017804@freefall.freebsd.org> To: hiren@FreeBSD.org, freebsd-wireless@FreeBSD.org, hiren@freebsd.org From: hiren@FreeBSD.org Subject: Re: kern/180094: [iwn] Incorrect id for Intel Centrino Wireless-N 130 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, 29 Jun 2013 19:24:24 -0000 Synopsis: [iwn] Incorrect id for Intel Centrino Wireless-N 130 Responsible-Changed-From-To: freebsd-wireless->hiren@freebsd.org Responsible-Changed-By: hiren Responsible-Changed-When: Sat Jun 29 19:23:59 UTC 2013 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=180094