Tvrtko Ursulin wrote: > I've collected several interesting events but the compressed log is quite > large. Not sure if it will make it to the mailing list, but you should at > least get it privately. Thanks. > There are events ranging from short to long connection dropouts (in the light > of that it is possible that the path Mohammed suggested did indeed help, at > least partially to unwedge some situation which would hang it completely > without the patch). There is always mention of the 'DMA' keyword when it > happens, so if you grep for that in my log you will see events happening at, > in printk time: > > 118.779362 - 118.795238 (WARN_ON WARNING: at > drivers/net/wireless/ath/ath9k/recv.c:531 ath_stoprecv+0x118/0x130 [ath9k]()) > > 524.162432 - 524.753750 > 1544.610658 - 1550.218324 > 1685.668241 - 1686.991166 > 1773.268867 - 1804.465933 > > Hope this helps? Yes ! Here are a couple of patches to help narrow down the issue. http://sujith.github.com/patches/wl/0001-ath9k-Add-some-debug-messages.patch http://sujith.github.com/patches/wl/0002-ath9k-Resync-beacons-after-a-reset.patch The first one adds some messages, the second sets up beacons properly in case a HW reset happens. Can you try these and post the log ? If you are willing to move to a more recent kernel, then current wireless-testing would be a good choice since it has various driver fixes. There are a few pending ath9k patches which have not been merged yet, you can find it here: http://sujith.github.com/patches/wl/wl-ath9k-May-29-2012.patch Sujith -- 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
