Bug 205813
| Summary: | Freeze system via 802.11k beacon reports using ath9k | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | vincent |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 4.19.85-1-MANJARO | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
I use the TL-WN722N as client to connect to the AP. So the client will freeze and not the AP. |
Driver: ath9k Hardware: TL-WN722N I use OpenWrt as AP, there you can just enable rrm by ubus call hostapd.wlan0 bss_mgmt_enable '{"neighbor_report":True, "beacon_report":True}' then you can send beacon request messages ubus call hostapd.wlan0 rrm_beacon_req '{"addr":"00:xx:xx:xx:xx:xx", "op_class":0, "channel":13,"duration":4,"mode":0,"bssid":"ff:ff:ff:ff:ff:ff", "ssid":""}' Just send several requests and change the mode (between 0 and 2) and the channels. Suddenly, your whole system will freeze until you unplug the wireless device. I tried with different hardware (mt76x2u, AC-1200) and I had no problems. So, I think this is a bug in the ath9k driver. I think this bug is critical.