[hardy] Network manager causes CPU load to go to 100%

Bug #204897 reported by Richard Seguin
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Network Manager 0.6.6-0ubuntu2 causes CPU load to go to 100% and will not connect to any wireless network. I am able to manually connect to a network using iwconfig. The problem started when I rebooted after a general system update for hardy.

Things that changed on system
* Java versions

Richard Seguin (sectech)
Changed in network-manager:
assignee: nobody → network-manager
Richard Seguin (sectech)
Changed in network-manager:
assignee: network-manager → nobody
Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

This regression has been detected and corrected. Please upgrade your system.

Changed in network-manager:
status: New → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

Thank you for taking the time to report this bug and help to improve Ubuntu.

This problem was caused by a regression in the hal package, which was previously reported and has been fixed in hal 0.5.11~rc2-1ubuntu2 in the archive.

The network-manager package should eventually be updated to not rely on deprecated hal interfaces, but for hardy this issue is now resolved.

Revision history for this message
Clark Archer (clark-archer) wrote :
Download full text (3.3 KiB)

I have updated to hal 0.5.11~rc2-1ubuntu2 this morning (installed 8.04 beta yesterday as an upgrade from 7.10), and even after a reboot am still seeing network manager 0.6.6-0ubuntu2 consume 100% CPU. This occurs when I remove my ethernet cable and network manager attempts to connect to my wifi network. The following is from the syslog:

Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) started...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1/wireless): access point 'WhiteStar' is encrypted, but NO valid key exists. New key needed.
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'WhiteStar'.
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) New wireless user key for network 'WhiteStar' received.
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Mar 22 10:48:18 swift NetworkManager: <info> Activation (eth1/wireless): access point 'WhiteStar' is encrypted, and a key exists. No new key needed.
Mar 22 10:48:19 swift NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace...
Mar 22 10:48:19 swift NetworkManager: ******************* START **********************************
Mar 22 10:48:19 swift NetworkManager: (no debugging symbols found)
Mar 22 10:48:19 swift NetworkManager: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Mar 22 10:48:19 swift NetworkManager: (no debugging symbols found)
Mar 22 10:48:19 swift last message repeated 10 times
Mar 22 10:48:19 swift NetworkManager: [Thread debugging using libthread_db enabled]
Mar 22 10:48:19 swift NetworkManager: [New Thread 0xb7b2f720 (LWP 4798)]
Mar 22 10:48:19 swift NetworkManager: [New Thread 0xb7b2eb90 (LWP 6519)]
Mar 22 10:48:19 swift NetworkManager: [New Thread 0xb732db90 (LWP 6500)]
Mar 22 10:48:19 swift NetworkManager: (no debugging symbols found)
Mar 22 10:48:19 swift last message repeated 9 times
Mar 22 10:48:19 swift NetworkManager: 0xb7f2f410 in __kernel_vsyscall ()
Mar 22 10:48:19 swift NetworkManager: ********...

Read more...

Revision history for this message
nshaw (nathanashaw) wrote :

I can confirm that I am still experiencing this bug on an up-to-date hardy system, even after it was claimed that a fix was released.

Revision history for this message
kellyness@hotmail.com (kellyness) wrote :

I am having a problem with Network Manager(CPU pegged looking for a wireless network) on an up-to-date Hardy system as well.

Revision history for this message
Richard Seguin (sectech) wrote : Re: [Bug 204897] Re: [hardy] Network manager causes CPU load to go to 100%

It seems to be fixed as far as last nights update went on my side.

On Sat, Mar 22, 2008 at 5:09 PM, <email address hidden> <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 204768 ***
> https://bugs.launchpad.net/bugs/204768
>
> I am having a problem with Network Manager(CPU pegged looking for a
> wireless network) on an up-to-date Hardy system as well.
>
> --
> [hardy] Network manager causes CPU load to go to 100%
> https://bugs.launchpad.net/bugs/204897
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Valentin Neacsu (valentin.neacsu) wrote :

I can confirm it too on a fresh install of Hardy Beta, with all updates installed.

Revision history for this message
Martin Gerdzhev (mgerdjev) wrote :
Download full text (3.3 KiB)

I can confirm it too as of now with all updates installed. Here is the relevant section of /var/log/daemon.log

Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) started...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) scheduled...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) started...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) scheduled...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) complete.
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) starting...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename/wireless): access point 'Marto' is encrypted, but NO valid key exists. New key needed.
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) New wireless user key requested for network 'Marto'.
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) complete.
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) New wireless user key for network 'Marto' received.
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) scheduled...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) started...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) scheduled...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 1 of 5 (Device Prepare) complete.
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename) Stage 2 of 5 (Device Configure) starting...
Mar 23 11:43:41 eraser-laptop NetworkManager: <info> Activation (wlan0_rename/wireless): access point 'Marto' is encrypted, and a key exists. No new key needed.
Mar 23 11:43:42 eraser-laptop NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace...
Mar 23 11:43:42 eraser-laptop NetworkManager: ******************* START **********************************
Mar 23 11:43:42 eraser-laptop NetworkManager: (no debugging symbols found)
Mar 23 11:43:42 eraser-laptop NetworkManager: Using host libthread_db library "/lib/libthread_db.so.1".
Mar 23 11:43:42 eraser-laptop NetworkManager: (no debugging symbols found)
Mar 23 11:43:43 eraser-laptop last message repeated 10 times
Mar 23 11:43:43 eraser-laptop NetworkManager: [Thread debugging using libthread_db enabled]
Mar 23 11:43:43 eraser-laptop NetworkManager: [New Thread 0x7fbb4fced780 (LWP 24288)]
Mar 23 11:43:43 eraser-laptop NetworkManager: [New Thread 0x40830950 (LWP 24304)]
Mar 23 11:43:43 eraser-laptop NetworkManager: [New Thread 0x41c51950 (LWP 24290)]
Mar 23 11:43:43 eraser-laptop NetworkManager: (no debugging symbols found)
Mar 23 11:43:43 eraser-laptop last message repeated 9 times
Mar 23 11:43:43 eras...

Read more...

Revision history for this message
Stuart Read (sread) wrote :

Changed duplicate status to Bug #204868, since the problem is solved by a debdiff there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.