[systemd-devel] systemctl suspend

Steve Abner pheonix.sja at att.net
Thu Nov 12 06:37:06 PST 2015

On 11/12/2015 07:56 AM, Lennart Poettering wrote:
> On Wed, 11.11.15 16:13, Steve Abner (pheonix.sja at att.net) wrote:
>> >I have an issue of the console not turning back on. I have a new build,
>> >linux 4.2, amd64, systemd, kdbus
>> >on a mac mini. The first try was hybrib-sleep, failed so tried suspend. From
>> >journalctl there seems to be
>> >no related errors, one:
>> >systemd-networkd[289]: wlan0: DHCPv4 address via
>> >
>> >systemd-network[289]: segfault at 6e00000063 ip 00007f913210409a sp
>> >00007fff38450b98 error 4 in libc-2.22.so[7f9132083000+19a000]
>> >  or with audit enabled
> networkd should never segfault, under no circumstances. Which version
> of systemd is this? Any chance you can get us a backtrace for this
> crash?
This happened on 227 and 224, but originally was using 224. I re-built 
system on first attempt to solve
monitor not switching on. As to backtrace, I am not sure how to help. I 
dont know how to intercept the
process. Please instruct this dummy (me) and I would love to provide 
> Bringing up hardware after returning from suspend is not systemd's
> job, that's a job the kernel is supposed to do on its own. Please ask
> the kernel guys for help.
Thankfully, Mantus's help provided me the direction I needed! Looked 
into ACPI a bit. Assumption was
that generic frame buffering, and kernel detection of devices still 
provided support for console power.
Appears I was mistaken! Configured in nouveau, and monitor now turns 
back on. But dang, that's a lot
of code :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20151112/1ed6bf3d/attachment.html>

More information about the systemd-devel mailing list