On Tue, Sep 6, 2011 at 9:39 AM, Christian Lamparter <chunkeey@xxxxxxxxxxxxxx> wrote: > On Monday, September 05, 2011 05:20:09 PM Mohammed Shafi wrote: >> On Sat, Sep 3, 2011 at 12:36 PM, Christian Lamparter >> <chunkeey@xxxxxxxxxxxxxx> wrote: >> > Minstrel HT tries very hard to establish a BA session with >> > each peer once there's some data on the way. However the >> > stack does not inform minstrel if an aggregation session >> > is already in place, so it keeps trying and wastes good >> > cycles in the tx status path. >> > >> > [ 8149.946393] Open BA session requested for $AP tid 0 >> > [ 8150.048765] Open BA session requested for $AP tid 0 >> > [ 8150.174509] Open BA session requested for $AP tid 0 >> > [ 8150.274376] Open BA session requested for $AP tid 0 >> > ... >> >> >> Hi Christian, >> >> I got this messages in ath9k after few cycles of suspend and resume. > There's nothing wrong with the message... as long as its reasonable > and does not spam the logs as in my case [had about 100k entries]. indeed, it spam's the log. > >> doing the same fix in ath9k rate control tx_status callback the >> messages did not re-appear. I will soon send a proper patch for ath9k >> too. > Well, ath9k's rc works different than minstrel_ht. In fact that check > is not needed as ath9k's rc can check the tid state directly in > ath_tx_aggr_check [which I think it already does... unless something > is wrong with the txtid->state check?!]. thanks, i will check into that. thanks, shafi -- 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
