Ubuntu
network-manager package

NetworkManager stops working intermittently and needs to be restarted

Bug #140034 reported by Tim Hull
This bug report is a duplicate of:  Bug #145683: Network manager crash with WPA. Edit Remove
0
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

On my system (MacBook Core Duo, 2GB RAM/160GB HD), NetworkManager intermittently stops working (and effectively dies) after about 2-3 hours of system use. This problem seems to occur even more frequently when I suspend the laptop, though I believe I've seen it happen when my system has been running constantly as well.

When this happens, the NetworkManager applet disappears from the system tray in GNOME, and my Internet connection ceases to function. Restarting NetworkManager (using command sudo NetworkManager restart in a terminal) makes the icon reappear and my Internet connection then works. However, the problem tends to reoccur frequently.

I am using wired ethernet for my primary network connection, though I also have an Atheros-based wireless card (which does detect open APs in NetworkManager). System is running the latest Ubuntu Gutsy, though I believe I have had this happen on Feisty as well.

Revision history for this message
Tim Hull (thully) wrote :

Here is the daemon.log that shows me using said system on wireless networks, and then NetworkManager crashing.
Marking as confirmed now.

Changed in network-manager:
status: New → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

which network-manager version are you running?

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Tim Hull (thully) wrote : Re: [Bug 140034] Re: NetworkManager stops working intermittently and needs to be restarted

This happens on both 0.6.4-6ubuntu7 (Feisty's version) as well as the
version on Gutsy as of a week or so ago...

On 9/22/07, Alexander Sack <email address hidden> wrote:
>
> which network-manager version are you running?
>
> ** Changed in: network-manager (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> NetworkManager stops working intermittently and needs to be restarted
> https://bugs.launchpad.net/bugs/140034
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Tim Hull (thully)
Changed in network-manager:
status: Incomplete → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

please look at https://wiki.ubuntu.com/DebuggingNetworkManager and do what is described in the DebuggingCrashes paragraph (in gutsy).

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Tim Hull (thully) wrote :

I have managed to determine that the problem only happens with madwifi drivers loaded, and not when they are disabled. Thus, this seems like it could be a madwifi issue - though it could be wireless/networkmanager in general.

Here is the syslog output...

Oct 2 16:47:37 thully-laptop avahi-daemon[5192]: Recieved repsonse with invalid source port 40213 on interface 'eth0.0'
Oct 2 16:50:19 thully-laptop NetworkManager: <WARN> nm_hal_deinit(): libhal shutdown failed - Connection is closed
Oct 2 16:50:19 thully-laptop NetworkManager: <info> Successfully reconnected to the system bus.
Oct 2 16:51:53 thully-laptop avahi-daemon[5192]: Recieved repsonse with invalid source port 40213 on interface 'eth0.0'
Oct 2 16:52:18 thully-laptop avahi-daemon[5192]: Registering new address record for fec0::8:219:e3ff:fe36:556d on eth0.*.
Oct 2 16:52:18 thully-laptop avahi-daemon[5192]: Registering new address record for 2002:8dd5:bb9a:8:219:e3ff:fe36:556d on eth0.*.
Oct 2 16:52:29 thully-laptop NetworkManager: <WARN> nm_hal_deinit(): libhal shutdown failed - Connection is closed
Oct 2 16:52:29 thully-laptop NetworkManager: <info> Successfully reconnected to the system bus.
Oct 2 16:53:20 thully-laptop avahi-daemon[5192]: Recieved repsonse with invalid source port 34049 on interface 'eth0.0'
Oct 2 16:53:26 thully-laptop avahi-daemon[5192]: Recieved repsonse with invalid source port 34049 on interface 'eth0.0'
Oct 2 17:01:09 thully-laptop NetworkManager: <WARN> nm_hal_deinit(): libhal shutdown failed - Connection is closed
Oct 2 17:01:09 thully-laptop NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace...
Oct 2 17:01:09 thully-laptop NetworkManager: <info> Successfully reconnected to the system bus.
Oct 2 17:01:09 thully-laptop NetworkManager: ******************* START **********************************
Oct 2 17:01:10 thully-laptop NetworkManager: (no debugging symbols found)
Oct 2 17:01:10 thully-laptop NetworkManager: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Oct 2 17:01:10 thully-laptop NetworkManager: (no debugging symbols found)
Oct 2 17:01:10 thully-laptop last message repeated 12 times
Oct 2 17:01:10 thully-laptop NetworkManager: [Thread debugging using libthread_db enabled]
Oct 2 17:01:10 thully-laptop NetworkManager: [New Thread -1211967824 (LWP 4867)]
Oct 2 17:01:10 thully-laptop NetworkManager: [New Thread -1211970672 (LWP 9880)]
Oct 2 17:01:10 thully-laptop NetworkManager: [New Thread -1220363376 (LWP 9866)]
Oct 2 17:01:10 thully-laptop NetworkManager: (no debugging symbols found)
Oct 2 17:01:10 thully-laptop last message repeated 4 times
Oct 2 17:01:10 thully-laptop NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Oct 2 17:01:10 thully-laptop NetworkManager: ******************* END **********************************

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

Other bug subscribers

Bug attachments

Remote bug watches

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