From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Howard Chu <hyc@symas.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k problems
Date: Mon, 22 Sep 2008 10:30:10 -0700 [thread overview]
Message-ID: <20080922173010.GD6048@tesla> (raw)
In-Reply-To: <48D78215.1050403@symas.com>
On Mon, Sep 22, 2008 at 04:31:33AM -0700, Howard Chu wrote:
> Luis R. Rodriguez wrote:
> > On Mon, Sep 22, 2008 at 2:09 AM, Howard Chu<hyc@symas.com> wrote:
> >> > For example - I added DPRINTFs to all the places that called ath9_hw_reset()
> >> > to see why the ForceXPAon message was occurring so often, and got the
> >> > attached log. I note that ForceXPAon doesn't occur on every call to
> >> > hw_reset, and sometimes there are repeated identical calls to set the
> >> > channel (e.g. at 22:06:36 in the log).
> >> >
> >> > It associates successfully with my AP on channel 8, but shortly thereafter
> >> > loses the association, scans again, and starts over again, ad nauseam. This
> >> > behavior was made even worse when I upgraded my freeradius server (was
> >> > authenticating with WPA EAP/PEAP) and configured TLS session caching - there
> >> > seems to be a bug in freeradius there so subsequent reassociation attempts
> >> > would always fail until I turned off session caching. (Haven't had time to
> >> > chase that down yet.)
> >
> > Howard, did you apply the pending group key patch yet?
>
> Yes, the patch didn't improve the situation on my wireless-testing build. It
> works fine on my 2.6.27-rc6 build though.
Can you provide a long of your wireless-testing run with the group key
patch applied? Also, please try running wpa_supplicant manually, but
first be sure to disable Network Manager completely by doing:
# Red Hat based systems
sudo /sbin/service NetworkMananger stop
# Debian based systems (Ubuntu is one)
sudo /etc/init.d/NetworkManager stop
sudo killall -TERM wpa_supplicant
Please read:
http://wireless.kernel.org/en/users/Reporting_bugs
Luis
next prev parent reply other threads:[~2008-09-22 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 4:17 ath9k problems Howard Chu
2008-09-21 4:22 ` Steven Noonan
2008-09-22 6:48 ` Luis R. Rodriguez
2008-09-22 7:21 ` Steven Noonan
2008-09-22 8:08 ` Luis R. Rodriguez
2008-09-22 19:47 ` John W. Linville
2008-09-22 9:09 ` Howard Chu
2008-09-22 9:45 ` Luis R. Rodriguez
2008-09-22 11:31 ` Howard Chu
2008-09-22 17:30 ` Luis R. Rodriguez [this message]
2008-09-22 20:34 ` Howard Chu
2008-09-22 21:16 ` 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=20080922173010.GD6048@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=hyc@symas.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).