system hangs on shutdown/reboot

[Jean-Baptiste Lallement]

On two machines running Utopic Desktop, the system hangs on shutd own/reboot. It doesn't happen immediately after the boot but after using the machine for a while.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart 1.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
Uname: Linux 3.16.0-16-generic x86_64
.etc.init.bluetooth.override: manual
.etc.init.mountall.override: console output
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 19 10:01:29 2014
InstallationDate: Installed on 2013-09-03 (380 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 --debug
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
modified.conffile..etc.apport.crashdb.conf: [modified]
modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission non accordée: '/etc/at.deny']
modified.conffile..etc.bumblebee.xorg.conf.nouveau: [modified]
modified.conffile..etc.default.cups: [modified]
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission non accordée: '/etc/libvirt/qemu.conf']
mtime.conffile..etc.apport.crashdb.conf: 2014-05-16T10:52:39.045793
mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2014-05-07T08:52:59.777754
mtime.conffile..etc.default.cups: 2014-03-12T09:14:04.955541

[Jean-Baptiste Lallement (jibel)]

syslog with debug mode enabled

[James Hunt (jamesodhunt)]

A few questions:

1) Has this problem always been present for you since upgrading both systems to utopic?
2) Do you have any other systems running utopic that do not manifest the issue?
3) How are you shutting the systems down? Via the Unity menu or via the command line.
4) When you say that the problem doesn't happen immediately after boot do you mean that shutdown is always reliable if the system has just booted?

[Jean-Baptiste Lallement (jibel)]

1) Has this problem always been present for you since upgrading both systems to utopic?
These systems have been upgraded to Utopic since day 1, but I don't reboot them very often. I cannot say exactly when ti stopped working but I know my laptop at least could be shut down successfully with Utopic and this stopped working. Sorry for not being more precise.

2) Do you have any other systems running utopic that do not manifest the issue?
I've a machine running Utopic Server which doesn't have this problem. But the usage is completely different than the 2 other systems.

3) How are you shutting the systems down? Via the Unity menu or via the command line.
Both command line and UI fail in the same way.

4) When you say that the problem doesn't happen immediately after boot do you mean that shutdown is always reliable if the system has just booted?
Yes. If I boot the system, log in and shutdown/Reboot immediately then it works.

[James Hunt (jamesodhunt)]

Can you try replacing your /etc/init.d/umountroot and /etc/init.d/umountfs with the ones from http://bazaar.launchpad.net/~jamesodhunt/ubuntu/trusty/sysvinit/log-open-files-on-shutdown/revision/193 and attaching an updated syslog file?

The end of your syslog shows that wpa_supplicant is still running, so it may be that network-manager is holding up the shutdown (it's happened before).

Also, nullmailer is still running and is very chatty. Could you try disabling that too to see if that helps (remove the package or modify /etc/init.d/nullmailer).

[Jean-Baptiste Lallement (jibel)]

syslog with patch mentioned in previous comment applied. nullmailer has been disabled.

[James Hunt (jamesodhunt)]

Looks like the shutdown never got as far as running umountroot. Do you have a /var/log/shutdown-lsof.log that you can attach to this bug?

I see that all the nullmailer output has gone, but we're still left with wpa_supplicant and dnsmasq output at the end of the log. As such, could you try shutting down the network manager job before the shutdown:

$ sudo stop network-manager

Then checking that wpa_supplicant and dnsmasq are no longer running. Then, try the shutdown and see if that completes.

[Jean-Baptiste Lallement (jibel)]

I stopped network-manager, but wpa-supplicant and dnsmasq were still running. Then switched to a console, stopped lightdm, dnsmasq and wpa_supplicant, but the system is still hanging on shutdown.

/var/log/shutdown-lsof.log attached