Slow shutdown after booting with systemd

Bug #1429143 reported by Colin Law
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When running vivid booted with systemd kernel, shutdown consistently takes around 90 seconds. With the normal kernel it is about 15 seconds.

In the log, shutdown started (from the cog) at 13:50:20, Mar 6th. The purple Ubuntu screen with dots appears after a few seconds and then sits there. It actually powered off at 13:51:55.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: colinl 1948 F.... pulseaudio
 /dev/snd/controlC1: colinl 1948 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Mar 6 13:54:29 2015
InstallationDate: Installed on 2014-10-21 (135 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 init=/lib/systemd/systemd
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU

Revision history for this message
Colin Law (colin-law) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
affects: linux (Ubuntu) → systemd (Ubuntu)
Changed in systemd (Ubuntu):
status: Confirmed → New
Revision history for this message
Martin Pitt (pitti) wrote :

Can you please boot without "quiet" and "splash" (in the grub menu, edit the default boot entry), then shut down. There should be a line like "waiting for job .... to shut down" and some asterisks. Which is that? If you don't get such a thing, please have a look at "Debugging boot/shutdown problems" in /usr/share/doc/systemd/README.Debian . Thanks!

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Colin Law (colin-law) wrote :

Oops, following Martin's helpful pointers I see that it was down to one my home-brewed services that does not seem to like being run via systemd. Likely a problem of my own making.

Thanks for the help and sorry for the noise.

Changed in systemd (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Martin Pitt (pitti) wrote :

Well, we do want to know about/fix issues like "that system does not seem to like being run via systemd", as we'll switch to systemd tomorrow :-) So unless it was a problem with a custom init.d script or so, and not with our Ubuntu packages, please do keep filing bugs. Thanks!

Revision history for this message
Colin Law (colin-law) wrote :

Yes, I understand that. Still analysing, but I think it is probably an error in my custom init.d script. Haven't done much with init.d so not sure what is going on yet. Will confirm what it was when I find out.

Revision history for this message
Thiago Martins (martinx) wrote :

I just upgraded my Macbook Air running Vivid / OSX.

With upstart, it boots in about 2 seconds (SSD disc).

With systemd, it takes an eternity to boot!

Also, the shutdown is much slower when with systemd = PID1.

I prefer upstart, so, I'm removing this systemd-sysv thing out of my site.

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.