From: Ben Hutchings <ben@decadent.org.uk>
To: Gunnar Stahl <gunnar.stahl@gunnarstahl.org>
Cc: "Richard Schütz" <r.schtz@t-online.de>,
ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>,
622753@bugs.debian.org, "Adrian Chadd" <adrian@freebsd.org>
Subject: Re: ath9k: Connection over wlan slows down and dies
Date: Tue, 17 May 2011 04:45:20 +0100 [thread overview]
Message-ID: <1305603920.19966.119.camel@localhost> (raw)
In-Reply-To: <BANLkTikr6LBGPf8roLyf9n9yL=7qk4y72g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Fri, 2011-04-15 at 15:52 +0800, Adrian Chadd wrote:
> On 15 April 2011 12:00, Ben Hutchings <ben@decadent.org.uk> wrote:
> [...]
> > https://bugzilla.kernel.org/show_bug.cgi?id=31452
>
>
> Thanks, I've set our bug tracker to follow that bug.
>
> Has it been established that it's the same bug though?
>
> I had a brief read of that and I'm not so sure. There's so many things
> that could impact TX throughput.
>
> I don't have this problem on FreeBSD on my AR9285 NICs and I've ported
> almost all of the (non-power saving) related code from ath9k. They
> happily sit at the expected TX/RX speeds in 11g and 11n modes.
>
> Is someone who is experiencing the problem able to do some kernel
> version bisecting between the known good and known bad kernel?
The bug fix from the report on Bugzilla has been included in stable
release 2.6.38.5 and Debian's version 2.6.38-5.
Does this version fix the problem for you?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-05-17 3:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110414123925.31837.14741.reportbug@noomadix>
2011-04-14 12:53 ` ath9k: Connection over wlan slows down and dies Ben Hutchings
2011-04-14 12:56 ` Richard Schütz
2011-04-15 4:00 ` Ben Hutchings
[not found] ` <BANLkTikr6LBGPf8roLyf9n9yL=7qk4y72g@mail.gmail.com>
2011-05-17 3:45 ` Ben Hutchings [this message]
2011-05-17 19:12 ` Gunnar Stahl
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=1305603920.19966.119.camel@localhost \
--to=ben@decadent.org.uk \
--cc=622753@bugs.debian.org \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=gunnar.stahl@gunnarstahl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=r.schtz@t-online.de \
/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).