[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110504153819.GA4551@thinkpad-t410>
Date: Wed, 4 May 2011 10:38:19 -0500
From: Seth Forshee <seth.forshee@...onical.com>
To: Jiri Slaby <jirislaby@...il.com>,
Nick Kossifidis <mickflemm@...il.com>,
"Luis R. Rodriguez" <lrodriguez@...eros.com>,
Bob Copeland <me@...copeland.com>
Cc: "John W. Linville" <linville@...driver.com>,
linux-wireless@...r.kernel.org, ath5k-devel@...ts.ath5k.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: ath5k regression associating with APs in 2.6.38
I've been investigating some reports of a regression in associating with
APs with AR2413 in 2.6.38. Association repeatedly fails with some
"direct probe to x timed out" messages (see syslog excerpt below),
although it will generally associate eventually, after many tries.
Bisection identifies 8aec7af (ath5k: Support synth-only channel change
for AR2413/AR5413) as offending commit. Prior to this commit there are
no direct probe messages at all in the logs. I've also found that
forcing fast to false at the top of ath5k_hw_reset() fixes the issue.
I'm not sure what the connection is between this commit and the
timeouts. Any suggestions?
Thanks,
Seth
May 4 09:32:15 AcerAspire5100 wpa_supplicant[757]: Trying to associate with c0:3f:0e:b9:f3:b2 (SSID='aureola' freq=2452 MHz)
May 4 09:32:15 AcerAspire5100 kernel: [ 120.063271] wlan0: direct probe to c0:3f:0e:b9:f3:b2 (try 1/3)
May 4 09:32:16 AcerAspire5100 kernel: [ 120.260074] wlan0: direct probe to c0:3f:0e:b9:f3:b2 (try 2/3)
May 4 09:32:16 AcerAspire5100 kernel: [ 120.460084] wlan0: direct probe to c0:3f:0e:b9:f3:b2 (try 3/3)
May 4 09:32:16 AcerAspire5100 kernel: [ 120.660082] wlan0: direct probe to c0:3f:0e:b9:f3:b2 timed out
May 4 09:32:25 AcerAspire5100 wpa_supplicant[757]: Authentication with c0:3f:0e:b9:f3:b2 timed out.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists