On Tue, Aug 25, 2009 at 2:58 PM, Luis R. Rodriguez<lrodriguez@xxxxxxxxxxx> wrote: > OK how about the band info, think that's useful? Yeah, band is useful. We don't have to pretty print it though (unless you really feel like it), %d would work just as well. Also WARN_ON_ONCE might be a good idea. >> which could indicate some >> race condition with flushing the rx queue on channel changes. > > I'll see if I can reproduce somehow. > >> I haven't yet seen a hw rate we didn't know about. > > So you've seen this lately as well? I saw it some time ago, but then changed the order of how the curchan/curband variables were set when we change channels and haven't seen since. But kerneloops says a lot of other people are still hitting it as well :( Hmm, ath5k_rx_stop probably wants an equivalent to txq_drainq in there somewhere. -- Bob Copeland %% www.bobcopeland.com -- 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
