Bug 75535 - systemd not able to reboot
Summary: systemd not able to reboot
Status: RESOLVED DUPLICATE of bug 33421
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: 2014-02-26 17:17 UTC by hp4everything
Modified: 2016-06-10 12:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
jpeg-photo with last screen contents before freeze (1.46 MB, image/jpeg)
2014-02-26 17:17 UTC, hp4everything
Details
once again with correct mime type (1.46 MB, image/jpeg)
2014-03-01 17:05 UTC, hp4everything
Details

Description hp4everything 2014-02-26 17:17:30 UTC
Created attachment 94776 [details]
jpeg-photo with last screen contents before freeze

I'm running a headless RaspnerryPi server with archlinuxarm using systemd. Sometimes the system freezes after starting a reboot. Attaching a display to zhe server indicates that systemd is not able to shutdown autofs (see attached screen photo with arrows pointing to an auto-mounted NAS-drive).

I waited for more than half an hour, nothing happend...there seem to be no supervision timers!

I think systemd should continue with reboot anyway and blame the misbehaving sw-components in the system-log.

Versions:
pacman -Q systemd
systemd 208-11 

cat /proc/sys/kernel/osrelease 
3.10.32-1-ARCH

pacman -Q autofs
autofs 5.0.8-2

BR
Hans-Peter
Comment 1 hp4everything 2014-03-01 17:05:10 UTC
Created attachment 94933 [details]
once again with correct mime type
Comment 2 hp4everything 2014-03-03 11:45:50 UTC
Is it possible that this problem is similar to the old Bug 33421, which still seems to be unresolved/status NEW?

Does this mean that circular dependencies might exist in service- and target- files of standard Linux-distributions and that systemd is not able to resolve these dependencies and perform its tasks anyway? If the administrator/user requests a reboot, systemd should respond to this request with internal strategies to resolve deadlocks or kill misbehaving components (because in many cases this is a reason to request a reboot).
Comment 3 Lennart Poettering 2016-06-10 12:59:34 UTC
I am pretty sure this is indeed a duplicate of bug 33421 (which has been fixed quite some time ago). Closing this one as duplicate hence.

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


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.