2.6.19-rc2 ipw2200 breakage with wpa_supplicant

[Robert Hancock <hancockr@shaw.ca>]

Something changed between 2.6.18-mm1 and 2.6.19-rc2 to cause my laptop's 
ipw2200 to be unable to associate with the access point using 
NetworkManager and wpa_supplicant. I keep seeing this kind of thing over 
and over in the wpa_supplicant output:

Trying to associate with (removed) (SSID='Robman' freq=0 MHz)
CTRL_IFACE monitor send - hexdump(len=43): (removed)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): (removed)
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22):(removed)
p key clearing
er_wext_set_drop_unencrypted
State: ASSOCIATING -> ASSOCIATING
wpa_driver_wext_associate
Setting authentication timeout: 15 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b19 len=8
Received 1373 bytes of scan results (6 BSSes)
Scan results: 6
Selecting BSS from priority group 0
0: (removed) ssid='Robman' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
   selected based on RSN IE
Trying to associate with (removed) (SSID='Robman' freq=0 MHz)

and iwevent keeps showing this repeatedly:

20:52:32.303911   eth1     Scan request completed
20:52:32.303945   eth1     Set Mode:Managed
20:52:32.303962   eth1     Set ESSID:"Robman"
20:52:32.671509   eth1     Scan request completed
20:52:32.671542   eth1     Set Mode:Managed
20:52:32.671560   eth1     Set ESSID:"Robman"
20:52:33.034063   eth1     Scan request completed

Replacing ipw2200.c from 2.6.18-mm1 (adapted for the irq changes) fixes 
the problem.

I do notice that I keep seeing those "Scan request completed" messages 
from iwevent when nothing is going on with the 2.6.19-rc2 driver but not 
the 2.6.18-mm1 driver.

Anyone else seeing this?

--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/