[systemd-bugs] [Bug 69663] New: Systemd crashes after suspend
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Sep 21 14:47:47 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=69663
Priority: medium
Bug ID: 69663
Assignee: systemd-bugs at lists.freedesktop.org
Summary: Systemd crashes after suspend
QA Contact: systemd-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: All
Reporter: derlafff at ya.ru
Hardware: Other
Status: NEW
Version: unspecified
Component: general
Product: systemd
Created attachment 86298
--> https://bugs.freedesktop.org/attachment.cgi?id=86298&action=edit
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130921/27884f70/attachment.html>
More information about the systemd-bugs
mailing list