Bug 59223 - Calling poweroff and reboot doesn't work
Summary: Calling poweroff and reboot doesn't work
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-11 01:40 UTC by Henrique Dante de Almeida
Modified: 2014-02-21 17:29 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (56.33 KB, text/plain)
2013-01-11 01:49 UTC, Henrique Dante de Almeida
Details
fstab (560 bytes, text/plain)
2013-01-11 01:50 UTC, Henrique Dante de Almeida
Details
full journal since install (2.07 MB, text/plain)
2013-01-11 01:51 UTC, Henrique Dante de Almeida
Details
ls -lR /dev/disk (3.17 KB, text/plain)
2013-01-11 01:51 UTC, Henrique Dante de Almeida
Details
/proc/swaps (99 bytes, text/plain)
2013-01-11 01:52 UTC, Henrique Dante de Almeida
Details
systemctl list-jobs (385 bytes, text/plain)
2013-01-11 01:52 UTC, Henrique Dante de Almeida
Details
udevadm info -q all -n /dev/sda4 (2.03 KB, text/plain)
2013-01-11 01:52 UTC, Henrique Dante de Almeida
Details
udevadm info -q all -n /dev/sdb4 (2.04 KB, text/plain)
2013-01-11 01:53 UTC, Henrique Dante de Almeida
Details
/proc/mdstat (402 bytes, text/plain)
2013-01-11 01:56 UTC, Henrique Dante de Almeida
Details
dmesg systemd.log_level=debug (142.37 KB, text/plain)
2013-02-03 22:32 UTC, Henrique Dante de Almeida
Details
systemctl dump (256.93 KB, text/plain)
2013-02-03 22:33 UTC, Henrique Dante de Almeida
Details

Description Henrique Dante de Almeida 2013-01-11 01:40:19 UTC
In a fresh install of Arch Linux, calling poweroff or reboot from the command line may get stuck at "Reached target Shutdown", without progressing for more than 10 minutes. It happens frequently. Running the debug shell led to problems with unmounting swap.
Comment 1 Henrique Dante de Almeida 2013-01-11 01:49:41 UTC
Created attachment 72823 [details]
dmesg
Comment 2 Henrique Dante de Almeida 2013-01-11 01:50:08 UTC
Created attachment 72824 [details]
fstab
Comment 3 Henrique Dante de Almeida 2013-01-11 01:51:17 UTC
Created attachment 72825 [details]
full journal since install
Comment 4 Henrique Dante de Almeida 2013-01-11 01:51:50 UTC
Created attachment 72826 [details]
ls -lR /dev/disk
Comment 5 Henrique Dante de Almeida 2013-01-11 01:52:06 UTC
Created attachment 72827 [details]
/proc/swaps
Comment 6 Henrique Dante de Almeida 2013-01-11 01:52:23 UTC
Created attachment 72828 [details]
systemctl list-jobs
Comment 7 Henrique Dante de Almeida 2013-01-11 01:52:55 UTC
Created attachment 72829 [details]
udevadm info -q all -n /dev/sda4
Comment 8 Henrique Dante de Almeida 2013-01-11 01:53:10 UTC
Created attachment 72830 [details]
udevadm info -q all -n /dev/sdb4
Comment 9 Henrique Dante de Almeida 2013-01-11 01:56:26 UTC
Created attachment 72831 [details]
/proc/mdstat
Comment 10 Henrique Dante de Almeida 2013-01-11 01:58:25 UTC
executing "swapoff /dev/sda4" successfully completes the shutdown.
Comment 11 Lennart Poettering 2013-01-14 22:33:27 UTC
Please follow the guide on:

http://freedesktop.org/wiki/Software/systemd/Debugging#Diagnosing_Shutdown_Problems

And try to get the shutdown log explained therein.
Comment 12 Henrique Dante de Almeida 2013-01-31 23:02:10 UTC
(In reply to comment #11)
> Please follow the guide on:
> 
> http://freedesktop.org/wiki/Software/systemd/
> Debugging#Diagnosing_Shutdown_Problems
> 
> And try to get the shutdown log explained therein.

I'm still owing you this one. I hope I can do this until the end of the week. You want systemd.log_level=debug, right ?
Comment 13 Henrique Dante de Almeida 2013-02-03 22:32:43 UTC
Created attachment 74155 [details]
dmesg systemd.log_level=debug
Comment 14 Henrique Dante de Almeida 2013-02-03 22:33:58 UTC
Created attachment 74156 [details]
systemctl dump
Comment 15 Lennart Poettering 2014-02-21 17:29:29 UTC
Hmm, I am pretty sure bugs like this one should be all fixed with 209. Could you retest? Please open a new bug if problem persists.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.