[systemd-devel] systemctl suspend

[Lennart Poettering]

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 192.168.1.82/24 via
> 192.168.1.254
> 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?


> audit[269]: ANOM_ABEND auid=4294967295 uid=76 gid=76 ses=4294967295
> subj=kernel pid=269 comm="systemd-network"
> exe="/lib/systemd/systemd-networkd"
> systemd-network[269]: segfault at 6e00000063 ip 00007f4d2bcb909a sp
> 00007ffedf852108 error 4 in libc-2.22.so[7f4d2bc38000+19a000]
> 
>  Once awaken from sleep, out journal to file, reboot. This regains console.
> Turning console monitor off/on
> has no effect. Also there is no dev/pts/ptmx as this is terminal only,
> working out bugs before adding
> display_manager. Maybe something in lunix config is not set to work with
> systemd suspend? I know of
> modules or builds not informing about dependencies, 4-5 days of builds to
> get wifi working because of it.

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.

Lennart

-- 
Lennart Poettering, Red Hat