From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Steven Noonan <steven@uplinklabs.net>
Cc: Howard Chu <hyc@symas.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k problems
Date: Sun, 21 Sep 2008 23:48:31 -0700 [thread overview]
Message-ID: <20080922064831.GB19580@tesla> (raw)
In-Reply-To: <f488382f0809202122v4c77bc96r54edd24bdf365724@mail.gmail.com>
On Sat, Sep 20, 2008 at 09:22:56PM -0700, Steven Noonan wrote:
> On Sat, Sep 20, 2008 at 9:17 PM, Howard Chu <hyc@symas.com> wrote:
> > With the 2.6.27-rc6 kernel I find that my wireless connection dies after a
> > few minutes. Using nm-applet I have to disable wireless and re-enable it
> > before I can re-establish a session (using WPA).
>
> Yeah, you need this patch:
> http://marc.info/?l=linux-wireless&m=122163541519736&w=2
>
> > I tried pulling the wireless-testing branch and found it behaved strangely
> > as well - within about 30 seconds of idle time it would die. But, it would
> > usually immediately begin to reconnect (and succeed). My logs were full of
> > "ForceXPAon: 0" messages which I found were from ath9_hw_reset(), which were
> > all being called from set_channel, during the scan that took place when the
> > card was not associated with the AP. It typically occurred every 30-35
> > seconds.
>
> I'm sure the ath9k guys can be more informative about what
> 'ForceXPAon: 0' is all about,
Its set *all the time* for our newer chipsets and can be safely ignored.
Not sure what the register is exactly for but its always set on
our newer chipsets upon reset.
> but wireless-testing is pretty outdated
This is not accurate.
It lacks new patches from Linus' tree, but it has the latest
and greatest possible wireless patches. John maintains Linux
wireless so he'll always have more updated patches for wireless than
Linus.
Luis
next prev parent reply other threads:[~2008-09-22 6:48 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 [this message]
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
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=20080922064831.GB19580@tesla \
--to=lrodriguez@atheros.com \
--cc=hyc@symas.com \
--cc=linux-wireless@vger.kernel.org \
--cc=steven@uplinklabs.net \
/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).