Bug 14196
| Summary: | Wireless cards cannot associate to APs (wpa_supplicant keeps doing scans) | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Fabio Scaccabarozzi (fsvm88) |
| Component: | Wireless | Assignee: | networking_wireless (networking_wireless) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | francoisvalenduc, linville |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.32-rc0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | dmesg non-working output | ||
This should be fixed in 2.6.32-rc1. *** Bug 14202 has been marked as a duplicate of this bug. *** Yep, fixed. Thanks. |
Created attachment 23121 [details] dmesg non-working output I'm running b43 driver on amd64, I upgraded to the latest git after running 2.6.31-rc9 for some time and found connection not working. Attached there's a log of the b43 driver. Running iwevent showed that it kept cycling through scans but never associating. Initially I thought it was a problem with b43 itself but trying to upgrade also on the laptop (ath5k on x86) showed the very same problem. I bisected the commits and found the culprit: cfg80211: fix SME connect (bbac31f4c0339f6c51afbd0edfb4959df9b53fa9) Reverting the commit fixes the issues, connection works again.