Skip to contentSkip to conversation

regression iwl3945/mac80211: association times out since 2.6.26-rc1

DISCUSSION [email protected] 2 participants 6 messages May 20, 2008 – May 26, 2008

lore
Share & tools
lore
#0 lore raw

Hi!
In all of 2.6.26-rc1, rc2 and rc3, my iwl3945 wifi card can't associate with my access point. It does associate in 2.6.25.

under 2.6.-26-rc[1,2,3] wpa_supplicant reports:

	Trying to associate with 00:16:e3:ef:5d:f0 (SSID='' freq=0 MHz)
	Authentication with 00:00:00:00:00:00 timed out.

where under 2.6.25 I was associating with

	Trying to associate with 00:16:e3:ef:5d:f0 (SSID='SIEMENS-EF5DF0' freq=2437 MHz)
	Associated with 00:16:e3:ef:5d:f0
	WPA: Key negotiation completed with 00:16:e3:ef:5d:f0 [PTK=CCMP GTK=CCMP]

I tried bisecting, and I got as far as git-bisect good 4b119e21d0c66c22e8ca03df05d9de623d0eb50f git-bisect bad 96d510566e4908f77f03ff1436c78ae7162a17d0

but a point between these 2 commits gets me iwl driver that hangs kernel when it's loaded, so I gave up on bisecting at this point.
Still this leaves us with 91 candidates that might be introducing the regression (get their list with git log
4b119e21d0c66c22e8ca03df05d9de623d0eb50f..96d510566e4908f77f03ff1436c78ae7162a17d0)

Additional info:

I get this in dmesg

[   99.153033] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[   99.204031] PM: Adding info for No Bus:iwl-phy1:radio
[   99.204031] Registered led device: iwl-phy1:radio
[   99.204031] PM: Adding info for No Bus:iwl-phy1:assoc
[   99.204031] Registered led device: iwl-phy1:assoc
[   99.204031] PM: Adding info for No Bus:iwl-phy1:RX
[   99.204031] Registered led device: iwl-phy1:RX
[   99.204031] PM: Adding info for No Bus:iwl-phy1:TX
[   99.204031] Registered led device: iwl-phy1:TX
[   99.220405] ADDRCONF(NETDEV_UP): wlan0: link is not ready

and even though the led now lights up, there's no association.

portions of .config: 2.6.26-rc3:

CONFIG_IWLWIFI=m
CONFIG_IWLCORE=m
# CONFIG_IWLWIFI_LEDS is not set
CONFIG_IWLWIFI_RFKILL=y
# CONFIG_IWL4965 is not set
CONFIG_IWL3945=m
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
CONFIG_IWL3945_LEDS=y
CONFIG_IWL3945_DEBUG=y

2.6.25:
# CONFIG_IWL4965 is not set
CONFIG_IWL3945=m
CONFIG_IWL3945_QOS=y
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
CONFIG_IWL3945_DEBUG=y

What kind of additional information would be useful for debugging this regression?

Thanks!

Signature · 1 line
MST
#3 lore raw
Quoted 6 lines · Michael S. Tsirkin
Quoted 2 lines · Michael S. Tsirkin

FYI, I created an item in bugzilla to track this
http://bugzilla.kernel.org/show_bug.cgi?id=10765

As requested, more configuration and log files have been attached to this item.

It looks like also this issue should be fixed by ' mac80211: reorder channel and freq reporting in wext scan report' patch.
http://article.gmane.org/gmane.linux.kernel.wireless.general/15177
Please try.
Thanks
Tomas

#4 lore raw
Quoted 9 lines · Tomas Winkler
Quoted 6 lines · Michael S. Tsirkin
Quoted 2 lines · Michael S. Tsirkin

FYI, I created an item in bugzilla to track this
http://bugzilla.kernel.org/show_bug.cgi?id=10765

As requested, more configuration and log files have been attached to this item.

Quoted 6 lines

It looks like also this issue should be fixed by ' mac80211: reorder channel and freq reporting in wext scan report' patch.
http://article.gmane.org/gmane.linux.kernel.wireless.general/15177
Please try.
Thanks
Tomas

I can confirm that the patch linked above has solved the regression for me. Is it queued for 2.6.26?

Signature · 1 line
MST
#5 lore raw
Quoted 17 lines · Michael S. Tsirkin
Quoted 9 lines · Tomas Winkler
Quoted 6 lines · Michael S. Tsirkin
Quoted 2 lines · Michael S. Tsirkin

FYI, I created an item in bugzilla to track this
http://bugzilla.kernel.org/show_bug.cgi?id=10765

As requested, more configuration and log files have been attached to this item.

Quoted 6 lines

It looks like also this issue should be fixed by ' mac80211: reorder channel and freq reporting in wext scan report' patch.
http://article.gmane.org/gmane.linux.kernel.wireless.general/15177
Please try.
Thanks
Tomas

Quoted 2 lines

I can confirm that the patch linked above has solved the regression for me. Is it queued for 2.6.26?

Hope so, it should go also to 25 If I remember someone posted version that matched the old file name
as well.
Thanks
Tomas