On Thu, Sep 18, 2008 at 02:49:45PM -0700, Steven Noonan wrote: > > No, it's in hex. 0x17 = 23, 0x11 = 17. IRQ 17 is the one that pooped > in my case, which is my wireless chipset. Ah - boo. > 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. > > Patches speak more than words, but yeah sorry, we should have > > addressed this there. I've personally have just been busy with > > tackling aggregation. > > > > 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. Luis -- 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
