[Bugme-new] [Bug 10765] New: iwl3945/mac80211: association times out since 2.6.26-rc1

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Tue May 20 22:46:18 PDT 2008


http://bugzilla.kernel.org/show_bug.cgi?id=10765

           Summary: iwl3945/mac80211: association times out since 2.6.26-rc1
           Product: Networking
           Version: 2.5
     KernelVersion: 2.6.26-rc1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Wireless
        AssignedTo: networking_wireless at kernel-bugs.osdl.org
        ReportedBy: m.s.tsirkin at gmail.com
                CC: yi.zhu at intel.com, reinette.chatre at intel.com


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
Problem Description:


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



Steps to reproduce:
 run wpa_cli, look at output


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


More information about the Bugme-new mailing list