On 30 December 2012 06:19, Mohammed Shafi <shafi.wireless@xxxxxxxxx> wrote: > On Tue, Dec 11, 2012 at 3:31 PM, Cedric VONCKEN > <cedric.voncken@xxxxxxxxx> wrote: >> Any suggestion to fix correctly this issue ? > > having a count to break out from the loop is bit hacky. I would > suggest to enable as many prints and see > why the infinite loop counts(ofcourse you can have a loop count to > figure out and break the loop). IMHO both need to be done. It's possible that it's taking way too long to handle frames in the driver layer. The ath/ath9k driver layer assumes that it can dequeue frames from the hardware FASTER than it can queue those frames to the network stack layer. If the latter falls behind (or both, really) then you can hit this condition. FWIW, I've done this in FreeBSD's ath(4) driver in both the TX and RX path, to ensure that I give the tasklets all a fair crack at being scheduled. Adrian -- 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
