From: Kalle Valo <kalle.valo@iki.fi>
To: linux-wireless@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>
Subject: wireless-testing broken
Date: Wed, 23 Sep 2009 18:00:41 -0700 [thread overview]
Message-ID: <da94abde0909231800v75b05677ka6b8570a73b6055c@mail.gmail.com> (raw)
Hi,
I upgraded to latest wireless-testing and noticed that I can't connect
anymore with my iwl3945. master-2009-09-16 still works. My syslog has
this:
Sep 24 03:53:28 tikku kernel: [ 719.479190] phy0: device no longer
idle - scanning
Sep 24 03:53:31 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:31 tikku wpa_supplicant[12381]: Trying to associate with
00:03:52:d9:27:10 (SSID='ibahn' freq=2452 MHz)
Sep 24 03:53:31 tikku wpa_supplicant[12381]: Association request to
the driver failed
Sep 24 03:53:31 tikku kernel: [ 722.096782] phy0: device now idle
Sep 24 03:53:31 tikku kernel: [ 722.099163] phy0: device no longer
idle - scanning
Sep 24 03:53:31 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:31 tikku kernel: [ 722.101652] phy0: device now idle
Sep 24 03:53:32 tikku kernel: [ 723.101920] phy0: device no longer
idle - scanning
Sep 24 03:53:34 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:34 tikku kernel: [ 725.804837] phy0: device now idle
Sep 24 03:53:36 tikku wpa_supplicant[12381]: Authentication with
00:03:52:d9:27:10 timed out.
Sep 24 03:53:36 tikku kernel: [ 727.101285] phy0: device no longer
idle - scanning
Sep 24 03:53:38 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:38 tikku wpa_supplicant[12381]: Trying to associate with
00:03:52:d9:77:70 (SSID='ibahn' freq=2427 MHz)
Sep 24 03:53:38 tikku wpa_supplicant[12381]: Association request to
the driver failed
Sep 24 03:53:38 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:38 tikku kernel: [ 729.816160] phy0: device now idle
Sep 24 03:53:39 tikku kernel: [ 730.777467] phy0: device no longer
idle - scanning
Sep 24 03:53:42 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:42 tikku kernel: [ 733.389081] phy0: device now idle
Sep 24 03:53:43 tikku wpa_supplicant[12381]: Authentication with
00:03:52:d9:77:70 timed out.
Sep 24 03:53:43 tikku kernel: [ 734.737634] phy0: device no longer
idle - scanning
Sep 24 03:53:46 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:46 tikku wpa_supplicant[12381]: Trying to associate with
00:03:52:a4:7d:b0 (SSID='ibahn' freq=2432 MHz)
Sep 24 03:53:46 tikku wpa_supplicant[12381]: Association request to
the driver failed
Sep 24 03:53:46 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
Sep 24 03:53:46 tikku kernel: [ 737.428317] phy0: device now idle
Sep 24 03:53:47 tikku kernel: [ 738.414783] phy0: device no longer
idle - scanning
Sep 24 03:53:50 tikku wpa_supplicant[12381]: CTRL-EVENT-SCAN-RESULTS
But gotta run now, more info later.
Kalle
next reply other threads:[~2009-09-24 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 1:00 Kalle Valo [this message]
2009-09-24 3:54 ` wireless-testing broken John W. Linville
2009-09-24 4:16 ` Kalle Valo
2009-09-24 4:39 ` Kalle Valo
2009-09-24 3:55 ` Luis R. Rodriguez
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=da94abde0909231800v75b05677ka6b8570a73b6055c@mail.gmail.com \
--to=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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