This commit in linus' tree can fix this issue and its in v3.14-rc6
commit 963a1852fbac4f75a2d938fa2e734ef1e6d4c044
Author: Johannes Berg <email address hidden>
Date: Fri Feb 21 20:34:34 2014 +0100
mac80211: don't validate unchanged AP bandwidth while tracking
The MLME code in mac80211 must track whether or not the AP changed
bandwidth, but if there's no change while tracking it shouldn't do
anything, otherwise regulatory updates can make it impossible to
connect to certain APs if the regulatory database doesn't match the
information from the AP. See the precise scenario described in the
code.
This still leaves some possible problems with CSA or if the AP
actually changed bandwidth, but those cases are less common and
won't completely prevent using it.
This commit in linus' tree can fix this issue and its in v3.14-rc6
commit 963a1852fbac4f7 5a2d938fa2e734e f1e6d4c044
Author: Johannes Berg <email address hidden>
Date: Fri Feb 21 20:34:34 2014 +0100
mac80211: don't validate unchanged AP bandwidth while tracking
The MLME code in mac80211 must track whether or not the AP changed
bandwidth, but if there's no change while tracking it shouldn't do
anything, otherwise regulatory updates can make it impossible to
connect to certain APs if the regulatory database doesn't match the
information from the AP. See the precise scenario described in the
code.
This still leaves some possible problems with CSA or if the AP
actually changed bandwidth, but those cases are less common and
won't completely prevent using it.
This fixes https:/ /bugzilla. kernel. org/show_ bug.cgi? id=70881
Cc: <email address hidden> and-tested- by: Nate Carlson <email address hidden>
Reported-
Signed-off-by: Johannes Berg <email address hidden>