NetworkManager 100% cpu usage on WiFi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
After latest upgrade of Hardy Beta NetworkManager utilizes 100% CPU and can't connect to any wireless network. Wired connections works fine.
Before upgrade everything worked fine.
Mar 22 01:53:37 thinkpad NetworkManager: <WARN> nm_signal_
Mar 22 01:53:37 thinkpad NetworkManager: ******************* START *******
Mar 22 01:53:37 thinkpad NetworkManager: (no debugging symbols found)
Mar 22 01:53:37 thinkpad NetworkManager: Using host libthread_db library "/lib/tls/
Mar 22 01:53:37 thinkpad NetworkManager: (no debugging symbols found)
Mar 22 01:53:37 thinkpad last message repeated 10 times
Mar 22 01:53:37 thinkpad NetworkManager: [Thread debugging using libthread_db enabled]
Mar 22 01:53:37 thinkpad NetworkManager: [New Thread 0xb7ba2720 (LWP 6993)]
Mar 22 01:53:37 thinkpad NetworkManager: [New Thread 0xb71ffb90 (LWP 7321)]
Mar 22 01:53:37 thinkpad NetworkManager: [New Thread 0xb7ba1b90 (LWP 7305)]
Mar 22 01:53:37 thinkpad NetworkManager: (no debugging symbols found)
Mar 22 01:53:37 thinkpad last message repeated 9 times
Mar 22 01:53:37 thinkpad NetworkManager: 0xb7fa2410 in __kernel_vsyscall ()
Mar 22 01:53:37 thinkpad NetworkManager: ******************* END *******
Description: Ubuntu hardy (development branch)
Release: 8.04
network-manager - 0.6.6-0ubuntu2
Steven Walter (stevenrwalter) wrote : | #1 |
Egon Kocjan (egon-kocjan) wrote : | #2 |
Same here, I have ipw2200 and wpa2.
Mar 22 09:02:10 konan NetworkManager: <info> Updating allowed wireless network lists.
Mar 22 09:02:10 konan NetworkManager: <info> SWITCH: no current connection, found better connection 'eth1'.
Mar 22 09:02:10 konan NetworkManager: <info> Will activate connection 'eth1/xxxxxxx'.
Mar 22 09:02:10 konan NetworkManager: <info> Device eth1 activation scheduled...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) started...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1/wireless): access point 'xxxxxxx' is encrypted, but NO valid key exists. New key neede
d.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'xxxxxxx'.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) New wireless user key for network 'xxxxxxx' received.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1/wireless): access point 'xxxxxxx' is encrypted, and a key exists. No new key needed.
Mar 22 09:02:10 konan NetworkManager: <info> Disconnected.
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1): cancelling...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1) cancellation handler scheduled...
Mar 22 09:02:10 konan NetworkManager: <info> Activation (eth1): waiting for device to cancel activation.
Mar 22 09:02:11 konan NetworkManager: <WARN> nm_signal_
Mar 22 09:02:11 konan NetworkManager: <info> Activation (eth1): waiting for device to cancel activation.
Mar 22 09:02:11 konan NetworkManager: ******************* START *******
Mar 22 09:02:12 konan NetworkManager: <info> Activation (eth1): waiting for device to cancel activation.
Mar 22 09:02:13 konan NetworkManager: <info> Activation (eth1): waiting for device to cancel activation.
Mar 22 09:02:13 konan NetworkManager: (no debugging symbols found)
Mar 22 09:02:13 konan NetworkManager: Using ho...
caribo (paul-caribo) wrote : | #3 |
Same problem here, 100% CPU usage with the majority being sys rather than user time.
some info:-
dpkg -l | grep network-manager
ii network-manager 0.6.6-0ubuntu2 network management framework daemon
ii network-manager-kde 1:0.2ubuntu1-
lspci -vv
02:03.0 Ethernet controller: Atheros Communications, Inc. AR5413 802.11abg NIC (rev 01)
Subsystem: Atheros Communications, Inc. Unknown device 1062
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 7
Region 0: Memory at f8fe0000 (32-bit, non-prefetchable) [size=64K]
uname -a
Linux paul-laptop 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Mar 22 08:28:55 paul-laptop NetworkManager: <info> SWITCH: found better connection 'ath0' than current connection 'eth0'.
Mar 22 08:28:55 paul-laptop dhcdbd: message_handler: message handler not found under /com/redhat/
Mar 22 08:28:55 paul-laptop NetworkManager: <info> Will activate connection 'ath0/MYSSID'.
Mar 22 08:28:55 paul-laptop NetworkManager: <info> Device ath0 activation scheduled...
Mar 22 08:28:55 paul-laptop NetworkManager: <info> Deactivating device eth0.
Mar 22 08:28:55 paul-laptop dhclient: There is already a pid file /var/run/
Mar 22 08:28:55 paul-laptop dhclient: killed old client process, removed PID file
Mar 22 08:28:55 paul-laptop dhclient: wifi0: unknown hardware address type 801
Mar 22 08:28:55 paul-laptop dhclient: wifi0: unknown hardware address type 801
Mar 22 08:28:55 paul-laptop dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
Mar 22 08:28:55 paul-laptop avahi-daemon[5071]: Withdrawing address record for 192.168.0.4 on eth0.
Mar 22 08:28:55 paul-laptop avahi-daemon[5071]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.4.
Mar 22 08:28:55 paul-laptop avahi-daemon[5071]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 22 08:28:56 paul-laptop avahi-daemon[5071]: Withdrawing address record for fe80::20b:
Mar 22 08:28:56 paul-laptop NetworkManager: <info> Activation (ath0) started...
Mar 22 08:28:56 paul-laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 08:28:56 paul-laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
Mar 22 08:28:56 paul-laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 08:28:56 paul-laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Mar 22 08:28:56 paul-laptop NetworkManager: <inf...
caribo (paul-caribo) wrote : | #4 |
Looks like a duplicate of bug# 204868 -- https:/
Stas Verberkt (legolas) wrote : | #5 |
I don't have the high CPU usage, but I'm also unable to connect to any wireless network:
Mar 22 09:37:51 citry NetworkManager: <debug> [1206175071.558558] nm_device_
Mar 22 09:37:51 citry NetworkManager: <info> User Switch: /org/freedeskto
Mar 22 09:37:51 citry NetworkManager: <info> Deactivating device wlan0_rename.
Mar 22 09:37:53 citry NetworkManager: <info> Device wlan0_rename activation scheduled...
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_rename) started...
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) started...
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) complete.
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) starting...
Mar 22 09:37:53 citry NetworkManager: <info> Activation (wlan0_
Mar 22 09:37:54 citry NetworkManager: <WARN> nm_signal_
Mar 22 09:37:54 citry NetworkManager: ******************* START *******
Mar 22 09:37:54 citry NetworkManager: (no debugging symbols found)
Mar 22 09:37:54 citry NetworkManager: Using host libthread_db library "/lib/tls/
Mar 22 09:37:54 citry NetworkManager: (no debugging symbols found)
Mar 22 09:37:54 citry last message repeated 10 times
Mar 22 09:37:54 citry NetworkManager: [Thread debugging using libthread_db enabled]
Mar 22 09:37:54 citry NetworkManager: [New Thread 0xb7bd9720 (LWP 8445)]
Mar 22 09:37:54 citry NetworkManager: [New Thread 0xb73d7b90 (LWP 8463)]
Mar 22 09:37:54 citry NetworkManager: [New Thread 0xb7bd8b90 (LWP 8456)]
Mar 22 09:37:54 citry NetworkManager: (no debugging symbols found)
Mar 22 09:37:54 citry last message repeated 9 times
Mar 22 09:37:54 citry NetworkManager: 0xb7fe2410 in __kernel_vsyscall ()
Mar 22 09:37:54 citry NetworkManager: ******************* END *******
I'm working on a Intel Core 2 Duo box, using a intel 3945abg adapter, connecting to a wpa encrypted network.
Jesper de Jong (jespdj) wrote : | #6 |
I have the same: NetworkManager uses 100% CPU and does not connect (the "Connecting" logo keeps animating), on a Lenovo Thinkpad T61 running Hardy Beta x86_64:
$ uname -a
Linux nl-l3a9355 2.6.24-12-generic #1 SMP Wed Mar 12 22:31:43 UTC 2008 x86_64 GNU/Linux
$ dpkg -l | grep network-manager
ii network-manager 0.6.6-0ubuntu2 network management framework daemon
ii network-
$ sudo lspci -vv
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
Subsystem: Intel Corporation Lenovo ThinkPad T61
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 505
Region 0: Memory at df3fe000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 41b9
Capabilities: [e0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <512ns, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <128ns, L1 <64us
Link: ASPM L0s Enabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
part of /var/log/syslog:
Mar 22 10:07:36 nl-l3a9355 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 22 10:07:36 nl-l3a9355 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 22 10:07:36 nl-l3a9355 NetworkManager: <info> Activation (wlan0/wireless): access point 'Jesper-WiFi' is encrypted, and a key exists. No new key needed.
Mar 22 10:07:37 nl-l3a9355 NetworkManager: <WARN> nm_signal_
Mar 22 10:07:37 nl-l3a9355 NetworkManager: ******************* START *******
Mar 22 10:07:38 nl-l3a9355 NetworkManager: (no debugging symbols found)
Mar 22 10:07:38 nl-l3a9355 NetworkManager: Using host libthread_db library "/lib/libthread
Mar 22 10:07:38 nl-l3a9355 NetworkManager: (no debugging symbols found)
Mar 22 10:07:38 nl-l3a9355 last message repeated 10 times
Mar 22 10:07:38 nl-l3a9355 NetworkManager: [Thread debugging using libthread_db enabled]
Mar 22 10:07:38 nl-l3a9355 NetworkManager: [New Thread 0x7f40d74b0780 (LWP 5133)]
Mar 22 10:07:38 nl-l3a9355 NetworkManager: [New Thread 0x422c9950 (LWP 5567)]
Mar 22 10:07:38 nl-l3a9355 NetworkManager: [New Thread 0x414e2950 (LWP 5510)]
Mar 22 10:07:38 nl-l3a9355 NetworkManager: (no debugging symbols found)
...
Changed in network-manager: | |
status: | New → Confirmed |
Lee Garrett (leegarrett) wrote : | #7 |
Happens for me too:
100% cpu time is used by NetworkManager.
Which package do I need to install to get the debugging symbols?
root@saitou:
NetworkManager: <info> starting...
NetworkManager: <info> New VPN service 'openvpn' (org.freedeskto
NetworkManager: <info> New VPN service 'vpnc' (org.freedeskto
NetworkManager: <info> ath0: Device is fully-supported using driver '(null)'.
NetworkManager: <info> ath0: driver does not support SSID scans (scan_capa 0x00).
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wireless (802.11) device 'ath0'.
NetworkManager: <info> Deactivating device ath0.
NetworkManager: <info> Found dial up configuration for dsl-provider via Modem: bei_franzi
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <debug> [1206180557.872567] nm_device_
NetworkManager: <info> User Switch: /org/freedeskto
NetworkManager: <info> Deactivating device ath0.
NetworkManager: <info> Device ath0 activation scheduled...
NetworkManager: <info> Activation (ath0) started...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (ath0/wireless): access point 'tina' is encrypted, but NO valid key exists. New key needed.
NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'tina'.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info> Activation (ath0) New wireless user key for network 'tina' received.
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> Activation (ath0/wireless): access point 'tina' is encrypted, and a key exists. No new key needed.
NetworkManager: <WARN> nm_signal_
NetworkManager: ******************* START *******
NetworkManager: (no debugging symbols found)
NetworkManager: Using host libthread_db library "/lib/tls/
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging s...
Lee Garrett (leegarrett) wrote : | #8 |
I forgot to mention: using Xubuntu Hardy on ath_pci.
Lee Garrett (leegarrett) wrote : | #9 |
I updated the following packages and now it works again:
acpi-support (0.107) to 0.108
grub (0.97-29ubuntu18) to 0.97-29ubuntu19
hal (0.5.11~
libhal-storage1 (0.5.11~
libhal1 (0.5.11~
libx86-1 (0.99-1.2ubuntu2) to 0.99-1.2ubuntu3
xubuntu-docs (8.04.1) to 8.04.2
This is what is in the changelog:
hal (0.5.11~
* debian/rules: build using --with-
break packages that were assuming this worked right up through beta.
LP: #204768.
-- Steve Langasek <email address hidden> Fri, 21 Mar 2008 20:24:33 +0000
Looks like this made NetworkManager break.
It would be interesting to look into this bug anyway, to make NetworkManager more robust. I had to kill NetworkManager with -9, as it wouldn't terminate otherwise.
Regards,
Lee
Gabor Halaszvari (g-halaszvari) wrote : | #10 |
I have the same problems here. Using Hardy Beta upgraded from Gutsy on a HP nx7400 (iwl3945).
Logs:
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) started...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0/wireless): access point 'portmax' is encrypted, but NO valid key exists. New key needed.
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'portmax'.
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) New wireless user key for network 'portmax' received.
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 22 11:39:46 nx7400 NetworkManager: <info> Activation (wlan0/wireless): access point 'portmax' is encrypted, and a key exists. No new key needed.
Mar 22 11:39:47 nx7400 NetworkManager: <WARN> nm_signal_
Mar 22 11:39:48 nx7400 NetworkManager: ******************* START *******
Mar 22 11:39:48 nx7400 NetworkManager: (no debugging symbols found)
Mar 22 11:39:48 nx7400 NetworkManager: Using host libthread_db library "/lib/tls/
Mar 22 11:39:48 nx7400 NetworkManager: (no debugging symbols found)
Mar 22 11:39:48 nx7400 last message repeated 10 times
Mar 22 11:39:48 nx7400 NetworkManager: [Thread debugging using libthread_db enabled]
Mar 22 11:39:48 nx7400 NetworkManager: [New Thread 0xb7b7d720 (LWP 5238)]
Mar 22 11:39:48 nx7400 NetworkManager: [New Thread 0xb737bb90 (LWP 5437)]
Mar 22 11:39:48 nx7400 NetworkManager: [New Thread 0xb7b7cb90 (LWP 5427)]
Mar 22 11:39:48 nx7400 NetworkManager: (no debugging symbols found)
Mar 22 11:39:48 nx7400 last message repeated 9 times
Mar 22 11:39:48 nx7400 NetworkManager: 0xb7f80410 in __kernel_vsyscall ()
Mar 22 11:39:48 nx7400 NetworkManager: ******************* END *******
# dpkg -l | grep network-manager
ii network-manager 0.6.6-0ubuntu2 network management framework daemon
ii ...
Alastair Sherringham (asherringham) wrote : | #11 |
Thanks Lee.
Those updates have fixed it for me as well. Having only installed the beta yesterday, it was very disappointing to see the NM breakage.
I hope there's no further disruption (or deeper problem).
Now I can continue testing ...
Alastair
Henning Moll (drscott) wrote : | #12 |
I am still having that problem (__kernel_
acpi-support 0.108
grub 0.97-29ubuntu19
hal 0.5.11~rc2-1ubuntu2
libhal-storage1 0.5.11~rc2-1ubuntu2
libhal1 0.5.11~rc2-1ubuntu2
libx86-1 0.99-1.2ubuntu3
Stas Verberkt (legolas) wrote : | #13 |
Those updates fixed the problem for me too
slamdunk (antongiulio05) wrote : | #14 |
Fixed for me too.
Thomas Heidrich (gnuheidix) wrote : | #15 |
I'm also still having that problem. Updates didn't fix it. :-(
kellyness@hotmail.com (kellyness) wrote : | #16 |
Same problem for me. The latest update didn't fix the problem. CPU still pegged w/ network manager(only w/ wireless enabled)
Migizi (nigot30) wrote : | #17 |
Those updates are applied on my machine and didn't help. I'm running an XPS1330 with a stupid Broadcom wireless card. Anyways, if go into Network under Administration and manually configure my wireless instead of leaving it on roaming it connects and doesn't peg out my CPU. At least this will get me going till it is fixed.
Elias K Gardner (zorkerz) wrote : | #18 |
i can confirm your workaround migizi
slamdunk (antongiulio05) wrote : | #19 |
@Migizi
I have a Dell XPS M1330. This is my wireless card:
Intel Corporation PRO/Wireless 4965 AG or AGN
but I have a Broadcom for ethernet
However updates worked for me.
Barteq (barteqpl) wrote : | #20 |
Hal patches relased today have fixed issue. Now network manager works fine.
Thomas Heidrich (gnuheidix) wrote : | #21 |
@Barteq: Thats not true. My wireless card is still refusing to work properly and I'm still having problems with the 100% CPU load of the NetworkManager.
Jan Frybort (jan.frybort) wrote : | #22 |
The updates solved it for me.
Braders (keith-bradford) wrote : | #23 |
Excellent - fixed it for me.
Barteq (barteqpl) wrote : | #24 |
@Thomas Heidrich
Some reports here confirms and some denies this issue after upgrade. Of course I'm talking about my very configuration, but it doesn't mean that it works on everyone's computer.
Before patch NM was polling something many times per second (watched via strace command). It looked like infinite loop.
Now it stays quiet in background and I`am able to see many other actions not only polling events. And it uses 0% cpu not 100% and makes me able to connect via WiFi (which I'm using right now). So in my case issue is resolved.
-- edit
While writing this post something strage happened. I was deauthenticated from AP, and can't connect once more.. In logs are many errors like
[ 6438.416453] wlan0: authenticated
[ 6438.416454] wlan0: associate with AP 00:13:10:4a:c6:88
[ 6438.417373] wlan0: RX ReassocResp from 00:13:10:4a:c6:88 (capab=0x431 status=0 aid=3)
[ 6438.417376] wlan0: associated
[ 6441.606793] wlan0: RX deauthentication from 00:13:10:4a:c6:88 (reason=2)
[ 6441.606802] wlan0: deauthenticated
So.. something happend or maybe it's a normal issue that reathentication using wpa-psk takes about 4 minutes to became valid?
Steven Walter (stevenrwalter) wrote : | #25 |
Seems like the common thread is that the HAL update does not fix broadcom users. I have a broadcom card here, and still have trouble with network-manager, despite having all updates.
Steven Walter (stevenrwalter) wrote : Found a fix | #26 |
- Don't apply ubuntu patches Edit (317 bytes, text/plain)
I rebuilt network-manager from source. If I disable all of ubuntu's patches, network-manager no longer crashes and associates with my network successfully. Apply this patch and rebuild network-manager; see if it fixes the crash for anybody else.
Henning Moll (drscott) wrote : | #27 |
The patch from Steven Walter (disabling ubuntu patches) solved the problem for me...
caribo (paul-caribo) wrote : | #28 |
downgrading hal, libhal & network-manager and re-applying latest updates seems to have resolved this problem for me....
downgraded to:-
/var/cache/
/var/cache/
/var/cache/
/var/cache/
/var/cache/
upgraded to:-
ii hal 0.5.11~rc2-1ubuntu2 Hardware Abstraction Layer
ii hal-info 20080317+
ii libhal-storage1 0.5.11~rc2-1ubuntu2 Hardware Abstraction Layer - shared library
ii libhal1 0.5.11~rc2-1ubuntu2 Hardware Abstraction Layer - shared library
ii network-manager 0.6.6-0ubuntu2 network management framework daemon
hmmm...... ????
Thomas Heidrich (gnuheidix) wrote : | #29 |
@caribo: That didn't work for me.
jyks (jyks) wrote : | #30 |
Using b43 driver for Broadcom 4311 (rev 01) card. Updates had not worked for me. Compiling from sources & disabling ubuntu patches as suggested by Steven Walter works like a charm.
jyks (jyks) wrote : | #31 |
Bug #204868 seems similar to this. debdiff by Emanuel Steen there also works for me. The debdiff seems to be more fine-grained patch than disabling all ubunu patches.
Thomas Heidrich (gnuheidix) wrote : | #32 |
Simply downgrading the NetworkManager to 0.6.6-0ubuntu1_i386 solved the problem for me. 8)
WiFi is up.
Elias K Gardner (zorkerz) wrote : Re: [Bug 204931] Re: NetworkManager 100% cpu usage on WiFi | #33 |
Im not quite sure about this but i suspect from peoples opposite response to
a number of the workarounds posted that we may be dealing with more than one
bug.
AJ (akertis) wrote : | #34 |
I upgraded from gutsy to hardy and I still have the 2.6.22 kernel and for some reason when I run that kernel NetworkManager doesn't have any issues. I'm using the bcm43xx kernel module. I haven't tried to downgrade NetworkManager yet.
AJ (akertis) wrote : | #35 |
Just downgrading to the previous networkmanager_
kellyness@hotmail.com (kellyness) wrote : | #36 |
you guys rule. just updated and it works....
thanks,
Kelly
Steven Walter (stevenrwalter) wrote : | #37 |
I can verify that network-
Henning Moll (drscott) wrote : | #38 |
fixed :-)
Ferdinand Hagethorn (ferdinand-hagethorn) wrote : | #39 |
Seems to work here now!
On Sat, 2008-03-22 at 09:37 +0000, JesperDJ wrote:
> I have the same: NetworkManager uses 100% CPU and does not connect (the
> "Connecting" logo keeps animating), on a Lenovo Thinkpad T61 running
> Hardy Beta x86_64:
>
> $ uname -a
> Linux nl-l3a9355 2.6.24-12-generic #1 SMP Wed Mar 12 22:31:43 UTC 2008 x86_64 GNU/Linux
>
> $ dpkg -l | grep network-manager
> ii network-manager 0.6.6-0ubuntu2 network management framework daemon
> ii network-
>
> $ sudo lspci -vv
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
> Subsystem: Intel Corporation Lenovo ThinkPad T61
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 505
> Region 0: Memory at df3fe000 (64-bit, non-prefetchable) [size=8K]
> Capabilities: [c8] Power Management version 3
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
> Address: 00000000fee0300c Data: 41b9
> Capabilities: [e0] Express Endpoint IRQ 0
> Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
> Device: Latency L0s <512ns, L1 unlimited
> Device: AtnBtn- AtnInd- PwrInd-
> Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
> Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
> Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
> Link: Latency L0s <128ns, L1 <64us
> Link: ASPM L0s Enabled RCB 64 bytes CommClk+ ExtSynch-
> Link: Speed 2.5Gb/s, Width x1
>
> part of /var/log/syslog:
>
> Mar 22 10:07:36 nl-l3a9355 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
> Mar 22 10:07:36 nl-l3a9355 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
> Mar 22 10:07:36 nl-l3a9355 NetworkManager: <info> Activation (wlan0/wireless): access point 'Jesper-WiFi' is encrypted, and a key exists. No new key needed.
> Mar 22 10:07:37 nl-l3a9355 NetworkManager: <WARN> nm_signal_
> Mar 22 10:07:37 nl-l3a9355 NetworkManager: ******************* START *******
> Mar 22 10:07:38 nl-l3a9355 NetworkManager: (no debugging symbols found)
> Mar 22 10:07:38 nl-l3a9355 NetworkManager: Using host libthread_db library "/lib/libthread
> Mar 22 10:07:38 nl-l3a9355 NetworkManager: (no debugging symbols found)
> Mar 22 10:07:38 nl-l3a9355 last message repeated 10 times
> Mar 22 10:07:38 nl-l3a9355 NetworkManager: [Thread debugging using libthread_db enabled]
> Mar 22 10:07:38 nl-l3a9355 NetworkManager: [New Thread 0x7f40d74b0780 (LWP 5133)]
> Mar 22 10:07:38 nl-l3a9355 NetworkManager: [New Thre...
Jesper de Jong (jespdj) wrote : | #40 |
The fix described in bug #204868 by Emanual Steen, implemented in network-manager version 0.6.6-0ubuntu3, fixes this bug too. From the description of the fix it makes sense; this is definitely the same problem.
Steve (st3v3) wrote : | #41 |
Xubuntu Hardy refused to connect to wifi using NM 0.6.6-0ubuntu5 on Thinkpad X61s with iwl3945 a/b/g wifi.
Building from source and using Steven Walter's patch (not to include Ubuntu patches) seems to have fixed the problem... haven't been able to pinpoint the cause yet.
Steve (st3v3) wrote : | #42 |
...perhaps I spoke too soon - my "working" NM of this morning is no longer working. It looks like I got lucky this morning!
I'll keep looking into it and post back if I find a fix.
I'm seeing this as well:
NetworkManager: <info> Activation (eth1/wireless): access point 'dasbrennen' is handler( ): Caught signal 11. Generating backt ******* ******* ******* ****** i686/cmov/ libthread_ db ******* ******* ******* ******
encrypted, and a key exists. No new key needed.
NetworkManager: <WARN> nm_signal_
race...
NetworkManager: ******************* START *******
NetworkManager: (no debugging symbols found)
NetworkManager: Using host libthread_db library "/lib/tls/
.so.1".
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: (no debugging symbols found)
NetworkManager: 0xb7f48410 in __kernel_vsyscall ()
NetworkManager: ******************* END *******
Using the b43 wireless driver here.