[Bug 789698] New: Shutdown sometimes hangs
https://bugzilla.novell.com/show_bug.cgi?id=789698 https://bugzilla.novell.com/show_bug.cgi?id=789698#c0 Summary: Shutdown sometimes hangs Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andrea.turrini@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=513168) --> (http://bugzilla.novell.com/attachment.cgi?id=513168) shutdown log on second hang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 It happens in my system that sometimes shutdown hangs. This does not happen every shutdown, but only from time to time. The first time it happened I obtained the following information in the logs after pressing Esc to remove the shutdown splash: Oct 07 22:42:00 orodruin.lotr network[29301]: ..done wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 07 22:42:00 orodruin.lotr ifdown[29775]: wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 07 22:42:01 orodruin.lotr dhcpcd[29819]: wlan0: dhcpcd not running Oct 07 22:42:01 orodruin.lotr dhcpcd[29819]: wlan0: exiting Oct 07 22:42:03 orodruin.lotr network[29301]: ..doneShutting down service (localfs) network . . . . . . . . ...done Oct 07 22:42:41 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:42:41 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:42:51 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:42:51 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:09 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:09 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:13 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:13 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:14 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:14 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:15 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:15 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:15 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:15 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:16 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:16 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:16 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:16 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:16 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:16 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:16 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:16 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:17 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:17 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:17 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:19 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:19 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. [snip] Oct 07 22:43:21 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:21 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. [snip] Oct 07 22:43:24 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:24 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:24 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:27 orodruin.lotr systemd[1]: dbus.service stopping timed out (2). Killing. Oct 07 22:43:27 orodruin.lotr systemd[1]: Unit dbus.service entered failed state. Oct 07 22:43:27 orodruin.lotr systemd[1]: Shutting down. Oct 07 22:43:27 orodruin.lotr systemctl[30129]: Failed to get D-Bus connection: Connection terminated during authentication. Oct 07 22:43:27 orodruin.lotr systemd-journal[282]: Journal stopped The first message at 22:42:41 should correspond to my first Ctrl-Alt-Del as the splash was not animated, so I pressed Esc to see the messages, the shutdown sequence was hanged and then I started to press Ctrl-Alt-Del repeatedly (with shorter and shorter interval) to force the shutdown. On a regular shutdown, I obtain: Oct 06 23:24:46 orodruin.lotr network[31080]: ..done wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 06 23:24:46 orodruin.lotr ifdown[31558]: wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 06 23:24:46 orodruin.lotr dhcpcd[31602]: wlan0: dhcpcd not running Oct 06 23:24:46 orodruin.lotr dhcpcd[31602]: wlan0: exiting Oct 06 23:24:48 orodruin.lotr network[31080]: ..doneShutting down service (localfs) network . . . . . . . . ...done Oct 06 23:24:49 orodruin.lotr systemd[1]: Shutting down. Oct 06 23:24:49 orodruin.lotr systemd-journal[276]: Journal stopped Oct 07 07:55:22 orodruin systemd-journal[282]: Journal started After asking in the opensuse-ml, I was told to enable the debug mode as explained in http://freedesktop.org/wiki/Software/systemd/Debugging#Diagnosing_Shutdown_P... In a following temporary hang, I obtained: Oct 31 23:02:23 orodruin.lotr network[6305]: ..done wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 31 23:02:23 orodruin.lotr ifdown[6783]: wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 31 23:02:24 orodruin.lotr dhcpcd[6827]: wlan0: dhcpcd not running Oct 31 23:02:24 orodruin.lotr dhcpcd[6827]: wlan0: exiting Oct 31 23:02:25 orodruin.lotr network[6305]: ..doneShutting down service (localfs) network . . . . . . . . ...done Oct 31 23:03:22 orodruin.lotr mtp-probe[7011]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-2" Oct 31 23:03:22 orodruin.lotr mtp-probe[7011]: bus: 4, device: 3 was not an MTP device Oct 31 23:03:50 orodruin.lotr umount[7031]: umount: /boot: target is busy. Oct 31 23:03:50 orodruin.lotr umount[7031]: (In some cases useful info about processes that use Oct 31 23:03:50 orodruin.lotr umount[7031]: the device is found by lsof(8) or fuser(1)) Oct 31 23:03:51 orodruin.lotr systemd-journal[283]: Journal stopped This temporary hang seems different from the previous one, but it is the only one that occurred after enabling the debug mode. The corresponding shutdown-log.txt is attached. Note that in my system I have a separated /boot ext2 partition; my system is fully updated from official repositories wrt. systemd and plymouth, as well as it was the kernel at the hang time (now I am using the latest from Kernel:stable and until now no hangs, but this does not imply an hang may not occur). I have decided to open this bug report since I received no answer from the ml after the second hang. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c
Jiaying ren
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c1
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c2
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c3
Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c4
--- Comment #4 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c5
--- Comment #5 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c6
--- Comment #6 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c7
--- Comment #7 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c8
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c9
--- Comment #9 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c10
--- Comment #10 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c11
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c12
--- Comment #12 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c13
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c14
Frederic Crozat
The problem is not that the system does not power-off, but the fact that randomly the shutdown process hangs for about 90 seconds and then continue. In the attached log, you see this at the two consecutive lines: [20794.187132] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [20882.444425] systemd[1]: dbus.service stopping timed out (2). Killing.
Then, a service is not shutting down (service stopping has 90s timeout). so, dbus.service or one of its services isn't shutting down properly. Another issue, when looking at the trace, is /boot being unmounted then remounted at shutdown, just when boot.cycle is being started.. Could you try to disable boot cycle initscript (systemctl disable cycle.service) to see if it improves shutdown. systemd in 13.1 will have improved support for this kind of shutdown lockup but I can't backport those fixes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c15
--- Comment #15 from Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c16
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c17
Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c18
--- Comment #18 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c19
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c20
Andrea Turrini
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c21
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c22
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c23
--- Comment #23 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c24
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=789698
https://bugzilla.novell.com/show_bug.cgi?id=789698#c25
--- Comment #25 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com