public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: iwl3945 dropping from network
Date: Mon, 13 Jul 2009 10:02:48 +0300	[thread overview]
Message-ID: <87r5wl5alj.fsf@litku.valot.fi> (raw)

Good morning,

during the weekend I have noticed that my iwl3945 is dropping from
network and wpa_supplicant can't connect to the network anymore, only
'wpa_action wlan0 stop' (which essentially quits wpa_supplicant) and
'ifup wlan0' (which starts wpa_supplicant, debian is weird here) makes
it work again. I think I'm seeing similar behaviour also when I resume.

I'm using debian unstable on Lenovo x60s with wpa_supplicant 0.6.9-3, so
the old wext interface is used. wpa_supplicant isn't updated since May
which points that this a problem in the wireless-testing kernel.

Here's one log from a situation when the connection suddenly dropped:

[201075.582192] phy0: device now idle
[201076.828989] phy0: device no longer idle - in use
[201076.828997] wlan0: direct probe to AP 00:12:17:e7:98:de (try 1)
[201076.831575] wlan0 direct probe responded
[201076.831580] wlan0: authenticate with AP 00:12:17:e7:98:de (try 1)
[201076.833491] wlan0: authenticated
[201077.028069] wlan0: associate with AP 00:12:17:e7:98:de (try 1)
[201077.030283] wlan0: RX AssocResp from 00:12:17:e7:98:de (capab=0x411
status=0 aid=2)
[201077.030289] wlan0: associated
[201077.030296] phy0: Allocated STA 00:12:17:e7:98:de
[201077.030303] phy0: Inserted STA 00:12:17:e7:98:de
[201077.032506] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[208063.200059] No probe response from AP 00:12:17:e7:98:de after 200ms,
disconnecting.
[208063.200081] phy0: device now idle
[208063.200092] phy0: Removed STA 00:12:17:e7:98:de
[208063.212054] phy0: Destroyed STA 00:12:17:e7:98:de
[208063.312201] phy0: device no longer idle - scanning
[208063.466419] phy0: device now idle
[208063.598042] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[208063.598069] phy0: device no longer idle - in use
[208063.598077] wlan0: direct probe to AP 00:12:17:e7:98:de (try 1)
[208063.599984] wlan0 direct probe responded
[208063.599990] wlan0: authenticate with AP 00:12:17:e7:98:de (try 1)
[208063.601910] wlan0: authenticated
[208063.800044] wlan0: associate with AP 00:12:17:e7:98:de (try 1)
[208063.802201] wlan0: RX AssocResp from 00:12:17:e7:98:de (capab=0x411
status=0 aid=2)
[208063.802207] wlan0: associated
[208063.802214] phy0: Allocated STA 00:12:17:e7:98:de
[208063.802221] phy0: Inserted STA 00:12:17:e7:98:de
[208063.804275] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[208066.200048] No probe response from AP 00:12:17:e7:98:de after 200ms,
disconnecting.
[208066.200073] phy0: device now idle
[208066.200083] phy0: Removed STA 00:12:17:e7:98:de
[208066.212060] phy0: Destroyed STA 00:12:17:e7:98:de
[208066.312311] phy0: device no longer idle - scanning
[208068.903824] phy0: device now idle
[208073.908401] phy0: device no longer idle - scanning
[208076.517689] phy0: device now idle
[208081.519682] phy0: device no longer idle - scanning
[208084.106036] phy0: device now idle
[208089.107114] phy0: device no longer idle - scanning
[208091.693636] phy0: device now idle
[208096.699172] phy0: device no longer idle - scanning
[208099.285510] phy0: device now idle
[208104.291055] phy0: device no longer idle - scanning
[208106.900124] phy0: device now idle
[208111.904403] phy0: device no longer idle - scanning
[208114.513533] phy0: device now idle
[208119.519072] phy0: device no longer idle - scanning
[208122.106209] phy0: device now idle

-- 
Kalle Valo

             reply	other threads:[~2009-07-13  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  7:02 Kalle Valo [this message]
2009-07-13 18:26 ` iwl3945 dropping from network reinette chatre

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=87r5wl5alj.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=johannes@sipsolutions.net \
    --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