Kernel Bug Tracker – Bug 13168
ath5k fails to associate with AP
Last modified: 2009-04-29 18:02:35 UTC
Don't know why. 220.127.116.11 works fine.
dmesg and config attached.
Created attachment 21116 [details]
Created attachment 21117 [details]
I unloaded ath5k module later, because the NetworkManager seemed to scan through all available frequencies again and again. This scanning used a lot of cpu.
Thanks for the report. I didn't see any association request -- I wonder if scan time is now exceeding network manager's built-in timeout. Any chance you could bisect just the changes in drivers/net/wireless/ath5k between 2.6.29 and 2.6.30 to see what broke?
Other possible things to try: configure wpa_supplicant to only scan a subset of the available frequencies, or try this patch:
linked to patch fixes this bug for me!
Thanks. Will this patch go into linus' tree?
It is currently queued for 2.6.31...