NetworkManager uses 95% CPU after changing eth0 to static address

Bug #153816 reported by Rocko
This bug report is a duplicate of:  Bug #145683: Network manager crash with WPA. Edit Remove
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: network-manager

Steps to reproduce:

1. Normal boot with networks eth0 (wired) and eth1, both configured for control by nm-applet ('roaming'), but with no wired network. The wireless connects to an unsecured network and I disable it.

2. I use nm-applet to manually select a configuration where eth0 has a static address.

3. This succeeds, but NetworkManager shows CPU usage around 85-95%. I have to use 'sudo kill -9' to terminate it. If I restart it, it runs normally (ie without high CPU usage).

network-manager is version 0.6.5-0ubuntu10.

The log is:

Oct 17 18:48:20 pegasus NetworkManager: <info> SUP: sending command 'AP_SCAN 0'
Oct 17 18:48:20 pegasus NetworkManager: <info> SUP: response was 'OK'
Oct 17 18:48:20 pegasus NetworkManager: <info> SUP: sending command 'TERMINATE'
Oct 17 18:48:20 pegasus NetworkManager: <info> SUP: response was 'OK'
Oct 17 18:48:39 pegasus NetworkManager: <info> /etc/network/interface changed: rebuilding the device list.
Oct 17 18:48:39 pegasus NetworkManager: <info> Removing wired Ethernet (802.3) device 'eth0'.
Oct 17 18:48:39 pegasus NetworkManager: <info> Deactivating device eth0.
Oct 17 18:48:39 pegasus NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace...
Oct 17 18:48:39 pegasus avahi-daemon[5157]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.1.1.11.
Oct 17 18:48:39 pegasus avahi-daemon[5157]: New relevant interface eth0.IPv4 for mDNS.
Oct 17 18:48:39 pegasus avahi-daemon[5157]: Registering new address record for 10.1.1.11 on eth0.IPv4.
Oct 17 18:48:39 pegasus NetworkManager: ******************* START **********************************
Oct 17 18:48:40 pegasus NetworkManager: (no debugging symbols found)
Oct 17 18:48:40 pegasus NetworkManager: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Oct 17 18:48:40 pegasus NetworkManager: (no debugging symbols found)
Oct 17 18:48:40 pegasus last message repeated 12 times
Oct 17 18:48:42 pegasus NetworkManager: [Thread debugging using libthread_db enabled]
Oct 17 18:48:42 pegasus NetworkManager: [New Thread -1211992400 (LWP 4562)]
Oct 17 18:48:42 pegasus NetworkManager: [New Thread -1228780656 (LWP 5778)]
Oct 17 18:48:42 pegasus NetworkManager: [New Thread -1220387952 (LWP 4693)]
Oct 17 18:48:42 pegasus NetworkManager: [New Thread -1211995248 (LWP 4685)]
Oct 17 18:48:42 pegasus NetworkManager: (no debugging symbols found)
Oct 17 18:48:42 pegasus last message repeated 4 times
Oct 17 18:48:42 pegasus NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Oct 17 18:48:42 pegasus NetworkManager: ******************* END **********************************

Revision history for this message
Jim Pharis (binbrain) wrote :

Any relation to Bug #83623? I have essentially this problem but I've only noticed it after a suspend. I have the same messages in daemon.log.

Revision history for this message
Alexander Sack (asac) wrote :

this is a duplicate of bug 145683 ... please test the packages mentioned in https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/145683/comments/15

Note: if you get confused why this is technically a _downgrade_ ... thats not a problem ... just take care that you don't upgrade again the version in gutsy right afterwards.

thanks,
 - Alexander

Changed in network-manager:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Pausanias (pausanias) wrote :

This problem persists for me after upgrading to the latest packages (which, if I understand things correctly, have already been pushed to gutsy-updates).

NetworkManager constantly uses 20-30% of my CPU after switching from wireless to eth0.

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.