linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Howard Chu <hyc@symas.com>
To: linux-wireless@vger.kernel.org
Subject: ath9k problems
Date: Sat, 20 Sep 2008 21:17:20 -0700	[thread overview]
Message-ID: <48D5CAD0.1080909@symas.com> (raw)

This may be related to this other thread
http://marc.info/?l=linux-wireless&m=122187323506092&w=2

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).

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 also found that if I kept a ping session to my wifi router running, then the 
wireless connection would not die, it would operate normally.

It seems that it all worked fine in 2.6.27-rc4...
-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

             reply	other threads:[~2008-09-21  4:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21  4:17 Howard Chu [this message]
2008-09-21  4:22 ` ath9k problems 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
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=48D5CAD0.1080909@symas.com \
    --to=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).