From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 1 01:10:15 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1E0A1065676 for ; Sun, 1 Jan 2012 01:10:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B0F4D8FC13 for ; Sun, 1 Jan 2012 01:10:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q011AFdX032401 for ; Sun, 1 Jan 2012 01:10:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q011AFiO032399; Sun, 1 Jan 2012 01:10:15 GMT (envelope-from gnats) Date: Sun, 1 Jan 2012 01:10:15 GMT Message-Id: <201201010110.q011AFiO032399@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/163689: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2012 01:10:15 -0000 The following reply was made to PR kern/163689; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/163689: commit references a PR Date: Sun, 1 Jan 2012 01:09:06 +0000 (UTC) Author: adrian Date: Sun Jan 1 01:08:51 2012 New Revision: 229165 URL: http://svn.freebsd.org/changeset/base/229165 Log: If frames are dumped out of the queue, let's at least see what they are. This shows that the majority of the weird traffic I see here are probe frames that haven't been sent out, but I can also trigger this condition by doing ICMP w/ -i 0.3 - enough to trigger the TX during actual scanning, but not fast enough to stop scanning from occuring. PR: kern/163689 Modified: head/sys/dev/ath/if_ath_tx.c Modified: head/sys/dev/ath/if_ath_tx.c ============================================================================== --- head/sys/dev/ath/if_ath_tx.c Sun Jan 1 00:23:32 2012 (r229164) +++ head/sys/dev/ath/if_ath_tx.c Sun Jan 1 01:08:51 2012 (r229165) @@ -2405,6 +2405,12 @@ ath_tx_tid_drain(struct ath_softc *sc, s tid->hwq_depth, tid->incomp, tid->baw_head, tid->baw_tail, tap == NULL ? -1 : tap->txa_start, ni->ni_txseqs[tid->tid]); + + /* XXX Dump the frame, see what it is? */ + ieee80211_dump_pkt(ni->ni_ic, + mtod(bf->bf_m, const uint8_t *), + bf->bf_m->m_len, 0, -1); + t = 1; } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 1 01:19:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 371FE1065677 for ; Sun, 1 Jan 2012 01:19:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E45878FC12 for ; Sun, 1 Jan 2012 01:19:13 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so20244818vbb.13 for ; Sat, 31 Dec 2011 17:19:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/BgFnhD9nFkGMWOo2KWvENPSpiXPhBEx3Lu7n39oVGs=; b=QyjeZw+lDNp+GZH2CmlXG2FgEl9ys9VrBLOv6+GvBywpD4kGRDPlhup3htphLHyNZm OfzwokHfbAaudq09anAhzntCOdWfqiEoQ4dGqDLK4oy0+hZ+GMEWdudUE7XBuXJP/7td urSLTp6ojHRhKsA6hEMrEcHQz+Mhn7J2LieWc= MIME-Version: 1.0 Received: by 10.52.33.99 with SMTP id q3mr20936493vdi.100.1325380753051; Sat, 31 Dec 2011 17:19:13 -0800 (PST) Received: by 10.52.36.5 with HTTP; Sat, 31 Dec 2011 17:19:13 -0800 (PST) In-Reply-To: References: Date: Sat, 31 Dec 2011 17:19:13 -0800 Message-ID: From: Adrian Chadd To: "Lay, Nathan" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" Subject: Re: ath "stops working" in hostap mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2012 01:19:14 -0000 On 31 December 2011 17:15, Lay, Nathan wrote: > Adrian, > Thanks for the prompt response. Bumping the interface up and down does no= t fix it. Destroying and recreating the interface does not fix it either. T= he interface is completely unresponsive when this problem arises. As far as= I can tell, it does not transmit (it vanishes from view from all other dev= ices). > > I do not have ATH_ENABLE_11N compiled in. Would this improve stability? T= he interface shows that it is using 11g mode with background scanning turne= d off. Here is exactly how it is configured and used: Hi, Please don't compile in ATH_ENABLE_11N. But do add: options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI > create_args_wlan0=3D"wlanmode hostap -bgscan" > autobridge_bridge0=3D"wlan0 lan0" > > It also sits behind pf (I saw pf mentioned in a similar message about ath= ). > > I've installed athstats. Attached is the output. Ok. Can you please do this: * recompile with the above options; * try running 'athstats -i ath0 -o bexmit,bmiss 1' * (athstats -l will list what you can track, statistics-wise) * Make sure it's sending those beacons, or at least queuing to send those beacons. Once that's done, wait until it fails and then try it again. It should still be trying to send the beacons, but we'll see what else shows up. Finally, do you have any FreeBSD stations? That we could use to see what's going on in the air? Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 1 01:30:16 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B830106566B for ; Sun, 1 Jan 2012 01:30:16 +0000 (UTC) (envelope-from nsl03@my.fsu.edu) Received: from DB3EHSOBE003.bigfish.com (db3ehsobe003.messaging.microsoft.com [213.199.154.141]) by mx1.freebsd.org (Postfix) with ESMTP id 696CD8FC0A for ; Sun, 1 Jan 2012 01:30:15 +0000 (UTC) Received: from mail12-db3-R.bigfish.com (10.3.81.250) by DB3EHSOBE003.bigfish.com (10.3.84.23) with Microsoft SMTP Server id 14.1.225.23; Sun, 1 Jan 2012 01:15:07 +0000 Received: from mail12-db3 (localhost [127.0.0.1]) by mail12-db3-R.bigfish.com (Postfix) with ESMTP id 7AF066C02F7; Sun, 1 Jan 2012 01:15:07 +0000 (UTC) X-SpamScore: -15 X-BigFish: PS-15(zz9371Ic85fh1447M1432N98dKzz1202hzzz2fh2a8h668h839h34h) X-Forefront-Antispam-Report: CIP:207.46.198.81; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0502HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI Received-SPF: pass (mail12-db3: domain of my.fsu.edu designates 207.46.198.81 as permitted sender) client-ip=207.46.198.81; envelope-from=nsl03@my.fsu.edu; helo=CH1PRD0502HT005.namprd05.prod.outlook.com ; .outlook.com ; Received: from mail12-db3 (localhost.localdomain [127.0.0.1]) by mail12-db3 (MessageSwitch) id 1325380507330628_27474; Sun, 1 Jan 2012 01:15:07 +0000 (UTC) Received: from DB3EHSMHS009.bigfish.com (unknown [10.3.81.241]) by mail12-db3.bigfish.com (Postfix) with ESMTP id 4C133340045; Sun, 1 Jan 2012 01:15:07 +0000 (UTC) Received: from CH1PRD0502HT005.namprd05.prod.outlook.com (207.46.198.81) by DB3EHSMHS009.bigfish.com (10.3.87.109) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 1 Jan 2012 01:15:07 +0000 Received: from CH1PRD0502MB118.namprd05.prod.outlook.com ([169.254.4.150]) by CH1PRD0502HT005.namprd05.prod.outlook.com ([10.28.29.225]) with mapi id 14.15.0029.001; Sun, 1 Jan 2012 01:15:06 +0000 From: "Lay, Nathan" To: "freebsd-wireless@freebsd.org" Thread-Topic: ath "stops working" in hostap mode Thread-Index: AczIH3ff9bH4FEEXTfmSyjYG+0XJfwAAaWMAAAAMC6Y= Date: Sun, 1 Jan 2012 01:15:05 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [68.35.230.205] Content-Type: multipart/mixed; boundary="_003_A838E171DD71354E99079424FC4F7DDB182A9042CH1PRD0502MB118_" MIME-Version: 1.0 X-OriginatorOrg: my.fsu.edu Cc: Subject: RE: ath "stops working" in hostap mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2012 01:30:16 -0000 --_003_A838E171DD71354E99079424FC4F7DDB182A9042CH1PRD0502MB118_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Adrian,=0A= Thanks for the prompt response. Bumping the interface up and down does not = fix it. Destroying and recreating the interface does not fix it either. The= interface is completely unresponsive when this problem arises. As far as I= can tell, it does not transmit (it vanishes from view from all other devic= es).=0A= =0A= I do not have ATH_ENABLE_11N compiled in. Would this improve stability? The= interface shows that it is using 11g mode with background scanning turned = off. Here is exactly how it is configured and used:=0A= =0A= create_args_wlan0=3D"wlanmode hostap -bgscan"=0A= autobridge_bridge0=3D"wlan0 lan0"=0A= =0A= It also sits behind pf (I saw pf mentioned in a similar message about ath).= =0A= =0A= I've installed athstats. Attached is the output.=0A= =0A= Best Regards,=0A= Nathan Lay=0A= =0A= ________________________________________=0A= From: Adrian Chadd [adrian.chadd@gmail.com]=0A= Sent: Saturday, December 31, 2011 8:03 PM=0A= To: Lay, Nathan=0A= Subject: Re: ath "stops working" in hostap mode=0A= =0A= Hi,=0A= =0A= I'd prefer you to email the -wireless list so we can debug this in public. = :)=0A= =0A= On 31 December 2011 16:59, Lay, Nathan wrote:=0A= > Hi Adrian,=0A= > I saw in the PR and mailing list that someone else seemed to have problem= s=0A= > with ath in hostap mode. I have no idea what causes it as it happens for = no=0A= > apparent reason after an arbitrary amount of time. The first time I saw t= his=0A= > problem, it happened after 1 day of uptime. The next time, it happened af= ter=0A= > a week of uptime. A reboot is required to remedy the problem although I'm= =0A= > not certain if reloading the module would solve the problem (I did not ha= ve=0A= > it compiled as a loadable module).=0A= =0A= Is this something that has been going on for a while? Or is it a recent thi= ng?=0A= =0A= > uname:=0A= > FreeBSD RADIO.LOCAL 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #2: Sat Dec 31= =0A= > 01:19:47 EST 2011 nslay@RADIO.LOCAL:/usr/obj/usr/src/sys/RADIO amd64= =0A= >=0A= > I don't know the SVN revision as I still have it setup to use CVS. Is the= re=0A= > anyway I can get the SVN revision from CVS? All I can tell you is that I= =0A= > updated the sources on the 23rd when the security advisories were issued.= =0A= =0A= There's no easy way, no. it's just easier to work from subversion. :)=0A= =0A= > Here's what I have:=0A= > ath0: mem 0xfe9f0000-0xfe9fffff irq 16 at device 0.0 on pc= i1=0A= > ath0: AR5418 mac 12.10 RF2133 phy 8.1=0A= >=0A= > I noticed that you claim the AR5416 is crap. I might just look for an AR9= xxx=0A= > card instead.=0A= =0A= It's not "crap", it's just an early version of their 802.11n stuff and=0A= the newer stuff is much more stable.=0A= =0A= > I'm not terribly familiar with the ath sysctl tunables, but here's someth= ing=0A= > that looks unusual:=0A= > dev.ath.0.stats.rx_phy_err.31: 30190=0A= =0A= Just ignore that unless it's actually continuing to rise. :)=0A= =0A= > (All others are 0 count)=0A= >=0A= > I also noticed this tunable:=0A= > dev.ath.0.hal.ar5416_biasadj=0A= >=0A= > Is this something relevant to me?=0A= >=0A= > I am fluent in C. Is there anywhere specific I could look through?=0A= =0A= The thing to do is figure out:=0A= =0A= * what you mean by "stops working" ;-)=0A= * is it a tx problem, an rx problem, or both=0A= * make sure you've not enabled 11n (ie, you haven't compiled the=0A= kernel with ATH_ENABLE_11N) as that could be part of it, even on -9.=0A= * do any counters change - compile up sys/tools/tools/ath/athstats and=0A= use that to start to figure out what's going on.=0A= * does bumping the interface fix things - ie ifconfig wlanX down;=0A= ifconfig wlanX up?=0A= =0A= =0A= =0A= Adrian=0A= =0A= --_003_A838E171DD71354E99079424FC4F7DDB182A9042CH1PRD0502MB118_ Content-Type: text/plain; name="athstats.txt" Content-Description: athstats.txt Content-Disposition: attachment; filename="athstats.txt"; size=842; creation-date="Sun, 01 Jan 2012 01:11:20 GMT"; modification-date="Sun, 01 Jan 2012 01:11:20 GMT" Content-ID: <8f243d47-9bca-4a02-ab9d-ab0101309f00> Content-Transfer-Encoding: base64 YXRoc3RhdHM6IGF0aDA6IEludmFsaWQgYXJndW1lbnQKYXRoc3RhdHM6IGF0aDA6IEludmFsaWQg YXJndW1lbnQKMjY0MzY5OSAgZGF0YSBmcmFtZXMgcmVjZWl2ZWQKNjgzNzgxICAgZGF0YSBmcmFt ZXMgdHJhbnNtaXQKNDY3ICAgICAgdHggZnJhbWVzIHdpdGggYW4gYWx0ZXJuYXRlIHJhdGUKOTY5 MjEgICAgbG9uZyBvbi1jaGlwIHR4IHJldHJpZXMKMTU0MDAgICAgdHggZmFpbGVkICdjdXogdG9v IG1hbnkgcmV0cmllcwo4MiAgICAgICBzdHVjayBiZWFjb24gY29uZGl0aW9ucwoxMk0gICAgICBj dXJyZW50IHRyYW5zbWl0IHJhdGUKMTQwODMgICAgdHggZnJhbWVzIHdpdGggbm8gYWNrIG1hcmtl ZAo2NDQyOTggICB0eCBmcmFtZXMgd2l0aCBzaG9ydCBwcmVhbWJsZQoxNjA2OTkgICByeCBmYWls ZWQgJ2N1eiBvZiBiYWQgQ1JDCjMwNjU4ICAgIHJ4IGZhaWxlZCAnY3V6IG9mIFBIWSBlcnIKICAg IDMwNjU4ICAgIENDSyByZXN0YXJ0CjY1ODA1MSAgIGJlYWNvbnMgdHJhbnNtaXR0ZWQKMjI0NiAg ICAgcGVyaW9kaWMgY2FsaWJyYXRpb25zCi0wLyswICAgIFRETUEgc2xvdCBhZGp1c3QgKHVzZWNz LCBzbW9vdGhlZCkKNTAgICAgICAgcnNzaSBvZiBsYXN0IGFjawoyNyAgICAgICBhdmcgcmVjdiBy c3NpCi05NiAgICAgIHJ4IG5vaXNlIGZsb29yCjI1NDE0ICAgIHR4IGZyYW1lcyB0aHJvdWdoIHJh dyBhcGkKMTE1OTYgICAgY2FicSBmcmFtZXMgdHJhbnNtaXR0ZWQKNjYxOSAgICAgY2FicSB4bWl0 IG92ZXJmbG93ZWQgYmVhY29uIGludGVydmFsCkFudGVubmEgcHJvZmlsZToKWzBdIHR4ICAgNjY4 MzUyIHJ4ICAgMTYyMTA1ClsxXSB0eCAgICAgICAgMCByeCAgMjQ4MTU5NAo= --_003_A838E171DD71354E99079424FC4F7DDB182A9042CH1PRD0502MB118_ Content-Type: text/plain; name="ifconfig.txt" Content-Description: ifconfig.txt Content-Disposition: attachment; filename="ifconfig.txt"; size=550; creation-date="Sun, 01 Jan 2012 01:13:52 GMT"; modification-date="Sun, 01 Jan 2012 01:13:52 GMT" Content-ID: Content-Transfer-Encoding: base64 d2xhbjA6IGZsYWdzPTg5NDM8VVAsQlJPQURDQVNULFJVTk5JTkcsUFJPTUlTQyxTSU1QTEVYLE1V TFRJQ0FTVD4gbWV0cmljIDAgbXR1IDE1MDAKCWV0aGVyIDFjOmFmOmY3OmYzOjQyOmMxCglpbmV0 NiBmZTgwOjoxZWFmOmY3ZmY6ZmVmMzo0MmMxJXdsYW4wIHByZWZpeGxlbiA2NCB0ZW50YXRpdmUg c2NvcGVpZCAweDEwIAoJbmQ2IG9wdGlvbnM9Mjk8UEVSRk9STU5VRCxJRkRJU0FCTEVELEFVVE9f TElOS0xPQ0FMPgoJbWVkaWE6IElFRUUgODAyLjExIFdpcmVsZXNzIEV0aGVybmV0IGF1dG9zZWxl Y3QgbW9kZSAxMWcgPGhvc3RhcD4KCXN0YXR1czogcnVubmluZwoJc3NpZCBMYW1wIGNoYW5uZWwg NSAoMjQzMiBNSHogMTFnKSBic3NpZCAxYzphZjpmNzpmMzo0MjpjMQoJcmVnZG9tYWluIEZDQyBp bmRvb3IgZWNtIGF1dGhtb2RlIFdQQSBwcml2YWN5IE1JWEVEIGRlZnR4a2V5IDIKCUFFUy1DQ00g MjoxMjgtYml0IEFFUy1DQ00gMzoxMjgtYml0IHR4cG93ZXIgMjcgc2NhbnZhbGlkIDYwCglwcm90 bW9kZSBDVFMgd21lIGJ1cnN0IGR0aW1wZXJpb2QgMSAtZGZzCg== --_003_A838E171DD71354E99079424FC4F7DDB182A9042CH1PRD0502MB118_-- From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 1 20:48:50 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D002106564A for ; Sun, 1 Jan 2012 20:48:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA078FC13 for ; Sun, 1 Jan 2012 20:48:50 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so20568199vbb.13 for ; Sun, 01 Jan 2012 12:48:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kgpzp4C1zDwzR0W9vxKbjtQ/teR/dF3jW9ek+mVF5nA=; b=f9tHC4OaGQ1IKlCvK7r1jgL0FxOtq2Ckq+L7hLZLgsNa9ev7tURoKJGM//mZcfLSUA SecLHeCO65X7hNzNs6xR70YUitw5AH+6QuWKiEq2ba+KrQLa/iJk5IHzSlSRjroR2KZk ctMq3KOttNDk1rZoWOoJlr+QSgFkHN/OgNHiU= MIME-Version: 1.0 Received: by 10.52.29.16 with SMTP id f16mr22035462vdh.45.1325450929590; Sun, 01 Jan 2012 12:48:49 -0800 (PST) Received: by 10.52.36.5 with HTTP; Sun, 1 Jan 2012 12:48:49 -0800 (PST) In-Reply-To: References: Date: Sun, 1 Jan 2012 12:48:49 -0800 Message-ID: From: Adrian Chadd To: "Lay, Nathan" Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" Subject: Re: ath "stops working" in hostap mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2012 20:48:50 -0000 Hi, Can you please wrap up all the attachments and stuff you've sent me and submit a PR for this? It looks like another noisy air problem. Or, something is configuring the radio in a way that completely messes up the noise. Try setting dev.ath.0.hal.force_full_reset to 1 if you're running -HEAD. Although I'm still not convinced I've done the "full reset" code entirely right.. Basically, some of the PHY parameters don't seem to be fully reset after a warm reset - they require a cold reset. I've noticed this on the AR9280, where things will get sufficiently upset as to force a storm of stuck beacons to appear. The only thing that fixes it is a complete power down and up of the PHY/radio, which we can do inside software. (We can't power down a few things on the NIC, but we can reset enough things for the RF issues to clear up.) There's another potential bug with the ANI code and how the PHY registers are read. It has the potential to make garbage choices and program in some terrible values to the signal detection/size/level PHY registers. I haven't yet sat down to write the solution to that. I really should. :) So please, file a PR so I don't forget to chase this stuff down. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 2 05:19:01 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 736C0106566B; Mon, 2 Jan 2012 05:19:01 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 49A678FC18; Mon, 2 Jan 2012 05:19:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q025J1jc048927; Mon, 2 Jan 2012 05:19:01 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q025J1Rc048923; Mon, 2 Jan 2012 05:19:01 GMT (envelope-from linimon) Date: Mon, 2 Jan 2012 05:19:01 GMT Message-Id: <201201020519.q025J1Rc048923@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/163759: [at] ath(4) "stops working" in hostap mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2012 05:19:01 -0000 Old Synopsis: ath(4) "stops working" in hostap mode New Synopsis: [at] ath(4) "stops working" in hostap mode Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 2 05:18:43 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=163759 From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 2 06:20:13 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 446291065673 for ; Mon, 2 Jan 2012 06:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 330598FC13 for ; Mon, 2 Jan 2012 06:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q026KCJI005015 for ; Mon, 2 Jan 2012 06:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q026KCxU005014; Mon, 2 Jan 2012 06:20:12 GMT (envelope-from gnats) Date: Mon, 2 Jan 2012 06:20:12 GMT Message-Id: <201201020620.q026KCxU005014@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Adrian Chadd Cc: Subject: Re: kern/163759: [at] ath(4) "stops working" in hostap mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2012 06:20:13 -0000 The following reply was made to PR kern/163759; it has been noted by GNATS. From: Adrian Chadd To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/163759: [at] ath(4) "stops working" in hostap mode Date: Sun, 1 Jan 2012 22:16:21 -0800 A little more digging has shown at least one source of these: software retries are sneaking onto the list. Ie: * force 11n aggregation up - do a whole bunch of traffic; * enabled debugging - sysctl dev.ath.1.debug=0x7c002000 - that's the SW TX handling bits and the TX_PROC debugging; * ping -i 0.3 in one screen * scan in the other (ifconfig wlan1 scan) * notice the tid_drain things being logged. What I've seen: * frame is queued via ath_start() or ath_raw_xmit() * .. it makes it out to the hardware * ath_tx_processq() is called in the flush routine, with dosched=0 * .. and it requires a retry, for reasons I haven't yet figured out. Since aggregation is up, the frame is retried in software. * .. so the frame is replaced on the software queue, but sched isn't called for it, so it sits on the software queue. * .. then drain is called, with a software-queued frame in the queue. So now, what should I do here? Hum. adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 2 11:07:17 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32E2C106566B for ; Mon, 2 Jan 2012 11:07:17 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1644B8FC1F for ; Mon, 2 Jan 2012 11:07:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q02B7G7v005298 for ; Mon, 2 Jan 2012 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q02B7Gh6005296 for freebsd-wireless@FreeBSD.org; Mon, 2 Jan 2012 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Jan 2012 11:07:16 GMT Message-Id: <201201021107.q02B7Gh6005296@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 Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2012 11:07:17 -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/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/163318 wireless [ath] ath(4) stops working o kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath 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/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/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using 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 p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e 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 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 62 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 4 07:20:06 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD05C106566B for ; Wed, 4 Jan 2012 07:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A73798FC0A for ; Wed, 4 Jan 2012 07:20:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q047K6QN092527 for ; Wed, 4 Jan 2012 07:20:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q047K68h092526; Wed, 4 Jan 2012 07:20:06 GMT (envelope-from gnats) Date: Wed, 4 Jan 2012 07:20:06 GMT Message-Id: <201201040720.q047K68h092526@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joel Dahl List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 07:20:06 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: bug-followup@freebsd.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working Date: Wed, 4 Jan 2012 08:18:46 +0100 This is the output in /var/log messages when running wlandebug +state +power (it dies as usual after a few hours). Output starts from right after the machine has been booted. Jan 3 17:27:24 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:27:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 17:32:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:32:29 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 17:37:29 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:37:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 17:42:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:42:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 17:43:37 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 17:47:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:47:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 17:52:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:52:39 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 17:57:39 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 17:57:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:02:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:02:44 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:07:44 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:07:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:12:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:12:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:17:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:17:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:22:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:22:54 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:27:54 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:27:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:32:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:32:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:37:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:38:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:43:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:43:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:43:36 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 18:48:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:48:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:53:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:53:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 18:58:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 18:58:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:03:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:03:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:08:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:08:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:13:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:13:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:18:19 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:18:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:23:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:23:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:28:24 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:28:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:33:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:33:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:38:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:38:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:43:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:43:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:43:36 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 19:48:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:48:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:53:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:53:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 19:58:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 19:58:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:03:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:03:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:08:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:08:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:13:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:13:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:18:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:18:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:23:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:23:53 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:28:53 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:28:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:33:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:33:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:38:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:39:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:43:37 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 20:44:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:44:03 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:49:03 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:49:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:54:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:54:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 20:59:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 20:59:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:04:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:04:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:09:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:09:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:14:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:14:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:19:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:19:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:24:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:24:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:29:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:29:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:33:39 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 21:34:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:34:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:39:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:39:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:44:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:44:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:49:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:49:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:54:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:54:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 21:59:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 21:59:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:04:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:04:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:09:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:09:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:14:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:14:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:19:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:19:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:24:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:24:53 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:29:53 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:29:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:33:39 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 22:34:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:34:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:39:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:40:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:45:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:45:03 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:50:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:50:07 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 22:55:07 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 22:55:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 23:00:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 23:00:12 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 23:03:09 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Jan 3 23:05:12 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 23:05:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 3 23:10:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 3 23:22:27 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 40, 1 now queued Jan 3 23:22:32 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 2 now queued Jan 3 23:22:40 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 3 now queued Jan 3 23:22:50 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 4 now queued Jan 3 23:23:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 5 now queued Jan 3 23:23:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 6 now queued Jan 3 23:23:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 7 now queued Jan 3 23:23:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 8 now queued Jan 3 23:23:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 9 now queued Jan 3 23:23:52 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 10 now queued Jan 3 23:24:05 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 11 now queued Jan 3 23:24:22 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 12 now queued Jan 3 23:24:52 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 13 now queued Jan 3 23:25:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 14 now queued Jan 3 23:25:10 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 15 now queued Jan 3 23:25:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 16 now queued Jan 3 23:26:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 17 now queued Jan 3 23:26:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 18 now queued Jan 3 23:26:52 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 19 now queued Jan 3 23:27:20 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 20 now queued Jan 3 23:27:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 21 now queued Jan 3 23:28:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 22 now queued Jan 3 23:29:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 23 now queued Jan 3 23:29:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 24 now queued Jan 3 23:30:00 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 25 now queued Jan 3 23:30:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 26 now queued Jan 3 23:30:40 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 27 now queued Jan 3 23:30:50 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 28 now queued Jan 3 23:31:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 29 now queued Jan 3 23:31:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 30 now queued Jan 3 23:31:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 31 now queued Jan 3 23:32:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 32 now queued Jan 3 23:33:15 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 33 now queued Jan 3 23:35:02 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 34 now queued Jan 3 23:36:20 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 35 now queued Jan 3 23:37:32 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 36 now queued Jan 3 23:37:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 37 now queued Jan 3 23:37:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 38 now queued Jan 3 23:38:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 39 now queued Jan 3 23:38:25 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 40 now queued Jan 3 23:38:37 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 41 now queued Jan 3 23:38:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 42 now queued Jan 3 23:39:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 43 now queued Jan 3 23:39:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 44 now queued Jan 3 23:39:20 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 45 now queued Jan 3 23:39:35 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 46 now queued Jan 3 23:39:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 47 now queued Jan 3 23:40:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 48 now queued Jan 3 23:40:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 49 now queued Jan 3 23:40:45 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 50 now queued Jan 3 23:41:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 1 (size 50) Jan 3 23:41:40 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 2 (size 50) Jan 3 23:42:24 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 3 (size 50) Jan 3 23:44:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 4 (size 50) Jan 3 23:44:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 5 (size 50) Jan 3 23:45:55 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 6 (size 50) Jan 3 23:47:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 7 (size 50) Jan 3 23:48:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 8 (size 50) Jan 3 23:51:45 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 9 (size 50) Jan 3 23:52:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 10 (size 50) Jan 3 23:52:32 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 11 (size 50) Jan 3 23:52:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 12 (size 50) Jan 3 23:52:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 13 (size 50) Jan 3 23:53:00 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 14 (size 50) Jan 3 23:53:17 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 15 (size 50) Jan 3 23:58:29 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 16 (size 50) Jan 3 23:58:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 17 (size 50) Jan 3 23:58:47 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 18 (size 50) Jan 3 23:59:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 19 (size 50) Jan 3 23:59:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 20 (size 50) Jan 4 00:04:30 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 21 (size 50) Jan 4 00:04:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 22 (size 50) Jan 4 00:04:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 23 (size 50) Jan 4 00:04:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 24 (size 50) Jan 4 00:05:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 25 (size 50) Jan 4 00:05:29 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 26 (size 50) Jan 4 00:10:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 27 (size 50) Jan 4 00:10:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 28 (size 50) Jan 4 00:10:42 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 29 (size 50) Jan 4 00:10:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 30 (size 50) Jan 4 00:11:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 31 (size 50) Jan 4 00:11:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 32 (size 50) Jan 4 00:16:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 33 (size 50) Jan 4 00:16:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 34 (size 50) Jan 4 00:16:44 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 35 (size 50) Jan 4 00:16:55 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 36 (size 50) Jan 4 00:17:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 37 (size 50) Jan 4 00:17:30 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 38 (size 50) Jan 4 00:22:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 39 (size 50) Jan 4 00:22:40 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 40 (size 50) Jan 4 00:22:47 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 41 (size 50) Jan 4 00:23:00 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 42 (size 50) Jan 4 00:23:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 43 (size 50) Jan 4 00:23:20 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 44 (size 50) Jan 4 00:28:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 45 (size 50) Jan 4 00:28:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 46 (size 50) Jan 4 00:28:55 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 47 (size 50) Jan 4 00:29:07 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 48 (size 50) Jan 4 00:29:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 49 (size 50) Jan 4 00:29:29 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 50 (size 50) One more thing, when I rebooted the machine after ath(4) stopped working the following messages quickly flashed by on the screen while it was shutting down: wlan0: [f8:1e:df:fc:34:2b] station deauth via MLME (reason 3) wlan0: ieee80211_new_state_locked: RUN -> INIT (nrunning 0 nscanning 0) wlan0: ieee80211_newstate_cb: RUN -> INIT arg 3 wlan0: sta_newstate: RUN -> INIT (3) ath0: ath_tx_tid_drain: node 0xffffff80014a2000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_stat=-1, ni_txseqs=1782 wlan0: [f8:1e:df:fc:34:2b] power save mode off, 0 sta's in ps mode wlan0: link state changed to DOWN wlan0: stop running, 1 vaps running wlan0: ieee80211_new_state_locked: RUN -> INIT (nrunning 0 nscanning 0) wlan0: down parent ath0 wlan0: ieee80211_newstate_cb: INIT -> INIT arg -1 wlan0: sta_newstate: INIT -> INIT (-1) wlan0: sta_newstate: unexpected state transition INIT -> INIT It looks like it managed come out of power save mode again? -- Joel From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 4 07:25:38 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7E9F10656D2; Wed, 4 Jan 2012 07:25:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 69B0E8FC1B; Wed, 4 Jan 2012 07:25:38 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so22444601vcb.13 for ; Tue, 03 Jan 2012 23:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=FRjVpQcjdBiPHQUBmJs9ySOnsJhlkxA9NxqdXoPQB+I=; b=RjOpXnwHHGCbHFy1lpmfotdseJYUhgAHqbPloGbj9R+Jfe5ZfxqYVooncKQ1NpHfYx 0xkqOrSsrgboqzrUl7qg2SMb8vFfnRQSZBOYWclxiXA78nF0TTUv2NI1YnwfkMsvLQ1M /r6skVTacdzZGv0aL8pXcbMkBqyhlhxOePnlM= MIME-Version: 1.0 Received: by 10.220.148.201 with SMTP id q9mr11641918vcv.33.1325661937596; Tue, 03 Jan 2012 23:25:37 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Tue, 3 Jan 2012 23:25:37 -0800 (PST) In-Reply-To: <201201040720.q047K68h092526@freefall.freebsd.org> References: <201201040720.q047K68h092526@freefall.freebsd.org> Date: Tue, 3 Jan 2012 23:25:37 -0800 X-Google-Sender-Auth: KCHMmro2SFp6KnSNdFA3NizorU0 Message-ID: From: Adrian Chadd To: Joel Dahl Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 07:25:38 -0000 Hi, Thanks for that. Hm. The problem is still not clear. There's no state transition, so I guess it's going into scan mode and out of scan mode again. How about doing this: wlandebug +state +power sysctl dev.ath.X.debug=0x00040000 That enables the _driver_ state checking. That should log when ath_scan_start and ath_scan_end are called. This is definitely a tricky one.. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 5 02:40:13 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54AB91065670 for ; Thu, 5 Jan 2012 02:40:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 432688FC15 for ; Thu, 5 Jan 2012 02:40:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q052eDTt090827 for ; Thu, 5 Jan 2012 02:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q052eDt5090826; Thu, 5 Jan 2012 02:40:13 GMT (envelope-from gnats) Date: Thu, 5 Jan 2012 02:40:13 GMT Message-Id: <201201050240.q052eDt5090826@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Adrian Chadd Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2012 02:40:13 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Adrian Chadd To: bug-followup@FreeBSD.org, joel@FreeBSD.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working Date: Wed, 4 Jan 2012 18:34:39 -0800 Hi, Please try this patch: Index: sys/net80211/ieee80211_power.c =================================================================== --- sys/net80211/ieee80211_power.c (revision 228893) +++ sys/net80211/ieee80211_power.c (working copy) @@ -504,8 +504,13 @@ { struct ieee80211_node *ni = vap->iv_bss; - if (!((enable != 0) ^ ((ni->ni_flags & IEEE80211_NODE_PWR_MGT) != 0))) + if (!((enable != 0) ^ + ((ni->ni_flags & IEEE80211_NODE_PWR_MGT) != 0))) { + IEEE80211_NOTE(vap, IEEE80211_MSG_POWER, ni, + "sta power save mode %s ignored", + enable ? "on" : "off"); return; + } IEEE80211_NOTE(vap, IEEE80211_MSG_POWER, ni, "sta power save mode %s", enable ? "on" : "off"); .. then just enable wlandebug +power. I'd like to see whether the station power management enable is being ignored for some reason. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 6 17:50:11 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 121C61065676 for ; Fri, 6 Jan 2012 17:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F07958FC13 for ; Fri, 6 Jan 2012 17:50:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q06HoAV2024159 for ; Fri, 6 Jan 2012 17:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q06HoACU024153; Fri, 6 Jan 2012 17:50:10 GMT (envelope-from gnats) Date: Fri, 6 Jan 2012 17:50:10 GMT Message-Id: <201201061750.q06HoACU024153@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joel Dahl List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2012 17:50:11 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: Adrian Chadd Cc: bug-followup@FreeBSD.org Subject: Re: kern/163318: [ath] ath(4) stops working Date: Fri, 6 Jan 2012 18:44:56 +0100 I've tried your patch now, but it didn't trigger any new messages. Output looks like this (it only took about 30 minutes after boot before it stopped working this time, must be a new record...): Jan 6 17:28:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 6 17:29:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 6 17:34:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 6 17:34:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 6 17:39:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 6 17:39:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 6 17:44:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 6 17:44:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 6 17:49:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 6 17:49:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 6 17:54:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode on Jan 6 17:57:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 40, 1 now queued Jan 6 17:57:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 2 now queued Jan 6 17:57:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 3 now queued Jan 6 17:57:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 4 now queued Jan 6 18:15:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 5 now queued Jan 6 18:15:32 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 6 now queued Jan 6 18:15:37 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 7 now queued Jan 6 18:16:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 8 now queued Jan 6 18:17:03 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 9 now queued Jan 6 18:17:05 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 10 now queued Jan 6 18:17:15 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 11 now queued Jan 6 18:17:24 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 12 now queued Jan 6 18:17:25 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 13 now queued Jan 6 18:17:26 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 14 now queued Jan 6 18:17:27 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 15 now queued Jan 6 18:17:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 16 now queued Jan 6 18:17:29 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 17 now queued Jan 6 18:17:30 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 18 now queued Jan 6 18:17:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 19 now queued Jan 6 18:17:32 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 20 now queued Jan 6 18:17:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 21 now queued Jan 6 18:17:34 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 22 now queued Jan 6 18:17:35 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 23 now queued Jan 6 18:17:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 24 now queued Jan 6 18:17:37 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 25 now queued Jan 6 18:17:38 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 26 now queued Jan 6 18:17:39 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 27 now queued Jan 6 18:17:40 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 28 now queued Jan 6 18:17:41 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 29 now queued Jan 6 18:17:42 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 30 now queued Jan 6 18:17:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 31 now queued Jan 6 18:17:44 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 32 now queued Jan 6 18:17:45 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 33 now queued Jan 6 18:17:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 34 now queued Jan 6 18:17:47 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 35 now queued Jan 6 18:17:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 36 now queued Jan 6 18:17:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 37 now queued Jan 6 18:17:50 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 38 now queued Jan 6 18:17:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 39 now queued Jan 6 18:17:52 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 40 now queued Jan 6 18:17:53 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 41 now queued Jan 6 18:21:02 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 42 now queued Jan 6 18:21:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 43 now queued Jan 6 18:21:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 44 now queued Jan 6 18:21:10 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 45 now queued Jan 6 18:21:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 46 now queued Jan 6 18:21:12 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 47 now queued Jan 6 18:21:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 48 now queued Jan 6 18:21:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 49 now queued Jan 6 18:21:15 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] save frame with age 0, 50 now queued Jan 6 18:21:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 1 (size 50) Jan 6 18:21:17 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 2 (size 50) Jan 6 18:21:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 3 (size 50) Jan 6 18:21:19 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 4 (size 50) Jan 6 18:21:20 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 5 (size 50) Jan 6 18:21:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 6 (size 50) Jan 6 18:21:22 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 7 (size 50) Jan 6 18:21:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 8 (size 50) Jan 6 18:21:24 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 9 (size 50) Jan 6 18:21:25 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 10 (size 50) Jan 6 18:23:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 11 (size 50) Jan 6 18:24:03 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 12 (size 50) Jan 6 18:24:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 13 (size 50) Jan 6 18:24:17 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 14 (size 50) Jan 6 18:24:27 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 15 (size 50) Jan 6 18:24:40 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 16 (size 50) Jan 6 18:24:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 17 (size 50) Jan 6 18:25:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 18 (size 50) Jan 6 18:26:35 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 19 (size 50) Jan 6 18:26:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 20 (size 50) Jan 6 18:26:50 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 21 (size 50) Jan 6 18:26:51 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 22 (size 50) Jan 6 18:26:52 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 23 (size 50) Jan 6 18:26:53 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 24 (size 50) Jan 6 18:26:54 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 25 (size 50) Jan 6 18:26:55 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 26 (size 50) Jan 6 18:26:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 27 (size 50) Jan 6 18:26:57 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 28 (size 50) Jan 6 18:26:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 29 (size 50) Jan 6 18:26:59 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 30 (size 50) Jan 6 18:27:00 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 31 (size 50) Jan 6 18:27:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 32 (size 50) Jan 6 18:27:02 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 33 (size 50) Jan 6 18:27:03 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 34 (size 50) Jan 6 18:27:04 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 35 (size 50) Jan 6 18:27:05 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 36 (size 50) Jan 6 18:27:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 37 (size 50) Jan 6 18:27:07 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 38 (size 50) Jan 6 18:27:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 39 (size 50) Jan 6 18:27:09 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 40 (size 50) Jan 6 18:27:10 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 41 (size 50) Jan 6 18:27:11 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 42 (size 50) Jan 6 18:27:12 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 43 (size 50) Jan 6 18:27:13 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 44 (size 50) Jan 6 18:27:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 45 (size 50) Jan 6 18:27:15 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 46 (size 50) Jan 6 18:27:16 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 47 (size 50) Jan 6 18:27:17 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 48 (size 50) Jan 6 18:27:18 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 49 (size 50) Jan 6 18:27:19 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 50 (size 50) Jan 6 18:27:20 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 51 (size 50) Jan 6 18:27:21 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 52 (size 50) Jan 6 18:27:22 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 53 (size 50) Jan 6 18:27:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 54 (size 50) Jan 6 18:27:24 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 55 (size 50) However, here I did a "ifconfig wlan0 scan", and got these messages: Jan 6 18:27:25 crashbox wpa_supplicant[475]: CTRL-EVENT-DISCONNECTED bssid=f8:1e:df:fc:34:2b reason=0 Jan 6 18:27:25 crashbox kernel: ath0: ath_tx_tid_drain: node 0xffffff80014a2000: tid 16: txq_depth=0, txq_aggr_depth=0, sched=1, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=137 Jan 6 18:27:25 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 56 (size 50) Jan 6 18:27:25 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off Jan 6 18:27:25 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] flush ps queue, 50 packets queued Jan 6 18:27:25 crashbox kernel: ath0: ath_tx_tid_drain: node 0xffffff80014a2000: tid 0: txq_depth=37, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=36, incomp=0, baw_head=0, baw_tail=0 txa_start=0, ni_txseqs=189 Jan 6 18:27:25 crashbox kernel: wlan0: link state changed to DOWN Jan 6 18:27:28 crashbox wpa_supplicant[475]: Trying to associate with f8:1e:df:fc:34:2b (SSID='DAHL' freq=2412 MHz) Jan 6 18:27:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off ignored Jan 6 18:27:28 crashbox kernel: wlan0: link state changed to UP Jan 6 18:27:28 crashbox wpa_supplicant[475]: Associated with 00:00:00:00:00:00 Jan 6 18:27:28 crashbox kernel: wlan0: link state changed to DOWN Jan 6 18:27:28 crashbox wpa_supplicant[475]: CTRL-EVENT-DISCONNECTED bssid=f8:1e:df:fc:34:2b reason=0 Jan 6 18:27:30 crashbox kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost Jan 6 18:27:30 crashbox last message repeated 3 times Jan 6 18:27:31 crashbox wpa_supplicant[475]: Trying to associate with f8:1e:df:fc:34:2b (SSID='DAHL' freq=2412 MHz) Jan 6 18:27:31 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] sta power save mode off ignored Jan 6 18:27:31 crashbox wpa_supplicant[475]: Associated with f8:1e:df:fc:34:2b Jan 6 18:27:31 crashbox kernel: wlan0: link state changed to UP Jan 6 18:27:31 crashbox wpa_supplicant[475]: WPA: Key negotiation completed with f8:1e:df:fc:34:2b [PTK=CCMP GTK=CCMP] Jan 6 18:27:31 crashbox wpa_supplicant[475]: CTRL-EVENT-CONNECTED - Connection to f8:1e:df:fc:34:2b completed (reauth) [id=0 id_str=] Jan 6 18:27:38 crashbox dhclient: New IP Address (wlan0): 10.10.10.238 Jan 6 18:27:38 crashbox dhclient: New Subnet Mask (wlan0): 255.255.255.0 Jan 6 18:27:38 crashbox dhclient: New Broadcast Address (wlan0): 10.10.10.255 Jan 6 18:27:38 crashbox dhclient: New Routers (wlan0): 10.10.10.1 ...and it's working again. So, "ifconfig wlan0 scan" seems to be an easy way to get it working again after it has died. -- Joel From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 7 08:40:08 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBD6A106564A for ; Sat, 7 Jan 2012 08:40:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 911658FC0A for ; Sat, 7 Jan 2012 08:40:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q078e8ha075775 for ; Sat, 7 Jan 2012 08:40:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q078e88F075774; Sat, 7 Jan 2012 08:40:08 GMT (envelope-from gnats) Date: Sat, 7 Jan 2012 08:40:08 GMT Message-Id: <201201070840.q078e88F075774@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joel Dahl List-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, 07 Jan 2012 08:40:08 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: bug-followup@freebsd.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sat, 7 Jan 2012 09:37:17 +0100 Some more information: Adrian requested that I set the following sysctl in order to collect more debugging information: wlandebug +state +power sysctl dev.ath.0.debug=0x00040000 However, wireless never stops working once the above is set, so it's hard to get any useful information. The machine has 1 CPU, with 2 cores. The NIC is PCI. The exact model of the NIC is: D-Link RangeBooster N 650 Desktop Adapter DWA-547 -- Joel