On Wed, Mar 2, 2011 at 7:38 PM, Luis R. Rodriguez <mcg...@gmail.com> wrote:
> On Wed, Mar 2, 2011 at 4:27 PM, crocket <crockabisc...@gmail.com> wrote:
>> What about
>> https://lists.ath9k.org/pipermail/ath9k-devel/2011-February/005157.html
>
> This is a FreeBSD issue, not Linux issue, see: "The problem is RX'ing
> packets on the FreeBSD station"
>
>> https://lists.ath9k.org/pipermail/ath9k-devel/2011-February/005242.html
>
> "DMA failed to stop" issues are non-fatal and we were not able to find
> an easy way to reproduce, we will look into reproducing and fixing
> this. In this case the issue is the card even goes deaf on STA mode!
> This may be card specific, I haven't had time yet to reproduce.
> Anyway, I stand by my statement, any issues found should be reported
> just like Bernhard reported his issue and will be looked into.

I see these DMA errors all the time on three different platforms.
x86_64 with 2.6.37, compat-wireless from early February, AR9380 with
single STA interface:

ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA!


On an AR9132 system running compat-wireless from 2011-02-25 (this one
with OpenWrt's patches) with a single AP interface,
Linux OpenWrt 2.6.37.1 #1 Sun Feb 27 11:48:13 EST 2011 mips GNU/Linux
system type             : Atheros AR9132 rev 2
machine                 : TP-LINK TL-WR1043ND

My kernel log gets filled with this:

ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020


And an IXP425 system running 2.6.32.27 and compat-wireless again from
2010-02-25 with an AR9220 shows much the same thing, in AP or STA
mode.  If a connection is active and I create a monitor-mode vif,
that's almost a sure way to see this on the IXP425 platform.

-Brian
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to