constant reassociation cycle for encrypted wifi (driver issue?)

[joel jaeggli]

Binary package hint: wpasupplicant

Description: Ubuntu karmic (development branch)
Release: 9.10

ii wpasupplicant 0.6.9-3 client support for WPA and WPA2 (IEEE 802.11
ii linux-image-2.6.31-4-generic 2.6.31-4.22 Linux kernel image for version 2.6.31 on x86
ii network-manager 0.7.1-0ubuntu1 network management framework daemon

connect to an unauthenticated network, see a near constant cycle of dis and re-associations

multiple aps tried (cisco (ap 1252 a/b/g/n), openwrt(buffalo 802.11g) etc)
multiple atheros chipsets (9280 5008)

example from jul 21 (/var/log/daemon.log):

Jul 21 07:11:42 chickenhawk wpa_supplicant[2748]: Trying to associate with 00:16:01:7f:6a:b5 (SSID='OW' freq=2412 MHz)
Jul 21 07:11:42 chickenhawk wpa_supplicant[2748]: Association request to the driver failed
Jul 21 07:11:42 chickenhawk NetworkManager: <info> (wlan2): supplicant connection state: scanning -> associating
Jul 21 07:11:42 chickenhawk wpa_supplicant[2748]: Associated with 00:16:01:7f:6a:b5
Jul 21 07:11:42 chickenhawk NetworkManager: <info> (wlan2): supplicant connection state: associating -> associated
Jul 21 07:11:42 chickenhawk wpa_supplicant[2748]: CTRL-EVENT-CONNECTED - Connection to 00:16:01:7f:6a:b5 completed (reauth) [id=0 id_str=]
Jul 21 07:11:42 chickenhawk NetworkManager: <info> (wlan2): supplicant connection state: associated -> completed
Jul 21 07:11:42 chickenhawk NetworkManager: <info> Activation (wlan2/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'OW'.
Jul 21 07:11:42 chickenhawk NetworkManager: <info> Activation (wlan2) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 21 07:11:42 chickenhawk NetworkManager: <info> Activation (wlan2) Stage 3 of 5 (IP Configure Start) started...
Jul 21 07:11:42 chickenhawk NetworkManager: <info> (wlan2): device state change: 5 -> 7

from july 24:

Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: Associated with 00:17:df:a2:45:31
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: associating -> disconnected
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: CTRL-EVENT-CONNECTED - Connection to 00:17:df:a2:45:31 completed (reauth) [id=0 id_str=]
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: disconnected -> associated
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: associated -> completed
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: completed -> disconnected
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: Associated with 00:17:df:a2:45:31
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: CTRL-EVENT-CONNECTED - Connection to 00:17:df:a2:45:31 completed (reauth) [id=0 id_str=]
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: disconnected -> associated
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: associated -> completed
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: completed -> disconnected
Jul 24 01:00:10 chickenhawk NetworkManager: <info> (ath1): supplicant connection state: disconnected -> associated
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: Associated with 00:17:df:a2:45:31
Jul 24 01:00:10 chickenhawk wpa_supplicant[2708]: CTRL-EVENT-CONNECTED - Connection to 00:17:df:a2:45:31 completed (reauth) [id=0 id_str=]

Disabling Network manager control of wifi, and manually connecting to an ssid with iwconfig followed by dhcping produces a stable association. on an indefinite basis.

higher traffic volumes seem to produce a more frequent disassociation reassociation cycle,but it's possible that they simply accentuate the fact that all tcp connections are stalled while the client is dissociated...

hardware is asus 1000he

root@chickenhawk:/home/joelja# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
01:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Attansic Technology Corp. Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)

bug was reproduceable in earlier versions of karmic

[Tim D (humbletim)]

also experiencing this on an asus 1005ha with jaunty.

secured networks (wep/wpa) work fine; all unsecured networks get stuck in the scanning -> associating -> disconnected loop and eventually timeout:

tim@tim-eee:/var/log$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
01:00.0 Ethernet controller: Attansic Technology Corp. Device 1062 (rev c0)
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

[Tim D (humbletim)]

augmenting my previous comment w/package versions:

ii linux-image-2.6.29-1-netbook 2.6.29-1.0array1 Linux kernel image for version 2.6.29 on x86
ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 network management framework daemon
ii wpasupplicant 0.6.6-2ubuntu1 client support for WPA and WPA2 (IEEE 802.11

[Tim D (humbletim)]

upgraded to newer kernel and enabled some hpeg/pcie grub defoptions, and wpa_supplicant connection problems disappeared:

ii linux-image-2.6.30-02063004-generic 2.6.30-02063004 Linux kernel image for version 2.6.30 on x86

# defoptions= ... force-hpet pciehp.pciehp_force=1 pciehp.pciehp_poll_mode=1

(ps: was in general following some instructions for latest kernel/drivers on eee from http://forum.eeebuntu.org/viewtopic.php?f=7&t=3866)

[hanzomon4 (hanzomon4)]

I also have the same problem on a macbook pro 3.1 with an Athros Card. It only happens when I'm at school on a wpa-eap ttls-pap connection. I'l test out these options and let you know if it works

[Václav Šmilauer (eudoxos)]

I am on a MSI Wind clone with intel 4965 card and have the same issue. The HPET-force as suggested by Tim D. didn't help though, running stock 2.6.31-10-generic kernel.

[hanzomon4 (hanzomon4)]

It worked for me, I have upgraded to Karmic as well so....

[Václav Šmilauer (eudoxos)]

Taking back my comment #5; backports modules really fixed the issue. (maybe I booted older kernel by accident?)

[Václav Šmilauer (eudoxos)]

2.6.31-11 doesn't have backports package, about 3 days since 2.6.31 now. Is it going to be available?

[Reinhard Tartler (siretart)]

This bug is not helpful for developers as it is. Various reporters report a similar symptom (constant reassociation) that reside from bugs in the wifi driver. Indeed, the different reporters indicate to use totally different wifi hardware and thus different drivers. In no way wpasupplicant can fix buggy wifi drivers. I'm therefore marking this bug as wontfix.

As for your various reports: I suggest that you file new bugs against the 'linux' package, as wifi drivers are shipped with the kernel in general. Please make sure that you include exact information about your hardware and drivers.

[Václav Šmilauer (eudoxos)]

Reassign to kernel, as it seems driver issue. Retitle as well.

[Václav Šmilauer (eudoxos)]

Official install kernels don't include backported modules. People with some hardware (?) will have this issue after fresh installation unless they google out the solution. Couldn't the relevant part of backports be included in the main release?

[Eduard Drenth (eduarddrenth)]

for my ar9285 (ath9k) card the problem seems to be related to suspend/resume. When rebooting the card works fine, after suspend/resume the disconnect/connect loop starts.

[rusart (ruslan-levitskiy)]

I have the same problem with RaLink (04:00.0 Network controller: RaLink RT2860) on Kubuntu Karmic (WPA-PSK). Sometimes connection lost with this lines in syslog:

2009-11-24 19:41:31 rusart-laptop NetworkManager <info> (ra0): device state change: 8 -> 3 (reason 11)
2009-11-24 19:41:31 rusart-laptop NetworkManager <info> (ra0): deactivating device (reason: 11).
2009-11-24 19:41:31 rusart-laptop NetworkManager <info> (ra0): canceled DHCP transaction, dhcp client pid 25869
2009-11-24 19:41:31 rusart-laptop NetworkManager <WARN> check_one_route(): (ra0) error -34 returned from rtnl_route_del(): Sucess#012
2009-11-24 19:41:31 rusart-laptop NetworkManager <info> (ra0): removing resolv.conf from /sbin/resolvconf
2009-11-24 19:41:31 rusart-laptop avahi-daemon[816] Withdrawing address record for 192.168.0.100 on ra0.
2009-11-24 19:41:31 rusart-laptop avahi-daemon[816] Leaving mDNS multicast group on interface ra0.IPv4 with address 192.168.0.100.
2009-11-24 19:41:31 rusart-laptop avahi-daemon[816] Interface ra0.IPv4 no longer relevant for mDNS.
2009-11-24 19:41:31 rusart-laptop avahi-daemon[816] querier.c: querier_remove() called but no querier to remove.
2009-11-24 19:41:31 rusart-laptop avahi-daemon[816] last message repeated 9 times
2009-11-24 19:41:31 rusart-laptop NetworkManager <info> Activation (ra0) starting connection 'exogenesis'

Only one way to reconnect is deactivate wireless and activate it again. Else there is requests for WPA keyphrase with no results.

P.S. Sorry for my english...

[penalvch (penalvch)]

joel jaeggli, thank you for reporting this and helping make Ubuntu better. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.9-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]