Bug 13168
Summary: | ath5k fails to associate with AP | ||
---|---|---|---|
Product: | Networking | Reporter: | Thomas Meyer (thomas) |
Component: | Wireless | Assignee: | networking_wireless (networking_wireless) |
Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
Severity: | normal | CC: | linville, me, rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.30-rc3 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 13070 | ||
Attachments: |
config file
dmesg |
Description
Thomas Meyer
2009-04-25 14:04:42 UTC
Created attachment 21116 [details]
config file
Created attachment 21117 [details]
dmesg
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: http://marc.info/?l=linux-wireless&m=123841474910111&w=2 linked to patch fixes this bug for me! Thanks. Will this patch go into linus' tree? It is currently queued for 2.6.31... |