All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alf <alf@mypals.org>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Bob Copeland <me@bobcopeland.com>,
	Tulio Magno Quites Machado Filho <tuliom@quites.com.br>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: ath5k in 2.6.29.1 won't associate with AP
Date: Wed, 6 May 2009 22:00:26 -0600	[thread overview]
Message-ID: <200905062200.26857.alf@mypals.org> (raw)
In-Reply-To: <40f31dec0905060454s513c5eeas44389e6527eed1fd@mail.gmail.com>

On Wednesday 06 May 2009 05:54:13 am Nick Kossifidis wrote:
> Can you please post the full dmesg output when ath5k loads ?

This is with debugging turned on.

========== dmesg ==========
15:43:35 ath5k 0000:00:07.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18         
15:43:35 ath5k 0000:00:07.0: registered as 'phy0'                               
15:43:35 phy0: Selected rate control algorithm 'minstrel'                       
15:43:35 ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)           
15:43:39 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:43:39 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2                      
15:43:39 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3                      
15:43:39 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out                  
15:43:50 wlan0: authenticate with AP 00:30:bd:60:d3:44                          
15:43:50 wlan0: authenticate with AP 00:30:bd:60:d3:44                          
15:43:50 wlan0: authenticate with AP 00:30:bd:60:d3:44                          
15:43:51 wlan0: authentication with AP 00:30:bd:60:d3:44 timed out              
15:44:01 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:44:01 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2                      
15:44:02 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3                      
15:44:02 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out                  
15:44:12 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:44:12 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2                      
15:44:13 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3                      
15:44:13 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out                  
15:44:29 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:44:29 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:44:30 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2                      
15:44:30 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3                      
15:44:30 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out                  
15:44:47 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:44:47 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1                      
15:44:47 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2                      
15:44:47 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
15:44:47 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
15:44:55 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:44:55 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
15:44:55 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
15:44:56 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
15:45:05 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:05 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:05 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:05 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
15:45:05 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
15:45:06 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
15:45:16 wlan0: authenticate with AP 00:30:bd:60:d3:44
15:45:16 wlan0: authenticate with AP 00:30:bd:60:d3:44
15:45:16 wlan0: authenticate with AP 00:30:bd:60:d3:44
15:45:17 wlan0: authenticate with AP 00:30:bd:60:d3:44
15:45:17 wlan0: authentication with AP 00:30:bd:60:d3:44 timed out
15:45:34 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:34 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:35 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
15:45:35 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
15:45:35 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
15:45:46 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:46 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 1
15:45:46 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 2
15:45:46 wlan0: direct probe to AP 00:30:bd:60:d3:44 try 3
15:45:46 wlan0: direct probe to AP 00:30:bd:60:d3:44 timed out
======== end dmesg ========

-- 
Alf
@

  reply	other threads:[~2009-05-07  4:00 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
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 [this message]
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=200905062200.26857.alf@mypals.org \
    --to=alf@mypals.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=tuliom@quites.com.br \
    /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.