Opened 7 years ago
Last modified 22 months ago
#9654 reopened defect
ath: DMA failed to stop in 10 ms
| Reported by: | anonymous | Owned by: | nbd |
|---|---|---|---|
| Priority: | normal | Milestone: | Barrier Breaker 14.07 |
| Component: | kernel | Version: | Trunk |
| Keywords: | atheros | Cc: |
Description
in my log:
{{{Jul 4 12:35:34 deepblue kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
Jul 4 12:35:34 deepblue kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up}}}
Attachments (6)
Change History (576)
comment:1 Changed 7 years ago by anonymous
comment:2 Changed 7 years ago by nbd
- Resolution set to fixed
- Status changed from new to closed
fixed in r27482
comment:3 Changed 7 years ago by Pilot6 <hanipouspilot@…>
- Resolution fixed deleted
- Status changed from closed to reopened
Not fixed.
Jul 7 09:24:21 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040 Jul 7 09:24:21 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
trunk r27489 tp-link 1043.
comment:4 follow-up: ↓ 483 Changed 6 years ago by nbd
please try current trunk, it should be fixed there.
comment:5 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I tried. Not fixed. trunk r27979
Aug 16 15:56:51 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:51 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:56:51 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:52 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:52 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:52 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:52 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:52 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:52 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:52 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:52 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:53 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:53 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:53 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:53 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:53 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:53 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:53 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:53 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:54 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:54 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:54 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:54 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:54 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:54 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:54 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:54 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:55 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:55 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:55 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:55 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:55 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:55 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:55 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:55 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 Aug 16 15:56:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:56:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:56:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:56:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:57 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:56:57 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:57 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:56:57 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:57 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:57 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:57 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:57 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:59 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:59 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:59 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:59 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:59 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:59 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:56:59 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:56:59 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:00 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:00 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:00 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:00 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:00 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:00 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:00 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:00 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:01 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:01 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:01 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:01 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:01 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:01 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:01 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:01 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:02 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:02 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:02 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:02 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:02 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:02 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:02 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:02 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:03 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:03 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:03 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:03 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:03 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 Aug 16 15:57:03 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:03 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Aug 16 15:57:03 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:04 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 Aug 16 15:57:04 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:04 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:04 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:04 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:04 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:04 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:04 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 Aug 16 15:57:05 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 Aug 16 15:57:05 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Aug 16 15:57:05 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Aug 16 15:57:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020
comment:6 Changed 6 years ago by nbd
please try latest trunk
comment:7 Changed 6 years ago by Pilot6 <hanipouspilot@…>
Compiled. Installed. Testing.
comment:8 Changed 6 years ago by Pilot6 <hanipouspilot@…>
Not fixed r28114. Does it make sense to test a few later updates or no?
comment:9 Changed 6 years ago by nbd
yes, please test a later version
comment:10 Changed 6 years ago by nbd
- Owner changed from developers to nbd
- Status changed from reopened to accepted
comment:11 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I do not see the error so far, but wireless is unusable now.
See /ticket/10031.html
comment:12 Changed 6 years ago by nbd
found and fixed another crash bug, please try the latest version
comment:13 Changed 6 years ago by Pilot6 <hanipouspilot@…>
Not fixed r28143
comment:14 Changed 6 years ago by nbd
what's not fixed, the DMA error or wireless being unusable?
comment:15 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I post regarding this tiket. DMA error is not fixet. The other issue IS fixed.
comment:16 Changed 6 years ago by Pilot6 <hanipouspilot@…>
After some testing I can say what became better. Wifi die NOT disconnect any more when these errors come.
comment:17 Changed 6 years ago by Pilot6 <hanipouspilot@…>
typo. does NOT.
comment:18 Changed 6 years ago by giuseppe_stolnicu@…
Am getting the same with r28173. By the way, the disassociation/deauthentification due to inactivity happened while I was very much active and after that the router did not respond over wireless.
my log:
Sep 8 20:23:48 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 8 20:23:48 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:23:48 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:23:48 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:23:48 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:23:50 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 8 20:23:50 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:23:50 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:23:50 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:23:50 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:23:53 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:23:53 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:23:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:23:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:23:59 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:23:59 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:02 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:02 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:05 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:09 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:09 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:12 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:12 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:16 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:16 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:20 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:20 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:22 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 8 20:24:22 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:24:22 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:23 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:24:23 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:25 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:25 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:28 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:28 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:30 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 8 20:24:30 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:24:30 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:31 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: disassociated due to inactivity Sep 8 20:24:32 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: deauthenticated due to inactivity Sep 8 20:24:32 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 8 20:24:32 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:32 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:36 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:36 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:38 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:24:38 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:41 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:41 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:44 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:44 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:46 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:46 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:50 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:50 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:53 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:53 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:24:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:24:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:00 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:25:00 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:04 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:04 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:08 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:08 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:13 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:25:13 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:17 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:17 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:22 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:25:22 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:27 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:27 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:32 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:32 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:43 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:25:43 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:49 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:25:49 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:25:55 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:25:55 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:01 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:26:01 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:07 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:26:07 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:14 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:26:14 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:21 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:26:21 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:28 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:26:28 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:35 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:26:35 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:42 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:26:42 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:50 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:26:50 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:26:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:26:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:06 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:06 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:14 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:14 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:22 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:22 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:31 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:31 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:40 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:40 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:49 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:49 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:27:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:27:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:28:08 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:28:08 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:28:17 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:28:17 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:28:27 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 8 20:28:27 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:28:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:28:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 8 20:28:48 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 8 20:28:48 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:19 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>
Actually it seems that my wireless network crashed, it is not visible anymore. After a couple minutes it dissapeared from the NetworkManager list (Ubuntu 11.04).
comment:20 Changed 6 years ago by nbd
please try r28203, i found and fixed a bug that could be directly related to this.
comment:21 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>
Yeah, I think your patch fixed it, after an hour of heavy traffic I am not getting any "DMA failed to stop in 10 ms" msgs.(In r28173 I got the msg in max 10 mins after starting the torrent client).
Am still getting connection quality drops (fixable by reconnecting to the network - ping of 28840.340) and I also got an kernel warn in linux-ar71xx_generic/compat-wireless-2011-08-26/net/mac80211/rx.c with the msg "Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 83 (0x53)", but I guess those are different bugs.
Thanx again.
comment:22 Changed 6 years ago by anonymous
confirm fixed DMA failed to stop in 10 ms error msg for me as of Openwrt | Attitude Adjustment (r28202) on Buffalo WZR-HP-G300NH after 18 hrs running
Nice work
comment:23 Changed 6 years ago by Pilot6 <hanipouspilot@…>
18 hours is not enough for testing. This error may cone in 3-4 days. I will install on Monday. After a week testing it will be possible to tell.
comment:24 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>
I got the damn message again after 1 day of uptime. my "dmesg | tail" :
---[ end trace bfdc6702640cd33f ]--- ath: Failed to stop TX DMA! ath: Failed to stop TX DMA! 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 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=0x000242c0 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:25 Changed 6 years ago by Giuseppe Stolnicu <giuseppe_stolnicu@…>
By the way my hardware is Linksys WRT160NL.
comment:26 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I never get
ath: Failed to stop TX DMA!
only
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000242c0
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:27 Changed 6 years ago by nbd
is it always the same value for DMADBG_7?
comment:28 Changed 6 years ago by Pilot6 <hanipouspilot@…>
Not one value. You can see my log I posted earlier. It is still same.
comment:29 Changed 6 years ago by nbd
with which version? trunk or backfire?
comment:30 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I did not test Backfire for some time. But my users use both trunk and Backfire builds. They report same error. The latest I tested is r28143. Now I am compiling the latest.
comment:31 Changed 6 years ago by Pilot6 <hanipouspilot@…>
But one user gets "Failed to stop TX DMA!"
I always wonder why only he does. Same hardware, nothing specific with clients.
comment:32 Changed 6 years ago by nbd
probably depends on the environment and the amount of network activity.
comment:33 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I did not noyice any correlation with network activity. Sometimes error come when no wireless devices are associated, sometimes under high torrent or something like that usage.
The error usually does not come up in first 24 hours after restart. I suspect some variable, like a counter is overflown. This bug must be simple and stupid. I used to find bugs like this. But in this case I can't help, because I know almost nothing about wireless protocols.
comment:34 Changed 6 years ago by nbd
It doesn't have to be *your* network activity. Probe requests and (and probe responses sent by your AP) also count as activity.
Also, I'm not going to look into any test feedback from older versions such as the one that you mentioned, because those had some nasty race conditions in the reset / channel change code, which could be responsible for all kinds of weird DMA issues.
I'm pretty sure the "DMA failed to stop in 10 ms" logspam isn't the only thing caused by that bug.
comment:35 Changed 6 years ago by Pilot6 <hanipouspilot@…>
OK. Now I installed r28208. Let's see...
comment:36 Changed 6 years ago by Pilot6 <hanipouspilot@…>
comment:37 Changed 6 years ago by Pilot6 <hanipouspilot@…>
One user already catched at r 28208
Sep 10 22:55:24 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 10 22:55:24 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 10 22:55:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 10 22:55:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 10 22:55:46 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 10 22:55:46 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:38 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I catched too r28202
Sep 11 02:03:19 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 11 02:03:19 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040 Sep 11 02:03:19 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:03:19 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Sep 11 02:03:19 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:04:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:04:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:05:24 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 11 02:05:24 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:05:24 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:05:24 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Sep 11 02:05:24 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:06:15 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:06:15 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:07:04 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd IEEE 802.11: disassociated due to inactivity Sep 11 02:07:05 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 11 02:07:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:07:05 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:07:05 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd IEEE 802.11: deauthenticated due to inactivity Sep 11 02:07:05 OpenWrt kern.err kernel: ath: Failed to stop TX DMA! Sep 11 02:07:05 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 Sep 11 02:07:05 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:07:56 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:07:56 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:08:46 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:08:46 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:09:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:09:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:10:28 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:10:28 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:11:19 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:11:19 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:12:11 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:12:11 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:13:02 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:13:02 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:13:54 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:13:54 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:14:47 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:14:47 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:15:39 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:15:39 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:16:31 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:16:31 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:17:24 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:17:24 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:18:17 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:18:17 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:19:11 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:19:11 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:20:04 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:20:04 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:20:58 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:20:58 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:21:52 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:21:52 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:22:46 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:22:46 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:23:40 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:23:40 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:24:35 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:24:35 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:25:29 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 11 02:25:29 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:26:24 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:26:24 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:27:19 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 11 02:27:19 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 11 02:27:28 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd IEEE 802.11: authenticated Sep 11 02:27:28 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd IEEE 802.11: associated (aid 1) Sep 11 02:27:28 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd WPA: pairwise key handshake completed (RSN) Sep 11 02:46:51 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd WPA: group key handshake completed (RSN) Sep 11 03:46:51 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd WPA: group key handshake completed (RSN) Sep 11 04:46:51 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd WPA: group key handshake completed (RSN) Sep 11 05:46:51 OpenWrt daemon.info hostapd: wlan0: STA 00:26:ab:1d:6d:bd WPA: group key handshake completed (RSN)
comment:39 Changed 6 years ago by Pilot6 <hanipouspilot@…>
And wireless disconnected during that time.
comment:40 Changed 6 years ago by Pilot6 <hanipouspilot@…>
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:41 Changed 6 years ago by Pilot6 <hanipouspilot@…>
Why not do like in Tp-link stock firmware? When DMA can't stop, just restart wireless. Disconnects would be so short, so noone will notice them.
comment:42 Changed 6 years ago by nbd
The message already only appears when the driver is resetting the hardware.
comment:43 Changed 6 years ago by alphasparc
Hi,
The people developing chrome os has the same issue with Atheros Wireless and they have fixes by patching compat-wireless maybe you guys would want to take a look at that.
http://code.google.com/p/chromium-os/issues/detail?id=13275
comment:44 Changed 6 years ago by nbd
I don't think that chromeos has any relevant changes that haven't made it upstream already. The DMA issue has always been much more severe on embedded hardware compared to regular PCs.
comment:45 Changed 6 years ago by stefan@…
I'm having the the same problem with my TP-Link device (r28173), however I am trying to use this watchdog script now:
#!/bin/sh # wifi-watchdog.sh by Stefan Tomanek <stefan@pico.ruhr.de> /sbin/logread -f | grep 'ath: Could not stop RX, we could be confusing the DMA engine when we start RX up' | while read LINE; do /sbin/wifi # restart wifi done
comment:46 Changed 6 years ago by Pilot6 <hanipouspilot@…>
This would be a solution, if implemented in the code. That's what I was talking about. But using a script is not too good. But I use a similar one.
comment:47 Changed 6 years ago by giuseppe_stolnicu@…
r28301 Linksys WRT160NL
root@OpenWrt:~# dmesg | tail ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: Failed to stop TX DMA, queues=00000004! ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: Failed to stop TX DMA, queues=00000004! ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: Failed to stop TX DMA, queues=00000004! ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Sep 26 15:44:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Sep 26 15:44:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 26 15:44:37 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004! Sep 26 15:44:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Sep 26 15:44:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Sep 26 15:44:41 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: authenticated Sep 26 15:44:41 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb IEEE 802.11: associated (aid 2) Sep 26 15:44:41 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:0f:6c:cb WPA: pairwise key handshake completed (RSN) Sep 26 15:44:41 OpenWrt daemon.info dnsmasq-dhcp[1296]: DHCPREQUEST(br-lan) 192.168.1.219 18:f4:6a:0f:6c:cb Sep 26 15:44:41 OpenWrt daemon.info dnsmasq-dhcp[1296]: DHCPACK(br-lan) 192.168.1.219 18:f4:6a:0f:6c:cb DevilsOrchard
comment:48 Changed 6 years ago by anonymous
Not fixed. trunk r28241. tp-link 1043.
comment:49 Changed 6 years ago by anonymous
Trunk r28344 TP-Link 1043ND
Oct 5 20:10:29 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:29 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:29 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:29 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004! Oct 5 20:10:29 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:29 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:29 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:29 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:30 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:30 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:30 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:30 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:30 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:30 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:30 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:30 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:31 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:31 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:31 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:31 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:31 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:31 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:31 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:31 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:32 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:32 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:32 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:32 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:32 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004! Oct 5 20:10:32 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 Oct 5 20:10:32 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:33 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:33 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:33 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:33 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:33 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:33 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:33 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:33 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:34 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004! Oct 5 20:10:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:34 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:34 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:35 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:35 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:35 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024020 Oct 5 20:10:35 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:35 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:35 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:35 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:35 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:36 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:36 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:36 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:36 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:36 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:36 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:36 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004! Oct 5 20:10:36 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:36 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:37 OpenWrt kern.err kernel: ath: Failed to stop TX DMA, queues=00000004! Oct 5 20:10:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:10:37 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Oct 5 20:10:37 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 5 20:11:09 OpenWrt daemon.info hostapd: wlan0: STA 0c:ee:e6:db:03:0e IEEE 802.11: authenticated Oct 5 20:11:09 OpenWrt daemon.info hostapd: wlan0: STA 0c:ee:e6:db:03:0e IEEE 802.11: associated (aid 1) Oct 5 20:11:09 OpenWrt daemon.info hostapd: wlan0: STA 0c:ee:e6:db:03:0e WPA: pairwise key handshake completed (RSN) Oct 5 20:11:09 OpenWrt daemon.info dnsmasq-dhcp[10376]: DHCPREQUEST(br-lan) 192.168.1.5 0c:ee:e6:db:03:0e
comment:50 Changed 6 years ago by nbd
might be fixed in r28383, please test
comment:51 Changed 6 years ago by Pilot6 <hanipouspilot@…>
Not fixed in r28395
Oct 10 13:48:17 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 Oct 10 13:48:17 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:52 follow-up: ↓ 59 Changed 6 years ago by Pilot6 <hanipouspilot@…>
This bug exists only on AR91xx devices. On AR92xx wifi works well on all builds.
comment:53 Changed 6 years ago by anonymous
catched at r28412 tp-link 1043
Oct 12 10:04:20 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 Oct 12 10:04:20 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 12 10:04:20 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 Oct 12 10:04:20 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 12 10:04:21 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 Oct 12 10:04:21 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 12 10:04:21 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 Oct 12 10:04:21 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 12 10:04:21 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 Oct 12 10:04:21 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Oct 12 10:04:21 OpenWrt kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008020 Oct 12 10:04:21 OpenWrt kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:54 Changed 6 years ago by anonymous
build Attitude Adjustment (r28428) on TP-LINK 1043 v1.8
{{{ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA, queues=0x005!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
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=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
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=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA, queues=0x001!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
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=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA, queues=0x005!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
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=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
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=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
}}}
comment:55 Changed 6 years ago by anonymous
build Attitude Adjustment (r28601) on Buffalo WZR-HP-G300NH
2011-10-27T19:34:31+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:54+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:54+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 2011-10-27T20:07:54+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:55+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:55+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040 2011-10-27T20:07:55+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:55+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:55+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:55+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:56+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:56+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:56+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:56+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:56+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:56+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:56+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:56+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:56+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:57+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:57+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:57+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:57+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:57+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:57+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:57+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:57+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:57+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:57+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:57+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:58+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:07:58+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:58+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:58+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:58+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:58+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:58+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:58+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:58+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:58+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:58+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:58+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:59+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:07:59+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:59+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:59+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:59+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:59+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:59+03:00: ath: Failed to stop TX DMA, queues=0x005! 2011-10-27T20:07:59+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:59+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:07:59+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:07:59+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:07:59+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:00+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:00+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:00+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:00+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:00+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:00+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:00+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:00+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:00+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:01+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:01+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:01+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:01+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:01+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:01+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:01+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:01+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:01+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:01+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:01+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:01+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:02+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:02+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:02+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:02+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:02+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:02+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:02+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:02+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:02+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:02+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:02+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:02+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:03+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:03+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:03+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:03+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:03+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:03+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:03+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:03+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:03+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:03+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:03+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:03+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:04+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:04+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:04+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:04+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:04+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:04+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:04+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:04+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:04+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:04+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:04+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:04+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:05+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:05+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:05+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:05+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:05+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:05+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:05+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:05+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:05+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:05+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:05+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:05+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:06+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:06+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:06+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:06+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:06+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:06+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:06+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:06+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:06+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:06+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:06+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:06+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:07+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:07+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:07+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:07+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:07+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:07+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:07+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:07+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:07+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:08+03:00: ath: Failed to stop TX DMA, queues=0x00c! 2011-10-27T20:08:08+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:08+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:08+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:08+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:08+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:08+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:08+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:08+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:08+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:08+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:08+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:09+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:09+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:09+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:09+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:09+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:09+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:09+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:09+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:09+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:09+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:09+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:09+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:10+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:10+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:11+03:00: ath: Failed to stop TX DMA, queues=0x004! 2011-10-27T20:08:11+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:11+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:11+03:00: ath: Failed to stop TX DMA, queues=0x104! 2011-10-27T20:08:11+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:11+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:11+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:11+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:12+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:12+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:12+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:12+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:12+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:12+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:12+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:12+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:12+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:13+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:13+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:13+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:13+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:13+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:13+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:13+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:13+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:13+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:13+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:14+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:14+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:14+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:14+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:14+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:14+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:14+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:14+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:14+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:14+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:15+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:15+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:15+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:15+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:15+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:15+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:15+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:15+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:15+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:15+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:16+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:16+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:16+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:16+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:16+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:16+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:16+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:16+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:16+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:17+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:17+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:17+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:17+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:17+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:17+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:17+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 2011-10-27T20:08:17+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:18+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:18+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:18+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:18+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:18+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:18+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:18+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:18+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:18+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:19+03:00: ath: Failed to stop TX DMA, queues=0x100! 2011-10-27T20:08:19+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:19+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:19+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:19+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:20+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 2011-10-27T20:08:20+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up 2011-10-27T20:08:20+03:00: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 2011-10-27T20:08:20+03:00: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:56 Changed 6 years ago by nicolas_dh
Hello, on a mid to light network usage
OpenWrt Firmware Attitude Adjustment (r28499) / LuCI Trunk (trunk+svn7765)
on a Buffalo WZR-HP-G300NH using Encryption: WPA2 PSK (CCMP)
wifi used to drop within 1-2 days before this snapshot, but
with r28499, wifi seems to remain available since last reboot:
Uptime 8d 20h 26m 45s
Although we also see 92 instances
of the following lines in the "Kernel Log"
*
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
*
comment:57 Changed 6 years ago by nbd
please try the latest version
comment:58 Changed 6 years ago by tachemihai@…
Still happening in r29152 on WRT160NL.
comment:59 in reply to: ↑ 52 Changed 6 years ago by anonymous
Replying to Pilot6 <hanipouspilot@…>:
This bug exists only on AR91xx devices. On AR92xx wifi works well on all builds.
I have a D-Link Dir-615 rev E5 with a AR9287 and Backfire rc-6 (r28719). Testing with iperf sometimes the wireless bitrate goes to less than 500 k, and most of that times i get from logread:
ath: Failed to stop TX DMA, queues=00000004!
Do you know if in older versions it could work better?
comment:60 Changed 6 years ago by nbd
the warnings might still be there, but the throughput drops or disconnect issues should be gone in latest backfire/trunk svn versions. please test
comment:61 follow-up: ↓ 62 Changed 6 years ago by Pilot6 <hanipouspilot@…>
I confirm that the issue is fixed since r28713 for TP-Link 1043.
comment:62 in reply to: ↑ 61 ; follow-up: ↓ 63 Changed 6 years ago by mad@…
Replying to Pilot6 <hanipouspilot@…>:
I confirm that the issue is fixed since r28713 for TP-Link 1043.
not fixed yet
comment:63 in reply to: ↑ 62 Changed 6 years ago by anonymous
Nov 24 05:25:52 WRT kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
Nov 24 05:25:52 WRT kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Nov 24 05:25:53 WRT kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
Nov 24 05:25:53 WRT kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Nov 24 05:25:53 WRT kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
comment:64 Changed 6 years ago by ispyisail@…
comment:65 Changed 6 years ago by ispyisail@…
Update on my post above
I was using Gargoyle and I believe is was build against r29342 and not r29323 as stated above. The test Router is TP-Link TL-WR1043ND v1-1.8
That version of Gargoyle was build with "Tor Anonymity Online". When Tor was enabled I would repeatedly get above errors.
When Tor was disabled the router worked perfect
comment:66 Changed 6 years ago by devwatchdog@…
I'm seeing the same thing.
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x4
2000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7
=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7
=0x00006040
(several hundred cut for the sake o' brevity)
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7
=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Data bus error, epc == 801365e4, ra == 8039c4a8
Oops[#1]:
Cpu 0
$ 0 : 00000000 1000f800 80ca9660 00000001
$ 4 : c0220024 00000024 00000024 00000240
$ 8 : 1000f800 1000001f 00000000 00000000
$12 : 8027d320 0000002a 802eee80 00470000
$16 : 80298000 80298000 00000001 00000020
$20 : 00010000 00000000 802d0000 00000001
$24 : 00477b44 803e1644
$28 : 80276000 80277bb8 80280000 8039c4a8
Hi : 00000000
Lo : 00000240
epc : 801365e4 0x801365e4
Tainted: P
ra : 8039c4a8 0x8039c4a8
Status: 1000b802 KERNEL EXL
Cause : 0080001c
PrId : 00029006 (Broadcom BMIPS3300)
Modules linked in: ath_pci ath_hal(P) 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 pppoe pppox ipt_REJEC
T xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptab
le_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k ath9k_co
mmon ath9k_hw ath mac80211 crc_ccitt cfg80211 compat arc4 aes_generic crypto_alg
api switch_adm switch_core
Process swapper (pid: 0, threadinfo=80276000, task=80279be0, tls=00000000)
Stack : 00000009 80ca9660 80298000 00000000 80ca9660 80298000 00000001 803e5748
8027bd50 80054100 00000000 8027dbb4 00000020 00000001 00000001 80f69300
8027dbb4 00000006 00000000 80051328 802c0000 800070d0 802c77e0 800070d0
8027dbb4 8027b64c 00000020 80280000 00010000 00000001 fffffffe 8027b768
8027bd50 80054100 00000000 1000f801 12b00000 00000083 8027b580 00000006
...
Call Trace:[<80298000>] 0x80298000
[<80298000>] 0x80298000
[<803e5748>] 0x803e5748
[<80054100>] 0x80054100
[<80051328>] 0x80051328
[<800070d0>] 0x800070d0
[<800070d0>] 0x800070d0
[<80054100>] 0x80054100
[<80050c8c>] 0x80050c8c
[<80298000>] 0x80298000
[<803830c8>] 0x803830c8
[<80298000>] 0x80298000
[<800070d0>] 0x800070d0
[<800054a4>] 0x800054a4
[<80391340>] 0x80391340
[<80048314>] 0x80048314
[<801239a4>] 0x801239a4
[<80298000>] 0x80298000
[<803e1644>] 0x803e1644
[<8039c398>] 0x8039c398
[<8039c398>] 0x8039c398
[<80298000>] 0x80298000
[<803e5498>] 0x803e5498
[<800422b8>] 0x800422b8
[<80022468>] 0x80022468
[<800229a4>] 0x800229a4
[<802a0000>] 0x802a0000
[<802a6068>] 0x802a6068
[<802a0000>] 0x802a0000
[<80022c08>] 0x80022c08
[<802a6068>] 0x802a6068
[<80022e00>] 0x80022e00
[<800054a4>] 0x800054a4
[<800056c0>] 0x800056c0
[<802a6068>] 0x802a6068
[<802a0000>] 0x802a0000
[<80016e08>] 0x80016e08
[<80007128>] 0x80007128
[<80007128>] 0x80007128
[<8028991c>] 0x8028991c
[<802a6068>] 0x802a6068
[<8028921c>] 0x8028921c
Code: 00431025 03e00008 3042ffff <8c820000> 03e00008 00000000 8c830000 0003
2602 00031600
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 3 seconds
Linux version 3.0.3 (jcwx@aeval) (gcc version 4.5.4 20110808 (prerelease) (Linar
o GCC 4.5-2011.08) ) #1 Wed Nov 16 14:25:17 CST 2011
CPU revision is: 00029006 (Broadcom BMIPS3300)
Can provide more if necessary, or test as well.
This is on a Belkin F5D8230-4 that originally came with an Airgo pre-N card. It has a standard mini-PCI slot so anything can be used. I have a Sparklan WMIA-199N installed now, which is a dual radio card (Atheros AR9160 + AR9106).
comment:67 Changed 6 years ago by openwrt@…
I get this with my backfire branch from svn 29502 on TP-Link WR1043ND, the router spits out lots of line like:
<pre>
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
</pre>
and the wifi completely stalls out for a while, sometimes 30 seconds, occaisionally needs reset.
It particularly happens when i change wireless network away and back to my SSID on this device from my macbook pro.
comment:68 Changed 6 years ago by Crazy Hank
Problem continues on TP-Link WR1043ND v1.8 running 10.03.1 interim release:
root@OpenWrt:~# dmesg
00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[...]
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020
root@OpenWrt:~# cat /etc/openwrt_version
10.03.1
When the error messages show up, the wireless link becomes unreliable. The connection drops out, AP SSID disappears from client, etc. Worse in g+n mode than g-only.
comment:69 Changed 6 years ago by jow
Those "me too" comments do not help at all, sorry. Attempt to capture traffic and logs during the dropouts (http://wiki.openwrt.org/doc/devel/debugging#wireless) and mention the involved client chipset types.
comment:70 Changed 6 years ago by nbd
please check if latest backfire branch (not the 10.03.1 release) or trunk still has this issue.
comment:71 Changed 6 years ago by Marcos Tadeu <marcos@…>
comment:72 Changed 6 years ago by anonymous
OpenWRT 10.03.1 on TP-Link WR1043ND, when downloading much, through WIFI.
kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
kernel: ath: Failed to stop TX DMA, queues=0x001!
hostapd: wlan0: STA 00:14:a4:74:45:cd IEEE 802.11: deauthenticated due to inactivity
kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020
kernel: ath: Failed to stop TX DMA, queues=0x005!
hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated due to inactivity
hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity
hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated due to inactivity
kernel: ath: Failed to stop TX DMA, queues=0x001!
hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity
kernel: ath: Failed to stop TX DMA, queues=0x005!
hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated due to inactivity
kernel: ath: Failed to stop TX DMA, queues=0x001!
hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity
kernel: ath: Failed to stop TX DMA, queues=0x005!
comment:73 Changed 6 years ago by anonymous
Attitude Adjustment (r30013)
[ 723.630000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[ 723.640000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:74 Changed 6 years ago by bsilva
just to add that it also happens on TP-Link WR1043ND, Attitude Adjustment (r30013), but with kernel 3.2.2.
comment:75 Changed 6 years ago by anonymous
DMADBG_7 0x000286c0
comment:76 Changed 6 years ago by marlonsc@…
I have this issue too. It was more frequent with high network load.
The project Chromium-OS has this issue too. Please check the patches for the ath9k and ath6k platforms they produced.
comment:77 Changed 6 years ago by nbd
I don't think chromium has any fixes that we don't have in our tree in trunk already.
comment:78 follow-up: ↓ 79 Changed 6 years ago by marcelvdh@…
Running r30919 on TP-Link TL-WR1043N/ND v1 and wireless has been rock solid so far (20h 38m 5s). Have about 3 wifi devices and 2 lan devices running off it.
On latest Backfire build the error used to happens at least every hour and wireless needed to be restarted.
So far so good, thanks for all the ath9k patches OpenWRT team!
comment:79 in reply to: ↑ 78 Changed 6 years ago by anonymous
Error fianlly appeared in kernel ring buffer:
[211930.500000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[211930.510000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
however wireless continued to work perfectly for all clients (Uptime 2d 20h 37m 49s).
comment:80 Changed 6 years ago by Daniel Holm <d.holmen@…>
I had my router up for 12 days and now, today, this issue occured and kicked all of my three devices out. Running r30753
comment:81 Changed 6 years ago by marcelvdh@…
I wonder if there's any logging that can be activated to help/enable the devs to get to the bottom of the issue.
comment:82 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!
or:
[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
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:83 Changed 6 years ago by nicke_rejv@…
I have also tried with the latest build ATTITUDE ADJUSTMENT (bleeding edge, r30919)
# dmesg | tail
[ 928.840000] ath: Failed to stop TX DMA, queues=0x004!
[ 929.070000] ath: Failed to stop TX DMA, queues=0x004!
[ 929.300000] ath: Failed to stop TX DMA, queues=0x004!
[ 929.520000] ath: Failed to stop TX DMA, queues=0x004!
[ 933.960000] ath: Failed to stop TX DMA, queues=0x004!
[ 938.810000] ath: Failed to stop TX DMA, queues=0x004!
[ 939.260000] ath: Failed to stop TX DMA, queues=0x004!
[ 939.480000] ath: Failed to stop TX DMA, queues=0x004!
[ 939.710000] ath: Failed to stop TX DMA, queues=0x004!
[ 939.940000] ath: Failed to stop TX DMA, queues=0x004!
When running iperf over wifi, " Failed to stop TX DMA"'s are more frequent
comment:84 Changed 6 years ago by nbd
please show me the output of 'cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset'
also, what kind of router are you using?
comment:85 Changed 6 years ago by nicke_rejv@…
Hi,
The router is: TP-Link TL-WR1043ND HW 1.7.
The output is as per below, this is just after reproducing the error with iperf
[ 2664.730000] ath: Failed to stop TX DMA, queues=0x004! [ 2664.960000] ath: Failed to stop TX DMA, queues=0x004! [ 2665.180000] ath: Failed to stop TX DMA, queues=0x004!
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
Do let me know if you need more information.
comment:86 Changed 6 years ago by niky
with htmode set to HT20 the WIFI is very stable. I have been running iperf for hours without any disconnects and no errors in the kernel ring buffer.
The only issue being that the network throughout is lower
Hope it helps.
comment:87 Changed 6 years ago by Pilot6 <hanipouspilot@…>
That is not true. With HT20 same problems.
comment:88 Changed 6 years ago by niky <nicke_rev@…>
damn you are right, indeed HT20 has the same problem.
[15178.930000] ath: Failed to stop TX DMA, queues=0x004!
comment:89 Changed 6 years ago by TheDracle
Device hardware: TPLink-WR1043ND VER 1.8
In DMESG:
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020
root@wrt:/# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 71
PLL RX Hang: 0
root@iBAHN-wrt:~# cat /etc/banner
_
| |.-----.-----.-----.| | | |.----.| |_
| - _ | -| | | _ _| |_ |_|| | || || W I R E L E S S F R E E D O M
ATTITUDE ADJUSTMENT (bleeding edge, unknown) ----------
comment:90 Changed 6 years ago by garlew
Can I do anything to help debug the problem? It makes my router effectively unusable.
comment:91 Changed 6 years ago by fkrlsn@…
I have the same problem on wr740n v4.2.
comment:92 Changed 6 years ago by anonymous
[220797.300000] ath: Failed to stop TX DMA, queues=0x001!
[220797.320000] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[220797.330000] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
kernel output from wr740n v2.4
comment:93 Changed 6 years ago by exi+openwrt@…
I am also experiencing this bug on my TL-WR1043ND kernel
Linux OpenWrt 2.6.32.27 #5 Wed Dec 21 01:59:33 CET 2011 mips GNU/Linux
with Backfire (10.03.1, r29592)
It happens to me when i transfer large amounts of data from one wireless device to another.
I get disassociated from the wifi.
kernel output repeated all the time:
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
I would like to offer my help to fix the problem too.
Is the disassociation already fixed in newer versions?
comment:94 Changed 6 years ago by garlew
Trunk r31182 (Linux 3.2.13) + ath9k changes from latest kernel trunk up to 1.04.2012 (https://github.com/torvalds/linux/commits/master/drivers/net/wireless/ath/ath9k) gives me much more stable wifi in G-mode. I haven't seen DMA failed message in logs though there are still disassociations sometimes. N-mode is very unstable :).
comment:95 Changed 6 years ago by niky <nicke_rev@…>
With the trunk from 21 apr 2012, ATTITUDE ADJUSTMENT (Bleeding Edge, r31387) on TP-LINK TL-WR1043ND.
After a few days of running the error appeared again. But most of the time it has been stable - well until now.
[345428.520000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345428.760000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345428.770000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345429.010000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345429.020000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345429.260000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345429.270000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345429.510000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020
[345429.520000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345429.760000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345429.770000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345430.010000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020
[345430.020000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345430.260000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345430.270000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345430.510000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345430.520000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[345430.770000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
[345430.780000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
comment:96 Changed 6 years ago by florian.sesser@…
Also am having the
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
problem with Wifi dying on a 1043ND v1 on ATTITUDE ADJUSTMENT (Bleeding Edge, r31639).
Looks like a regression to me, this already worked a lot better in the past. I had r296xx (sorry, don't know anymore) running for quite some time. It had wifi resets every now and then, but was usable.
comment:97 Changed 6 years ago by garlew
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:98 Changed 6 years ago by christophe@…
I'm getting the same error messages on a TL-WR1043ND v1 (Wifi: AR9100/AR2133) running r32020.
comment:99 follow-up: ↓ 100 Changed 6 years ago by anonymous
Also on a TL-WR941ND v2 (Wifi: AR9100/AR2133) running r32020.
comment:100 in reply to: ↑ 99 Changed 6 years ago by christophe@…
ath: phy0: Failed to stop TX DMA, queues=0x005! ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:101 Changed 6 years ago by Newgel
TL-WR1043ND v1.6 running trunk r32020. Lots and lots of errors. Seems worse than 10.03.1 Final!!!
[ 3214.690000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 3215.160000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 3727.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 3732.680000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 3996.530000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4297.250000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4352.190000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4442.670000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4614.570000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 5733.880000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 7435.850000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10464.710000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10469.480000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10475.370000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10478.700000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10487.360000] ath: phy0: Failed to stop TX DMA, queues=0x104! [10541.690000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10722.290000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10725.940000] ath: phy0: Failed to stop TX DMA, queues=0x104! [10771.380000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10874.550000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10875.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10920.140000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10928.590000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10939.100000] ath: phy0: Failed to stop TX DMA, queues=0x004! [10959.240000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11000.780000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11014.880000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11019.030000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11022.790000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11040.250000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11046.350000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11056.450000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11059.060000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11063.110000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11071.670000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11077.460000] ath: phy0: Failed to stop TX DMA, queues=0x104! [11175.310000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11175.980000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11204.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11214.300000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11234.320000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11236.020000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11239.460000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11250.090000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11251.470000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11256.240000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11263.680000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11274.700000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11282.560000] ath: phy0: Failed to stop TX DMA, queues=0x104! [11332.290000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11351.090000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11389.130000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11400.560000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11401.030000] ath: phy0: Failed to stop TX DMA, queues=0x104! [11408.560000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11408.710000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11413.680000] ath: phy0: Failed to stop TX DMA, queues=0x100! [11441.500000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11453.740000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11454.520000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11471.470000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11511.560000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11547.980000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11551.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11557.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11561.590000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11562.050000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11563.040000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11606.090000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11609.540000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11609.910000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11610.170000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11610.650000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11614.310000] ath: phy0: Failed to stop TX DMA, queues=0x104! [11618.260000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11619.040000] ath: phy0: Failed to stop TX DMA, queues=0x004! [11620.120000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13764.010000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13791.940000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13797.520000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13827.780000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13829.270000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13830.760000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13832.360000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13834.470000] ath: phy0: Failed to stop TX DMA, queues=0x004! [13919.970000] ath: phy0: Failed to stop TX DMA, queues=0x004! [14025.410000] ath: phy0: Failed to stop TX DMA, queues=0x004! [14242.710000] ath: phy0: Failed to stop TX DMA, queues=0x004! [15676.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! [16375.770000] ath: phy0: Failed to stop TX DMA, queues=0x004! [16435.340000] ath: phy0: Failed to stop TX DMA, queues=0x004! [16830.570000] ath: phy0: Failed to stop TX DMA, queues=0x004! [16923.000000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17041.320000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17044.160000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17044.830000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17054.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17065.210000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17066.390000] ath: phy0: Failed to stop TX DMA, queues=0x004! [17080.590000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:102 Changed 6 years ago by BIG666
Hi all. I have make a brief search in google for "atheros AR9103 drivers linux" and find something interesting
www.wireless-driver.com/engenius-emp9602-windows-2000-xp-vista-win7-linux-drivers/
If to be more exactly - engeniuscanada.com/ESW/Files/LSDK-WLAN-pb42fus7.0.0.360.tar
This archive contains a lot of kernel code for Atheros chipsets which is significantly differs from code in OpenWRT.
Can it be useful to solve our problem? Maybe it's possible to replace our buggy driver by this one and see if something changed?
comment:103 follow-up: ↓ 104 Changed 6 years ago by nbd
with that driver, you'd be trading one set of bugs for a completely different set of bugs, and a massive loss of features, as well as a license violation.
please try latest trunk, i added some fixes that could help.
comment:104 in reply to: ↑ 103 Changed 6 years ago by anonymous
Replying to nbd:
with that driver, you'd be trading one set of bugs for a completely different set of bugs, and a massive loss of features, as well as a license violation.
please try latest trunk, i added some fixes that could help.
I'm talking just about to try the alternative driver and see if there are the same issue or not. If there are no such bugs then you can analyse their code and figure out what you doing wrong in code of your driver in and fix the bug.
comment:105 Changed 6 years ago by nbd
testing that driver won't be helpful at all. it doesn't work with any recent kernel, it won't print the same message, and even if it wouldn't have the same kind of connectivity issues, that still wouldn't tell us anything that could be used to fix this.
comment:106 Changed 6 years ago by anonymous
I agree with nbd. That driver has connectivity issues, but after disconnects, hardware is reset very fastly, so a user does not see it. Maybe it makes sense to try to get some knowledge from that driver and try to implement it into mac80211.
comment:107 Changed 6 years ago by Pilot6 <hanipouspilot@…>
That was me.
comment:108 Changed 6 years ago by christophe@…
I updated a couple of devices to r32046, I'll let you know about the results.
comment:109 Changed 6 years ago by BIG666
May be this information will be usefull for you: when i switch to 802.11b the issue does not appears and wifi very stable.
comment:110 Changed 6 years ago by wellingtonuemura@…
Got the same error, too bad, it was fine all this days.
This report it's just a formality, I'll try the new trunk version:
Hardware: TP-Link WR1043ND v1.8
Software: Trunk r31858
Jun 4 06:37:58 Aguia kern.err kernel: [80102.440000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Jun 4 06:37:58 Aguia kern.err kernel: [80102.450000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up .... and the list goes on....
Just one note, at this time 6:37 AM, no one was using the wireless, looks like it start by it self and it's followed by a hardware reset. My windows machine detected a network connection lost at the exact same time.
comment:111 Changed 6 years ago by wellingtonuemura@…
Question[[BR]]
What it's the best way to install the trunk version, full install or upgrade?
Here I install the original TP-LINK firmware, then I install the trunk squashfs factory version.
Thanks.
PS: Last r32033 up and running.
comment:112 Changed 6 years ago by anonymous
[10020.370000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 [10020.380000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [10020.400000] ath: phy0: Failed to stop TX DMA, queues=0x004! [15056.350000] ath: phy0: Failed to stop TX DMA, queues=0x004! [49883.360000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [49883.370000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Same problems with r32046. :(
comment:113 Changed 6 years ago by gelson.santos@…
Wellington, you can upgrade by flashing the openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin
comment:114 Changed 6 years ago by wellingtonuemura@…
Hardware: TP-Link WR1043ND v1.8
Software: Trunk r32130
Jun 10 07:51:41 Aguia kern.err kernel: [37271.710000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Jun 10 07:51:41 Aguia kern.err kernel: [37271.720000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
With the trunk version r32033 I was getting the error occasionally, now on this r32130 version I get nothing but this error message flooding the system log followed by a hardware reset.
Nobody were using the wireless at the time, it happens by it self.
comment:115 Changed 6 years ago by nbd
please try r32159
comment:116 Changed 6 years ago by Daniel Holm <d.holmen@…>
Running r32174 and n-mode seem to be much more stable. I got one of these error messages, and the router has been up for like 6 hours since last flash.
comment:117 Changed 6 years ago by Christophe <christophe@…>
nbd, thank you very much for working on this bug. I'm really appreciating it. Your last commit did unfortunately not fix the bug. On of my wr941 running r32163 hung for about 6 minutes but then recovered. Another one hasn't recovered yet.
[...] ath: phy0: Failed to stop TX DMA, queues=0x004! ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [...]
comment:118 Changed 6 years ago by wellingtonuemura@…
Hardware: TP-Link WR1043ND v1.8
Software: Trunk r32343
So far, no errors at all.
comment:119 follow-up: ↓ 120 Changed 6 years ago by gelson.santos@…
Where can I find binaries for these versions? Just tried upgrading to the latest snapshoot and it is r32130.
comment:120 in reply to: ↑ 119 Changed 6 years ago by anonymous
Replying to gelson.santos@…:
Where can I find binaries for these versions? Just tried upgrading to the latest snapshoot and it is r32130.
You have to download the last source revision and compile your own. Read the main Wiki page for more information.
http://wiki.openwrt.org/doc/howto/buildroot.exigence
comment:121 Changed 6 years ago by wellingtonuemura@…
Hardware: TP-Link WR1043ND v1.8
Software: Trunk r32343
[142572.940000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [142573.190000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
I'm not a programmer but, there is something else we can do about it to help out instead of "try the last version"?
Maybe a core dump? A more verbose output, a specific log? A debug driver?
Thanks.
comment:122 follow-up: ↓ 123 Changed 6 years ago by nbd
I don't know any better way to track this down. This "Could not stop RX" stuff is a symptom of a big variety of different issues (most of which I have fixed already and have found through code review).
An important piece of information that you should always add when posting such debug messages is whether this log entry happens during a time where there are actual connectivity issues, or if it's just logspam with no apparent side effects.
comment:123 in reply to: ↑ 122 Changed 6 years ago by wellingtonuemura@…
Replying to nbd:
An important piece of information that you should always add when posting such debug messages is whether this log entry happens during a time where there are actual connectivity issues, or if it's just logspam with no apparent side effects.
I my case this always happens when there is no connection, this happens by it self. Before with previous revisions the router would do a reboot, now it's just a message with no side effects, I can connect my laptop or any computer in the house just fine, after the fact. I've never been able to catch or test the connection right when it happens.
comment:124 Changed 6 years ago by Christophe <christophe@…>
I just noticed the wifi hanging and found about fifty of these messages in the logs of two TL-WR941 running r32421. Link quality was affected until the next reboot. Traffic was low: <5p/s.
ath: phy0: Failed to stop TX DMA, queues=0x004! ath: phy0: Failed to stop TX DMA, queues=0x004! ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:125 Changed 6 years ago by anonymous
Im currently running r32130 downloaded from snapshoots repository and it has the same issue. I see those TX DMA and also RX DMA error messages all the time (few minutes apart from each other) but it DOES NOT seems to affect wi-fi quality. However, from time to time (usually once each 24hs-48hs) wi-fi starts to lag and bandwidth goes down and down, untill I reboot router. I tried pinging router when it happens and packets are being lost between my laptop and router. They are located just 1 meter apart from each other. I also tried switching to cable connection while wi-fi was bad, and access through cable is just fine, so this is not a router/cpu/memory issue. It really affects only wi-fi. On one ocasion I was running inSSIDer , a free wireless network monitoring tool and the DB graphic clearly showed heavy oscillation on signal quality while wi-fi was unstable. It goes from -30db (normal signal) to -90db (really bad), then goes up again about two seconds later, then stays this way for a few seconds and goes down again, untill I reboot router.
I will try to capture a screenshoot next time I see this beavior.
comment:126 Changed 6 years ago by SuperSpy
I seem to be having the same issue as described by anon above, logging into the router and running 'wifi' to recycle the radio seems to immediately fix it for an indeterminate amount of time. It also seems to depend on the quality of the signal as I moved to a different external antenna with less blockage and it is greatly reduced, but still happens occasionally.
If there's any information I can provide I'll be glad to post it.
comment:127 follow-up: ↓ 128 Changed 6 years ago by wellingtonuemura@…
I think we should consider the issue of some one from outside trying to break in and causing all this troubles. Got an unpleasant experience to see my wireless been used by some one from outside my network, and I use passwords with a complexity like this ptLeVYN2J(dW$#/Rk*4hia+0o01, the router password it's even worse than that so, It can't be an easy guess.
Not to say that the wireless password it's stored in clear text inside /etc/config/wireless
As I have been reporting, this "Could not stop..." stuff happens when no one is using the wireless, this could be some sort of an exploit that this cracker do to crash the driver or something like it and use the opportunity to get in.
I can't prove this right now, but I'll soon.
Using Trunk r32449.
comment:128 in reply to: ↑ 127 ; follow-ups: ↓ 130 ↓ 133 Changed 6 years ago by exi+openwrt@…
Replying to wellingtonuemura@…:
I think we should consider the issue of some one from outside trying to break in and causing all this troubles. Got an unpleasant experience to see my wireless been used by some one from outside my network, and I use passwords with a complexity like this ptLeVYN2J(dW$#/Rk*4hia+0o01, the router password it's even worse than that so, It can't be an easy guess.
Not to say that the wireless password it's stored in clear text inside /etc/config/wireless
As I have been reporting, this "Could not stop..." stuff happens when no one is using the wireless, this could be some sort of an exploit that this cracker do to crash the driver or something like it and use the opportunity to get in.
I can't prove this right now, but I'll soon.
Using Trunk r32449.
I think this possibility is _very_ unlikely as I am experiencing this bug in a very remote area where a am absolutely certain that nobody else is trying to break into my wireless.
This is most certainly just a driver bug.
comment:129 Changed 6 years ago by Christophe <christophe@…>
Hi, here's some statistics made by collectd on the OLSR LQ (success rate of packets sent) and NLQ (success rate of packets received) of three routers running r32421.
The bug seems to affect outgoing packets only and sometimes it's recovering by itself. (wr941nd-b at 13:00)
I restarted wr941nd-a at 13:50 but the problem quckly reappeared at 14:10.
There hasn't been any significant traffic in that period, but seems to be more likely to occur when there's other people using that channel.
chr-wr1043-b040: 194.196.20.66
chr-wr941nd-b: 104.196.20.3
chr-wr941nd-a: 104.196.20.2
I didn't find any error messages directly related to these events but some of the routers have this message in their error log:
ath: phy0: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d02
comment:130 in reply to: ↑ 128 Changed 6 years ago by wellingtonuemura@…
Replying to exi+openwrt@…:
I think this possibility is _very_ unlikely as I am experiencing this bug in a very remote area where a am absolutely certain that nobody else is trying to break into my wireless.
This is most certainly just a driver bug.
Same here, you don't need a populated area to get some one trying to break in, all you need it's one person with a can of pringles searching for a target inside a car or near by. At the time this happens here, there are not a living soul around me.
It's too soon to just discard it and assume it's a driver bug.
Did the developers ever tried to overload/flood the driver with requests? All a "kid" need this days is a distro like Backtrack Linux.
Until we can find evidence that prove otherwise, I think this matter should be take in to consideration.
comment:131 Changed 6 years ago by fkrlsn@…
I see someone brought his tin foil hat ;-)
comment:132 Changed 6 years ago by camden.lindsay+openwrt@…
wndr3700v2 seeing the same issue..
Wireless issues/packet loss and the following in logs
kernel: [90750.250000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000082c0
kernel: [90750.260000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:133 in reply to: ↑ 128 Changed 6 years ago by gelson.santos@…
Replying to exi+openwrt@…:
Replying to wellingtonuemura@…:
I think we should consider the issue of some one from outside trying to break in and causing all this troubles. Got an unpleasant experience to see my wireless been
I think this possibility is _very_ unlikely as I am experiencing this bug in a very remote area where a am absolutely certain that nobody else is trying to break into my wireless.
This is most certainly just a driver bug.
I would say both are right. This is certainly a driver bug, so its more likely to hit that bug when there are more wireless activity. A hacker trying hundreds of passwords in a short time is likely to hit it earlier than a router with normal traffic. However, this does not means a router MUST be attacked and/or password MUST be cracked to experience this bug. I see it happens at random while I´m connected to it. I´m a heavy user; during the day I always have 3 notebooks and 2 smartphones connected; I use voice over IP (SIP) a lot, I keep a VPN connection open during business time, my son plays Diablo 3 online and I´m a big fan of NASA Channel.
I live in a big city with dozens of neighbour wifi networks around, although all the ones using my channel (11) are under -80dbs, so it shouldn´t be an issue.
Running r32130 from trunk on a WR-1043nd v1.6
comment:134 follow-up: ↓ 135 Changed 6 years ago by gelson.santos@…
Had to reboot again this afternoon. Now I noticed this on system log. It starts just after reboot.
Jun 21 14:12:23 Vortex user.info sysinit: setting up led USB Jun 21 14:12:23 Vortex user.info sysinit: setting up led WLAN Jun 21 14:12:24 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: authenticated Jun 21 14:12:24 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: authenticated Jun 21 14:12:24 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: associated (aid 2) Jun 21 14:12:25 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: pairwise key handshake completed (WPA) Jun 21 14:12:25 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 17:12:26 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPDISCOVER(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Jun 21 17:12:26 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPOFFER(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Jun 21 17:12:26 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPREQUEST(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Jun 21 17:12:26 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPACK(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 brcmp-gelsantos Jun 21 17:19:45 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPINFORM(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Jun 21 17:19:45 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPACK(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Asimov Jun 21 14:22:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 14:22:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 14:32:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 14:32:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 14:42:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 14:42:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 17:47:49 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPINFORM(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Jun 21 17:47:49 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPACK(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Asimov Jun 21 17:51:24 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPINFORM(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Jun 21 17:51:24 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPACK(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Asimov Jun 21 14:51:24 Vortex kern.err kernel: [ 2301.330000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 21 14:51:27 Vortex kern.err kernel: [ 2304.270000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 21 14:52:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 14:52:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 15:02:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 15:02:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 15:12:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 15:12:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 15:22:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 15:22:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 18:26:06 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPINFORM(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Jun 21 18:26:06 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPACK(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Asimov Jun 21 15:28:31 Vortex kern.info kernel: [ 4528.530000] usb 1-1.4: new high-speed USB device number 3 using ehci-platform Jun 21 15:28:31 Vortex kern.info kernel: [ 4528.660000] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Jun 21 15:32:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 15:32:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 15:42:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 15:42:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jun 21 18:45:45 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPINFORM(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Jun 21 18:45:45 Vortex daemon.info dnsmasq-dhcp[1722]: DHCPACK(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 brcmp-gelsantos Jun 21 15:52:10 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jun 21 15:52:10 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA)
Why so many DHCP traffic? My lease time is set to 24hs, but I see host Asimov getting a DHCPInform every few minutes, for example at 17:27:49 UTC and again at 17:51:24 UTC. At exactly the same time, 14:51:24 GMT-3 there was the TX error.
There is also lots of WPA handshakes, is that normal?
comment:135 in reply to: ↑ 134 Changed 6 years ago by wellingtonuemura@…
Replying to gelson.santos@…
Why so many DHCP traffic? My lease time is set to 24hs, but I see host Asimov getting a DHCPInform every few minutes, for example at 17:27:49 UTC and again at 17:51:24 UTC. At exactly the same time, 14:51:24 GMT-3 there was the TX error.
There is also lots of WPA handshakes, is that normal?
No it's not normal, and YES some one is messing up with your connection, trying to break in, specially if you see this:
Jun 21 13:05:29 Aguia daemon.warn dnsmasq-dhcp[27136]: not giving name Dragon.lan to the DHCP lease of 192.168.1.41 because the name exists in /etc/hosts with address 192.168.1.32 Jun 21 13:05:29 Aguia daemon.warn dnsmasq-dhcp[27136]: not giving name Dragon to the DHCP lease of 192.168.1.41 because the name exists in /etc/hosts with address 192.168.1.32 Jun 21 13:33:22 Aguia daemon.info dnsmasq-dhcp[27136]: DHCPDISCOVER(br-lan) 192.168.48.189 xx:xx:xx:xx:xx Jun 21 13:33:22 Aguia daemon.info dnsmasq-dhcp[27136]: DHCPOFFER(br-lan) 192.168.1.41 xx:xx:xx:xx:xx Jun 21 13:33:22 Aguia daemon.info dnsmasq-dhcp[27136]: DHCPREQUEST(br-lan) 192.168.1.41 xx:xx:xx:xx:xx Jun 21 13:33:22 Aguia daemon.info dnsmasq-dhcp[27136]: DHCPACK(br-lan) 192.168.1.41 xx:xx:xx:xx:xx Dragon Jun 21 13:43:10 Aguia authpriv.info dropbear[7205]: Child connection from 192.168.1.41:53801 Jun 21 13:43:17 Aguia authpriv.warn dropbear[7205]: Bad password attempt for 'root' from 192.168.1.41:53801 Jun 21 13:43:21 Aguia authpriv.warn dropbear[7205]: Bad password attempt for 'root' from 192.168.1.41:53801 Jun 21 13:43:28 Aguia authpriv.info dropbear[7205]: Exit before auth (user 'root', 2 fails): Exited normally
Or this:
Jun 21 14:04:36 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:04:36 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:04:36 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:04:41 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:04:41 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:04:47 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:04:47 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:04:52 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:04:52 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:04:58 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:04:58 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:04 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:04 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:10 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:10 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:16 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:16 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:21 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:21 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:27 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:27 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:32 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:32 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:37 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:37 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:43 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:43 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:48 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:48 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:05:54 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:05:54 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:06:59 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:06:59 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:07:05 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:07:05 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:07:12 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: authenticated Jun 21 14:07:12 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1) Jun 21 14:07:12 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:22 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:22 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:27 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:27 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:33 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:33 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:38 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:38 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:45 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:45 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) Jun 21 14:07:51 Aguia daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN) ...
This is a WPA/WPA2 attack with aireplay/aircrack to get a WPA handshake, than use a list to discover your wireless password. I've discovered this crap today, looks like the WPA2 has a problem named "hole196" too.
Oh, and guess what come after all that?
"Could not stop..." error or "Failed to stop..."
comment:136 follow-up: ↓ 153 Changed 6 years ago by biglion@…
This issue still present on r32482 from trunk on a WR-1043nd.
comment:137 Changed 6 years ago by anonymous
Tl-WR1043ND (r32482):
... Jun 24 05:31:43 iHome kern.err kernel: [30703.070000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up Jun 24 05:31:43 iHome kern.err kernel: [30703.090000] ath: phy0: Failed to stop TX DMA, queues=0x004! ... Jun 24 05:31:45 iHome kern.err kernel: [30705.480000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 Jun 24 05:31:45 iHome kern.err kernel: [30705.490000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up ... $ uname -a Linux iHome 3.3.8 #1 Sat Jun 23 03:07:55 PDT 2012 mips GNU/Linux
comment:138 Changed 6 years ago by openwrt@…
I'm also having wifi connectivity issues after this entry:
[30476.050000] ath: phy0: TX while HW is in FULL_SLEEP mode
Power management is off however:
root@OpenWrt:/# iwconfig wlan0
---
Power Management:off
---
Only after a reboot will wifi work again.
Running a very recent trunk in STA (client) mode. I wish I had more debug infos.
comment:139 Changed 6 years ago by nbd
I made a debug patch that will help narrow down the source of the hang related to the "ath: phy0: TX while HW is in FULL_SLEEP mode" message: http://nbd.name/900-ath9k_debug.patch
If you're getting this message, please do the following to help me figure this out:
- Copy the patch to package/mac80211/patches
- Make sure that CONFIG_KERNEL_KALLSYMS is enabled in your config
- Recompile and install the updated binaries.
- Post the changed error message along with the stack trace when it happens.
comment:140 Changed 6 years ago by gelson.santos@…
How about "Failed to stop TX DMA, queues=0x004! " errors? Any patch for helping debug these ones?
comment:141 Changed 6 years ago by openwrt@…
Here is one I caught:
(new one) [85770.890000] ath: phy0: RX failed to go idle in 10 ms RXSM=0x902400
[88307.520000] ath: phy0: TX while HW is in FULL_SLEEP mode, fc=c000
[88307.530000] Call Trace:
[88307.530000] [<80281b64>] dump_stack+0x8/0x34
[88307.530000] [<81564850>] ath9k_ps_restore+0xde4/0xe6c [ath9k]
I used to get the TX DMA messages as well, so thats why I thought this was related.
nbd if you get a Paypal option I can donate some bucks
b.t.w.: it's a WR1043ND
comment:142 Changed 6 years ago by openwrt@…
ugh
[85770.890000] ath: phy0: RX failed to go idle in 10 ms RXSM=0x902400 [88307.520000] ath: phy0: TX while HW is in FULL_SLEEP mode, fc=c000 [88307.530000] Call Trace: [88307.530000] [<80281b64>] dump_stack+0x8/0x34 [88307.530000] [<81564850>] ath9k_ps_restore+0xde4/0xe6c [ath9k]
comment:143 follow-up: ↓ 144 Changed 6 years ago by nbd
the "TX while HW is in FULL_SLEEP mode" issue is being worked on, no need to post updated debug logs anymore.
as for the DMA issues, please try r32510 to see if it changes anything
comment:144 in reply to: ↑ 143 Changed 6 years ago by igor@…
Replying to nbd:
as for the DMA issues, please try r32510 to see if it changes anything
I have one host with WNDR3700 and problematic wifi-client, that causes immediate "Failed to stop TX DMA, queues=0x004!" right after connection. r32511 doesn't help in this case:
Jun 27 19:16:02 OpenWrt daemon.info hostapd: wlan0: STA a0:6c:ec:c9:1a:e6 IEEE 802.11: authenticated Jun 27 19:16:02 OpenWrt daemon.info hostapd: wlan0: STA a0:6c:ec:c9:1a:e6 IEEE 802.11: associated (aid 2) Jun 27 19:16:02 OpenWrt daemon.info hostapd: wlan0: STA a0:6c:ec:c9:1a:e6 WPA: pairwise key handshake completed (RSN) Jun 27 19:16:02 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPDISCOVER(br-lan) a0:6c:ec:c9:1a:e6 Jun 27 19:16:02 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPOFFER(br-lan) 172.31.254.195 a0:6c:ec:c9:1a:e6 Jun 27 19:16:02 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPREQUEST(br-lan) 172.31.254.195 a0:6c:ec:c9:1a:e6 Jun 27 19:16:02 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPACK(br-lan) 172.31.254.195 a0:6c:ec:c9:1a:e6 Playbook Jun 27 19:17:35 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:36 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:36 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:37 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:37 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:37 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:37 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:40 OpenWrt daemon.info hostapd: wlan0: STA a0:6c:ec:c9:1a:e6 IEEE 802.11: authenticated Jun 27 19:17:40 OpenWrt daemon.info hostapd: wlan0: STA a0:6c:ec:c9:1a:e6 IEEE 802.11: associated (aid 2) Jun 27 19:17:40 OpenWrt daemon.info hostapd: wlan0: STA a0:6c:ec:c9:1a:e6 WPA: pairwise key handshake completed (RSN) Jun 27 19:17:40 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPDISCOVER(br-lan) a0:6c:ec:c9:1a:e6 Jun 27 19:17:40 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPOFFER(br-lan) 172.31.254.195 a0:6c:ec:c9:1a:e6 Jun 27 19:17:40 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPREQUEST(br-lan) 172.31.254.195 a0:6c:ec:c9:1a:e6 Jun 27 19:17:40 OpenWrt daemon.info dnsmasq-dhcp[1608]: DHCPACK(br-lan) 172.31.254.195 a0:6c:ec:c9:1a:e6 Playbook Jun 27 19:17:41 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004! Jun 27 19:17:41 OpenWrt user.err kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
Such problem makes wifi fully unusable on this device and causes drops/reconnects for others.
comment:145 Changed 6 years ago by Christophe <christophe@…>
I upgraded to r32511 about one hour ago. Unfortunately there's already "Failed to stop TX DMA" error messages on two WR941ND nodes and I had to reboot another one because it wasn't reachable any more.
comment:146 follow-up: ↓ 147 Changed 6 years ago by david weil <tenuki@…>
did someone try this (from: http://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg07870.html ):
disabling power save would be a nice idea, to see if this issue disappears. i got the same issue after a long stress test with some other card, sujith gave me the idea to see if disabling PS helps sudo iwconfig wlanX power off sudo iw dev wlanX set power_save off also please ensure that you run with your power adapter :) i noticed PS gets enabled via wext when we plug out the power adapter
i still have to test it..
comment:147 in reply to: ↑ 146 Changed 6 years ago by david weil <tenuki@…>
Replying to david weil <tenuki@…>:
did someone try this (from: http://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg07870.html ):
sudo iwconfig wlanX power off sudo iw dev wlanX set power_save off
i still have to test it..
and.. I can't :
wlan0 Link encap:Ethernet HWaddr B0:48:7A:99:AB:4E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1052357 errors:0 dropped:0 overruns:0 frame:0
TX packets:1163053 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:136678426 (130.3 MiB) TX bytes:703724157 (671.1 MiB)
~
root@chin:~# iwconfig wlan0 power off
Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Invalid argument.
root@chin:~# iw dev
phy#0
Interface wlan0
ifindex 7
type AP
root@chin:~# iw dev wlan0 set power_save off
command failed: Operation not supported (-122)
is it already disabled in some way?
comment:148 follow-up: ↓ 149 Changed 6 years ago by wellingtonuemura@…
I don't have this problems but the power save modem doesn't can't be turned off indeed, TP-Link WR1043ND v1.8 e Trunk 32517.
root@Aguia:~# iw dev wlan0 info Interface wlan0 ifindex 30 type AP wiphy 3
root@Aguia:~# iw dev wlan0 get power_save Power save: on
root@Aguia:~# iw dev wlan0 set power_save off command failed: Operation not supported (-122)
comment:149 in reply to: ↑ 148 Changed 6 years ago by david weil <tenuki@…>
Replying to wellingtonuemura@…:
I don't have this problems but the power save modem doesn't can't be turned off indeed, TP-Link WR1043ND v1.8 e Trunk 32517.
Oh, well, perhaps I should update mine, because I have the same mode/version of tp-link, with:
# OpenWrt version: Attitude Adjustment (r32074) # Tue Jun 5 21:27:33 2012
and I'm getting:
[150951.280000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [150951.290000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
root@Aguia:~# iw dev wlan0 info Interface wlan0 ifindex 30 type AP wiphy 3
Here:
root@chin:~# iw dev wlan0 info Interface wlan0 ifindex 7 type AP wiphy 3
is that normal, right?
root@Aguia:~# iw dev wlan0 get power_save Power save: on
Same here.
In the next days, I'll build a new version.. thanks!
comment:150 Changed 6 years ago by wellingtonuemura@…
I don't know if this would solve your problem but it solved mine. What I've done was to reduce the transmit power to 11dBm, why?
Some one was messing up with my wireless and the S.O.B. broke in 2 times, while he was trying to break in I also got all this DMA and other strange errors. 11dBm to me it's more than enough to provide internet to my wife's laptop.
Try and see if it helps, tweak the transmit power to fit your needs.
comment:151 Changed 6 years ago by nbd
Forget trying to play with powersave in AP mode, it makes no sense whatsoever. Powersave is a client mode feature.
comment:152 Changed 6 years ago by david weil <tenuki@…>
Thanks wellingtonuemura@ and nbd@ !
comment:153 in reply to: ↑ 136 Changed 6 years ago by biglion@…
Replying to biglion@…:
This issue still present on r32482 from trunk on a WR-1043nd.
I have encountered same DMA problem on WR1043ND r32482. After dozens attempts to figure why it happens, I changed WiFi channel from Auto to 6. And this problem just gone. About five days Wifi is pretty stable. Here is part of wireless config:
option type 'mac80211' list ht_capab 'SHORT-GI-40' list ht_capab 'DSSS_CCK-40' option txpower '20' option hwmode '11ng' option htmode 'HT40+' option country 'RU' option channel '6' option distance '20' option noscan '1' option bursting '1' option ff '1' option xr '1' option ar '1'
I hope it helps someone.
comment:154 follow-up: ↓ 155 Changed 6 years ago by Sabidabi
nbd, Please take a look at this post https://forum.openwrt.org/viewtopic.php?id=37540. It might add some valuable information for understanding the issue.
comment:155 in reply to: ↑ 154 Changed 6 years ago by gelson.santos@…
Replying to Sabidabi:
nbd, Please take a look at this post https://forum.openwrt.org/viewtopic.php?id=37540. It might add some valuable information for understanding the issue.
This is interesting. I have already posted above asking why there is so many DHCP requestes at the time I experience a "Failed to stop TX" error but it seems nobody has a clue. Would it be possible that DHCP process is interfering somehow with WIFI?
I still cant understand why my stations get a new IP address after just a fez dozen minutes even with a lease time set for 24hs.
comment:156 Changed 6 years ago by Steven Roberts <strobert-openwrt@…>
Seeing nasty performance/stability drop-off for wifi. on my WZR-HP-G300NH 10.03.01-rc5 worked the best so far. wireless speed is okay, and stays stable for the laptops and media consoles. my DroidX has hte wifi drop off weird at times, but otherwise is semi-stable.
with both 10.03.01 final and the 2012-07-03 snapshot after a while performance gets really bad. signal strength stays strong, but ping times go fromt he usual ~1ms to sometimes 300-1000ms. router load stays fine. I tried the snapshot upon recommendation on the IRC channel. any data I can collect to help solve this issue?
comment:157 follow-ups: ↓ 158 ↓ 159 Changed 6 years ago by nbd
Thanks for the info. I'm working on identifying differences between those two drivers.
Please try if this patch helps: http://nbd.name/900-test.patch
Simply copy it to package/mac80211/patches on latest trunk
comment:158 in reply to: ↑ 157 Changed 6 years ago by Steven Roberts <strobert-openwrt@…>
Replying to nbd:
Thanks for the info. I'm working on identifying differences between those two drivers.
Please try if this patch helps: http://nbd.name/900-test.patch
Simply copy it to package/mac80211/patches on latest trunk
I (finally) got my build env up and installed from a local build. first up is without the patch to make sure I still see the problem. In theory I should still see it since I built off of the trunk. r32628. although that is a little newer than the 2012-07-03 snapshot I tested with before.
comment:159 in reply to: ↑ 157 Changed 6 years ago by Steven Roberts <strobert-openwrt@…>
Replying to nbd:
Thanks for the info. I'm working on identifying differences between those two drivers.
Please try if this patch helps: http://nbd.name/900-test.patch
Simply copy it to package/mac80211/patches on latest trunk
gave the patch a whirl. and no change. after a while the wifi connection gets unstable.
note sure if it is a useful note, but when I ran the 2012-07-03 snapshot from openwrt.org I could run the 'wifi' command and it would re-init the wireless and get it working again. with both of the trunk builds I have done (with and without the patch) running 'wifi' seems to take out wireless and I have had to reboot the router to get things back to normal.
LAN connections stay stable the entrie time FYI.
I'm probably going to go back to the rc5 codebase for the moment. Please let me know if there are other patches to try out or logs to work on grabbing to help debug.
comment:160 Changed 6 years ago by nbd
please try latest trunk (without the patch)
comment:161 Changed 6 years ago by somerst@…
This problem is still there, r32656 on TP-LINK TL-WA901ND v2 and Buffalo WZR-HP-AG300H hardware. Daily reboot helps us through the day, but it's an annoying problem.
Thanks for all the efforts in solving this!
comment:162 Changed 6 years ago by anonymous
Why not to contact developers from Atheros?
comment:163 Changed 6 years ago by jow
There already is contact to Atheros.
comment:164 Changed 6 years ago by igor@…
To nbd: tested r32685 - nothing changes with WNDR3700, problematic client and "ath: phy0: Failed to stop TX DMA, queues=0x004!".
comment:165 Changed 6 years ago by wellingtonuemura@…
Just to give a feedback about the issue, my case, still using r32517 with TL-WR1043ND v1.8 and it's rock stable running 24/7. The only thing that I found on my system log is internal stuff related.
comment:166 Changed 6 years ago by anonymous
hi, it seems a signa/link quality related.
my test setup is a three mesh nodes,
all in one room, two is alix pc engines with EMP9605H (ar9220) with antennas
like on soho routers and one is my laptop with dbii f52n-pro ar9220 based too.
Use compat-wireless-3.5-rc5-1-snpc on all nodes.
All three nodes work fine, but then i remove antenas from one of the node (it
contiue work only with pigtails) signal levels with this node is low but enough
to work, it continue to work but i have errors in dmesg on all three nodes:
ath: phy0: Failed to stop TX DMA, queues=0x001!
Links is become unstable, packet loss regardless to which node taffic is goes,
to node without antennas or betwen nodes with antennas.
I tryin change wireless cards with no results, but all what i try is ar9220 based,
just different manufactures. Also i try add ubiquiti nanostation M2 with openwrt
on it in this setup, and get same results on it too - dma erros and unstable links
with packetloss.
Then i connect antennas back, all strat working fine again withous erorors.
I think it seems low signal and/or low quality links is triggering with bug.
comment:167 Changed 6 years ago by nbd
- Resolution set to fixed
- Status changed from accepted to closed
rx dma related logspam fixed in r32709
comment:168 Changed 6 years ago by Steven Roberts <strobert-openwrt@…>
managed to make time last weekend to try out latest trunk. I'm running:
ATTITUDE ADJUSTMENT (Bleeding Edge, r32719)
It is better so far than the previous trunk revs I ran. I'm still seeing issues with latency. ping times will occasionally spike.
Do you want to handle the ongoing issues in this ticket or a new one?
I did get this once from the kernel:
ath: phy0: Failed to stop TX DMA, queues=0x004
I did get this compile warning in my build:
/usr/local/src/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2012-07-06/drivers/net/wireless/ath/ath9k/mac.c: In function 'ath9k_hw_stopdmarecv':
/usr/local/src/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2012-07-06/drivers/net/wireless/ath/ath9k/mac.c:721:51: warning: 'mac_status' may be used uninitialized in this function [-Wuninitialized]
looks like you addressed that in r32734. So I'll work on a new build.
I did notice your comment on fixing 'wifi' locking things up in r32689. it does look to be working for me again. I have a script that uses 'wifi' to bounce the connection if it detects bad ping times to the laptops.
comment:169 follow-up: ↓ 188 Changed 6 years ago by nbd
Ongoing issues should be handled in different tickets. One issue per ticket please :)
As for the 'Failed to stop TX DMA' stuff, I think that's already covered in multiple tickets, you can find the relevant ones using the search function.
comment:170 Changed 6 years ago by Steven Roberts <strobert-openwrt@…>
I had found 10923 before but it got resolved as a dupe of 9693 which got resolved as a dupe of this ticket. So I though 10923's issue should get handled here. I found 11862 so I'll follow-up in that one.
comment:171 Changed 6 years ago by Roy van Lamoen <rvlamoen@…>
- Resolution fixed deleted
- Status changed from closed to reopened
Error Could not stop RX still occurs/reoccurs on r32741 on TP-Link WR1043ND:
Jul 17 07:54:20 OpenWrt kern.err kernel: [70578.360000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 Jul 17 07:54:20 OpenWrt kern.err kernel: [70578.370000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Only active client (TP-Link WLAN printer server) was authenticated again approx. 1m30s after the error, so I suspect loss of connectivity has occurred. Connectivity was restored however.
comment:172 Changed 6 years ago by Fraterius
Hello Roy, have small question whether it was only log info and disconnection issue or there was also loose of perfomance?
comment:173 Changed 6 years ago by Roy van Lamoen <rvlamoen@…>
Can't tell if there was a drop in performance, I wasn't at home when the log messages were thrown.
However, in earlier revisions I didn't notice a performance drop, only a disconnect.
comment:174 Changed 6 years ago by gelson.santos@…
Just upgraded to r32739 from trunk and I can see several TX DMA errors at boot time:
Dec 31 22:00:38 Vortex kern.info kernel: [ 36.400000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 Dec 31 22:00:38 Vortex kern.info kernel: [ 36.440000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 Dec 31 22:00:38 Vortex kern.info kernel: [ 36.460000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 Dec 31 22:00:38 Vortex kern.info kernel: [ 36.460000] hub 1-0:1.0: USB hub found Dec 31 22:00:38 Vortex kern.info kernel: [ 36.470000] hub 1-0:1.0: 1 port detected Dec 31 22:00:38 Vortex kern.info kernel: [ 36.490000] nf_conntrack version 0.5.0 (456 buckets, 1824 max) Dec 31 22:00:38 Vortex kern.info kernel: [ 36.700000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Dec 31 22:00:38 Vortex kern.info kernel: [ 36.880000] usb 1-1: new high-speed USB device number 2 using ehci-platform Dec 31 22:00:38 Vortex kern.info kernel: [ 37.030000] hub 1-1:1.0: USB hub found Dec 31 22:00:38 Vortex kern.info kernel: [ 37.030000] hub 1-1:1.0: 4 ports detected Dec 31 22:00:40 Vortex daemon.notice netifd: Interface 'lan' is now up Dec 31 22:00:40 Vortex daemon.notice netifd: Interface 'loopback' is now up Dec 31 22:00:40 Vortex daemon.notice netifd: Interface 'wan' is now up Dec 31 22:00:40 Vortex kern.info kernel: [ 40.250000] eth0: link up (1000Mbps/Full duplex) Dec 31 22:00:40 Vortex kern.info kernel: [ 40.250000] device eth0.1 entered promiscuous mode Dec 31 22:00:40 Vortex kern.info kernel: [ 40.260000] device eth0 entered promiscuous mode Dec 31 22:00:40 Vortex kern.info kernel: [ 40.270000] br-lan: port 1(eth0.1) entered forwarding state Dec 31 22:00:40 Vortex kern.info kernel: [ 40.270000] br-lan: port 1(eth0.1) entered forwarding state Dec 31 22:00:41 Vortex user.notice ifup: Enabling Router Solicitations on lan (br-lan) Dec 31 22:00:41 Vortex kern.info kernel: [ 41.340000] cfg80211: Calling CRDA for country: BR Dec 31 22:00:41 Vortex kern.info kernel: [ 41.340000] cfg80211: Regulatory domain changed to country: BR Dec 31 22:00:41 Vortex kern.info kernel: [ 41.350000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 31 22:00:41 Vortex kern.info kernel: [ 41.360000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) Dec 31 22:00:41 Vortex kern.info kernel: [ 41.360000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Dec 31 22:00:41 Vortex kern.info kernel: [ 41.370000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 31 22:00:41 Vortex kern.info kernel: [ 41.380000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 31 22:00:41 Vortex kern.info kernel: [ 41.390000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) Dec 31 22:00:42 Vortex kern.info kernel: [ 42.270000] br-lan: port 1(eth0.1) entered forwarding state Dec 31 22:00:42 Vortex user.notice ifup: Enabling Router Solicitations on wan (eth0.2) Dec 31 22:00:43 Vortex kern.info kernel: [ 43.770000] device wlan0 entered promiscuous mode Dec 31 22:00:44 Vortex user.notice ifup: Enabling Router Solicitations on loopback (lo) Dec 31 22:00:44 Vortex kern.info kernel: [ 44.440000] br-lan: port 2(wlan0) entered forwarding state Dec 31 22:00:44 Vortex kern.info kernel: [ 44.450000] br-lan: port 2(wlan0) entered forwarding state Dec 31 22:00:46 Vortex kern.info kernel: [ 46.450000] br-lan: port 2(wlan0) entered forwarding state Dec 31 22:00:47 Vortex user.info sysinit: Loading defaults Dec 31 22:00:47 Vortex user.info sysinit: Loading synflood protection Dec 31 22:00:48 Vortex user.info sysinit: Adding custom chains Dec 31 22:00:48 Vortex user.info sysinit: Loading zones Dec 31 22:00:49 Vortex user.info sysinit: Loading forwardings Dec 31 22:00:49 Vortex user.info sysinit: Loading rules Dec 31 22:00:49 Vortex user.info sysinit: Loading redirects Dec 31 22:00:49 Vortex user.info sysinit: Loading includes Dec 31 22:00:49 Vortex user.info sysinit: Loading interfaces Dec 31 22:00:49 Vortex user.info firewall: adding lan (br-lan) to zone lan Dec 31 22:00:50 Vortex user.info firewall: adding wan (eth0.2) to zone wan Dec 31 22:00:51 Vortex authpriv.info dropbear[1263]: Running in background Dec 31 22:00:51 Vortex user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses! Dec 31 22:00:51 Vortex user.notice dnsmasq: Allowing 127.0.0.0/8 responses Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: started, version 2.59 cachesize 150 Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: compile time options: IPv6 GNU-getopt no-DBus no-i18n DHCP TFTP no-conntrack no-IDN Dec 31 22:00:55 Vortex daemon.info dnsmasq-dhcp[1307]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 1d Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: using local addresses only for domain metaverse.com.br Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: reading /tmp/resolv.conf.auto Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: using nameserver 8.8.8.8#53 Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: using nameserver 8.8.4.4#53 Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: using local addresses only for domain metaverse.com.br Dec 31 22:00:55 Vortex daemon.info dnsmasq[1307]: read /etc/hosts - 1 addresses Dec 31 22:00:55 Vortex daemon.info dnsmasq-dhcp[1307]: read /etc/ethers - 0 addresses Dec 31 22:00:55 Vortex user.info sysinit: setting up led USB Dec 31 22:00:55 Vortex user.info sysinit: setting up led WLAN Dec 31 22:00:55 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Dec 31 22:00:55 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Joaninha Dec 31 22:00:55 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.49 e8:9a:8f:c8:a4:ab Dec 31 22:00:55 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.49 e8:9a:8f:c8:a4:ab Asimov-eth0 Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPDISCOVER(br-lan) 169.254.70.29 00:22:fb:8e:be:e0 Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPOFFER(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPDISCOVER(br-lan) 04:46:65:7a:5d:6b Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPOFFER(br-lan) 192.168.1.45 04:46:65:7a:5d:6b Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.45 04:46:65:7a:5d:6b Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.45 04:46:65:7a:5d:6b GalaxyS2 Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Dec 31 22:00:56 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 brcmp-gelsantos Dec 31 22:00:59 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPINFORM(br-lan) 192.168.1.49 e8:9a:8f:c8:a4:ab Dec 31 22:00:59 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.49 e8:9a:8f:c8:a4:ab Asimov-eth0 Jul 17 17:57:14 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 IEEE 802.11: authenticated Jul 17 17:57:14 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 IEEE 802.11: associated (aid 1) Jul 17 17:57:14 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 WPA: pairwise key handshake completed (WPA) Jul 17 17:57:14 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 WPA: group key handshake completed (WPA) Jul 17 17:57:14 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Jul 17 17:57:14 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Joaninha Jul 17 17:57:19 Vortex kern.err kernel: [ 79.410000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 17:57:19 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPINFORM(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Jul 17 17:57:19 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Joaninha Jul 17 17:57:28 Vortex authpriv.info dropbear[1353]: Child connection from 192.168.1.49:58986 Jul 17 17:57:38 Vortex authpriv.notice dropbear[1353]: Password auth succeeded for 'root' from 192.168.1.49:58986 Jul 17 17:57:42 Vortex kern.info kernel: [ 102.730000] usb 1-1.4: new high-speed USB device number 3 using ehci-platform Jul 17 17:57:44 Vortex kern.err kernel: [ 104.150000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 17:57:45 Vortex kern.err kernel: [ 105.440000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 17:57:45 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: authenticated Jul 17 17:57:45 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 IEEE 802.11: associated (aid 2) Jul 17 17:57:45 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: pairwise key handshake completed (WPA) Jul 17 17:57:45 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jul 17 17:57:49 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 Jul 17 17:57:49 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.41 00:22:fb:8e:be:e0 brcmp-gelsantos Jul 17 18:00:06 Vortex kern.notice kernel: [ 246.930000] SCSI subsystem initialized Jul 17 18:00:07 Vortex kern.info kernel: [ 247.000000] Initializing USB Mass Storage driver... Jul 17 18:00:07 Vortex kern.info kernel: [ 247.010000] usbcore: registered new interface driver usb-storage Jul 17 18:00:07 Vortex kern.info kernel: [ 247.020000] USB Mass Storage support registered. Jul 17 18:02:49 Vortex user.notice miniupnpd: adding firewall rules for eth0.2 to zone wan Jul 17 18:02:49 Vortex user.info syslog: SNet version started Jul 17 18:02:49 Vortex daemon.notice miniupnpd[2045]: HTTP listening on port 5000 Jul 17 18:02:49 Vortex daemon.notice miniupnpd[2045]: Listening for NAT-PMP traffic on port 5351 Jul 17 18:03:08 Vortex kern.err kernel: [ 428.790000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:03:16 Vortex kern.info kernel: [ 436.590000] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Jul 17 18:03:16 Vortex kern.info kernel: [ 436.600000] usbcore: registered new interface driver usblp Jul 17 18:03:23 Vortex lpr.err p9100d[2116]: socket: Address family not supported by protocol Jul 17 18:04:36 Vortex kern.info kernel: [ 516.450000] usb 1-1.4: USB disconnect, device number 3 Jul 17 18:04:36 Vortex kern.info kernel: [ 516.460000] usblp0: removed Jul 17 18:04:42 Vortex kern.info kernel: [ 522.320000] usb 1-1.4: new high-speed USB device number 4 using ehci-platform Jul 17 18:04:42 Vortex kern.info kernel: [ 522.450000] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Jul 17 18:04:57 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPINFORM(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Jul 17 18:04:57 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Joaninha Jul 17 18:05:27 Vortex kern.err kernel: [ 567.900000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:05:29 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc IEEE 802.11: authenticated Jul 17 18:05:29 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc IEEE 802.11: associated (aid 3) Jul 17 18:05:29 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: pairwise key handshake completed (WPA) Jul 17 18:05:29 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jul 17 18:05:29 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Jul 17 18:05:29 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Asimov Jul 17 18:05:29 Vortex kern.err kernel: [ 569.800000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:05:32 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPINFORM(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Jul 17 18:05:32 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.42 e0:ca:94:65:3f:dc Asimov Jul 17 18:05:36 Vortex kern.err kernel: [ 576.410000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:05:37 Vortex kern.err kernel: [ 577.380000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:06:01 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 IEEE 802.11: authenticated Jul 17 18:06:01 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 IEEE 802.11: associated (aid 1) Jul 17 18:06:01 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 WPA: pairwise key handshake completed (WPA) Jul 17 18:06:01 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 WPA: group key handshake completed (WPA) Jul 17 18:06:01 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Jul 17 18:06:01 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Joaninha Jul 17 18:06:04 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPINFORM(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Jul 17 18:06:04 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.43 00:21:6a:5f:f8:58 Joaninha Jul 17 18:06:10 Vortex kern.err kernel: [ 610.210000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:07:00 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 WPA: group key handshake completed (WPA) Jul 17 18:07:00 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jul 17 18:07:00 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jul 17 18:07:16 Vortex kern.err kernel: [ 676.770000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:11:25 Vortex kern.err kernel: [ 925.450000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:13:06 Vortex kern.err kernel: [ 1026.910000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:13:08 Vortex kern.err kernel: [ 1028.610000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:13:11 Vortex kern.err kernel: [ 1031.020000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:13:11 Vortex kern.err kernel: [ 1031.790000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:14:49 Vortex kern.err kernel: [ 1129.600000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:17:00 Vortex daemon.info hostapd: wlan0: STA e0:ca:94:65:3f:dc WPA: group key handshake completed (WPA) Jul 17 18:17:00 Vortex daemon.info hostapd: wlan0: STA 00:21:6a:5f:f8:58 WPA: group key handshake completed (WPA) Jul 17 18:17:00 Vortex daemon.info hostapd: wlan0: STA 00:22:fb:8e:be:e0 WPA: group key handshake completed (WPA) Jul 17 18:17:13 Vortex daemon.info hostapd: wlan0: STA e8:5b:5b:58:fd:83 IEEE 802.11: authenticated Jul 17 18:17:13 Vortex daemon.info hostapd: wlan0: STA e8:5b:5b:58:fd:83 IEEE 802.11: associated (aid 4) Jul 17 18:17:13 Vortex daemon.info hostapd: wlan0: STA e8:5b:5b:58:fd:83 WPA: pairwise key handshake completed (WPA) Jul 17 18:17:13 Vortex daemon.info hostapd: wlan0: STA e8:5b:5b:58:fd:83 WPA: group key handshake completed (WPA) Jul 17 18:17:14 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPDISCOVER(br-lan) e8:5b:5b:58:fd:83 Jul 17 18:17:14 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPOFFER(br-lan) 192.168.1.48 e8:5b:5b:58:fd:83 Jul 17 18:17:14 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPREQUEST(br-lan) 192.168.1.48 e8:5b:5b:58:fd:83 Jul 17 18:17:14 Vortex daemon.info dnsmasq-dhcp[1307]: DHCPACK(br-lan) 192.168.1.48 e8:5b:5b:58:fd:83 Cimema3D Jul 17 18:17:21 Vortex kern.err kernel: [ 1281.770000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:17:56 Vortex kern.err kernel: [ 1316.560000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:17:56 Vortex kern.err kernel: [ 1316.710000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:17:57 Vortex kern.err kernel: [ 1317.790000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:18:01 Vortex kern.err kernel: [ 1321.740000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 17 18:18:03 Vortex kern.err kernel: [ 1323.020000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Will report back if I still experience performance drops, however the messages above (that should be fixed) right after first boot are disapointing.
comment:175 Changed 6 years ago by Sabidabi
My configuration is:
Router Model: TP-Link TL-WR1043ND v1.8
Firmware Version: Attitude Adjustment r32739/LuCI Trunk (trunk+svn8885)
Kernel Version: 3.3.8
After almost two days of working OK, I got some huge bursts of:
[ 488.550000] ath: phy0: Failed to stop TX DMA, queues=0x100! [ 489.020000] ath: phy0: Failed to stop TX DMA, queues=0x100! [ 489.500000] ath: phy0: Failed to stop TX DMA, queues=0x100! [ 489.970000] ath: phy0: Failed to stop TX DMA, queues=0x100! [ 490.450000] ath: phy0: Failed to stop TX DMA, queues=0x100! [ 490.920000] ath: phy0: Failed to stop TX DMA, queues=0x100! [ 492.330000] ath: phy0: Failed to stop TX DMA, queues=0x100!
When it happens the Wi-Fi goes down, and after a while the entire router crashes.
My WiFi configuration is as follows:
comment:176 Changed 6 years ago by Sabidabi
I just had a relatively short burst of these messages with no crash, so the burst of messages did not overrun the entire log space, thus I could notice that I had one of these messages:
Jul 19 08:36:49 OpenWrt kern.err kernel: [10172.470000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 Jul 19 08:36:49 OpenWrt kern.err kernel: [10172.480000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Less than a minute before getting the burst of these:
Jul 19 08:37:17 OpenWrt kern.err kernel: [10200.290000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:18 OpenWrt kern.err kernel: [10201.230000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:19 OpenWrt kern.err kernel: [10202.170000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:21 OpenWrt kern.err kernel: [10204.030000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:22 OpenWrt kern.err kernel: [10204.970000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:23 OpenWrt kern.err kernel: [10205.910000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:27 OpenWrt kern.err kernel: [10210.550000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:31 OpenWrt kern.err kernel: [10214.270000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:32 OpenWrt kern.err kernel: [10215.210000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:33 OpenWrt kern.err kernel: [10216.140000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:35 OpenWrt kern.err kernel: [10218.010000] ath: phy0: Failed to stop TX DMA, queues=0x100! Jul 19 08:37:36 OpenWrt kern.err kernel: [10218.950000] ath: phy0: Failed to stop TX DMA, queues=0x100!
comment:177 Changed 6 years ago by Sabidabi
I guess the priority of this ticket should be raised, as it may crash my router several times a day. In some cases it will reset and come up, and in several others it will just leave the router down with just the 'power' led on.
When it is not crashing I can see that it is no coincidence, and the burst of (that often results in the crash):
Jul 24 10:37:23 OpenWrt kern.err kernel: [230148.900000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:23 OpenWrt kern.err kernel: [230149.150000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:24 OpenWrt kern.err kernel: [230149.390000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:24 OpenWrt kern.err kernel: [230149.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:24 OpenWrt kern.err kernel: [230149.880000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:24 OpenWrt kern.err kernel: [230150.120000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:25 OpenWrt kern.err kernel: [230150.360000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:25 OpenWrt kern.err kernel: [230150.600000] ath: phy0: Failed to stop TX DMA, queues=0x004! Jul 24 10:37:25 OpenWrt kern.err kernel: [230150.850000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Is always preceded with:
Jul 24 10:37:23 OpenWrt kern.err kernel: [230148.870000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 Jul 24 10:37:23 OpenWrt kern.err kernel: [230148.880000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
I also get a few occasional stand-alone cases of:
Jul 25 10:22:48 OpenWrt kern.err kernel: [ 897.220000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 Jul 25 10:22:48 OpenWrt kern.err kernel: [ 897.230000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
and fewer cases of:
[ 552.790000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000042c0 [ 552.800000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
I hope this information may help.
comment:178 follow-up: ↓ 181 Changed 6 years ago by gelson.santos@…
If you read my message from July 17 you will realize I was very disapointed after upgrading to r32739 and receiving TX DMA errors right after my first boot. I later confirmed that wi-fi drops and poor performance were still happening; I even had a spontaneus router reboot for the first time. Well, I´m glad to tell you guys that I manage to fix it last Friday!!!! I´m still running r32739,but I´ve changed authentication from WPA-Personal TKIP to WPA2-Personal CCMP and also added " option noscan 1" to force 40Mhz. After changing these setting I have not experienced any log messages nor wi-fi performance issues!. Its been rock solid for 5 days, so I´m now confident enough to share it with you. See bellow my /etc/config/wireless. Hope it helps:
config wifi-device 'radio0'
option type 'mac80211'
option macaddr XXXXDELETEDXXXX' '
list ht_capab 'SHORT-GI-40'
list ht_capab 'DSSS_CCK-40'
option country 'BR'
option distance '20'
option channel '11'
option txpower '19'
option hwmode '11ng'
option htmode 'HT40-'
option noscan '1'
config wifi-iface
option device 'radio0'
option key 'XXXXDELETEDXXXX'
option mode 'ap'
option network 'lan'
option ssid 'XXXXDELETEDXXXX'
option encryption 'psk2+ccmp'
comment:179 follow-up: ↓ 180 Changed 6 years ago by wellingtonuemura@…
I'm using a stable router since the beginning of last month, my case was some one trying to break in.
config wifi-device 'radio0' option type 'mac80211' option macaddr 'xx:DELETED:xx' option hwmode '11ng' list ht_capab 'SHORT-GI-40' list ht_capab 'DSSS_CCK-40' option country 'US' option noscan '1' option diversity '1' option disabled '0' option channel 'auto' option htmode 'HT20' option txpower '9' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option ssid 'xx:DELETED:xx' option encryption 'psk2+ccmp' option macfilter 'allow' option key 'xx:DELETED:xx' list maclist 'xx:DELETED:xx' list maclist 'xx:DELETED:xx'
comment:180 in reply to: ↑ 179 Changed 6 years ago by anonymous
By the way, my hardware it's a TP-Link WR1043ND v1.8 now running Trunk r32895
Replying to wellingtonuemura@…:
config wifi-device 'radio0' option type 'mac80211' option macaddr 'xx:DELETED:xx' option hwmode '11ng' list ht_capab 'SHORT-GI-40' list ht_capab 'DSSS_CCK-40' option country 'US' option noscan '1' option diversity '1' option disabled '0' option channel 'auto' option htmode 'HT20' option txpower '9' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option ssid 'xx:DELETED:xx' option encryption 'psk2+ccmp' option macfilter 'allow' option key 'xx:DELETED:xx' list maclist 'xx:DELETED:xx' list maclist 'xx:DELETED:xx'
comment:181 in reply to: ↑ 178 Changed 6 years ago by Lukas G. <veekinz@…>
Replying to gelson.santos@…:
It may actually be connected to the encryption settings. TKIP encryption isn't supported with 300Mbit/s bandwidth and maybe it is able to produce severe driver errors when it is enabled and used nonetheless. Just something I noticed, no idea if this is actually a case.
comment:182 follow-ups: ↓ 183 ↓ 184 Changed 6 years ago by Sabidabi
It doesn't work for me.
I always used WPA2, so I only added the line:
option 'noscan' '1'
to the file /etc/config/wireless in the block of
config 'wifi-device' 'radio0'
But I still get the resets, crashes and all the flavors of 'failed to stop' logs I mentioned above.
comment:183 in reply to: ↑ 182 Changed 6 years ago by wellingtonuemura@…
Try this, add this option:
option txpower '10'
This will cut your transmit power down, IF, there is some one outside trying to mess up with your wireless this option will let then out of range.
It has been over a month that this error doesn't show up at my router log.
TP-Link WR1043ND
v1.8
Replying to Sabidabi:
But I still get the resets, crashes and all the flavors of 'failed to stop' logs I mentioned above.
comment:184 in reply to: ↑ 182 ; follow-ups: ↓ 185 ↓ 186 Changed 6 years ago by anonymous
Replying to Sabidabi:
It doesn't work for me.
I always used WPA2, so I only added the line:
option 'noscan' '1'
Looking at configuration you posted a few days back it seems you are also setting RTS/CTS and Fragmentation threshoulds. I have nothing on those fields, i.e. I use whatever defaults OpenWRT provides. My Distance Optimization is also set to 20 while you use 40.
Also, as pointed by Welligton, I use TX power 19 instead of the default 20. I lowered it a bit when I read somewhere (forum?) that setting it to maximum could cause driver issues.
comment:185 in reply to: ↑ 184 ; follow-up: ↓ 187 Changed 6 years ago by Lukas G. <veekinz@…>
Replying to anonymous:
Replying to Sabidabi:
It doesn't work for me.
I always used WPA2, so I only added the line:
option 'noscan' '1'Looking at configuration you posted a few days back it seems you are also setting RTS/CTS and Fragmentation threshoulds. I have nothing on those fields, i.e. I use whatever defaults OpenWRT provides. My Distance Optimization is also set to 20 while you use 40.
Also, as pointed by Welligton, I use TX power 19 instead of the default 20. I lowered it a bit when I read somewhere (forum?) that setting it to maximum could cause driver issues.
You should try changing the encryption mode to AES only, as well. I've been running it now for 2 days at full bandwidth without any issues. (I even pushed some large files around just to stress test it...between two systems with 300Mbit/s WLAN adapters, of course. No problems so far.)
comment:186 in reply to: ↑ 184 Changed 6 years ago by Sabidabi
Replying to anonymous:
Replying to Sabidabi:
It doesn't work for me.
I always used WPA2, so I only added the line:
option 'noscan' '1'Looking at configuration you posted a few days back it seems you are also setting RTS/CTS and Fragmentation threshoulds. I have nothing on those fields, i.e. I use whatever defaults OpenWRT provides. My Distance Optimization is also set to 20 while you use 40.
Also, as pointed by Welligton, I use TX power 19 instead of the default 20. I lowered it a bit when I read somewhere (forum?) that setting it to maximum could cause driver issues.
I have implemented the changes you mention. But I still get these:
[59988.330000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [59988.340000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [60171.470000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [60171.480000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [60560.130000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [60560.140000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [60564.320000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60564.560000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60564.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60565.510000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60565.990000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60566.930000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60567.170000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60567.410000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60568.350000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60568.820000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60569.990000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60570.940000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60572.110000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60572.360000] ath: phy0: Failed to stop TX DMA, queues=0x004! [60744.140000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [60744.150000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:187 in reply to: ↑ 185 Changed 6 years ago by Sabidabi
Replying to Lukas G. <veekinz@…>:
You should try changing the encryption mode to AES only, as well. I've been running it now for 2 days at full bandwidth without any issues. (I even pushed some large files around just to stress test it...between two systems with 300Mbit/s WLAN adapters, of course. No problems so far.)
As you can see from my configuration above. I always used "Force CCMP (AES)" Cipher.
comment:188 in reply to: ↑ 169 Changed 5 years ago by Sabidabi
Replying to nbd:
Ongoing issues should be handled in different tickets. One issue per ticket please :)
As for the 'Failed to stop TX DMA' stuff, I think that's already covered in multiple tickets, you can find the relevant ones using the search function.
Replying to Roy van Lamoen <rvlamoen@…>:
Does reopening this ticket imply that the owner would resume work on it? Or do we need to open new tickets for each flavor of 'Failed to stop', as I see that pretty much all other 'Failed to stop' are closed as duplicates of this ticket?
comment:189 Changed 5 years ago by gelson.santos@…
Ok, its now 9 days since my last reboot and my router is working just fine with r32739. I found 3 error messages on log but these are about RX DMA errors, not TX as before.
[ 7410.630000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [ 7410.640000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
As far as I see, these RX errors does not impact wi-fi performance. Also, only 3 errors in 9 days are excelent, compared to tousands of TX DMA I was getting before I changed authentication to AES and setting option noscan ´1' .
comment:190 follow-up: ↓ 191 Changed 5 years ago by Lukas G. <veekinz@…>
Any news on this matter?
For the last three weeks my router has been running just fine with the experimental workarounds from this ticket.
My log has been clean ever since but I want to know if someone of you guys got some more insight by now...
comment:191 in reply to: ↑ 190 ; follow-ups: ↓ 192 ↓ 193 Changed 5 years ago by gelson.santos@…
Replying to Lukas G. <veekinz@…>:
My log has been clean ever since but I want to know if someone of you guys got some more insight by now...
I still see a few RX errors on log but it does not impacts wi-fi performance. HOWEVER, I´m now experiencing router reboots and lockups now and then. It seems router reboots every 24hs or so, and sometimes it´s unable to recover by itself and I find it with power led on and all the other leds off. I have enabled an external syslog and I´m waiting for the next lookup to see whats going on.
comment:192 in reply to: ↑ 191 Changed 5 years ago by Lukas G. <veekinz@…>
Replying to gelson.santos@…:
Replying to Lukas G. <veekinz@…>:
My log has been clean ever since but I want to know if someone of you guys got some more insight by now...
I still see a few RX errors on log but it does not impacts wi-fi performance. HOWEVER, I´m now experiencing router reboots and lockups now and then. It seems router reboots every 24hs or so, and sometimes it´s unable to recover by itself and I find it with power led on and all the other leds off. I have enabled an external syslog and I´m waiting for the next lookup to see whats going on.
Weird. Keep us posted.
I digged some on the Linux Wireless homepage and apparently, the TX DMA bug has been fixed in the 2.6.38 version. (We're on *.32 if the package version refers to the module version of Linux Wireless) So maybe an upgrade to the latest version might finally fix this issue. The RX bug doesn't seem to be fixed yet.
http://linuxwireless.org/en/users/Drivers/ath9k/bugs
I hate to be "that guy" but I have no idea how one would upgrade that kernel module.
comment:193 in reply to: ↑ 191 ; follow-up: ↓ 195 Changed 5 years ago by Sabidabi
Replying to gelson.santos@…:
Replying to Lukas G. <veekinz@…>:
My log has been clean ever since but I want to know if someone of you guys got some more insight by now...
I still see a few RX errors on log but it does not impacts wi-fi performance. HOWEVER, I´m now experiencing router reboots and lockups now and then. It seems router reboots every 24hs or so, and sometimes it´s unable to recover by itself and I find it with power led on and all the other leds off. I have enabled an external syslog and I´m waiting for the next lookup to see whats going on.
I believe the reboots and lockups are due to the TX DMA problem. The log is being cleared after the reboot so you don't see it. The external Syslog would verify that.
I have by now upgraded to r33206, where I still see a lot of TX DMA error messages. The only improvement is that in this later release the TX DMA don't end up in a reset or lockups.
Let's hope one of the developers will see your last reply and will upgrade to 2.6.38.
comment:194 Changed 5 years ago by Lukas G. <veekinz@…>
A sad day!
After weeks of stable operation I just recieved another batch of DMA errors.
I can only make vague assumptions on why it happened now and not earlier. The most 'grave' change in my network was that I recently re-enabled my second access point. (Another TP-Link product, TL-WA801N, 300mbps, different SSID, different channel) Apart from that, nothing has changed as far as I can tell. I left everything as it is to keep testing.
And honestly, I wouldn't blame nbd if he is sick and tired of working on this issue. It seems to be pretty tedious.
Anyway, I disabled the second AP and rebooted my WR1043ND. I'll let it work for a few days until I re-enable the second AP again to see if it may be caused by that. Maybe it has something to do with radio scans done by other devices...?
comment:195 in reply to: ↑ 193 ; follow-up: ↓ 196 Changed 5 years ago by gelson.santos@…
Replying to Sabidabi:
I believe the reboots and lockups are due to the TX DMA problem. The log is being cleared after the reboot so you don't see it. The external Syslog would verify that.
I have by now upgraded to r33206, where I still see a lot of TX DMA error messages. The only improvement is that in this later release the TX DMA don't end up in a reset or lockups.
Let's hope one of the developers will see your last reply and will upgrade to 2.6.38.
I experienced a reboot today. This time router was able to recover itself, i.e. it was not necessary to cicle power off/on. Unfortunalely, there was no message on syslog server. Last message was a plain "WPA group key handshake completed" for one of my station and then a 8 minutes hole on logs and then "Interface wan is now up".
So, router crashed and rebooted without any clue.
No idea what else i could try.
comment:196 in reply to: ↑ 195 Changed 5 years ago by Sabidabi
Replying to gelson.santos@…:
I experienced a reboot today. This time router was able to recover itself, i.e. it was not necessary to cicle power off/on. Unfortunalely, there was no message on syslog server. Last message was a plain "WPA group key handshake completed" for one of my station and then a 8 minutes hole on logs and then "Interface wan is now up".
So, router crashed and rebooted without any clue.
No idea what else i could try.
The syslog server should be able to catch something eventually. Make sure you have the server that runs as a service on a strong and unloaded machine on a 1GB wired port of the router.
comment:197 Changed 5 years ago by wellingtonuemura@…
For those who needs it, I use Syslog Server, works like a charm on my Win7 machine as a standard app, you can hide it at your system tray.
All you have to do it's to set the external log server at System > Logging, set you computer IP and 514 as a port.
comment:198 Changed 5 years ago by Clayman
I don't know if this can help, but the same problem is discussed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171
There is a patch proposed on this page that possibly can solve the problem with "Failed to stop TX DMA". Of course, it can't be directly applied to OpenWRT, but maybe it can be adapted to OpenWRT somehow?
comment:199 Changed 5 years ago by wellingtonuemura@…
Here is the patch, it's sign by some one from Atheros it self.
Thank you Clayman.
From 1da85f0f630ae3a9e294e39b411d17975cbfdd4b Mon Sep 17 00:00:00 2001 From: Vasanthakumar Thiagarajan <vasanth@atheros.com> Date: Sun, 6 Feb 2011 21:48:19 -0800 Subject: [PATCH 1/2] ath9k: Fix race in starting/stopping DMA of hw data queues pcu_lock needs to be aquired before starting DMA on a particular hw queue to avoid the race while trying to stop that queue in ath_drain_all_txq(). Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com> --- drivers/net/wireless/ath/ath9k/xmit.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c index 68a1c76..07afae0 100644 --- a/drivers/net/wireless/ath/ath9k/xmit.c +++ b/drivers/net/wireless/ath/ath9k/xmit.c @@ -1396,7 +1396,10 @@ static void ath_tx_send_ampdu(struct ath_softc *sc, struct ath_atx_tid *tid, TX_STAT_INC(txctl->txq->axq_qnum, a_queued_hw); bf->bf_lastbf = bf; ath_buf_set_rate(sc, bf, fi->framelen); + + spin_lock_bh(&sc->sc_pcu_lock); ath_tx_txqaddbuf(sc, txctl->txq, &bf_head); + spin_unlock_bh(&sc->sc_pcu_lock); } static void ath_tx_send_normal(struct ath_softc *sc, struct ath_txq *txq, @@ -1416,7 +1419,10 @@ static void ath_tx_send_normal(struct ath_softc *sc, struct ath_txq *txq, bf->bf_lastbf = bf; fi = get_frame_info(bf->bf_mpdu); ath_buf_set_rate(sc, bf, fi->framelen); + + spin_lock_bh(&sc->sc_pcu_lock); ath_tx_txqaddbuf(sc, txq, bf_head); + spin_unlock_bh(&sc->sc_pcu_lock); TX_STAT_INC(txq->axq_qnum, queued); } -- 1.7.0.4
comment:200 follow-up: ↓ 201 Changed 5 years ago by gelson.santos@…
Problem is: nbd does not seems to be following this ticket anymore....
comment:201 in reply to: ↑ 200 Changed 5 years ago by Lukas G. <veekinz@…>
Replying to gelson.santos@…:
Problem is: nbd does not seems to be following this ticket anymore....
Or he just doesn't have the time to fiddle around with his stuff. Dunno.
I'd take a look at the files myself but I can't seem to find the ath9k driver files in the repository. (The ath9k package is, for some reason, only visible in a very old revision from 4 years ago.)
comment:202 Changed 5 years ago by gelson.santos@…
This note from nbd on another ticket (https://dev.openwrt.org/ticket/9693#comment:85) seems to imply they are not using ath9k kernel drivers, so I´m assuming the path is worthless. Why OpenWRT would reinvent the well is beyond me.
comment:203 Changed 5 years ago by jow
OpenWrt does not reinvent the wheel, it uses wireless-next to track linux wireless development, sources + patches are packaged in package/mac80211/ .
As for the proposed patch, the DMA issue at hand is merely a symptom of various different problems which are complex to reproduce and fix. A simple two-line patch scraped off some random bug report of a random distro is most likely not the final solution to this issue.
As for nbd not tracking this ticket - he's very well aware of whats being posted here but that does not mean that he comments on every wrong conclusion and random guesswork made here.
comment:204 Changed 5 years ago by wellingtonuemura@…
Why not ask some one at Atheros? Or invite then to join in?
I'm sure that nbd has done a great job and has great skills, but some times it's hard to deal with all this issues alone, don't you think?
comment:205 Changed 5 years ago by gelson.santos@…
BTW, my syslog server recorded another crash and this time I was able to confirm it was related to TX and RX DMA bug:
[166981.990000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[166982.000000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[166983.180000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[166984.400000] ath: phy0: Failed to stop TX DMA, queues=0x004!
.....
It goes on with TX DMA messages for about two minutes and then router reboots. So, my problem is not fixed. I still expericence these errors; the only difference is that on previous OpenWRT versions wi-fi performance was impacted until I rebooted manually. Now router reboots by itself, although sometimes it hangs and I find it with power led on and all other leds off. Running version r32739.
comment:206 Changed 5 years ago by anonymous
Happened here today using vanilia 10.03.1 (r29592) on a 1043nd, wlan0 was in monitor mode since boot. Wireless suddenly stopped working for no apparent reason and the usual message flooded the log:
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006020 ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:207 follow-up: ↓ 209 Changed 5 years ago by anonymous
Using monitor mode is the fastest way to reproduce this issue (< 10 minutes) on r29592, e.g. do airodump-ng wlan0 (no other parameters) on the affected device and start generating traffic on a nearby network.
After generating 1-2GB traffic the bug kicks in as my limited testing has shown.
Didn't have the time to play around with newer versions, someone should see if the bug can be reproduced this way on a later rev, if yes then hopefully future patches can be tested faster (no need to wait for days to learn that a patch is not working as expected)
comment:208 Changed 5 years ago by anonymous
My wndr3700v2 also have this issue. I bought that router because someone told me it's the best router for OpenWRT and I can't use it with OpenWRT. It makes me angry.
comment:209 in reply to: ↑ 207 ; follow-up: ↓ 211 Changed 5 years ago by anonymous
Replying to anonymous:
Using monitor mode is the fastest way to reproduce this issue (< 10 minutes) on r29592, e.g. do airodump-ng wlan0 (no other parameters) on the affected device and start generating traffic on a nearby network.
After generating 1-2GB traffic the bug kicks in as my limited testing has shown.
Didn't have the time to play around with newer versions, someone should see if the bug can be reproduced this way on a later rev, if yes then hopefully future patches can be tested faster (no need to wait for days to learn that a patch is not working as expected)
I was also able to reproduce the issue using this method within a few minutes. I tracked everything with the syslog server that was recommended a few posts up but it didn't show anything else beside the error messages that we know all too well. Is there any other way to provide more info than that?
comment:210 Changed 5 years ago by camden.lindsay+openwrt@…
Would console output help at all? I have a unit wired with that I could try to get and recreate...
comment:211 in reply to: ↑ 209 ; follow-ups: ↓ 212 ↓ 213 Changed 5 years ago by gelson.santos@…
Replying to anonymous:
I was also able to reproduce the issue using this method within a few minutes.
Which version are you running? The first person is running r29592 which is a really old version and I bet nbd would not waste any time debuging it.
I´m currently running r33288 from trunk and this is the best ever OpenWRT release I have tried. I´m up for 6 days 20hs now and router is rock solid. No more reboots nor hangs as in previous versions. Accordingly to changelog the reboot/hang issue was fix at r33055 (ath9k: fix hang issues on hw reset caused by interrupt storms)
For those still experiencing issues I suggest again to look at my previous comments above. In my case, AES CCMP encryption plus option noscan "1" plus a very recent build seems to have fixed all issues.
I´m still running an external syslog and will let you known if I spot something. Hopefully not :-)
comment:212 in reply to: ↑ 211 Changed 5 years ago by Lukas G. <veekinz@…>
Replying to gelson.santos@…:
Replying to anonymous:
I was also able to reproduce the issue using this method within a few minutes.
Which version are you running? The first person is running r29592 which is a really old version and I bet nbd would not waste any time debuging it.
I´m currently running r33288 from trunk and this is the best ever OpenWRT release I have tried. I´m up for 6 days 20hs now and router is rock solid. No more reboots nor hangs as in previous versions. Accordingly to changelog the reboot/hang issue was fix at r33055 (ath9k: fix hang issues on hw reset caused by interrupt storms)
For those still experiencing issues I suggest again to look at my previous comments above. In my case, AES CCMP encryption plus option noscan "1" plus a very recent build seems to have fixed all issues.
I´m still running an external syslog and will let you known if I spot something. Hopefully not :-)
(I replied as anon above, forgot to change settings)
I was running the latest stable version for almost a month perfectly stable with the maybe-workaround (;-)) settings mentioned above until the DMA errors hit me again. With the same settings I'm able to reproduce the error using airodump as mentioned above.
If I'm not doing that with airodump, the device seems to be rather stable again. In a few days (I'd like to see if people are encountering severe problems, first. I can't afford having my device bricked after my USB to TTL-cable broke...and I didn't get a new one, yet.) I'll update to Attitude Adjustment and try to reproduce the errors again.
comment:213 in reply to: ↑ 211 Changed 5 years ago by anonymous
Replying to gelson.santos@…:
Which version are you running? The first person is running r29592 which is a really old version and I bet nbd would not waste any time debuging it.
Reproduced multiple times successfully on 12.09-beta r33312 using the exact same steps.
comment:214 Changed 5 years ago by gelson.santos@…
Looks like this page does not allows comments anymore. Anything I write here is marked as spam. Lets see it this one goes through.
comment:215 Changed 5 years ago by gelson.santos@…
Poor performance again. Issue is not fixed. Cant provide more info because commentary is marked as spam.
comment:216 Changed 5 years ago by anonymous
specialfriedrice.net
comment:217 Changed 5 years ago by anonymous
i can reproduce the buggy symptom by:
step 1, set up the linux router
step 2, in the intranet, bridge the wireless (by the athero driver) and the wire lan
step 3, have a PC connected with the wire AND wireless device at the same time
Then after minutes, the symptom comes.
On the other hand, if in the step3, set up either wireless device or wire device ONLY, no such symptom.
comment:218 Changed 5 years ago by sayap
Have been running r33369 on tl-wdr4310 and tl-wr2543 for more than 11 days. Not a single trace of error in dmesg :)
comment:219 follow-up: ↓ 220 Changed 5 years ago by anonymous
comment:220 in reply to: ↑ 219 ; follow-up: ↓ 222 Changed 5 years ago by anonymous
Not fixed.
[ 4522.980000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4699.550000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4888.200000] ath: phy0: Failed to stop TX DMA, queues=0x004!
TL-WR941ND, r33562.
comment:221 Changed 5 years ago by Lukas G. <veekinz@…>
Hey guys, small update.
The error only seems to occur for me when the internal radio is used AND devices are being connected using wired LAN. With the internal radio and no wired devices, everything seems to be working like a charm.
Additionally, using a USB dongle using a ath9k chipset does not trigger this error; with or without wired LAN devices.
comment:222 in reply to: ↑ 220 ; follow-up: ↓ 223 Changed 5 years ago by anonymous
comment:223 in reply to: ↑ 222 Changed 5 years ago by Clayman
No problem here with tx power 17
Can't say if the problem is linked with TX power.
A have a lot of such errors (RX and TX) with:
- Tx power = 18dB;
- No wired devices connected;
- 2 "g" and 1 "n" wireless devices connected.
TL-WR941ND, r33562.
comment:224 Changed 5 years ago by alphasparc@…
Happened here as well.
Sep 29 01:08:59 openwrt kern.err kernel: [141855.130000] ath: phy0: Failed to stop TX DMA, queues=0x004! Sep 29 01:08:59 openwrt kern.err kernel: [141855.380000] ath: phy0: Failed to stop TX DMA, queues=0x104! Sep 29 01:08:59 openwrt kern.err kernel: [141855.620000] ath: phy0: Failed to stop TX DMA, queues=0x004! Sep 29 01:09:00 openwrt kern.err kernel: [141856.790000] ath: phy0: Failed to stop TX DMA, queues=0x100!
LuCI Trunk (trunk+svn9330) OpenWrt Attitude Adjustment r33562
comment:225 Changed 5 years ago by nbd
- Resolution set to fixed
- Status changed from reopened to closed
those log messages belong to a different ticket, #11862.
feel free to reopen if the ones from this ticket re-appear.
comment:226 Changed 5 years ago by Clayman
- Resolution fixed deleted
- Status changed from closed to reopened
As I stated before I have a lot such messages in log:
[ 2782.730000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000042c0 [ 2782.740000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[13331.120000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [13331.130000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[18769.730000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000202c0 [18769.740000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[25278.390000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000062c0 [25278.400000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
- No wired devices connected;
- 2 "g" and 1 "n" wireless devices connected;
- TL-WR941ND;
- r33562.
comment:227 Changed 5 years ago by wellingtonuemura@…
Router: TL-WR1043ND v1.8
Trunk: 33527
I was using trunk 32895 and now 33527, I still don't have any of this DMA errors.
I have the router full August log and it's clear, there is no DMA errors. Tihs doesn't mean it doesn't happen with other people, this is my configuration, irrelevant parts was DELETED.
/etc/config/wireless
config wifi-device 'radio0' option type 'mac80211' option macaddr 'DELETED' option hwmode '11ng' list ht_capab 'SHORT-GI-40' list ht_capab 'DSSS_CCK-40' option country 'US' option noscan '1' option diversity '1' option disabled '0' option channel 'auto' option txpower '9' option htmode 'HT40+' option rts '512' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option ssid 'Patocenter' option encryption 'psk2+ccmp' option macfilter 'allow' option key 'DELETED' list maclist 'DELETED' list maclist 'DELETED' list maclist 'DELETED'
comment:228 Changed 5 years ago by mikaelbrostrom <mikael_openwrt@…>
I am running 33618 on a tl-1043nd, the messages are gone and it seems stable! :)
comment:229 Changed 5 years ago by sayap
Is this problem chipset specific? I upgraded from r33369 to r33595, and my tl-wdr4310 and tl-wr2543 continue to work fine with no error for 5+ days till now.
However, 3 days ago, I unretired my wzr-hp-g300nh, upgrading it to r33595 and deploying it in the office. It seems stable so far, but dmesg shows:
[77057.730000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c1 [77057.740000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [77057.760000] ath: phy0: Failed to stop TX DMA, queues=0x004! [156027.420000] ath: phy0: Failed to stop TX DMA, queues=0x005!
No reboot needed yet.
comment:230 Changed 5 years ago by mikaelbrostrom <mikael_openwrt@…>
Well try this release: 33618 there is many ath9x fixes between your release and this one.
comment:231 Changed 5 years ago by msxcms@…
r33633 on TPLINK WDR4310
these error msgs exists yet, not fixed
comment:232 Changed 5 years ago by wellingtonuemura@…
Router: TP-Link TL-WR1043ND v1.8
Trunk: r33633
No issues so far.
comment:233 Changed 5 years ago by tperalta82@…
After 1 day:
[ 7073.120000] ath: phy0: Failed to stop TX DMA, queues=0x104!
[10210.390000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[69981.430000] ath: phy0: Failed to stop TX DMA, queues=0x005!
[74730.020000] ------------[ cut here ]------------
[74730.020000] WARNING: at /home/tperalta/OpenWRT/trunk/build_dir/linux-ar71xx_g eneric/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80d19fd0()
[74730.040000] Rate marked as an HT rate but passed status->rate_idx is not an M CS index [0-76]: 78 (0x4e)
[74730.050000] Modules linked in: sch_fq_codel sch_hfsc cls_fw sch_ingress act_m irred act_connmark em_u32 cls_u32 ifb ath79_wdt ledtrig_usbdev ledtrig_netdev nf _nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt _string xt_layer7 ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE iptable_nat nf_nat xt_r ecent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT xt_NOTRACK ipt able_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppox i pt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mang le iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k( O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base ts _fsm ts_bm ts_kmp crc_ccitt cfg80211(O) compat(O) arc4 aes_generic crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [last unloade d: ifb]
[74730.130000] Call Trace:[<80267d5c>] 0x80267d5c
[74730.140000] [<80267d5c>] 0x80267d5c
[74730.140000] [<8007198c>] 0x8007198c
[74730.140000] [<80d19fd0>] 0x80d19fd0
[74730.150000] [<80071a40>] 0x80071a40
[74730.150000] [<80d19fd0>] 0x80d19fd0
[74730.160000] [<801d8a38>] 0x801d8a38
[74730.160000] [<80c46ea0>] 0x80c46ea0
[74730.160000] [<8009c588>] 0x8009c588
[74730.170000] [<80160b84>] 0x80160b84
[74730.170000] [<80c44fc8>] 0x80c44fc8
[74730.170000] [<80076a70>] 0x80076a70
[74730.180000] [<80076f94>] 0x80076f94
[74730.180000] [<802f0000>] 0x802f0000
[74730.180000] [<802f0000>] 0x802f0000
[74730.190000] [<800771a0>] 0x800771a0
[74730.190000] [<800a8440>] 0x800a8440
[74730.190000] [<800773d4>] 0x800773d4
[74730.200000] [<8006306c>] 0x8006306c
[74730.200000] [<80063240>] 0x80063240
[74730.200000] [<802f0000>] 0x802f0000
[74730.210000] [<80095190>] 0x80095190
[74730.210000] [<80064aa8>] 0x80064aa8
[74730.220000] [<80063260>] 0x80063260
[74730.220000] [<802d18b0>] 0x802d18b0
[74730.220000] [<802d10dc>] 0x802d10dc
[74730.230000]
[74730.230000] ---[ end trace b2f6245a7ff0274e ]---
[157043.770000] ath: phy0: Failed to stop TX DMA, queues=0x005!
[158232.780000] ath: phy0: Failed to stop TX DMA, queues=0x104!
[158283.920000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[158538.020000] ath: phy0: Failed to stop TX DMA, queues=0x104!
The same on two routers, TP-LINK TL-WR1043ND v1.0's
One is still working, the other one had to be rebooted.
comment:234 Changed 5 years ago by tperalta82@…
The same as above, but Formatted
[ 7073.120000] ath: phy0: Failed to stop TX DMA, queues=0x104! [10210.390000] ath: phy0: Failed to stop TX DMA, queues=0x004! [69981.430000] ath: phy0: Failed to stop TX DMA, queues=0x005! [74730.020000] ------------[ cut here ]------------ [74730.020000] WARNING: at /home/tperalta/OpenWRT/trunk/build_dir/linux-ar71xx_generic/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80d19fd0() [74730.040000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 78 (0x4e) [74730.050000] Modules linked in: sch_fq_codel sch_hfsc cls_fw sch_ingress act_mirred act_connmark em_u32 cls_u32 ifb ath79_wdt ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_string xt_layer7 ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE iptable_nat nf_nat xt_recent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd 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 ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base ts_fsm ts_bm ts_kmp crc_ccitt cfg80211(O) compat(O) arc4 aes_generic crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [last unloaded: ifb] [74730.130000] Call Trace:[<80267d5c>] 0x80267d5c [74730.140000] [<80267d5c>] 0x80267d5c [74730.140000] [<8007198c>] 0x8007198c [74730.140000] [<80d19fd0>] 0x80d19fd0 [74730.150000] [<80071a40>] 0x80071a40 [74730.150000] [<80d19fd0>] 0x80d19fd0 [74730.160000] [<801d8a38>] 0x801d8a38 [74730.160000] [<80c46ea0>] 0x80c46ea0 [74730.160000] [<8009c588>] 0x8009c588 [74730.170000] [<80160b84>] 0x80160b84 [74730.170000] [<80c44fc8>] 0x80c44fc8 [74730.170000] [<80076a70>] 0x80076a70 [74730.180000] [<80076f94>] 0x80076f94 [74730.180000] [<802f0000>] 0x802f0000 [74730.180000] [<802f0000>] 0x802f0000 [74730.190000] [<800771a0>] 0x800771a0 [74730.190000] [<800a8440>] 0x800a8440 [74730.190000] [<800773d4>] 0x800773d4 [74730.200000] [<8006306c>] 0x8006306c [74730.200000] [<80063240>] 0x80063240 [74730.200000] [<802f0000>] 0x802f0000 [74730.210000] [<80095190>] 0x80095190 [74730.210000] [<80064aa8>] 0x80064aa8 [74730.220000] [<80063260>] 0x80063260 [74730.220000] [<802d18b0>] 0x802d18b0 [74730.220000] [<802d10dc>] 0x802d10dc [74730.230000] [74730.230000] ---[ end trace b2f6245a7ff0274e ]--- [157043.770000] ath: phy0: Failed to stop TX DMA, queues=0x005! [158232.780000] ath: phy0: Failed to stop TX DMA, queues=0x104! [158283.920000] ath: phy0: Failed to stop TX DMA, queues=0x004! [158538.020000] ath: phy0: Failed to stop TX DMA, queues=0x104!
comment:235 Changed 5 years ago by tperalta82@…
Trunk r33652
comment:236 Changed 5 years ago by Sabidabi
One interesting observation:
After the stop TX DMA messages stop and the WiFi link is restored, it always takes several good minutes before the wireless clients can actually connect to the WAN.
Hope this is helpful somehow.
comment:237 follow-up: ↓ 238 Changed 5 years ago by anonymous
Any chance to increase the priority of this issue? It makes my wr1043nd virtually useless. Does anyone know whether this issue appears on dd-wrt as well?
Regarding the comment above by Sabidabi, this is not always the case for me. My router is in client mode on a WPA-E network. Streaming any youtube video will cause the connection to get dropped at least 2 times, but often it picks it up fairly quickly.
comment:238 in reply to: ↑ 237 Changed 5 years ago by Sabidabi
Replying to anonymous:
Any chance to increase the priority of this issue? It makes my wr1043nd virtually useless.
I agree that the priority of this issue needs to be increased. It is happening to us many times a day, and people just sit and wait for the WiFi to come back. It is most annoying when it happens during a VoIP over WiFi call.
Does anyone know whether this issue appears on dd-wrt as well?
From my experience dd-wrt support for WR1043ND is practically non-existent. There are too many things that don't work there.
Regarding the comment above by Sabidabi, this is not always the case for me. My router is in client mode on a WPA-E network. Streaming any youtube video will cause the connection to get dropped at least 2 times, but often it picks it up fairly quickly.
In my case the router is used in router mode with 4 wired clients (both Windows and Linux) and several wireless clients (G, N, wide and narrow N and both Windows and Android clients). I also have a second SSID (on standby for guests) bridged only to the WAN, QoS, DDNS, and OpenVPN on that router. This is probably why we have different experience.
comment:239 follow-up: ↓ 247 Changed 5 years ago by anonymous
OpenWrt: Attitude Adjustment r33696. Router: TL-WR1043ND. Uptime: ~ 1 d 19 h.
I see today in the logs.
[153029.260000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [153029.270000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [153030.840000] device wlan0 left promiscuous mode [153030.840000] br-lan: port 2(wlan0) entered disabled state [153032.150000] device wlan0 entered promiscuous mode [153032.470000] br-lan: port 2(wlan0) entered forwarding state [153032.480000] br-lan: port 2(wlan0) entered forwarding state [153034.480000] br-lan: port 2(wlan0) entered forwarding state [153053.380000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [153053.390000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [153054.320000] device wlan0 left promiscuous mode [153054.320000] br-lan: port 2(wlan0) entered disabled state [153054.350000] ath: phy0: Failed to stop TX DMA, queues=0x001! [153055.100000] device wlan0 entered promiscuous mode [153055.420000] br-lan: port 2(wlan0) entered forwarding state [153055.430000] br-lan: port 2(wlan0) entered forwarding state [153057.430000] br-lan: port 2(wlan0) entered forwarding state [153058.010000] device wlan0 left promiscuous mode [153058.010000] br-lan: port 2(wlan0) entered disabled state [153058.740000] device wlan0 entered promiscuous mode [153059.070000] br-lan: port 2(wlan0) entered forwarding state [153059.080000] br-lan: port 2(wlan0) entered forwarding state [153061.080000] br-lan: port 2(wlan0) entered forwarding state
I use a script /etc/wi_fi_watchdog.sh to avoid problems.
#!/bin/sh
logread -f | dd bs=1 | awk '
/ath: phy0: Failed to stop/ { system("/sbin/wifi"); }
/ath: phy0: DMA failed to stop/ { system("/sbin/wifi"); }
'
comment:240 follow-up: ↓ 241 Changed 5 years ago by anonymous
The problem happens only in N-HT (40 MHz) mode. As a workaround I had to disable HT mode.
comment:241 in reply to: ↑ 240 Changed 5 years ago by anonymous
I have got the same problems running HT20, maybe setting plain 11g could help thou this would have a huge impact on performance.
comment:242 Changed 5 years ago by anonymous
because of this problem I went back to original firmware. it is too annoying. and give up to 40Mhz is not a solution. that why i bought this router, to have wireless n. i have tplink wr1043nd
comment:243 Changed 5 years ago by anonymous
I am using a Buffalo WZR-HP-AG300H, and had this problem for over a year now. 2 days ago i installed 12.09beta and it is gone for me ! Great !
root@Buffalo:~# cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option macaddr '00:24:a5:xxxxx'
list ht_capab 'SHORT-GI-40'
list ht_capab 'DSSS_CCK-40'
option country 'DE'
option channel '5'
option txpower '14'
option hwmode '11b'
option distance '15'
config wifi-iface
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'xxxxxxxx'
option key 'xxxxxxx'
option encryption 'psk+ccmp'
comment:244 follow-up: ↓ 245 Changed 5 years ago by anonymous
Problem solved for me with option country '00'
It is probably a coincidence...
1043ND v1.8
comment:245 in reply to: ↑ 244 Changed 5 years ago by anonymous
Replying to anonymous:
Problem solved for me with option country '00'
It is probably a coincidence...
1043ND v1.8
Here my wireless config, no more problems :)
config wifi-device 'radio0'
option type 'mac80211'
option channel '1'
option hwmode '11ng'
option path 'platform/ath9k'
list ht_capab 'SHORT-GI-40'
list ht_capab 'DSSS_CCK-40'
option txpower '17'
option htmode 'HT40+'
option xr '1'
option ar '1'
option ff '1'
option bursting '1'
option compression '1'
option noscan '1'
config wifi-iface
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'psk2+ccmp'
option key 'MyWirelessPassword'
option hidden '1'
comment:246 Changed 5 years ago by anonymous
I put all APs in mode 11g but DMA problems are still there.
comment:247 in reply to: ↑ 239 Changed 5 years ago by Lukas G.
Replying to anonymous:
OpenWrt: Attitude Adjustment r33696. Router: TL-WR1043ND. Uptime: ~ 1 d 19 h.
I see today in the logs.
[153029.260000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [153029.270000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [153053.380000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [153053.390000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Yeah, I'm now seeing these as well. The "queries" error doesn't appear though. I think these here appear for a different reason since they only happen once or twice in a short period of time and they don't really seem to affect the network that much.
comment:248 Changed 5 years ago by anonymous
for me it seems to be enough to switch option country in /etc/config/wireless to this:
..
option country '00'
..
After that it seems I only get:
[71052.040000] ath: phy0: Failed to stop TX DMA, queues=0x00c! [72260.160000] ath: phy0: Failed to stop TX DMA, queues=0x004!
so I'm switching to check #10486.
ps: I built this firmware with my previous post to this ticket (about 4 months ago).
comment:249 Changed 5 years ago by nbd
please try the latest version to see if it fixes the issue
comment:250 Changed 5 years ago by ravine.hu@…
Hello!
I'm having serious issues with the atheros chip too (WR941ND, currently hostapd random disconnects "due to inactivity"), but i had this DMA-errors too. Just wanna ask: these fixes are in the latest trunk (Barrier Breaker), or i have to test the Attitude Adjustment?
Just compiled r33934, gonna test it later this day.
comment:251 Changed 5 years ago by nbd
They're both in trunk and in the attitude_adjustment branch.
comment:252 Changed 5 years ago by msxcms@…
BARRIER BREAKER (Bleeding Edge, r33867)
[103790.120000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[103808.670000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[103844.110000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[103864.000000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[103864.540000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[104153.890000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[104733.180000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[105108.190000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[105108.420000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:253 Changed 5 years ago by msxcms@…
I will try the latest version.
comment:254 Changed 5 years ago by msxcms <msxcms@…>
BARRIER BREAKER (Bleeding Edge, r33938) / TP-LINK WDR4310
not fixed
Oct 26 21:05:35 Chen kern.err kernel: [ 1913.090000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:05:36 Chen kern.err kernel: [ 1913.530000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:05:37 Chen kern.err kernel: [ 1914.990000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:06:16 Chen kern.err kernel: [ 1953.640000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:06:28 Chen kern.err kernel: [ 1966.060000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:06:35 Chen kern.err kernel: [ 1972.740000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:06:39 Chen kern.err kernel: [ 1976.450000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Oct 26 21:07:36 Chen kern.err kernel: [ 2034.000000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:255 Changed 5 years ago by anonymous
Hm, same here. First i thought it's okay, because there were no problem with my old wifi-card. But when i connected with a broadcom N-capable notebookwifi, the error popped up almost immediately.
comment:256 Changed 5 years ago by rav1ne
The actual log (that anonymous was me too):
http://pastebin.com/1nUKbmsP
(used pastebin, coz trac detected my log az a spam)
What is this "disconnected due to excessive missing ACKs" ?
comment:257 Changed 5 years ago by msxcms <msxcms@…>
Same as rav1ne, I found the "disconnected due to excessive missing ACKs" too.
comment:258 Changed 5 years ago by gelson.santos@…
I´ve updated to Attitude Adjustment 12.09-beta2 four days ago and so far it is rock solid. Not a single error message nor wi-fi performance issues so far. Previously I was running r33288 and it was good enough, althoug I had the ocasional error messages on logs. My uptime record at r33288 was 17 days. Lets hope 12.09-beta2 outperforms it. Looks promising.
comment:259 Changed 5 years ago by nbd
please try the latest version of trunk or attitude_adjustment, the fix in r33989/r33990 could be relevant.
comment:260 Changed 5 years ago by tperalta82@…
Using r33991, and after 1h10m :
[ 3976.040000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[ 3976.050000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
There are about 10 to 15 clients connected to this AP.
Best Regards
comment:261 Changed 5 years ago by nbd
please show me the output of
cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
after such messages.
comment:262 Changed 5 years ago by rav1ne
r33991 with TP-Link WR941ND:
I'm still getting the "ath: phy0: Failed to stop TX DMA, queues=0x004!" message, 3-4 in every minute while downloading over wifi. I cannot test with more users ATM.
comment:263 follow-up: ↓ 264 Changed 5 years ago by tperalta82@…
nbd:
[ 3976.040000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[ 3976.050000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX
root@ConstrulinkP5-2:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
[ 9551.300000] ath: phy0: Failed to stop TX DMA, queues=0x104!
root@ConstrulinkP5-2:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 1
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
I hope this is somewhat useful to you
Best Regards
comment:264 in reply to: ↑ 263 Changed 5 years ago by Lary
using r33983 on TL-WR1043ND
I got these DMA errors every time I tried to transfer big files @300mbit.
With r33946 I started to compile my own images. I've deactivated the mesh support for the 80211 driver because i don't need it and since then, i don't got these errors again.
Can anyone confirm tis correlation?
comment:265 Changed 5 years ago by msxcms@…
TL-WDR4310
I also got these errors when I downloading some big files or playing online videos. One error displays on every 5-10ms.
It's rare when browsering web pages or other low speed actions.
comment:266 Changed 5 years ago by anonymous
Woot, trac is alive again.
TL-WR941ND , r33991
I tried Lary's solution, but i still got that DMA errors. What was that exactly?
"Kernel modules->Wireless drivers->kmod-mac80211->Enable mesh..." to disable?
comment:267 Changed 5 years ago by rav1ne
Woot, trac is alive again.
TL-WR941ND , r33991
I tried Lary's solution, but i still got that DMA errors. What was that exactly?
"Kernel modules->Wireless drivers->kmod-mac80211->Enable mesh..." to disable?
comment:268 Changed 5 years ago by tperalta82@…
nbd:
[77259.090000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[82876.440000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[83547.220000] ath: phy0: Failed to stop TX DMA, queues=0x005!
root@ConstrulinkP5-2:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 2
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 1
PLL RX Hang: 0
The interesting part, is that, at home i have another AP, but a 1.1 o4 1.4, and i'm not having any errors with r33991, exactly the same configuration
comment:269 Changed 5 years ago by gelson.santos@…
Just got a burst of errors and my laptop disconnected from wi-fi. I´m running AA 12.09-beta2, uptime 7 days.
I was hopping AA would be more stable than r33288 which I was running before upgrading, but it seems its not.
[561358.340000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561358.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561359.750000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561360.690000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561362.120000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561362.590000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561363.070000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561363.540000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561364.480000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561367.270000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561367.740000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561368.220000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561368.690000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561369.170000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561369.640000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561372.450000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561372.920000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561373.390000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561373.870000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561374.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561377.130000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561377.610000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561378.080000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561378.560000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561379.500000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561382.290000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561382.760000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561383.240000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561383.720000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561384.660000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561387.450000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561387.930000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561388.400000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561388.880000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561389.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561392.140000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561392.620000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561393.090000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561393.570000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561394.500000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561397.290000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561397.770000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561398.240000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561398.720000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561399.660000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561402.450000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561402.920000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561403.400000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561403.870000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561404.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561407.140000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561407.610000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561408.080000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561408.560000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561409.500000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561412.290000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561412.760000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561413.240000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561413.710000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561414.650000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561416.510000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561416.990000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561417.460000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561417.940000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561418.410000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561418.890000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561422.140000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561422.620000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561423.090000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561423.570000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561424.500000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561427.290000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561427.770000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561428.240000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561428.720000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561429.660000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561432.450000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561432.920000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561433.400000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561433.870000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561434.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561437.140000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561437.610000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561438.080000] ath: phy0: Failed to stop TX DMA, queues=0x100! [561438.560000] ath: phy0: Failed to stop TX DMA, queues=0x100!
root@Vortex:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
comment:270 Changed 5 years ago by tperalta82@…
nbd:
[96678.330000] ------------[ cut here ]------------ [96678.330000] WARNING: at /home/devil/Sources/OpenWRT/build_dir/linux-ar71xx_generic/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80d1a000() [96678.350000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 78 (0x4e) [96678.360000] Modules linked in: sch_fq_codel sch_hfsc cls_fw sch_ingress act_mirred act_connmark em_u32 cls_u32 ifb ath79_wdt ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_string xt_layer7 ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE iptable_nat nf_nat xt_recent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd 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 ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base ts_fsm ts_bm ts_kmp crc_ccitt cfg80211(O) compat(O) arc4 aes_generic crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [last unloaded: ifb] [96678.440000] Call Trace:[<80267e3c>] 0x80267e3c [96678.450000] [<80267e3c>] 0x80267e3c [96678.450000] [<8007198c>] 0x8007198c [96678.450000] [<80d1a000>] 0x80d1a000 [96678.460000] [<80071a40>] 0x80071a40 [96678.460000] [<80d1a000>] 0x80d1a000 [96678.460000] [<801d8ae8>] 0x801d8ae8 [96678.470000] [<801d9f0c>] 0x801d9f0c [96678.470000] [<80de6eb0>] 0x80de6eb0 [96678.480000] [<80de4fd8>] 0x80de4fd8 [96678.480000] [<80076a70>] 0x80076a70 [96678.480000] [<80076f94>] 0x80076f94 [96678.490000] [<802f0000>] 0x802f0000 [96678.490000] [<802f0000>] 0x802f0000 [96678.490000] [<800771a0>] 0x800771a0 [96678.500000] [<800a8440>] 0x800a8440 [96678.500000] [<800773d4>] 0x800773d4 [96678.500000] [<8006306c>] 0x8006306c [96678.510000] [<80063240>] 0x80063240 [96678.510000] [<802f0000>] 0x802f0000 [96678.510000] [<80095190>] 0x80095190 [96678.520000] [<80064aa8>] 0x80064aa8 [96678.520000] [<80063260>] 0x80063260 [96678.520000] [<802d18b0>] 0x802d18b0 [96678.530000] [<802f6b00>] 0x802f6b00 [96678.530000] [<802d10dc>] 0x802d10dc [96678.540000] [96678.540000] ---[ end trace b05ceae727b0d873 ]---
This sometimes happens, this also doesn't affect /sys/kernel/debug/ieee80211/phy0/ath9k/reset values.
I can't actually force this error, but it just happens.
still at r33991
Best Regards
comment:271 Changed 5 years ago by rav1ne
Happens on WR941ND also. No client was connected when it happened. This same exact error happened multiple times over this 2 days.
Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.240000] ------------[ cut here ]------------ Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.250000] WARNING: at /mnt/data/SRC/OPENWRT/BB_WR941ND_UJ/build_dir/linux-ar71xx_generic/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80c59034() Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.260000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 79 (0x4f) Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.270000] Modules linked in: ath79_wdt ledtrig_netdev nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_string xt_layer7 ipt_MASQUERADE iptable_nat nf_nat pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state n Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.330000] Call Trace:[<8026451c>] 0x8026451c Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.330000] [<8026451c>] 0x8026451c Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.340000] [<8007198c>] 0x8007198c Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.340000] [<80c59034>] 0x80c59034 Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.340000] [<80071a40>] 0x80071a40 Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.350000] [<80c59034>] 0x80c59034 Nov 2 14:09:19 OpenWrt kern.warn kernel: [169462.350000] [<801d8ae0>] 0x801d8ae0
root@OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
comment:272 Changed 5 years ago by anonymous
Please raise the bug priority because the error means, that the wifi is practically useless on routers with Atheros chipset.
comment:273 follow-up: ↓ 275 Changed 5 years ago by jow
There is no point in raising the priority of this ticket since there is only one person who can really work on it. It won't speed up anything and the issue is already actively being worked on most of the time.
Also this issue does not manifest on all atheros chipsets, it is hardware and environment specific, in some locations it is not reproducible at all.
comment:274 Changed 5 years ago by hanipouspilot@…
How can I unsubscribe from this ticket? I cannot find any options.
comment:275 in reply to: ↑ 273 Changed 5 years ago by wellingtonuemura@…
Replying to jow:
There is no point in raising the priority of this ticket since there is only one person who can really work on it. It won't speed up anything and the issue is already actively being worked on most of the time.
Also this issue does not manifest on all atheros chipsets, it is hardware and environment specific, in some locations it is not reproducible at all.
Agree, this is my case, on my WR1043ND v1.8 Trunk r34036 the issue doesn't happen at all since long time ago.
comment:276 Changed 5 years ago by anonymous
I do not agree. Running multiple WR1043ND v1.8 Trunk r34093 and my logs are full of "Failed to stop TX DMA".
comment:277 Changed 5 years ago by w01f
Running beta2 on wr1043nd, I have never before seen anything like this, maybe it will help:
[28451.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28461.970000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28588.360000] ------------[ cut here ]------------ [28588.360000] WARNING: at /build/ar71xx/generic/build_dir/linux-ar71xx_generic/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80c59fe4() [28588.380000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 78 (0x4e) [28588.390000] Modules linked in: ath79_wdt ohci_hcd ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd 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 ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base crc_ccitt cfg80211(O) compat(O) arc4 aes_generic crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [28588.440000] Call Trace:[<802838f8>] 0x802838f8 [28588.450000] [<802838f8>] 0x802838f8 [28588.450000] [<8007198c>] 0x8007198c [28588.450000] [<80c59fe4>] 0x80c59fe4 [28588.460000] [<80071a40>] 0x80071a40 [28588.460000] [<80c59fe4>] 0x80c59fe4 [28588.470000] [<801e1674>] 0x801e1674 [28588.470000] [<80ce6ea0>] 0x80ce6ea0 [28588.470000] [<80ce4fc8>] 0x80ce4fc8 [28588.480000] [<80076a90>] 0x80076a90 [28588.480000] [<80076fb8>] 0x80076fb8 [28588.480000] [<80310000>] 0x80310000 [28588.490000] [<80310000>] 0x80310000 [28588.490000] [<800771c8>] 0x800771c8 [28588.490000] [<800a8560>] 0x800a8560 [28588.500000] [<800773fc>] 0x800773fc [28588.500000] [<8006306c>] 0x8006306c [28588.500000] [<80063240>] 0x80063240 [28588.510000] [<80310000>] 0x80310000 [28588.510000] [<800952a0>] 0x800952a0 [28588.510000] [<800a8294>] 0x800a8294 [28588.520000] [<80064aa8>] 0x80064aa8 [28588.520000] [<80063260>] 0x80063260 [28588.530000] [<802f08b4>] 0x802f08b4 [28588.530000] [<802f00dc>] 0x802f00dc [28588.530000] [28588.530000] ---[ end trace 8ca9d9e5f2ea059b ]--- [28620.930000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28628.430000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28640.030000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28648.970000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28649.920000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28650.150000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28650.480000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28681.850000] ath: phy0: Failed to stop TX DMA, queues=0x004! [28686.890000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:278 Changed 5 years ago by anonymous
This has been happening to me. I just got this in my logread:
kernel: [ 423.680000] ath: phy0: Failed to stop TX DMA, queues=0x100!
Here's the "counter" output that was asked for:
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 4
PLL RX Hang: 0
I'm on r33823 and I built without mesh support.
comment:279 Changed 5 years ago by MediaManRIT
This has been happening to me. I just got this in my logread:
kernel: [ 423.680000] ath: phy0: Failed to stop TX DMA, queues=0x100!
Here's the "counter" output that was asked for:
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 4
PLL RX Hang: 0
I'm on r33823 and I built without mesh support.
comment:280 Changed 5 years ago by tperalta82@…
Currently testing r34180,
Firmware is currently built with kernel 3.6.6 (built and booted with no issues at all)
comment:281 Changed 5 years ago by tperalta82@…
Using Kernel 3.6.6, i only got this
[91797.670000] WARNING: at /home/tperalta/OpenWRT/trunk/build_dir/linux-ar71xx_g eneric/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80d1a064() [91797.680000] Rate marked as an HT rate but passed status->rate_idx is not an M CS index [0-76]: 78 (0x4e) [91797.690000] Modules linked in: ifb act_connmark act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_fq_codel sch_codel s ch_ingress ath79_wdt ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_conntrack_irc n f_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcp mss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_string xt_layer7 ipt_REDIR ECT ipt_NETMAP ipt_MASQUERADE iptable_nat nf_nat xt_recent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntr ack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppox ipt_REJECT xt_TCPMSS xt_comm ent xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpu dp x_tables ppp_async ppp_generic slhc ath9k(O) ath9k_common(O) ath9k_hw(O) ath( O) mac80211(O) usbcore usb_common nls_base ts_fsm ts_bm ts_kmp crc_ccitt cfg8021 1(O) compat(O) aes_generic crypto_algapi ledtrig_timer ledtrig_default_on leds_g pio gpio_button_hotplug(O) [last unloaded: ifb] [91797.780000] Call Trace:[<802751f4>] 0x802751f4 [91797.780000] [<802751f4>] 0x802751f4 [91797.790000] [<80071e4c>] 0x80071e4c [91797.790000] [<80d1a064>] 0x80d1a064 [91797.790000] [<80071f00>] 0x80071f00 [91797.800000] [<80d1a064>] 0x80d1a064 [91797.800000] [<801e675c>] 0x801e675c [91797.800000] [<80c46ec0>] 0x80c46ec0 [91797.810000] [<80c44fe8>] 0x80c44fe8 [91797.810000] [<800793e0>] 0x800793e0 [91797.820000] [<80078b84>] 0x80078b84 [91797.820000] [<80078db0>] 0x80078db0 [91797.820000] [<800abad0>] 0x800abad0 [91797.830000] [<80078fe4>] 0x80078fe4 [91797.830000] [<8006306c>] 0x8006306c [91797.830000] [<80063240>] 0x80063240 [91797.840000] [<800975e0>] 0x800975e0 [91797.840000] [<800ab7f8>] 0x800ab7f8 [91797.840000] [<80064aa8>] 0x80064aa8 [91797.850000] [<80063260>] 0x80063260 [91797.850000] [<802e58f0>] 0x802e58f0 [91797.850000] [<802e52a8>] 0x802e52a8 [91797.860000] [91797.860000] ---[ end trace a1c40f30330b0d44 ]--- root@ConstrulinkP5-2:~#
But no issues with disconnections or anything
comment:282 follow-up: ↓ 283 Changed 5 years ago by tperalta82@…
okay, the issues came back, but with about 30 to 40 clients connected
[ 3639.380000] ath: phy0: Failed to stop TX DMA, queues=0x005!
root@ConstrulinkP4:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
root@ConstrulinkP4:~# uname -a
Linux ConstrulinkP4 3.6.6 #1 Wed Nov 14 13:50:37 WET 2012 mips GNU/Linux
Not one complained though.
comment:283 in reply to: ↑ 282 Changed 5 years ago by Lukas G.
Replying to tperalta82@…:
okay, the issues came back, but with about 30 to 40 clients connected
[ 3639.380000] ath: phy0: Failed to stop TX DMA, queues=0x005! root@ConstrulinkP4:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset Baseband Hang: 0 Baseband Watchdog: 0 Fatal HW Error: 0 TX HW error: 0 TX Path Hang: 0 PLL RX Hang: 0 root@ConstrulinkP4:~# uname -a Linux ConstrulinkP4 3.6.6 #1 Wed Nov 14 13:50:37 WET 2012 mips GNU/LinuxNot one complained though.
So, the device didn't freeze nor did it reboot? Did the "TX DMA" message appear only once? I'd say exception handling is really good by now. ;-)
I'm currently running my device without any errors for 7 days straight (finally), somehow my "magical" configuration works again. I'll post it later today.
comment:284 Changed 5 years ago by tperalta82@…
Okay, on the other AP which is always with about 30 to 40 clients (28 at the moment lol)
Currently connected clients
root@ConstrulinkP4:~# iw dev wlan0 station dump | grep wlan0 | wc -l 28
In this time frame
root@ConstrulinkP4:~# uptime 10:27:15 up 1 day, 30 min, load average: 0.00, 0.01, 0.04
i had
root@ConstrulinkP4:~# dmesg | grep "Failed to stop TX DMA" | wc -l 177
And the output of
root@ConstrulinkP4:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
And still no one is complaining (they usually complained all day long, since this AP is on a corporate network)
So i kind of assume that kernel 3.6.6 made some kind of difference, try to change the kernel from 3.3.8 to 3.6.6 in the ar71xx target Makefile
(i can't be held responsible if you brick it, all i can say is that it's working here)
comment:285 Changed 5 years ago by MediaManRIT
I tried 3.6.6 as well, on r34193. I'm still getting the log entries. It just happened...haven't heard from anyone yet:
root@Bldg E:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 3
PLL RX Hang: 0
14 clients connected across 4 different SSIDs. Been up 14 minutes now and this has logged once:
root@Bldg E:~# logread | grep ath Nov 16 17:52:45 Bldg E kern.err kernel: [ 436.140000] ath: phy0: Failed to stop TX DMA, queues=0x100!
I haven't mentioned before, I'm using Ubiquiti UniFi APs.
comment:286 Changed 5 years ago by anonymous
I'm getting those logs as well, but the clients aren't getting disconnected (at least no one reported me anything)
comment:287 Changed 5 years ago by anonymous
I get this error on my TL-MR3040 when I go into monitor mode and try to access mon0 with something like "horst -i mon0" before establishing a connection in sta mode or starting to host a wifi network in ap mode.
If I connect in sta-mode or host in ap-mode, then use "ifconfig wlan0 down" (optionally, it works with and without that command), then go into monitor mode, then everything works fine.
Looks like the wifi device isnt correctly initialized without ap-mode?
comment:288 Changed 5 years ago by anonymous
commit cd585fb70b89fb57f8dffb03a2a72c30f81f5da6
Author: Felix Fietkau <nbd@openwrt.org>
Date: Fri Oct 26 00:31:11 2012 +0200
ath9k: fix stale pointers potentially causing access to free'd skbs
commit 8c6e30936a7893a85f6222084f0f26aceb81137a upstream.
bf->bf_next is only while buffers are chained as part of an A-MPDU
in the tx queue. When a tid queue is flushed (e.g. on tearing down
an aggregation session), frames can be enqueued again as normal
transmission, without bf_next being cleared. This can lead to the
old pointer being dereferenced again later.
This patch might fix crashes and "Failed to stop TX DMA!" messages.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(Source: https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.6.7 )
Thanks for (possibly) fixing it, nbd. Now we only need an update to 3.6.7. :)
comment:289 follow-up: ↓ 290 Changed 5 years ago by anonymous
Oh the kernel was already updated in r34227 a few hours ago, didnt saw that.
Thanks a lot!
comment:290 in reply to: ↑ 289 ; follow-up: ↓ 291 Changed 5 years ago by Lukas G.
comment:291 in reply to: ↑ 290 Changed 5 years ago by anonymous
Replying to Lukas G.:
Replying to anonymous:
Oh the kernel was already updated in r34227 a few hours ago, didnt saw that.
Thanks a lot!
That patch has also already been implemented with r33939 :)
Oh, alright.. I still have that error with r34131 and hoped the kernel would fix it.
But thanks for telling me so I don't have to go through the kernel trouble and just use standard 3.3.8 instead :)
comment:292 Changed 5 years ago by rav1ne
So far so good, no error popped up with the quick test. thx for the fix!
comment:293 Changed 5 years ago by wellingtonuemura@…
TL-WR1043ND v1.8, r34245.
So far it's stable with no errors.
comment:294 Changed 5 years ago by tperalta82@…
I'm running the same HW version, but with r34247 and i got this:
7525.470000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [ 7525.480000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:295 Changed 5 years ago by LB
comment:296 Changed 5 years ago by LB
Spoke too quickly: r34287 still has the problem:
Nov 23 12:43:39 OpenWrt kern.err kernel: [ 4752.940000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
Nov 23 12:43:39 OpenWrt kern.err kernel: [ 4752.950000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Nov 23 12:43:39 OpenWrt kern.err kernel: [ 4752.970000] ath: phy0: Failed to stop TX DMA, queues=0x004!
N
and wifi disconnected.
comment:297 Changed 5 years ago by gelson.santos@…
I always wait for at least 17 days before reporting any changes. Somewhow in my case 17 days is a " magic amount of time " where I´m forced to reboot router because it does not recovers by itself. I do get some error messages before 17 days uptime, but wifi keeps working. After 17 days uptime, wifi does not works anymore and I´m forced to reboot it.
comment:298 follow-up: ↓ 299 Changed 5 years ago by anonymous
I found some interesting information about this issue at:
https://lkml.org/lkml/2012/3/25/119
Would the patch they are discussing be applicable in our case?
comment:299 in reply to: ↑ 298 Changed 5 years ago by Lukas G.
Replying to anonymous:
I found some interesting information about this issue at:
https://lkml.org/lkml/2012/3/25/119
Would the patch they are discussing be applicable in our case?
I'd guess that a similar patch has already been applied; there are several changesets regarding aggregation and the DMA errors.
I recently got a batch of errors again (Not too many, actually) and, thankfully, the device didn't freeze; I only lost a few packets.
Isn't there any way to provide more useful data?
comment:300 Changed 5 years ago by w01f
I have tl-wr1043nd, running a client mode on a wpa-e network and then rebroadcasting on wpa2 in master mode. Running 12.09 rc1 attitude adjustment, still see tons of errors:
Nov 28 20:11:10 OpenWrt kern.err kernel: [ 5511.170000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:18 OpenWrt kern.err kernel: [ 5519.190000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:23 OpenWrt kern.err kernel: [ 5524.140000] ath: phy0: Failed to stop TX DMA, queues=0x104! Nov 28 20:11:33 OpenWrt kern.err kernel: [ 5534.320000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:34 OpenWrt kern.err kernel: [ 5535.190000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:36 OpenWrt kern.err kernel: [ 5537.270000] ath: phy0: Failed to stop TX DMA, queues=0x005! Nov 28 20:11:39 OpenWrt kern.err kernel: [ 5540.370000] ath: phy0: Failed to stop TX DMA, queues=0x005! Nov 28 20:11:41 OpenWrt kern.err kernel: [ 5542.240000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:41 OpenWrt kern.err kernel: [ 5542.480000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:50 OpenWrt kern.err kernel: [ 5550.600000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:11:55 OpenWrt kern.err kernel: [ 5556.460000] ath: phy0: Failed to stop TX DMA, queues=0x004! Nov 28 20:12:08 OpenWrt kern.err kernel: [ 5568.580000] ath: phy0: Failed to stop TX DMA, queues=0x005!
Actually, seems worse than before. I will try to install a separate wifi adapter and use that one for the master network, will report if that makes a difference.
comment:301 Changed 5 years ago by anonymous
I´m also having this problem.
dmesg is giving this:
root@OpenWrt:~# dmesg |grep phy [ 0.000000] Determined physical RAM map: [ 31.770000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 31.770000] Registered led device: ath9k-phy0 [ 31.770000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=47 [ 31.790000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 31.790000] Registered led device: ath9k-phy1 [ 31.790000] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=40 [ 321.670000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 461.400000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1551.720000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1607.210000] ath: phy0: Failed to stop TX DMA, queues=0x004!
My TP-Link wr1043nd with 12.09 rc1 isn´t reproduce this fault...
comment:302 Changed 5 years ago by LB
Still on 34287 and I can't explain why I can spend some days with relative stability and some others with the error popping up every 5 minutes and disconnecting.
Does anyone have a clue of why could triggering the issue and ways to alleviate it?
comment:303 Changed 5 years ago by anonymous
2 other solutions found in other forums related to atheros hardware which seem to have worked:
http://us.generation-nt.com/answer/ath-dma-failed-stop-10-ms-ar-cr-0x00000024-ar-diag-sw-0x02000020-dmadbg-7-0x00008040-help-206689192.html
this is has become a know issue but less harmful, please try to see if
the workaround of disabling power save helps
iw dev wlanX set power_save off
http://ubuntuforums.org/archive/index.php/t-1843638.html
Try a module parameter:
sudo modprobe -rf ath9k sudo modprobe -v ath9k nohwcrypt=1 sudo service network-manager restart # or wicd or whatever
If it works, make it permanent:
echo "options ath9k nohwcrypt=1" | sudo tee /etc/modprobe.d/ath9k.conf
Would that be applicable in our case?
If so, how to make the change in openwrt?
comment:304 Changed 5 years ago by nbd
The problems behind those links are old and have been fixed. While the symptoms look similar, the issues are different. There's no point in trying any of the workarounds mentioned in those links.
comment:305 Changed 5 years ago by LB
I had never tried the stock firmware before. When I bought my wr1043ND, I went straight to openwrt.
With the recent stability issues which had gotten worst and worst, it is not worth having openwrt or dd-wrt to use extra features that are not available in the stock firmware as the basic service is just not delivered.
So yesterday I reverted to the latest stock firmware. Since then, 2 things to note:
- the performances (bandwidth and range) are far better than what I could ever get with openwrt
- the router has been stable since yesterday afternoon.
If tp-link can get their hardware to work well with their firmware, why can't we get the same from openwrt?
I would like to go back to openwrt to use ssh and openssl. What information is required to nail the issue down?
comment:306 Changed 5 years ago by MediaManRIT
Another report. I read in ticket 9693 that this wasn't happening on r31858, but someone in this ticket says it is. I'm getting desperate for a fix, so I tried building r31858, and still got these in my log:
Dec 12 09:55:58 Cafeteria kern.err kernel: [10300.120000] ath: phy0: Failed to stop TX DMA, queues=0x004!
It does appear to be related to load somehow, with either the number of clients or the amount of bandwidth, or maybe a combination of the two. I can't reproduce this with 3 machines on my test AP (same hardware as the "production" APs) all streaming HD video from a local server, but APs in the heavy areas of the building seem to have the problem.
Is there any data I can collect that would be helpful in solving this issue? I see that there are non-OpenWRT users having problems with this from reading on other lists, but as I said, I'm getting desperate. As was said in "Wargames", "I'd piss on a spark plug if it'd help".
comment:307 Changed 5 years ago by duvi
Got one with symbol table info, maybe that helps a bit:
[51884.650000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [51884.660000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [51884.670000] ------------[ cut here ]------------ [51884.670000] WARNING: at /mnt/hda/openwrt/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2012-12-06/drivers/net/wireless/ath/ath9k/recv.c:497 ath_stoprecv+0xd4/0x10c [ath9k]() [51884.690000] Modules linked in: act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_fq_codel sch_codel sch_ingress usblp ath79_wdt ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_nat_ftp nf_conntrack_irc nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_string xt_layer7 ipt_MASQUERADE iptable_nat nf_nat xt_recent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppox ipt_REJECT xt_TCPMSS xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base ts_fsm ts_bm ts_kmp crc_ccitt cfg80211(O) compat(O) arc4 aes_generic crypto_blkcipher cryptomgr aead crypto_hash crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [51884.780000] Call Trace: [51884.780000] [<8027740c>] dump_stack+0x8/0x34 [51884.790000] [<8007228c>] warn_slowpath_common+0x78/0xa4 [51884.790000] [<800722d0>] warn_slowpath_null+0x18/0x24 [51884.800000] [<80de6270>] ath_stoprecv+0xd4/0x10c [ath9k] [51884.800000] [<80de2cc0>] ath_descdma_cleanup+0x434/0xc04 [ath9k] [51884.810000] [<80de3040>] ath_descdma_cleanup+0x7b4/0xc04 [ath9k] [51884.810000] [51884.820000] ---[ end trace 48eb8336d7489ad1 ]--- [51889.430000] ath: phy0: Failed to stop TX DMA, queues=0x004! [51911.480000] ath: phy0: Failed to stop TX DMA, queues=0x004! [51941.400000] ath: phy0: Failed to stop TX DMA, queues=0x004! [51971.440000] ath: phy0: Failed to stop TX DMA, queues=0x004!
TL-WR1043ND, trunk r34640
root@OpenWrt:~# cat /etc/config/wireless
config wifi-device 'radio0'
option disabled '0'
option type 'mac80211'
option path 'platform/ath9k'
option hwmode '11ng'
option htmode 'HT40+'
option noscan '1'
option channel '5'
option txpower '20'
list ht_capab 'SHORT-GI-40'
list ht_capab 'DSSS_CCK-40'
config wifi-iface
option device 'radio0'
option mode 'ap'
option network 'lan'
option ssid 'private'
option encryption 'psk-mixed'
option key 'private'
option wpa_group_rekey '3600'
config wifi-iface
option device 'radio0'
option mode 'ap'
option network 'pub'
option ssid 'public'
option encryption 'psk-mixed'
option key 'public'
option wpa_group_rekey '3600'
comment:308 follow-up: ↓ 311 Changed 5 years ago by anonymous
I guess this is what we should follow:
http://wireless.kernel.org/en/users/Drivers/ath9k/bugs#TX_DMA_stop_failures
and it appears not to be fixed yet as of:
http://permalink.gmane.org/gmane.linux.drivers.ath9k.devel/9940
Let's hope this:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=0d51cccc2436fa4d978efc3764552779e163d840
will finally fix it.
comment:309 Changed 5 years ago by anonymous
That's old stuff that has already been posted. It (obviously) didn't work for OpenWRT. From what I understand there are several things that can trigger TX/RX DMA stop failures.
By the way: Going strong for 7 days. I guess as soon as I let more people join the AP again, it will probably break.
comment:310 Changed 5 years ago by DaveRack
after 20 days without any problem on my new 1043ND with AA RC1, i also received the errors.
[1685077.980000] ath: phy0: Failed to stop TX DMA, queues=0x004! [1685078.770000] ath: phy0: Failed to stop TX DMA, queues=0x004! [1685079.810000] ath: phy0: Failed to stop TX DMA, queues=0x004!
only one client (54G) was connected.
comment:311 in reply to: ↑ 308 Changed 5 years ago by anonymous
Replying to anonymous:
Let's hope this:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=0d51cccc2436fa4d978efc3764552779e163d840
will finally fix it.
Thats from 2011, so its probably already in the non-testing compat-wireless anyway.
comment:312 follow-up: ↓ 317 Changed 5 years ago by anonymous
The place to contribute to the fix of this problem is probably this mailing list:
http://search.gmane.org/?query=DMA%20failed%20to%20stop&group=gmane.linux.drivers.ath9k.devel&sort=date
comment:313 in reply to: ↑ description Changed 5 years ago by anonymous
Replying to anonymous:
in my log:
{{{Jul 4 12:35:34 deepblue kern.err kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026020
Jul 4 12:35:34 deepblue kern.err kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up}}}
I also have this bug!
I am using attitude adjustment beta2 and i got:
[636164.610000] ath: phy0: Failed to stop TX DMA, queues=0x004
Is the problem fixed now?
comment:314 Changed 5 years ago by pontillo@…
In case it helps anyone troubleshoot, I am using OpenWrt Attitude Adjustment 12.09-rc1 and saw this in the kernel log:
[ 4010.570000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [ 4010.580000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [53372.540000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [53372.550000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
I checked the log after noticing that the wireless throughput had dropped to ~1 Mbps. (It has since recovered on its own.) This is on a Buffalo WZR-HP-G300NH.
comment:315 Changed 5 years ago by exi <exi+openwrt@…>
I would like to unsubscribe from this ticket too but can't find an option either.
Could someone tell me how to do it?
comment:316 Changed 5 years ago by sayap
r34927, Buffalo WZR-HP-G300NH, errors happened despite no wireless client since the router booted up:
[14005.260000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [14005.270000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [14301.500000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [14301.510000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [17344.870000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [17344.880000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [18750.630000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [18750.640000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [26170.130000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [26170.140000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:317 in reply to: ↑ 312 Changed 5 years ago by Bud
Replying to anonymous:
The place to contribute to the fix of this problem is probably this mailing list:
http://search.gmane.org/?query=DMA%20failed%20to%20stop&group=gmane.linux.drivers.ath9k.devel&sort=date
I guess that was the old place. The new one is here:
https://bugzilla.kernel.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Drivers&component=network-wireless&long_desc_type=substring&long_desc=&cf_kernel_version_type=allwordssubstr&cf_kernel_version=&emailassigned_to1=1&emailreporter1=1&emailcc1=1&emaillongdesc1=1&emailtype1=substring&email1=ath9k&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emaillongdesc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Last+Changed&field0-0-0=noop&type0-0-0=noop&value0-0-0=
And it looks like our specific bug report is this:
https://bugzilla.kernel.org/show_bug.cgi?id=27392
and I don't think it has been too active lately...
comment:318 follow-ups: ↓ 319 ↓ 321 Changed 5 years ago by anonymous
I had no issue for the last 10 days and did not understand why.
Then, my wife received her iPhone 5 after having no phone for that number of days (round trip to Apple care).
The minute I turned the iPhone on, the issue triggered.
This may explain why the router stays stable for some days and then breaks repeatedly some other days with no way to keep it stable: it depends whether the neighbors are in or not and whether my wife is in or not.
Could this be the cause of the problem: somehow, the router is changing its settings to adapt to the iPhone or its load?
comment:319 in reply to: ↑ 318 Changed 5 years ago by MediaManRIT
Replying to anonymous:
I had no issue for the last 10 days and did not understand why.
Then, my wife received her iPhone 5 after having no phone for that number of days (round trip to Apple care).
The minute I turned the iPhone on, the issue triggered.
This may explain why the router stays stable for some days and then breaks repeatedly some other days with no way to keep it stable: it depends whether the neighbors are in or not and whether my wife is in or not.
Could this be the cause of the problem: somehow, the router is changing its settings to adapt to the iPhone or its load?
I don't think it can be ONLY the presence of the iPhone that does it. On my office network I've got several iPhone 5 devices, plus the new iPad and some older iPads (in addition to several Windows laptops) and don't have problems in that environment.
comment:320 Changed 5 years ago by anonymous
comment:321 in reply to: ↑ 318 Changed 5 years ago by anonymous
Replying to anonymous:
The minute I turned the iPhone on, the issue triggered.
Was this iphone broadcasting its own SSID to offer tethering?
comment:322 Changed 5 years ago by trojanfoe@…
Just to add my $0.02 (and to subscribe to this ticket so I get automatic updates). I see the log messages on r35089 on a TP-Link WA901ND although I have not noticed an impact on performance:
[53823.210000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[53823.220000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[58732.620000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[58732.630000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[75841.720000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[75841.730000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[82699.360000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[82699.370000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[110185.550000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[110185.560000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[154343.640000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[154343.650000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
root@OpenWrt:/tmp/log# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 1
PLL RX Hang: 0
MCI Reset: 0
comment:323 follow-up: ↓ 324 Changed 5 years ago by trojanfoe@…
After updating to r35100 (TP-Link WA901ND) this is no longer happening (uptime: 12 hrs).
comment:324 in reply to: ↑ 323 Changed 5 years ago by anonymous
Replying to trojanfoe@…:
After updating to r35100 (TP-Link WA901ND) this is no longer happening (uptime: 12 hrs).
After 48 hours uptime, still no error:
[ 14.090000] eth0: link up (100Mbps/Full duplex) [ 14.740000] cfg80211: Calling CRDA for country: GB [ 14.750000] cfg80211: Regulatory domain changed to country: GB [ 14.750000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 14.760000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 14.770000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 14.780000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 14.780000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 56.160000] eth0: link down [ 64.160000] ar71xx: pll_reg 0xb8050014: 0x13000a44 [ 64.160000] eth0: link up (100Mbps/Full duplex) [ 82.160000] eth0: link down [ 83.160000] ar71xx: pll_reg 0xb8050014: 0x13000a44 [ 83.160000] eth0: link up (100Mbps/Full duplex) [118931.370000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Which is good news, no?
comment:325 Changed 5 years ago by anonymous
Still same problems after updating to r35162.
comment:326 Changed 5 years ago by anonymous
Two dais is a way too short time window to prove anything. In my case this bug happens apter aprox 14 days uptime. Please allow at least a few weeks before posting results.
comment:327 Changed 5 years ago by duvi
I really don't think this error is uptime dependent.
It may come up after 5 minutes or 2 weeks of uptime, it doesn't really matter.
For me it sometimes happens late at night, when there is not a single station connected to the AP, so the error is most probably triggered by a different wireless network / a device in a different network. Or just someone using the microwave oven..
What I think matters is what triggers it; which I believe noone knows yet (:
comment:328 Changed 5 years ago by mars
ath-9k keeps broken.
Hardware WR1043ND v1.0 / v1.8 (both Versions)
"DMA failed to stop" every 10 minutes to maximum 2hours. No recover.
Wireless-N/B/G does not matter (AP WDS, WMM inactive), severall other option do not influence.
Attitude Adjustment rc1 or trunk - no difference.
Restart of wifi does not help. Workaround with full reboot (takes 31s) Script:
/etc/rc.local add: /etc/config/watchdog.sh >> /dev/null 2>&1 &
/etc/config/watchdog.sh:
#!/bin/sh
sleep 60
logread | grep 'Could not stop RX, we could be confusing the DMA engine when we start RX up' | while read LINE; do
wget http://192.168.2.24/usr/logger.php?action=online 2> /dev/null & #log reboot to server
reboot
done
/etc/config/watchdog.sh >> /dev/null 2>&1 &
Is there a better (faster) way to reset or deal with that problem?
Script at comment 45 did not work for unknown reason.
Waiting for fixed version.
comment:329 Changed 5 years ago by nbd
which trunk version did you try?
comment:330 Changed 5 years ago by mars
http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin from 22-Jan-2013
(also tried builds of some days before)
sorry I don't remember the exact build number - as problems kept the same I switched back to attitude adjustement, due to at least better working luci ;)
comment:331 Changed 5 years ago by mars
additional information:
only the 1043ND v1.8 configured as AP WDS has this problems - the 1043ND v1.0 used before as AP WDS is now used as Client WDS + AP WDS Repeater and at this mode does not show this problem.
comment:332 Changed 5 years ago by anonymous
I have the same problem on my 1043ND. Configured as an AP. Currently running AA R35090.
Failed to stop TX DMA
errors seem to appear when there are more than two hosts connected to the AP. If I'm the only one using it then the problem rarely manifests. But if there are several people. And they are actively using their PCs - downloading/streaming then Internet connection slows down to a crawl (speedtest - from 50 MPPS down to <1 MPBS down, up speed seems to be unaffected).
My colleague has the same router. But there are only two active users in his household. Sometimes there are same errors in his logs and he experience slowdowns but for him those happen like once a month. Whereas I can get > 100 error messages in one evening before it forces me to restart the router.
comment:333 Changed 5 years ago by gertvdijk+openwrt@…
I may have provide a clue here.
I'm running AA-beta2 for a few months now on my TP-Link TL-WDR4300 and it was running fine ever since. Not a single wireless stability issue until today.
One Android device, an Asus Transformer TF300T tablet was updated with a new firmware and only minutes after updating it successfully, the wireless connections on that 2.4GHz radio are disconnecting regularly on all devices connected. Every single time the connection is dropped the kernel log reads the famous lines
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400 ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
The firmware of the tablet was updated from V10.4.2.18 to V10.4.2.20. As nothing else has changed in the network, I have a strong feeling that this device with its update is the cause and clues about it may lead to a fix, I hope.
I've also observed that the tablet connects fine to another very old WRT54G access point (running very old OpenWRT) and has no connection issues. The network on my AA-powered AP is stable again when having this tablet switched over.
The source of both firmwares is available for download here: Asus Download page for TF300T (select Android OS, then section Source code)
Relevant changes on this version by inspecting the differences is just this: Broadcom wireless driver updated from V7.0.24 to V7.0.64 (I'm not sure which exact driver from Broadcom this is).
comment:334 follow-up: ↓ 335 Changed 5 years ago by Romain Riviere <net+wrt@…>
Interesting. Could it be that only a particular type of client would cause this bug?
I am seeing it with a Broadcom chipset too (432b in a MacBookPro, problem occurs in Linux and MacOSX).
comment:335 in reply to: ↑ 334 ; follow-up: ↓ 336 Changed 5 years ago by anonymous
Replying to Romain Riviere <net+wrt@…>:
Interesting. Could it be that only a particular type of client would cause this bug?
I am seeing it with a Broadcom chipset too (432b in a MacBookPro, problem occurs in Linux and MacOSX).
Well, it happens on the router/access point and not on the client. I'd say that the clients' chipset does not change anything at all.
comment:336 in reply to: ↑ 335 Changed 5 years ago by Romain Riviere <net+wrt@…>
Replying to anonymous:
Replying to Romain Riviere <net+wrt@…>:
Interesting. Could it be that only a particular type of client would cause this bug?
I am seeing it with a Broadcom chipset too (432b in a MacBookPro, problem occurs in Linux and MacOSX).
Well, it happens on the router/access point and not on the client. I'd say that the clients' chipset does not change anything at all.
I was only reacting to the comment above mine, where a simple driver update seems to have triggered the bug. Then again, it might be coincidental.
comment:337 Changed 5 years ago by adxgrave@…
kern.err kernel: [20246.830000] ath: phy0: Failed to stop TX DMA, queues=0x100!
Lost the signal a few minutes, no reboot needed, the sinal came back on its own. Running AA 12.09 beta on TLWR1043ND.
comment:338 Changed 5 years ago by nbd
please try r35786 or newer
comment:339 Changed 5 years ago by duvi
Sorry, I got the same warning as described in comment:307
TL-WR1043ND, r35819:
[32043.600000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [32043.610000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [32043.620000] ------------[ cut here ]------------ [32043.620000] WARNING: at /mnt/hda/openwrt/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/recv.c:487 ath_stoprecv+0xfc/0xd64 [ath9k]() [32043.640000] Modules linked in: em_nbyte em_cmp sch_prio sch_gred em_meta act_ipt sch_dsmark sch_teql cls_basic em_text sch_htb sch_red sch_tbf sch_sfq act_police act_connmark act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_fq_codel sch_codel sch_ingress usblp ath79_wdt ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_nat_ftp nf_conntrack_irc nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_string xt_layer7 ipt_MASQUERADE iptable_nat xt_nat nf_nat_ipv4 nf_nat xt_recent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppox ipt_REJECT xt_TCPMSS xt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base ts_fsm ts_bm ts_kmp crc_ccitt ipv6 cfg80211(O) compat(O) arc4 crypto_blkcipher aead ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [32043.740000] Call Trace: [32043.740000] [<800703b0>] dump_stack+0x8/0x34 [32043.750000] [<80078dfc>] warn_slowpath_common+0x78/0xa4 [32043.750000] [<80078e40>] warn_slowpath_null+0x18/0x24 [32043.760000] [<80e67680>] ath_stoprecv+0xfc/0xd64 [ath9k] [32043.760000] [<80e62e08>] ath9k_deinit_device+0x4ec/0xb94 [ath9k] [32043.770000] [<80e63064>] ath9k_deinit_device+0x748/0xb94 [ath9k] [32043.770000] [32043.780000] ---[ end trace 2d7b868317930638 ]---
comment:340 Changed 5 years ago by slippern
Have the same problem on TP-Link TL-WR1043N/ND v1 with 12.09-rc1
[401424.610000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[401424.620000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[540368.590000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[540368.600000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[694359.610000] ------------[ cut here ]------------
[694359.610000] WARNING: at /build/ar71xx/generic/build_dir/linux-ar71xx_generic/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80859fd4()
[694359.630000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 78 (0x4e)
[694359.640000] Modules linked in: sch_fq_codel sch_hfsc cls_fw sch_ingress act_mirred act_connmark em_u32 cls_u32 ifb ath79_wdt ledtrig_usbdev ledtrig_netdev nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_string xt_layer7 ipt_MASQUERADE iptable_nat nf_nat xt_recent xt_helper xt_connmark xt_connbytes pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack 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(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) ts_fsm ts_bm ts_kmp crc_ccitt ipv6 cfg80211(O) compat(O) arc4 aes_generic mmc_block mmc_core usb_storage ohci_hcd ehci_hcd sd_mod ext4 jbd2 mbcache usbcore usb_common scsi_mod nls_base crc16 crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [last unloaded: ifb]
[694359.730000] Call Trace:[<80283918>] 0x80283918
[694359.730000] [<80283918>] 0x80283918
[694359.740000] [<8007198c>] 0x8007198c
[694359.740000] [<80859fd4>] 0x80859fd4
[694359.740000] [<80071a40>] 0x80071a40
[694359.750000] [<80859fd4>] 0x80859fd4
[694359.750000] [<801e1694>] 0x801e1694
[694359.760000] [<81b66eb0>] 0x81b66eb0
[694359.760000] [<8009c6a8>] 0x8009c6a8
[694359.760000] [<80165a44>] 0x80165a44
[694359.770000] [<80808000>] 0x80808000
[694359.770000] [<81b64fd8>] 0x81b64fd8
[694359.770000] [<80076a90>] 0x80076a90
[694359.780000] [<80076fb8>] 0x80076fb8
[694359.780000] [<80310000>] 0x80310000
[694359.780000] [<80310000>] 0x80310000
[694359.790000] [<800771c8>] 0x800771c8
[694359.790000] [<800a8560>] 0x800a8560
[694359.790000] [<800773fc>] 0x800773fc
[694359.800000] [<8006306c>] 0x8006306c
[694359.800000] [<80063240>] 0x80063240
[694359.810000] [<80310000>] 0x80310000
[694359.810000] [<800952a0>] 0x800952a0
[694359.810000] [<80064aa8>] 0x80064aa8
[694359.820000] [<80063260>] 0x80063260
[694359.820000] [<802f08b4>] 0x802f08b4
[694359.820000] [<803165f8>] 0x803165f8
[694359.830000] [<802f00dc>] 0x802f00dc
[694359.830000]
[694359.830000] ---[ end trace ca4a2faf4294de1f ]---
[1224717.950000] br-lan: port 2(wlan0) entered disabled state
[1224717.960000] br-lan: port 1(eth0.1) entered disabled state
[1224717.970000] device eth0.1 left promiscuous mode
[1224717.970000] device eth0 left promiscuous mode
[1224717.980000] br-lan: port 1(eth0.1) entered disabled state
[1224717.990000] device wlan0 left promiscuous mode
[1224718.000000] br-lan: port 2(wlan0) entered disabled state
[1224718.300000] eth0: link down
[1224720.270000] ar71xx: pll_reg 0xb8050014: 0x1a000000
[1224720.580000] eth0: link up (1000Mbps/Full duplex)
[1224720.600000] device eth0.1 entered promiscuous mode
[1224720.610000] device eth0 entered promiscuous mode
[1224720.630000] br-lan: port 1(eth0.1) entered forwarding state
[1224720.630000] br-lan: port 1(eth0.1) entered forwarding state
[1224721.600000] ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
[1224722.630000] br-lan: port 1(eth0.1) entered forwarding state
[1224723.090000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[1224723.110000] device wlan0 entered promiscuous mode
[1224723.140000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[1224723.800000] br-lan: port 2(wlan0) entered forwarding state
[1224723.800000] br-lan: port 2(wlan0) entered forwarding state
[1224723.810000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[1224725.800000] br-lan: port 2(wlan0) entered forwarding state
[1356462.140000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:341 Changed 5 years ago by Christophe <christophe@…>
I just ran into that bug again, the router was running a brand new r35887
ath: phy0: Failed to stop TX DMA, queues=0x00c! ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:342 Changed 5 years ago by alphasparc@…
On OpenWRT TP-Link WR1043ND (Attitude Adjustment, r35864)
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:343 follow-up: ↓ 346 Changed 5 years ago by gogothebee@…
I know this sounds silly, but I wrote a script today that listens to dmesg output and when it detects any errors from ath9k (like ath: phy0: Failed to stop TX DMA), it brings down the wifi, removes all ath9k related modules, reinserts them again and brings wifi up. Takes around 3 seconds. I know this is a temporary fix, but can somebody (nbd) explain would it work at all as a temporary cure, because a lot of people seem to depend on this driver working correctly.
comment:344 follow-up: ↓ 345 Changed 5 years ago by LokNar
comment:345 in reply to: ↑ 344 Changed 5 years ago by anonymous
Replying to LokNar:
Same issue:
ath: phy0: Failed to stop TX DMA, queues=0x100!TP-Link TL-WR1043ND v1
r35896
Also have in log:
random: Cannot read from /dev/random: Resource temporarily unavailable random: Only 16/20 bytes of strong random data available from /dev/random random: Not enough entropy pool available for secure operations WPA: Not enough entropy in random pool for secure operations - update keys later when the first station connects
Problem above discussed previously(https://forum.openwrt.org/viewtopic.php?id=30931)
Could it be somehow linked with topic's issue?
comment:346 in reply to: ↑ 343 ; follow-up: ↓ 347 Changed 5 years ago by Calin C. <calin@…>
Replying to gogothebee@…:
I know this sounds silly, but I wrote a script today that listens to dmesg output and when it detects any errors from ath9k (like ath: phy0: Failed to stop TX DMA), it brings down the wifi, removes all ath9k related modules, reinserts them again and brings wifi up. Takes around 3 seconds. I know this is a temporary fix, but can somebody (nbd) explain would it work at all as a temporary cure, because a lot of people seem to depend on this driver working correctly.
May I ask for your script?
Thanks!
comment:347 in reply to: ↑ 346 Changed 5 years ago by gogothebee@…
Replying to Calin C. <calin@…>:
May I ask for your script?
Thanks!
Of course. I'm off my workplace now and I won't have access to it for a week, but once I return, test and confirm for at least a day or two that it works at all, I'll post it here. Last Friday it worked - it detected several ath9k (the wireless driver) failures, disabled it and re-enabled it, but I'm not sure this will do any good in the long term. Sometimes the router becomes inaccessible for up to a minute (when the driver locks) and the only possible "cure" this patch potentially could do is bring this minute down do several seconds. It won't fix the root cause. I don't want to give people useless things to try, so first I must confirm it does anything useful myself.
I also managed to compile ath9k (the wireless driver) with a patch that is supposed to fix the issue: https://launchpadlibrarian.net/66622641/0001-ath9k-Fix-race-in-starting-stopping-DMA-of-hw-data-q.patch
The problem is that there are so many patches, "supposed" to fix it, that I must try them one by one. On other bug trackers the problem appears to be fixed, but a regression was reintroduced again.
I haven't tested it yet, because the first test bricked the router - the kernel module insterted okay in the kernel, but once I brought Wifi up -> kernel panic. I guess I had to use all other dependent modules from my compilation as well. Now the router dies on each boot when it tries to bring up the Wifi interface. As WR941ND doesn't have working failsafe mode yet (a patch is committed in trunk however), I'll have to open it, soldier here and there and unbrick it.
Be sure that I'll write in this thread as soon as I have more information.
comment:348 Changed 5 years ago by Fernando Hartmann <matafagafo@…>
Hi, I'm using OpenWrt Backfire 10.03.1 on TP-Link WR1043ND and had the same errors, until I changed the Wifi channel configuration from AUTO to 1.
I made this change 15 days ago, and after that the problem raised one 1 message (before a had alot of them in a few days), and even with this 1 message the router works well without needing to be restarted anymore.
I hope this help some one in the mitigation process.
comment:349 Changed 5 years ago by alphasparc@…
ATTITUDE ADJUSTMENT (Attitude Adjustment, r35974)
TL-WR1043ND
[ 3673.080000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [ 3673.090000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:350 Changed 5 years ago by Tiago Peralta <tperalta82@…>
Running r35953 for 2 days, and no issues so far.
The only difference is that i no longer live in Portugal (weird stuff)
heres my config
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11ng'
option path 'platform/ath9k'
list ht_capab 'SHORT-GI-40'
list ht_capab 'DSSS_CCK-40'
option channel '2'
option txpower '27'
option htmode 'HT40+'
option country 'IE'
config wifi-iface
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid '403 Forbidden'
option encryption 'psk2'
option key 'ixxxxxx'
comment:351 Changed 5 years ago by MediaManRIT
FYI, I'm still getting these on r36084. The day has been up ~1 1/2 days. People are getting disconnected several time a day. Here's /sys/kernel/debug/ieee80211/phy0/ath9k/reset
root@MainOffice:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 2
PLL RX Hang: 0
MCI Reset: 0
However, in the log for today I see all this
Mar 22 08:16:13 10.3.79.242 Mar 22 08:16:13 kernel: [110459.640000] ath: phy0: Failed to stop TX DMA, queues=0x10d! Mar 22 09:28:18 10.3.79.242 Mar 22 09:28:18 kernel: [114784.620000] ath: phy0: Failed to stop TX DMA, queues=0x001! Mar 22 09:32:42 10.3.79.242 Mar 22 09:32:42 kernel: [115049.200000] ath: phy0: Failed to stop TX DMA, queues=0x004! Mar 22 09:33:21 10.3.79.242 Mar 22 09:33:21 kernel: [115088.210000] ath: phy0: Failed to stop TX DMA, queues=0x005! Mar 22 10:03:58 10.3.79.242 Mar 22 10:03:58 kernel: [116925.070000] ath: phy0: Failed to stop TX DMA, queues=0x004! Mar 22 10:27:54 10.3.79.242 Mar 22 10:27:54 kernel: [118360.770000] ath: phy0: Failed to stop TX DMA, queues=0x100! Mar 22 10:42:59 10.3.79.242 Mar 22 10:42:59 kernel: [119265.740000] ath: phy0: Failed to stop TX DMA, queues=0x004! Mar 22 10:43:25 10.3.79.242 Mar 22 10:43:25 kernel: [119291.720000] ath: phy0: Failed to stop TX DMA, queues=0x005! Mar 22 10:50:13 10.3.79.242 Mar 22 10:50:13 kernel: [119699.440000] ath: phy0: Failed to stop TX DMA, queues=0x005! Mar 22 11:43:26 10.3.79.242 Mar 22 11:43:26 kernel: [122892.670000] ath: phy0: Failed to stop TX DMA, queues=0x104! Mar 22 11:45:48 10.3.79.242 Mar 22 11:45:48 kernel: [123035.100000] ath: phy0: Failed to stop TX DMA, queues=0x004!
A lot more then two "Failed to stop"s in there...
comment:352 Changed 5 years ago by valent.turkovic@…
With DD-WRT is the same issue:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=169135
Some of dd-wrt users ported wifi working ok when reverting back to a much older version...
comment:353 Changed 5 years ago by valent.turkovic@…
Also this comment is most useful that I have found so far and has great deal of good info:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=724078#724078
comment:354 Changed 5 years ago by mikaelbrostrom <mikael_openwrt@…>
Just thinking loud:
Does the "mtd4" flash device with namned "art" has something to do with this?
if older devices work until they get upgraded. but starts failing after downgrading again.
maby this partition gets upgraded? and the "Atheros Radio Test" is done on a new way and mess up the chip state?
ART = Atheros Radio Test - it contains mac addresses and calibration data for the wifi (EEPROM). If it is missing or corrupt, ath9k won't come up anymore.
NOTE: Make backup before trying something:
dd if=/dev/mtd4 of=mtd4.dd
/Mikael
comment:355 Changed 5 years ago by mikaelbrostrom <mikael_openwrt@…>
Try this config, is has worked without any problems for 2 weeks on a ap.
ctrl_interface=/tmp/hostapd-wlan0.ctrl
driver=nl80211
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
tx_queue_data3_aifs=7
tx_queue_data3_cwmin=15
tx_queue_data3_cwmax=1023
tx_queue_data3_burst=0
tx_queue_data2_aifs=3
tx_queue_data2_cwmin=15
tx_queue_data2_cwmax=63
tx_queue_data2_burst=0
tx_queue_data1_aifs=1
tx_queue_data1_cwmin=7
tx_queue_data1_cwmax=15
tx_queue_data1_burst=3.0
tx_queue_data0_aifs=1
tx_queue_data0_cwmin=3
tx_queue_data0_cwmax=7
tx_queue_data0_burst=1.5
hw_mode=g
channel=6
beacon_int=100
country_code=US
ieee80211n=1
ht_capab=[HT20-][SHORT-GI-40][DSSS_CCK-40]
wmm_enabled=1
ieee80211d=1
ignore_broadcast_ssid=0
interface=wlan0
bridge=br0
ssid=OpenWrt
debug=0
wpa=2
wpa_pairwise=CCMP
wpa_passphrase=CHANGEME
noscan=1
auth_algs=1
dtim_period=2
fragm_threshold=2346
max_num_sta=256
rts_threshold=2346
# restart hostapd:
hostapd -B -P /tmp/hostapd-wlan0.pid /tmp/hostapd-wlan0.conf
comment:356 Changed 5 years ago by valent.turkovic@…
Is this issue causing also this bug:
/ticket/13230.html ?
comment:357 follow-up: ↓ 363 Changed 5 years ago by gogothebee@…
Ok, I gave up. OpenWrt turned out too unstable for my router/configuration. I've reverted back to stock FW since the WR941ND is used only as Dump AP. Here is my auto-restart script, which actually works, but is a ugly workaround.
/etc/init.d/ath9k_restart
#!/bin/sh /etc/rc.common
# Copyright (C) 2006-2010 OpenWrt.org
# Copyright (C) 2006 Carlos Sobrinho
START=98
STOP=98
SERVICE_USE_PID=1
NAME=ath9_restart
PIDCOUNT=0
#EXTRA_COMMANDS="killclients"
#EXTRA_HELP=" killclients Kill ${NAME} processes except servers and yourself"
start()
{
/usr/bin/ath9k_restart.sh &
}
stop()
{
killall ath9k_restart.sh
}
/usr/bin/ath9k_restart.sh
#!/bin/sh
echo -n "Script started at: " >> /tmp/ath9_restart_time
date >> /tmp/ath9_restart_time
new_timestamp=`dmesg |tail -1| awk '{print $1}'`
old_timestamp=$new_timestamp
while [ 1 ]
do
new_timestamp=`dmesg |tail -1| awk '{print $1}'`
if [ "$new_timestamp" != "$old_timestamp" ]; then
echo "Timestamps differ"
old_timestamp=$new_timestamp
dmesg | tail -1 | grep "ath: phy0: Failed" >/dev/null
if [ $? -eq 0 ]; then
echo "Comparion success"
wifi down
rmmod ath9k
rmmod ath9k_common
rmmod ath9k_hw
rmmod ath
/etc/init.d/dnsmasq restart
insmod ath
insmod ath9k_hw
insmod ath9k_common
insmod ath9k
wifi up
echo -n "Restart at: " >> /tmp/ath9_restart_time
date >> /tmp/ath9_restart_time
fi
fi
sleep 5
done
echo -n "Script stopped at: " >> /tmp/ath9_restart_time
date >> /tmp/ath9_restart_time
Once you create both files, do:
chmod +x /usr/bin/ath9k_restart.sh
chmod 755 /etc/init.d/ath9k_restart
/etc/init.d/ath9k_restart start
comment:358 Changed 5 years ago by gogothebee@…
If the above script works for you, enable the script permanently.
CAUTION!!! Test it first. It works here, may not work somewhere else!!! I don't take any responsibility.
/etc/init.d/ath9k_restart enable
comment:359 Changed 5 years ago by hojuruku@…
I've tried disabling short preamble as some has suggested at DDRT. No great improvement.
disabling HT options.. nope. fiddling with RTS/frag. Nope.
Further research shows that this issue is known on other platforms.
At least previously ath9k didn't support multiple VAPS (master mode interfaces) and hw encryption at the same time. If you want HW encryption, then have only one master. I can't have it that way because WMM is broken on some androids (like mine) so I need another VAP with it disabled.
Disabling HW encryption (loading ath9k module with nohwcrypt=1) is going to slow throughput to 13mbit with a 400Mhz so this is a really painful issue.
Maybe the offical atheros drivers need to be ported to kernel 3.8.(just kidding)
comment:360 Changed 5 years ago by hojuruku@…
No that wasn't it either. Disabled all VAP reverting to 1. So far NO error. Look at how multiple VAP's are enabled in the madwifi code in respect to encryption. Also running on the same mac address the card came with seemed to have solved the issue for me. Really I tried every possible setting incrementally. Did everyone who reported this issue have multiple SSIDs?
comment:361 Changed 5 years ago by valent.turkovic@…
I'm just fidling with wifi power settings, after lowering wifi power from 27 dBm (500mW) to 17 dBm (50mW) looks like client clients keep RX speed on higher levels (MCS 6-7) instead of dropping RX to lower speeds (MSC 0).
comment:362 Changed 5 years ago by Luke McKee <hojuruku@…>
Yeah I confirm that setting the default power level (not using txpower) keeps the rx speed at higher levels.
Also the error is *almost* nonexistent when there is only one VAP. It doesn't apply to master mode interfaces either. Having one STA (wds) and one AP is still going to provoke this error.
comment:363 in reply to: ↑ 357 Changed 5 years ago by Torxgewinde
I modfied the script of yours, because it might miss an entry since it just checks the last line. Here is my version of that script. For the convenience i kept the unaltered files as they were, so it is easy to copy and paste.
To test simply issue the command below and check the kernel messages:
logger "ath: phy0: Failed"
Replying to gogothebee@…:
... Here is my auto-restart script, which actually works, but is a ugly workaround.
/etc/init.d/ath9k_restart
#!/bin/sh /etc/rc.common # Copyright (C) 2006-2010 OpenWrt.org # Copyright (C) 2006 Carlos Sobrinho START=98 STOP=98 SERVICE_USE_PID=1 NAME=ath9_restart PIDCOUNT=0 #EXTRA_COMMANDS="killclients" #EXTRA_HELP=" killclients Kill ${NAME} processes except servers and yourself" start() { /usr/bin/ath9k_restart.sh & } stop() { killall ath9k_restart.sh }
/usr/bin/ath9k_restart.sh
#!/bin/sh logger "ath9k restart script started at: $(date)" logread -f | while read LINE; do echo "$LINE" | grep -e 'ath: phy.*[Ff]ailed' if [ $? -ne 0 ]; then continue fi # Line above contains our trigger to perform the restart now logger "RESTARTING ATH9K" wifi down rmmod ath9k rmmod mac80211 rmmod ath9k_common rmmod ath9k_hw rmmod ath rmmod cfg80211 rmmod compat /etc/init.d/network stop insmod compat insmod cfg80211 insmod ath insmod ath9k_hw insmod ath9k_common insmod mac80211 insmod ath9k /etc/init.d/network start /etc/init.d/led restart done exit 0
Once you create both files, do:
chmod +x /usr/bin/ath9k_restart.sh
chmod 755 /etc/init.d/ath9k_restart
/etc/init.d/ath9k_restart start
comment:364 Changed 5 years ago by Torxgewinde
Ok, I had the error very reproducible and I could try a couple of different settings.
I narrowed it down to the 40MHz/20MHz bandwidth. After respecting busy channels and thus limiting the radio to slow 20 MHz bandwidth it is now working stable again.
Below is my config, as you can see I commented more and more options out. As soon as I disabled the noscan option it told me when bringing up the interface:
20/40 MHz operation not permitted on channel pri=6 sec=2 based on overlapping BSSes
I tried in this order:
- disabled both WMM options (comment # 1) -> still errors
- disabling the secondary VAP (comment # 2) -> still the error ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
- commented out "bursting, distance, ar, xr, compression, ff, beacon_int" (comment # 3) -> still error present
- commented out "noscan" (comment # 4) and since then it is running fine, but it seems to respect my neighbours networks and thus works on 20 MHz bandwidth only.
This means it will be slower than it could be, but at least it stays active.
config wifi-device 'radio0' option type 'mac80211' option macaddr '.......' option hwmode '11ng' list ht_capab 'SHORT-GI-40' list ht_capab 'DSSS_CCK-40' option channel '6' option htmode 'HT40-' option country 'US' option txpower '23' #4 option noscan '1' #3 option bursting '1' #3 option ff '1' #3 option compression '1' #3 option xr '1' #3 option ar '1' #3 option distance '25' #3 option beacon_int '5000' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option ssid 'Papa George Net 2' option encryption 'psk2+ccmp' option key '............' #1 option wmm '1' #2config wifi-iface #2 option device 'radio0' #2 option network 'lan' #2 option mode 'ap' #2 option ssid 'Papa George Net 1' #2 option encryption 'psk2+ccmp' #2 option key '................' #1 option wmm '1'
comment:365 Changed 5 years ago by hojuruku@…
Torxgewinde,
half of the settings only apply to "atheros" drivers not ath9k/ath5k. extended range is only supported in client mode on that driver too. you might want to grep for them in /lib/wifi/*.sh
With noscan=0 i get the tx dma error when there is a second client mode interface after 2 mins uptime.
ath: phy0: Failed to stop TX DMA, queues=0x004!
After 10 mins uptime with noscan=0, the sta1 (wds vlan AP) on the other 941-nd there has been no error. Not to say that it will hit something in due course. Interference plus having multiple master and or client interfaces on AR91xx / AR9330 rev 1 Soc WMACS seems to be the cause of the problem.
Setting txpower to auto seems to help as well, but all this is subjective. With txpower set to auto it takes a few minuites for the packet loss / tx errors to go down to more acceptable levels, but after that the network is more responsive.
Also the rx speed issue is attributed to this: /ticket/12372.html
Disable_ami really helps. echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/disable_ami.
comment:366 Changed 5 years ago by Torxgewinde
Thanks for the info, I have it now working with all ath9k (not atheros) options enabled and I also changed the wifi restart script to send me an email for every restart of wifi. After my first few bad days with up to 30 restarts of the wifi driver, I have now zero.
I set the language to DE since the router is a German v1.1 and I can imagine that the radio calibration partition is somehow the culprit. As a result the maximum tx power is now 20 dbm, which does not really hurt. I also selected a "not so ideal" channel which is not used by anyone in my wifi-wise-busy-neighborhood.
Taking into account the adaptive noise immunity (assuming a typo above) disable recommendation of yours, for me it sounds as if there is something a bit bonkers with densely populated neighborhoods. Why might it be that the drivers do not play nicely with other networks next door , don't know - but at least I can use it now...
comment:367 Changed 5 years ago by hajduatti@…
1043ND with Attitude Adjustment (12.09 final):
[ 1273.770000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[ 1273.780000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 1273.800000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 1274.040000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:368 Changed 5 years ago by cyberbastion
Hi All,
I'm using ATTITUDE ADJUSTMENT (12.09-rc1, r34185)
and having same error
[275375.630000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[275375.640000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[276367.460000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[276367.470000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:369 Changed 5 years ago by anonymous
Tired with this nasty bug from early releases of backfire, thinked to move to 12.09, but
bug is not fixed, so no reason to update ...
Maybe look to other projects, gargoyle/dd-wrt for a solution?
or even mail to TP-Link
comment:370 Changed 5 years ago by mikaelbrostrom <mikael_openwrt@…>
Just send a mail to support@tp-link... :) asking for the developers.
i will try to ask them later for some directions how to solve this issue.
btw.....
can it be that when a client-device comes too far away, the device transmitting at high power, so that the power is not enough to power the circuit? and this in turn generates DMA error I put down txpower to 24mw and after that I have not had any problems at 14days.
iwconfig wlan0 txpower 24mw
comment:371 Changed 5 years ago by lct@…
Hello! This is very sad, that this Ticket exists...
If you want to contact TPLink, you can contact me at LCT ATTTT mail DOOTTTT ru, I can provide you with SN for my device so you get to lower level support.
Please make sure that Level one support understands that:
I have bought all my TP-Link devices ONLY because they support OpenWRT.
I called TPLink and thanked them for that.
This is because due to that, I can use OpenWRT or TPLink own firmware.
If TPLink EOLs my device, I can always go with OpenWRT.
Their support for OpenWRT is beneficial to BOTH OpenWRT AND TPLink.
They should understand, that supporting OpenWRT is in their OWN interest.
If TPLink does not support OpenWRT, I will NOT PURCHASE TPLink device.. This is something that must be clear to them.
comment:372 Changed 5 years ago by nbd
please try latest trunk
comment:373 Changed 5 years ago by anonymous
I tied latest trunk two weeks ago and still had this issue.
Has there been any significant change in code that could fix this issue? If not then I can safely say that latest trunk is still broken (since two weeks ago).
comment:374 Changed 5 years ago by nbd
I committed something for this issue on AR913x hardware today
comment:375 Changed 5 years ago by sayap
@anonymous, just keep checking https://dev.openwrt.org/log from time to time, and whenever you see a commit from nbd that says mac80211, in particularly ath9k, it's time to build from the trunk once again.
@nbd, thanks for the hard work! Much appreciated. Will try the latest trunk as soon as I can.
comment:376 Changed 5 years ago by mikaelbrostrom <mikael_openwrt@…>
Sad news :/
nbd, thanks for your good work! trying to solve this!
[13836.880000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[13836.890000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
problem, still there :/
comment:377 Changed 5 years ago by veekinz@…
Yup, same here: (r36531)
[ 1745.740000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[ 1745.750000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9814.110000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[ 9814.120000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[10261.030000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[10261.050000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[10261.060000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[72741.650000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[72741.660000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[72741.670000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
But it's pretty comforting to know that I never noticed this until I looked into the logs just now.
The device doesn't freeze/reboot nor does the connection break. Good work. :)
comment:378 Changed 5 years ago by cquijano
Same problem Here, kernel error only happens when clients are connecting (10 clients aprox) or high load on ap's.
[ 96.360000] br-lan: port 2(client_0_priv) entered forwarding state [ 96.480000] IPv6: ADDRCONF(NETDEV_UP): mesh_0_g: link is not ready [ 96.750000] mesh_0_g: Selected IBSS BSSID 02:ca:ff:ee:ba:be based on configured SSID [ 96.750000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh_0_g: link becomes ready [ 98.940000] batman_adv: bat0: Adding interface: mesh_0_g [ 98.950000] batman_adv: bat0: Interface activated: mesh_0_g [ 98.960000] device bat0 entered promiscuous mode [ 98.960000] br-lan: port 3(bat0) entered listening state [ 98.970000] br-lan: port 3(bat0) entered listening state [ 99.210000] batman_adv: bat0: ap_isolation: Changing from: disabled to: enabled [ 99.230000] batman_adv: bat0: bridge_loop_avoidance: Changing from: disabled to: enabled [ 99.230000] batman_adv: bat0: distributed_arp_table: Changing from: enabled to: disabled [ 99.250000] batman_adv: bat0: Changing gateway bandwidth from: '41' to: '48' (propagating: 4MBit/512KBit) [ 99.270000] batman_adv: bat0: Changing gw mode from: off to: server [ 100.970000] br-lan: port 3(bat0) entered learning state [ 102.970000] br-lan: topology change detected, propagating [ 102.970000] br-lan: port 3(bat0) entered forwarding state ====Clients start to connect=== [22241.210000] ath: phy0: Failed to stop TX DMA, queues=0x004! [22520.300000] ath: phy0: Failed to stop TX DMA, queues=0x104! [22540.340000] ath: phy0: Failed to stop TX DMA, queues=0x005! [22677.310000] ath: phy0: Failed to stop TX DMA, queues=0x104! [22699.080000] ath: phy0: Failed to stop TX DMA, queues=0x004! [22721.120000] ath: phy0: Failed to stop TX DMA, queues=0x005!
Board
root@OpenWrt:~# cat /proc/cpuinfo system type : Atheros AR7241 rev 1 machine : Ubiquiti UniFi processor : 0 cpu model : MIPS 24Kc V7.4 BogoMIPS : 259.27 wait instruction : yes microsecond timers : yes tlb_entries : 16 extra interrupt vector : yes hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x0ff8, 0x0ff8, 0x0ff8] ASEs implemented : mips16 shadow register sets : 1 kscratch registers : 0 core : 0 VCED exceptions : not available VCEI exceptions : not available
Release
commit 6f35334f3c9b5d0586107c86d26a29db87e23db4 Author: cyrus <cyrus@3c298f89-4303-0410-b956-a3cf2f4a3e73> Date: Tue May 7 07:19:51 2013 +0000
Wireless Config
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11ng'
option path 'pci0000:00/0000:00:00.0'
list ht_capab 'SHORT-GI-40'
list ht_capab 'TX-STBC'
list ht_capab 'RX-STBC1'
list ht_capab 'DSSS_CCK-40'
option htmode 'HT40+'
option noscan '1'
option channel '5'
option country 'US'
option txpower 'auto'
option disabled '0'
config wifi-iface 'mesh_0_g'
option device 'radio0'
option network 'mesh'
option mode 'adhoc'
option bssid '02:CA:FF:EE:BA:BE'
option ssid ' '
option encryption 'none'
option hidden '1'
option ifname 'mesh_0_g'
option macaddr '00:27:22:23:1A:4E'
config wifi-iface 'client_0_pub'
option device 'radio0'
option network 'lan'
option ifname 'client_0_pub'
option mode 'ap'
option macaddr '1A:27:22:23:1A:4E'
option disabled '0'
option ssid 'Publica'
option encryption 'none'
config wifi-iface 'client_0_priv'
option device 'radio0'
option network 'lan'
option ifname 'client_0_priv'
option mode 'ap'
option encryption 'psk2+aes'
option key '********'
option macaddr '0A:27:22:23:1A:4E'
option disabled '0'
option ssid 'FCatolico'
This error make network Unusable! latency is very high:
Ping to a client connected to the ap:
root@OpenWrt:~# ping julia PING julia (10.0.159.234): 56 data bytes 64 bytes from 10.0.159.234: seq=0 ttl=128 time=236.509 ms 64 bytes from 10.0.159.234: seq=1 ttl=128 time=330.416 ms 64 bytes from 10.0.159.234: seq=2 ttl=128 time=24.567 ms 64 bytes from 10.0.159.234: seq=3 ttl=128 time=6.102 ms 64 bytes from 10.0.159.234: seq=4 ttl=128 time=41.278 ms ^C --- julia ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 6.102/127.774/330.416 ms
comment:379 Changed 5 years ago by anonymous
Hello nbd, testing latest trunk...
r36676 - TL-WR1043ND V1.1
still got the:
[ 123.680000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 133.510000] ath: phy0: Failed to stop TX DMA, queues=0x004!
and it now reboots the machine, i can't get further error information.
best regards.
comment:380 Changed 5 years ago by don.nasco@…
Hi,
Just for the record (Attitude Adjustment, r36715):
[60710.260000] ------------[ cut here ]------------
[60710.270000] WARNING: at /home/vlado/owrt/a_a/build_dir/linux-ar71xx_generic/compat-wireless-2013-02-22/net/mac80211/rx.c:3291 0x80e1bba4()
[60710.280000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 79 (0x4f)
[60710.290000] Modules linked in: fuse ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ath79_wdt ledtrig_usbdev ledtrig_netdev ipt_MASQUERADE iptable_nat nf_nat xt_conntrack xt_CT 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 msdos vfat fat ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) nls_utf8 nls_koi8_r nls_iso8859_2 nls_iso8859_15 nls_iso8859_13 nls_iso8859_1 nls_cp866 nls_cp852 nls_cp850 nls_cp775 nls_cp437 nls_cp1251 nls_cp1250 mac80211(O) cfg80211(O) compat(O) md5 md4 hmac ecb des_generic arc4 aes_generic crypto_blkcipher cryptomgr aead usb_storage ohci_hcd ehci_hcd sd_mod ext4 jbd2 mbcache usbcore usb_common scsi_mod nls_base crc16 crypto_hash crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O)
[60710.380000] Call Trace:[<8026bf2c>] 0x8026bf2c
[60710.380000] [<8026bf2c>] 0x8026bf2c
[60710.380000] [<80071a8c>] 0x80071a8c
[60710.390000] [<80e1bba4>] 0x80e1bba4
[60710.390000] [<80071b40>] 0x80071b40
[60710.390000] [<80e1bba4>] 0x80e1bba4
[60710.400000] [<80259504>] 0x80259504
[60710.400000] [<801e0510>] 0x801e0510
[60710.410000] [<80d067a4>] 0x80d067a4
[60710.410000] [<8025a560>] 0x8025a560
[60710.410000] [<8025a34c>] 0x8025a34c
[60710.420000] [<8006b7e0>] 0x8006b7e0
[60710.420000] [<80d042f4>] 0x80d042f4
[60710.420000] [<80076b70>] 0x80076b70
[60710.430000] [<80077094>] 0x80077094
[60710.430000] [<800772a0>] 0x800772a0
[60710.430000] [<800a8540>] 0x800a8540
[60710.440000] [<800774d4>] 0x800774d4
[60710.440000] [<8006316c>] 0x8006316c
[60710.440000] [<80063340>] 0x80063340
[60710.450000] [<80095290>] 0x80095290
[60710.450000] [<800a8274>] 0x800a8274
[60710.460000] [<80064ba8>] 0x80064ba8
[60710.460000] [<80063360>] 0x80063360
[60710.460000] [<802d78b0>] 0x802d78b0
[60710.470000] [<802fcd28>] 0x802fcd28
[60710.470000] [<802d70dc>] 0x802d70dc
[60710.470000]
[60710.470000] ---[ end trace a4142f1bb122f3ca ]---
[151185.800000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[151185.810000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:381 Changed 5 years ago by ufo@…
also at #battlemesh with https://github.com/battlemesh/battlemesh-packages/issues/13
comment:382 Changed 5 years ago by anonymous
This issue is still present, TL-WR1043ND running release version of Attitude Adjustment 12.09:
[ 26.770000] br-lan: port 2(wlan0) entered forwarding state
[74624.380000] ath: phy0: Failed to stop TX DMA, queues=0x100!
[74692.490000] ath: phy0: Failed to stop TX DMA, queues=0x100!
[74744.700000] ath: phy0: Failed to stop TX DMA, queues=0x100!
[99101.650000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0
[99101.660000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[99153.440000] ath: phy0: Failed to stop TX DMA, queues=0x100!
[183504.190000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[183504.200000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:383 Changed 5 years ago by nbd
please try latest trunk
comment:384 Changed 5 years ago by valent.turkovic@…
Is there any sign of tracking down this bug? Is anybody of developers working on this? Can we (users) help in any way? Do you need some extra logs? Do you need access to this routers running openwrt? Do you need pizza? Caffee? I'm willing to donate some ammount of money to get this bug fixed because I can't do anything else...
comment:385 Changed 5 years ago by nbd
There's no 'this bug' - there's a bunch of different issues that result in the same or similar symptoms. Most of these issues I've already fixed, some remain.
I don't have any suggestions for capturing more logs. My approach for fixing this is to keep reviewing the code, running different tests, fixing issues that I find, and then waiting for people to give feedback.
The best way for you guys to help me is to keep testing newer versions as I make changes to mac80211/ath9k. Many people who have had these symptoms now have reliably working systems, only in some setups or on some setups the problems remain.
When testing, please make sure you use very recent versions and always report the revision that you're using.
Thanks.
comment:386 Changed 5 years ago by miguel.arce@…
Hi nbd,
Reporting on the lastest trunk r36859 on a TL-WR1043ND REV 1.7 from june 6.
previously this messages didn't apeared, it just got rebooted or crashed.
i havent got the time to test the june 8 build, i am hoping of testing it tonight and report tomorrow, i only see a couple of changes in the ath9k package.
[138574.550000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [138574.560000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [141254.480000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [141254.490000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
same behavior as on the r36736, still have the ath TX DMA messages but
it seems a bit more stable for some reason, previously it just rebooted or
crashed instantly within 5 minutes of high traffic, now it still reboots itself but
takes about 30 - 50 minutes under high traffic.
also r36859 seems much more stable in heavy duty than previous trunks releases.
This is from r36736:
i manage to get error information as for the unstable wireless.
i have been waiting for the router to report something and not just
hang or reboot, i finally got the following, by simply leaving it work without any
kind of traffic.
BusyBox v1.19.4 (2013-05-27 13:15:06 PDT) 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
-----------------------------------------------------
BARRIER BREAKER (Bleeding Edge, r36736)
-----------------------------------------------------
* 1/2 oz Galliano Pour all ingredients into
* 4 oz cold Coffee an irish coffee mug filled
* 1 1/2 oz Dark Rum with crushed ice. Stir.
* 2 tsp. Creme de Cacao
-----------------------------------------------------
root@TL-WR1043ND:~# dmesg
[306829.550000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[311168.630000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[383084.610000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[399010.080000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[426044.310000] ------------[ cut here ]------------
[426044.320000] WARNING: at /ramdisk/openwrt/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2013-04-16/net/mac80211/rx.c:3310 ieee80211_rx+0x134/0x800 [mac80211]()
[426044.340000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 79 (0x4f)
[426044.350000] Modules linked in: ath79_wdt ledtrig_usbdev ledtrig_netdev ledtrig_heartbeat ip6t_REJECT ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6table_mangle ip6table_filter ip6_tables nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_irc nf_nat_ftp nf_conntrack_irc nf_conntrack_ftp xt_REDIRECT ipt_MASQUERADE iptable_nat xt_nat nf_nat_ipv4 nf_nat pppoe xt_conntrack xt_CT iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack pppox xt_mark xt_time ipt_REJECT xt_TCPMSS xt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) crc_ccitt ipv6 cfg80211(O) compat(O) arc4 crypto_blkcipher aead usb_storage ohci_hcd ehci_platform ehci_hcd sd_mod ext4 jbd2 mbcache usbcore usb_common scsi_mod nls_base crc16 crypto_hash ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O)
[426044.430000] Call Trace:
[426044.430000] [<8006df60>] dump_stack+0x8/0x34
[426044.440000] [<80076864>] warn_slowpath_common+0x78/0xa4
[426044.440000] [<80076918>] warn_slowpath_fmt+0x2c/0x38
[426044.450000] [<80e1c9d0>] ieee80211_rx+0x134/0x800 [mac80211]
[426044.450000] [<80e66984>] ath_rx_tasklet+0xef0/0xfcc [ath9k]
[426044.460000] [<80e6441c>] ath9k_tasklet+0xe8/0x140 [ath9k]
[426044.470000] [<8007dbac>] tasklet_action+0x78/0xc8
[426044.470000] [<8007d3f4>] __do_softirq+0xb0/0x184
[426044.470000] [<8007d578>] do_softirq+0x48/0x68
[426044.480000] [<8007d794>] irq_exit+0x4c/0x84
[426044.480000] [<8006082c>] ret_from_irq+0x0/0x4
[426044.490000] [<80060a60>] r4k_wait+0x20/0x40
[426044.490000] [<8006b8c8>] cpu_idle+0x30/0x60
[426044.500000] [<803398ec>] start_kernel+0x364/0x384
[426044.500000]
[426044.500000] ---[ end trace b921a9934dd70b1d ]---
root@TL-WR1043ND:~#
The last version I used is the official 10.03.1 on this router, in which the wireless was working rock solid.
I decided to upgrade because of some new features introduced, like the packages minidlna, libffmpeg-full, and other kernel fetures enabled like inotify.
I will continue to test out the revistions and posting in this threat as this is the one I see you are monitoring…
Thanks for all your great work
Best regards.
comment:387 Changed 5 years ago by openwrt@…
I tried AA rc2, release and then the latest AA trunk (as of 8th June) on my WR1043ND. All had the same issue - after a period of time, usually coinciding with heavy activity, pings from my Realtek 8192SE powered Toshiba laptop (to either the WR1043ND itself, or a gigabit ethernet device connected to it) would go through the roof - like 3000 or 4000ms. There was also some hefty (but not total) packet loss, maybe around 33%. On the earlier builds I'm sure I saw DMA errors, but on trunk I kept checking the logs but there were none of the DMA errors people have listed above - in fact nothing that suggested it was having any problems at all. Is it related to the other issues listed under this bug or is it something new?
I've switched back to running TP Link stock firmware and the Wifi is rock solid, although their firmware has other (DHCP/DNS) issues that make it next to useless.
comment:388 Changed 5 years ago by miguel.arce@…
hello nbd, reporting on latest trunk
BARRIER BREAKER (Bleeding Edge, r36909) (from june 10).
on a TL-WR1043ND REV 1.7.-
same behaviour, as soon as high traffic start it reboots,
and seems its not much more stable than previous snapshots,
as now as soon as i start transmission, 5 - 7 minutes that
it start sending an receiving data, i get a lot of TX DMA messages
and reboots.
of if i use the minidlna vía wifi it also reboots...
if i access the minidlna service vía ethernet, it works without incident.
best regards.
[ 0.000000] Linux version 3.8.13 (fnord@tschunk) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2012.12 r36909) ) #1 Mon Jun 10 21:39:18 UTC 2013 [ 0.000000] MyLoader: sysp=ffffffff, boardp=ffffffff, parts=ffffffff [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU revision is: 00019374 (MIPS 24Kc) [ 0.000000] SoC: Atheros AR9132 rev 2 [ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:5.000MHz [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 02000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x00000000-0x01ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x01ffffff] [ 0.000000] On node 0 totalpages: 8192 [ 0.000000] free_area_init_node: node 0, pgdat 80320a40, node_mem_map 81000000 [ 0.000000] Normal zone: 64 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 8128 pages, LIFO batch:0 [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128 [ 0.000000] Kernel command line: board=TL-WR1043ND console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd [ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes) [ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] __ex_table already sorted, skipping sort [ 0.000000] Writing ErrCtl register=00000000 [ 0.000000] Readback ErrCtl register=00000000 [ 0.000000] Memory: 28720k/32768k available (2306k kernel code, 4048k reserved, 599k data, 228k init, 0k highmem) [ 0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:51 [ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104) [ 0.080000] pid_max: default: 32768 minimum: 301 [ 0.080000] Mount-cache hash table entries: 512 [ 0.090000] NET: Registered protocol family 16 [ 0.100000] MIPS: machine is TP-LINK TL-WR1043ND [ 0.360000] bio: create slab <bio-0> at 0 [ 0.370000] Switching to clocksource MIPS [ 0.380000] NET: Registered protocol family 2 [ 0.380000] TCP established hash table entries: 512 (order: 0, 4096 bytes) [ 0.380000] TCP bind hash table entries: 512 (order: -1, 2048 bytes) [ 0.390000] TCP: Hash tables configured (established 512 bind 512) [ 0.390000] TCP: reno registered [ 0.400000] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.400000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.410000] NET: Registered protocol family 1 [ 0.410000] PCI: CLS 0 bytes, default 32 [ 0.430000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.430000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.450000] msgmni has been set to 56 [ 0.450000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.460000] io scheduler noop registered [ 0.460000] io scheduler deadline registered (default) [ 0.470000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled [ 0.500000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A [ 0.510000] console [ttyS0] enabled, bootconsole disabled [ 0.520000] ath79-spi ath79-spi: master is unqueued, this is deprecated [ 0.530000] m25p80 spi0.0: found s25sl064p, expected m25p80 [ 0.530000] m25p80 spi0.0: s25sl064p (8192 Kbytes) [ 0.540000] 5 tp-link partitions found on MTD device spi0.0 [ 0.540000] Creating 5 MTD partitions on "spi0.0": [ 0.550000] 0x000000000000-0x000000020000 : "u-boot" [ 0.560000] 0x000000020000-0x000000124800 : "kernel" [ 0.560000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only [ 0.580000] 0x000000124800-0x0000007f0000 : "rootfs" [ 0.580000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only [ 0.590000] mtd: partition "rootfs" set to be root filesystem [ 0.600000] mtd: partition "rootfs_data" created automatically, ofs=2E0000, len=510000 [ 0.610000] 0x0000002e0000-0x0000007f0000 : "rootfs_data" [ 0.620000] 0x0000007f0000-0x000000800000 : "art" [ 0.620000] 0x000000020000-0x0000007f0000 : "firmware" [ 0.630000] Realtek RTL8366RB ethernet switch driver version 0.2.4 [ 0.750000] rtl8366rb rtl8366rb: using GPIO pins 18 (SDA) and 19 (SCK) [ 0.750000] rtl8366rb rtl8366rb: RTL5937 ver. 3 chip found [ 0.930000] libphy: rtl8366rb: probed [ 0.940000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII [ 1.250000] TCP: cubic registered [ 1.250000] NET: Registered protocol family 17 [ 1.250000] Bridge firewalling registered [ 1.260000] 8021q: 802.1Q VLAN Support v1.8 [ 1.270000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. [ 1.280000] Freeing unused kernel memory: 228k freed [ 3.470000] ar71xx: pll_reg 0xb8050014: 0x1a000000 [ 3.470000] eth0: link up (1000Mbps/Full duplex) [ 6.870000] jffs2: notice: (458) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 18 of xref (0 dead, 8 orphan) found. [ 7.760000] SCSI subsystem initialized [ 7.890000] usbcore: registered new interface driver usbfs [ 7.900000] usbcore: registered new interface driver hub [ 7.910000] usbcore: registered new device driver usb [ 8.520000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 8.530000] ehci-platform: EHCI generic platform driver [ 8.530000] ehci-platform ehci-platform: EHCI Host Controller [ 8.540000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 [ 8.550000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 [ 8.570000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 [ 8.570000] hub 1-0:1.0: USB hub found [ 8.580000] hub 1-0:1.0: 1 port detected [ 8.600000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 8.680000] Initializing USB Mass Storage driver... [ 8.690000] usbcore: registered new interface driver usb-storage [ 8.690000] USB Mass Storage support registered. [ 8.900000] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 9.050000] scsi0 : usb-storage 1-1:1.0 [ 10.060000] scsi 0:0:0:0: Direct-Access Kingston DT 100 G2 PMAP PQ: 0 ANSI: 0 CCS [ 10.070000] sd 0:0:0:0: [sda] 31260672 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 10.080000] sd 0:0:0:0: [sda] Write Protect is off [ 10.090000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 10.090000] sd 0:0:0:0: [sda] No Caching mode page present [ 10.090000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 10.110000] sd 0:0:0:0: [sda] No Caching mode page present [ 10.110000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 10.120000] sda: sda1 sda2 [ 10.130000] sd 0:0:0:0: [sda] No Caching mode page present [ 10.140000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 10.150000] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 29.040000] eth0: link down [ 30.050000] compat-drivers backport release: compat-drivers-2013-03-28-5 [ 30.060000] Backport based on wireless-testing.git master-2013-04-16 [ 30.060000] compat.git: wireless-testing.git [ 30.120000] cfg80211: Calling CRDA to update world regulatory domain [ 30.130000] cfg80211: World regulatory domain updated: [ 30.130000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 30.140000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 30.150000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 30.160000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 30.160000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 30.170000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 30.440000] NET: Registered protocol family 10 [ 31.130000] ath: EEPROM regdomain: 0x0 [ 31.130000] ath: EEPROM indicates default country code should be used [ 31.130000] ath: doing EEPROM country->regdmn map search [ 31.130000] ath: country maps to regdmn code: 0x3a [ 31.130000] ath: Country alpha2 being used: US [ 31.130000] ath: Regpair used: 0x3a [ 31.140000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 31.140000] ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 mem=0xb80c0000, irq=2 [ 31.150000] cfg80211: Calling CRDA for country: US [ 31.160000] cfg80211: Regulatory domain changed to country: US [ 31.160000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 31.170000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 31.180000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 31.190000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.190000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.200000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.210000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 31.390000] PPP generic driver version 2.4.2 [ 31.640000] ip_tables: (C) 2000-2006 Netfilter Core Team [ 31.760000] xt_time: kernel timezone is -0000 [ 31.800000] NET: Registered protocol family 24 [ 31.870000] nf_conntrack version 0.5.0 (452 buckets, 1808 max) [ 32.120000] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 38.400000] ar71xx: pll_reg 0xb8050014: 0x1a000000 [ 38.700000] eth0: link up (1000Mbps/Full duplex) [ 38.720000] device eth0.1 entered promiscuous mode [ 38.720000] device eth0 entered promiscuous mode [ 38.740000] br-lan: port 1(eth0.1) entered forwarding state [ 38.740000] br-lan: port 1(eth0.1) entered forwarding state [ 39.700000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready [ 40.740000] br-lan: port 1(eth0.1) entered forwarding state [ 41.140000] Adding 262140k swap on /dev/sda1. Priority:-1 extents:1 across:262140k [ 45.140000] EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended [ 45.150000] EXT4-fs (sda2): recovery complete [ 45.170000] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 46.210000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 46.270000] device wlan0 entered promiscuous mode [ 46.360000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 46.980000] br-lan: port 2(wlan0) entered forwarding state [ 46.980000] br-lan: port 2(wlan0) entered forwarding state [ 46.990000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 48.980000] br-lan: port 2(wlan0) entered forwarding state [ 50.300000] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready [ 51.350000] br-lan: port 2(wlan0) entered disabled state [ 52.340000] wlan0-1: authenticate with 00:26:44:68:90:67 [ 52.400000] wlan0-1: send auth to 00:26:44:68:90:67 (try 1/3) [ 52.400000] wlan0-1: authenticated [ 52.420000] ath9k ath9k wlan0-1: disabling HT/VHT due to WEP/TKIP use [ 52.420000] ath9k ath9k wlan0-1: disabling HT as WMM/QoS is not supported by the AP [ 52.430000] ath9k ath9k wlan0-1: disabling VHT as WMM/QoS is not supported by the AP [ 52.450000] wlan0-1: associate with 00:26:44:68:90:67 (try 1/3) [ 52.450000] wlan0-1: RX AssocResp from 00:26:44:68:90:67 (capab=0x411 status=0 aid=1) [ 52.460000] wlan0-1: associated [ 52.470000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready [ 53.380000] br-lan: port 2(wlan0) entered forwarding state [ 53.390000] br-lan: port 2(wlan0) entered forwarding state [ 53.390000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 55.390000] br-lan: port 2(wlan0) entered forwarding state [ 57.740000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 124.090000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 141.490000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 229.150000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 524.190000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 582.750000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 663.420000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:389 Changed 5 years ago by anonymous
comment:390 Changed 5 years ago by miguel.arce@…
hello nbd,
reporting:
TL-WR1043ND REV 1.7 : r36952 from june 18.
its the same, some ath errors, router reboots when transmission starts
using heavy traffic, but something that i havent noticed yet is that the CPU use
goes to the roof, so not quite sure now if this reboots are ath9k related or
transmission related... will be testing tomorrow using ethernet for transmission,
and not using wifi at all.
0.000000] Linux version 3.8.13 (openwrt@huchra) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2012.12 r36952) ) #1 Tue Jun 18 02:09:56 PDT 2013 [ 0.000000] MyLoader: sysp=00000000, boardp=00000000, parts=00000000 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU revision is: 00019374 (MIPS 24Kc) [ 0.000000] SoC: Atheros AR9132 rev 2 [ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:5.000MHz [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 02000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x00000000-0x01ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x01ffffff] [ 0.000000] On node 0 totalpages: 8192 [ 0.000000] free_area_init_node: node 0, pgdat 80320a40, node_mem_map 81000000 [ 0.000000] Normal zone: 64 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 8128 pages, LIFO batch:0 [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128 [ 0.000000] Kernel command line: board=TL-WR1043ND console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd [ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes) [ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] __ex_table already sorted, skipping sort [ 0.000000] Writing ErrCtl register=00000000 [ 0.000000] Readback ErrCtl register=00000000 [ 0.000000] Memory: 28720k/32768k available (2306k kernel code, 4048k reserved, 599k data, 228k init, 0k highmem) [ 0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:51 [ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104) [ 0.080000] pid_max: default: 32768 minimum: 301 [ 0.080000] Mount-cache hash table entries: 512 [ 0.090000] NET: Registered protocol family 16 [ 0.100000] MIPS: machine is TP-LINK TL-WR1043ND [ 0.360000] bio: create slab <bio-0> at 0 [ 0.370000] Switching to clocksource MIPS [ 0.380000] NET: Registered protocol family 2 [ 0.380000] TCP established hash table entries: 512 (order: 0, 4096 bytes) [ 0.380000] TCP bind hash table entries: 512 (order: -1, 2048 bytes) [ 0.390000] TCP: Hash tables configured (established 512 bind 512) [ 0.390000] TCP: reno registered [ 0.400000] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.400000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.410000] NET: Registered protocol family 1 [ 0.410000] PCI: CLS 0 bytes, default 32 [ 0.430000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.430000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.450000] msgmni has been set to 56 [ 0.450000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.460000] io scheduler noop registered [ 0.460000] io scheduler deadline registered (default) [ 0.470000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled [ 0.500000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A [ 0.510000] console [ttyS0] enabled, bootconsole disabled [ 0.520000] ath79-spi ath79-spi: master is unqueued, this is deprecated [ 0.530000] m25p80 spi0.0: found s25sl064p, expected m25p80 [ 0.530000] m25p80 spi0.0: s25sl064p (8192 Kbytes) [ 0.540000] 5 tp-link partitions found on MTD device spi0.0 [ 0.540000] Creating 5 MTD partitions on "spi0.0": [ 0.550000] 0x000000000000-0x000000020000 : "u-boot" [ 0.560000] 0x000000020000-0x000000124600 : "kernel" [ 0.560000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only [ 0.580000] 0x000000124600-0x0000007f0000 : "rootfs" [ 0.580000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only [ 0.590000] mtd: partition "rootfs" set to be root filesystem [ 0.600000] mtd: partition "rootfs_data" created automatically, ofs=2E0000, len=510000 [ 0.610000] 0x0000002e0000-0x0000007f0000 : "rootfs_data" [ 0.620000] 0x0000007f0000-0x000000800000 : "art" [ 0.620000] 0x000000020000-0x0000007f0000 : "firmware" [ 0.630000] Realtek RTL8366RB ethernet switch driver version 0.2.4 [ 0.750000] rtl8366rb rtl8366rb: using GPIO pins 18 (SDA) and 19 (SCK) [ 0.750000] rtl8366rb rtl8366rb: RTL5937 ver. 3 chip found [ 0.930000] libphy: rtl8366rb: probed [ 0.940000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII [ 1.250000] TCP: cubic registered [ 1.250000] NET: Registered protocol family 17 [ 1.250000] Bridge firewalling registered [ 1.260000] 8021q: 802.1Q VLAN Support v1.8 [ 1.270000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. [ 1.280000] Freeing unused kernel memory: 228k freed [ 3.480000] ar71xx: pll_reg 0xb8050014: 0x1a000000 [ 3.480000] eth0: link up (1000Mbps/Full duplex) [ 6.890000] jffs2: notice: (458) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 17 of xref (0 dead, 7 orphan) found. [ 7.780000] SCSI subsystem initialized [ 7.910000] usbcore: registered new interface driver usbfs [ 7.910000] usbcore: registered new interface driver hub [ 7.920000] usbcore: registered new device driver usb [ 8.530000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 8.540000] ehci-platform: EHCI generic platform driver [ 8.550000] ehci-platform ehci-platform: EHCI Host Controller [ 8.550000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 [ 8.560000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 [ 8.590000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 [ 8.590000] hub 1-0:1.0: USB hub found [ 8.600000] hub 1-0:1.0: 1 port detected [ 8.620000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 8.690000] Initializing USB Mass Storage driver... [ 8.700000] usbcore: registered new interface driver usb-storage [ 8.700000] USB Mass Storage support registered. [ 8.930000] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 9.080000] scsi0 : usb-storage 1-1:1.0 [ 10.090000] scsi 0:0:0:0: Direct-Access Kingston DT 100 G2 PMAP PQ: 0 ANSI: 0 CCS [ 10.100000] sd 0:0:0:0: [sda] 31260672 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 10.110000] sd 0:0:0:0: [sda] Write Protect is off [ 10.120000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 10.120000] sd 0:0:0:0: [sda] No Caching mode page present [ 10.120000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 10.140000] sd 0:0:0:0: [sda] No Caching mode page present [ 10.140000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 10.150000] sda: sda1 sda2 [ 10.160000] sd 0:0:0:0: [sda] No Caching mode page present [ 10.170000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 10.180000] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 29.060000] eth0: link down [ 30.080000] Loading modules backported from Linux version master-2013-06-13-0-g09fcdfb [ 30.090000] Backport generated by backports.git backports-20130531-13-g3d933eb [ 30.130000] cfg80211: Calling CRDA to update world regulatory domain [ 30.130000] cfg80211: World regulatory domain updated: [ 30.140000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 30.150000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 30.160000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 30.160000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 30.170000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 30.180000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 30.470000] NET: Registered protocol family 10 [ 31.200000] ath: EEPROM regdomain: 0x0 [ 31.200000] ath: EEPROM indicates default country code should be used [ 31.200000] ath: doing EEPROM country->regdmn map search [ 31.200000] ath: country maps to regdmn code: 0x3a [ 31.200000] ath: Country alpha2 being used: US [ 31.200000] ath: Regpair used: 0x3a [ 31.210000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 31.210000] ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 mem=0xb80c0000, irq=2 [ 31.220000] cfg80211: Calling CRDA for country: US [ 31.230000] cfg80211: Regulatory domain changed to country: US [ 31.230000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 31.240000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 31.250000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 31.250000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.260000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.270000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 31.280000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 31.460000] PPP generic driver version 2.4.2 [ 31.720000] ip_tables: (C) 2000-2006 Netfilter Core Team [ 31.840000] xt_time: kernel timezone is -0000 [ 31.880000] NET: Registered protocol family 24 [ 31.950000] nf_conntrack version 0.5.0 (452 buckets, 1808 max) [ 32.200000] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 37.930000] ar71xx: pll_reg 0xb8050014: 0x1a000000 [ 38.230000] eth0: link up (1000Mbps/Full duplex) [ 38.250000] device eth0.1 entered promiscuous mode [ 38.250000] device eth0 entered promiscuous mode [ 38.270000] br-lan: port 1(eth0.1) entered forwarding state [ 38.270000] br-lan: port 1(eth0.1) entered forwarding state [ 38.930000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready [ 40.270000] br-lan: port 1(eth0.1) entered forwarding state [ 42.760000] Adding 262140k swap on /dev/sda1. Priority:-1 extents:1 across:262140k [ 44.890000] EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended [ 44.900000] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 45.380000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 45.400000] device wlan0 entered promiscuous mode [ 45.450000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 46.050000] br-lan: port 2(wlan0) entered forwarding state [ 46.060000] br-lan: port 2(wlan0) entered forwarding state [ 46.060000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 48.060000] br-lan: port 2(wlan0) entered forwarding state [ 49.480000] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready [ 50.490000] br-lan: port 2(wlan0) entered disabled state [ 51.120000] wlan0-1: authenticate with 00:26:44:68:90:67 [ 51.130000] wlan0-1: send auth to 00:26:44:68:90:67 (try 1/3) [ 51.140000] wlan0-1: authenticated [ 51.140000] ath9k ath9k wlan0-1: disabling HT/VHT due to WEP/TKIP use [ 51.150000] ath9k ath9k wlan0-1: disabling HT as WMM/QoS is not supported by the AP [ 51.150000] ath9k ath9k wlan0-1: disabling VHT as WMM/QoS is not supported by the AP [ 51.170000] wlan0-1: associate with 00:26:44:68:90:67 (try 1/3) [ 51.180000] wlan0-1: RX AssocResp from 00:26:44:68:90:67 (capab=0x411 status=0 aid=2) [ 51.190000] wlan0-1: associated [ 51.190000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready [ 52.190000] br-lan: port 2(wlan0) entered forwarding state [ 52.190000] br-lan: port 2(wlan0) entered forwarding state [ 52.200000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 54.190000] br-lan: port 2(wlan0) entered forwarding state [ 108.550000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 136.780000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 197.760000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:391 Changed 5 years ago by nbd
please test the latest trunk update
comment:392 follow-up: ↓ 393 Changed 5 years ago by miguel.arce@…
hi nbd, i saw the important changes in r37105, unfortunatley current snapshot is 37092. as soon as i have the next snapshot i'll be giving it a test. i am also having problems with the new ubox handling the fstab things... so it takes me a bit longer to flash and setup the router for testing. what i can say is that transmission was updated to 2.80, and with this snapshot i tested it and still resets the router, as well as minidlna with high wifi traffic. i'll keep you posted about the new wireless-testing 2013-06-27, best regards.
comment:393 in reply to: ↑ 392 ; follow-up: ↓ 394 Changed 5 years ago by anonymous
Replying to miguel.arce@…:
hi nbd, i saw the important changes in r37105, unfortunatley current snapshot is 37092. as soon as i have the next snapshot i'll be giving it a test. i am also having problems with the new ubox handling the fstab things... so it takes me a bit longer to flash and setup the router for testing. what i can say is that transmission was updated to 2.80, and with this snapshot i tested it and still resets the router, as well as minidlna with high wifi traffic. i'll keep you posted about the new wireless-testing 2013-06-27, best regards.
The reboot has nothing to do with atheros. Transmission is VERY CPU intensive and causes the router to crash when demanding too much from it. When downloading a torrent, the router has to connect to seeders, convert information to data and write it to a hard drive. It is doing that while still serving wifi to all clients, leasing DHCP, DNS ect ect. The CPU can't cope with all this and shuts down.
It's a simple router with embedded hardware, not a NAS..
comment:394 in reply to: ↑ 393 Changed 5 years ago by anonymous
Worked without incident with Backfire 10.03.1, an in fact still does, i just wanted to check out the barrier breaker, and use newer packages. i have tranmission 2.77 running an successfully downloading all sizes of info in another similar router WRT160NL without incident also, even tree or four simultaneous downloads, no reboots.
Replying to anonymous:
Replying to miguel.arce@…:
hi nbd, i saw the important changes in r37105, unfortunatley current snapshot is 37092. as soon as i have the next snapshot i'll be giving it a test. i am also having problems with the new ubox handling the fstab things... so it takes me a bit longer to flash and setup the router for testing. what i can say is that transmission was updated to 2.80, and with this snapshot i tested it and still resets the router, as well as minidlna with high wifi traffic. i'll keep you posted about the new wireless-testing 2013-06-27, best regards.
The reboot has nothing to do with atheros. Transmission is VERY CPU intensive and causes the router to crash when demanding too much from it. When downloading a torrent, the router has to connect to seeders, convert information to data and write it to a hard drive. It is doing that while still serving wifi to all clients, leasing DHCP, DNS ect ect. The CPU can't cope with all this and shuts down.
It's a simple router with embedded hardware, not a NAS..
comment:395 Changed 5 years ago by miguel.arce@…
hey nbd, good morning.
testing r37177 got same results, TX DMA,
it doesn't reboot now, but heartbeat indicates very busy, it stop logging and
responding, but seems to continue transmiting info and answering pings.
best regards.
comment:396 Changed 5 years ago by geadas
hello.
with r37154 in a tp-link 1043ND and doing a "ping -i 0.001 router_ip" after some time i had the error again. but then i saw a lot of very high pings and i remembered other issues i had with this chipset. i changed the channel and since then i've had no more errors. its up for more than 4 days with more than 106 million packets and no issues.
i'll test this setup till the end of this week and i'll let you know if i found any issues.
thank you for your great work!
comment:397 Changed 5 years ago by openwrt@…
Running r37177. I'm seeing DMA errors, but the router seems to carry on running. I'll try putting it back to 20MHz and see if they occur again.
[ 297.830000] cfg80211: Calling CRDA for country: GB [ 297.870000] cfg80211: Regulatory domain changed to country: GB [ 297.870000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 297.880000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 297.890000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 297.890000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 297.900000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 299.910000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 299.930000] device wlan0 entered promiscuous mode [ 299.950000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 300.250000] br-lan: port 2(wlan0) entered forwarding state [ 300.260000] br-lan: port 2(wlan0) entered forwarding state [ 300.260000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 302.260000] br-lan: port 2(wlan0) entered forwarding state [ 954.190000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [ 955.460000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [ 956.740000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [ 1143.170000] device wlan0 left promiscuous mode [ 1143.170000] br-lan: port 2(wlan0) entered disabled state [ 1145.640000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1145.660000] device wlan0 entered promiscuous mode [ 1145.680000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1146.870000] br-lan: port 2(wlan0) entered forwarding state [ 1146.870000] br-lan: port 2(wlan0) entered forwarding state [ 1146.880000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1148.870000] br-lan: port 2(wlan0) entered forwarding state [125240.760000] device wlan0 left promiscuous mode [125240.760000] br-lan: port 2(wlan0) entered disabled state [125280.870000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [125280.890000] device wlan0 entered promiscuous mode [125280.910000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [125282.100000] br-lan: port 2(wlan0) entered forwarding state [125282.100000] br-lan: port 2(wlan0) entered forwarding state [125282.110000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [125284.100000] br-lan: port 2(wlan0) entered forwarding state [125295.960000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [125297.190000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [125298.420000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [125304.180000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [125305.410000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [125306.640000] IPv6: ADDRCONF(NETDEV_UP): tmp.wlan0: link is not ready [163709.900000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [163709.910000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [163717.340000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163734.100000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163735.040000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163736.440000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163736.910000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163737.390000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163739.720000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163753.650000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163759.680000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163765.740000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163772.740000] ath: phy0: Failed to stop TX DMA, queues=0x100! [163773.240000] ath: phy0: Failed to stop TX DMA, queues=0x004! [173394.440000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [173394.450000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [185081.130000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [185081.140000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [202788.990000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [202789.000000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [202795.760000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202796.230000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202800.410000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202801.350000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202804.140000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202805.080000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202805.550000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202806.030000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202806.500000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202807.440000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202810.700000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202814.410000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202815.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202829.720000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202834.600000] ath: phy0: Failed to stop TX DMA, queues=0x004! [202846.420000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202852.920000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202858.950000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202867.300000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202870.090000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202888.170000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202892.820000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202893.290000] ath: phy0: Failed to stop TX DMA, queues=0x100! [202905.810000] ath: phy0: Failed to stop TX DMA, queues=0x100! [289043.020000] device wlan0 left promiscuous mode [289043.020000] br-lan: port 2(wlan0) entered disabled state [289045.290000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [289045.300000] device wlan0 entered promiscuous mode [289045.330000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [289045.750000] br-lan: port 2(wlan0) entered forwarding state [289045.750000] br-lan: port 2(wlan0) entered forwarding state [289045.760000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [289047.750000] br-lan: port 2(wlan0) entered forwarding state
comment:398 Changed 5 years ago by geadas
after more than 4 days station disconnected with "IEEE 802.11: disconnected due to excessive missing ACKs"
maybe this is another issue.
reconnected and testing again.
comment:399 Changed 5 years ago by anonymous
Happened to me:
Router Model TP-Link TL-WR1043N/ND v1
Firmware Version
OpenWrt Attitude Adjustment 12.09 /
LuCI 0.11.1 Release (0.11.1)
Kernel Version3.3.8
With wifi HT mode 20 MHz the router works OK OK, with 40 MHz this bug happens all the time with android phone disconnecting all the time.
HW version is 1.8, purchased in 2011.
comment:400 Changed 5 years ago by anonymous
Is there any progress?
I have read that finaly in kernel 3.11 there should be a fix. So far openwrt 12.09 final should not be released before this bug is fixed because it is a CRITICAL BUG and makes use of 12.09 for all atheros users not usable at all...
comment:401 Changed 5 years ago by jow
a) yes there is progress and as stated multiple times already, there is no "this bug", its a collection of vastly different issues
b) 12.09 final is released already
c) kernel versions are irellevant since we rely on wireless backports which are ahead of any kernel releases
d) this bug does not affect anyone or any atheros router
comment:402 Changed 5 years ago by anonymous
thx for your answer!
a) But the most people which run a 1043nd for example see no really difference... I have had more as 10 of this devices for customers from version 1.0 up to the really newest. Also which really ALL possible tested u-boot/bootloader versions... And the error/or the dma error message is still existent here. And all channels tested and also all router in different enviroments. If there is no much traffic, yes than this error is not here i think (or this message).
b) dont know. it was written that rc1 will be final if there are no critical bugs but than rc2 was released. maybe there will be a rc3 then? the finaly was linked into the rc1 so in reallity it was only rc1. or will rc2 really be the last?
c) Oh, ok,nice to know then. Can you then say it is a kernel or a openwrt problem? Also I tested gargoly, dd wrt and so on. And this wireless drops are also there. that would show us that it has to be a driver/kernel problem, right?
d) Maybe not, but i found it because i googled for this message of error. there are many, many reports all over the web about this problem. the mosts are about 1043nd and atheros devices. also a german site stated that it IS a atheros problem. (they wrote it). In tplink forum there said also that i migh be a hardware fault. But i cant believe it.
there have to be any way to show WHAT IS THE PROBLEM, right? For my example what it could be?neither hardware version, software version, enviroument, channel or something. all different, still same error... maybe because txpower is about 20dbm? have anyone tested this? I have this routers several years and the problem was there all the time and never changed/fixed. yes it is something better but the messages and so on are all existing anymore...
On this router I have newest u-boot version from latest firmware and revision 1.8 of 1043nd atheros device. had one laptop connected and in ONE NIGHT at morning there was:
[22267.070000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[22267.080000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[22297.930000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[22297.940000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Like on all others too. had this bug on every 12.09 version. It is really sad that no one can change or fix this/or this message or what ever it is... I am really happy that you and others are working on openwrt and it is really nice but it is really frustrating with this error. Also on the most other tp link devives like wnr4300 or so there is this error. also on buffalo atheros routers and so on... Never seen this on others as atheros. But some people had it also on their atheros mimo wlan cards. that woukd show that it is a driver problem... or finally a hardware fault... then never will be a/some fixes.
comment:403 Changed 5 years ago by nbd
It sounds like I should probably remove the messages soon.
It seems to me that too many people spot them in their log and instantly switch off the logical parts of their brain and go into panic mode, and start complaining about serious issues, when in fact often the messages are the only symptoms and wifi is working mostly fine.
By the way, 12.09 branch recently got another big wifi driver backport from trunk, and there's more work being tested in trunk which might make it to the release as well if the test feedback continues to be good.
As for 1043ND - take a look at what one guy wrote in a related ticket: https://dev.openwrt.org/ticket/11862#comment:105
comment:404 Changed 5 years ago by anonymous
No, also if this messages appears my traffic goes really down and the down and upload is low until I reboot the router or reboot wifi device.
But that would be awesome if the comment which you have linked is true and it will be in rc3 then maybe? Than I hope all will be good :-)
Thanks for your feedback. And no, i use my brain but I have noticed this so often in connection with wifi slowdown and so on. and this was also on other opensource firmwares the fact.
Normaly it should be equal on all revisions of 1043nd, because the hardware is all the same right? and u-boot version are also not important? (except the wan problem some time ago) How long could it be until this fixes from trunk go to 12.09 then?
comment:405 Changed 5 years ago by anonymous
Have read different comments from you in the other ticket and understand fully what you mean now. I will look if I get a other 1043nd only for testing the newest possible versions to help to sort out the problems. would be than trunk version, right?
comment:406 Changed 5 years ago by anonymous
This bug is definitely OpenWRT related. My TP-Link 1043ND v 1.6 works just fine with original TP-Link firware, but I had all sort of issues with poor wi-fi performance while running OpenWRT on it. I waited for over a year and tried all trunk releases with no luck. I finally gave up about six months ago and I´m very happy with original firmware. I still miss the flexibility of OpenWRT but since TPlink implemmented network printing on original firware I can live with it.
Good luck to all. BTW, how do I unsubscribe to this ticket? I still get every and all messages posted here.
comment:407 Changed 5 years ago by anonymous
Hm looks like that it is not only a definitely OpenWRT Bug. Read what nbd answered to me and see tickets. I can prof that is not OpenWRT fault with the fact (see above comments) there are also people with the same problem under other opensource router firmwares. Also under linux itself at a desktop pc. It looks that it is a ath9k driver issue. And looks like nbd is working for them to get this bunch of errors which results often in this messages is fixing. Maybe you should test openwrt with 12.09-rc3 again? Also look for your bootloader and maybe try an other? Dont know. But nbd wrote:
As for 1043ND - take a look at what one guy wrote in a related ticket: https://dev.openwrt.org/ticket/11862#comment:105
And if that is really true that could fix your issues and my issues too. :)
comment:408 Changed 5 years ago by anonymous
Didn´t find any usefull comment on the thread you pointed to. Just guys complainning about hangs just like everyone else here on this ticket. By the way, I´m sure MY 1043ND hardware is not broken. As I said before, it has been working just fine for a few months running original TPLink firmware. It is also based on Linux and its sources are available, so I really do not understand why OpenWRT and other open source firmwares don´t backport wifi driver from it and fix this problem.
Besides grat stability I also noticed HUGE improvements on transfer speeds when using TPLink original firmware.
comment:409 Changed 5 years ago by geadas
hello.
tp-link 1043ND
1 client (debian with intel wifi chipset)
test
"ping -i 0.001 router_ip"
uptime
01:33:44 up 6 days, 9:32, load average: 0.01, 0.03, 0.04
dmesg
[ 0.000000] Linux version 3.8.13 (openwrt@snapon) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2012.12 r37154) ) #1 Thu Jul 4 03:27:09 PDT 2013
[ 0.000000] MyLoader: sysp=00000000, boardp=00000000, parts=00020000
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 00019374 (MIPS 24Kc)
[ 0.000000] SoC: Atheros AR9132 rev 2
[ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:5.000MHz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x01ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x01ffffff]
[ 0.000000] On node 0 totalpages: 8192
[ 0.000000] free_area_init_node: node 0, pgdat 80320a40, node_mem_map 81000000
[ 0.000000] Normal zone: 64 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 8128 pages, LIFO batch:0
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
[ 0.000000] Kernel command line: board=TL-WR1043ND console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] ex_table already sorted, skipping sort
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 28720k/32768k available (2306k kernel code, 4048k reserved, 599k data, 228k init, 0k highmem)
[ 0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[ 0.080000] pid_max: default: 32768 minimum: 301
[ 0.080000] Mount-cache hash table entries: 512
[ 0.090000] NET: Registered protocol family 16
[ 0.100000] MIPS: machine is TP-LINK TL-WR1043ND
[ 0.360000] bio: create slab <bio-0> at 0
[ 0.370000] Switching to clocksource MIPS
[ 0.380000] NET: Registered protocol family 2
[ 0.380000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.380000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[ 0.390000] TCP: Hash tables configured (established 512 bind 512)
[ 0.390000] TCP: reno registered
[ 0.400000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.400000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.410000] NET: Registered protocol family 1
[ 0.410000] PCI: CLS 0 bytes, default 32
[ 0.430000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.430000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.450000] msgmni has been set to 56
[ 0.450000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 0.460000] io scheduler noop registered
[ 0.460000] io scheduler deadline registered (default)
[ 0.470000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.500000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
[ 0.510000] console [ttyS0] enabled, bootconsole disabled
[ 0.520000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[ 0.530000] m25p80 spi0.0: found s25sl064p, expected m25p80
[ 0.530000] m25p80 spi0.0: s25sl064p (8192 Kbytes)
[ 0.540000] 5 tp-link partitions found on MTD device spi0.0
[ 0.540000] Creating 5 MTD partitions on "spi0.0":
[ 0.550000] 0x000000000000-0x000000020000 : "u-boot"
[ 0.560000] 0x000000020000-0x000000124600 : "kernel"
[ 0.560000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.580000] 0x000000124600-0x0000007f0000 : "rootfs"
[ 0.580000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.590000] mtd: partition "rootfs" set to be root filesystem
[ 0.600000] mtd: partition "rootfs_data" created automatically, ofs=410000, len=3E0000
[ 0.610000] 0x000000410000-0x0000007f0000 : "rootfs_data"
[ 0.620000] 0x0000007f0000-0x000000800000 : "art"
[ 0.620000] 0x000000020000-0x0000007f0000 : "firmware"
[ 0.630000] Realtek RTL8366RB ethernet switch driver version 0.2.4
[ 0.750000] rtl8366rb rtl8366rb: using GPIO pins 18 (SDA) and 19 (SCK)
[ 0.750000] rtl8366rb rtl8366rb: RTL5937 ver. 3 chip found
[ 0.930000] libphy: rtl8366rb: probed
[ 0.940000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
[ 1.250000] TCP: cubic registered
[ 1.250000] NET: Registered protocol family 17
[ 1.250000] Bridge firewalling registered
[ 1.260000] 8021q: 802.1Q VLAN Support v1.8
[ 1.270000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[ 1.280000] Freeing unused kernel memory: 228k freed
[ 3.350000] usbcore: registered new interface driver usbfs
[ 3.360000] usbcore: registered new interface driver hub
[ 3.370000] usbcore: registered new device driver usb
[ 3.480000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.480000] ehci-platform: EHCI generic platform driver
[ 3.490000] ehci-platform ehci-platform: EHCI Host Controller
[ 3.490000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[ 3.500000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[ 3.530000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[ 3.530000] hub 1-0:1.0: USB hub found
[ 3.540000] hub 1-0:1.0: 1 port detected
[ 3.820000] ar71xx: pll_reg 0xb8050014: 0x1a000000
[ 3.820000] eth0: link up (1000Mbps/Full duplex)
[ 4.010000] jffs2: notice: (311) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (0 unchecked, 0 orphan) and 11 of xref (0 dead, 0 orphan) found.
[ 4.040000] eth0: link down
[ 6.220000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
[ 6.230000] Backport generated by backports.git backports-20130617-4-ge3220f5
[ 6.260000] cfg80211: Calling CRDA to update world regulatory domain
[ 6.260000] cfg80211: World regulatory domain updated:
[ 6.270000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 6.280000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 6.290000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 6.290000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 6.300000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 6.310000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 7.020000] ath: EEPROM regdomain: 0x0
[ 7.020000] ath: EEPROM indicates default country code should be used
[ 7.020000] ath: doing EEPROM country->regdmn map search
[ 7.020000] ath: country maps to regdmn code: 0x3a
[ 7.020000] ath: Country alpha2 being used: US
[ 7.020000] ath: Regpair used: 0x3a
[ 7.030000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 7.040000] ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 mem=0xb80c0000, irq=2
[ 7.050000] cfg80211: Calling CRDA for country: US
[ 7.050000] cfg80211: Regulatory domain changed to country: US
[ 7.060000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 7.070000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 7.080000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 7.080000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 7.090000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 7.100000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 7.110000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 7.240000] tun: Universal TUN/TAP device driver, 1.6
[ 7.240000] tun: (C) 1999-2004 Max Krasnyansky <maxk@…>
[ 7.400000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 7.440000] xt_time: kernel timezone is -0000
[ 7.470000] nf_conntrack version 0.5.0 (452 buckets, 1808 max)
[ 10.950000] ar71xx: pll_reg 0xb8050014: 0x1a000000
[ 11.250000] eth0: link up (1000Mbps/Full duplex)
[ 11.250000] device eth0.1 entered promiscuous mode
[ 11.260000] device eth0 entered promiscuous mode
[ 11.270000] br-lan_vpn: port 1(eth0.1) entered forwarding state
[ 11.270000] br-lan_vpn: port 1(eth0.1) entered forwarding state
[ 13.270000] br-lan_vpn: port 1(eth0.1) entered forwarding state
[ 16.400000] cfg80211: Calling CRDA for country: BW
[ 18.840000] device wlan0 entered promiscuous mode
[ 19.150000] br-lan_vpn: port 2(wlan0) entered forwarding state
[ 19.150000] br-lan_vpn: port 2(wlan0) entered forwarding state
[ 19.580000] cfg80211: Calling CRDA to update world regulatory domain
[ 19.580000] cfg80211: World regulatory domain updated:
[ 19.590000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 19.600000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.610000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 19.610000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 19.620000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.630000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.640000] cfg80211: Calling CRDA for country: BW
[ 21.150000] br-lan_vpn: port 2(wlan0) entered forwarding state
[ 22.810000] cfg80211: Calling CRDA to update world regulatory domain
[ 22.820000] cfg80211: World regulatory domain updated:
[ 22.820000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 22.830000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 22.840000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 22.850000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 22.850000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 22.860000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cat /proc/net/nf_conntrack|grep icmp
ipv4 2 icmp 1 29 src=client_ip dst=router_ip type=8 code=0 id=8817 packets=177014235 bytes=14869195740 src=router_ip dst=client_ip type=0 code=0 id=8817 packets=177014227 bytes=14869195068 mark=0 use=2
thats it. more than 6 days and more than 177 million packets and still no issues.
i'll keep you update.
comment:410 Changed 5 years ago by valent.turkovic@…
Guys please don't spam this bug ticket with too long logs, use attachment for log logs, dammit!
With latest trunk r37528 I don't see DMA issues, but one laptop in my home doesn't like openwrt on wr1043nd no matter what I do! It just goes beserk whenever it is connected to it, if I use openwrt on tplink wr841nd or Siemens SX763 it works ok, but on this router it has pings upto 1500ms and around 15% drop packets when in the same room as wr1043nd router!
Other machines have normal pings 1-2ms and no dropped packages. Has anybody seen something like this?
comment:411 Changed 5 years ago by anonymous
info : I have the issue on D-Link DIR-825 too (Atheros AR7161), running AA 12.09 final
comment:412 Changed 5 years ago by miguel.arce@…
running r37560 on 1043ND 1.7:
I followed some advice on this ticket, changed a bit the testing setup i have been using, specially using 20 mhz channels.
Still shows TX DMA messages, althought wifi seems more stable with 20 mhz channels.
testing case 1: using 20 Mhz channels, the router actually gets to last longer downloading and transfering files, minidlna with wifi as br-lan, even with frecuent TX DMA messages, it seems to have no impact on the traffic or getting the router rebooted, using only wifi as br-lan (1 network).
testing case 2: disabled wifi as br-lan, using it only as client for wireless torrent downloader, using 20 mhz channels. the router works fine for about 2 hours, it downloads multiple torrents fine until all of the sudden traffic stops, and the wifi start failing and ultimately rebots. (still lots of tx dma messages)
testing case 3: using 40 mhz channels with multiple ssid, wifi as br-lan, minidlna reboots the device, also transfer of files to and from the router (same files as with 20 mhz channels), and same goes for testing case 2 with 40 mhz channels.
testing case 4: using 40 mhz channels with wifi only as client for wireless downloader, router reboots after shor 10 - 12 minutes.
testing case 5: using it as a downloader (transmission + ethernet) works wihout incident (no wifi involved).
still waiting for my serial adapter.
best regards.
comment:413 Changed 5 years ago by miguel.arce@…
here is the last thing the router said in the serial console before a halt.
[ 343.330000] udhcpc invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 343.340000] CPU: 0 PID: 815 Comm: udhcpc Not tainted 3.10.3 #1
[ 343.340000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000032
81b4f818 802d2c80 80372a0c 803233db 0000032f 000201da 00000000 00000000
803234b0 800793ac 50808400 80076dec 00000000 00000000 802d457c 808c5b84
008c5b84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 808c5b10
...
[ 343.380000] Call Trace:
[ 343.380000] [<8006df68>] show_stack+0x48/0x70
[ 343.380000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 343.390000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 343.400000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 343.400000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 343.410000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 343.410000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 343.420000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 343.420000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 343.430000] [<80071c74>] do_page_fault+0x110/0x354
[ 343.430000] [<80060820>] ret_from_exception+0x0/0xc
[ 343.440000]
[ 343.440000] Mem-Info:
[ 343.440000] Normal per-cpu:
[ 343.440000] CPU 0: hi: 0, btch: 1 usd: 0
[ 343.450000] active_anon:0 inactive_anon:2 isolated_anon:0
[ 343.450000] active_file:11 inactive_file:11 isolated_file:0
[ 343.450000] unevictable:0 dirty:0 writeback:0 unstable:0
[ 343.450000] free:231 slab_reclaimable:339 slab_unreclaimable:1437
[ 343.450000] mapped:1 shmem:0 pagetables:83 bounce:0
[ 343.450000] free_cma:0
[ 343.480000] Normal free:924kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:8kB active_file:44kB inactive_file:44kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:1356kB slab_unreclaimable:5748kB kernel_stack:384kB pagetables:332kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:144 all_unreclaimable? yes
[ 343.520000] lowmem_reserve[]: 0 0
[ 343.520000] Normal: 83*4kB (EMR) 65*8kB (EMR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 916kB
[ 343.530000] 24 total pagecache pages
[ 343.540000] 2 pages in swap cache
[ 343.540000] Swap cache stats: add 9815, delete 9813, find 2822/4038
[ 343.550000] Free swap = 253056kB
[ 343.550000] Total swap = 262140kB
[ 343.560000] 8192 pages RAM
[ 343.560000] 959 pages reserved
[ 343.560000] 78118 pages shared
[ 343.570000] 3960 pages non-shared
[ 343.570000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 343.580000] [ 497] 0 497 227 0 4 22 0 ubusd
[ 343.580000] [ 498] 0 498 192 0 3 14 0 askfirst
[ 343.590000] [ 726] 0 726 374 1 5 49 0 netifd
[ 343.600000] [ 815] 0 815 374 0 4 18 0 udhcpc
[ 343.610000] [ 1031] 0 1031 204 1 3 18 0 6relayd
[ 343.620000] [ 1113] 0 1113 371 0 3 14 0 sleep
[ 343.630000] [ 1250] 0 1250 371 0 3 14 0 sleep
[ 343.630000] [ 1378] 0 1378 423 0 4 43 0 hostapd
[ 343.640000] [ 1425] 0 1425 407 0 4 28 0 wpa_supplicant
[ 343.650000] [ 1453] 0 1453 376 0 4 20 0 udhcpc
[ 343.660000] [ 1476] 0 1476 289 0 3 18 0 dropbear
[ 343.670000] [ 1501] 0 1501 286 0 4 19 0 uhttpd
[ 343.680000] [ 1539] 65534 1539 239 0 4 22 0 dnsmasq
[ 343.680000] [ 1586] 0 1586 394 0 4 39 0 dynamic_dns_upd
[ 343.690000] [ 1661] 0 1661 374 0 4 18 0 ntpd
[ 343.700000] [ 1727] 0 1727 371 0 3 14 0 sleep
[ 343.710000] [ 1728] 0 1728 300 0 3 31 0 dropbear
[ 343.720000] [ 1729] 0 1729 377 1 5 22 0 ash
[ 343.720000] [ 1926] 0 1926 4183 0 8 1709 0 transmission-da
[ 343.730000] [ 1930] 0 1930 352 0 4 53 0 htop
[ 343.740000] Out of memory: Kill process 1539 (dnsmasq) score 0 or sacrifice child
[ 343.750000] Killed process 1539 (dnsmasq) total-vm:956kB, anon-rss:0kB, file-rss:0kB
[ 351.340000] ath: phy0: Failed to stop TX DMA, queues=0x004!
now that i have a serial console, is there any tips for gathering helpfull debug information?
comment:414 Changed 5 years ago by miguel.arce@…
this is r37560
here is another log, this time it wasnt a halt, it was a full reboot, but more info got logged to the serial console.
[ 435.010000] dropbear invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0
[ 435.020000] CPU: 0 PID: 1729 Comm: dropbear Not tainted 3.10.3 #1
[ 435.020000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000035
81bcdac8 802d2c80 80372a0c 803233db 000006c1 000200da 00000000 00000000
803234b0 800793ac 50808400 80076dec 00000000 00000000 802d457c 80c3f964
00c3f964 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80c3f8f0
...
[ 435.060000] Call Trace:
[ 435.060000] [<8006df68>] show_stack+0x48/0x70
[ 435.070000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 435.070000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 435.080000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 435.080000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 435.090000] [<800dc688>] read_swap_cache_async+0x84/0x19c
[ 435.090000] [<800dc828>] swapin_readahead+0x88/0xf4
[ 435.100000] [<800d1478>] handle_pte_fault+0x36c/0x6dc
[ 435.100000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 435.110000] [<80071c74>] do_page_fault+0x110/0x354
[ 435.110000] [<80060820>] ret_from_exception+0x0/0xc
[ 435.120000] [<800644d8>] __copy_user_common+0xd0/0x2b8
[ 435.120000] [<800f581c>] core_sys_select+0x230/0x2c0
[ 435.130000] [<800f596c>] SyS_select+0xc0/0xfc
[ 435.130000] [<80062544>] stack_done+0x20/0x40
[ 435.140000]
[ 435.140000] Mem-Info:
[ 435.140000] Normal per-cpu:
[ 435.140000] CPU 0: hi: 0, btch: 1 usd: 0
[ 435.150000] active_anon:0 inactive_anon:0 isolated_anon:0
[ 435.150000] active_file:5 inactive_file:51 isolated_file:0
[ 435.150000] unevictable:0 dirty:0 writeback:0 unstable:0
[ 435.150000] free:156 slab_reclaimable:322 slab_unreclaimable:1492
[ 435.150000] mapped:1 shmem:0 pagetables:80 bounce:0
[ 435.150000] free_cma:0
[ 435.180000] Normal free:608kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:0kB active_file:20kB inactive_file:204kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5968kB kernel_stack:376kB pagetables:320kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:90 all_unreclaimable? yes
[ 435.220000] lowmem_reserve[]: 0 0
[ 435.220000] Normal: 18*4kB (UMR) 47*8kB (UR) 8*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 608kB
[ 435.240000] 67 total pagecache pages
[ 435.240000] 0 pages in swap cache
[ 435.240000] Swap cache stats: add 7773, delete 7773, find 2974/3627
[ 435.250000] Free swap = 253664kB
[ 435.250000] Total swap = 262140kB
[ 435.260000] 8192 pages RAM
[ 435.260000] 959 pages reserved
[ 435.260000] 143300 pages shared
[ 435.270000] 3994 pages non-shared
[ 435.270000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 435.280000] [ 492] 0 492 227 0 4 22 0 ubusd
[ 435.290000] [ 493] 0 493 192 0 3 13 0 askfirst
[ 435.290000] [ 727] 0 727 374 1 4 49 0 netifd
[ 435.300000] [ 812] 0 812 374 0 4 18 0 udhcpc
[ 435.310000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 435.320000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 435.330000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 435.330000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 435.340000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 435.350000] [ 1454] 0 1454 376 0 4 20 0 udhcpc
[ 435.360000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 435.370000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 435.380000] [ 1535] 65534 1535 239 0 3 22 0 dnsmasq
[ 435.380000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 435.390000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 435.400000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 435.410000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 435.420000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 435.430000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 435.430000] Out of memory: Kill process 1535 (dnsmasq) score 0 or sacrifice child
[ 435.440000] Killed process 1535 (dnsmasq) total-vm:956kB, anon-rss:0kB, file-rss:0kB
[ 439.360000] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 439.360000] CPU: 0 PID: 1618 Comm: ntpd Not tainted 3.10.3 #1
[ 439.370000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000031
81bcc1a8 802d2c80 80372a0c 803233db 00000652 000201da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d457c 80ddbb84
00ddbb84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80ddbb10
...
[ 439.410000] Call Trace:
[ 439.410000] [<8006df68>] show_stack+0x48/0x70
[ 439.410000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 439.420000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 439.420000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 439.430000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 439.430000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 439.440000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 439.440000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 439.450000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 439.450000] [<80071c74>] do_page_fault+0x110/0x354
[ 439.460000] [<80060820>] ret_from_exception+0x0/0xc
[ 439.460000]
[ 439.460000] Mem-Info:
[ 439.470000] Normal per-cpu:
[ 439.470000] CPU 0: hi: 0, btch: 1 usd: 0
[ 439.470000] active_anon:0 inactive_anon:2 isolated_anon:0
[ 439.470000] active_file:6 inactive_file:10 isolated_file:0
[ 439.470000] unevictable:0 dirty:0 writeback:2 unstable:0
[ 439.470000] free:156 slab_reclaimable:322 slab_unreclaimable:1492
[ 439.470000] mapped:1 shmem:0 pagetables:77 bounce:0
[ 439.470000] free_cma:0
[ 439.500000] Normal free:624kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:8kB active_file:24kB inactive_file:40kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:8kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5968kB kernel_stack:376kB pagetables:308kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
[ 439.540000] lowmem_reserve[]: 0 0
[ 439.550000] Normal: 34*4kB (UMR) 53*8kB (UMR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 624kB
[ 439.560000] 18 total pagecache pages
[ 439.560000] 2 pages in swap cache
[ 439.570000] Swap cache stats: add 7833, delete 7831, find 2992/3656
[ 439.570000] Free swap = 253752kB
[ 439.580000] Total swap = 262140kB
[ 439.580000] 8192 pages RAM
[ 439.580000] 959 pages reserved
[ 439.590000] 274231 pages shared
[ 439.590000] 3981 pages non-shared
[ 439.590000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 439.600000] [ 492] 0 492 227 0 4 22 0 ubusd
[ 439.610000] [ 493] 0 493 192 0 3 13 0 askfirst
[ 439.620000] [ 727] 0 727 374 1 4 49 0 netifd
[ 439.630000] [ 812] 0 812 374 0 4 18 0 udhcpc
[ 439.640000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 439.640000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 439.650000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 439.660000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 439.670000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 439.680000] [ 1454] 0 1454 376 0 4 20 0 udhcpc
[ 439.690000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 439.690000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 439.700000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 439.710000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 439.720000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 439.730000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 439.740000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 439.740000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 439.750000] Out of memory: Kill process 492 (ubusd) score 0 or sacrifice child
[ 439.760000] Killed process 492 (ubusd) total-vm:908kB, anon-rss:0kB, file-rss:0kB
[ 439.800000] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 439.800000] CPU: 0 PID: 1618 Comm: ntpd Not tainted 3.10.3 #1
[ 439.810000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000031
81bcc1a8 802d2c80 80372a0c 803233db 00000652 000201da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d457c 80ddbb84
00ddbb84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80ddbb10
...
[ 439.840000] Call Trace:
[ 439.850000] [<8006df68>] show_stack+0x48/0x70
[ 439.850000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 439.860000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 439.860000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 439.870000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 439.870000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 439.880000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 439.880000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 439.890000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 439.890000] [<80071c74>] do_page_fault+0x110/0x354
[ 439.900000] [<80060820>] ret_from_exception+0x0/0xc
[ 439.900000]
[ 439.900000] Mem-Info:
[ 439.910000] Normal per-cpu:
[ 439.910000] CPU 0: hi: 0, btch: 1 usd: 0
[ 439.910000] active_anon:0 inactive_anon:2 isolated_anon:0
[ 439.910000] active_file:6 inactive_file:10 isolated_file:0
[ 439.910000] unevictable:0 dirty:0 writeback:2 unstable:0
[ 439.910000] free:150 slab_reclaimable:322 slab_unreclaimable:1493
[ 439.910000] mapped:1 shmem:0 pagetables:73 bounce:0
[ 439.910000] free_cma:0
[ 439.940000] Normal free:592kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:8kB active_file:24kB inactive_file:40kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:8kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5972kB kernel_stack:376kB pagetables:292kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:1066 all_unreclaimable? yes
[ 439.980000] lowmem_reserve[]: 0 0
[ 439.990000] Normal: 36*4kB (UMR) 47*8kB (UMR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 584kB
[ 440.000000] 18 total pagecache pages
[ 440.000000] 2 pages in swap cache
[ 440.010000] Swap cache stats: add 7833, delete 7831, find 2992/3656
[ 440.010000] Free swap = 253840kB
[ 440.020000] Total swap = 262140kB
[ 440.020000] 8192 pages RAM
[ 440.020000] 959 pages reserved
[ 440.030000] 77643 pages shared
[ 440.030000] 3985 pages non-shared
[ 440.030000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 440.040000] [ 493] 0 493 192 0 3 13 0 askfirst
[ 440.050000] [ 727] 0 727 374 1 4 49 0 netifd
[ 440.060000] [ 812] 0 812 374 0 4 18 0 udhcpc
[ 440.070000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 440.070000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 440.080000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 440.090000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 440.100000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 440.110000] [ 1454] 0 1454 376 0 4 20 0 udhcpc
[ 440.120000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 440.120000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 440.130000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 440.140000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 440.150000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 440.160000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 440.170000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 440.170000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 440.180000] Out of memory: Kill process 493 (askfirst) score 0 or sacrifice child
[ 440.190000] Killed process 493 (askfirst) total-vm:768kB, anon-rss:0kB, file-rss:0kB
[ 440.230000] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 440.230000] CPU: 0 PID: 1618 Comm: ntpd Not tainted 3.10.3 #1
[ 440.240000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000031
81bcc1a8 802d2c80 80372a0c 803233db 00000652 000201da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d457c 80ddbb84
00ddbb84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80ddbb10
...
[ 440.280000] Call Trace:
[ 440.280000] [<8006df68>] show_stack+0x48/0x70
[ 440.280000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 440.290000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 440.290000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 440.300000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 440.300000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 440.310000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 440.310000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 440.320000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 440.320000] [<80071c74>] do_page_fault+0x110/0x354
[ 440.330000] [<80060820>] ret_from_exception+0x0/0xc
[ 440.330000]
[ 440.330000] Mem-Info:
[ 440.340000] Normal per-cpu:
[ 440.340000] CPU 0: hi: 0, btch: 1 usd: 0
[ 440.340000] active_anon:0 inactive_anon:2 isolated_anon:0
[ 440.340000] active_file:6 inactive_file:10 isolated_file:0
[ 440.340000] unevictable:0 dirty:0 writeback:2 unstable:0
[ 440.340000] free:146 slab_reclaimable:322 slab_unreclaimable:1493
[ 440.340000] mapped:1 shmem:0 pagetables:70 bounce:0
[ 440.340000] free_cma:0
[ 440.370000] Normal free:584kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:8kB active_file:24kB inactive_file:40kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:8kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5972kB kernel_stack:376kB pagetables:280kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:1796 all_unreclaimable? yes
[ 440.410000] lowmem_reserve[]: 0 0
[ 440.420000] Normal: 36*4kB (UMR) 47*8kB (UMR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 584kB
[ 440.430000] 18 total pagecache pages
[ 440.430000] 2 pages in swap cache
[ 440.440000] Swap cache stats: add 7833, delete 7831, find 2992/3656
[ 440.440000] Free swap = 253892kB
[ 440.450000] Total swap = 262140kB
[ 440.450000] 8192 pages RAM
[ 440.460000] 959 pages reserved
[ 440.460000] 143147 pages shared
[ 440.460000] 3981 pages non-shared
[ 440.460000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 440.470000] [ 727] 0 727 374 1 4 49 0 netifd
[ 440.480000] [ 812] 0 812 374 0 4 18 0 udhcpc
[ 440.490000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 440.500000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 440.510000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 440.510000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 440.520000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 440.530000] [ 1454] 0 1454 376 0 4 20 0 udhcpc
[ 440.540000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 440.550000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 440.550000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 440.560000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 440.570000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 440.580000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 440.590000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 440.600000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 440.600000] Out of memory: Kill process 727 (netifd) score 0 or sacrifice child
[ 440.610000] Killed process 812 (udhcpc) total-vm:1496kB, anon-rss:0kB, file-rss:0kB
[ 440.620000] udhcpc: page allocation failure: order:0, mode:0x2005a
[ 440.630000] CPU: 0 PID: 812 Comm: udhcpc Not tainted 3.10.3 #1
[ 440.630000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000032
81509268 802d2c80 80372a0c 803233db 0000032c 00000001 00000002 00000000
00000040 800793ac 50808000 80076dec 00000000 00000000 802d457c 80b03b14
00b03b14 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80b03aa0
...
[ 440.670000] Call Trace:
[ 440.670000] [<8006df68>] show_stack+0x48/0x70
[ 440.680000] [<800ba5e0>] warn_alloc_failed+0x108/0x12c
[ 440.680000] [<800bca64>] __alloc_pages_nodemask+0x5dc/0x63c
[ 440.690000] [<800b6a40>] grab_cache_page_nowait+0x7c/0xc8
[ 440.690000] [<80138de0>] squashfs_readpage+0x600/0x7b8
[ 440.700000] [<800bf748>] __do_page_cache_readahead+0x1b8/0x234
[ 440.710000] [<800bfacc>] ra_submit+0x28/0x34
[ 440.710000] [<800b83f8>] filemap_fault+0x198/0x3e8
[ 440.720000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 440.720000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 440.720000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 440.730000] [<80071c74>] do_page_fault+0x110/0x354
[ 440.730000] [<80060820>] ret_from_exception+0x0/0xc
[ 440.740000]
[ 440.740000] Mem-Info:
[ 440.740000] Normal per-cpu:
[ 440.750000] CPU 0: hi: 0, btch: 1 usd: 0
[ 440.750000] active_anon:0 inactive_anon:2 isolated_anon:0
[ 440.750000] active_file:6 inactive_file:10 isolated_file:0
[ 440.750000] unevictable:0 dirty:0 writeback:2 unstable:0
[ 440.750000] free:140 slab_reclaimable:322 slab_unreclaimable:1493
[ 440.750000] mapped:1 shmem:0 pagetables:70 bounce:0
[ 440.750000] free_cma:0
[ 440.780000] Normal free:560kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:8kB active_file:24kB inactive_file:40kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:8kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5972kB kernel_stack:376kB pagetables:280kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:117 all_unreclaimable? yes
[ 440.820000] lowmem_reserve[]: 0 0
[ 440.830000] Normal: 36*4kB (UMR) 43*8kB (UMR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 552kB
[ 440.840000] 18 total pagecache pages
[ 440.840000] 2 pages in swap cache
[ 440.850000] Swap cache stats: add 7833, delete 7831, find 2992/3656
[ 440.850000] Free swap = 253892kB
[ 440.850000] Total swap = 262140kB
[ 440.860000] 8192 pages RAM
[ 440.860000] 959 pages reserved
[ 440.870000] 77605 pages shared
[ 440.870000] 3989 pages non-shared
[ 441.270000] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 441.270000] CPU: 0 PID: 1618 Comm: ntpd Not tainted 3.10.3 #1
[ 441.280000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000031
81bcc1a8 802d2c80 80372a0c 803233db 00000652 000201da 00000000 00000000
803234b0 800793ac 80330000 80076dec 00000000 00000000 802d457c 80ddbb84
00ddbb84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80ddbb10
...
[ 441.310000] Call Trace:
[ 441.320000] [<8006df68>] show_stack+0x48/0x70
[ 441.320000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 441.330000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 441.330000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 441.340000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 441.340000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 441.350000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 441.350000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 441.360000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 441.360000] [<80071c74>] do_page_fault+0x110/0x354
[ 441.370000] [<80060820>] ret_from_exception+0x0/0xc
[ 441.370000]
[ 441.370000] Mem-Info:
[ 441.380000] Normal per-cpu:
[ 441.380000] CPU 0: hi: 0, btch: 1 usd: 0
[ 441.380000] active_anon:0 inactive_anon:0 isolated_anon:0
[ 441.380000] active_file:6 inactive_file:9 isolated_file:0
[ 441.380000] unevictable:0 dirty:0 writeback:0 unstable:0
[ 441.380000] free:149 slab_reclaimable:322 slab_unreclaimable:1493
[ 441.380000] mapped:1 shmem:0 pagetables:66 bounce:0
[ 441.380000] free_cma:0
[ 441.410000] Normal free:596kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:0kB active_file:24kB inactive_file:36kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5972kB kernel_stack:376kB pagetables:264kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:18288 all_unreclaimable? yes
[ 441.450000] lowmem_reserve[]: 0 0
[ 441.460000] Normal: 43*4kB (UMR) 44*8kB (UMR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 588kB
[ 441.470000] 15 total pagecache pages
[ 441.470000] 0 pages in swap cache
[ 441.480000] Swap cache stats: add 7833, delete 7833, find 2992/3656
[ 441.480000] Free swap = 253964kB
[ 441.490000] Total swap = 262140kB
[ 441.490000] 8192 pages RAM
[ 441.490000] 959 pages reserved
[ 441.500000] 77570 pages shared
[ 441.500000] 3961 pages non-shared
[ 441.500000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 441.510000] [ 727] 0 727 374 1 4 49 0 netifd
[ 441.520000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 441.530000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 441.540000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 441.540000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 441.550000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 441.560000] [ 1454] 0 1454 376 0 4 20 0 udhcpc
[ 441.570000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 441.580000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 441.590000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 441.590000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 441.600000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 441.610000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 441.620000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 441.630000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 441.640000] Out of memory: Kill process 727 (netifd) score 0 or sacrifice child
[ 441.640000] Killed process 1454 (udhcpc) total-vm:1504kB, anon-rss:0kB, file-rss:0kB
[ 442.320000] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 442.320000] CPU: 0 PID: 1618 Comm: ntpd Not tainted 3.10.3 #1
[ 442.330000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000031
81bcc1a8 802d2c80 80372a0c 803233db 00000652 000201da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d457c 80ddbb84
00ddbb84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80ddbb10
...
[ 442.360000] Call Trace:
[ 442.370000] [<8006df68>] show_stack+0x48/0x70
[ 442.370000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 442.380000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 442.380000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 442.390000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 442.390000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 442.400000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 442.400000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 442.410000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 442.410000] [<80071c74>] do_page_fault+0x110/0x354
[ 442.420000] [<80060820>] ret_from_exception+0x0/0xc
[ 442.420000]
[ 442.420000] Mem-Info:
[ 442.430000] Normal per-cpu:
[ 442.430000] CPU 0: hi: 0, btch: 1 usd: 0
[ 442.430000] active_anon:0 inactive_anon:0 isolated_anon:0
[ 442.430000] active_file:6 inactive_file:9 isolated_file:0
[ 442.430000] unevictable:0 dirty:0 writeback:0 unstable:0
[ 442.430000] free:131 slab_reclaimable:322 slab_unreclaimable:1494
[ 442.430000] mapped:1 shmem:0 pagetables:62 bounce:0
[ 442.430000] free_cma:0
[ 442.460000] Normal free:524kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:0kB active_file:24kB inactive_file:36kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5976kB kernel_stack:376kB pagetables:248kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
[ 442.500000] lowmem_reserve[]: 0 0
[ 442.510000] Normal: 47*4kB (UMR) 32*8kB (MR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 508kB
[ 442.520000] 15 total pagecache pages
[ 442.520000] 0 pages in swap cache
[ 442.530000] Swap cache stats: add 7841, delete 7841, find 3792/4457
[ 442.530000] Free swap = 254044kB
[ 442.540000] Total swap = 262140kB
[ 442.540000] 8192 pages RAM
[ 442.540000] 959 pages reserved
[ 442.550000] 77440 pages shared
[ 442.550000] 3985 pages non-shared
[ 442.550000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 442.560000] [ 727] 0 727 374 1 4 49 0 netifd
[ 442.570000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 442.580000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 442.590000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 442.600000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 442.600000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 442.610000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 442.620000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 442.630000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 442.640000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 442.650000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 442.650000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 442.660000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 442.670000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 442.680000] Out of memory: Kill process 727 (netifd) score 0 or sacrifice child
[ 442.690000] Killed process 727 (netifd) total-vm:1496kB, anon-rss:0kB, file-rss:4kB
[ 442.700000] netifd: page allocation failure: order:0, mode:0x20058
[ 442.700000] CPU: 0 PID: 727 Comm: netifd Not tainted 3.10.3 #1
[ 442.710000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000032
81bcce38 802d2c80 80372a0c 803233db 000002d7 00000000 00000002 00000000
00000040 800793ac 10800400 80076dec 00000000 00000000 802d457c 81b539e4
00b539e4 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 81b53970
...
[ 442.740000] Call Trace:
[ 442.750000] [<8006df68>] show_stack+0x48/0x70
[ 442.750000] [<800ba5e0>] warn_alloc_failed+0x108/0x12c
[ 442.760000] [<800bca64>] __alloc_pages_nodemask+0x5dc/0x63c
[ 442.760000] [<800b6c08>] find_or_create_page+0x68/0xd8
[ 442.770000] [<8010e724>] __getblk+0x130/0x310
[ 442.770000] [<8013718c>] squashfs_read_data+0x17c/0x66c
[ 442.780000] [<80137858>] squashfs_cache_get+0x1dc/0x324
[ 442.780000] [<80138d10>] squashfs_readpage+0x530/0x7b8
[ 442.790000] [<800bf748>] __do_page_cache_readahead+0x1b8/0x234
[ 442.790000] [<800bfacc>] ra_submit+0x28/0x34
[ 442.800000] [<800b83f8>] filemap_fault+0x198/0x3e8
[ 442.800000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 442.810000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 442.810000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 442.820000] [<80071c74>] do_page_fault+0x110/0x354
[ 442.820000] [<80060820>] ret_from_exception+0x0/0xc
[ 442.830000]
[ 442.830000] Mem-Info:
[ 442.830000] Normal per-cpu:
[ 442.840000] CPU 0: hi: 0, btch: 1 usd: 0
[ 442.840000] active_anon:0 inactive_anon:0 isolated_anon:0
[ 442.840000] active_file:6 inactive_file:9 isolated_file:0
[ 442.840000] unevictable:0 dirty:0 writeback:0 unstable:0
[ 442.840000] free:115 slab_reclaimable:322 slab_unreclaimable:1494
[ 442.840000] mapped:1 shmem:0 pagetables:62 bounce:0
[ 442.840000] free_cma:0
[ 442.870000] Normal free:460kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:0kB active_file:24kB inactive_file:36kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5976kB kernel_stack:376kB pagetables:248kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
[ 442.910000] lowmem_reserve[]: 0 0
[ 442.910000] Normal: 47*4kB (UMR) 25*8kB (MR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 452kB
[ 442.930000] 15 total pagecache pages
[ 442.930000] 0 pages in swap cache
[ 442.930000] Swap cache stats: add 7841, delete 7841, find 3792/4457
[ 442.940000] Free swap = 254044kB
[ 442.940000] Total swap = 262140kB
[ 442.950000] 8192 pages RAM
[ 442.950000] 959 pages reserved
[ 442.950000] 77396 pages shared
[ 442.960000] 3995 pages non-shared
[ 443.530000] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
[ 443.530000] CPU: 0 PID: 1618 Comm: ntpd Not tainted 3.10.3 #1
[ 443.540000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000031
81bcc1a8 802d2c80 80372a0c 803233db 00000652 000201da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d457c 80ddbb84
00ddbb84 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 80ddbb10
...
[ 443.580000] Call Trace:
[ 443.580000] [<8006df68>] show_stack+0x48/0x70
[ 443.580000] [<800b8ed8>] dump_header.isra.16+0x4c/0x138
[ 443.590000] [<800b9224>] oom_kill_process+0xd4/0x3b0
[ 443.590000] [<800b9964>] out_of_memory+0x290/0x2ec
[ 443.600000] [<800bc9e0>] __alloc_pages_nodemask+0x558/0x63c
[ 443.600000] [<800b84f4>] filemap_fault+0x294/0x3e8
[ 443.610000] [<800ce4ec>] __do_fault+0xcc/0x444
[ 443.610000] [<800d1438>] handle_pte_fault+0x32c/0x6dc
[ 443.620000] [<800d1898>] handle_mm_fault+0xb0/0xdc
[ 443.620000] [<80071c74>] do_page_fault+0x110/0x354
[ 443.630000] [<80060820>] ret_from_exception+0x0/0xc
[ 443.630000]
[ 443.630000] Mem-Info:
[ 443.640000] Normal per-cpu:
[ 443.640000] CPU 0: hi: 0, btch: 1 usd: 0
[ 443.640000] active_anon:0 inactive_anon:0 isolated_anon:0
[ 443.640000] active_file:5 inactive_file:8 isolated_file:0
[ 443.640000] unevictable:0 dirty:0 writeback:0 unstable:0
[ 443.640000] free:134 slab_reclaimable:322 slab_unreclaimable:1494
[ 443.640000] mapped:1 shmem:0 pagetables:58 bounce:0
[ 443.640000] free_cma:0
[ 443.670000] Normal free:528kB min:676kB low:844kB high:1012kB active_anon:0kB inactive_anon:0kB active_file:20kB inactive_file:32kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:1288kB slab_unreclaimable:5976kB kernel_stack:376kB pagetables:232kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:80 all_unreclaimable? yes
[ 443.710000] lowmem_reserve[]: 0 0
[ 443.720000] Normal: 52*4kB (UMR) 32*8kB (MR) 2*16kB (R) 1*32kB (R) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 528kB
[ 443.730000] 13 total pagecache pages
[ 443.730000] 0 pages in swap cache
[ 443.740000] Swap cache stats: add 7841, delete 7841, find 3792/4457
[ 443.740000] Free swap = 254240kB
[ 443.750000] Total swap = 262140kB
[ 443.750000] 8192 pages RAM
[ 443.750000] 959 pages reserved
[ 443.760000] 77339 pages shared
[ 443.760000] 3978 pages non-shared
[ 443.760000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 443.770000] [ 1018] 0 1018 204 1 3 18 0 6relayd
[ 443.780000] [ 1116] 0 1116 371 0 3 14 0 sleep
[ 443.790000] [ 1251] 0 1251 371 0 3 14 0 sleep
[ 443.800000] [ 1379] 0 1379 423 0 4 43 0 hostapd
[ 443.800000] [ 1426] 0 1426 407 0 4 27 0 wpa_supplicant
[ 443.810000] [ 1477] 0 1477 289 0 5 18 0 dropbear
[ 443.820000] [ 1502] 0 1502 286 0 4 18 0 uhttpd
[ 443.830000] [ 1588] 0 1588 394 0 4 40 0 dynamic_dns_upd
[ 443.840000] [ 1618] 0 1618 374 0 4 18 0 ntpd
[ 443.850000] [ 1728] 0 1728 371 0 3 14 0 sleep
[ 443.850000] [ 1729] 0 1729 300 0 5 31 0 dropbear
[ 443.860000] [ 1730] 0 1730 376 0 4 21 0 ash
[ 443.870000] [ 1915] 0 1915 4079 0 7 1614 0 transmission-da
[ 443.880000] Out of memory: Kill process 1018 (6relayd) score 0 or sacrifice child
[ 443.890000] Killed process 1018 (6relayd) total-vm:816kB, anon-rss:0kB, file-rss:4kB
ÿ
U-Boot 1.1.4 (Feb 1 2010 - 10:11:24)
comment:415 Changed 5 years ago by miguel.arce@…
in the attachment error-reboot-2.txt, there is this line:
[ 739.860000] ath: skbuff alloc of size 1926 failed
comment:416 Changed 5 years ago by alphasparc@…
If you are running out of memory (which I suspect you are) the following 3 lines in /etc/sysctl.conf will probably help to prevent that.
vm.vfs_cache_pressure=1000 vm.min_free_kbytes=4099 vm.swappiness=0
comment:417 Changed 5 years ago by miguel.arce@…
hi alphasparc, nbd. i will give that a shot.
last night i firewalled transmission so that it seeds very little. the router managed to stay working all night (and still is) and finished all torrents downloads without reboots.
i think there might be a posible memory leak in the ath9x tx code.
comment:418 Changed 5 years ago by nbd
committed some more critical fixes in r37616, please test that one
comment:419 Changed 5 years ago by H4110
I don't know, whether this is related to this issue, but as I have the same symptoms described here I think it might be another symptom, and would like to know if anyone else can reproduce this or if my router is broken.
Router: Buffalo WZR-HP-G300NH
Problem: Nexus 4 regularily fails to update Apps with error "Package file invalid", and today download and verification of an Android update failed about a dozen times before I gave up. I never had such problems on other wifi networks.
So I put two 100MB files on a web server on my desktop (wired connection), one containing only 0x00 and the other one only 0xFF, and downloaded them with the Nexus 4 using Chrome. They were corrupted. At first I used the tagged 12.09 release and then reproduced the results with r37615 of the Attitude Adjustment branch. The wireless config is default with country set to DE.
These are the files as downloaded by the Nexus. Some bits are flipped. I got worse with the second download.
$ hexdump foo.bin 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 022fec0 0008 0000 0000 0000 0000 0000 0000 0000 022fed0 0000 0000 0000 0000 0000 0000 0000 0000 * 6400000
$ hexdump bar.bin 0000000 ffff ffff ffff ffff ffff ffff ffff ffff * 00bed50 fff7 ffff ffff ffff ffff ffff ffff ffff 00bed60 ffff ffff ffff ffff ffff ffff ffff ffff * 00e5a30 ffff ffff ffff ffff fff7 ffff ffff ffff 00e5a40 ffff ffff ffff ffff ffff ffff ffff ffff * 0e483d0 fff7 ffff ffff ffff ffff ffff ffff ffff 0e483e0 ffff ffff ffff ffff ffff ffff ffff ffff * 23cafe0 fff7 ffff ffff ffff ffff ffff ffff ffff 23caff0 ffff ffff ffff ffff ffff ffff ffff ffff * 2433c00 fff7 ffff ffff ffff ffff ffff ffff ffff 2433c10 ffff ffff ffff ffff ffff ffff ffff ffff * 2ca9be0 fff7 ffff ffff ffff ffff ffff ffff ffff 2ca9bf0 ffff ffff ffff ffff ffff ffff ffff ffff * 2cd8d00 fff7 ffff ffff ffff ffff ffff ffff ffff 2cd8d10 ffff ffff ffff ffff ffff ffff ffff ffff * 35da730 fff7 ffff ffff ffff ffff ffff ffff ffff 35da740 ffff ffff ffff ffff ffff ffff ffff ffff * 36fc0d0 fff7 ffff ffff ffff ffff ffff ffff ffff 36fc0e0 ffff ffff ffff ffff ffff ffff ffff ffff * 3b0ce20 fff7 ffff ffff ffff ffff ffff ffff ffff 3b0ce30 ffff ffff ffff ffff ffff ffff ffff ffff * 3eb5d00 fff7 ffff ffff ffff ffff ffff ffff ffff 3eb5d10 ffff ffff ffff ffff ffff ffff ffff ffff * 40fb0b0 fff7 ffff ffff ffff ffff ffff ffff ffff 40fb0c0 ffff ffff ffff ffff ffff ffff ffff ffff * 424b080 ffff ffff ffff ffff fff7 ffff ffff ffff 424b090 ffff ffff ffff ffff ffff ffff ffff ffff * 4368180 fff7 ffff ffff ffff ffff ffff ffff ffff 4368190 ffff ffff ffff ffff ffff ffff ffff ffff * 444b8d0 fff7 ffff ffff ffff ffff ffff ffff ffff 444b8e0 ffff ffff ffff ffff ffff ffff ffff ffff * 45fc5c0 ffff ffff ffff ffff fff7 ffff ffff ffff 45fc5d0 ffff ffff ffff ffff ffff ffff ffff ffff * 517c600 ffff ffff ffff ffff fff7 ffff ffff ffff 517c610 ffff ffff ffff ffff ffff ffff ffff ffff * 53032a0 fff7 ffff ffff ffff ffff ffff ffff ffff 53032b0 ffff ffff ffff ffff ffff ffff ffff ffff * 53fbda0 ffff ffff ffff ffff fff7 ffff ffff ffff 53fbdb0 ffff ffff ffff ffff ffff ffff ffff ffff * 58aeec0 fff7 ffff ffff ffff ffff ffff ffff ffff 58aeed0 ffff ffff ffff ffff ffff ffff ffff ffff * 58f9a70 ffff ffff ffff ffff fff7 ffff ffff ffff 58f9a80 ffff ffff ffff ffff ffff ffff ffff ffff * 5b8a6f0 fff7 ffff ffff ffff ffff ffff ffff ffff 5b8a700 ffff ffff ffff ffff ffff ffff ffff ffff * 6400000
Does anyone else have similar symptoms? I've been having this problem for a few month now, they became worse with Attitude Adjustment. Focus is probably on Android, but I don't use a laptop very often. I'll bring one from work this weekend and repeat the test with it, and also with the latest patches, if they make it into the Attitude Adjustment branch.
comment:420 Changed 5 years ago by miguel.arce@…
Hi, nbd
Two things: 1 tried 37560 with the three lines sugested by alphasparc and it stop rebooting, that one had a lot of tx queue messages.
i am testing r37619.
fewer tx queue messages, a LOT less, and i am not using the alphasparc lines and its not rebooting, nor it seems like its heartbeat is going crazy. i am viewing videos from minidlna, and seeding torrents, and using HT40, without issues so far.
the heartbeat led is quite stable, i am going to stress it tonight and tell you later about it, also, wireless feels somewhat more responsive than before too, minidlna via wifi used to delay a couple of secs before response, it is now instantaneous and the configurations used are exactly the same from the last r37560, same tests.
comment:421 Changed 5 years ago by nbd
H4110, with the kind of corruption that you're describing, it does look to me like the router is not at fault here. Since the router is not involved in the TCP connection (aside from relaying packets), such corruption should have been detected by checksum validation and invalid packets should have been discarded and retransmitted.
I don't have any idea what could cause this though.
comment:422 follow-up: ↓ 444 Changed 5 years ago by edmondo
Hi nbd
Thanks for the new fixes.
I've done some testing of r37673 yesterday and it seems stable.
I'll check in the next days if I can confirm this, at the moment it seems positive.
comment:423 follow-up: ↓ 424 Changed 5 years ago by anonymous
If the fix is stable when/how will it get to the stable release?
comment:424 in reply to: ↑ 423 Changed 5 years ago by anonymous
Replying to anonymous:
If the fix is stable when/how will it get to the stable release?
It might still crash very soon. I ran a very old trunk (January '13) for 14 days before it crashed.
Also, should it be stable, it will probably appear in the next stable release of OWRT.
comment:425 Changed 4 years ago by miguel.arce@…
comment:426 Changed 4 years ago by nbd
please test versions inbetween and let me know where it broke
comment:427 Changed 4 years ago by miguel.arce@…
hi, i am sorry i have to wait to the snapshot build to update, cuz i dont know how to compile snapshots :(
comment:428 Changed 4 years ago by nbd
more fixes added in r37747, please test
comment:429 Changed 4 years ago by miguel.arce@…
testing r37748,
same behaviour, reboots. lots of tx dma.
[ 335.660000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 372.020000] 6relayd invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0
[ 372.020000] CPU: 0 PID: 1025 Comm: 6relayd Not tainted 3.10.4 #1
[ 372.030000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000034
81bc41a8 802d2cf4 80372a0c 803233db 00000401 000200da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d45f0 8088f9f4
0088f9f4 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 8088f980
...
[ 372.070000] Call Trace:
[ 372.070000] [<8006df68>] show_stack+0x48/0x70
[ 372.070000] [<800b8ec0>] dump_header.isra.16+0x4c/0x138
[ 372.080000] [<800b920c>] oom_kill_process+0xd4/0x3b0
[ 372.080000] [<800b994c>] out_of_memory+0x290/0x2ec
[ 372.090000] [<800bc9c8>] __alloc_pages_nodemask+0x558/0x63c
[ 372.090000] [<800dc670>] read_swap_cache_async+0x84/0x19c
[ 372.100000] [<800dc810>] swapin_readahead+0x88/0xf4
[ 372.100000] [<800d1460>] handle_pte_fault+0x36c/0x6dc
[ 372.110000] [<800d1880>] handle_mm_fault+0xb0/0xdc
[ 372.110000] [<80071c74>] do_page_fault+0x110/0x354
[ 372.120000] [<80060820>] ret_from_exception+0x0/0xc
[ 372.120000] [<8011d434>] ep_send_events_proc+0xa4/0x178
[ 372.130000] [<8011ddc8>] ep_scan_ready_list.isra.17+0x98/0x198
[ 372.140000] [<8011ebd4>] SyS_epoll_wait+0x284/0x328
[ 372.140000] [<80062544>] stack_done+0x20/0x40
[ 372.140000]
[ 372.150000] Mem-Info:
[ 372.150000] Normal per-cpu:
[ 372.150000] CPU 0: hi: 0, btch: 1 usd: 0
[ 372.160000] active_anon:0 inactive_anon:0 isolated_anon:3
[ 372.160000] active_file:47 inactive_file:324 isolated_file:0
[ 372.160000] unevictable:0 dirty:0 writeback:3 unstable:0
[ 372.160000] free:976 slab_reclaimable:229 slab_unreclaimable:1308
[ 372.160000] mapped:17 shmem:0 pagetables:78 bounce:0
[ 372.160000] free_cma:0
[ 372.190000] Normal free:3904kB min:4096kB low:5120kB high:6144kB active_anon:0kB inactive_anon:0kB active_file:188kB inactive_file:1296kB unevictable:0kB isolated(anon):12kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:12kB mapped:68kB shmem:0kB slab_reclaimable:916kB slab_unreclaimable:5232kB kernel_stack:360kB pagetables:312kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:3166 all_unreclaimable? yes
[ 372.230000] lowmem_reserve[]: 0 0
[ 372.230000] Normal: 42*4kB (E) 73*8kB (UEM) 99*16kB (UEM) 43*32kB (M) 1*64kB (R) 1*128kB (R) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3904kB
[ 372.240000] 374 total pagecache pages
[ 372.250000] 3 pages in swap cache
[ 372.250000] Swap cache stats: add 2931, delete 2928, find 465/577
[ 372.260000] Free swap = 254084kB
[ 372.260000] Total swap = 262140kB
[ 372.270000] 8192 pages RAM
[ 372.270000] 959 pages reserved
[ 372.270000] 268511 pages shared
[ 372.280000] 3998 pages non-shared
[ 372.280000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 372.290000] [ 498] 0 498 227 0 3 22
0 ubusd
[ 372.290000] [ 724] 0 724 374 4 6 49
0 netifd
[ 372.300000] [ 806] 0 806 374 0 4 18
0 udhcpc
[ 372.310000] [ 1025] 0 1025 204 7 4 19
0 6relayd
[ 372.320000] [ 1110] 0 1110 371 0 4 14
0 sleep
[ 372.330000] [ 1248] 0 1248 371 0 3 15
0 sleep
[ 372.330000] [ 1376] 0 1376 423 1 4 43
0 hostapd
[ 372.340000] [ 1423] 0 1423 407 1 4 28
0 wpa_supplicant
[ 372.350000] [ 1451] 0 1451 376 0 4 20
0 udhcpc
[ 372.360000] [ 1474] 0 1474 289 1 5 18
0 dropbear
[ 372.370000] [ 1499] 0 1499 286 0 4 19
0 uhttpd
[ 372.380000] [ 1532] 65534 1532 239 0 4 22
0 dnsmasq
[ 372.380000] [ 1585] 0 1585 394 0 4 39
0 dynamic_dns_upd
[ 372.390000] [ 1615] 0 1615 374 1 4 18
0 ntpd
[ 372.400000] [ 1725] 0 1725 371 0 4 14
0 sleep
[ 372.410000] [ 1930] 0 1930 4017 8 9 1552
0 transmission-da
[ 372.420000] [ 1933] 0 1933 192 0 3 13
0 askfirst
[ 372.430000] Out of memory: Kill process 1532 (dnsmasq) score 0 or sacrifice child
[ 372.430000] Killed process 1532 (dnsmasq) total-vm:956kB, anon-rss:0kB, file-rss:0kB
[ 372.620000] 6relayd invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0
[ 372.620000] CPU: 0 PID: 1025 Comm: 6relayd Not tainted 3.10.4 #1
[ 372.630000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000034
81bc41a8 802d2cf4 80372a0c 803233db 00000401 000200da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d45f0 8088f9f4
0088f9f4 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 8088f980
...
[ 372.670000] Call Trace:
[ 372.670000] [<8006df68>] show_stack+0x48/0x70
[ 372.670000] [<800b8ec0>] dump_header.isra.16+0x4c/0x138
[ 372.680000] [<800b920c>] oom_kill_process+0xd4/0x3b0
[ 372.680000] [<800b994c>] out_of_memory+0x290/0x2ec
[ 372.690000] [<800bc9c8>] __alloc_pages_nodemask+0x558/0x63c
[ 372.690000] [<800dc670>] read_swap_cache_async+0x84/0x19c
[ 372.700000] [<800dc810>] swapin_readahead+0x88/0xf4
[ 372.700000] [<800d1460>] handle_pte_fault+0x36c/0x6dc
[ 372.710000] [<800d1880>] handle_mm_fault+0xb0/0xdc
[ 372.710000] [<80071c74>] do_page_fault+0x110/0x354
[ 372.720000] [<80060820>] ret_from_exception+0x0/0xc
[ 372.720000] [<8011d434>] ep_send_events_proc+0xa4/0x178
[ 372.730000] [<8011ddc8>] ep_scan_ready_list.isra.17+0x98/0x198
[ 372.730000] [<8011ebd4>] SyS_epoll_wait+0x284/0x328
[ 372.740000] [<80062544>] stack_done+0x20/0x40
[ 372.740000]
[ 372.750000] Mem-Info:
[ 372.750000] Normal per-cpu:
[ 372.750000] CPU 0: hi: 0, btch: 1 usd: 0
[ 372.760000] active_anon:0 inactive_anon:3 isolated_anon:0
[ 372.760000] active_file:47 inactive_file:324 isolated_file:0
[ 372.760000] unevictable:0 dirty:0 writeback:3 unstable:0
[ 372.760000] free:966 slab_reclaimable:229 slab_unreclaimable:1308
[ 372.760000] mapped:17 shmem:0 pagetables:74 bounce:0
[ 372.760000] free_cma:0
[ 372.790000] Normal free:3860kB min:4096kB low:5120kB high:6144kB active_anon:0kB inactive_anon:12kB active_file:188kB inactive_file:1296kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:12kB mapped:68kB shmem:0kB slab_reclaimable:916kB slab_unreclaimable:5236kB kernel_stack:360kB pagetables:296kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:2964 all_unreclaimable? yes
[ 372.830000] lowmem_reserve[]: 0 0
[ 372.830000] Normal: 43*4kB (EM) 73*8kB (UEM) 100*16kB (UEM) 41*32kB (M) 1*64kB (R) 1*128kB (R) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3860kB
[ 372.840000] 374 total pagecache pages
[ 372.850000] 3 pages in swap cache
[ 372.850000] Swap cache stats: add 2931, delete 2928, find 465/578
[ 372.860000] Free swap = 254172kB
[ 372.860000] Total swap = 262140kB
[ 372.870000] 8192 pages RAM
[ 372.870000] 959 pages reserved
[ 372.870000] 268652 pages shared
[ 372.880000] 3996 pages non-shared
[ 372.880000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 372.890000] [ 498] 0 498 227 0 3 22
0 ubusd
[ 372.890000] [ 724] 0 724 374 4 6 49
0 netifd
[ 372.900000] [ 806] 0 806 374 0 4 18
0 udhcpc
[ 372.910000] [ 1025] 0 1025 204 7 4 19
0 6relayd
[ 372.920000] [ 1110] 0 1110 371 0 4 14
0 sleep
[ 372.930000] [ 1248] 0 1248 371 0 3 15
0 sleep
[ 372.940000] [ 1376] 0 1376 423 1 4 43
0 hostapd
[ 372.940000] [ 1423] 0 1423 407 1 4 28
0 wpa_supplicant
[ 372.950000] [ 1451] 0 1451 376 0 4 20
0 udhcpc
[ 372.960000] [ 1474] 0 1474 289 1 5 18
0 dropbear
[ 372.970000] [ 1499] 0 1499 286 0 4 19
0 uhttpd
[ 372.980000] [ 1585] 0 1585 394 0 4 39
0 dynamic_dns_upd
[ 372.990000] [ 1615] 0 1615 374 1 4 18
0 ntpd
[ 372.990000] [ 1725] 0 1725 371 0 4 14
0 sleep
[ 373.000000] [ 1930] 0 1930 4017 8 9 1552
0 transmission-da
[ 373.010000] [ 1933] 0 1933 192 0 3 13
0 askfirst
[ 373.020000] Out of memory: Kill process 498 (ubusd) score 0 or sacrifice child
[ 373.030000] Killed process 498 (ubusd) total-vm:908kB, anon-rss:0kB, file-rss:0kB
[ 373.160000] 6relayd invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0
[ 373.160000] CPU: 0 PID: 1025 Comm: 6relayd Not tainted 3.10.4 #1
[ 373.170000] Stack : 00000006 00000000 00000000 00000000 00000000 00000000 80392a96 00000034
81bc41a8 802d2cf4 80372a0c 803233db 00000401 000200da 00000000 00000000
803234b0 800793ac 10800400 80076dec 00000000 00000000 802d45f0 8088f9f4
0088f9f4 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 8088f980
...
[ 373.210000] Call Trace:
[ 373.210000] [<8006df68>] show_stack+0x48/0x70
[ 373.210000] [<800b8ec0>] dump_header.isra.16+0x4c/0x138
[ 373.220000] [<800b920c>] oom_kill_process+0xd4/0x3b0
[ 373.220000] [<800b994c>] out_of_memory+0x290/0x2ec
[ 373.230000] [<800bc9c8>] __alloc_pages_nodemask+0x558/0x63c
[ 373.230000] [<800dc670>] read_swap_cache_async+0x84/0x19c
[ 373.240000] [<800dc810>] swapin_readahead+0x88/0xf4
[ 373.240000] [<800d1460>] handle_pte_fault+0x36c/0x6dc
[ 373.250000] [<800d1880>] handle_mm_fault+0xb0/0xdc
[ 373.250000] [<80071c74>] do_page_fault+0x110/0x354
[ 373.260000] [<80060820>] ret_from_exception+0x0/0xc
[ 373.260000] [<8011d434>] ep_send_events_proc+0xa4/0x178
[ 373.270000] [<8011ddc8>] ep_scan_ready_list.isra.17+0x98/0x198
[ 373.270000] [<8011ebd4>] SyS_epoll_wait+0x284/0x328
[ 373.280000] [<80062544>] stack_done+0x20/0x40
[ 373.280000]
[ 373.290000] Mem-Info:
[ 373.290000] Normal per-cpu:
[ 373.290000] CPU 0: hi: 0, btch: 1 usd: 0
[ 373.300000] active_anon:0 inactive_anon:3 isolated_anon:0
[ 373.300000] active_file:47 inactive_file:324 isolated_file:0
[ 373.300000] unevictable:0 dirty:0 writeback:3 unstable:0
[ 373.300000] free:969 slab_reclaimable:229 slab_unreclaimable:1309
[ 373.300000] mapped:17 shmem:0 pagetables:71 bounce:0
[ 373.300000] free_cma:0
[ 373.330000] Normal free:3876kB min:4096kB low:5120kB high:6144kB active_anon:0kB inactive_anon:12kB active_file:188kB inactive_file:1296kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:32768kB managed:28720kB mlocked:0kB dirty:0kB writeback:12kB mapped:68kB shmem:0kB slab_reclaimable:916kB slab_unreclaimable:5236kB kernel_stack:360kB pagetables:284kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:2615 all_unreclaimable? yes
[ 373.370000] lowmem_reserve[]: 0 0
[ 373.370000] Normal: 45*4kB (UEM) 74*8kB (UEM) 100*16kB (UEM) 41*32kB (M) 1*64kB (R) 1*128kB (R) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3876kB
[ 373.380000] 374 total pagecache pages
[ 373.390000] 3 pages in swap cache
[ 373.390000] Swap cache stats: add 2931, delete 2928, find 465/578
[ 373.400000] Free swap = 254260kB
[ 373.400000] Total swap = 262140kB
[ 373.410000] 8192 pages RAM
[ 373.410000] 959 pages reserved
[ 373.410000] 268652 pages shared
[ 373.410000] 3976 pages non-shared
[ 373.420000] [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name
[ 373.430000] [ 724] 0 724 374 4 6 49
0 netifd
[ 373.430000] [ 806] 0 806 374 0 4 18
0 udhcpc
[ 373.440000] [ 1025] 0 1025 204 7 4 19
0 6relayd
[ 373.450000] [ 1110] 0 1110 371 0 4 14
0 sleep
[ 373.460000] [ 1248] 0 1248 371 0 3 15
0 sleep
[ 373.470000] [ 1376] 0 1376 423 1 4 43
0 hostapd
[ 373.470000] [ 1423] 0 1423 407 1 4 28
0 wpa_supplicant
[ 373.480000] [ 1451] 0 1451 376 0 4 20
0 udhcpc
[ 373.490000] [ 1474] 0 1474 289 1 5 18
0 dropbear
[ 373.500000] [ 1499] 0 1499 286 0 4 19
0 uhttpd
[ 373.510000] [ 1585] 0 1585 394 0 4 39
0 dynamic_dns_upd
[ 373.520000] [ 1615] 0 1615 374 1 4 18
0 ntpd
[ 373.520000] [ 1725] 0 1725 371 0 4 14
0 sleep
[ 373.530000] [ 1930] 0 1930 4017 8 9 1552
0 transmission-da
[ 373.540000] [ 1933] 0 1933 192 0 3 13
0 askfirst
[ 373.550000] Out of memory: Kill process 724 (netifd) score 0 or sacrifice child
[ 373.560000] Killed process 806 (udhcpc) total-vm:1496kB, anon-rss:0kB, file-rss:0kB
and i am using the alphasparc sugested lines.
comment:430 follow-up: ↓ 431 Changed 4 years ago by nbd
Neither the Tx DMA message, nor the reboots are related to this ticket.
The reboots have nothing to do with the wifi driver.
comment:431 in reply to: ↑ 430 Changed 4 years ago by miguel.arce@…
Replying to nbd:
Neither the Tx DMA message, nor the reboots are related to this ticket.
The reboots have nothing to do with the wifi driver.
Hi nbd,
i see. what in your opinion could then be the problem? any sugestions as where to look?
comment:432 Changed 4 years ago by nbd
Well, you're running out of memory. 32 MB isn't exactly a lot for running transmission.
comment:433 Changed 4 years ago by anonymous
The router actually does quite a bit of caching and rarely releases memory, we need some sort of sysctl to release cache memory when it is running out of memory to allocate.
comment:434 follow-up: ↓ 441 Changed 4 years ago by miguel.arce@…
using 10.03.1, right now, with transmission, and no memory problems, it doesnt reboot at all, this is 2.32 right now is 2.82 current openwrt release, i will be testing 2.82 with 10.03.1 as base system to see if it gets out of memory problem.
if it really is transmission > 2.80+ that is causing the out of memory it should reboot with 10.03.1 as well.
comment:435 Changed 4 years ago by alphasparc@…
@miguel.arce
I am using the firmware I have compiled here it is updated to the latest AA.
Works fine.
Got a few "ath: phy0: Failed to stop TX DMA, queues=0x004!" message but it auto recovers.
Changed 4 years ago by valent.turkovic@…
Just returned from 2 week vacation to find my wr1043nd full log of issues. I'm running r37673...
comment:436 Changed 4 years ago by anonymous
I am using the lastet AA. problem still exist. wifi stop after 2-3 days. router: wr703n.
logread have:
Chonge daemon.info hostapd: wlan0: STA 00:26:c6:8b:8c:70 IEEE 802.11: disconnected due to excessive missing ACKs
Chonge daemon.info hostapd: wlan0: STA 00:26:c6:8b:8c:70 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
debug info: /sys/kernel/debug/ieee80211/phy0/ath9k
------------------ ani ------------------------------
ANI: ENABLED
ANI RESET: 6
SPUR UP: 1014
SPUR DOWN: 1014
OFDM WS-DET ON: 0
OFDM WS-DET OFF: 0
MRC-CCK ON: 0
MRC-CCK OFF: 0
FIR-STEP UP: 733
FIR-STEP DOWN: 736
INV LISTENTIME: 0
OFDM ERRORS: 4428969
CCK ERRORS: 564775
------------------ end ------------------------------
------------------ base_eeprom ------------------------------
EEPROM Version : 2
RegDomain1 : 0
RegDomain2 : 31
TX Mask : 1
RX Mask : 1
Allow 5GHz : 0
Allow 2GHz : 1
Disable 2GHz HT20 : 0
Disable 2GHz HT40 : 0
Disable 5Ghz HT20 : 0
Disable 5Ghz HT40 : 0
Big Endian : 0
RF Silent : 0
BT option : 0
Device Cap : 0
Device Type : 4
Power Table Offset : 0
Tuning Caps1 : 96
Tuning Caps2 : 0
Enable Tx Temp Comp : 1
Enable Tx Volt Comp : 0
Enable fast clock : 1
Enable doubling : 1
Internal regulator : 1
Enable Paprd : 1
Driver Strength : 0
Quick Drop : 0
Chain mask Reduce : 0
Write enable Gpio : 3
WLAN Disable Gpio : 0
WLAN LED Gpio : 8
Rx Band Select Gpio : 255
Tx Gain : 1
Rx Gain : 1
SW Reg : 0
MacAddress : 00:03:7f:be:f1:f5
------------------ end ------------------------------
------------------ chanbw ------------------------------
0x00000000
------------------ end ------------------------------
------------------ diag ------------------------------
0x00000000
------------------ end ------------------------------
------------------ diversity ------------------------------
0
------------------ end ------------------------------
------------------ dma ------------------------------
Raw DMA Debug values:
0: 88888888 1: 00000000 2: 12249249 3: 00000000
4: 00000000 5: 00000000 6: 00192474 7: 00028000
Num QCU: chain_st fsp_ok fsp_st DCU: chain_st
0 0 1 1 0
1 0 1 1 0
2 0 1 1 0
3 0 1 1 0
4 0 1 1 0
5 0 1 1 0
6 0 1 1 0
7 0 1 1 0
8 0 0 1 0
9 0 0 1 0
qcu_stitch state: 0 qcu_fetch state: 0
qcu_complete state: 0 dcu_complete state: 0
dcu_arb state: 0 dcu_fp state: 0
chan_idle_dur: 29 chan_idle_dur_valid: 1
txfifo_valid_0: 0 txfifo_valid_1: 0
txfifo_dcu_num_0: 9 txfifo_dcu_num_1: 12
pcu observe: 0x2880
AR_CR: 0xc
------------------ end ------------------------------
------------------ gpio_mask ------------------------------
0
------------------ end ------------------------------
------------------ gpio_val ------------------------------
0
------------------ end ------------------------------
------------------ ignore_extcca ------------------------------
N
------------------ end ------------------------------
------------------ interrupt ------------------------------
RXLP: 1601923
RXHP: 0
WATHDOG: 0
RXEOL: 6
RXORN: 0
TX: 3891957
TXURN: 0
MIB: 0
RXPHY: 0
RXKCM: 0
SWBA: 19520271
BMISS: 0
BNR: 0
CST: 179
GTT: 3709
TIM: 0
CABEND: 0
DTIMSYNC: 0
DTIM: 0
TSFOOR: 0
MCI: 0
GENTIMER: 0
TOTAL: 24984121
SYNC_CAUSE stats:
Sync-All: 0
RTC-IRQ: 0
MAC-IRQ: 0
EEPROM-Illegal-Access: 0
APB-Timeout: 0
PCI-Mode-Conflict: 0
HOST1-Fatal: 0
HOST1-Perr: 0
TRCV-FIFO-Perr: 0
RADM-CPL-EP: 0
RADM-CPL-DLLP-Abort: 0
RADM-CPL-TLP-Abort: 0
RADM-CPL-ECRC-Err: 0
RADM-CPL-Timeout: 0
Local-Bus-Timeout: 0
PM-Access: 0
MAC-Awake: 0
MAC-Asleep: 0
MAC-Sleep-Access: 0
------------------ end ------------------------------
------------------ misc ------------------------------
BSSID: 00:00:00:00:00:00
BSSID-MASK: ff:ff:ff:ff:ff:ff
OPMODE: AP
RXFILTER: 0x4497 UCAST MCAST BCAST BEACON PROBEREQ COMP_BAR PSPOLL
INTERRUPT-MASK: 0xf0010473 SWBA CST RX RXHP RXLP BB_WATCHDOG
VIF-COUNTS: AP: 1 STA: 0 MESH: 0 WDS: 0 ADHOC: 0 TOTAL: 1 BEACON-VIF: 1
------------------ end ------------------------------
------------------ modal_eeprom ------------------------------
2GHz modal Header :
Chain0 Ant. Control : 336
Chain1 Ant. Control : 336
Chain2 Ant. Control : 336
Ant. Common Control : 272
Ant. Common Control2 : 139810
Ant. Gain : 0
Switch Settle : 44
Chain0 xatten1DB : 0
Chain1 xatten1DB : 0
Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
Temp Slope : 40
Volt Slope : 0
spur Channels0 : 164
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
Chain0 NF Threshold : -1
Chain1 NF Threshold : 0
Chain2 NF Threshold : 0
Quick Drop : 0
txEndToXpaOff : 0
xPA Bias Level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
txFrameToXpaOn : 14
txClip : 3
ADC Desired size : -30
5GHz modal Header :
Chain0 Ant. Control : 0
Chain1 Ant. Control : 0
Chain2 Ant. Control : 0
Ant. Common Control : 272
Ant. Common Control2 : 139810
Ant. Gain : 0
Switch Settle : 45
Chain0 xatten1DB : 0
Chain1 xatten1DB : 0
Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
Temp Slope : 68
Volt Slope : 0
spur Channels0 : 0
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
Chain0 NF Threshold : -1
Chain1 NF Threshold : 0
Chain2 NF Threshold : 0
Quick Drop : 0
txEndToXpaOff : 0
xPA Bias Level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
txFrameToXpaOn : 14
txClip : 3
ADC Desired size : -30
------------------ end ------------------------------
------------------ paprd ------------------------------
N
------------------ end ------------------------------
------------------ qlen_be ------------------------------
123
------------------ end ------------------------------
------------------ qlen_bk ------------------------------
123
------------------ end ------------------------------
------------------ qlen_vi ------------------------------
123
------------------ end ------------------------------
------------------ qlen_vo ------------------------------
123
------------------ end ------------------------------
------------------ queues ------------------------------
(VO): qnum: 0 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(VI): qnum: 1 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(BE): qnum: 2 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(BK): qnum: 3 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(CAB): qnum: 8 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
------------------ end ------------------------------
------------------ recv ------------------------------
CRC ERR : 217765
DECRYPT CRC ERR : 0
PHY ERR : 459
MIC ERR : 0
PRE-DELIM CRC ERR : 0
POST-DELIM CRC ERR : 15
DECRYPT BUSY ERR : 0
RX-LENGTH-ERR : 0
RX-OOM-ERR : 0
RX-RATE-ERR : 0
RX-TOO-MANY-FRAGS : 0
UNDERRUN ERR : 0
TIMING ERR : 0
PARITY ERR : 0
RATE ERR : 0
LENGTH ERR : 0
RADAR ERR : 0
SERVICE ERR : 0
TOR ERR : 0
OFDM-TIMING ERR : 0
OFDM-SIGNAL-PARITY ERR : 0
OFDM-RATE ERR : 0
OFDM-LENGTH ERR : 0
OFDM-POWER-DROP ERR : 0
OFDM-SERVICE ERR : 0
OFDM-RESTART ERR : 59
FALSE-RADAR-EXT ERR : 0
CCK-TIMING ERR : 0
CCK-HEADER-CRC ERR : 0
CCK-RATE ERR : 0
CCK-SERVICE ERR : 0
CCK-RESTART ERR : 400
CCK-LENGTH ERR : 0
CCK-POWER-DROP ERR : 0
HT-CRC ERR : 0
HT-LENGTH ERR : 0
HT-RATE ERR : 0
RX-Pkts-All : 1754679
RX-Bytes-All : 455156757
RX-Beacons : 208690
RX-Frags : 813
RX-Spectral : 0
------------------ end ------------------------------
------------------ reset ------------------------------
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
MCI Reset: 0
------------------ end ------------------------------
------------------ rx_chainmask ------------------------------
0x00000001
------------------ end ------------------------------
------------------ spectral_count ------------------------------
8
------------------ end ------------------------------
------------------ spectral_fft_period ------------------------------
15
------------------ end ------------------------------
------------------ spectral_period ------------------------------
255
------------------ end ------------------------------
------------------ spectral_scan0 ------------------------------
------------------ end ------------------------------
------------------ spectral_scan_ctl ------------------------------
disable
------------------ end ------------------------------
------------------ spectral_short_repeat ------------------------------
1
------------------ end ------------------------------
------------------ tx_chainmask ------------------------------
0x00000001
------------------ end ------------------------------
------------------ xmit ------------------------------
BE BK VI VO
MPDUs Queued: 5140 680 9 45035
MPDUs Completed: 22900 2002 14 46338
MPDUs XRetried: 827 24 0 95
Aggregates: 38062 212 0 0
AMPDUs Queued HW: 0 0 0 0
AMPDUs Queued SW: 1532444 7611 16 1398
AMPDUs Completed: 1513165 6248 11 0
AMPDUs Retried: 32192 216 0 0
AMPDUs XRetried: 692 17 0 0
TXERR Filtered: 797 5 0 8
FIFO Underrun: 0 0 0 0
TXOP Exceeded: 0 0 0 0
TXTIMER Expiry: 0 0 0 0
DESC CFG Error: 0 0 0 0
DATA Underrun: 0 0 0 0
DELIM Underrun: 0 0 0 0
TX-Pkts-All: 1537584 8291 25 46433
TX-Bytes-All: 1796308981 3275934 5426 7708662
HW-put-tx-buf: 1392072 7988 25 46433
HW-tx-start: 0 0 0 0
HW-tx-proc-desc: 1393023 7989 25 46433
TX-Failed: 0 0 0 0
------------------ end ------------------------------
After a few minutes， debug again:
------------------ ani ------------------------------
ANI: ENABLED
ANI RESET: 6
SPUR UP: 1015
SPUR DOWN: 1015
OFDM WS-DET ON: 0
OFDM WS-DET OFF: 0
MRC-CCK ON: 0
MRC-CCK OFF: 0
FIR-STEP UP: 734
FIR-STEP DOWN: 737
INV LISTENTIME: 0
OFDM ERRORS: 4430678
CCK ERRORS: 565467
------------------ end ------------------------------
------------------ base_eeprom ------------------------------
EEPROM Version : 2
RegDomain1 : 0
RegDomain2 : 31
TX Mask : 1
RX Mask : 1
Allow 5GHz : 0
Allow 2GHz : 1
Disable 2GHz HT20 : 0
Disable 2GHz HT40 : 0
Disable 5Ghz HT20 : 0
Disable 5Ghz HT40 : 0
Big Endian : 0
RF Silent : 0
BT option : 0
Device Cap : 0
Device Type : 4
Power Table Offset : 0
Tuning Caps1 : 96
Tuning Caps2 : 0
Enable Tx Temp Comp : 1
Enable Tx Volt Comp : 0
Enable fast clock : 1
Enable doubling : 1
Internal regulator : 1
Enable Paprd : 1
Driver Strength : 0
Quick Drop : 0
Chain mask Reduce : 0
Write enable Gpio : 3
WLAN Disable Gpio : 0
WLAN LED Gpio : 8
Rx Band Select Gpio : 255
Tx Gain : 1
Rx Gain : 1
SW Reg : 0
MacAddress : 00:03:7f:be:f1:f5
------------------ end ------------------------------
------------------ chanbw ------------------------------
0x00000000
------------------ end ------------------------------
------------------ diag ------------------------------
0x00000000
------------------ end ------------------------------
------------------ diversity ------------------------------
0
------------------ end ------------------------------
------------------ dma ------------------------------
Raw DMA Debug values:
0: 88888888 1: 00000000 2: 12249249 3: 00000000
4: 00000000 5: 00000000 6: 00192510 7: 00028000
Num QCU: chain_st fsp_ok fsp_st DCU: chain_st
0 0 1 1 0
1 0 1 1 0
2 0 1 1 0
3 0 1 1 0
4 0 1 1 0
5 0 1 1 0
6 0 1 1 0
7 0 1 1 0
8 0 0 1 0
9 0 0 1 0
qcu_stitch state: 0 qcu_fetch state: 0
qcu_complete state: 0 dcu_complete state: 0
dcu_arb state: 0 dcu_fp state: 0
chan_idle_dur: 68 chan_idle_dur_valid: 1
txfifo_valid_0: 0 txfifo_valid_1: 0
txfifo_dcu_num_0: 9 txfifo_dcu_num_1: 12
pcu observe: 0x2880
AR_CR: 0xc
------------------ end ------------------------------
------------------ gpio_mask ------------------------------
0
------------------ end ------------------------------
------------------ gpio_val ------------------------------
0
------------------ end ------------------------------
------------------ ignore_extcca ------------------------------
N
------------------ end ------------------------------
------------------ interrupt ------------------------------
RXLP: 1601924
RXHP: 0
WATHDOG: 0
RXEOL: 6
RXORN: 0
TX: 3893233
TXURN: 0
MIB: 0
RXPHY: 0
RXKCM: 0
SWBA: 19530477
BMISS: 0
BNR: 0
CST: 179
GTT: 3709
TIM: 0
CABEND: 0
DTIMSYNC: 0
DTIM: 0
TSFOOR: 0
MCI: 0
GENTIMER: 0
TOTAL: 24995604
SYNC_CAUSE stats:
Sync-All: 0
RTC-IRQ: 0
MAC-IRQ: 0
EEPROM-Illegal-Access: 0
APB-Timeout: 0
PCI-Mode-Conflict: 0
HOST1-Fatal: 0
HOST1-Perr: 0
TRCV-FIFO-Perr: 0
RADM-CPL-EP: 0
RADM-CPL-DLLP-Abort: 0
RADM-CPL-TLP-Abort: 0
RADM-CPL-ECRC-Err: 0
RADM-CPL-Timeout: 0
Local-Bus-Timeout: 0
PM-Access: 0
MAC-Awake: 0
MAC-Asleep: 0
MAC-Sleep-Access: 0
------------------ end ------------------------------
------------------ misc ------------------------------
BSSID: 00:00:00:00:00:00
BSSID-MASK: ff:ff:ff:ff:ff:ff
OPMODE: AP
RXFILTER: 0x4497 UCAST MCAST BCAST BEACON PROBEREQ COMP_BAR PSPOLL
INTERRUPT-MASK: 0xf0010473 SWBA CST RX RXHP RXLP BB_WATCHDOG
VIF-COUNTS: AP: 1 STA: 0 MESH: 0 WDS: 0 ADHOC: 0 TOTAL: 1 BEACON-VIF: 1
------------------ end ------------------------------
------------------ modal_eeprom ------------------------------
2GHz modal Header :
Chain0 Ant. Control : 336
Chain1 Ant. Control : 336
Chain2 Ant. Control : 336
Ant. Common Control : 272
Ant. Common Control2 : 139810
Ant. Gain : 0
Switch Settle : 44
Chain0 xatten1DB : 0
Chain1 xatten1DB : 0
Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
Temp Slope : 40
Volt Slope : 0
spur Channels0 : 164
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
Chain0 NF Threshold : -1
Chain1 NF Threshold : 0
Chain2 NF Threshold : 0
Quick Drop : 0
txEndToXpaOff : 0
xPA Bias Level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
txFrameToXpaOn : 14
txClip : 3
ADC Desired size : -30
5GHz modal Header :
Chain0 Ant. Control : 0
Chain1 Ant. Control : 0
Chain2 Ant. Control : 0
Ant. Common Control : 272
Ant. Common Control2 : 139810
Ant. Gain : 0
Switch Settle : 45
Chain0 xatten1DB : 0
Chain1 xatten1DB : 0
Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
Temp Slope : 68
Volt Slope : 0
spur Channels0 : 0
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
Chain0 NF Threshold : -1
Chain1 NF Threshold : 0
Chain2 NF Threshold : 0
Quick Drop : 0
txEndToXpaOff : 0
xPA Bias Level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
txFrameToXpaOn : 14
txClip : 3
ADC Desired size : -30
------------------ end ------------------------------
------------------ paprd ------------------------------
N
------------------ end ------------------------------
------------------ qlen_be ------------------------------
123
------------------ end ------------------------------
------------------ qlen_bk ------------------------------
123
------------------ end ------------------------------
------------------ qlen_vi ------------------------------
123
------------------ end ------------------------------
------------------ qlen_vo ------------------------------
123
------------------ end ------------------------------
------------------ queues ------------------------------
(VO): qnum: 0 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(VI): qnum: 1 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(BE): qnum: 2 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(BK): qnum: 3 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(CAB): qnum: 8 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
------------------ end ------------------------------
------------------ recv ------------------------------
CRC ERR : 217766
DECRYPT CRC ERR : 0
PHY ERR : 459
MIC ERR : 0
PRE-DELIM CRC ERR : 0
POST-DELIM CRC ERR : 15
DECRYPT BUSY ERR : 0
RX-LENGTH-ERR : 0
RX-OOM-ERR : 0
RX-RATE-ERR : 0
RX-TOO-MANY-FRAGS : 0
UNDERRUN ERR : 0
TIMING ERR : 0
PARITY ERR : 0
RATE ERR : 0
LENGTH ERR : 0
RADAR ERR : 0
SERVICE ERR : 0
TOR ERR : 0
OFDM-TIMING ERR : 0
OFDM-SIGNAL-PARITY ERR : 0
OFDM-RATE ERR : 0
OFDM-LENGTH ERR : 0
OFDM-POWER-DROP ERR : 0
OFDM-SERVICE ERR : 0
OFDM-RESTART ERR : 59
FALSE-RADAR-EXT ERR : 0
CCK-TIMING ERR : 0
CCK-HEADER-CRC ERR : 0
CCK-RATE ERR : 0
CCK-SERVICE ERR : 0
CCK-RESTART ERR : 400
CCK-LENGTH ERR : 0
CCK-POWER-DROP ERR : 0
HT-CRC ERR : 0
HT-LENGTH ERR : 0
HT-RATE ERR : 0
RX-Pkts-All : 1754680
RX-Bytes-All : 455156885
RX-Beacons : 208691
RX-Frags : 813
RX-Spectral : 0
------------------ end ------------------------------
------------------ reset ------------------------------
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
MCI Reset: 0
------------------ end ------------------------------
------------------ rx_chainmask ------------------------------
0x00000001
------------------ end ------------------------------
------------------ spectral_count ------------------------------
8
------------------ end ------------------------------
------------------ spectral_fft_period ------------------------------
15
------------------ end ------------------------------
------------------ spectral_period ------------------------------
255
------------------ end ------------------------------
------------------ spectral_scan0 ------------------------------
------------------ end ------------------------------
------------------ spectral_scan_ctl ------------------------------
disable
------------------ end ------------------------------
------------------ spectral_short_repeat ------------------------------
1
------------------ end ------------------------------
------------------ tx_chainmask ------------------------------
0x00000001
------------------ end ------------------------------
------------------ xmit ------------------------------
BE BK VI VO
MPDUs Queued: 5140 680 9 45035
MPDUs Completed: 22900 2002 14 46338
MPDUs XRetried: 827 24 0 95
Aggregates: 38062 212 0 0
AMPDUs Queued HW: 0 0 0 0
AMPDUs Queued SW: 1532444 7611 16 1398
AMPDUs Completed: 1513165 6248 11 0
AMPDUs Retried: 32192 216 0 0
AMPDUs XRetried: 692 17 0 0
TXERR Filtered: 797 5 0 8
FIFO Underrun: 0 0 0 0
TXOP Exceeded: 0 0 0 0
TXTIMER Expiry: 0 0 0 0
DESC CFG Error: 0 0 0 0
DATA Underrun: 0 0 0 0
DELIM Underrun: 0 0 0 0
TX-Pkts-All: 1537584 8291 25 46433
TX-Bytes-All: 1796308981 3275934 5426 7708662
HW-put-tx-buf: 1392072 7988 25 46433
HW-tx-start: 0 0 0 0
HW-tx-proc-desc: 1393023 7989 25 46433
TX-Failed: 0 0 0 0
------------------ end ------------------------------
comment:437 Changed 4 years ago by anonymous
add above information:
I run: iw wlan0 scan. wifi is fine.
compare ath9k debug info,
the ath9k debug info:
------------------ ani ------------------------------
ANI: ENABLED
ANI RESET: 17
SPUR UP: 1190
SPUR DOWN: 1190
OFDM WS-DET ON: 0
OFDM WS-DET OFF: 0
MRC-CCK ON: 0
MRC-CCK OFF: 0
FIR-STEP UP: 916
FIR-STEP DOWN: 921
INV LISTENTIME: 0
OFDM ERRORS: 4755168
CCK ERRORS: 657935
------------------ end ------------------------------
------------------ base_eeprom ------------------------------
EEPROM Version : 2
RegDomain1 : 0
RegDomain2 : 31
TX Mask : 1
RX Mask : 1
Allow 5GHz : 0
Allow 2GHz : 1
Disable 2GHz HT20 : 0
Disable 2GHz HT40 : 0
Disable 5Ghz HT20 : 0
Disable 5Ghz HT40 : 0
Big Endian : 0
RF Silent : 0
BT option : 0
Device Cap : 0
Device Type : 4
Power Table Offset : 0
Tuning Caps1 : 96
Tuning Caps2 : 0
Enable Tx Temp Comp : 1
Enable Tx Volt Comp : 0
Enable fast clock : 1
Enable doubling : 1
Internal regulator : 1
Enable Paprd : 1
Driver Strength : 0
Quick Drop : 0
Chain mask Reduce : 0
Write enable Gpio : 3
WLAN Disable Gpio : 0
WLAN LED Gpio : 8
Rx Band Select Gpio : 255
Tx Gain : 1
Rx Gain : 1
SW Reg : 0
MacAddress : 00:03:7f:be:f1:f5
------------------ end ------------------------------
------------------ chanbw ------------------------------
0x00000000
------------------ end ------------------------------
------------------ diag ------------------------------
0x00000000
------------------ end ------------------------------
------------------ diversity ------------------------------
0
------------------ end ------------------------------
------------------ dma ------------------------------
Raw DMA Debug values:
0: 88888888 1: 00000000 2: 12249249 3: 00000000
4: 00000000 5: 00000000 6: 00192460 7: 00028000
Num QCU: chain_st fsp_ok fsp_st DCU: chain_st
0 0 1 1 0
1 0 1 1 0
2 0 1 1 0
3 0 1 1 0
4 0 1 1 0
5 0 1 1 0
6 0 1 1 0
7 0 1 1 0
8 0 0 1 0
9 0 0 1 0
qcu_stitch state: 0 qcu_fetch state: 0
qcu_complete state: 0 dcu_complete state: 0
dcu_arb state: 0 dcu_fp state: 0
chan_idle_dur: 24 chan_idle_dur_valid: 1
txfifo_valid_0: 0 txfifo_valid_1: 0
txfifo_dcu_num_0: 9 txfifo_dcu_num_1: 12
pcu observe: 0x2880
AR_CR: 0xc
------------------ end ------------------------------
------------------ gpio_mask ------------------------------
0
------------------ end ------------------------------
------------------ gpio_val ------------------------------
0
------------------ end ------------------------------
------------------ ignore_extcca ------------------------------
N
------------------ end ------------------------------
------------------ interrupt ------------------------------
RXLP: 1601988
RXHP: 0
WATHDOG: 0
RXEOL: 17
RXORN: 0
TX: 3977919
TXURN: 0
MIB: 0
RXPHY: 0
RXKCM: 0
SWBA: 20207719
BMISS: 0
BNR: 0
CST: 179
GTT: 3709
TIM: 0
CABEND: 0
DTIMSYNC: 0
DTIM: 0
TSFOOR: 0
MCI: 0
GENTIMER: 0
TOTAL: 25757606
SYNC_CAUSE stats:
Sync-All: 0
RTC-IRQ: 0
MAC-IRQ: 0
EEPROM-Illegal-Access: 0
APB-Timeout: 0
PCI-Mode-Conflict: 0
HOST1-Fatal: 0
HOST1-Perr: 0
TRCV-FIFO-Perr: 0
RADM-CPL-EP: 0
RADM-CPL-DLLP-Abort: 0
RADM-CPL-TLP-Abort: 0
RADM-CPL-ECRC-Err: 0
RADM-CPL-Timeout: 0
Local-Bus-Timeout: 0
PM-Access: 0
MAC-Awake: 0
MAC-Asleep: 0
MAC-Sleep-Access: 0
------------------ end ------------------------------
------------------ misc ------------------------------
BSSID: 00:00:00:00:00:00
BSSID-MASK: ff:ff:ff:ff:ff:ff
OPMODE: AP
RXFILTER: 0x4497 UCAST MCAST BCAST BEACON PROBEREQ COMP_BAR PSPOLL
INTERRUPT-MASK: 0xf0010473 SWBA CST RX RXHP RXLP BB_WATCHDOG
VIF-COUNTS: AP: 1 STA: 0 MESH: 0 WDS: 0 ADHOC: 0 TOTAL: 1 BEACON-VIF: 1
------------------ end ------------------------------
------------------ modal_eeprom ------------------------------
2GHz modal Header :
Chain0 Ant. Control : 336
Chain1 Ant. Control : 336
Chain2 Ant. Control : 336
Ant. Common Control : 272
Ant. Common Control2 : 139810
Ant. Gain : 0
Switch Settle : 44
Chain0 xatten1DB : 0
Chain1 xatten1DB : 0
Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
Temp Slope : 40
Volt Slope : 0
spur Channels0 : 164
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
Chain0 NF Threshold : -1
Chain1 NF Threshold : 0
Chain2 NF Threshold : 0
Quick Drop : 0
txEndToXpaOff : 0
xPA Bias Level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
txFrameToXpaOn : 14
txClip : 3
ADC Desired size : -30
5GHz modal Header :
Chain0 Ant. Control : 0
Chain1 Ant. Control : 0
Chain2 Ant. Control : 0
Ant. Common Control : 272
Ant. Common Control2 : 139810
Ant. Gain : 0
Switch Settle : 45
Chain0 xatten1DB : 0
Chain1 xatten1DB : 0
Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
Temp Slope : 68
Volt Slope : 0
spur Channels0 : 0
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
Chain0 NF Threshold : -1
Chain1 NF Threshold : 0
Chain2 NF Threshold : 0
Quick Drop : 0
txEndToXpaOff : 0
xPA Bias Level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
txFrameToXpaOn : 14
txClip : 3
ADC Desired size : -30
------------------ end ------------------------------
------------------ paprd ------------------------------
N
------------------ end ------------------------------
------------------ qlen_be ------------------------------
123
------------------ end ------------------------------
------------------ qlen_bk ------------------------------
123
------------------ end ------------------------------
------------------ qlen_vi ------------------------------
123
------------------ end ------------------------------
------------------ qlen_vo ------------------------------
123
------------------ end ------------------------------
------------------ queues ------------------------------
(VO): qnum: 0 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(VI): qnum: 1 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(BE): qnum: 2 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(BK): qnum: 3 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
(CAB): qnum: 8 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
------------------ end ------------------------------
------------------ recv ------------------------------
CRC ERR : 217789
DECRYPT CRC ERR : 0
PHY ERR : 460
MIC ERR : 0
PRE-DELIM CRC ERR : 0
POST-DELIM CRC ERR : 15
DECRYPT BUSY ERR : 0
RX-LENGTH-ERR : 0
RX-OOM-ERR : 0
RX-RATE-ERR : 0
RX-TOO-MANY-FRAGS : 0
UNDERRUN ERR : 0
TIMING ERR : 0
PARITY ERR : 0
RATE ERR : 0
LENGTH ERR : 0
RADAR ERR : 0
SERVICE ERR : 0
TOR ERR : 0
OFDM-TIMING ERR : 0
OFDM-SIGNAL-PARITY ERR : 0
OFDM-RATE ERR : 0
OFDM-LENGTH ERR : 0
OFDM-POWER-DROP ERR : 0
OFDM-SERVICE ERR : 0
OFDM-RESTART ERR : 60
FALSE-RADAR-EXT ERR : 0
CCK-TIMING ERR : 0
CCK-HEADER-CRC ERR : 0
CCK-RATE ERR : 0
CCK-SERVICE ERR : 0
CCK-RESTART ERR : 400
CCK-LENGTH ERR : 0
CCK-POWER-DROP ERR : 0
HT-CRC ERR : 0
HT-LENGTH ERR : 0
HT-RATE ERR : 0
RX-Pkts-All : 1754751
RX-Bytes-All : 455193434
RX-Beacons : 208695
RX-Frags : 821
RX-Spectral : 0
------------------ end ------------------------------
------------------ reset ------------------------------
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
MCI Reset: 0
------------------ end ------------------------------
------------------ rx_chainmask ------------------------------
0x00000001
------------------ end ------------------------------
------------------ spectral_count ------------------------------
8
------------------ end ------------------------------
------------------ spectral_fft_period ------------------------------
15
------------------ end ------------------------------
------------------ spectral_period ------------------------------
255
------------------ end ------------------------------
------------------ spectral_scan0 ------------------------------
------------------ end ------------------------------
------------------ spectral_scan_ctl ------------------------------
disable
------------------ end ------------------------------
------------------ spectral_short_repeat ------------------------------
1
------------------ end ------------------------------
------------------ tx_chainmask ------------------------------
0x00000001
------------------ end ------------------------------
------------------ xmit ------------------------------
BE BK VI VO
MPDUs Queued: 5140 680 9 45066
MPDUs Completed: 22900 2002 14 46369
MPDUs XRetried: 827 24 0 95
Aggregates: 38062 212 0 0
AMPDUs Queued HW: 0 0 0 0
AMPDUs Queued SW: 1532444 7611 16 1398
AMPDUs Completed: 1513165 6248 11 0
AMPDUs Retried: 32192 216 0 0
AMPDUs XRetried: 692 17 0 0
TXERR Filtered: 797 5 0 8
FIFO Underrun: 0 0 0 0
TXOP Exceeded: 0 0 0 0
TXTIMER Expiry: 0 0 0 0
DESC CFG Error: 0 0 0 0
DATA Underrun: 0 0 0 0
DELIM Underrun: 0 0 0 0
TX-Pkts-All: 1537584 8291 25 46464
TX-Bytes-All: 1796308981 3275934 5426 7712825
HW-put-tx-buf: 1392072 7988 25 46464
HW-tx-start: 0 0 0 0
HW-tx-proc-desc: 1393023 7989 25 46464
TX-Failed: 0 0 0 0
------------------ end ------------------------------
comment:438 Changed 4 years ago by sash-kan <alex@…>
router: tl-wr1043nd
commit 3f22cca52 (r37825)
[82585.400000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [82585.410000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:439 follow-up: ↓ 440 Changed 4 years ago by nbd
any stability issues along with that, or just the messages in the log?
comment:440 in reply to: ↑ 439 Changed 4 years ago by sash-kan <alex@…>
Replying to nbd:
any stability issues along with that, or just the messages in the log?
most likely "just the messages".
the router is not mine, and they sent me the logs in connection with another error.
comment:441 in reply to: ↑ 434 Changed 4 years ago by anonymous
Replying to miguel.arce@…:
using 10.03.1, right now, with transmission, and no memory problems, it doesnt reboot at all, this is 2.32 right now is 2.82 current openwrt release, i will be testing 2.82 with 10.03.1 as base system to see if it gets out of memory problem.
if it really is transmission > 2.80+ that is causing the out of memory it should reboot with 10.03.1 as well.
I think you're better off starting your own ticket.. Your problem has nothing to do with this ticket.
comment:442 Changed 4 years ago by anonymous
Seeing it today
[48395.870000] ath: phy0: Failed to stop TX DMA, queues=0x006! [52038.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [53471.910000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57541.680000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57551.770000] ath: phy0: Failed to stop TX DMA, queues=0x104! [57567.380000] ath: phy0: Failed to stop TX DMA, queues=0x100! [57570.390000] ath: phy0: Failed to stop TX DMA, queues=0x104! [57570.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57570.960000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57572.630000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57574.830000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57581.830000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57608.910000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57609.250000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57618.210000] ath: phy0: Failed to stop TX DMA, queues=0x104! [57618.760000] ath: phy0: Failed to stop TX DMA, queues=0x004! [57620.220000] ath: phy0: Failed to stop TX DMA, queues=0x004!
Hardware: Mercury MW4530R same hardware as TPLink WDR4300
Software: Attitude Adjustment 12.09.1 r38093
Kernel: 3.3.8
comment:443 Changed 4 years ago by anonymous
I see
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 with r38303. Are there any stats that you'd be interested in?
It doesn't stop working, but it gets very very slow until I do "wifi up".
comment:444 in reply to: ↑ 422 Changed 4 years ago by edmondo
Replying to edmondo:
I've done some testing of r37673 yesterday and it seems stable.
I'll check in the next days if I can confirm this, at the moment it seems positive.
Ok, I tested it a bit longer than two days and a bit less than I wanted... sorry about that.
I'm anyway VERY HAPPY about the stability of r37673. This is the first time I can reliably use the wireless of my TP-Link TL-WR1043ND. So THANKS a lot!!
comment:445 Changed 4 years ago by KadettGTE
@nbd
I haven't checked, but have you tried any of these patches mentioned here?
They seem to be related with this particular issue as well.
https://bbs.archlinux.org/viewtopic.php?pid=1330973#p1330973
comment:446 Changed 4 years ago by anonymous
This is really bad now, just updated to latest trunk from attitude adjustment as I was seeing ath: phy0: Failed to stop TX DMA, queues=0x001! about 100 times a day, now I get ath: phy0: Failed to stop TX DMA, queues=0x005! about every second with openwrt-ar71xx-generic-wzr-hp-g300nh, trunk is almost completely useless due to packet loss.
comment:447 Changed 4 years ago by xosevp
A patch was posted on this thread: http://marc.info/?t=138681280900002
direct link: http://msujith.org/dir/patches/wl/Dec-13-2013/0001-ath9k-Interrupt-handling-fix-for-AR9002-family.patch
comment:448 follow-up: ↓ 449 Changed 4 years ago by tperalta82@…
have you tested it?
comment:449 in reply to: ↑ 448 ; follow-up: ↓ 457 Changed 4 years ago by xosevp
Replying to tperalta82@…:
have you tested it?
No, I'm sorry. Right now my device, WZR-HP-G300NH, is off(it was replaced by WZR-HP-G300NH*2* time ago).
But people with wndr3700v2/3800/mac can give it a try: http://marc.info/?l=linux-wireless&m=138696819824746
comment:450 Changed 4 years ago by mario_lopes
Hi. More problems relating to this:
"ath: phy1: Failed to stop TX DMA, queues=0x004!"
"ath: phy1: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000062c0"
"ath: phy1: Could not stop RX, we could be confusing the DMA engine when we start RX up"
"ath: phy1: Failed to stop TX DMA, queues=0x004!"
(the last message repeats several times in dmesg until system halts)
This appens on iperf TCP client which is generating traffic on R52n-M NIC, the system running iperf in server mode remain stable.
Iperf in client mode on other interfaces cause no problems at all (XR7 and 100Base-T).
Running OpenWrt Barrier Breaker r39088 generic x86, on Alix 3D3 + Ubiquity XR7 + RouterBOARD R52n-M (ath9k - AR9220).
On OpenWRT 12.09-rc1 and 12.09 final this problem does not occurs.
Thanks.
comment:451 Changed 4 years ago by javier@…
Still broken in r39096
ath: phy0: Failed to stop TX DMA
comment:452 Changed 4 years ago by mario_lopes
comment:453 Changed 4 years ago by javier@…
If I knew this bug was open for 2 years, I would have never bought a device based on the atheros platform.
comment:454 Changed 4 years ago by valentt
I would just suggest that you sell wr1043 and but a cheaper model because wr741, wr841 and wr941 AFAIK aren't suffering from this bug and are working perfectly. If I'm wrong please correct me, but I have used lots of wr741 and wr841 routers and had no issue with them whatsoever...
comment:455 follow-up: ↓ 456 Changed 4 years ago by javier@…
@valentt, Do they use the ath9k driver in those models?
I rather just change the platform because from what I find, this DMA issue is in the upstream linux kernel. If I am wrong then perhaps its a hardware issue and needs a work around. my work around is a cron job that executes /sbin/wifi ever hour to keep things up and running.
comment:456 in reply to: ↑ 455 Changed 4 years ago by valentt
Replying to javier@…:
@valentt, Do they use the ath9k driver in those models?
Yes they also use ath9k, but it seams that only wr1043nd model has this issue, I have been using lost of atheros based routers for last two years and only had issues with wr1043nd model. If anybody else has issue with any other model please let us know, but I didn't.
I rather just change the platform because from what I find, this DMA issue is in the upstream linux kernel. If I am wrong then perhaps its a hardware issue and needs a work around. my work around is a cron job that executes /sbin/wifi ever hour to keep things up and running.
Atheros is really rock solid platform, only issue is this one tp-link model, I would prefer atheros over most other platforms, which ones are you considering? Which exact models of routers?
comment:457 in reply to: ↑ 449 Changed 4 years ago by anonymous
Replying to xosevp:
Replying to tperalta82@…:
have you tested it?
No, I'm sorry. Right now my device, WZR-HP-G300NH, is off(it was replaced by WZR-HP-G300NH*2* time ago).
But people with wndr3700v2/3800/mac can give it a try: http://marc.info/?l=linux-wireless&m=138696819824746
Took a look at the patch, and actually it is already on the tree, so I guess we will have to wait a little longer.
comment:458 Changed 4 years ago by mikaelbrostrom
nbd, i sent you an email with a link to the source-code of atheros driver used in stock firmware.
hope it helps :)
comment:459 Changed 4 years ago by javier@…
So I did 2 things today.
1st: I did s sysupgrade to latest firmware.
I am now on r39185.
2nd: I setup a cisco AM10 on the USB port (so i have a backup/test radio)
I am on a TP-Link 1043ND V1.8
Here is some interesting dmesg output:
[ 4099.610000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 0
[ 4099.620000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 0
[ 4099.630000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 0
[ 4099.640000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 0
[ 4099.650000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 0
[ 4100.940000] br-lan: port 3(wlan0) entered forwarding state
[ 4339.730000] ath: phy1: Failed to stop TX DMA, queues=0x004!
[ 4474.670000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[ 4474.680000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[ 4474.690000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[ 4474.700000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[ 4474.710000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[ 4474.720000] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2
[ 4527.440000] ath: phy1: Failed to stop TX DMA, queues=0x105!
I am getting TX timeout warnings on the AM10 dongle as well as the ath radio.
Not sure if they are related but might be of interest.
comment:460 Changed 4 years ago by mario_lopes
More info:
- On revision 36080 (shown as revision 36080) problem persists
- On revision 36088 (shown as revision 36085) problem persists
- On revision 36088 (shown as revision 36088, downloaded image of Attitude adjustment) no problem at all
- On revision 36099 (shown as revision 36099) problem persists
- On revision 39404 (shown as revision 39404) problem persists
comment:461 Changed 4 years ago by Romain Riviere <net+wrt@…>
I'm using a downloaded image of AA, shown as rev 36088, and the problem still crops up fairly regularly, though not as often as before. I went the cron way, and a daily restart of the wireless is enough for me.
Also, I've had a couple of severe enough issues causing a trace to appear:
[7193491.940000] ------------[ cut here ]------------ [7193491.940000] WARNING: at /build/ar71xx/generic/build_dir/linux-ar71xx_generic/compat-wireless-2012-09-07/net/mac80211/rx.c:3087 0x80d19fd4() [7193491.960000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 77 (0x4d) [7193491.970000] Modules linked in: xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length xt_DSCP xt_dscp xt_recent xt_helper xt_connmark xt_connbytes ip6t_REJECT ip6t_LOG ip6t_rt ip6t_hbh ip 6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables nf_conntrack_ipv6 nf_defrag_ipv6 sit tunnel4 ipv6 ath79_wdt ohci_hcd ledtrig_usbdev ledtrig_netdev nf_nat_ir c nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat pppoe xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd pppox ipt_REJECT xt_TCPMSS ipt_L OG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k(O) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base crc_ccitt cf g80211(O) compat(O) arc4 aes_generic crypto_algapi ledtrig_timer ledtrig_default_on leds_gpio gpio_button_hotplug(O) [last unloaded: gre] [7193492.060000] Call Trace:[<80284158>] 0x80284158 [7193492.060000] [<80284158>] 0x80284158 [7193492.070000] [<80071a0c>] 0x80071a0c [7193492.070000] [<80d19fd4>] 0x80d19fd4 [7193492.070000] [<80071ac0>] 0x80071ac0 [7193492.080000] [<80d19fd4>] 0x80d19fd4 [7193492.080000] [<801e1ed4>] 0x801e1ed4 [7193492.090000] [<801e3360>] 0x801e3360 [7193492.090000] [<80de6d44>] 0x80de6d44 [7193492.090000] [<8009c728>] 0x8009c728 [7193492.100000] [<80165ac4>] 0x80165ac4 [7193492.100000] [<80de4f98>] 0x80de4f98 [7193492.100000] [<80076b10>] 0x80076b10 [7193492.110000] [<80077038>] 0x80077038 [7193492.110000] [<80077248>] 0x80077248 [7193492.110000] [<800a85e0>] 0x800a85e0 [7193492.120000] [<8007747c>] 0x8007747c [7193492.120000] [<800630ec>] 0x800630ec [7193492.130000] [<800632c0>] 0x800632c0 [7193492.130000] [<80095320>] 0x80095320 [7193492.130000] [<800a8314>] 0x800a8314 [7193492.140000] [<80064b28>] 0x80064b28 [7193492.140000] [<800632e0>] 0x800632e0 [7193492.140000] [<802f28b4>] 0x802f28b4 [7193492.150000] [<80318850>] 0x80318850 [7193492.150000] [<802f20dc>] 0x802f20dc [7193492.160000] [7193492.160000] ---[ end trace 97aa72432f72e18a ]---
comment:462 follow-up: ↓ 463 Changed 4 years ago by nbd
please try r39688 or newer
comment:463 in reply to: ↑ 462 Changed 4 years ago by morckman@…
Replying to nbd:
please try r39688 or newer
running r39729 for 22h gives me:
[ 1317.640000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0 [ 1317.650000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
but the wlan connection is still stable and usable.
comment:464 Changed 4 years ago by doooku
I have same issue (r39585) on tp-link 1043nd
... [ 216.430000] br-lan: port 2(wlan0) entered forwarding state [ 692.040000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 709.490000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 871.480000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 992.530000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1071.660000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1118.580000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1120.440000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1125.620000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1145.780000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1164.740000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1264.900000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1471.480000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1551.780000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1674.570000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1728.730000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1732.550000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1867.330000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 1974.810000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 3332.180000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 3814.300000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4613.390000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4822.010000] ath: phy0: Failed to stop TX DMA, queues=0x004! [ 4878.720000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:465 Changed 4 years ago by doooku
comment:466 Changed 4 years ago by nbd
comment:467 Changed 4 years ago by anonymous
I have same issue r39757 on tp-link 1043nd v1.2
Fri Feb 28 16:10:02 2014 kern.err kernel: [ 489.860000] ath: phy0: Failed to stop TX DMA, queues=0x004! Fri Feb 28 16:10:03 2014 kern.err kernel: [ 491.600000] ath: phy0: Failed to stop TX DMA, queues=0x004! Fri Feb 28 16:10:04 2014 kern.err kernel: [ 491.910000] ath: phy0: Failed to stop TX DMA, queues=0x004! Fri Feb 28 16:10:06 2014 kern.err kernel: [ 494.470000] ath: phy0: Failed to stop TX DMA, queues=0x004! Fri Feb 28 16:10:12 2014 kern.err kernel: [ 500.710000] ath: phy0: Failed to stop TX DMA, queues=0x004! Fri Feb 28 16:10:18 2014 kern.err kernel: [ 505.730000] ath: phy0: Failed to stop TX DMA, queues=0x004! Fri Feb 28 16:10:19 2014 kern.err kernel: [ 507.570000] ath: phy0: Failed to stop TX DMA, queues=0x004!
comment:468 Changed 4 years ago by nbd
r39767 should also improve stability
comment:469 Changed 4 years ago by wevie
Just installed r39770 on my TP-link 1043nd v1.8, within 5 minutes I get:
[ 805.490000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028cc0
[ 805.500000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:470 Changed 4 years ago by anonymous
Updated to r39770 4 days ago on TP-Link 1043nd. Wireless is for me usable since I updated to r37673.
Firmware Version OpenWrt Barrier Breaker r39770 / LuCI Trunk (svn-r9960)
Uptime 4d 0h 16m 34s
This is in my log file:
[197781.950000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
[197781.960000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
comment:471 follow-up: ↓ 472 Changed 4 years ago by anonymous
I've similar message in my dmesg as well:
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000042c0
[132410.010000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Mine is a Buffalo AG300H, using self-built r39876 eglibc compiled with -O2 -mips32r2 with MIPS16 option enabled.
comment:472 in reply to: ↑ 471 Changed 4 years ago by anonymous
Replying to anonymous:
Sorry forget to update although the message pops up all my WIFI devices seem to work properly.
I've similar message in my dmesg as well:
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000042c0
[132410.010000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Mine is a Buffalo AG300H, using self-built r39876 eglibc compiled with -O2 -mips32r2 with MIPS16 option enabled.
comment:473 follow-up: ↓ 474 Changed 4 years ago by bittorf@…
ok r39888 here on TP-LINK TL-WR1043ND v1 in AP-mode/20MHz - alot of:
[ 9891.470000] ath: phy0: Failed to stop TX DMA, queues=0x005! [ 9894.950000] ath: phy0: Failed to stop TX DMA, queues=0x005! [ 9908.360000] ath: phy0: Failed to stop TX DMA, queues=0x004!
root@box:~ cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
MAC Hang: 380
Stuck Beacon: 233
MCI Reset: 0
what else can i provide?
comment:474 in reply to: ↑ 473 Changed 4 years ago by bittorf@…
Replying to bittorf@…:
ok r39888 here on TP-LINK TL-WR1043ND v1 in AP-mode/20MHz - alot of:
i double-checked: the wifi-mode is hybrid = adhoc + ap
root@box:~ uci show wireless wireless.radio0=wifi-device wireless.radio0.type=mac80211 wireless.radio0.country=US wireless.radio0.channel=11 wireless.radio0.macaddr=f4:ec:38:c9:c3:2c wireless.radio0.frag=off wireless.radio0.hwmode=11ng wireless.radio0.ht_capab=SHORT-GI-40 DSSS_CCK-40 wireless.radio0.beacon_int=100 wireless.@wifi-iface[0]=wifi-iface wireless.@wifi-iface[0].device=radio0 wireless.@wifi-iface[0].network=wlanadhoc wireless.@wifi-iface[0].mode=adhoc wireless.@wifi-iface[0].bssid=02:ca:ff:ee:00:11 wireless.@wifi-iface[0].ssid=x wireless.@wifi-iface[1]=wifi-iface wireless.@wifi-iface[1].device=radio0 wireless.@wifi-iface[1].network=wlan wireless.@wifi-iface[1].mode=ap wireless.@wifi-iface[1].ssid=myssid
comment:475 Changed 4 years ago by tperalta82@…
11 Days uptime for my TP-LINK TL-WDR3600 with no messages on dmesg, everything seems stable.
root@SPAWN:~# uptime
12:26:47 up 11 days, 17:58, load average: 0.28, 0.12, 0.15
root@SPAWN:~#
root@SPAWN:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 119
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
MCI Reset: 0
BARRIER BREAKER (Bleeding Edge, r39535)
wireless.radio0=wifi-device
wireless.radio0.type=mac80211
wireless.radio0.hwmode=11ng
wireless.radio0.path=platform/ar934x_wmac
wireless.radio0.ht_capab=LDPC SHORT-GI-20 SHORT-GI-40 TX-STBC RX-STBC1 DSSS_CCK- 40
wireless.radio0.disabled=0
wireless.radio0.country=IE
wireless.radio0.channel=1
wireless.radio0.txpower=20
wireless.radio0.htmode=HT40+
wireless.@wifi-iface[0]=wifi-iface
wireless.@wifi-iface[0].device=radio0
wireless.@wifi-iface[0].network=lan
wireless.@wifi-iface[0].mode=ap
wireless.@wifi-iface[0].ssid=xxxxx
wireless.@wifi-iface[0].encryption=psk2
wireless.@wifi-iface[0].key=xxxxx
wireless.radio1=wifi-device
wireless.radio1.type=mac80211
wireless.radio1.hwmode=11na
wireless.radio1.path=pci0000:00/0000:00:00.0
wireless.radio1.ht_capab=LDPC SHORT-GI-20 SHORT-GI-40 TX-STBC RX-STBC1 DSSS_CCK- 40
wireless.radio1.disabled=0
wireless.radio1.txpower=17
wireless.radio1.country=IE
wireless.radio1.channel=40
wireless.radio1.htmode=HT20
wireless.@wifi-iface[1]=wifi-iface
wireless.@wifi-iface[1].device=radio1
wireless.@wifi-iface[1].network=lan
wireless.@wifi-iface[1].mode=ap
wireless.@wifi-iface[1].ssid=xxxx
wireless.@wifi-iface[1].encryption=psk2
wireless.@wifi-iface[1].key=xxxx
comment:476 follow-up: ↓ 477 Changed 4 years ago by skaapgif
TP-LINK TL-WR1043ND (Attitude Adjustment, r39952), which has many of these patches backported.
I get much more "ath: phy0: Failed to stop TX DMA" errors than on the 12.09 release. On the 12.09 release I'd get a few here and there, now there's a whole string of messages.
comment:477 in reply to: ↑ 476 Changed 4 years ago by skaapgif
# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 0
PLL RX Hang: 0
MAC Hang: 159
Stuck Beacon: 25
MCI Reset: 0
# uptime
05:17:49 up 13:55, load average: 0.00, 0.01, 0.04
Replying to skaapgif:
TP-LINK TL-WR1043ND (Attitude Adjustment, r39952), which has many of these patches backported.
I get much more "ath: phy0: Failed to stop TX DMA" errors than on the 12.09 release. On the 12.09 release I'd get a few here and there, now there's a whole string of messages.
comment:478 follow-ups: ↓ 517 ↓ 519 ↓ 520 Changed 4 years ago by pedro@…
I seem to be hitting this issue on 12.09 on a wr1043nd. Adding a comment here as Trac account register seems to be broken and there doesn't seem to be a way to just subscribe to the bug report. Sorry for the spam.