All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sujith <Sujith.Manoharan@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] No probe response from AP after 500ms, disconnecting.
Date: Wed, 13 Jan 2010 11:39:57 +0530	[thread overview]
Message-ID: <19277.25525.360201.408454@gargle.gargle.HOWL> (raw)
In-Reply-To: <20100111164903.9039.qmail@stuge.se>

Peter Stuge wrote:
> I've seen the problem in every RF environment I've visited with this
> card. Most are in cities small and large, but one is in an office on
> the outskirts of a small city, where the only wifi to be seen is the
> two closest of the six-or-so WAP54 access points that we have set up
> throughout the adjacent buildings. There's very little traffic in
> that network and I still see disconnects.
> 
> In any case I would love to debug this from the bottom and up. Any
> pointers on registers and settings that may be useful too look into,
> in particular if some features of the hardware are not yet supported
> by the driver, would be most welcome.

Can you upgrade to the latest wireless-testing kernel ?
RX errors can be seen in the 'recv' debugfs file.
The contents of 'rcstat' and 'interrupt' would also be useful.

For more information: http://wireless.kernel.org/en/users/Drivers/ath9k/debug

Sujith

  reply	other threads:[~2010-01-13  6:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 17:23 [ath9k-devel] Linux bug 14267 "No probe response from AP after 500ms, disconnecting." Peter Stuge
2009-12-16 17:41 ` Luis R. Rodriguez
2009-12-16 22:21   ` Peter Stuge
2009-12-16 23:43     ` Luis R. Rodriguez
2009-12-18 11:57       ` No probe response from AP after 500ms, disconnecting Peter Stuge
2009-12-18 11:57         ` [ath9k-devel] " Peter Stuge
2009-12-18 16:18         ` Luis R. Rodriguez
2009-12-18 16:18           ` Luis R. Rodriguez
2009-12-18 20:07           ` Peter Stuge
2009-12-18 20:07             ` Peter Stuge
2009-12-19  5:03             ` Vivek Natarajan
2009-12-19  5:03               ` Vivek Natarajan
2009-12-20 12:57               ` Peter Stuge
2009-12-27  1:15                 ` Peter Stuge
2010-01-11 15:03                 ` Peter Stuge
2010-01-11 16:19                   ` Felix Fietkau
2010-01-11 16:49                     ` Peter Stuge
2010-01-13  6:09                       ` Sujith [this message]
2010-01-16  4:05                         ` Peter Stuge
2010-01-17 19:22                           ` Peter Stuge
2011-05-25  6:58 Cedric Sodhi
2011-05-25  8:07 ` Mohammed Shafi
2011-05-25  8:39   ` Mohammed Shafi
2011-05-27 16:06 ` Maciej Mrozowski
2011-05-28 13:30   ` Mohammed Shafi
2011-05-29 18:56     ` Cedric Sodhi
2011-05-30  4:31       ` Mohammed Shafi

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=19277.25525.360201.408454@gargle.gargle.HOWL \
    --to=sujith.manoharan@atheros.com \
    --cc=ath9k-devel@lists.ath9k.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.