[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=487183. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-02-24T17:37:44+00:00 Nigel wrote: Created attachment 333065 syslogd log Description of problem: NetworkManager doesn't always connect to Network Version-Release number of selected component (if applicable): NetworkManager-0.7.0.97-4.git20090219.fc11.i586 wpa_supplicant-0.6.7-3.fc11.i386 kernel-PAE-2.6.29-0.137.rc5.git4.fc11.i686 How reproducible: Intermittent Steps to Reproduce: Either 1. Resume suspended laptop 2. wait for NM to connect to previously selected SSID 3. observe that NM fails & pops up request for secrets or 1. Start with NM already connected to an AP 2. Select an alternate (but correctly configured, and available) AP 3. observe that NM fails &^ pops up secrets request Actual results: NM fails to connect Expected results: NM connects Additional info: Basically sometimes this works, sometimes it doesn't. Association appears to time out. Other non-linux clients (S60/Nokia N95 8Gb/Nokia N96/Windows 7/Windows Vista) don't *appear* to have a problem In the log file attached note the "jonesn: " messages in the log. These were created with the "logger" command to aid in documenting the scenario The Ap that I had been connected to ok was "planetf1c". The one that failed was "planetf1f". Ignore "planetf1e" -- this one is not active and I clicked on it in the GUI by mistake. Error seems to hinge around Activation (wlan0/wireless): association took too long. Security in use is WPA2-PSK AES wifi driver is iwl3945 Both AP are "fonera" routers running openwrt with atheros wireless. In this config the router broadcasts 2 SSIDs. Same problem has been observed with ddwrt (single SSID) Log file is attached (kernel debug log, -dddt ) Not entirely clear if the issue is supplicant, NM or driver. Final note: I am also seeing issues with WPA Enterprise (LEAP and EAP-TLS) but figure it makes sense to address the simpler PSK case first (less variables, more control home vs enterprise...) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413874/comments/0 On 2009-02-24T17:45:02+00:00 Nigel wrote: I tried restarting NM, and the problem persisted... ie once we get into this state the "bad" AP cannot be connected to. I then stopped NM and unloaded the iwl3945 module, followed by reloading/restarting NM started and connected to the "good" AP just fine (c). I then clicked on the "bad" AP in the GUI (f) and again it connected perfectly. So is this some form of driver blacklisting/bad state info in iwl3945 driver? >From syslog during driver load: iwl3945 :03:00.0: PCI INT A disabled iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26kds iwl3945: Copyright(c) 2003-2008 Intel Corporation iwl3945 :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwl3945 :03:00.0: setting latency timer to 64 iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels iwl3945: Detected Intel Wireless WiFi Link 3945ABG wmaster0 (iwl3945): not using net_device_ops yet phy1: Selected rate control algorithm 'iwl-3945-rs' wlan0 (iwl3945): not using net_device_ops yet iwl3945 :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwl3945 :03:00.0: irq 31 for MSI/MSI-X iwl3945 :03:00.0: firmware: requesting iwlwifi-3945-2.ucode iwl3945 loaded firmware version 15.28.2.8 Registered led device: iwl-phy1:radio Registered led device: iwl-phy1:assoc Registered led device: iwl-phy1:RX Registered led device: iwl-phy1:TX Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413874/comments/1 On 2009-02-24T18:03:25+00:00 Nigel wrote: Created attachment 333072 wpa supplicant log from same time period Added wpa supplicant log -- hopefully from correct times! Also adding options iwl3945 debug=0xbc88 for next time (43fff was too verbose) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413874/comments/2 On 2009-02-24T19:11:14+00:00 Nigel wrote: >From full wpa_supplicant log it appears that Association timeout is the issue -- then causing blacklisting. 1235497219.167758: Selecting BSS from priority group 0 1235497219.167805: Try to find WPA-enabled AP 1235497219.167852: 0: 00:18:84:2a:74:67 ssid='planetf1f' wpa_ie_len=0 rsn_ie_len=20 caps=0x11 1235497219.167921:skip - disabled 1235497219.167973:selected based on RSN IE 1235497219.168020:selected WPA AP 00:18:84:2a:74:67 ssid='planetf1f' 12
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
Hi, Thanks for your comments. I'm updating as "Invalid" since you have no more access to that hardware. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
Hi, I no longer own the hardware mentioned in this post and are unable to confirm the current status. Sorry. Thanks for getting back to me in any way. -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
Hi, Please, can you tell us whether this is still an issue for you? It seem to be solved. ** Tags added: jaunty ** Changed in: linux (Ubuntu) Status: New => Incomplete -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
** Changed in: linux Status: Unknown => Fix Released -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
** Also affects: linux via https://bugzilla.redhat.com/show_bug.cgi?id=487183 Importance: Unknown Status: Unknown -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
Redhat Bugzilla #487183 (https://bugzilla.redhat.com/show_bug.cgi?id=487183) reports a similar issue as failure case 2. Reported fixed in "kernel- PAE-2.6.29-0.176.rc6.git5.fc11.i686", so there is hope that (part of) this bug might be fixed in a later kernel. ** Bug watch added: Red Hat Bugzilla #487183 https://bugzilla.redhat.com/show_bug.cgi?id=487183 -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
Output from syslog and matched with output from wpa_supplicant over the same period; Aug 15 02:22:43 cg-dell-laptop kernel: [41851.362704] Registered led device: iwl-phy0:radio Aug 15 02:22:43 cg-dell-laptop kernel: [41851.362725] Registered led device: iwl-phy0:assoc Aug 15 02:22:43 cg-dell-laptop kernel: [41851.362778] Registered led device: iwl-phy0:RX Aug 15 02:22:43 cg-dell-laptop kernel: [41851.362793] Registered led device: iwl-phy0:TX Aug 15 02:22:43 cg-dell-laptop kernel: [41851.382400] ADDRCONF(NETDEV_UP): wlan0: link is not ready Aug 15 02:22:46 cg-dell-laptop kernel: [41854.265714] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:22:46 cg-dell-laptop kernel: [41854.464123] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 2 Aug 15 02:22:46 cg-dell-laptop kernel: [41854.664450] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 3 Aug 15 02:22:47 cg-dell-laptop kernel: [41854.864504] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 timed out Aug 15 02:22:57 cg-dell-laptop kernel: [41865.670080] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:22:57 cg-dell-laptop kernel: [41865.671651] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:22:58 cg-dell-laptop kernel: [41865.868239] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 2 Aug 15 02:22:58 cg-dell-laptop kernel: [41866.068242] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 3 Aug 15 02:22:58 cg-dell-laptop kernel: [41866.268055] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 timed out Aug 15 02:23:09 cg-dell-laptop kernel: [41877.097659] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:23:09 cg-dell-laptop kernel: [41877.304481] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 2 Aug 15 02:23:09 cg-dell-laptop kernel: [41877.504246] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 3 Aug 15 02:23:09 cg-dell-laptop kernel: [41877.705238] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 timed out Aug 15 02:23:20 cg-dell-laptop kernel: [41888.590756] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:23:20 cg-dell-laptop kernel: [41888.591526] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:23:21 cg-dell-laptop kernel: [41888.788243] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 2 Aug 15 02:23:21 cg-dell-laptop kernel: [41888.988259] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 3 Aug 15 02:23:21 cg-dell-laptop kernel: [41889.188243] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 timed out Aug 15 02:23:32 cg-dell-laptop kernel: [41899.971467] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:32 cg-dell-laptop kernel: [41899.972371] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:32 cg-dell-laptop kernel: [41900.172239] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:32 cg-dell-laptop kernel: [41900.372240] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:32 cg-dell-laptop kernel: [41900.572239] wlan0: authentication with AP 00:04:ed:5b:b9:c9 timed out Aug 15 02:23:43 cg-dell-laptop kernel: [41911.293628] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:43 cg-dell-laptop kernel: [41911.294394] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:43 cg-dell-laptop kernel: [41911.492236] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:43 cg-dell-laptop kernel: [41911.692052] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:44 cg-dell-laptop kernel: [41911.892048] wlan0: authentication with AP 00:04:ed:5b:b9:c9 timed out Aug 15 02:23:54 cg-dell-laptop kernel: [41922.742190] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:23:54 cg-dell-laptop kernel: [41922.744827] wlan0: direct probe to AP 00:04:ed:5b:b9:c9 try 1 Aug 15 02:23:54 cg-dell-laptop kernel: [41922.744844] wlan0 direct probe responded Aug 15 02:23:54 cg-dell-laptop kernel: [41922.744849] wlan0: authenticate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:54 cg-dell-laptop kernel: [41922.748440] wlan0: authenticated Aug 15 02:23:54 cg-dell-laptop kernel: [41922.748443] wlan0: associate with AP 00:04:ed:5b:b9:c9 Aug 15 02:23:54 cg-dell-laptop kernel: [41922.766737] wlan0: RX AssocResp from 00:04:ed:5b:b9:c9 (capab=0x411 status=0 aid=1) Aug 15 02:23:54 cg-dell-laptop kernel: [41922.766741] wlan0: associated Aug 15 02:23:54 cg-dell-laptop kernel: [41922.770064] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Aug 15 02:23:56 cg-dell-laptop avahi-daemon[2884]: Registering new address record for fe80::21c:bfff:fe65:e8c7 on wlan0.*. Aug 15 02:24:05 cg-dell-laptop kernel: [41933.021223] wlan0: no IPv6 routers present ** Attachment added: "wpa_supplicant output matched to syslog output in description" http://launchpadlibrarian.net/30347224/wpa_supplicant-20090815-2.txt -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubu
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
** Attachment added: "wpa_supplicant output (annotated) for Failure Case 3" http://launchpadlibrarian.net/30347019/wpa_supplicant-FailureCase3.txt -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
** Attachment added: "wpa_supplicant output (annotated) for Failure Case 2" http://launchpadlibrarian.net/30347014/wpa_supplicant-FailureCase2.txt -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/30346880/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/30346881/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/30346882/Dependencies.txt ** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/30346883/HalComputerInfo.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/30346884/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/30346885/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/30346888/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/30346889/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/30346892/ProcModules.txt -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries
** Attachment added: "wpa_supplicant output (annotated) for Failure Case 1" http://launchpadlibrarian.net/30346954/wpa_supplicant-FailureCase1.txt -- [jaunty][iwl3945] WPA fully associate only after many retries https://bugs.launchpad.net/bugs/413874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
