On Wed, May 04, 2011 at 10:38:19AM -0500, Seth Forshee wrote: > 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? Have you tried reverting that commit on top of 2.6.38? Can you recreate the issue with 2.6.39-rc6 (or later)? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
