netdev - Re: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Mar 2012 20:49:36 +0530
From:	Mohammed Shafi <shafi.wireless@...il.com>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	Linux-netdev <netdev@...r.kernel.org>,
	Linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: ath: DMA failed to stop in 10 ms AR_CR=0x00000024
 AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040

On Wed, Mar 7, 2012 at 7:55 PM, Justin P. Mattock
<justinmattock@...il.com> wrote:
> ath9k craps out from time to time(more annoying if anything)
>
> [44309.840830] ath: Failed to stop TX DMA, queues=0x001!
> [44309.858246] ath: DMA failed to stop in 10 ms AR_CR=0x00000024
> AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040
> [44309.858255] ath: Could not stop RX, we could be confusing the DMA engine
> when we start RX up
> [44309.932801] ath: Failed to stop TX DMA, queues=0x001!
> [44309.950352] ath: DMA failed to stop in 10 ms AR_CR=0x00000024
> AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040
> [44309.950361] ath: Could not stop RX, we could be confusing the DMA engine
> when we start RX up
> [44310.024301] ath: Failed to stop TX DMA, queues=0x001!
> [44310.041641] ath: DMA failed to stop in 10 ms AR_CR=0x00000024
> AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040
> [44310.041646] ath: Could not stop RX, we could be confusing the DMA engine
> when we start RX up
> [44310.116316] ath: Failed to stop TX DMA, queues=0x001!
> [44310.133909] ath: DMA failed to stop in 10 ms AR_CR=0x00000024
> AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040
> [44310.133918] ath: Could not stop RX, we could be confusing the DMA engine
> when we start RX up
> [44310.208021] ath: Failed to stop TX DMA, queues=0x001!
> [44310.225752] ath: DMA failed to stop in 10 ms AR_CR=0x00000024
> AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040
> [44310.225761] ath: Could not stop RX, we could be confusing the DMA engine
> when we start RX up
> [44310.299922] ath: Failed to stop TX DMA, queues=0x001!
> [44310.317579] ath: DMA failed to stop in 10 ms AR_CR=0x00000024
> AR_DIAG_SW=0x02000020 DMADBG_7=0x00006040
> [44310.317587] ath: Could not stop RX, we could be confusing the DMA engine
> whe

this is has become a know issue but less harmful, please try to see if
the workaround of disabling power save helps

iw dev wlanX set power_save off



>
>
> part of dmesg here:
> http://fpaste.org/xew6/
> I can supply full log if needed..
>
> Justin P. Mattock
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
thanks,
shafi
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html