On Fri, 2011-03-25 at 13:55 +0100, Helmut Schaa wrote: > So far the tx status as returned by the device look correct. I printed the > sequence numbers of failed AMPDU subframes and had a second device capturing > the traffic and compared them. > > But I noticed that there still appear holes from time to time that cause the > strange Intel driver stuck problem (which is really really strange and IMHO > the driver has a problem too). And it is not necessarily PS related. > > Johannes, what happens if a frame gets dropped on its way though the tx path > after getting a seqnr assigned? That would cause a hole in the sequence number > series without the chance to get a IEEE80211_TX_STAT_AMPDU_NO_BACK tx status. Yeah that's correct, try not to do that :) It's one of the reasons the Intel driver assigns its own sequence numbers to AMPDU frames (the other being some odd seqno/queue place match requirement.) johannes -- 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
