| Summary: | systemd not able to reboot | ||
|---|---|---|---|
| Product: | systemd | Reporter: | hp4everything |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED DUPLICATE | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
jpeg-photo with last screen contents before freeze
once again with correct mime type |
||
Created attachment 94933 [details]
once again with correct mime type
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). |
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.
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