ok, there were changes in this area to trigger faster in order to address some performance issue. so I believe more logic need to go in and delay the trigger in some cases. Would you be able to test for me if I have a patch for testing? Thanks Wey On Mon, 2011-11-14 at 13:18 -0800, Lars Schotte wrote: > of course he deactivates the aggregation soon after, because the AP > sees no reason why there should be one. > > triggering the aggreggation is that problem and it exists only since > 3.0.9. 3.0.8 is OK, but 3.1.1 seems to be affected as well. 3.1.0 was > OK. > > so someting broke it recently. > > unfortunately i can not remember if 3.2 kernel had that problem, i > already removed it because it was too unstable for me, so i can not > test it any more (w/o compiling it again). > > On Mon, 14 Nov 2011 12:38:21 -0800 > wwguy <wey-yi.w.guy@xxxxxxxxx> wrote: > > > Hi Schotte, > > > > looks like driver has problem activate the aggregation, you can see in > > the log, the aggregation queue being activate then deactivate soon > > after. that is why you are seeing the messages showing up in dmesg > > log. > > > > what AP you are using? is similar thing happen if you connect to > > different AP? > > > > Thanks > > Wey > > -- 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
