On Tue, 30 Mar 2010 08:03:06 +0200, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2010-03-29 at 10:26 -0700, Ben Gamari wrote: > > New (2.6.33 and greater) kernels seem to result in a selective hang on my > > machine directly only seconds after association with an 802.11N access point > > (hosted with hostapd and another ar5008). I've included dmesg output for a > > failure event, including back traces of hung processes. What ath9k.debug flags > > would be most helpful for tracing this further? > > None, I would think, this seems to be a lockup between > modprobe/stop_machine and some rtnl things, but I have no idea why that > would happen. Do you have lockdep enabled? And if you do, please disable > RCU lockdep as it typically gives you a warning and then turns off > lockdep... > Thank you very much for your response. I do not currently have lockdep enabled, but I'm building a new kernel as we speak. Thanks again, - Ben -- 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
