OK, if you can change /etc/init/network-manager.conf so the exec line reads:
exec NetworkManager --log-level=DEBUG And apply the attached patch to the n-m sources, rebuild & install, what happens? (As you need syslogd to stay up to log the results, just 'sudo stop network-manager' and have a in /var/log/syslog.) I see (slightly edited): Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> caught signal 15, shutting down normally. Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): device state change: activated -> disconnected (reason 'connection-removed') [100 30 38] Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): deactivating device (reason 'connection-removed') [38] Mar 4 22:07:44 xubuntu NetworkManager[27154]: <debug> [nm-dhcp-client.c:148] nm_dhcp_client_stop_pid(): Sending SIGTERM to 27161. Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): canceled DHCP transaction, DHCP client pid 27161 ?field.comment=OK, if you can change /etc/init/network-manager.conf so the exec line reads: exec NetworkManager --log-level=DEBUG And apply the attached patch to the n-m sources, rebuild & install, what happens? (As you need syslogd to stay up to log the results, just 'sudo stop network-manager' and have a in /var/log/syslog.) I see (slightly edited): Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> caught signal 15, shutting down normally. Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): device state change: activated -> disconnected (reason 'connection-removed') [100 30 38] Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): deactivating device (reason 'connection-removed') [38] Mar 4 22:07:44 xubuntu NetworkManager[27154]: <debug> [nm-dhcp-client.c:148] nm_dhcp_client_stop_pid(): Sending SIGTERM to 27161. Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): canceled DHCP transaction, DHCP client pid 27161 ** Patch added: "Patch to add some debug to n-m" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614/+attachment/4007427/+files/nm-dbg.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1169614 Title: /etc/init.d/umountroot: "mount: / is busy" due to dhclient is not stopped Status in “network-manager” package in Ubuntu: Triaged Bug description: The result is "mount: / is busy" and root filesystem recovery during next boot. network-manager 0.9.8.0-0ubuntu3 in Raring neither stop dhclient in response to "stop network-manager" nor remove pid file from /run/sendsigs.omit.d/ So dhclient skipped by /etc/init.d/sendsigs and a lease file is open for writing in /var/lib/NetworkManager while /etc/init.d/umountroot is running. As a consequence root filesystem can not be cleanly remount readonly before poweroff. In default setup the problem is hidden by plymouth. The problem does not appear if network is disabled or the cable is unplugged before shutdown. There are some other bugs that might be caused by this issue: Bug lp: #1073433 Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
