On Thu, Sep 18, 2008 at 3:01 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: >> If I do, I'll need to know what precisely to do about it. What debug >> info should I collect before rebooting? > > Sure, OK so in ath9k's core.h we have a macro used to indicate what > type of debugging stuff gets print out. By default we only leave > enabled the fatal stuff. > > #define DBG_DEFAULT (ATH_DBG_FATAL ) > > You want to add to this ATH_DBG_INTERRUPT as follows: > > #define DBG_DEFAULT (ATH_DBG_FATAL | ATH_DBG_INTERRUPT) > > Then since the issue seems to come up when you rmmod, simply try to > download do some large RXing or TXing or both and then rmmod. Capture > the output and send along. Will do! And actually, to be precise, the issue occurred not on the rmmod, but on the following modprobe for ath9k. >> Which is far more important, I agree. It's annoying to get speeds >> <802.11b on my pre-802.11n capable chipset and network. ;) > > Yeah exactly, I hope the work we do will get in for 27. We'll see. Linus has been fairly strict lately, so I am as uncertain as you are. It really should get merged, because having 2.6.27 with [partially] broken wireless networking is kind of stupid. In the worst case, isn't it possible to do a revert to get the old aggregation crap back in? -- 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
