Modify

Opened 7 years ago

Closed 4 years ago

Last modified 4 years ago

#9693 closed defect (duplicate)

Backfire ar71xx error: ath: Failed to stop TX DMA!

Reported by: oss@… Owned by: nbd
Priority: response-needed Milestone: Chaos Calmer 15.05
Component: kernel Version: Backfire 10.03.1 RC4
Keywords: ath ar71xx DMA Error Cc: zioproto@…

Description

There is no version of "10.03.1 RC5" but that's what this from, a recent build:

BusyBox v1.15.3 (2011-07-09 11:04:58 CDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 Backfire (10.03.1-RC5, r27574) --------------------------
  * 1/3 shot Kahlua    In a shot glass, layer Kahlua 
  * 1/3 shot Bailey's  on the bottom, then Bailey's, 
  * 1/3 shot Vodka     then Vodka.
 ---------------------------------------------------

Wireless performance is very bad, random disassociation, all sorts of not-good, and in dmesg, the log dreaded log entry:

ath: Failed to stop TX DMA!

Attachments (0)

Change History (101)

comment:1 Changed 7 years ago by nbd

what kind of hardware, what wireless configuration, etc are you using?

comment:2 Changed 7 years ago by jow

  • Priority changed from normal to response-needed

Also please update to the offical RC5 build to give us a point of reference to work from.

comment:3 Changed 7 years ago by sly.account@…

same problem here on wzr-hp-g300nh on backfire 10.03.1-rc5

Mar 27 02:50:10 AR9132 user.err kernel: ath: Failed to stop TX DMA!
Mar 27 02:50:10 AR9132 user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000062c0
Mar 27 02:50:10 AR9132 user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Mar 27 02:50:24 AR9132 user.err kernel: ath: Failed to stop TX DMA!
Mar 27 02:50:38 AR9132 user.err kernel: ath: Failed to stop TX DMA!

followed by the router rebooting/crashing. this happens during large amounts of wifi data transfer.

highly unstable

comment:4 Changed 7 years ago by pekseg@…

Same here on WR1043ND (10.03.1-RC5, r27608):

root@OpenWrt-router:~# dmesg
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!

and the connection dropped.

comment:5 Changed 7 years ago by philchetcuti

WR1043 still experiencing ath: Failed to stop TX DMA!
During my last test over a 12 hour period I averaged 8 of these per hour.
It does not drop my connection (or perhaps it recovers by itself)
Streaming apps with buffering continue to work, those without buffers stop.

I am also now experiencing (or perhaps its the first time I've trapped it)

ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up

This would appear to be dropping my connection.
Also, perhaps its coincidence, but my bluetooth is now experiencing severe tx/rx issues since this new error has appeared. I am operating in the 2.4 band and am aware of the co-existence issues that this causes but until this error occurred, I was getting severe tx/rx on the bluetooth perhaps once a week. Now I am getting them several times an hour, severe enough that the system either freezes or reboots.

phil@phil-laptop:~/OpenWrt/trunk$ svn info
Path: .
URL: svn://svn.openwrt.org/openwrt/trunk
Repository Root: svn://svn.openwrt.org/openwrt
Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73
Revision: 27917
Node Kind: directory
Schedule: normal
Last Changed Author: lars
Last Changed Rev: 27917
Last Changed Date: 2011-08-05 13:53:43 -0300 (Fri, 05 Aug 2011)

comment:6 Changed 6 years ago by dollarsignfoo@…

I'm using a TP-LINK TL-WR1043ND v1.4 running RC5 (27608) and I'm experiencing the same symptoms as above -- http://pastebin.com/Nqhyip5m

I am on IRC using the nick steve_ if anyone needs me to troubleshoot.

comment:7 Changed 6 years ago by dollarsignfoo@…

I did a 'sysupgrade' to the Jul-30 snapshot (27832) and the problem seems to be resolved.

comment:8 Changed 6 years ago by anonymous

Same Device Model here, same errors. I will wait for the fix to be included in the stable release, though. No need to have an unstable system just because a fix is only applied to the experimental OS...

comment:9 Changed 6 years ago by anonymous

Using a TP-LINK TL-WR1043ND v1.8 running 10.03.1-RC5, r27608
This issue has happened the first time after more than 10 days of uptime, at moderate wireless load.

dmesg output:


WARNING: at /home/jow/devel/openwrt/rc5/ar71xx/build_dir/linux-ar71xx/compat-wireless-2011-06-22/net/mac80211/rx.c:2916 0x80d19f40()
Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 79 (0x4f)
Modules linked in: ath_pci ath_hal(P) xt_IMQ imq nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_MARK ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length ipt_ecn xt_DSCP xt_dscp xt_string xt_layer7 ipt_MASQUERADE iptable_nat nf_nat xt_CONNMARK xt_recent xt_helper xt_conntrack xt_connmark xt_connbytes xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables tun ppp_async ath9k ath9k_common ath9k_hw ath mac80211 ts_fsm ts_bm ts_kmp crc_ccitt pppoe pppox ppp_generic slhc cfg80211 compat_firmware_class compat arc4 aes_generic deflate ecb cbc usb_storage ohci_hcd ehci_hcd sd_mod ext3 jbd ext4 jbd2 usbcore scsi_mod nls_base mbcache crc16 leds_gpio button_hotplug gpio_buttons input_polldev input_core
Call Trace:[<8007e7f4>] 0x8007e7f4
[<80069200>] 0x80069200
[<80069200>] 0x80069200
[<8007ddfc>] 0x8007ddfc
[<80d19f40>] 0x80d19f40
[<8007de7c>] 0x8007de7c
[<800d7714>] 0x800d7714
[<80d19f40>] 0x80d19f40
[<80d34080>] 0x80d34080
[<801e7a28>] 0x801e7a28
[<80ca74d4>] 0x80ca74d4
[<8009cac4>] 0x8009cac4
[<80ca53c8>] 0x80ca53c8
[<80071834>] 0x80071834
[<80083070>] 0x80083070
[<800a905c>] 0x800a905c
[<80083868>] 0x80083868
[<80083948>] 0x80083948
[<8006082c>] 0x8006082c
[<80060a00>] 0x80060a00
[<8006d604>] 0x8006d604
[<80060a20>] 0x80060a20
[<802dca54>] 0x802dca54
[<802dc3a8>] 0x802dc3a8

---[ end trace bbacb5db511b9cf0 ]---
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!

comment:10 Changed 6 years ago by philchetcuti

This situation has gone from bad to tragic.
Failed to stop TX DMA has increased in frequency.
And while my system believes it is still connected to the router, it is unusable. Cannot connect to websites, cannot ssh, cannot ftp. The router however, is not rebooting itself.
Only a complete wireless failure would be worse than current conditions.

phil@phil-laptop:~/OpenWrt/trunk$ svn info
Path: .
URL: svn://svn.openwrt.org/openwrt/trunk
Repository Root: svn://svn.openwrt.org/openwrt
Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73
Revision: 28007
Node Kind: directory
Schedule: normal
Last Changed Author: juhosg
Last Changed Rev: 28007
Last Changed Date: 2011-08-15 16:00:23 -0300 (Mon, 15 Aug 2011)

comment:11 Changed 6 years ago by dollarsignfoo@…

For stability I ended up disabling the 'n' protocol on the client side with:

$ cat /etc/modprobe.d/iwlagn.conf

options iwlagn 11n_disable=1

comment:12 Changed 6 years ago by anonymous

I have 'n' disabled and, so far, the two connections to the access point seems stable, but I am seeing a lot these errors in 'logread':

Aug 17 14:35:59 gue-fw kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
Aug 17 14:35:59 gue-fw kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Aug 17 14:38:56 gue-fw kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
Aug 17 14:38:56 gue-fw kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Aug 17 14:38:56 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:38:56 gue-fw kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024040
Aug 17 14:38:56 gue-fw kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Aug 17 14:38:57 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:38:58 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:38:58 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:38:59 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:00 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:00 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:01 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:02 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:02 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:06 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:06 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:07 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:08 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:11 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:12 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:12 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:13 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:13 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:14 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:16 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:16 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:17 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:18 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:19 gue-fw kern.err kernel: ath: Failed to stop TX DMA!
Aug 17 14:39:20 gue-fw kern.err kernel: ath: Failed to stop TX DMA!

comment:13 Changed 6 years ago by dollarsignfoo@…

Here is the output with linebreaks -- http://pastebin.com/PwTy3Hwf

comment:14 Changed 6 years ago by newgel

I can confirm this behavior on an TP-Link 1043ND hw version 1.6. Backfire 10.03.1-rc5 is _extremely_ unstable, actually unusable. Several wi-fi drops a day (around once an hour) even without torrents or skype traffic. I'm now running snapshoot r27832 and drops are _a little_ better: I experience two or three over a period of 24hs. There is definitely something really wrong with atheros on recent builds. Previously I was running snapshoot r26822 and it seemed a lot more stable.

This is what I found on system log imediatley after a connection drop:

Aug 17 22:11:46 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:46 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:46 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:46 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:46 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:46 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:46 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:47 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:47 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:47 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:47 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:47 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:47 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:47 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:47 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:47 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:48 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:48 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:48 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:48 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:48 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:48 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:48 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:48 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:48 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:49 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:49 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:49 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:49 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:49 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:49 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:49 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:49 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:49 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:50 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:50 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:50 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:50 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:50 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:50 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:50 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:50 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:50 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:50 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:51 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:51 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:51 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:51 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:51 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:51 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:51 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:51 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:51 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:52 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:52 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:52 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:52 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:52 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:52 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:52 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:52 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:52 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:53 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:53 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:53 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:53 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:53 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:53 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:53 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:53 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:53 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:53 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:54 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:54 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:54 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:54 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:54 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:54 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:54 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:54 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:54 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:54 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:55 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:55 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:55 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:55 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:55 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:55 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:55 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:55 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Aug 17 22:11:55 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:56 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:56 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:56 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:56 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:56 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:56 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:56 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:56 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:56 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:57 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:57 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:57 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:57 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:57 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:57 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:57 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:58 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:58 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:58 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:58 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:58 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:58 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:58 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:58 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:58 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:59 Vortex kern.err kernel: ath: Failed to stop TX DMA! Aug 17 22:11:59 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:59 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:59 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:59 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:59 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:59 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:11:59 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:11:59 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:12:00 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:12:00 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:12:00 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:12:00 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:12:00 Vortex kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 17 22:12:00 Vortex kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 17 22:12:34 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: authenticated Aug 17 22:12:34 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: associated (aid 2) Aug 17 22:12:34 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: pairwise key handshake completed (WPA) Aug 17 22:12:34 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA)


    

comment:15 Changed 6 years ago by dollarsignfoo@…

FWIW, I did a sysupgrade to r28057 and the ath errors are still present:
http://tinypaste.com/dd6dd4

comment:16 Changed 6 years ago by Newgel (gelson.santos@…

I gave up recent releases and set up an Ubuntu build environment so I could compile back r26885, which is the most stable release I have experienced so far. I'm now back at r26885 and there are NO MORE DROPS! I still see ath: Failed to stop TX DMA! but wi-fi clientes seems less affected by this. I'm also monitoring wi-fi signal with inSSIDer 2.0 on a notebook and since downgrading to r26885 I have not seen any more signal intensity drop on inSSIDer graphic. Before that each time my wi-fi clientes disconnected inSSIDer plot a big hole on wi-fi signal graphic.

Something was broken between r26885 and RC5. It would be nice to also fix that ath: Failed to stop TX DMA! error logs but so far I'm happy with it as long as r26885 keeps working.

comment:17 Changed 6 years ago by Gelson Dias Santos <gelson.santos@…>

I was Googling about this DMA issue and found reports from all Linux distributions reporting simmilar issues (TX DMA errors, wi-fi drops, poor wi-fi performance). One such report is this Ubuntu ticket: https://bugs.launchpad.net/ubuntu/+sour … bug/736171

So looks like it was a bug introduced on ath9x drives on Linux kernel 2.6.38.x. That makes sence since I'm running trunk R26885 with kernel 2.6.37.6 and does not experience this issue. According to OpenWRT timeline, kernel 2.3.38 was used from R27218 up to R28022. If you happen to be running a kernel on this interval try upgrading to a more recent trunk version and see if the problem goes away.

@dollarsignfoo: what kernel version are you running on r28057 ?

comment:18 Changed 6 years ago by dollarsignfoo@…

It's using: Linux gue-fw 2.6.39.4 #1 Mon Aug 22 10:18:45 CEST 2011 mips GNU/Linux

I turned off my other AP. I haven't had one error in 52 hours. My old AP ran an old version of openwrt on channel 1. My new AP is on channel 11. I'm still forcing 'g'. I'll try 'n' on the weekend.

comment:19 Changed 6 years ago by nbd

please try backfire with http://nbd.name/backfire-mac80211-update.patch (apply with -p1 to the tree) or try latest trunk

comment:20 Changed 6 years ago by Gert van Dijk <gertvdijk+openwrt@…>

Running latest trunk r28108. Seems a *lot* better now. My Android phone now comes from 30 kB/s to the regular full 54 Mbps speed. Haven't seen the 'DMA failed' messages again.

Great work :)

comment:21 Changed 6 years ago by nbd

  • Owner changed from developers to nbd
  • Status changed from new to accepted

comment:22 Changed 6 years ago by s7mx1

r28127

uptime: 1 day, 5:28

The DMA error happened once:

Sep 1 21:53:04 Firewall user.err kernel: ath: Failed to stop TX DMA!
Sep 1 21:53:04 Firewall user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
Sep 1 21:53:04 Firewall user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up

comment:23 Changed 6 years ago by nbd

please use at least r28139 or newer. it fixes a critical bug in the driver

comment:24 Changed 6 years ago by slybunda

these dma errors fixed yet?

comment:25 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>

r28203
after an kernel warn (ticket #10075)
I got this too : "ath: Failed to stop TX DMA!"

heres's the end of my dmesg :

wlan1: authenticate with f0:7d:68:49:ad:48 (try 1)
wlan1: authenticated
wlan1: associate with f0:7d:68:49:ad:48 (try 1)
wlan1: RX AssocResp from f0:7d:68:49:ad:48 (capab=0xc31 status=0 aid=2)
wlan1: associated
wlan1: deauthenticated from f0:7d:68:49:ad:48 (Reason: 2)
wlan1: authenticate with f0:7d:68:49:ad:48 (try 1)
wlan1: authenticated
wlan1: associate with f0:7d:68:49:ad:48 (try 1)
wlan1: RX ReassocResp from f0:7d:68:49:ad:48 (capab=0xc31 status=0 aid=1)
wlan1: associated
------------[ cut here ]------------
WARNING: at /home/giuseppe/my_openwrt/trunk/build_dir/linux-ar71xx_generic/compat-wireless-2011-08-26/net/mac80211/rx.c:2960 0x80c5a010()
Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 83 (0x53)
Modules linked in: nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_conntrack xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc rt2800usb ath9k rt2800lib ath9k_common ath9k_hw rt2x00usb ath rt2x00lib mac80211 usbcore nls_base crc_itu_t crc_ccitt cfg80211 compat arc4 aes_generic crypto_algapi leds_gpio button_hotplug gpio_keys_polled input_polldev input_core
Call Trace:[<801886b0>] 0x801886b0
[<80253624>] 0x80253624
[<80253624>] 0x80253624
[<80074e50>] 0x80074e50
[<80c5a010>] 0x80c5a010
[<80074f04>] 0x80074f04
[<80c5a010>] 0x80c5a010
[<81ab4078>] 0x81ab4078
[<801cb59c>] 0x801cb59c
[<80ce7f80>] 0x80ce7f80
[<80ceb0a0>] 0x80ceb0a0
[<80ceba50>] 0x80ceba50
[<80c9ae48>] 0x80c9ae48
[<80ce4bb0>] 0x80ce4bb0
[<8007a254>] 0x8007a254
[<8007a80c>] 0x8007a80c
[<8007a604>] 0x8007a604
[<802d0000>] 0x802d0000
[<802d0000>] 0x802d0000
[<8007a80c>] 0x8007a80c
[<8006256c>] 0x8006256c
[<80062740>] 0x80062740
[<802d0000>] 0x802d0000
[<80ce17e0>] 0x80ce17e0
[<80063fac>] 0x80063fac
[<80062760>] 0x80062760
[<802b78d0>] 0x802b78d0
[<802b721c>] 0x802b721c

---[ end trace bfdc6702640cd33f ]---
ath: Failed to stop TX DMA!

comment:26 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>

If u need any more info pls ask.

comment:27 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>

Also, the reason for the drops in connection quality could be that on my pc I have an atheros card that uses the ath9k driver, and that seems to have some problems of its own.

I'm saying this because on an intel wifi link 5100 I am getting no connection drops. And the quality seems to be constant.

comment:28 Changed 6 years ago by stefan.bauer@…

folks,

we're having the same problem also with the latest snapshot.

root@OpenWrt:~# tcpdump -i wlan0 ether src 00:21:6a:78:d5:9e
tcpdump: WARNING: wlan0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 65535 bytes

No traffic from this client.

After a /etc/init.d/network restart

i get new packages and traffic is flowing for a while without problems. It looks like it hit some barriers.

comment:29 Changed 6 years ago by nbd

please try trunk r28301

comment:30 Changed 6 years ago by anonymous

r28301 Linksys WRT160NL

root@OpenWrt:~# dmesg | tail
br-lan: port 2(wlan0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
wlan1: authenticate with f0:7d:68:49:ad:48 (try 1)
wlan1: authenticated
wlan1: associate with f0:7d:68:49:ad:48 (try 1)
wlan1: RX AssocResp from f0:7d:68:49:ad:48 (capab=0xc31 status=0 aid=1)
wlan1: associated
ath: Failed to stop TX DMA, queues=00000004!
root@OpenWrt:~# logread | tail
Sep 26 14:57:50 OpenWrt daemon.info hostapd: wlan0: STA 00:21:6b:09:da:f2 WPA: group key handshake completed (RSN)
Sep 26 14:57:50 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb WPA: group key handshake completed (RSN)
Sep 26 15:07:50 OpenWrt daemon.info hostapd: wlan0: STA 00:21:6b:09:da:f2 WPA: group key handshake completed (RSN)
Sep 26 15:07:51 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb WPA: group key handshake completed (RSN)
Sep 26 15:09:17 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004!
Sep 26 15:17:50 OpenWrt daemon.info hostapd: wlan0: STA 00:21:6b:09:da:f2 WPA: group key handshake completed (RSN)
Sep 26 15:17:54 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: deauthenticated due to local deauth request
Sep 26 15:17:55 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: authenticated
Sep 26 15:17:55 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: associated (aid 2)
Sep 26 15:17:55 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb WPA: pairwise key handshake completed (RSN)

comment:31 Changed 6 years ago by slybunda

Wzr-hp-g300nh

r28301:

ath: Failed to stop TX DMA,

wifi crashes on router and restarts.

comment:32 Changed 6 years ago by Petr Titera <p.titera@…>

Same here with r28310. It seems better than it was after I've deleted all ht_capab setting from my config. I client still disassciates from time to time

Sep 28 11:12:22 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004!
Sep 28 11:12:23 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004!
Sep 28 11:12:23 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004!
Sep 28 11:12:23 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004!

comment:33 Changed 6 years ago by Oleg Baranov <ol@…>

After two days of running r28314 on WR1043ND without high traffice dmesg has got these lines. No complains from users though.

ath: Failed to stop TX DMA, queues=00000104!
ath: Failed to stop TX DMA, queues=00000005!

Config is as follows:

config wifi-device  radio0
	option type     mac80211
	option channel  7
	option phy 	phy0
	option hwmode	11ng
	option htmode   HT40+

        list 'ht_capab' 'SHORT-GI-40'
        list 'ht_capab' 'DSSS_CCK-40'

comment:34 Changed 6 years ago by anonymous

i see so many times in log on BUFFALO WZR-HP-G300NH, OpenWRT r28380:

OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004!
...


Config:

config 'wifi-device' 'radio0'
        option 'type' 'mac80211'
        option 'macaddr' '.....'
        list 'ht_capab' 'SHORT-GI-40'
        list 'ht_capab' 'DSSS_CCK-40'
        option 'hwmode' '11gn'
        option 'channel' '11'
        option 'txpower' '20'
        option 'disabled' '0'
        option 'wmm' '0'

config 'wifi-iface'
        option 'device' 'radio0'
        option 'mode' 'ap'
        option 'key' '....'
        option 'encryption' 'psk2'
        option 'ssid' '....'
        option 'wmm' '0'
        option 'network' 'lan'

comment:35 Changed 6 years ago by Oleg Baranov <ol@…>

Mine WR1043ND running r28314 stopped bridging wifi with ethernet today. Nothing in logs. Had to reboot it because of user complains. Anything I can check next time it gets stick before sending it to reboot?

comment:36 Changed 6 years ago by André Gaul <gaul@…>

I installed backfire branch [28388] yesterday on a TL-WR1043ND and cannot observe any problems so far: no more 'Failed to stop TX DMA' (or similar) log messages and wireless performance seems to be very good again. Hopefully the recent changes in ath9k/mac80211 fixed this nasty bug! ;)

I'll conduct further tests this evening and report back then. Thx a lot @nbd in any case!

comment:37 Changed 6 years ago by anonymous

Got this Backfire (10.03.1-RC6, r28391):

ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA, queues=00000005!

comment:38 Changed 6 years ago by André Gaul <gaul@…>

Damn, I also got a (single!)

ath: Failed to stop TX DMA, queues=00000004!

with backfire [28388] on TL-WR1043ND. I'll check if it's as unusable as with prior versions.

comment:39 Changed 6 years ago by André Gaul <gaul@…>

I just ran some further tests and unfortunately the wifi performance is still very poor. The following result was obtained by pinging between two TL-WR741ND (short distance and within sight)

100 packets transmitted, 98 packets received, 292 duplicates, 2% packet loss
round-trip min/avg/max = 1.215/3122.470/12446.284 ms

Notice the avg time and the # of DUPs! No errors/warnings showed up in the logs before and while pinging.

comment:40 Changed 6 years ago by nbd

what configuration are you using on the client side?

comment:41 Changed 6 years ago by André Gaul <gaul@…>

Both routers are in adhoc mode and have the following /etc/config/wireless file (apart from a different macaddr value):

config 'wifi-device' 'radio0'
	option 'type' 'mac80211'
	option 'macaddr' '94:0c:6d:a2:85:46'
	option 'hwmode' '11ng'
	list 'ht_capab' 'SHORT-GI-40'
	list 'ht_capab' 'TX-STBC'
	list 'ht_capab' 'RX-STBC1'
	list 'ht_capab' 'DSSS_CCK-40'
	option 'disabled' '0'
	option 'country' 'DE'
	option 'distance' '1000'
	option 'channel' '10'
	option 'htmode' 'HT40-'
	option 'txpower' '17'

config 'wifi-iface'
	option 'ssid' 'olsr.freifunk.net'
	option 'encryption' 'none'
	option 'device' 'radio0'
	option 'bssid' '02:CA:FF:EE:BA:BE'
	option 'mode' 'adhoc'
	option 'network' 'wireless0'

I don't get any DUPs at the moment, but packet loss and high latency for a few seconds (cf. http://pastebin.com/BkiqjgZW).

comment:42 Changed 6 years ago by garridomota@…

Hi, I have tl-wr741nd update from backfire 10.03.1-RC5 to the last snapshot release "ATTITUDE ADJUSTMENT (bleeding edge, r28601)" because I have exactly the same problem: too packages loss and "ath: Failed to stop TX DMA!" but now, with r28601, the problem persist: TOO packages loss but now the system log is (I don't know if its an error)

... TOO MUCH TIMES THE SAME
br-lan: port 5(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 5(wlan0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 5(wlan0) entering forwarding state
br-lan: port 5(wlan0) entering forwarding state
wan: link down
lan1: link down
br-lan: port 1(lan1) entering forwarding state
wan: link up, 100 Mb/s, full duplex, flow control disabled
.... TOO MUCH TIMES THE SAME

Somebody have any idea about how resolve this problem? Is impossible use the wifi because the I have ~40% packet loss. ping command return too times: From 190.79.45.134 icmp_seq=1198 Destination Host Unreachable

Regards.

comment:43 follow-up: Changed 6 years ago by nbd

please try trunk r28772

comment:44 in reply to: ↑ 43 ; follow-up: Changed 6 years ago by Giacomo

This still in OpenWrt Backfire 10.03.1-RC6 / LuCI 0.10 Branch (0.10+svn7852) on a WR1043ND.
This bug led the wifi to stop working until
wifi down
wifi up
from ethernet or crontab.
Here's the dmesg
http://paste.ubuntu.com/729781/

comment:45 Changed 6 years ago by anonymous

Just for your information. I still see this in r28772. Bu I have to check if wifi connections are more stable than before. They are definitelly more stable than in r28717 (I've tested it but have to go back because of wifi drops every 10 seconds).

Petr

comment:46 in reply to: ↑ 44 Changed 6 years ago by aqua

Replying to Giacomo:

This still in OpenWrt Backfire 10.03.1-RC6 / LuCI 0.10 Branch (0.10+svn7852) on a WR1043ND.

Also still reproducible (indeed, so far it's worse) under RC6 on WZR-HP-G300NH (ath9k). Same error pattern as Giacomo cites.

comment:47 Changed 6 years ago by anonymous

Any news on this defect? What version would you recommend to use? I have some Dir-615 rev E5 with Backfire rc-6 (r28719) and the problem is there. In fact, i'm not completely sure that my problem is only about this dma error, because sometimes i get very bad throughputs without the error, and when it appears it's just:

ath: Failed to stop TX DMA, queues=0x004!

And i don't know if that's the worst error of all related to dma.

G

comment:48 follow-up: Changed 6 years ago by nbd

comment:49 in reply to: ↑ 48 Changed 6 years ago by anonymous

Replying to nbd:

Please try the build from http://openwrt.linux-appliance.net/ar71xx/

Thanks nbd, i'll try with that. Is there a way to compile myself? To add some packages.

comment:50 follow-up: Changed 6 years ago by jow

Sure, just build the Backfire branch.

comment:51 in reply to: ↑ 50 Changed 6 years ago by anonymous

Replying to jow:

Sure, just build the Backfire branch.

Ok, i didn´t know if it was some special patch or something.. So it's just the last backfire revision, i'll try to see what happens. Thanks!

G

comment:52 Changed 6 years ago by Varava

Backfire (10.03.1-RC6, r29322)

wlan0: authenticate with 00:1d:7e:bc:37:3c (try 1)
wlan0: authenticated
wlan0: associate with 00:1d:7e:bc:37:3c (try 1)
wlan0: RX ReassocResp from 00:1d:7e:bc:37:3c (capab=0x411 status=0 aid=2)
wlan0: associated
ath: Failed to stop TX DMA, queues=0x005!

Happens on high dl/ul (200kb/s)

comment:53 Changed 6 years ago by Paul Warren <p.a.warren@…>

I was also getting this with my wr841nd v7.2 a few months ago, r28344, ended up having to use stock firmware as my household was getting impatient. Following on from #9950.

God donkey spam filter, what needs to be done to defeat it so I can get updates to this ticket?

comment:54 Changed 6 years ago by anonymous

I'm using r29322 too, and i've seen the same error:

ath: Failed to stop TX DMA, queues=0x004!

But i'm not sure if it's related with the low throughputs, do you know how could i check to be sure that's the problem? I'm getting very variable rates.

G

comment:55 Changed 6 years ago by zioproto

  • Cc zioproto@… added

Same here with r29537 trunk, and TP-Link WR1043ND

It looks like this happens when more than 4 or 5 clients are connected. WiFi stops working and dmesg is like :

[ 214.430000] ath: Failed to stop TX DMA, queues=0x004!
[ 215.400000] ath: Failed to stop TX DMA, queues=0x004!
[ 237.560000] ath: Failed to stop TX DMA, queues=0x004!
[ 243.400000] ath: Failed to stop TX DMA, queues=0x004!
[ 244.370000] ath: Failed to stop TX DMA, queues=0x005!
[ 245.020000] ath: Failed to stop TX DMA, queues=0x004!
[ 246.940000] ath: Failed to stop TX DMA, queues=0x004!
[ 251.820000] ath: Failed to stop TX DMA, queues=0x004!
[ 252.250000] ath: Failed to stop TX DMA, queues=0x004!
[ 252.900000] ath: Failed to stop TX DMA, queues=0x004!
[ 299.420000] ath: Failed to stop TX DMA, queues=0x004!
[ 300.280000] ath: Failed to stop TX DMA, queues=0x004!
[ 303.270000] ath: Failed to stop TX DMA, queues=0x004!
[ 306.980000] ath: Failed to stop TX DMA, queues=0x004!
[ 314.410000] ath: Failed to stop TX DMA, queues=0x004!
[ 314.850000] ath: Failed to stop TX DMA, queues=0x004!
[ 315.180000] ath: Failed to stop TX DMA, queues=0x004!
[ 315.830000] ath: Failed to stop TX DMA, queues=0x005!
[ 317.110000] ath: Failed to stop TX DMA, queues=0x004!
[ 322.420000] ath: Failed to stop TX DMA, queues=0x004!

comment:56 Changed 6 years ago by Varava

setting the rate to 11mb fixed it for me

in ssh console - iwconfig wlan0 rate 11M

comment:57 Changed 6 years ago by nikolay@…

Same here with ubnt routerstation with R52N card

Backfire (10.03.1, r29592)

ath: Failed to stop TX DMA, queues=0x004!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up

comment:58 Changed 6 years ago by duvi

TL-WR1043ND, r29606.
This happened after 35 days of uptime:

[3076699.500000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[3076699.510000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
[3076699.520000] ------------[ cut here ]------------
[3076699.520000] WARNING: at /mnt/hda/openwrt/r29606/build_dir/linux-ar71xx_generic/compat-wireless-2011-12-01/drivers/net/wireless/ath/ath9k/recv.c:537 0x80c06ff0()
[3076699.540000] Modules linked in: usblp ledtrig_usbdev xt_HL xt_hl ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length ipt_ecn xt_DSCP xt_dscp xt_string xt_layer7 xt_quota xt_pkttype xt_owner ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE iptable_nat nf_nat xt_recent xt_helper xt_connmark xt_connbytes xt_conntrack xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit tunnel4 tun ppp_async ppp_generic slhc ath9k ath9k_common ath9k_hw ath mac80211 usbcore nls_base ts_fsm ts_bm ts_kmp crc_ccitt ipv6 cfg80211 compat arc4 aes_generic crypto_algapi leds_gpio button_hotplug gpio_keys_polled input_polldev input_core
[3076699.610000] Call Trace:[<8025a810>] 0x8025a810
[3076699.620000] [<8025a810>] 0x8025a810
[3076699.620000] [<80075230>] 0x80075230
[3076699.620000] [<80c06ff0>] 0x80c06ff0
[3076699.630000] [<80c10000>] 0x80c10000
[3076699.630000] [<80075274>] 0x80075274
[3076699.630000] [<80189bec>] 0x80189bec
[3076699.640000] [<80c06ff0>] 0x80c06ff0
[3076699.640000] [<80189bec>] 0x80189bec
[3076699.640000] [<80c02bcc>] 0x80c02bcc
[3076699.650000] [<80c042f0>] 0x80c042f0
[3076699.650000] [<80c05c8c>] 0x80c05c8c
[3076699.660000] [<80c033ec>] 0x80c033ec
[3076699.660000] [<80c05c8c>] 0x80c05c8c
[3076699.660000] [<80c043f0>] 0x80c043f0
[3076699.670000] [<80087ffc>] 0x80087ffc
[3076699.670000] [<80086cc8>] 0x80086cc8
[3076699.670000] [<8006164c>] 0x8006164c
[3076699.680000] [<80088fb4>] 0x80088fb4
[3076699.680000] [<8025b0d8>] 0x8025b0d8
[3076699.690000] [<80088d78>] 0x80088d78
[3076699.690000] [<80088d78>] 0x80088d78
[3076699.690000] [<8008c8cc>] 0x8008c8cc
[3076699.700000] [<80064300>] 0x80064300
[3076699.700000] [<8008c84c>] 0x8008c84c
[3076699.700000] [<800642f0>] 0x800642f0
[3076699.710000]
[3076699.710000] ---[ end trace 0ae2183253999a6f ]---

Prior to that, the only ath related messages (in 35 days) were only once these:

[2458319.340000] ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
[2460394.290000] ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
[2460681.240000] ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
[2461886.700000] ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22

Config:

config wifi-device      'radio0'
        option disabled '0'
        option type     'mac80211'
        option channel  '5'
        option txpower  '20'
        option macaddr  '00:23:cd:19:11:50'
        option hwmode   '11ng'
        option htmode   'HT40+'
        option noscan   '1'
        list ht_capab   'SHORT-GI-40'
        list ht_capab   'DSSS_CCK-40'

config wifi-iface
        option device   'radio0'
        option network  'lan'
        option mode     'ap'
        option ssid     'xxx'
        option encryption       'psk-mixed'
        option key      'xxx'
        option wpa_group_rekey  '3600'

config wifi-iface
        option device   'radio0'
        option network  'pub'
        option mode     'ap'
        option ssid     'xxx'
        option encryption       'psk-mixed'
        option key      'xxx'

Although everything seems to work fine, I haven't heard any complains about disconnections or slow transfer speeds.

comment:59 follow-up: Changed 6 years ago by Thytum@…

Hello,

Im having problems to apply the patch of Changeset 29606

root@VKengRouterNordeste:~# dmesg
ath: Failed to stop TX DMA, queues=0x004!
ath: Failed to stop TX DMA, queues=0x004!
ath: Failed to stop TX DMA, queues=0x004!

The file was downloaded from here:
https://dev.openwrt.org/changeset/29606?format=diff&new=29606

Don't know if i will need this too https://dev.openwrt.org/browser/trunk/package/mac80211/files/lib/wifi/mac80211.sh?rev=29606

im trying to:

root@VKengRouterNordeste:/lib/wifi#  patch -p1 <  /mnt/share/29606.diff    
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: /trunk/package/mac80211/files/lib/wifi/mac80211.sh
|===================================================================
|--- /trunk/package/mac80211/files/lib/wifi/mac80211.sh (revision 29569)
|+++ /trunk/package/mac80211/files/lib/wifi/mac80211.sh (revision 29606)
--------------------------
File to patch: 

What should i put on "File to patch:" ?
Was trying to put "mac80211.sh"
but i didn't works!

Can someone please help me with it?

comment:60 in reply to: ↑ 59 Changed 6 years ago by anonymous

Replying to Thytum@…:

Hello,

Im having problems to apply the patch of Changeset 29606

root@VKengRouterNordeste:~# dmesg
ath: Failed to stop TX DMA, queues=0x004!
ath: Failed to stop TX DMA, queues=0x004!
ath: Failed to stop TX DMA, queues=0x004!

The file was downloaded from here:
https://dev.openwrt.org/changeset/29606?format=diff&new=29606

Don't know if i will need this too https://dev.openwrt.org/browser/trunk/package/mac80211/files/lib/wifi/mac80211.sh?rev=29606

im trying to:

root@VKengRouterNordeste:/lib/wifi#  patch -p1 <  /mnt/share/29606.diff    
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: /trunk/package/mac80211/files/lib/wifi/mac80211.sh
|===================================================================
|--- /trunk/package/mac80211/files/lib/wifi/mac80211.sh (revision 29569)
|+++ /trunk/package/mac80211/files/lib/wifi/mac80211.sh (revision 29606)
--------------------------
File to patch: 

What should i put on "File to patch:" ?
Was trying to put "mac80211.sh"
but i didn't works!

Can someone please help me with it?

PS:

BusyBox v1.15.3 (2012-02-06 02:01:42 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

_

| |.-----.-----.-----.| | | |.----.| |_

| - |_
_ | -| | | _ _|
|_||| ||

|| W I R E L E S S F R E E D O M

Backfire (10.03.1, r30306) ------------------------

  • 1/3 shot Kahlua In a shot glass, layer Kahlua
  • 1/3 shot Bailey's on the bottom, then Bailey's,
  • 1/3 shot Vodka then Vodka.

---------------------------------------------------

comment:61 Changed 6 years ago by Johan <johan@…>

I'm getting this issue at least once a day with my Buffalo WZR-HP-G300NH using a week-old trunk snapshot of OpenWRT. All traffic stops suddenly and sometimes the wireless connection to my router drops, too. Then everything returns to normal within a minute or so. I typically have three or four wireless devices connected to the router and one connected via LAN port. The kernel log is full of this message:

[692344.540000] ath: Failed to stop TX DMA, queues=0x004!
[692345.200000] ath: Failed to stop TX DMA, queues=0x005!
[692810.380000] ath: Failed to stop TX DMA, queues=0x104!
[693034.700000] ath: Failed to stop TX DMA, queues=0x004!

It just goes on and on. Is there anyone out there who has managed to resolve this?

comment:62 Changed 6 years ago by anonymous

ATTITUDE ADJUSTMENT (bleeding edge, r30919) ----------
TEW-632BRP AR71xx

Router locks up once a week. Wireless on debian (Intel chipset) client & WII drops regularly. OSX seems to hold up.
My system log is full with these messages.

[58461.410000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
[58461.650000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[58461.660000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
[58461.900000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[58461.910000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
[58462.150000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[58462.160000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up

comment:63 Changed 6 years ago by garlew

I'm using TL-WR1043ND: ATTITUDE ADJUSTMENT r30919

same thing happens to me - errors in log and unable to connect

[ 49.970000] ath: Failed to stop TX DMA, queues=0x004!
[ 50.630000] ath: Failed to stop TX DMA, queues=0x004!

I've tried several versions of Backfire and trunk. I think the problem occurs mostly
in the afternoon when there are more people around using their wifi routers.

comment:64 Changed 6 years ago by anonymous

WZR-HP-G300NH with last trunk version on client wifi mode:
OpenWrt kern.debug kernel: [ 1441.630000] wlan0: RX AssocResp from * (capab=0xc31 status=0 aid=1)
OpenWrt kern.debug kernel: [ 1441.640000] wlan0: associated
OpenWrt kern.err kernel: [ 1465.600000] ath: Failed to stop TX DMA, queues=0x004!

and

OpenWrt kern.err kernel: [ 987.430000] ath: Failed to stop TX DMA, queues=0x005!

comment:65 Changed 6 years ago by garlew

now this happened (r30919):
[117257.400000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[117257.410000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up

comment:66 Changed 6 years ago by anonymous

WNDR3700v2: ath: Failed to stop TX DMA, queues=0x004!

Recent 30968 build.

comment:67 Changed 6 years ago by anonymous

WNDR3700v2 with the TX DMA error above, infos:

Version:

BusyBox v1.15.3 (2012-03-04 14:15:03 PST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 Backfire (10.03.1, r30807) ------------------------
  * 1/3 shot Kahlua    In a shot glass, layer Kahlua 
  * 1/3 shot Bailey's  on the bottom, then Bailey's, 
  * 1/3 shot Vodka     then Vodka.
 ---------------------------------------------------

Radio Settings:

config 'wifi-device' 'radio0'
	option 'type' 'mac80211'
	option 'macaddr' 'c4:3d:c7:a3:d3:26'
	option 'hwmode' '11ng'
	list 'ht_capab' 'SHORT-GI-40'
	list 'ht_capab' 'TX-STBC'
	list 'ht_capab' 'RX-STBC1'
	list 'ht_capab' 'DSSS_CCK-40'
	option 'txpower' '27'
	option 'htmode' 'HT40-'
	option 'country' 'US'
	option 'channel' '9'

config 'wifi-device' 'radio1'
	option 'type' 'mac80211'
	option 'macaddr' 'c4:3d:c7:a3:d3:28'
	option 'hwmode' '11na'
	list 'ht_capab' 'SHORT-GI-40'
	list 'ht_capab' 'TX-STBC'
	list 'ht_capab' 'RX-STBC1'
	list 'ht_capab' 'DSSS_CCK-40'
	option 'channel' '157'
	option 'txpower' '30'
	option 'country' 'US'
	option 'htmode' 'HT40+'

comment:68 Changed 6 years ago by ersin

same here:

Router NameOpenWrt

Router ModelBuffalo WZR-HP-G300NH
Firmware Version

OpenWrt Backfire 10.03.1 /

LuCI 0.10.0 Release (0.10.0)


Kernel Version2.6.32.27

Local TimeTue Apr 3 22:16:23 2012
Uptime21h 16m 17s
Load Average1.00, 1.08, 0.78

7> Normal zone: 128 pages used for memmap

Normal zone: 0 pages reserved
Normal zone: 16256 pages, LIFO batch:3

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 board=WZR-HP-G300NH
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=00000000
Readback ErrCtl register=00000000
Memory: 61692k/65536k available (2126k kernel code, 3772k reserved, 423k data, 152k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:56
Calibrating delay loop... 266.24 BogoMIPS (lpj=1331200)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
MIPS: machine is Buffalo WZR-HP-G300NH
Found an RTL8366S switch
bio: create slab <bio-0> at 0
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
yaffs Dec 10 2011 18:14:12 Installing.
msgmni has been set to 120
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console [ttyS0] enabled, bootconsole disabled
ar91xx-flash ar91xx-flash: 02000000 at 1e000000
ar91xx-flash: Found 1 x16 devices at 0x0 in 16-bit bank

CFI mfr 0x00000001
CFI id 0x00002201
Amd/Fujitsu Extended Query Table at 0x0040

Amd/Fujitsu Extended Query version 1.3.

ar91xx-flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
ar91xx-flash ar91xx-flash: using static partition mapping
Creating 7 MTD partitions on "ar91xx-flash":
0x000000000000-0x000000040000 : "u-boot"
0x000000040000-0x000000060000 : "u-boot-env"
0x000000060000-0x000000160000 : "kernel"
0x000000160000-0x000001fc0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
split_squashfs: no squashfs found in "ar91xx-flash"
0x000001fc0000-0x000001fe0000 : "user_property"
0x000001fe0000-0x000002000000 : "art"
0x000000060000-0x000001fc0000 : "firmware"
Atheros AR71xx SPI Controller driver version 0.2.4
Realtek RTL8366S ethernet switch driver version 0.2.2
rtl8366s rtl8366s: using GPIO pins 19 (SDA) and 20 (SCK)
rtl8366s rtl8366s: RTL8366 ver. 1 chip found
rtl8366s: probed
eth0: Atheros AG71xx at 0xb9000000, irq 4
eth0: using fixed link parameters
eth1: Atheros AG71xx at 0xba000000, irq 5
eth1: connected to PHY at rtl8366s:04 [uid=001cc960, driver=Realtek RTL8366S]
Atheros AR71xx hardware watchdog driver version 0.1.0
ar71xx-wdt: timeout=15 secs (max=21)
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@…>
All bugs added by David S. Miller <davem@…>
yaffs: dev is 32505859 name is "mtdblock3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
yaffs: MTD device is not NAND it's type 3
VFS: Mounted root (jffs2 filesystem) readonly on device 31:3.
Freeing unused kernel memory: 152k freed
Please be patient, while OpenWrt loads ...
input: gpio-buttons as /devices/platform/gpio-buttons/input/input0
Button Hotplug driver version 0.3.1
ar71xx: pll_reg 0xb8050014: 0x1e000100
eth0: link up (1000Mbps/Full duplex)
Registered led device: wzr-hp-g300nh:orange:security
Registered led device: wzr-hp-g300nh:green:wireless
Registered led device: wzr-hp-g300nh:green:router
Registered led device: wzr-hp-g300nh:red:diag
Registered led device: wzr-hp-g300nh:blue:usb
eth0: link down
ar71xx: pll_reg 0xb8050014: 0x1e000100
eth0: link up (1000Mbps/Full duplex)
device eth0 entered promiscuous mode
br-lan: port 1(eth0) entering forwarding state
Compat-wireless backport release: compat-wireless-2011-11-08-1-g4ab9b62
Backport based on wireless-testing.git master-2011-11-15
cfg80211: Calling CRDA to update world regulatory domain
SCSI subsystem initialized
cfg80211: World regulatory domain updated:
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ar71xx: pll_reg 0xb8050018: 0x13000a44
eth1: link up (100Mbps/Full duplex)
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 mem=0xb80c0000, irq=2
cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
PPP generic driver version 2.4.2
PPP MPPE Compression module registered
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 24
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ar71xx-ehci ar71xx-ehci: Atheros AR91xx built-in EHCI controller
ar71xx-ehci ar71xx-ehci: new USB bus registered, assigned bus number 1
ar71xx-ehci ar71xx-ehci: irq 3, io mem 0x1b000000
ar71xx-ehci ar71xx-ehci: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
nf_conntrack version 0.5.0 (967 buckets, 3868 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
usb 1-1: new high speed USB device using ar71xx-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
xt_time: kernel timezone is -0000
IMQ driver loaded successfully.

Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.

ath_hal: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
ath_hal: 2009-05-08 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, REGOPS_FUNC, XR)
ath_pci: trunk
wlan: trunk
wlan: mac acl policy registered
ath_rate_minstrel: Minstrel automatic rate control algorithm 1.2 (trunk)
ath_rate_minstrel: look around rate set to 10%
ath_rate_minstrel: EWMA rolloff level set to 75%
ath_rate_minstrel: max segment size in the mrr set to 6000 us
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
fuse init (API version 7.13)
cfg80211: Calling CRDA for country: GB
cfg80211: Regulatory domain changed to country: GB
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
scsi 0:0:0:0: Direct-Access Generic USB Disk 9.02 PQ: 0 ANSI: 2
usb-storage: device scan complete
sd 0:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through

sda: sda1 sda2 < sda5 >

sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI disk
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
EXT4-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
EXT4-fs (sda1): mounted filesystem without journal
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
yaffs: dev is 8388610 name is "sda2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.2, "sda2"
yaffs: dev is 8388610 name is "sda2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.2, "sda2"
attempt to access beyond end of device
sda2: rw=0, want=4, limit=2
EXT4-fs (sda2): unable to read superblock
Adding 2947888k swap on /dev/sda5. Priority:-1 extents:1 across:2947888k
ar71xx-wdt: enabling watchdog timer
usb 1-1: USB disconnect, address 2
usb 1-1: new high speed USB device using ar71xx-ehci and address 3
usb 1-1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 1:0:0:0: Direct-Access Generic USB Disk 9.02 PQ: 0 ANSI: 2
usb-storage: device scan complete
sd 1:0:0:0: [sdb] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Assuming drive cache: write through

sdb: sdb1 sdb2 < sdb5 >

sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Attached SCSI disk
yaffs: dev is 8388625 name is "sdb1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.17, "sdb1"
yaffs: dev is 8388625 name is "sdb1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.17, "sdb1"
EXT4-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
EXT4-fs (sdb1): mounted filesystem without journal
yaffs: dev is 8388626 name is "sdb2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.18, "sdb2"
yaffs: dev is 8388626 name is "sdb2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.18, "sdb2"
attempt to access beyond end of device
sdb2: rw=0, want=4, limit=2
EXT4-fs (sdb2): unable to read superblock
yaffs: dev is 8388629 name is "sdb5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.21, "sdb5"
yaffs: dev is 8388629 name is "sdb5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 8.21, "sdb5"
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0-1 left promiscuous mode
br-lan: port 3(wlan0-1) entering disabled state
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entering forwarding state

comment:69 Changed 6 years ago by alex@…

same here: nanostation m2 loco with Linux 0027229A10DB 2.6.39.4 #131 Fri Apr 6 18:34:44 CEST 2012 mips GNU/Linux using 802.11s mode with 2 virtual ap

Apr 9 00:05:39 0027229A10DB daemon.info hostapd: wlan0: STA 00:26:08:ab:e5:02 RADIUS: starting accounting session 4F820815-00000001
Apr 9 00:16:48 0027229A10DB daemon.info hostapd: wlan0: STA 00:26:08:ab:e5:02 RADIUS: stopped accounting session 4F820815-00000001
Apr 9 00:16:48 0027229A10DB daemon.info hostapd: wlan0: STA 00:26:08:ab:e5:02 IEEE 802.11: disassociated due to inactivity
Apr 9 00:16:49 0027229A10DB daemon.info hostapd: wlan0: STA 00:26:08:ab:e5:02 IEEE 802.11: deauthenticated due to inactivity
Apr 9 00:27:20 0027229A10DB kern.err kernel: [ 2271.790000] ath: Failed to stop TX DMA, queues=0x001!
Apr 9 00:27:30 0027229A10DB kern.err kernel: [ 2281.870000] ath: Failed to stop TX DMA, queues=0x001!
Apr 9 00:28:23 0027229A10DB kern.err kernel: [ 2335.070000] ath: Failed to stop TX DMA, queues=0x001!
Apr 9 00:28:24 0027229A10DB kern.err kernel: [ 2335.420000] ath: Failed to stop TX DMA, queues=0x001!
Apr 9 00:32:44 0027229A10DB daemon.info hostapd: wlan0: STA 48:60:bc:55:0c:16 IEEE 802.11: authenticated
Apr 9 00:32:44 0027229A10DB daemon.info hostapd: wlan0: STA 48:60:bc:55:0c:16 IEEE 802.11: authenticated
Apr 9 00:32:44 0027229A10DB daemon.info hostapd: wlan0: STA 48:60:bc:55:0c:16 IEEE 802.11: associated (aid 1)
Apr 9 00:32:44 0027229A10DB daemon.info hostapd: wlan0: STA 48:60:bc:55:0c:16 RADIUS: starting accounting session 4F820815-00000002

config 'wifi-device' 'radio0'

option 'type' 'mac80211'
option 'htmode' 'HT20'
option 'ht_capab' 'TX-STBC RX-STBC1 DSSS_CCK-40'
option 'channel' '1'
option 'hwmode' '11g'
option 'disabled' '0'
option 'macaddr' '00:27:22:9a:10:db'

config 'wifi-iface'

option 'device' 'radio0'
option 'network' 'lan'
option 'mode' 'ap'
option 'encryption' 'none'
option 'isolate' '1'
option 'acct_server' 'ip'
option 'acct_port' '1645'
option 'acct_secret' 'secret'
option 'nasid' '1be'
option 'ssid' 'ssid'

config 'wifi-iface'

option 'device' 'radio0'
option 'network' 'wan'
option 'mode' 'mesh'
option 'mesh_id' '1'
option 'encryption' 'none'
option 'ssid' 'ssid'

comment:70 Changed 6 years ago by wellingtonuemura@…

I'm having the exact same problem.

Hardware: TP-Link WR1043ND v1.8
Software: Backfire (10.03.2, r31328)

Wireless configuration, 'erased' means that the info was deleted by me.

config 'wifi-device' 'radio0'
        option 'type' 'mac80211'
        option 'macaddr' 'erased'
        option 'hwmode' '11ng'
        option 'htmode' 'HT20'
        list 'ht_capab' 'SHORT-GI-40'
        list 'ht_capab' 'DSSS_CCK-40'
        option 'txpower' '27'
        option 'country' 'US'
        option 'channel' '7'

config 'wifi-iface'
        option 'device' 'radio0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'ssid' 'erased'
        option 'encryption' 'psk2+ccmp'
        option 'key' 'erased'
        option 'macfilter' 'allow'
        list 'maclist' 'erased'
        list 'maclist' 'erased'
        option 'disabled' '1'

System log message:

May  9 21:04:24 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: authenticated
May  9 21:04:24 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: associated (aid 1)
May  9 21:04:24 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: pairwise key handshake completed (RSN)
May  9 21:04:27 Aguia daemon.info dnsmasq-dhcp[824]: DHCPREQUEST(br-lan) 192.168.1.10 'erased' 
May  9 21:04:27 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May  9 21:04:27 Aguia daemon.info dnsmasq-dhcp[824]: DHCPREQUEST(br-lan) 192.168.1.10 'erased' 
May  9 21:04:27 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May  9 21:04:30 Aguia daemon.info dnsmasq-dhcp[824]: DHCPINFORM(br-lan) 192.168.1.10 'erased' 
May  9 21:04:30 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May  9 21:05:39 Aguia daemon.info dnsmasq-dhcp[824]: DHCPINFORM(br-lan) 192.168.1.10 'erased' 
May  9 21:05:39 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May  9 21:08:04 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: group key handshake completed (RSN)
May  9 21:14:22 Aguia daemon.info dnsmasq-dhcp[824]: DHCPINFORM(br-lan) 192.168.1.10 'erased' 
May  9 21:14:22 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May  9 21:18:04 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: group key handshake completed (RSN)
May  9 21:22:14 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:14 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:15 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:15 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:15 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:15 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:16 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:16 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:16 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:16 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:22:16 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x005!
...
May  9 21:22:24 Aguia user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May  9 21:27:18 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: disassociated due to inactivity
May  9 21:27:19 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: deauthenticated due to inactivity
May 10 20:14:16 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: authenticated
May 10 20:14:16 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: associated (aid 1)
May 10 20:14:16 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: pairwise key handshake completed (RSN)
May 10 20:14:16 Aguia daemon.info dnsmasq-dhcp[824]: DHCPDISCOVER(br-lan) 'erased' 
May 10 20:14:16 Aguia daemon.info dnsmasq-dhcp[824]: DHCPOFFER(br-lan) 192.168.1.10 'erased' 
May 10 20:14:16 Aguia daemon.info dnsmasq-dhcp[824]: DHCPREQUEST(br-lan) 192.168.1.10 'erased' 
May 10 20:14:16 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May 10 20:14:20 Aguia daemon.info dnsmasq-dhcp[824]: DHCPINFORM(br-lan) 192.168.1.10 'erased' 
May 10 20:14:20 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May 10 20:15:30 Aguia daemon.info dnsmasq-dhcp[824]: DHCPINFORM(br-lan) 192.168.1.10 'erased' 
May 10 20:15:30 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May 10 20:18:05 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: group key handshake completed (RSN)
May 10 20:24:10 Aguia daemon.info dnsmasq-dhcp[824]: DHCPINFORM(br-lan) 192.168.1.10 'erased' 
May 10 20:24:10 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May 10 20:28:05 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: group key handshake completed (RSN)
May 10 20:35:01 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: disassociated due to inactivity
May 10 20:35:02 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: authenticated
May 10 20:35:02 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: associated (aid 1)
May 10 20:35:02 Aguia daemon.info hostapd: wlan0: STA 'erased' WPA: pairwise key handshake completed (RSN)
May 10 20:35:02 Aguia daemon.info dnsmasq-dhcp[824]: DHCPREQUEST(br-lan) 192.168.1.10 'erased' 
May 10 20:35:02 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May 10 20:35:06 Aguia daemon.info dnsmasq-dhcp[824]: DHCPREQUEST(br-lan) 192.168.1.10 'erased' 
May 10 20:35:06 Aguia daemon.info dnsmasq-dhcp[824]: DHCPACK(br-lan) 192.168.1.10 'erased' 'erased'
May 10 20:38:14 Aguia daemon.info hostapd: wlan0: STA 'erased' IEEE 802.11: deauthenticated due to local deauth request

In general, this is followed by the router reboot by it self, I don't know how to reproduce the error because it's aleatory.

comment:71 Changed 6 years ago by P.TItera@…

I'm starting to wonder if this even is more hardware related. I have two routers at home one TPLink 841NDv7 and one TPLink 941NDv3. When I tesetd using the same release on both 841 had some major problems with wireless (connection drops or stalls, erros in log etc.) 941 does not show those problems and works flawlessly.

Petr

comment:72 Changed 6 years ago by nbd

It definitely happens more frequently on some chips than others, it also depends on the environment. I don't see these issues at all at home.
By the way, please try latest trunk to see if it reduces the severity and frequency of these issues.

comment:73 Changed 6 years ago by wellingtonuemura@…

Hardware: TP-Link WR1043ND v1.8
Software: Backfire (10.03.2, r31761)

Nothing change from previous, setup just the error message. This is the last firmware from Trunk, date 17-May-2012.

May 18 10:33:56 Aguia user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
May 18 10:33:57 Aguia user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
May 18 10:33:57 Aguia user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
May 18 10:33:57 Aguia user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
May 18 10:33:57 Aguia user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
May 18 10:33:57 Aguia user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
May 18 10:33:57 Aguia user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
May 18 10:33:57 Aguia user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
May 18 10:33:57 Aguia user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
May 18 10:33:58 Aguia user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
May 18 10:33:58 Aguia user.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
May 18 10:33:58 Aguia user.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020

comment:74 Changed 6 years ago by varac

Hi,

i am having the same issue, running OpenWrt Stable Backfire 10.03.1 on an Buffalo AirStation
Infiniti WZR-HP-G300NH.

Didn't try latest trunk because recent comments show no progress according to this issue.

May 22 10:23:55 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:23:56 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:01 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:37 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:38 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:41 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:47 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:48 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:49 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:49 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:24:57 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:25:06 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!
May 22 10:44:43 OpenWrt user.err kernel: ath: Failed to stop TX DMA, queues=0x004!

comment:75 follow-up: Changed 6 years ago by jow

Whats the point of your report then? It is well known that 10.03.1 has this issue. Pasting the same TX DMA line without context will reveal no useful information.

comment:76 Changed 6 years ago by djtempleton@…

Gargoyle build with OpenWrt backfire r30752
Maybe just be coincidence,
but I only notice the DMA stop error appearing when my lap top with a RealTek wireless chipset (RTL8191SE) is connected and transferring large amounts of data. Most noticeable when running torrents.
My other laptops which have Intel wireless chip sets don't appear to cause the DMA stop error, even when running torrents.

Dave.

comment:77 in reply to: ↑ 75 Changed 6 years ago by anonymous

Replying to jow:

Whats the point of your report then? It is well known that 10.03.1 has this issue. Pasting the same TX DMA line without context will reveal no useful information.

well, reporting on what hardware i experience this bug does provide useful information i.m.h.o.

and i hope saying that it affects more users (me = +1) would raise the importance of this bug.

comment:78 Changed 6 years ago by jow

We don't judge the importance of bugs by the number of "me too" comments.

comment:79 Changed 6 years ago by wellingtonuemura@…

Hardware: TP-Link WR1043ND v1.8
Software: Trunk (10.03.2, r31858)

I'm here just to report that the 'DMA' issue stoped at this version (so far), did some stress tests like connect/disconnect a dozen times, load the router wireless connection with huge files transfer (100GB+). My wife it's watching netflix right now with no issues.

r31858 looks pretty stable to me, no hang, no crash, no freezing, no erros at the syslog, no slowdown, CPU and network load are less than 1%.

comment:80 follow-up: Changed 6 years ago by nbd

Are you using trunk or the 10.03.2 branch?

comment:81 in reply to: ↑ 80 Changed 6 years ago by anonymous

Replying to nbd:

Are you using trunk or the 10.03.2 branch?

I'm using the Trunk version:
OpenWrt Attitude Adjustment r31858

comment:82 Changed 6 years ago by Newgel

Now I´m curious. Is there a 10.03.2 branch avaialble? I can only find 10.03.1 Final and trunk snapshoots at OpenWRT Downloads Site.

comment:83 Changed 6 years ago by nbd

well, there's a 10.03 branch (backfire), of which there will be a 10.03.2 release.

there's a prerelease build available at http://openwrt.linux-appliance.net/ar71xx/ but it doesn't have all the mac80211/ath9k changes from trunk.

comment:84 Changed 6 years ago by anonymous

Wellingtonuemura says above that problem are still present at r31761 and seems fixed at r31858, so I checked changelog and noticed kernel was upgraded to 3.3.7 between those releases. I checked http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.3.7 and looks like there was a patch to fix tx/rx issues, however I´m not a developer (far from that) and could be plain wrong here.
So, could the developers take a look at it and confirm whether kernel 3.3.7 has fixed these issues? Also, when can we expect a 10.03.2 Release Candidate with kernel 3.3.7? I would like to go with a RC version instead of trunk, since RCs packages are always available at OpenWRT download site (trunk ones changes every day and sooner or later we experience kernel/modules mismatches).

comment:85 Changed 6 years ago by nbd

The kernel version is irrelevant for wifi related issues, we build mac80211/ath9k outside of the kernel tree.

comment:86 Changed 6 years ago by wellingtonuemura@…

I still confirm that the TX/RX errors are gone (r31858), router it's working non stop so far 100%.

comment:87 Changed 6 years ago by blindbox

I'm currently on r32002.

I don't seen any TX/RX errors yet. The wifi has also been stable all day. However, I have a cronjob running that restarts the wifi twice a day.

I'll report again by monday, without the cronjob.

comment:88 Changed 6 years ago by nbd

  • Resolution set to fixed
  • Status changed from accepted to closed

comment:89 Changed 6 years ago by garlew

  • Resolution fixed deleted
  • Status changed from closed to reopened

1043ND, ATTITUDE ADJUSTMENT (Bleeding Edge, r32012)
much better but still broken
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020

comment:90 Changed 6 years ago by nbd

  • Resolution set to duplicate
  • Status changed from reopened to closed

why did you have to reopen two tickets for the same issue?
continued in #9654

comment:91 Changed 6 years ago by anonymous

Do any of you guys have a bin around r31858 for openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin I inadvertently deleted mine after updating to trunk (jul 23). It's not stable for me and I'd like to revert.

Sorry for posted in a closed thread.

comment:92 Changed 6 years ago by dollarsignfoo@…

Does anyone have a stable bin (openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin)? I'm using a TP-Link TL-WR1043ND v1.4. Or would anyone be kind enough to compile me a bin somewhere around r31858?

comment:93 Changed 5 years ago by rav1ne

Bah...this error was fixed months ago, now i'm getting that same error with the latest Attitude Adjustment release 12.09-beta2 (probably same with BB).

comment:94 Changed 5 years ago by anonymous

  • Resolution duplicate deleted
  • Status changed from closed to reopened

Hardware: TP-Link WR1043ND v1.8
Software: BARRIER BREAKER (trunk,r34122)
Kernel: 3.3.8

The issue is still exists in a latest trunk version (r34122).
Here is the output from dmesg:

[352112.100000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[352114.660000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352114.900000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352115.840000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352116.080000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352116.320000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352117.260000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352118.200000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352118.440000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352119.380000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352119.850000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352120.100000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352121.040000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352122.450000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352123.400000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352127.580000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352130.600000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352135.710000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352135.950000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352136.890000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[352140.610000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[352140.850000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[352141.790000] ath: phy0: Failed to stop TX DMA, queues=0x004!

comment:95 Changed 5 years ago by jow

  • Resolution set to invalid
  • Status changed from reopened to closed

And the issue still is a duplicate of #9654

comment:96 Changed 4 years ago by xhz900@…

  • Resolution invalid deleted
  • Status changed from closed to reopened

Hardware: Mercury MW4530R same hardware as TPLink WDR4300
Software: Attitude Adjustment 12.09.1 r37747
Kernel: 3.3.8
I'm also experiencing it.

[1882560.230000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1882999.160000] ath: phy0: Failed to stop TX DMA, queues=0x104!
[1883005.240000] ath: phy0: Failed to stop TX DMA, queues=0x104!
[1883005.470000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1883010.220000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1883022.230000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1884340.590000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1939989.840000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1939992.230000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1939992.460000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1942298.880000] ath: phy0: Failed to stop TX DMA, queues=0x005!
[1950562.910000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1950587.110000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1951530.660000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[1964994.380000] ath: phy0: Failed to stop TX DMA, queues=0x006!
[1985152.620000] HTB: quantum of class 11006 is small. Consider r2q change.
[1985152.690000] HTB: quantum of class 11006 is small. Consider r2q change.
[1985152.800000] HTB: quantum of class 11002 is small. Consider r2q change.
[1985152.870000] HTB: quantum of class 11002 is small. Consider r2q change.
[2008724.930000] ath: phy0: Failed to stop TX DMA, queues=0x004!

comment:97 Changed 4 years ago by nbd

  • Resolution set to duplicate
  • Status changed from reopened to closed

Please update to a newer version. Also, please do *NOT* reopen tickets that have already been marked as duplicate.

comment:98 Changed 4 years ago by anonymous

Hardware: TP-Link WR1043ND v1.7
Software: Barrier Breaker r38636 / LuCI Trunk (svn-r9932)
Kernel: 3.10.17

The issue is still exists in trunk version r38636.
Here is the output from dmesg:

[243322.860000] ath: phy0: Failed to stop TX DMA, queues=0x008!
[243323.130000] ath: phy0: Failed to stop TX DMA, queues=0x008!
[243323.400000] ath: phy0: Failed to stop TX DMA, queues=0x008!
[243323.670000] ath: phy0: Failed to stop TX DMA, queues=0x008!
[243323.940000] ath: phy0: Failed to stop TX DMA, queues=0x009!
[273279.950000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[273279.960000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[276216.440000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[276216.450000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

comment:99 Changed 4 years ago by anonymous

  • Resolution duplicate deleted
  • Status changed from closed to reopened

Hardware: TP-Link WR1043ND v1.7
Software: Barrier Breaker r38647 / LuCI Trunk (svn-r9933)
Kernel: 3.10.17

The issue is still exists in trunk version r38636.
Here is the output from dmesg:

[ 6909.620000] ath: phy0: Failed to stop TX DMA, queues=0x009!
[ 6909.890000] ath: phy0: Failed to stop TX DMA, queues=0x008!
[ 6939.480000] ath: phy0: Failed to stop TX DMA, queues=0x001!
[63446.470000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[63446.480000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[63448.030000] ath: phy0: Failed to stop TX DMA, queues=0x008!
[63450.360000] ath: phy0: Failed to stop TX DMA, queues=0x00c!
[63454.490000] ath: phy0: Failed to stop TX DMA, queues=0x004!

comment:100 Changed 4 years ago by jow

  • Resolution set to duplicate
  • Status changed from reopened to closed

And the issue still is a duplicate of #9654

comment:101 Changed 4 years ago by jow

  • Milestone changed from Backfire 10.03.2 to Chaos Calmer (trunk)

Milestone Backfire 10.03.2 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.