Kernel Bug Tracker – Bug 10765
iwl3945/mac80211: association times out since 2.6.26-rc1
Last modified: 2008-06-10 12:09:39 UTC
Latest working kernel version: 2.6.25
Earliest failing kernel version: 2.6.25-rc1
Distribution: ubuntu dapper, mainline kernel from kernel.org
Hardware Environment: thinkpad T60p, wireless card iwl3945
Software Environment: wpa_supplicant version 0.5.4
In all of 2.6.26-rc1, rc2 and rc3, my iwl3945 wifi card can't associate with my
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
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
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_LEDS is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL4965 is not set
Steps to reproduce:
run wpa_cli, look at output
Please attach your wpa_supplicant.conf. The output of "wpa_supplicant -ddd" and dmesg in the failed case.
*** Bug 10763 has been marked as a duplicate of this bug. ***
This entry is being used for tracking a regression from 2.6.25. Please don't
close it until the problem is fixed in the mainline.
Handled-By : Zhu Yi <email@example.com>
Created attachment 16256 [details]
cleaned version of wpa_supplicant (identity and password left out)
Created attachment 16257 [details]
log from running wpa_supplicant -ddd with supplied config
some identity data cleaned out
Created attachment 16258 [details]
I note that there are no messages from the card after
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Created attachment 16268 [details]
my kernel .config file
Can you enable mac80211 debugging? maybe CONFIG_MAC80211_VERBOSE_DEBUG too.
The bisect is pretty useless since all the interesting wireless commits are in that range.
It's not easy to do anything about it though because I get kernel hangs on commits in between. I guess I could try bisecting the hangs but seems
to be a kind of waste because mainline does not hang.
OK, I will enable CONFIG_MAC80211_VERBOSE_DEBUG.
When you say enable debugging, do you mean CONFIG_MAC80211_DEBUG?
Created attachment 16273 [details]
dmesg with debugging turned on
I modified .config in this way:
# CONFIG_MAC80211_DEBUG_PACKET_ALIGNMENT is not set
# CONFIG_MAC80211_HT_DEBUG is not set
# CONFIG_MAC80211_DEBUG_COUNTERS is not set
# CONFIG_MAC80211_IBSS_DEBUG is not set
# CONFIG_MAC80211_VERBOSE_PS_DEBUG is not set
dmesg attached, but does not seem very informative.
Are there some module flags I should set as well?
Tomas is probably right then, try this patch: http://article.gmane.org/gmane.linux.kernel.wireless.general/15177
I can confirm that the patch in comment 11 fixes the regression for me.
Regressions list annotation:
Handled-By : Johannes Berg <firstname.lastname@example.org>
Patch : http://article.gmane.org/gmane.linux.kernel.wireless.general/15177
I have verified that this bug is fixed