Felix Fietkau wrote: > On 2011-03-10 10:55 PM, Mark Mentovai wrote: >> Based on the message you sent with patch 2/4, “I can no longer trigger >> these messages on AR9380, and on AR9280 they become much more rare,” >> and the fact that you left the message intact in that patch’s >> ath_drain_all_txq, I wonder it’s appropriate to remove the message >> from this function. > Anything beacon related will report stuck beacons if frames stay in the > queue until the next interval, so there is some degree of reporting > there already. OK, that makes sense. The stuck-beacon logging is ath_dbg, but that’s probably enough given what ath_beacon_tasklet tries to do to recover from a stuck beacon. I think I just get antsy when I see that ath_reset might be called quietly, because it’s a big hammer. No Big Deal. -- 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
