From: Michael Hirsch <hirsch@teufel.de>
To: linux-wireless@vger.kernel.org
Subject: Connection drop while running iperf on ARM based platform
Date: Tue, 15 Apr 2014 11:30:45 +0200 [thread overview]
Message-ID: <534CFC45.90101@teufel.de> (raw)
Hi all,
I have an issue using a with RT5572 chipset (TP-Link N600) on a Armada
based embedded system.
After connecting to an AP and using iperf to stress-test the USB Wifi
Dongle stops receiving data. Kernel version is 3.14, it happens both on
firmware version 0.29 and 0.33.
iperf -c 192.168.44.170 -i 1 -t 1000 &
# ------------------------------------------------------------
Client connecting to 192.168.44.170, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.44.245 port 55342 connected with 192.168.44.170 port
5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 2.12 MBytes 17.8 Mbits/sec
[ 147.046945] ieee80211 phy2: rt2800usb_watchdog: Warning - TX HW queue
1 timed out, invoke forced kick
[ 3] 1.0- 2.0 sec 2.25 MBytes 18.9 Mbits/sec
[ 148.046626] ieee80211 phy2: rt2800usb_watchdog: Warning - TX HW queue
1 timed out, invoke forced kick
[ 148.058795] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status
for an empty queue 3, dropping
[ 3] 2.0- 3.0 sec 1.50 MBytes 12.6 Mbits/sec
[ 3] 3.0- 4.0 sec 1.88 MBytes 15.7 Mbits/sec
[ 3] 4.0- 5.0 sec 1.75 MBytes 14.7 Mbits/sec
[ 3] 5.0- 6.0 sec 2.12 MBytes 17.8 Mbits/sec
[ 3] 6.0- 7.0 sec 2.12 MBytes 17.8 Mbits/sec
[ 3] 7.0- 8.0 sec 2.38 MBytes 19.9 Mbits/sec
[ 3] 8.0- 9.0 sec 2.12 MBytes 17.8 Mbits/sec
[ 155.047086] ieee80211 phy2: rt2800usb_watchdog: Warning - TX HW queue
1 timed out, invoke forced kick
[ 155.067200] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status
for an empty queue 3, dropping
[ 3] 9.0-10.0 sec 1.75 MBytes 14.7 Mbits/sec
[ 3] 10.0-11.0 sec 2.25 MBytes 18.9 Mbits/sec
[ 3] 11.0-12.0 sec 1.75 MBytes 14.7 Mbits/sec
[ 3] 12.0-13.0 sec 1.88 MBytes 15.7 Mbits/sec
[ 158.343582] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status
for an empty queue 3, dropping
[ 3] 13.0-14.0 sec 1.62 MBytes 13.6 Mbits/sec
[ 3] 14.0-15.0 sec 1.88 MBytes 15.7 Mbits/sec
[ 3] 15.0-16.0 sec 2.25 MBytes 18.9 Mbits/sec
[ 162.116741] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status
for an empty queue 3, dropping
[ 3] 16.0-17.0 sec 2.25 MBytes 18.9 Mbits/sec
[ 3] 17.0-18.0 sec 1.75 MBytes 14.7 Mbits/sec
[ 3] 18.0-19.0 sec 1.62 MBytes 13.6 Mbits/sec
[ 3] 19.0-20.0 sec 2.12 MBytes 17.8 Mbits/sec
[ 3] 20.0-21.0 sec 2.00 MBytes 16.8 Mbits/sec
[ 3] 21.0-22.0 sec 1.62 MBytes 13.6 Mbits/sec
[ 3] 22.0-23.0 sec 1.50 MBytes 12.6 Mbits/sec
[ 3] 23.0-24.0 sec 1.75 MBytes 14.7 Mbits/sec
[ 3] 24.0-25.0 sec 1.75 MBytes 14.7 Mbits/sec
[ 3] 25.0-26.0 sec 1.50 MBytes 12.6 Mbits/sec
[ 171.816309] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 14 in queue 2
[ 171.827208] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 14 in queue 2
[ 171.838062] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 14 in queue 2
[ 171.848877] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 14 in queue 2
[ 171.859690] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 14 in queue 2
[ 171.870544] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 15 in queue 2
[ 171.881371] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 15 in queue 2
[ 171.892183] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 0 in queue 2
[ 171.902905] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 0 in queue 2
[ 171.913630] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 1 in queue 2
[ 171.924348] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 1 in queue 2
[ 171.935094] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 2 in queue 2
[ 171.945816] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 2 in queue 2
[ 171.956571] ieee80211 phy2: rt2800usband_entry_txstatus_timeout:
Warning - TX status timeout for entry 3 in queue 2
[ 171.967293] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 3 in queue 2
[ 171.978020] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 4 in queue 2
[ 171.988754] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 4 in queue 2
[ 171.999496] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 5 in queue 2
[ 172.010217] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 5 in queue 2
[ 172.022059] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 5 in queue 2
[ 172.033004] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 6 in queue 2
[ 172.043807] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning
- TX status timeout for entry 6 in queue 2
and it stops.
I noticed
iw dev wlan1 link shows a tx bitrate of 1.0 MBit/s and according to iw
it does not receive any packets any more.
Running the same wifi module on a x86 Laptop with 3.14 kernel works better.
There is also drops to 0 at running iperf, but it seems to be able to
recover. Also on a x86 laptops is see the TX Status timeout messages (if
it's enabled in the kernel config). I followed the discussion a bit
about those messages and can't say whether these messages have anything
todo with shown issue (no packets received)
Any suggestion where I could start searching? For me it looks like a
rate-control issue, but that's speculation.
Best regards
Michael
next reply other threads:[~2014-04-15 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 9:30 Michael Hirsch [this message]
2014-04-19 12:42 ` Connection drop while running iperf on ARM based platform Andreas Hartmann
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=534CFC45.90101@teufel.de \
--to=hirsch@teufel.de \
--cc=linux-wireless@vger.kernel.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.