* wireless-testing broken @ 2009-09-24 1:00 Kalle Valo 2009-09-24 3:54 ` John W. Linville 2009-09-24 3:55 ` Luis R. Rodriguez 0 siblings, 2 replies; 5+ messages in thread From: Kalle Valo @ 2009-09-24 1:00 UTC (permalink / raw) To: linux-wireless; +Cc: John W. Linville 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wireless-testing broken 2009-09-24 1:00 wireless-testing broken Kalle Valo @ 2009-09-24 3:54 ` John W. Linville 2009-09-24 4:16 ` Kalle Valo 2009-09-24 3:55 ` Luis R. Rodriguez 1 sibling, 1 reply; 5+ messages in thread From: John W. Linville @ 2009-09-24 3:54 UTC (permalink / raw) To: Kalle Valo; +Cc: linux-wireless On Wed, Sep 23, 2009 at 06:00:41PM -0700, Kalle Valo wrote: > 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) Kalle, I know you aren't in a great situation for this, but could you try a bisect? Or, you might just try reverting "iwlwifi: reduce noise when skb allocation" as a start... John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wireless-testing broken 2009-09-24 3:54 ` John W. Linville @ 2009-09-24 4:16 ` Kalle Valo 2009-09-24 4:39 ` Kalle Valo 0 siblings, 1 reply; 5+ messages in thread From: Kalle Valo @ 2009-09-24 4:16 UTC (permalink / raw) To: John W. Linville; +Cc: linux-wireless On Wed, Sep 23, 2009 at 8:54 PM, John W. Linville <linville@tuxdriver.com> wrote: > On Wed, Sep 23, 2009 at 06:00:41PM -0700, Kalle Valo wrote: >> 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) > > Kalle, > > I know you aren't in a great situation for this, but could you try > a bisect? Or, you might just try reverting "iwlwifi: reduce noise > when skb allocation" as a start... Sure, I'll start bisecting right now. Kalle ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wireless-testing broken 2009-09-24 4:16 ` Kalle Valo @ 2009-09-24 4:39 ` Kalle Valo 0 siblings, 0 replies; 5+ messages in thread From: Kalle Valo @ 2009-09-24 4:39 UTC (permalink / raw) To: John W. Linville; +Cc: linux-wireless, Johannes Berg On Wed, Sep 23, 2009 at 9:16 PM, Kalle Valo <kalle.valo@iki.fi> wrote: > On Wed, Sep 23, 2009 at 8:54 PM, John W. Linville > <linville@tuxdriver.com> wrote: >> I know you aren't in a great situation for this, but could you try >> a bisect? Or, you might just try reverting "iwlwifi: reduce noise >> when skb allocation" as a start... > > Sure, I'll start bisecting right now. The result is: 55a00b83339f25d2979b85ab6e2151390327db80 is first bad commit commit 55a00b83339f25d2979b85ab6e2151390327db80 Author: Johannes Berg <johannes@sipsolutions.net> Date: Thu Sep 17 17:15:31 2009 -0700 cfg80211: don't overwrite privacy setting When cfg80211 is instructed to connect, it always uses the default WEP key for the privacy setting, which clearly is wrong when using wpa_supplicant. Don't overwrite the setting, and rely on it being false when wpa_supplicant is not running, instead set it to true when we have keys. Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com> I verified the result by manually reverting the commit and this is really causing my problem. My current setup is debian unstable, default debian wpa_supplicant (using wext I think, haven't checked) and open network at Portland Marriott hotel. I can reproduce the problem every time. Kalle ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wireless-testing broken 2009-09-24 1:00 wireless-testing broken Kalle Valo 2009-09-24 3:54 ` John W. Linville @ 2009-09-24 3:55 ` Luis R. Rodriguez 1 sibling, 0 replies; 5+ messages in thread From: Luis R. Rodriguez @ 2009-09-24 3:55 UTC (permalink / raw) To: Kalle Valo; +Cc: linux-wireless, John W. Linville On Wed, Sep 23, 2009 at 6:00 PM, Kalle Valo <kalle.valo@iki.fi> wrote: > 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: Hm, seems to work fine with my ath5k and ath9k device. So perhaps this is just an iwl3945 regression? Luis ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-09-24 4:39 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-09-24 1:00 wireless-testing broken Kalle Valo 2009-09-24 3:54 ` 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox