All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: Regression in 2.6.38 (30% package losses, ~20KBit/s throughput) with AR9285
Date: Mon, 25 Apr 2011 14:51:39 +0200	[thread overview]
Message-ID: <4DB56E5B.4090101@hauke-m.de> (raw)

Hi,

with kernel 2.6.38 the wifi connection with my Atheros AR9285 is
unusable when the distance from the AP is more that 3 meters. (30%
package losses, ~20K/s throughput compared to ~3M/s) Tested with two
cards on different devices. With kernel 2.6.35 or kernel 2.6.38 +
compat-wireless 15 meters distance is no problem. The problem only
occurs in 2.6.38-rc1 to 2.6.38.4 but not in any more recent versions. I
did a git bisect and found the commit fixing the problem.

commit 115dad7a7f42e68840392767323ceb9306dbdb36
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Fri Jan 14 00:06:27 2011 +0100

    ath9k_hw: partially revert "fix dma descriptor rx error bit parsing"

http://www.spinics.net/lists/linux-wireless/msg62742.html

Please send this commit to the stable series for 2.6.38.

The problem is also described at the Ubuntu launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735431

Hauke

WARNING: multiple messages have this Message-ID (diff)
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Felix Fietkau <nbd@openwrt.org>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Vasanthakumar Thiagarajan <vasanth@atheros.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	Jouni Malinen <jmalinen@atheros.com>
Cc: ath9k-devel@lists.ath9k.org,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath9k: Regression in 2.6.38 (30% package losses, ~20KBit/s throughput) with AR9285
Date: Mon, 25 Apr 2011 14:51:39 +0200	[thread overview]
Message-ID: <4DB56E5B.4090101@hauke-m.de> (raw)

Hi,

with kernel 2.6.38 the wifi connection with my Atheros AR9285 is
unusable when the distance from the AP is more that 3 meters. (30%
package losses, ~20K/s throughput compared to ~3M/s) Tested with two
cards on different devices. With kernel 2.6.35 or kernel 2.6.38 +
compat-wireless 15 meters distance is no problem. The problem only
occurs in 2.6.38-rc1 to 2.6.38.4 but not in any more recent versions. I
did a git bisect and found the commit fixing the problem.

commit 115dad7a7f42e68840392767323ceb9306dbdb36
Author: Felix Fietkau <nbd@openwrt.org>
Date:   Fri Jan 14 00:06:27 2011 +0100

    ath9k_hw: partially revert "fix dma descriptor rx error bit parsing"

http://www.spinics.net/lists/linux-wireless/msg62742.html

Please send this commit to the stable series for 2.6.38.

The problem is also described at the Ubuntu launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735431

Hauke

             reply	other threads:[~2011-04-25 12:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 12:51 Hauke Mehrtens [this message]
2011-04-25 12:51 ` ath9k: Regression in 2.6.38 (30% package losses, ~20KBit/s throughput) with AR9285 Hauke Mehrtens
2011-04-25 13:05 ` [ath9k-devel] " Hauke Mehrtens
2011-04-25 13:05   ` Hauke Mehrtens
2011-04-25 17:07   ` [ath9k-devel] " John W. Linville
2011-04-25 17:07     ` John W. Linville
2011-04-25 17:38     ` [ath9k-devel] [stable] " Greg KH
2011-04-25 17:38       ` Greg KH

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=4DB56E5B.4090101@hauke-m.de \
    --to=hauke@hauke-m.de \
    --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.