[1.5.4][TL-WR1043ND] Incredibly huge ping times to router

[raz]

This has just started, I presume that a reboot would fix things. Nevertheless, this definitely sounds like a major bug.

Code: Select all

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2052ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2019ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1963ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=807ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2109ms TTL=64
Reply from 192.168.1.1: bytes=32 time=583ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1762ms TTL=64
Reply from 192.168.1.1: bytes=32 time=758ms TTL=64
Reply from 192.168.1.1: bytes=32 time=913ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 583ms, Maximum = 2109ms, Average = 1440ms

TL-WR1043ND, running Gargoyle 1.5.4

Memory usage: 14MB/28.8MB (48.6%)
Connections: 190/12288
CPU Load Averages: 0.00/0.00/0.00 (1/5/15 minutes)
Uptime: 2 days, 9 hours, 58 minutes


Nothing unusual in the logread, but dmesg spits this over and over:

Code: Select all

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

Any clues?

[pbix]

I agree that this is strange and I do not know the reason. Perhaps someone here on this forum will comment but I suggest you also start a thread over at openwrt.org. They are the one who authored the driver in question and may be able to comment.

[raz]

Hmm,

Looks like the following may/may not fix it.. guess we'll have to wait for the next Gargoyle release to include it?

https://dev.openwrt.org/changeset/30919

[raz]

Hmm.. happened again.. starting to get annoying .

Would anyone know if it is possible to have the router auto-reboot when a few successive DMA errors occur?

[raz]

Interesting reply from the OpenWRT forum:

Hello, those RX messages are a known issue with the 10.03.1 -RCX.

I currently have TL-WR1043ND with 10.03.1 Final (dec 2011), and no more RX messages, awesome stability with transfers, etc.

AFAIK, Gargoyle 1.5.4 is based on OpenWRT 10.03.1 R30752, correct?
Is that considered more recent than the version the above poster refers to?

Also, something of interest: the Gargoyle 1.3.x "doritos" custom build was rock solid for the 1043ND. Sad to see a regression in drivers.

[mix]

Unless your fix is backported to backfire, nothing will change:

https://dev.openwrt.org/log/branches/ba ... ollow_copy

But yes, Gargoyle 1.5.4 is based on newer code than 10.03.1 final. So it should have any claimed fixes compiled in. There have been many reports of the dma stop error on Atheros routers in the past on this message board.

[DoesItMatter]

I'm running a very recent trunk build I compiled myself.

See the info in my signature

Seems VERY stable - but, this is just OpenWRT - it's a LOT of work
that I unfortunately don't have time for, to compile trunk + Gargoyle

If some of you 1043ND users want to try a trunk OpenWRT build
and can't compile, reply here and I'll post the builds.

This is just vanilla OpenWRT with the LuCI GUI for easier configs.

[raz]

I'd love to try it.. had to reboot again today.

Please post!

Edit: OH, just noticed that you were talking about an OpenWRT build. I need Gargoyle's stats and QoS, so I guess I'll have to wait until a new Gargoyle build is realeased

[raz]

Another (separate?) issue:

This is the graph produced by pinging the router over a period of 30 minutes, when connected wirelessly.


Full graph here.

We can see periodic spiking in latency.

I redid the same exercise but connected directly to the router using a physical LAN connection. The latency never went beyond 2ms, with none of the period spikes seen over the wireless connection.

Concerning the spikes: What may be the cause? Can someone else try this on their setup? I used a tool called MultiPing (by Nessoft).

[mix]

Wireless interference? A microwave oven or another wireless router in range? What does a program like InSSIDer show?