[ath9k-devel] Ath9k packets dropping issue

All of lore.kernel.org
 help / color / mirror / Atom feed

* [ath9k-devel] Ath9k packets dropping issue
@ 2009-03-02 18:30 Wang Jian
  2009-03-03 14:06 ` Yura
  0 siblings, 1 reply; 4+ messages in thread
From: Wang Jian @ 2009-03-02 18:30 UTC (permalink / raw)
  To: ath9k-devel

Hi there,

I am using openwrt on TL-WR941ND, using dev snapshot build ( http://downloads.openwrt.org/people/agb/ar71xx-ath9k-snapshots/ ).

  root at OpenWrt:~# uname -a
  Linux OpenWrt 2.6.28.7 #2 Sat Feb 28 23:35:50 PST 2009 mips unknown

TL-WR941ND is an consumer router based on AP81, using AR9132/AR9103 chips (per RoundSparrow).

I notice strange packets dropping, for example, I can (telnet) connect from wireless client to the other side of (wired) network to port 22, but got stuck when connection established. After random but
long freezing time, I get ssh banner. But ping from wireless client to the other side of (wired) network is very smooth.

The scenario:

A(XP box) .......(wireless)...... B (WR941N as pure AP) ------------(wired)------------ C(Linux box)
 192.168.0.121                          192.168.1.1                                     192.168.0.254

1. A ping C: very smooth
2. C ping A: most ping lost, with one or two responses out of 40+ pings

I silent A by closing most packet sending program, run sniffers (wireshark or tcpdump) on A,B,C, and watch tx/rx counters of B's wlan0 interface. Then I run ping from A to C, and C to A.

1. For every ping packets A sends to C, B's rx and tx counter increase.
2. For nearly every ping packets C sends to A, B's tx counter increases, A doesn't receive this ping, B's rx counter stays unchanged.
3. Every a few seconds, arp requests occurs, and C may get one and only one ping response.
4. All ping request shows itself in B's tcpdump output.

So, things get clear here: B seems only succeed to do tx after rx on wireless interface.

This looks like queue related problem or interrupt handler problem.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] Ath9k packets dropping issue
  2009-03-02 18:30 [ath9k-devel] Ath9k packets dropping issue Wang Jian
@ 2009-03-03 14:06 ` Yura
  2009-03-03 14:21   ` Wang Jian
  0 siblings, 1 reply; 4+ messages in thread
From: Yura @ 2009-03-03 14:06 UTC (permalink / raw)
  To: ath9k-devel

Hello Wang,

It seems that I have very similar issues with Intel cards in 11n mode. Are you
using an Intel card at client side too?

I've noticed that packets coming from wired to wireless are actually not
dropped, but are queued and thrown every 5-8 seconds. Here is the
example of ping output:


PING 10.0.0.133 (10.0.0.133) 56(84) bytes of data.
64 bytes from 10.0.0.133: icmp_seq=1 ttl=128 time=1264 ms
64 bytes from 10.0.0.133: icmp_seq=2 ttl=128 time=265 ms
64 bytes from 10.0.0.133: icmp_seq=3 ttl=128 time=6668 ms
64 bytes from 10.0.0.133: icmp_seq=4 ttl=128 time=5668 ms
64 bytes from 10.0.0.133: icmp_seq=5 ttl=128 time=4668 ms
64 bytes from 10.0.0.133: icmp_seq=6 ttl=128 time=3669 ms
64 bytes from 10.0.0.133: icmp_seq=7 ttl=128 time=2669 ms
64 bytes from 10.0.0.133: icmp_seq=8 ttl=128 time=1669 ms
64 bytes from 10.0.0.133: icmp_seq=9 ttl=128 time=669 ms
64 bytes from 10.0.0.133: icmp_seq=10 ttl=128 time=7070 ms
64 bytes from 10.0.0.133: icmp_seq=11 ttl=128 time=6070 ms
64 bytes from 10.0.0.133: icmp_seq=12 ttl=128 time=5070 ms
64 bytes from 10.0.0.133: icmp_seq=13 ttl=128 time=4071 ms
64 bytes from 10.0.0.133: icmp_seq=14 ttl=128 time=3071 ms
64 bytes from 10.0.0.133: icmp_seq=15 ttl=128 time=2071 ms
64 bytes from 10.0.0.133: icmp_seq=16 ttl=128 time=1071 ms
64 bytes from 10.0.0.133: icmp_seq=17 ttl=128 time=71.6 ms
64 bytes from 10.0.0.133: icmp_seq=18 ttl=128 time=6476 ms
64 bytes from 10.0.0.133: icmp_seq=19 ttl=128 time=5476 ms
64 bytes from 10.0.0.133: icmp_seq=20 ttl=128 time=4476 ms
64 bytes from 10.0.0.133: icmp_seq=21 ttl=128 time=3476 ms
64 bytes from 10.0.0.133: icmp_seq=22 ttl=128 time=2476 ms
64 bytes from 10.0.0.133: icmp_seq=23 ttl=128 time=1476 ms
64 bytes from 10.0.0.133: icmp_seq=24 ttl=128 time=477 ms
64 bytes from 10.0.0.133: icmp_seq=25 ttl=128 time=6875 ms
64 bytes from 10.0.0.133: icmp_seq=26 ttl=128 time=5877 ms
64 bytes from 10.0.0.133: icmp_seq=27 ttl=128 time=4878 ms
64 bytes from 10.0.0.133: icmp_seq=28 ttl=128 time=3878 ms
64 bytes from 10.0.0.133: icmp_seq=29 ttl=128 time=2878 ms
64 bytes from 10.0.0.133: icmp_seq=30 ttl=128 time=1879 ms
64 bytes from 10.0.0.133: icmp_seq=31 ttl=128 time=879 ms
64 bytes from 10.0.0.133: icmp_seq=32 ttl=128 time=7282 ms
64 bytes from 10.0.0.133: icmp_seq=33 ttl=128 time=6284 ms
64 bytes from 10.0.0.133: icmp_seq=34 ttl=128 time=5284 ms
64 bytes from 10.0.0.133: icmp_seq=35 ttl=128 time=4284 ms
64 bytes from 10.0.0.133: icmp_seq=36 ttl=128 time=3284 ms
64 bytes from 10.0.0.133: icmp_seq=37 ttl=128 time=2284 ms
64 bytes from 10.0.0.133: icmp_seq=38 ttl=128 time=1286 ms
64 bytes from 10.0.0.133: icmp_seq=39 ttl=128 time=286 ms
64 bytes from 10.0.0.133: icmp_seq=40 ttl=128 time=6685 ms
64 bytes from 10.0.0.133: icmp_seq=41 ttl=128 time=5686 ms
64 bytes from 10.0.0.133: icmp_seq=42 ttl=128 time=4686 ms
64 bytes from 10.0.0.133: icmp_seq=43 ttl=128 time=3686 ms
64 bytes from 10.0.0.133: icmp_seq=44 ttl=128 time=2686 ms
64 bytes from 10.0.0.133: icmp_seq=45 ttl=128 time=1686 ms
64 bytes from 10.0.0.133: icmp_seq=46 ttl=128 time=686 ms
64 bytes from 10.0.0.133: icmp_seq=47 ttl=128 time=7087 ms
64 bytes from 10.0.0.133: icmp_seq=48 ttl=128 time=6088 ms
64 bytes from 10.0.0.133: icmp_seq=49 ttl=128 time=5088 ms
64 bytes from 10.0.0.133: icmp_seq=50 ttl=128 time=4088 ms
64 bytes from 10.0.0.133: icmp_seq=51 ttl=128 time=3088 ms
64 bytes from 10.0.0.133: icmp_seq=52 ttl=128 time=2088 ms
64 bytes from 10.0.0.133: icmp_seq=53 ttl=128 time=1088 ms
64 bytes from 10.0.0.133: icmp_seq=54 ttl=128 time=88.9 ms
64 bytes from 10.0.0.133: icmp_seq=55 ttl=128 time=6490 ms
64 bytes from 10.0.0.133: icmp_seq=56 ttl=128 time=5490 ms
64 bytes from 10.0.0.133: icmp_seq=57 ttl=128 time=4490 ms
64 bytes from 10.0.0.133: icmp_seq=58 ttl=128 time=3490 ms
64 bytes from 10.0.0.133: icmp_seq=59 ttl=128 time=2490 ms
64 bytes from 10.0.0.133: icmp_seq=60 ttl=128 time=1490 ms
64 bytes from 10.0.0.133: icmp_seq=61 ttl=128 time=490 ms
64 bytes from 10.0.0.133: icmp_seq=62 ttl=128 time=6895 ms
64 bytes from 10.0.0.133: icmp_seq=63 ttl=128 time=5895 ms
64 bytes from 10.0.0.133: icmp_seq=64 ttl=128 time=4895 ms
64 bytes from 10.0.0.133: icmp_seq=66 ttl=128 time=3011 ms
64 bytes from 10.0.0.133: icmp_seq=67 ttl=128 time=2011 ms
64 bytes from 10.0.0.133: icmp_seq=70 ttl=128 time=3.15 ms
64 bytes from 10.0.0.133: icmp_seq=71 ttl=128 time=6402 ms
64 bytes from 10.0.0.133: icmp_seq=72 ttl=128 time=5402 ms
64 bytes from 10.0.0.133: icmp_seq=73 ttl=128 time=4402 ms
64 bytes from 10.0.0.133: icmp_seq=74 ttl=128 time=3402 ms
64 bytes from 10.0.0.133: icmp_seq=75 ttl=128 time=2402 ms
64 bytes from 10.0.0.133: icmp_seq=76 ttl=128 time=1402 ms
64 bytes from 10.0.0.133: icmp_seq=77 ttl=128 time=403 ms
64 bytes from 10.0.0.133: icmp_seq=78 ttl=128 time=3.21 ms
64 bytes from 10.0.0.133: icmp_seq=79 ttl=128 time=6397 ms
64 bytes from 10.0.0.133: icmp_seq=80 ttl=128 time=5397 ms
64 bytes from 10.0.0.133: icmp_seq=81 ttl=128 time=4397 ms
64 bytes from 10.0.0.133: icmp_seq=82 ttl=128 time=3398 ms
64 bytes from 10.0.0.133: icmp_seq=83 ttl=128 time=2398 ms
64 bytes from 10.0.0.133: icmp_seq=84 ttl=128 time=1398 ms
64 bytes from 10.0.0.133: icmp_seq=85 ttl=128 time=398 ms
64 bytes from 10.0.0.133: icmp_seq=86 ttl=128 time=3.13 ms
64 bytes from 10.0.0.133: icmp_seq=87 ttl=128 time=6405 ms
64 bytes from 10.0.0.133: icmp_seq=88 ttl=128 time=5405 ms
64 bytes from 10.0.0.133: icmp_seq=89 ttl=128 time=4405 ms
64 bytes from 10.0.0.133: icmp_seq=90 ttl=128 time=3405 ms
64 bytes from 10.0.0.133: icmp_seq=91 ttl=128 time=2405 ms
64 bytes from 10.0.0.133: icmp_seq=92 ttl=128 time=1406 ms
64 bytes from 10.0.0.133: icmp_seq=93 ttl=128 time=406 ms
64 bytes from 10.0.0.133: icmp_seq=94 ttl=128 time=6807 ms
64 bytes from 10.0.0.133: icmp_seq=95 ttl=128 time=5807 ms
64 bytes from 10.0.0.133: icmp_seq=96 ttl=128 time=4808 ms
64 bytes from 10.0.0.133: icmp_seq=97 ttl=128 time=3808 ms
64 bytes from 10.0.0.133: icmp_seq=98 ttl=128 time=2808 ms
64 bytes from 10.0.0.133: icmp_seq=99 ttl=128 time=1808 ms
64 bytes from 10.0.0.133: icmp_seq=100 ttl=128 time=808 ms
64 bytes from 10.0.0.133: icmp_seq=101 ttl=128 time=7209 ms
64 bytes from 10.0.0.133: icmp_seq=102 ttl=128 time=6210 ms
64 bytes from 10.0.0.133: icmp_seq=103 ttl=128 time=5210 ms
64 bytes from 10.0.0.133: icmp_seq=104 ttl=128 time=4210 ms
64 bytes from 10.0.0.133: icmp_seq=105 ttl=128 time=3210 ms
64 bytes from 10.0.0.133: icmp_seq=106 ttl=128 time=2210 ms
64 bytes from 10.0.0.133: icmp_seq=107 ttl=128 time=1210 ms
64 bytes from 10.0.0.133: icmp_seq=108 ttl=128 time=210 ms

--- 10.0.0.133 ping statistics ---
111 packets transmitted, 105 received, 5% packet loss, time 110051ms
rtt min/avg/max/mdev = 3.138/3495.188/7282.109/2175.738 ms, pipe 8






-- 
Best regards,
 Yura                            mailto:gt at ukr.net

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] Ath9k packets dropping issue
  2009-03-03 14:06 ` Yura
@ 2009-03-03 14:21   ` Wang Jian
  2009-03-03 23:02     ` Yura
  0 siblings, 1 reply; 4+ messages in thread
From: Wang Jian @ 2009-03-03 14:21 UTC (permalink / raw)
  To: ath9k-devel

Hi Yura,

Yes I am using T500, wireless card is Intel WiFi Link 5100 AGN. It looks like
your router also have queue problem, but there is difference.

In my test, even I keep two ping (A to C while C to A) running at the same time,
C to A pings almost dropped. Only when arp packets flush through, the C to A ping
can get through, but one packet a time. It seems the problem occurs with timing
pattern.

But you confirm one thing: ath9k driver has tx problem.

Can you run some sniffer and see what packets trigger the burst out?

Yura wrote:
> Hello Wang,
> 
> It seems that I have very similar issues with Intel cards in 11n mode. Are you
> using an Intel card at client side too?
> 
> I've noticed that packets coming from wired to wireless are actually not
> dropped, but are queued and thrown every 5-8 seconds. Here is the
> example of ping output:
> 
> 
> PING 10.0.0.133 (10.0.0.133) 56(84) bytes of data.
> 64 bytes from 10.0.0.133: icmp_seq=1 ttl=128 time=1264 ms
> 64 bytes from 10.0.0.133: icmp_seq=2 ttl=128 time=265 ms
> 64 bytes from 10.0.0.133: icmp_seq=3 ttl=128 time=6668 ms
> 64 bytes from 10.0.0.133: icmp_seq=4 ttl=128 time=5668 ms
> 64 bytes from 10.0.0.133: icmp_seq=5 ttl=128 time=4668 ms
> 64 bytes from 10.0.0.133: icmp_seq=6 ttl=128 time=3669 ms
> 64 bytes from 10.0.0.133: icmp_seq=7 ttl=128 time=2669 ms
> 64 bytes from 10.0.0.133: icmp_seq=8 ttl=128 time=1669 ms
> 64 bytes from 10.0.0.133: icmp_seq=9 ttl=128 time=669 ms
> 64 bytes from 10.0.0.133: icmp_seq=10 ttl=128 time=7070 ms
> 64 bytes from 10.0.0.133: icmp_seq=11 ttl=128 time=6070 ms
> 64 bytes from 10.0.0.133: icmp_seq=12 ttl=128 time=5070 ms
> 64 bytes from 10.0.0.133: icmp_seq=13 ttl=128 time=4071 ms
> 64 bytes from 10.0.0.133: icmp_seq=14 ttl=128 time=3071 ms
> 64 bytes from 10.0.0.133: icmp_seq=15 ttl=128 time=2071 ms
> 64 bytes from 10.0.0.133: icmp_seq=16 ttl=128 time=1071 ms
> 64 bytes from 10.0.0.133: icmp_seq=17 ttl=128 time=71.6 ms
> 64 bytes from 10.0.0.133: icmp_seq=18 ttl=128 time=6476 ms
> 64 bytes from 10.0.0.133: icmp_seq=19 ttl=128 time=5476 ms
> 64 bytes from 10.0.0.133: icmp_seq=20 ttl=128 time=4476 ms
> 64 bytes from 10.0.0.133: icmp_seq=21 ttl=128 time=3476 ms
> 64 bytes from 10.0.0.133: icmp_seq=22 ttl=128 time=2476 ms
> 64 bytes from 10.0.0.133: icmp_seq=23 ttl=128 time=1476 ms
> 64 bytes from 10.0.0.133: icmp_seq=24 ttl=128 time=477 ms
> 64 bytes from 10.0.0.133: icmp_seq=25 ttl=128 time=6875 ms
> 64 bytes from 10.0.0.133: icmp_seq=26 ttl=128 time=5877 ms
> 64 bytes from 10.0.0.133: icmp_seq=27 ttl=128 time=4878 ms
> 64 bytes from 10.0.0.133: icmp_seq=28 ttl=128 time=3878 ms
> 64 bytes from 10.0.0.133: icmp_seq=29 ttl=128 time=2878 ms
> 64 bytes from 10.0.0.133: icmp_seq=30 ttl=128 time=1879 ms
> 64 bytes from 10.0.0.133: icmp_seq=31 ttl=128 time=879 ms
> 64 bytes from 10.0.0.133: icmp_seq=32 ttl=128 time=7282 ms
> 64 bytes from 10.0.0.133: icmp_seq=33 ttl=128 time=6284 ms
> 64 bytes from 10.0.0.133: icmp_seq=34 ttl=128 time=5284 ms
> 64 bytes from 10.0.0.133: icmp_seq=35 ttl=128 time=4284 ms
> 64 bytes from 10.0.0.133: icmp_seq=36 ttl=128 time=3284 ms
> 64 bytes from 10.0.0.133: icmp_seq=37 ttl=128 time=2284 ms
> 64 bytes from 10.0.0.133: icmp_seq=38 ttl=128 time=1286 ms
> 64 bytes from 10.0.0.133: icmp_seq=39 ttl=128 time=286 ms
> 64 bytes from 10.0.0.133: icmp_seq=40 ttl=128 time=6685 ms
> 64 bytes from 10.0.0.133: icmp_seq=41 ttl=128 time=5686 ms
> 64 bytes from 10.0.0.133: icmp_seq=42 ttl=128 time=4686 ms
> 64 bytes from 10.0.0.133: icmp_seq=43 ttl=128 time=3686 ms
> 64 bytes from 10.0.0.133: icmp_seq=44 ttl=128 time=2686 ms
> 64 bytes from 10.0.0.133: icmp_seq=45 ttl=128 time=1686 ms
> 64 bytes from 10.0.0.133: icmp_seq=46 ttl=128 time=686 ms
> 64 bytes from 10.0.0.133: icmp_seq=47 ttl=128 time=7087 ms
> 64 bytes from 10.0.0.133: icmp_seq=48 ttl=128 time=6088 ms
> 64 bytes from 10.0.0.133: icmp_seq=49 ttl=128 time=5088 ms
> 64 bytes from 10.0.0.133: icmp_seq=50 ttl=128 time=4088 ms
> 64 bytes from 10.0.0.133: icmp_seq=51 ttl=128 time=3088 ms
> 64 bytes from 10.0.0.133: icmp_seq=52 ttl=128 time=2088 ms
> 64 bytes from 10.0.0.133: icmp_seq=53 ttl=128 time=1088 ms
> 64 bytes from 10.0.0.133: icmp_seq=54 ttl=128 time=88.9 ms
> 64 bytes from 10.0.0.133: icmp_seq=55 ttl=128 time=6490 ms
> 64 bytes from 10.0.0.133: icmp_seq=56 ttl=128 time=5490 ms
> 64 bytes from 10.0.0.133: icmp_seq=57 ttl=128 time=4490 ms
> 64 bytes from 10.0.0.133: icmp_seq=58 ttl=128 time=3490 ms
> 64 bytes from 10.0.0.133: icmp_seq=59 ttl=128 time=2490 ms
> 64 bytes from 10.0.0.133: icmp_seq=60 ttl=128 time=1490 ms
> 64 bytes from 10.0.0.133: icmp_seq=61 ttl=128 time=490 ms
> 64 bytes from 10.0.0.133: icmp_seq=62 ttl=128 time=6895 ms
> 64 bytes from 10.0.0.133: icmp_seq=63 ttl=128 time=5895 ms
> 64 bytes from 10.0.0.133: icmp_seq=64 ttl=128 time=4895 ms
> 64 bytes from 10.0.0.133: icmp_seq=66 ttl=128 time=3011 ms
> 64 bytes from 10.0.0.133: icmp_seq=67 ttl=128 time=2011 ms
> 64 bytes from 10.0.0.133: icmp_seq=70 ttl=128 time=3.15 ms
> 64 bytes from 10.0.0.133: icmp_seq=71 ttl=128 time=6402 ms
> 64 bytes from 10.0.0.133: icmp_seq=72 ttl=128 time=5402 ms
> 64 bytes from 10.0.0.133: icmp_seq=73 ttl=128 time=4402 ms
> 64 bytes from 10.0.0.133: icmp_seq=74 ttl=128 time=3402 ms
> 64 bytes from 10.0.0.133: icmp_seq=75 ttl=128 time=2402 ms
> 64 bytes from 10.0.0.133: icmp_seq=76 ttl=128 time=1402 ms
> 64 bytes from 10.0.0.133: icmp_seq=77 ttl=128 time=403 ms
> 64 bytes from 10.0.0.133: icmp_seq=78 ttl=128 time=3.21 ms
> 64 bytes from 10.0.0.133: icmp_seq=79 ttl=128 time=6397 ms
> 64 bytes from 10.0.0.133: icmp_seq=80 ttl=128 time=5397 ms
> 64 bytes from 10.0.0.133: icmp_seq=81 ttl=128 time=4397 ms
> 64 bytes from 10.0.0.133: icmp_seq=82 ttl=128 time=3398 ms
> 64 bytes from 10.0.0.133: icmp_seq=83 ttl=128 time=2398 ms
> 64 bytes from 10.0.0.133: icmp_seq=84 ttl=128 time=1398 ms
> 64 bytes from 10.0.0.133: icmp_seq=85 ttl=128 time=398 ms
> 64 bytes from 10.0.0.133: icmp_seq=86 ttl=128 time=3.13 ms
> 64 bytes from 10.0.0.133: icmp_seq=87 ttl=128 time=6405 ms
> 64 bytes from 10.0.0.133: icmp_seq=88 ttl=128 time=5405 ms
> 64 bytes from 10.0.0.133: icmp_seq=89 ttl=128 time=4405 ms
> 64 bytes from 10.0.0.133: icmp_seq=90 ttl=128 time=3405 ms
> 64 bytes from 10.0.0.133: icmp_seq=91 ttl=128 time=2405 ms
> 64 bytes from 10.0.0.133: icmp_seq=92 ttl=128 time=1406 ms
> 64 bytes from 10.0.0.133: icmp_seq=93 ttl=128 time=406 ms
> 64 bytes from 10.0.0.133: icmp_seq=94 ttl=128 time=6807 ms
> 64 bytes from 10.0.0.133: icmp_seq=95 ttl=128 time=5807 ms
> 64 bytes from 10.0.0.133: icmp_seq=96 ttl=128 time=4808 ms
> 64 bytes from 10.0.0.133: icmp_seq=97 ttl=128 time=3808 ms
> 64 bytes from 10.0.0.133: icmp_seq=98 ttl=128 time=2808 ms
> 64 bytes from 10.0.0.133: icmp_seq=99 ttl=128 time=1808 ms
> 64 bytes from 10.0.0.133: icmp_seq=100 ttl=128 time=808 ms
> 64 bytes from 10.0.0.133: icmp_seq=101 ttl=128 time=7209 ms
> 64 bytes from 10.0.0.133: icmp_seq=102 ttl=128 time=6210 ms
> 64 bytes from 10.0.0.133: icmp_seq=103 ttl=128 time=5210 ms
> 64 bytes from 10.0.0.133: icmp_seq=104 ttl=128 time=4210 ms
> 64 bytes from 10.0.0.133: icmp_seq=105 ttl=128 time=3210 ms
> 64 bytes from 10.0.0.133: icmp_seq=106 ttl=128 time=2210 ms
> 64 bytes from 10.0.0.133: icmp_seq=107 ttl=128 time=1210 ms
> 64 bytes from 10.0.0.133: icmp_seq=108 ttl=128 time=210 ms
> 
> --- 10.0.0.133 ping statistics ---
> 111 packets transmitted, 105 received, 5% packet loss, time 110051ms
> rtt min/avg/max/mdev = 3.138/3495.188/7282.109/2175.738 ms, pipe 8
> 
> 
> 
> 
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [ath9k-devel] Ath9k packets dropping issue
  2009-03-03 14:21   ` Wang Jian
@ 2009-03-03 23:02     ` Yura
  0 siblings, 0 replies; 4+ messages in thread
From: Yura @ 2009-03-03 23:02 UTC (permalink / raw)
  To: ath9k-devel

Hello Wang,

Tuesday, March 3, 2009, 4:21:51 PM, you wrote:

> Can you run some sniffer and see what packets trigger the burst out?

No packet triggers. Just short transfer windows seem to occur every 8
seconds. But sometimes it normalizes for a short time and works fine
in both directions.


srv:~# ping 10.0.0.133
64 bytes from 10.0.0.133: icmp_seq=232 ttl=128 time=402 ms
64 bytes from 10.0.0.133: icmp_seq=233 ttl=128 time=3.56 ms
64 bytes from 10.0.0.133: icmp_seq=234 ttl=128 time=6406 ms
64 bytes from 10.0.0.133: icmp_seq=235 ttl=128 time=5409 ms
64 bytes from 10.0.0.133: icmp_seq=236 ttl=128 time=4409 ms
64 bytes from 10.0.0.133: icmp_seq=237 ttl=128 time=3409 ms
64 bytes from 10.0.0.133: icmp_seq=238 ttl=128 time=2409 ms
64 bytes from 10.0.0.133: icmp_seq=241 ttl=128 time=3.21 ms
64 bytes from 10.0.0.133: icmp_seq=242 ttl=128 time=6399 ms
64 bytes from 10.0.0.133: icmp_seq=245 ttl=128 time=3399 ms
64 bytes from 10.0.0.133: icmp_seq=246 ttl=128 time=2398 ms
64 bytes from 10.0.0.133: icmp_seq=247 ttl=128 time=1399 ms
64 bytes from 10.0.0.133: icmp_seq=248 ttl=128 time=399 ms
64 bytes from 10.0.0.133: icmp_seq=249 ttl=128 time=3.23 ms
64 bytes from 10.0.0.133: icmp_seq=250 ttl=128 time=6406 ms
64 bytes from 10.0.0.133: icmp_seq=251 ttl=128 time=5406 ms
64 bytes from 10.0.0.133: icmp_seq=252 ttl=128 time=4406 ms
64 bytes from 10.0.0.133: icmp_seq=253 ttl=128 time=3406 ms
64 bytes from 10.0.0.133: icmp_seq=254 ttl=128 time=2406 ms
64 bytes from 10.0.0.133: icmp_seq=255 ttl=128 time=1406 ms
....


root at asus:~# tcpdump -i wlan0 host 10.0.0.133
tcpdump: WARNING: wlan0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
17:51:48.608805 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 280, length 64
17:51:48.984621 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 274, length 64
17:51:48.984713 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 275, length 64
17:51:48.984796 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 276, length 64
17:51:48.984879 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 277, length 64
17:51:48.984961 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 278, length 64
17:51:48.985043 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 279, length 64
17:51:48.985162 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 280, length 64
17:51:49.608215 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 281, length 64
17:51:49.611095 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 281, length 64
17:51:50.620226 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 282, length 64
17:51:51.620346 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 283, length 64
17:51:52.622268 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 284, length 64
17:51:53.636380 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 285, length 64
17:51:54.636550 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 286, length 64
17:51:55.636453 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 287, length 64
17:51:56.636606 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 288, length 64
17:51:57.015008 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 282, length 64
17:51:57.015098 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 283, length 64
17:51:57.015180 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 284, length 64
17:51:57.015262 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 285, length 64
17:51:57.015345 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 286, length 64
17:51:57.015539 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 287, length 64
17:51:57.015645 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 288, length 64
17:51:57.640441 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 289, length 64
17:51:57.643062 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 289, length 64
17:51:58.644685 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 290, length 64
17:51:59.646771 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 291, length 64
17:52:00.660620 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 292, length 64
17:52:01.660602 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 293, length 64
17:52:02.660639 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 294, length 64
17:52:03.660573 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 295, length 64
17:52:04.660696 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 296, length 64
17:52:05.046712 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 290, length 64
17:52:05.046803 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 291, length 64
17:52:05.046885 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 292, length 64
17:52:05.046968 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 293, length 64
17:52:05.047051 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 294, length 64
17:52:05.047134 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 295, length 64
17:52:05.047216 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 296, length 64
17:52:05.664693 IP srv.lan > 10.0.0.133: ICMP echo request, id 6014, seq 297, length 64
17:52:05.667301 IP 10.0.0.133 > srv.lan: ICMP echo reply, id 6014, seq 297, length 64


--------------------
ping from windows:


C:\Documents and Settings\Yura>ping 10.0.0.1 -t -w 500

????? ???????? ? 10.0.0.1 ?? 32 ????:

????? ?? 10.0.0.1: ????? ????=32 ?????=59?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=438?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=2?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=407?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=3?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=407?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=2?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=407?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=2?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=407?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=2?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=407?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=2?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
????? ?? 10.0.0.1: ????? ????=32 ?????=407?? TTL=64
????? ?? 10.0.0.1: ????? ????=32 ?????=2?? TTL=64
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.
???????? ???????? ???????? ??? ???????.

?????????? Ping ??? 10.0.0.1:
    ???????: ?????????? = 47, ???????? = 15, ???????? = 32 (68% ??????),
??????????????? ????? ??????-???????? ? ??:
    ??????????? = 2????, ???????????? = 438 ????, ??????? = 196 ????





root at asus:~# tcpdump -i wlan0 host 10.0.0.133
tcpdump: WARNING: wlan0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
18:05:58.910007 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 10586, length 40
18:05:58.922285 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 10586, length 40
18:06:00.408137 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 10842, length 40
18:06:00.408624 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 10842, length 40
18:06:01.907940 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 11098, length 40
18:06:01.908427 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 11098, length 40
18:06:02.907928 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 11354, length 40
18:06:02.908465 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 11354, length 40
18:06:03.907908 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 11610, length 40
18:06:03.908392 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 11610, length 40
18:06:05.408100 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 11866, length 40
18:06:05.408598 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 11866, length 40
18:06:06.908075 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 12122, length 40
18:06:06.908568 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 12122, length 40
18:06:07.907510 arp who-has 10.0.0.133 tell router.lan
18:06:08.418178 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 12378, length 40
18:06:08.418664 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 12378, length 40
18:06:08.907511 arp who-has 10.0.0.133 tell router.lan
18:06:09.907511 arp who-has 10.0.0.133 tell router.lan
18:06:09.907955 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 12634, length 40
18:06:09.908561 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 12634, length 40
18:06:10.315672 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:10.315762 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:10.315843 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:10.908624 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 12890, length 40
18:06:10.909099 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 12890, length 40
18:06:11.907982 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 13146, length 40
18:06:11.908458 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 13146, length 40
18:06:13.407776 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 13402, length 40
18:06:13.408262 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 13402, length 40
18:06:14.907941 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 13658, length 40
18:06:14.908419 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 13658, length 40
18:06:16.407719 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 13914, length 40
18:06:16.408201 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 13914, length 40
18:06:17.907722 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 14170, length 40
18:06:17.908210 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 14170, length 40
18:06:18.907881 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 14426, length 40
18:06:18.908359 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 14426, length 40
18:06:19.907895 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 14682, length 40
18:06:19.908370 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 14682, length 40
18:06:21.407882 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 14938, length 40
18:06:21.408366 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 14938, length 40
18:06:22.907840 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 15194, length 40
18:06:22.908332 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 15194, length 40
18:06:24.407629 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 15450, length 40
18:06:24.408106 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 15450, length 40
18:06:25.907802 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 15706, length 40
18:06:25.908288 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 15706, length 40
18:06:26.907828 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 15962, length 40
18:06:26.908309 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 15962, length 40
18:06:27.907721 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 16218, length 40
18:06:27.908199 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 16218, length 40
18:06:29.407739 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 16474, length 40
18:06:29.408226 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 16474, length 40
18:06:30.907582 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 16730, length 40
18:06:30.908059 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 16730, length 40
18:06:32.408024 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 16986, length 40
18:06:32.408504 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 16986, length 40
18:06:33.907671 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 17242, length 40
18:06:33.908156 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 17242, length 40
18:06:34.907826 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 17498, length 40
18:06:34.908349 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 17498, length 40
18:06:35.907676 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 17754, length 40
18:06:35.908152 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 17754, length 40
18:06:37.407549 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 18010, length 40
18:06:37.408039 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 18010, length 40
18:06:38.907630 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 18266, length 40
18:06:38.908121 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 18266, length 40
18:06:40.407602 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 18522, length 40
18:06:40.408088 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 18522, length 40
18:06:41.907604 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 18778, length 40
18:06:41.908096 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 18778, length 40
18:06:42.907362 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 19034, length 40
18:06:42.907920 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 19034, length 40
18:06:43.907589 arp who-has 10.0.0.133 tell router.lan
18:06:43.907397 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 19290, length 40
18:06:43.908326 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 19290, length 40
18:06:44.907511 arp who-has 10.0.0.133 tell router.lan
18:06:45.407599 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 19546, length 40
18:06:45.408082 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 19546, length 40
18:06:45.907509 arp who-has 10.0.0.133 tell router.lan
18:06:46.907565 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 19802, length 40
18:06:46.911601 arp who-has 10.0.0.133 tell router.lan
18:06:46.913866 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:46.914061 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 19802, length 40
18:06:48.407311 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 20058, length 40
18:06:48.407874 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 20058, length 40
18:06:49.907519 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 20314, length 40
18:06:49.908005 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 20314, length 40
18:06:50.315206 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:50.315295 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:50.315377 arp reply 10.0.0.133 is-at 00:16:ea:60:97:9a (oui Unknown)
18:06:50.907526 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 20570, length 40
18:06:50.908004 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 20570, length 40
18:06:51.907245 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 20826, length 40
18:06:51.907812 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 20826, length 40
18:06:53.052458 arp who-has newhome.lan tell 10.0.0.133
18:06:53.052438 arp who-has newhome.lan tell 10.0.0.133
18:06:53.407396 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 21082, length 40
18:06:53.407950 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 21082, length 40
18:06:54.907390 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 21338, length 40
18:06:54.907951 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 21338, length 40
18:06:56.407366 IP 10.0.0.133 > router.lan: ICMP echo request, id 512, seq 21594, length 40
18:06:56.407934 IP router.lan > 10.0.0.133: ICMP echo reply, id 512, seq 21594, length 40



-- 
Best regards,
 Yura                            mailto:gt at ukr.net

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-03-03 23:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-02 18:30 [ath9k-devel] Ath9k packets dropping issue Wang Jian
2009-03-03 14:06 ` Yura
2009-03-03 14:21   ` Wang Jian
2009-03-03 23:02     ` Yura

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.