Red Hat Bugzilla – Bug 798684
Random delay on Fedora shut-down
Last modified: 2012-03-02 06:56:47 EST
Description of problem:
A delay occurs randomly during the shut-down process of Fedora, for both turning off the system and for rebooting. I read a statement somewhere that a delay occurs when the shut-down process is invoked too soon after start-up. As far as I can check, this appears to be true. Shutting down after a significant amount of time after start-up does not cause the delay. Pressing Esc during shut-down to hide the Plymouth screen and see the messages does not show anything abnormal, except the "write cache" message as reported in bug no. 769747, but I do not know if that bug is related to this issue. This delay can be found reported in some forums, etc., which appear in a Google search, but I could not find any report in Bugzilla, and neither could I find any solution or workaround.
Version-Release number of selected component (if applicable):
14 to 16, although it may still be in 17 and/or Rawhide.
Steps to Reproduce:
1. Start a Fedora desktop system and log in.
2. Turn off the system using the desktop menu, very few seconds after logging in.
A significant delay occurs before the system turns off.
The system turns off in that amount of time that it requires when shutting down normally after several minutes of logging in. In other words, the shut-down process should finish within a few seconds.
The delay also often occurs after a YUM operation, such as installing or updating packages.
What does the command "systemctl list-jobs" print immediately after logging in?
Nothing. 0 jobs listed.
I have also confirmed that the delay sometimes occurs even a long time after login. However, I am unable to find any particular usage pattern that causes it.
Save this script as /lib/systemd/system-shutdown/debug.sh:
mount / -o rw,remount
dmesg > /dmesg.txt
mount / -o ro,remount
Make it executable (chmod +x /lib/systemd/system-shutdown/debug.sh).
Then boot with the following kernel command line parameters:
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0
Reproduce the delay on shutdown.
After booting back, attach the resulting /dmesg.txt file here. Thanks.
OK, I'll do this and report back. If I can get a delay after a short session, well and good, otherwise I don't know when I'll be able to get a delay, because of the random nature of the problem.
Created attachment 567038 [details]
dmesg debug output for delayed shut-down
I have attached the dmesg output from a delayed shut-down. I have also kept a copy of the output from a normal shut-down. I can provide that too, and/or a diff, if you want.
NetworkManager did not quit after SIGTERM and was killed by SIGKILL after a timeout of 90 s.
*** This bug has been marked as a duplicate of bug 739836 ***