[Bug 469038] New: iwl3945 causing syslog errors related to LED lights
https://bugzilla.novell.com/show_bug.cgi?id=469038 Summary: iwl3945 causing syslog errors related to LED lights Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jrobiso2@ford.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5 My syslog shows the following: kernel: Registered led device: iwl-phy0:radio kernel: Registered led device: iwl-phy0:assoc kernel: Registered led device: iwl-phy0:RX kernel: Registered led device: iwl-phy0:TX which is all well and good. However, right away these start showing up in syslogs: "iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28 iwl3945: No space for Tx" cat /sys/class/leds/iwl*assoc/trigger shows: none ide-disk AC-online BAT0-charging-or-full BAT0-charging BAT0-full phy1rx phy1tx [phy1assoc] phy1radio rfkill1 Because I absolutely HATE the LED light blinking in my face over and over again, I figured out (with help) to echo "none" > /sys/class/leds/iwl-*:assoc/trigger. Note that echo'ing "none" to any of the other 4 trigger files did not stop the blinking - only the assoc trigger did. Now cat on the trigger file shows: [none] ide-disk AC-online BAT0-charging-or-full BAT0-charging BAT0-full phy1rx phy1tx phy1assoc phy1radio rfkill1 Anyhow, as soon as I did that (and made it permanent by adding it to the wireless startup scripts) the REPLY_LEDS_CMD errors stopped happening. Please recall that with the old ipw driver (10.X), the led would be off if there was no connection, blinking while making a connection, and solid once the connection was made. In 11.0 we had no led at all. Now, in 11.1, the led blinked all the time, even after the connection was established. My bug for that (# 462967) was made INVALID because supposedly it is supposed to blink like that. I think it should work like it used to - blink only while establishing the connection. So, here's the rub: Could the blinking actually have been caused by the error in the system's attempts to send LEDS_CMDs, and can we fix whatever is causing that error? Reproducible: Always Steps to Reproduce: 1. buy a laptop with an Intel 3945 wireless 2. connect with Network Manager 3. Watch the pretty blinking led -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c1 --- Comment #1 from Jonathon Robison <jrobiso2@ford.com> 2009-01-23 15:07:59 MST --- Disregard the change to iwl-phy1 vice iwl-phy0 - happened when I re-loaded the firmware. Makes no difference to the bug content. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |hschaa@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c2 --- Comment #2 from Jonathon Robison <jrobiso2@ford.com> 2009-01-25 17:04:25 MST --- Also - getting the following in /var/log/NetworkManager: Jan 25 18:53:53 Jons NetworkManager: <debug> [1232927633.213552] periodic_update(): Roamed from BSSID 00:12:17:0A:DA:2F (AirnetA) to (none) ((none)) Jan 25 18:53:59 Jons NetworkManager: <debug> [1232927639.221032] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) Jan 25 18:55:53 Jons NetworkManager: <debug> [1232927753.297772] periodic_update(): Roamed from BSSID 00:12:17:0A:DA:2F (AirnetA) to (none) ((none)) Jan 25 18:55:59 Jons NetworkManager: <debug> [1232927759.301270] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) Jan 25 18:57:53 Jons NetworkManager: <debug> [1232927873.374002] periodic_update(): Roamed from BSSID 00:12:17:0A:DA:2F (AirnetA) to (none) ((none)) Jan 25 18:57:59 Jons NetworkManager: <debug> [1232927879.376987] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) Jan 25 18:59:53 Jons NetworkManager: <debug> [1232927993.441017] periodic_update(): Roamed from BSSID 00:12:17:0A:DA:2F (AirnetA) to (none) ((none)) Jan 25 18:59:59 Jons NetworkManager: <debug> [1232927999.445036] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) Jan 25 19:01:53 Jons NetworkManager: <debug> [1232928113.514002] periodic_update(): Roamed from BSSID 00:12:17:0A:DA:2F (AirnetA) to (none) ((none)) Jan 25 19:01:59 Jons NetworkManager: <debug> [1232928119.517013] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) Given the very short interval between these errors, having the light blink during association would lead to a heck of a lot of blinking. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c3 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jrobiso2@ford.com --- Comment #3 from Helmut Schaa <hschaa@novell.com> 2009-01-26 01:04:21 MST --- Uhh, that looks pretty strange. Could you please additionally attach /var/log/wpa_supplicant and /var/log/messages when these messages appear? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c4 --- Comment #4 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 05:39:51 MST --- Created an attachment (id=267587) --> (https://bugzilla.novell.com/attachment.cgi?id=267587) var-log-messages file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c5 --- Comment #5 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 05:41:00 MST --- Created an attachment (id=267589) --> (https://bugzilla.novell.com/attachment.cgi?id=267589) var-log-NetworkManager -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c6 --- Comment #6 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 05:41:30 MST --- Created an attachment (id=267590) --> (https://bugzilla.novell.com/attachment.cgi?id=267590) wpa-supplicant log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c7 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jrobiso2@ford.com | --- Comment #7 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 05:42:05 MST --- OK. Last night I changed the WPA keys, so I have grabbed the logs that start when that change started working. [NetworkManager doesn't seem to want to let you change keys - you have to delete the network connection and create a new one]. Also, these logs are from after upgrading the firmware to the latest from Intel - the iwlwifi-3945-2.ucode (vice the -1.ucode). Hmm . . . had to add attachments one at a time. Sorry about that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c8 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jrobiso2@ford.com --- Comment #8 from Helmut Schaa <hschaa@novell.com> 2009-01-26 05:50:03 MST --- (In reply to comment #7)
Also, these logs are from after upgrading the firmware to the latest from Intel - the iwlwifi-3945-2.ucode (vice the -1.ucode).
That ucode won't work with 2.6.27 shipped with 11.1. Only API-version 1 ucodes are supported. However, could you please enable wpa_supplicant debugging (see [1]) and attach /var/log/wpa_supplicant again with full debug output? I wasn't able to reproduce the problem here. [1] http://en.opensuse.org/Tracking_down_wireless_problems -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c9 --- Comment #9 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 05:53:56 MST --- I can do that this afternoon. Currently stuck in **shudder** Windows XP making new network login scripts in VBScript (somebody please kill me before they make me use Visual Studio!) Also - the firmware seem to be doing OK (I ended up symlinking new to old), but I'll put the old back if you say so. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c10 --- Comment #10 from Helmut Schaa <hschaa@novell.com> 2009-01-26 06:08:02 MST --- (In reply to comment #9)
Also - the firmware seem to be doing OK (I ended up symlinking new to old)
You may put the firmware there but please don't link .1 to .2 as these are different API versions and might cause real harm then. If the driver is able to use API version 2 it will just pick the .2 file and otherwise the .1. So you can put both versions there and the driver will pick the one it supports. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c11 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@novell.com --- Comment #11 from Helmut Schaa <hschaa@novell.com> 2009-01-26 06:24:40 MST --- Tambet, could you please have a look at the NM log in comment #5. Did you see something similar already? Any idea? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c12 --- Comment #12 from Tambet Ingo <tambet@novell.com> 2009-01-26 08:11:41 MST --- Nope, I haven't seen such roaming spam before. Here's what's happening: NM polls periodically the driver to get it's BSSID to detect roaming. It does so by using SIOCGIWAP ioctl and then matches the result with already scanned APs. So it looks like every second ioctl fails? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c13 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #267587|0 |1 is obsolete| | Attachment #267589|0 |1 is obsolete| | Attachment #267590|0 |1 is obsolete| | Status|NEEDINFO |NEW Info Provider|jrobiso2@ford.com | --- Comment #13 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 11:17:24 MST --- Created an attachment (id=267728) --> (https://bugzilla.novell.com/attachment.cgi?id=267728) Log file tarball OK, I dropped down to runlevel 1, moved all the logs files to *.old, touched them, then changed to runlevel 5. I also pulled the wired connection here at work so it would use the wireless. WPA debug is on. This tarball contains /var/log/messages, /var/log/NetworkManager, and /var/log/wpa_supplicant.log. The only difference you might need to know is that here at work we use Dynamic WEP with LEAP, whereas at home it was WPA-Personal. But the same errors still show up in the logs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c14 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jrobiso2@ford.com --- Comment #14 from Helmut Schaa <hschaa@novell.com> 2009-01-26 11:32:40 MST --- Thanks Jonathon. The network you're trying to associate is hidden. What about your home network? Is it hidden too? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c15 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hschaa@novell.com |tambet@novell.com --- Comment #15 from Helmut Schaa <hschaa@novell.com> 2009-01-26 11:37:43 MST --- However the logs indicate that the wireless card is not really disassociating and associating again and again. I assume this is only a bug in NetworkManager when dealing with hidden networks. Hence reassigning to Tambet. Tambet, NM triggers a scan every once in a while. As this scan is a broadcast scan it will not find the hidden AP and NM thinks the AP is gone. After that wpa_supplicant also thinks the AP is gone and triggers a ssid scan which finds the AP again. I'm not sure but maybe something like below might fix this issue. diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c index 0e8555e..b0c4e75 100644 --- a/src/nm-device-wifi.c +++ b/src/nm-device-wifi.c @@ -809,7 +809,7 @@ periodic_update (NMDeviceWifi *self) NMAccessPoint *new_ap; guint32 new_rate; - new_ap = get_active_ap (self, NULL, FALSE); + new_ap = get_active_ap (self, NULL, TRUE); if (new_ap) nm_device_wifi_update_signal_strength (self, new_ap); -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c16 --- Comment #16 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 11:44:11 MST --- Home network is NOT hidden. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|jrobiso2@ford.com |tambet@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|tambet@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c17 --- Comment #17 from Jonathon Robison <jrobiso2@ford.com> 2009-01-26 21:00:57 MST --- Also, I have put the ucode-1 file back and deleted the ucode-2 (and deleted the symlink that pointed ucode-1 to ucode-2). The issue with 2 bars is back. So it may be reasonable to assume that the "only 2 bars" issue noted in other iwl3945 bug reports is a firmware issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c18 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jrobiso2@ford.com --- Comment #18 from Helmut Schaa <hschaa@novell.com> 2009-01-27 00:54:03 MST --- (In reply to comment #16)
Home network is NOT hidden.
Hmm, and you get the same roaming messages as at work? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c19 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jrobiso2@ford.com | --- Comment #19 from Jonathon Robison <jrobiso2@ford.com> 2009-01-27 06:18:37 MST --- Yep. Exactly the same. AirnetA to none, none to AirnetA, back and forth, etc. I named the home ESSID AirnetA 'cuz work uses AirnetL. It was easy to remember. Made my church's one AirnetB. :-) The home wireless used to be hidden, but I changed that months ago when I went to WPA vice WEP. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c20 --- Comment #20 from Tambet Ingo <tambet@novell.com> 2009-01-29 02:12:43 MST --- Helmut, I'm not convinced at all it's a NM issue. :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c21 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jrobiso2@ford.com --- Comment #21 from Helmut Schaa <hschaa@novell.com> 2009-01-29 02:32:49 MST --- I'm not sure too :) but neither the drivers log nor the supplicant log shows that much assocs/disassocs happening. Jonathon, could you please run iwevent and attach the output here when you get this huge amount of roaming messages in the NetworkManager log? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c22 Jonathon Robison <jrobiso2@ford.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jrobiso2@ford.com | --- Comment #22 from Jonathon Robison <jrobiso2@ford.com> 2009-01-29 07:48:09 MST --- Here's the NetworkManager log for a short period: Jan 29 09:43:23 Jons NetworkManager: <debug> [1233240203.212757] periodic_update(): Roamed from BSSID 00:1E:4A:54:DD:F0 (AirnetL) to (none) ((none)) Jan 29 09:43:29 Jons NetworkManager: <debug> [1233240209.216989] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:4A:54:DD:F0 (AirnetL) Jan 29 09:44:53 Jons NetworkManager: <debug> [1233240293.261803] periodic_update(): Roamed from BSSID 00:1E:4A:54:DD:F0 (AirnetL) to (none) ((none)) Jan 29 09:44:59 Jons NetworkManager: <debug> [1233240299.264818] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:4A:54:DD:F0 (AirnetL) and now here's the iwevent output for the same period: 09:43:15.469046 airnet Scan request completed 09:43:24.178420 airnet Scan request completed 09:44:55.480892 airnet Scan request completed 09:45:04.192880 airnet Scan request completed Also, I noted last night - when using the wireless for some heavy traffic (I was watching hulu.com videos) the roams stopped. I presume that the videos are streamed using UDP (why waste TCP acks on streams?) if that matters. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c23 --- Comment #23 from Jonathon Robison <jrobiso2@ford.com> 2009-01-29 19:06:12 MST --- Hmm. At work, iwevent got the above. Here at home, while getting the same "Roamed" message in NetworkManager: Jan 29 20:49:16 Jons NetworkManager: <debug> [1233280156.381954] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) ==============================Jan 29 21:00:56 Jons NetworkManager: <info> (airnet): supplicant connection state: completed -> associated Jan 29 21:00:57 Jons NetworkManager: <info> (airnet): supplicant connection state: associated -> 4-way handshake Jan 29 21:01:07 Jons NetworkManager: <info> (airnet): supplicant connection state: 4-way handshake -> disconnected Jan 29 21:01:07 Jons NetworkManager: <info> (airnet): supplicant connection state: disconnected -> scanning Jan 29 21:01:07 Jons NetworkManager: <info> (airnet): supplicant connection state: scanning -> disconnected Jan 29 21:01:10 Jons NetworkManager: <debug> [1233280870.787529] periodic_update(): Roamed from BSSID 00:12:17:0A:DA:2F (AirnetA) to (none) ((none)) Jan 29 21:01:10 Jons NetworkManager: <info> (airnet): supplicant connection state: disconnected -> associating Jan 29 21:01:11 Jons NetworkManager: <info> (airnet): supplicant connection state: associating -> associated Jan 29 21:01:12 Jons NetworkManager: <info> (airnet): supplicant connection state: associated -> 4-way handshake Jan 29 21:01:12 Jons NetworkManager: <info> (airnet): supplicant connection state: 4-way handshake -> group handshake Jan 29 21:01:12 Jons NetworkManager: <info> (airnet): supplicant connection state: group handshake -> completed Jan 29 21:01:16 Jons NetworkManager: <debug> [1233280876.789950] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:0A:DA:2F (AirnetA) iwevent got the following: 20:50:58.203591 airnet Scan request completed 20:52:58.205865 airnet Scan request completed 20:54:58.210068 airnet Scan request completed 20:56:58.227944 airnet Scan request completed 20:58:58.235372 airnet Scan request completed 21:00:55.908559 airnet Scan request completed 21:00:56.049307 airnet Custom driver event:ASSOCINFO(ReqIEs=00074169726e657441010802040b160c12182432043048606cdd160050f20101000050f20201000050f20201000050f202 RespIEs=010882848b962430486c32040c121860dd06001018020100) 21:00:56.049338 airnet New Access Point/Cell address:00:12:17:0A:DA:2F 21:01:07.054686 airnet New Access Point/Cell address:Not-Associated 21:01:10.758064 airnet Scan request completed 21:01:10.759072 airnet Set Mode:Managed 21:01:10.787206 airnet Set Frequency:2.437 GHz (Channel 6) 21:01:11.012292 airnet Custom driver event:ASSOCINFO(ReqIEs=00074169726e657441010802040b160c12182432043048606cdd160050f20101000050f20201000050f20201000050f202 RespIEs=010882848b962430486c32040c121860dd06001018020000) 21:01:11.012334 airnet New Access Point/Cell address:00:12:17:0A:DA:2F 21:02:58.239168 airnet Scan request completed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c24 --- Comment #24 from Helmut Schaa <hschaa@novell.com> 2009-01-30 01:23:26 MST --- Thanks Jonathon. Tambet, comment #22 shows that NetworkManager prints the roaming messages in sync with receiving the scan results but the driver does not send any associate/disassociate events. Hence I guess this is an NM issue, maybe related to hidden APs. However comment #23 shows that the supplicant is not able to successfully complete the 4-way handshake and therefore disassociates and reassociates with the AP. Jonathon, if this behavior is reproducible could you please open a new bug report for that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c25 --- Comment #25 from Jonathon Robison <jrobiso2@ford.com> 2009-01-30 08:21:05 MST --- I'll try and do some more testing this afternoon (nighttime for you, sorry). I've got half a mind to do an install on another hard drive on the same laptop and see how it behaves with a fresh clean install. The laptop has been repeatedly upgraded since around 10.1, I believe. And considering the amount of hand-edits that have been required (things like manually setting model=dell-m22 in the modprobe/sound file, and hand edits of hal xml files), sometimes I wonder if I can trust the OS not to run away screaming. I'll update the bug this evening or tomorrow. Have a good weekend. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=469038 User jrobiso2@ford.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469038#c26 --- Comment #26 from Jonathon Robison <jrobiso2@ford.com> 2009-02-04 05:22:53 MST --- OK, I have good news and bad: I built another drive (SATA, USB connected) and installed a pristine 11.1 on it. Running KDE4 only (although by default, some kde3 apps, like knetworkmanager, were installed). The issue of "Roam" items in /var/log/NetworkManager does not exist. While I have not yet changed wpa_supplicant to use -dddt, so far it looks better. Note that I do still have (every minute or so) moments when the network "burps" and I have to wait a moment before a web page will load, or a download will start. Very noticeable when doing zypper installs from cli - often the initial attempt to connect to the source will fail, but re-issuing the command works. I will get back to you this evening with results from -dddt on wpa_supplicant. Initial complaint regarding "das blinken lights" still exists. Bloody annoying! I want the old light style back! Blink for initial connection, then stay solid unless you actually LOSE connection and need to re-connect. On a side note, KDE 4.2 (updated from the KDE repo) appears a little more solid than 4.1, but is still a pain to configure, and only God knows what they were thinking with that NetworkManager "widget" instead of knetworkmanager. Solid thinking on openSuSE's part to default to kde3 networkmanager programs even for a KDE4 install. Good job guys. :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com