Bug 75231
Summary: | ath9k AR9485: intemittent failure to WPA 4way 1st msg: did not Ack EAPOL-Key frame | ||
---|---|---|---|
Product: | Drivers | Reporter: | David Hubbard (david.c.hubbard) |
Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
Status: | NEW --- | ||
Severity: | normal | CC: | ath9k-devel, kishanpgondaliya, linville, sujith |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | ubuntu 3.13.11, linux-next | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
lspci -nnv
syslog showing the one time it succeeded syslog of what it typically does, failure |
Description
David Hubbard
2014-05-01 11:01:01 UTC
Created attachment 134571 [details]
syslog showing the one time it succeeded
Created attachment 134581 [details]
syslog of what it typically does, failure
(In reply to David Hubbard from comment #0) > "modprobe ath9k nohwcrypt=1 debug=0x84f9" That was 0x8f49 actually, typo in submitting the bug report. Some additional testing makes it seem like an 11n issue: Fails to associate when STA "iw dev wlan0 link" is about -65 dBm or worse. When signal is better, it associates fine. By forcibly disabling 802.11n modes (patch below) the STA connects from positions it failed before, and the RSSI improves from -78 dBm to -60 dBm (approximate). diff --git a/drivers/net/wireless/ath/ath9k/init.c b/drivers/net/wireless/ath/ath9k/init.c index 9eea982..3a4c4e4 100644 --- a/drivers/net/wireless/ath/ath9k/init.c +++ b/drivers/net/wireless/ath/ath9k/init.c @@ -832,6 +832,8 @@ static void ath9k_init_txpower_limits(struct ath_softc *sc) void ath9k_reload_chainmask_settings(struct ath_softc *sc) { +#if 0 +forcibly disable all 802.11n modes if (!(sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_HT)) return; @@ -839,6 +841,7 @@ void ath9k_reload_chainmask_settings(struct ath_softc *sc) setup_ht_cap(sc, &sc->sbands[IEEE80211_BAND_2GHZ].ht_cap); if (sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_5GHZ) setup_ht_cap(sc, &sc->sbands[IEEE80211_BAND_5GHZ].ht_cap); +#endif } static const struct ieee80211_iface_limit if_limits[] = { Do you still see this issue with the latest kernel ? I will check tomorrow. I *think* so. Still showing the same problem. See "Steps to Reproduce" from comment #0 with the following changes: 5. STA kernel: ubuntu-3.16.4-92a0e72 cloned from git://kernel.ubuntu.com/ubuntu/ubuntu-vivid.git Problem: 1. Association only works when RSSI measures approx -78 dBm 2. The rest of the STA's I have access to report much better RSSI (approx -50 dBm) in the same physical location. 3. The link quality is poor at this location, approx 20KB/s and about 750ms latency. 4. The AP reports constant dissociations: Tue Oct 28 22:03:28 2014 daemon.info hostapd: wlan0: STA 44:6d:57:xx:xx:xx IEEE 802.11: disconnected due to excessive missing ACKs Tue Oct 28 22:03:29 2014 daemon.info hostapd: wlan0: STA 44:6d:57:xx:xx:Xx IEEE 802.11: authenticated Tue Oct 28 22:03:29 2014 daemon.info hostapd: wlan0: STA 44:6d:57:xx:xx:xx IEEE 802.11: associated (aid 2) Tue Oct 28 22:03:31 2014 daemon.info hostapd: wlan0: STA 44:6d:57:xx:xx:xx WPA: pairwise key handshake completed (RSN) Can you test the latest backports driver ? http://www.kernel.org/pub/linux/kernel/projects/backports/2014/10/23/backports-20141023.tar.xz Installation instructions are here: https://backports.wiki.kernel.org/index.php/Documentation Use the "ath9k-debug" config to build the driver: make defconfig-ath9k-debug && make && sudo make install With this driver, please post the contents of these files: /sys/kernel/debug/ieee80211/phy*/ath9k/base_eeprom /sys/kernel/debug/ieee80211/phy*/ath9k/modal_eeprom /sys/kernel/debug/ieee80211/phy*/ath9k/interrupt /sys/kernel/debug/ieee80211/phy*/ath9k/recv /sys/kernel/debug/ieee80211/phy*/ath9k/phy_err /sys/kernel/debug/ieee80211/phy*/ath9k/xmit /sys/kernel/debug/ieee80211/phy*/ath9k/reset /sys/kernel/debug/ieee80211/phy*/ath9k/misc I'll do the build you suggest this weekend. (In reply to David Hubbard from comment #9) > I'll do the build you suggest this weekend. Have you looked further into it? I am facing the same issue. |