From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@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 regression associating with APs in 2.6.38
Date: Wed, 4 May 2011 13:27:17 -0400 [thread overview]
Message-ID: <20110504172716.GC18541@tuxdriver.com> (raw)
In-Reply-To: <20110504153819.GA4551@thinkpad-t410>
On Wed, May 04, 2011 at 10:38:19AM -0500, Seth Forshee wrote:
> I've been investigating some reports of a regression in associating with
> APs with AR2413 in 2.6.38. Association repeatedly fails with some
> "direct probe to x timed out" messages (see syslog excerpt below),
> although it will generally associate eventually, after many tries.
>
> Bisection identifies 8aec7af (ath5k: Support synth-only channel change
> for AR2413/AR5413) as offending commit. Prior to this commit there are
> no direct probe messages at all in the logs. I've also found that
> forcing fast to false at the top of ath5k_hw_reset() fixes the issue.
> I'm not sure what the connection is between this commit and the
> timeouts. Any suggestions?
Have you tried reverting that commit on top of 2.6.38? Can you
recreate the issue with 2.6.39-rc6 (or later)?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-05-04 17:31 UTC|newest]
Thread overview: 20+ 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 15:38 ` Seth Forshee
2011-05-04 17:27 ` John W. Linville
2011-05-04 17:27 ` John W. Linville [this message]
2011-05-04 19:26 ` Seth Forshee
2011-05-04 20:09 ` Nick Kossifidis
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 ` [ath5k-devel] " Felix Fietkau
2011-05-17 17:14 ` Nick Kossifidis
2011-05-05 14:30 ` Nick Kossifidis
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=20110504172716.GC18541@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 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.