From: Wang Jian <lark@linux.net.cn>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Ath9k packets dropping issue
Date: Tue, 03 Mar 2009 22:21:51 +0800 [thread overview]
Message-ID: <49AD3CFF.907@linux.net.cn> (raw)
In-Reply-To: <127559990.20090303160636@ukr.net>
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
>
>
>
>
>
>
next prev parent reply other threads:[~2009-03-03 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-03-03 23:02 ` Yura
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49AD3CFF.907@linux.net.cn \
--to=lark@linux.net.cn \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.