On 11 March 2015 at 17:22, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Wed, 2015-03-11 at 14:25 +0100, Michal Kazior wrote: >> NativeWifi tx mode expects QoS Data frames to be >> delivered as Data frames with QoS part (e.g. tid) >> being delievered out-of-band in fw tx command. >> >> The QoS bit wasn't stripped before submitting to >> firmware. >> >> Stripping fixes two known problems: >> >> * qca6174 IOT with some APs, e.g. >> Cisco AIR-AP 1252 (which would crash after >> ath10k association). Some ath9k APs would >> crash as well. > > It would probably be interesting to figure out why and fix that - this > is clearly a major issue. Good point. The patch was originally just a small fix for sniffing but it happened to fix the IOT problem that we started seeing with the new chip fw as well. I believe that if 11n was disabled on APs the problem did not reproduce. I think ath9k was crashing somewhere along the BA session teardown (as per kernel call trace). The ath9k codebase from what I know was rather old (some custom 3.4 fork) so perhaps it was a race of some sort that has been fixed long since. I'll try to get some sniff logs and take a look at this more closely. Michał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
