7767 2015-05-14 18:08:18 +0000 systemd shudown hang 2015-05-28 11:21:05 +0000 1 1 11 Runtime General Runtime General Runtime unspecified x86 Multiple VERIFIED WORKSFORME Medium normal 1.9 1 gonesailing gonesailing cristina-danielax.agurida randy.e.witt cristina-danielax.agurida --- --- No (bug/feature does not impact docs) oldest_to_newest 51022 0 gonesailing 2015-05-14 18:08:18 +0000 using systemctl shutdown the system hangs. After a bunch of tracing we have found that systemd is restarting the two services with watchdog timers after they have been initially stopped as part of shutting down. Eventually, systemd reports a dependency failure for one of these daemons and quits. At this point the systemd has shutdown enough of the system that we are unable to get in and force a reboot. Raising the watchdog timeout on the daemons to a large enough value is a allows the system to shutdown. But that value is way larger than we can tolerate one of these daemons being hung. The assumption is we have done something wrong in the our daemons but are not sure what. Is this a know problem have we done something wrong if so what are we not doing that we should be doing. 51028 1 randy.e.witt 2015-05-14 20:43:51 +0000 I tried running "systemctl poweroff" in qemu using core-image-sato on fido and it shut down successfully. That suggests it really is something to do with the configuration of your services or with systemd itself. Do you have an example of failure using a Yocto Project image without your services that fails to shutdown using "systemctl poweroff?" If you do, could you please provide more information on how to reproduce the issue? If not, I would suggest that you contact the systemd mailing list or IRC. http://lists.freedesktop.org/mailman/listinfo/systemd-devel #systemd on irc.freenode.org 51169 2 gonesailing 2015-05-20 14:58:25 +0000 We seem to have stumbled across a work around for the issue that does not involve getting rid of the watchdog timers or changing the timing. Forrest 51170 3 gonesailing 2015-05-20 15:02:23 +0000 We seem to have stumbled across a work around for the issue that does not involve getting rid of the watchdog timers or changing the timing. Forrest 51319 4 cristina-danielax.agurida 2015-05-28 11:21:05 +0000 Verified on master: 5170177719a93a69cc6c7c1218b3f26eed82d6e0 I followed the steps of reproducing the issue provided by Randy in his comment and running "systemctl poweroff" worked successfully. I used a core-image-sato image on qemux86. Based on Forrest last comment I changed the status in "verified worksforme" since from his initial comment I can't get more details. Cristina