On Sat, Jun 5, 2010 at 4:34 AM, Benoit Papillault <benoit.papilla...@free.fr > wrote:
> It might be likely that the problem is caused by background scan done by > network manager since this calls ath5k_reset. So, one way to trigger the > problem more often is by doing more scanning. > > Could you try a script like below when downloading ? > > while true; do iw dev wlan0 scan ; sleep 1 ; done > > My feeling is that both RXDP & TXDP registers are not properly initialized > after a reset causing duplicate in both directions. So I believe you should > see duplicate on the TX side as well. > I transferred 1 Gb of data twice while executing the scan command as above. I got 3 corrupted blocks on the first transfer and 2 on the second, which is more than I normally expect. Usually, I have to transfer 2 or 3 Gb before I see one bad block. Not conclusive, but it supports your hunch. The length of each bad run was 1445 bytes. bob
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
