public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, willy@linux.intel.com,
	lrodriguez@atheros.com
Subject: ath5k gets lost with eeepc-laptop removal
Date: Fri, 31 Oct 2008 11:05:02 -0200	[thread overview]
Message-ID: <20081031110502.18e33eba@doriath.conectiva> (raw)


 Hi guys,

 If I do a 'rmmod eeepc-laptop', while connected to my AP, I get the
following error messages from ath5k:

"""
ath5k phy0: noise floor calibration timeout (2417MHz)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
wlan0: No ProbeResp from current AP 00:1d:0f:e9:c7:c0 - assume out of range
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: ath5k_chan_set: unable to reset channel (2412 Mhz)
wlan0: failed to set freq to 2412 MHz for scan
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: ath5k_chan_set: unable to reset channel (2417 Mhz)
wlan0: failed to set freq to 2417 MHz for scan
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: ath5k_chan_set: unable to reset channel (2422 Mhz)
wlan0: failed to set freq to 2422 MHz for scan
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: ath5k_chan_set: unable to reset channel (2427 Mhz)
wlan0: failed to set freq to 2427 MHz for scan
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: ath5k_chan_set: unable to reset channel (2432 Mhz)
wlan0: failed to set freq to 2432 MHz for scan
wlan0: failed to set freq to 2437 MHz for scan
wlan0: failed to set freq to 2442 MHz for scan
wlan0: failed to set freq to 2447 MHz for scan
wlan0: failed to set freq to 2452 MHz for scan
wlan0: failed to set freq to 2457 MHz for scan
wlan0: failed to set freq to 2462 MHz for scan
wlan0: failed to set freq to 2467 MHz for scan
wlan0: failed to set freq to 2472 MHz for scan
wlan0: failed to set freq to 2484 MHz for scan
wlan0: failed to restore operational channel after scan
wlan0: authenticate with AP 00:1d:0f:e9:c7:c0
wlan0: authenticate with AP 00:1d:0f:e9:c7:c0
wlan0: authenticate with AP 00:1d:0f:e9:c7:c0
wlan0: authentication with AP 00:1d:0f:e9:c7:c0 timed out
"""

 Then I lost my wireless connection.

 I'm running latest Linus git tree (2.6.28-rc2) on a Eeepc 701.

 The problem doesn't happen on 2.6.27.4, but as 2.6.28-rc1 doesn't
boot on this machine, it would be a bit difficult to bisect it.

 Thanks.

-- 
Luiz Fernando N. Capitulino

             reply	other threads:[~2008-10-31 13:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 13:05 Luiz Fernando N. Capitulino [this message]
2008-10-31 13:51 ` ath5k gets lost with eeepc-laptop removal Alan Jenkins
2008-10-31 14:23   ` Matthew Garrett
2008-10-31 18:35     ` Nick Kossifidis
2008-11-02  9:23       ` Matthew Garrett
2008-10-31 16:26 ` Nick Kossifidis
2008-10-31 17:19   ` Luiz Fernando N. Capitulino
2008-10-31 18:33     ` Nick Kossifidis
2008-10-31 18:43       ` Luiz Fernando N. Capitulino
2008-10-31 18:48         ` Luiz Fernando N. Capitulino
2008-11-02  9:04           ` Matthew Garrett

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=20081031110502.18e33eba@doriath.conectiva \
    --to=lcapitulino@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=willy@linux.intel.com \
    /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