i looked over some changelogs .. from the linux kernel 3.1 branch. i saw that you ve introduced some patches to this, or you at least signed them off. the changelog also says that you've changed the logging level for that aggregation problem, so even if it would be there, it doesnt pop up on kernel 3.1's. i also did read there that there was like waiting for a real reason to move to aggregation. so it was there the whole time, only it did not write itself out on the log. so i am not sure if we were not just hunting ghosts here. On Mon, 14 Nov 2011 14:59:33 -0800 wwguy <wey-yi.w.guy@xxxxxxxxx> wrote: > ok, thanks > > please do let us know if it appear on 3.1.1 > > at the meantime, we will look into how to backport to 3.0.x > > Regards > Wey > > On Mon, 2011-11-14 at 14:56 -0800, Lars Schotte wrote: > > i definitely see it in 3.0.8 and 3.0.9. > > > > on the fedora fc16 linux kernel 3.1.1 it did not yet appear, but > > that may change. > > > > so maybe it would be worth a look if it is not fixed by 3.1.1, or if > > something changed. however ... if it is a FIX, it should definitely > > be fixed also in 3.0.X branch. > > > > so that message still is there on 3.0.9 and 3.0.8, we will see about > > the more current ones. > > > > On Mon, 14 Nov 2011 14:41:42 -0800 > > wwguy <wey-yi.w.guy@xxxxxxxxx> wrote: > > > > > so youno longer seeing the issue? > > > > > > Wey > > > > > > > > -- Lars Schotte @ Hana (F16) -- 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
