public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Jiri Slaby <jirislaby@gmail.com>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Bob Copeland <me@bobcopeland.com>,
	linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ath5k-devel] ath5k regression associating with APs in 2.6.38
Date: Tue, 31 May 2011 19:31:07 +0200	[thread overview]
Message-ID: <4DE525DB.1000908@openwrt.org> (raw)
In-Reply-To: <BANLkTi=8ZRUVWn3FLAMtPh=4yY1F0k6i9w@mail.gmail.com>

On 2011-05-17 7:14 PM, Nick Kossifidis wrote:
> 2011/5/17 Seth Forshee<seth.forshee@canonical.com>:
>>  On Mon, May 09, 2011 at 09:02:30AM +0200, Seth Forshee wrote:
>>>  On Thu, May 05, 2011 at 05:30:42PM +0300, Nick Kossifidis wrote:
>>>  >  Hmm I don't see any errors from reset/phy code, can you disable
>>>  >  Network Manager/wpa-supplicant and test connection on an open network
>>>  >  using iw ? It 'll give us a better picture...
>>>  >
>>>  >  If iw doesn't return any scan results we are probably hitting a PHY/RF
>>>  >  error specific to your device (not all vendors follow the reference
>>>  >  design). Maybe we should follow a blacklist/whitelist approach for
>>>  >  this feature.
>>>
>>>  I got the results back from my tester. He was able to get scan results,
>>>  but it took multiple tries and the direct probe failures appear in the
>>>  log. He didn't enable ATH5K_DEBUG_RESET this time; let me know if you
>>>  need that and I'll request he retest with the extra debug logs enabled.
>>
>>  I got some more feedback. Most of the time iw does not get scan results,
>>  but even when it does connecting to the AP isn't always successful. The
>>  tester did note that he doesn't seem to have any trouble if his machine
>>  is within a few feet of his AP. Let me know if you'd like something else
>>  tested.
>>
>>  I noticed that bugzilla #31922 (ath5k: Decreased throughput in IBSS or
>>  802.11n mode) is also fixed by reverting 8aec7af9. It seems like the
>>  synth-only channel changes are resulting in poor connection quality.
>>  Maybe that patch needs to be reverted?
>>
>>  Thanks,
>>  Seth
>>
>>
>
> http://www.kernel.org/pub/linux/kernel/people/mickflemm/01-fast-chan-switch-modparm
Disabling fast channel change also fixed a reproducible crash on 
Broadcom based MIPS boards with some cards (AR2413, I think).

- Felix

      parent reply	other threads:[~2011-05-31 17:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 15:38 ath5k regression associating with APs in 2.6.38 Seth Forshee
2011-05-04 17:27 ` John W. Linville
2011-05-04 19:26   ` Seth Forshee
2011-05-04 20:09     ` Nick Kossifidis
2011-05-05 13:52       ` Seth Forshee
2011-05-05 14:30         ` Nick Kossifidis
2011-05-05 14:54           ` Seth Forshee
2011-05-05 15:01           ` Justin P. Mattock
2011-05-05 15:15             ` Nick Kossifidis
2011-05-09  7:02           ` Seth Forshee
2011-05-17 16:57             ` Seth Forshee
2011-05-17 17:14               ` Nick Kossifidis
2011-05-17 18:50                 ` Seth Forshee
2011-05-19 21:28                   ` Seth Forshee
2011-05-31 17:31                 ` Felix Fietkau [this message]

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=4DE525DB.1000908@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=netdev@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