[Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"
Launchpad Bug Tracker
1582011 at bugs.launchpad.net
Fri May 20 19:31:09 UTC 2016
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
Swap Failed, Indefinite hang on reboot/shutdown "Reached target
Status in systemd package in Ubuntu:
This bug has been affecting me since 15.04
Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
I have followed bug #1464917 and installed Xenial-proposed with systemd 229-4ubuntu5 package.
I have finally collected shutdown info using vt9.
Issues collecting info due to what I believe is a timeout where vt9 is not activated when ctl+alt+F9 is pressed. I was able to collect info in vt9 to file "shutdown.text" I appended outputs to file "shutdown.text" the following commands in this order:
systemctl list-jobs >>shutdown.text
systemctl --failed >>shutdown.text
uname -a >>shutdown.text
systemd --version >>shutdown.text
journalctl -b >>shutdown.text
systemctl -all >>shutdown.text
journalctl -xe >>shutdown.text
After gaining these data I was only able to finish the reboot with the alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
Each output I separated upon next boot by hand with a line ######################### for easier perusing.
As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
&& systemctl poweroff' or 'sudo swapoff -a && reboot' which
occasionally fails if SWAP has more data than available RAM. In that
latter case I am left waiting for the hang and then using
alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
before SWAP has a chance to gain data, then I can use any form of
halt, poweroff or menu to shutdown.
I have been unable to get answers from AskUbuntu or the above listed
bug #1464917 "Reached target Shutdown" I am filing this bug per
instructions requested in that bug. Other systemd bugs I have
researched #788303 Debian bug reports, #2930 Github and #3087 Github.
Thanks for your time and efforts to help with this issue.
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
Date: Sun May 15 12:08:34 2016
InstallationDate: Installed on 2015-06-29 (321 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Sony Corporation VGN-FW250J
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
[EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf
[EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
3 overridden configuration files found.
UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
dmi.bios.vendor: American Megatrends Inc.
dmi.board.vendor: Sony Corporation
dmi.chassis.vendor: Sony Corporation
dmi.sys.vendor: Sony Corporation
To manage notifications about this bug go to:
More information about the foundations-bugs