All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alf <alf@mypals.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath5k in 2.6.29.1 won't associate with AP
Date: Sat, 02 May 2009 23:14:54 +0200	[thread overview]
Message-ID: <1241298894.13562.28.camel@johannes.local> (raw)
In-Reply-To: <200905021218.23747.alf@mypals.org>

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

On Sat, 2009-05-02 at 12:18 -0600, Alf wrote:

> It seems I am able to associate with an AP (not just my AP) sporadically.  
> It seems that when it works, it works reliably, but that's only 10% of the 
> time, if that.  I have turned on debugging on ath5 and on mac80211 but the 
> debug messages don't offer anything useful.  The only thing I get is this:
> 
> May  2 12:08:20 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
> May  2 12:08:20 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
> May  2 12:08:20 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
> May  2 12:08:20 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
> May  2 12:08:28 wlan0 direct probe responded

What kernel are you using?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-05-02 21:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02 18:18 ath5k in 2.6.29.1 won't associate with AP Alf
2009-05-02 21:14 ` Johannes Berg [this message]
2009-05-02 21:16   ` Johannes Berg
2009-05-02 21:53   ` Alf
2009-05-04 22:49     ` Tulio Magno Quites Machado Filho
2009-05-05  5:36       ` Bob Copeland
2009-05-06  3:42         ` Alf
2009-05-06 11:54           ` Nick Kossifidis
2009-05-07  4:00             ` Alf
2009-05-12 13:36           ` Nick Kossifidis
2009-05-13  5:29             ` Alf

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=1241298894.13562.28.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=alf@mypals.org \
    --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 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.