Bug 70413 - abnormal delay during reboot and shutdown
Summary: abnormal delay during reboot and shutdown
Status: RESOLVED DUPLICATE of bug 70593
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-12 23:03 UTC by Barto
Modified: 2013-11-06 20:34 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
sigkill (88.77 KB, text/plain)
2013-10-12 23:03 UTC, Barto
Details

Description Barto 2013-10-12 23:03:01 UTC
Created attachment 87540 [details]
sigkill

since systemd-205 I notice an abnormal delay during shutdown and reboot, systemd-208 seems to have problems to shutdown some processes,

for example under an i686 installation of archlinux ( laptop pentium 4 2.4 Ghz, KDE 4.11 ) I notice that systemd waits 15 seconds when he tries to shutdown the process "kdesud" :

Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining procesess...
Sending SIGKILL to PID 1291 (kdesud)

with another installation of i686 archlinux under virtualbox it's now another process : VBoxClient :

Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining procesess...
Sending SIGKILL to PID 692(VBoxClient)

if I shutdown manually theses processes ( kdesud, VboxClient ) under KDE before the shutdown then systemd-208 can do his job without problems, no delays on shutdown,

so I think there is a problem, something is wrong in the source code,

sometimes a long delay is add to the "15 seconds" delay, systemd waits for something, after one or two minutes systemd continues the shutdown and I can see the "15 seconds delay" ( when the line "Sending SIGTERM to remaining processes" is showed )

there is no error message in log files,

some archlinux users report similar bugs :

https://bugs.archlinux.org/task/37288?project=1&order=dateopened&sort=desc
Comment 1 Arokux 2013-11-06 20:34:38 UTC

*** This bug has been marked as a duplicate of bug 70593 ***


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.