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 ********************************** -- NetworkManager stops working intermittently and needs to be restarted https://bugs.launchpad.net/bugs/140034 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
