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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080520184859.GA8168@robinhood.home>
Date:	Tue, 20 May 2008 21:49:30 +0300
From:	m.s.tsirkin@...il.com
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	LKML <linux-kernel@...r.kernel.org>, yi.zhu@...el.com,
	reinette.chatre@...el.com, linux-wireless@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net, johannes@...solutions.net,
	flamingice@...rmilk.net
Subject: regression iwl3945/mac80211: association times out since 2.6.26-rc1

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!

-- 
MST
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/