From: Seth Forshee <seth.forshee@canonical.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
Senthil Balasubramanian <senthilb@qca.qualcomm.com>,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: CTS timeout issue with AR9285
Date: Thu, 2 Feb 2012 08:20:53 -0600 [thread overview]
Message-ID: <20120202142053.GA24483@ubuntu-macmini> (raw)
In-Reply-To: <CAD2nsn0tk_A18vjsCzgO2_7swuM=VPghyTaiHjkHAUc3h3+MiQ@mail.gmail.com>
On Thu, Feb 02, 2012 at 04:58:23PM +0530, Mohammed Shafi wrote:
> On Thu, Feb 2, 2012 at 9:55 AM, Seth Forshee <seth.forshee@canonical.com> wrote:
> > I recently updated a machine with AR9285 wireless from kernel version
> > 3.0 to 3.2 and saw that wireless had become slow and unreliable. It
> > seems that the problem is extremely frequent CTS timeouts, which began
> > happening with commit adb5066 (ath9k_hw: do not apply the 2.4 ghz ack
> > timeout workaround to cts). Restoring the CTS timeout to the value prior
> > to this commit on top of 3.2 gets performance back to what it was with
> > 3.0.
>
> does the environment is a noisy one (or) clear one
It's relatively clear, there isn't much activity at all on the channel
besides this card and the AP. And like I said, other cards aren't having
this problem. Using wireshark I can also see that RTS frames are being
sent repeatedly even though the AP responds with CTS frames.
next prev parent reply other threads:[~2012-02-02 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 4:25 CTS timeout issue with AR9285 Seth Forshee
2012-02-02 11:28 ` Mohammed Shafi
2012-02-02 14:20 ` Seth Forshee [this message]
2012-02-02 12:35 ` Felix Fietkau
2012-02-02 14:15 ` Martin Hundebøll
2012-02-02 14:22 ` Felix Fietkau
2012-02-02 14:38 ` Seth Forshee
2012-02-04 6:08 ` Marek Lindner
2012-02-04 10:24 ` Adrian Chadd
2012-02-04 20:18 ` Felix Fietkau
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=20120202142053.GA24483@ubuntu-macmini \
--to=seth.forshee@canonical.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=nbd@openwrt.org \
--cc=senthilb@qca.qualcomm.com \
--cc=shafi.wireless@gmail.com \
--cc=vthiagar@qca.qualcomm.com \
/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).