Modify

Opened 5 years ago

Closed 5 years ago

#12501 closed defect (duplicate)

DMA and RX stop failed errors in WR740N_v4.21 kernel log

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: DMA Cc:

Description

Can this indicate a hardware error?
This router needs to be turned OFF and ON again almost every day to get the WiFi radio working.
This device doesn't even handle too much load.
Or is it a software problem...?

I could sometimes cactch some similar error messages with both 3.3.8 and 3.6.7 kernels:

[   26.970000] br-lan: port 2(wlan0) entered forwarding state
[ 8755.960000] device wlan0 left promiscuous mode
[ 8755.960000] br-lan: port 2(wlan0) entered disabled state
[ 8756.960000] device wlan0 entered promiscuous mode
[ 8757.250000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 8757.260000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 8757.270000] br-lan: port 2(wlan0) entered forwarding state
[ 8757.280000] br-lan: port 2(wlan0) entered forwarding state
[ 8757.490000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 8757.500000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 8759.280000] br-lan: port 2(wlan0) entered forwarding state
[ 8792.750000] device wlan0 left promiscuous mode
[ 8792.750000] br-lan: port 2(wlan0) entered disabled state
[ 8793.740000] device wlan0 entered promiscuous mode
[ 8794.020000] br-lan: port 2(wlan0) entered forwarding state
[ 8794.030000] br-lan: port 2(wlan0) entered forwarding state
[ 8796.030000] br-lan: port 2(wlan0) entered forwarding state
[ 9136.640000] device wlan0 left promiscuous mode
[ 9136.640000] br-lan: port 2(wlan0) entered disabled state
[ 9138.370000] device wlan0 entered promiscuous mode
[ 9138.460000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9138.470000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9138.610000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9138.610000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9138.760000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9138.760000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9138.910000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9138.910000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9139.060000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9139.060000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9139.210000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9139.210000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9139.360000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9139.360000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9139.510000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9139.510000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9139.660000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9139.660000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9139.810000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9139.810000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9140.050000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9140.060000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9140.070000] br-lan: port 2(wlan0) entered forwarding state
[ 9140.080000] br-lan: port 2(wlan0) entered forwarding state
[ 9140.290000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9140.300000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9142.080000] br-lan: port 2(wlan0) entered forwarding state
[ 9391.220000] device wlan0 left promiscuous mode
[ 9391.220000] br-lan: port 2(wlan0) entered disabled state
[ 9392.950000] device wlan0 entered promiscuous mode
[ 9393.440000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9393.450000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9393.470000] br-lan: port 2(wlan0) entered forwarding state
[ 9393.470000] br-lan: port 2(wlan0) entered forwarding state
[ 9393.690000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006400
[ 9393.700000] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[ 9395.470000] br-lan: port 2(wlan0) entered forwarding state
[23551.900000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.

Attachments (0)

Change History (1)

comment:1 Changed 5 years ago by jow

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

Add Comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.