Bug 14202 - no connection with iwl4695
Summary: no connection with iwl4695
Status: RESOLVED DUPLICATE of bug 14196
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-21 17:01 UTC by François Valenduc
Modified: 2009-09-29 18:36 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31-gitX
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description François Valenduc 2009-09-21 17:01:56 UTC
With the current mainline git tree, there is no way to make any connection with the iwl4965 driver using wpa encryption. With dhcpcd, I get the message "waiting for carrier" when I run it.
After a git-bisect run, it seems that the first bad commit is the following:

bbac31f4c0339f6c51afbd0edfb4959df9b53fa9 is first bad commit
commit bbac31f4c0339f6c51afbd0edfb4959df9b53fa9
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Wed Sep 16 09:04:26 2009 -0700

    cfg80211: fix SME connect

    There's a check saying
        /* we're good if we have both BSSID and channel */
        if (wdev->conn->params.bssid && wdev->conn->params.channel) {

    but that isn't true -- we need the BSS struct. This leads
    to errors such as

        Trying to associate with 00:1b:53:11:dc:40 (SSID='TEST' freq=2412 MHz)
        ioctl[SIOCSIWFREQ]: No such file or directory
        ioctl[SIOCSIWESSID]: No such file or directory
        Association request to the driver failed
        Associated with 00:1b:53:11:dc:40

    in wpa_supplicant, as reported by Holger.

    Instead, we really need to have the BSS struct, and if we
    don't, then we need to initiate a scan for it. But we may
    already have the BSS struct here, so hang on to it if we
    do and scan if we don't.

    Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
    Tested-by: Holger Schurig <hs4233@mail.mn-solutions.de>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

If I revert this commit, the problem doesn't occur.
Comment 1 François Valenduc 2009-09-23 18:24:05 UTC
Does anybody take care of this annoying bug ?
I have compared the output of dmesg with kernel-2.6.31 and the current mainline git tree. In 2.6.31, I get this:

[   10.518652] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27k
[   10.518657] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[   10.518860] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   10.518900] iwlagn 0000:02:00.0: setting latency timer to 64
[   10.519003] iwlagn 0000:02:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
[   10.577123] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 19 802.11a channels
[   10.577277] iwlagn 0000:02:00.0: irq 32 for MSI/MSI-X
[   10.789227] phy0: Selected rate control algorithm 'iwl-agn-rs'
[   30.041746] iwlagn 0000:02:00.0: firmware: requesting iwlwifi-4965-2.ucode
[   30.111945] iwlagn 0000:02:00.0: loaded firmware version 228.57.2.23
[   33.292551] wlan0: authenticate with AP 00:1a:70:9a:3c:be
[   33.294456] wlan0: authenticated
[   33.294460] wlan0: associate with AP 00:1a:70:9a:3c:be
[   33.297029] wlan0: RX AssocResp from 00:1a:70:9a:3c:be (capab=0x411 status=0 aid=2)
[   33.297033] wlan0: associated

The last lines showing the association to my access point don't appear with the current git tree.
Comment 2 John W. Linville 2009-09-29 18:36:41 UTC

*** This bug has been marked as a duplicate of bug 14196 ***

Note You need to log in before you can comment on or make changes to this bug.