| Summary: | Systemd crashes after suspend | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Alexey Kharlamov <derlafff> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED NOTOURBUG | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | derlafff, pedrogfrancisco |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
coredump
dmesg log |
||
Created attachment 86299 [details]
dmesg log
Apparently it's a kernel bug. http://bugzilla.kernel.org/show_bug.cgi?id=61781 |
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 86298 [details] coredump How can I reproduce it: 1) Suspend to RAM 2) Repeat step 1 until systemd dies in suffer What I get then: $ systemctl status Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused I can reproduce it on the two different Acer Aspire One laptops. I've seen messages that's it BIOS bug (it probably reports that laptop is being closing even when it is being opening), but updating BIOS to the version where it should be fixed did not help. Moreover, suspending using 'systemctl suspend' also kills systemd I tried both Debian and Arch (systemd 204 and 207 accordingly). I even bootstraped clean Archlinux system without anything can make problems. Dmesg lines: [ 125.101904] PM: resume of devices complete after 2291.003 msecs [ 125.102600] PM: Finishing wakeup. [ 125.102604] Restarting tasks ... [ 125.102907] traps: systemd[1] general protection ip:b74f4390 sp:bfb03abc error:0 [ 125.102929] in libc-2.18.so[b74dd000+1a9000] There is systemd coredump and full dmesg in the attachments.