From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Date: Mon, 25 Mar 2013 02:38:49 -0700 Subject: [ath9k-devel] ath9k not connecting to one particular network.. In-Reply-To: References: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Mon, Mar 25, 2013 at 2:23 AM, Linus Torvalds wrote: > > Interestingly, the kernel messages from doing this were different: > > wlan0: RX AssocResp from 50:46:5d:02:85:08 (capab=0x411 status=0 aid=16) > > notice how now it says "aid=16" instead of "aid=10". WTF? This seems to be irrelevant. Restarting NetworkManager (just to test) still didn't give me a working connection, but I got that "aid=16" again. So the driver messages don't tell me anything, except that NM does *something* that triggers that wlan0: disassociating from 50:46:5d:02:85:08 by local choice (reason=3) immediately after associating. It also results in cfg80211: Calling CRDA to update world regulatory domain and then all the frequencies are shown again, so I assume it's some kind of link reset. "reason=3" seems to be WLAN_REASON_DEAUTH_LEAVING. I'll do a NM bug-report, but if somebody has a clue what NM might be doing that would trigger this (when running wpa_supplicant manually does not), that would be lovely to add to the bugreport. Linus