Bug 42062 - Receiving regulatory information causes loss of association
Summary: Receiving regulatory information causes loss of association
Status: RESOLVED INSUFFICIENT_DATA
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-30 15:35 UTC by Paul Martin
Modified: 2012-08-30 13:29 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.0+
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Paul Martin 2011-08-30 15:35:15 UTC 
This possibly only affects the ath5k driver.

The sequence to reproduce the possible race condition is:

You preferably need an access point that advertises its regulatory domain.

Associate to the access point.

Run "wpa_cli disconnect".

Wait a minute.

Run "wpa_cli reconnect".

Note the sequence in kernel log of roughly: default configured regdom being set; association succeeding; the "00" regdom being set; AP's regdom being set; loss of association.

Try "wpa_cli reconnect" again immediately. Same result.

Allow things to settle for a few minutes, then try "wpa_cli reconnect" again. It may or may not work.

For some reason, the first ever association to the AP never has a problem.
Comment 1 John W. Linville 2012-01-13 19:14:55 UTC 
Does this problem persist with 3.2 kernels?
Note You need to log in before you can comment on or make changes to this bug.