From owner-freebsd-wireless@FreeBSD.ORG Wed Jun 19 15:49:12 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 35CD5C6F for ; Wed, 19 Jun 2013 15:49:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id EB9EE1B71 for ; Wed, 19 Jun 2013 15:49:11 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id u12so3145206qcx.12 for ; Wed, 19 Jun 2013 08:49:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KplhRSv5HhNfqhe9SpQzpGPROuSAqosqFAeDHHYy0Ug=; b=phxNkQdbQvIM4wPTGCR+eKzKghKxn6fcqgDSYgCsjE+5XKGc2jHNKR+vKLOIMmoPy0 R8ja4m4gPQSqiPvHnBCpegmiXZo3LLL7yR4w8T2vldC3/IEMp05At2fJQ7D4+EVtT1YM YGqzlZZjcbAIoQf8qGpI2uSxSznyGpz/JoQnZ3QBdJx6L9m3TWgLFKB6jitkjWtns2CC MndKP7eWc9YULfe5Zw2UoapR1C3yb0XuREQAZY8m1J1TG/nqxOu9ANe8GVQdr5NMtcn+ Uvi3LvNQY+bPwUDuNQhzzxEYoq0HEhG+Wp3dn1eyKQPdOMTs6wn9wQmSHp+Qeg8DKb1y ahaQ== MIME-Version: 1.0 X-Received: by 10.49.109.72 with SMTP id hq8mr4175094qeb.38.1371656950740; Wed, 19 Jun 2013 08:49:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Wed, 19 Jun 2013 08:49:10 -0700 (PDT) In-Reply-To: <20130619091310.GD985@gpr.nnz-home.ru> References: <201306140815.r5E8FSPn029488@svn.freebsd.org> <20130619072806.GA985@gpr.nnz-home.ru> <20130619082855.GC985@gpr.nnz-home.ru> <20130619091310.GD985@gpr.nnz-home.ru> Date: Wed, 19 Jun 2013 08:49:10 -0700 X-Google-Sender-Auth: 8a4chN734R4sDIGHA9WjlNO2GBU 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: Wed, 19 Jun 2013 15:49:12 -0000 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" >> >> >> >> >> >>