Andreas Hartmann schrieb: > Hello Helmut, > > Am Tue, 10 Jan 2012 10:50:16 +0100 > schrieb Helmut Schaa <helmut.schaa@xxxxxxxxxxxxxx>: > >> On Tue, Jan 10, 2012 at 9:03 AM, Andreas Hartmann >> <andihartmann@xxxxxxxxxxxxxxx> wrote: > [...] >>> Looks as if sending of any package is reported as broken at some >>> point of time and this circle cannot be left anymore. >> >> Not necessarily since mac80211 will only retry the BAR if a data frame >> transmission was successful. Hence, it seems as if only the BARs TX >> status is reported incorrectly ... >> >> I see two issues here: >> 1) rt2800pci seems to have problems delivering the BAR _or_ doesn't >> report the tx status correctly >> 2) If the same BAR fails consecutively we should maybe really tear down >> the BA session as it was done before >> >> 2 is done in the below untested patch and will also work around 1. >> Mind to give it a try? > > I encountered some temporary, short stalls during low bandwith > (running X terminal sessions tunneled through ssh). Therefore I set > > MAX_BAR_RETRIES=0 > > This means, > > ieee80211_send_bar(&sta->sdata->vif, addr, tid, > tid_tx->failed_bar_ssn); > > isn't called any more. But that's not all: the BA session isn't torn > down any more, too - but it's working fine (high bandwith, too) anyway!? > Why? (If I remove your patch again, the session completely stalls as > ever). Cool, this behaves completely other with ath9k-based STA. In the latter, I'm "sometimes" getting entries like these in messages of the AP: Jan 19 13:51:06 pc kernel: [17742.408040] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:51:19 pc kernel: [17755.342010] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:51:19 pc kernel: [17755.342013] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:51:19 pc kernel: [17755.342015] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:51:19 pc kernel: [17755.342016] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.271100] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.271106] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.271111] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.271114] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.271118] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.399106] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.399113] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.399117] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.399120] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:14 pc kernel: [17810.399124] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.581007] net_ratelimit: 3 callbacks suppressed Jan 19 13:52:59 pc kernel: [17855.581011] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.581013] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.581016] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.581018] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.581020] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.582015] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.582018] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.582020] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.582022] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames Jan 19 13:52:59 pc kernel: [17855.582023] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames nfs or streaming protocols aren't that happy with this situation. Iaw: it's unusable. All in one: Your workaround was a good idea, but unfortunately it doesn't "solve" / workaround the problem introduced with the patch "mac80211: retry sending failed BAR frames later instead of tearing down aggr" [1]. I don't know off any other solution at this time as to revert it. Do you have any idea how to fix the problem introduced with [1]? Kind regards and thank you! Andreas [1] http://www.spinics.net/lists/linux-wireless/msg76379.html -- 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
