On Thu, Jun 7, 2012 at 3:04 PM, Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxxxxx> wrote: > On Tuesday 29 May 2012 13:12:33 Sujith Manoharan wrote: >> > 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.patc >> h >> http://sujith.github.com/patches/wl/0002-ath9k-Resync-beacons-after-a-rese >> t.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 > > For the record, we swapped the mini PCI card to a different one of the same > model and now it seems to work fine. Could you imagine a hardware fault or > tolerance issue causing such errors? > could be, i shorted a resistor in one of the chips for some reason and saw some Failed to stop DMA issues(well the chip was not working at all) -- thanks, shafi -- 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
