From: Benjamin Hodgetts <ben@xnode.org>
To: linux-wireless@vger.kernel.org
Subject: IWLWIFI Issues (TX Retries, Speed, Disconnections)
Date: Mon, 26 Nov 2012 22:41:13 +0000 [thread overview]
Message-ID: <50B3F009.4010903@xnode.org> (raw)
The wireless card seems to cap out around 6MB/s even when connected at
(apparently) 216Mb so throughput isn't as high as it should be (even
accounting for the massive wireless overheads) but that isn't the main
issue...
Currently I'm seeing a MASSIVE amount of Tx excessive retries. After
copying a 4GB file the figure was at 825394 (without any bluetooth
activity).
Secondly (the main issue): If I use something bluetooth at the same time
as the Wireless card, it seems to fall over after a few minutes (it's
fine up until that point).
The device in question is a Intel(R) Centrino(R) Wireless-N 2230 BGN
Mini-PCIe card (it's both a Wireless G/N card and a Bluetooth 4 card).
For example, I just tried to use it again and ended up giving up. I was
trying to use Bluetooth headphones and the wireless at the same time. It
was ok for a minute or two and then just kept silently dropping out (not
disconnecting from the AP though). The time between it happening would
shorten each time until it seemed to happen every 20 seconds or so.
Kernel output:
[301961.010199] iwlwifi 0000:04:00.0: fail to flush all tx fifo queues
[302045.433040] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302052.978602] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302067.127391] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302073.046653] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302076.299569] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302079.683274] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302143.254305] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302170.259993] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302203.089092] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302345.510246] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302361.812532] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302375.833424] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302383.333181] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302396.240417] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302399.632266] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302446.190562] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302466.248471] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302479.420951] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[302488.926232] iwlwifi 0000:04:00.0: BT traffic (2), no aggregation allowed
[303036.959778] iwlwifi 0000:04:00.0: fail to flush all tx fifo queues
[303157.754721] iwlwifi 0000:04:00.0: fail to flush all tx fifo queues
[303279.622419] iwlwifi 0000:04:00.0: fail to flush all tx fifo queues
This is Arch Linux using the 3.6.6 kernel. This same scenario works fine
on my laptop.
reply other threads:[~2012-11-26 23:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50B3F009.4010903@xnode.org \
--to=ben@xnode.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).