http://bugzilla.opensuse.org/show_bug.cgi?id=918507 Thomas Röggla <tom@vertical-life.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tom@vertical-life.info --- Comment #1 from Thomas Röggla <tom@vertical-life.info> --- Hello, We also have a server running openSuSE, which since the mentioned update exhibits the same behaviour. All services run fine but terminated SSH sessions show up in the process list as zombie processes, also login in via SSH (or su and sudo) takes much longer than usual. Moreover, I cannot start/stop/reload services. These commands fail with the following error message: <code> Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused </code> Shutdown/reboot fails as well. I performed a hardware reset yesterday, which seemed to fix the issue for a while. The strange behaviour continued again 10-12 hours after the reboot. While digging through /var/log/messages I happened upon the following line: <code> 2015-02-19T12:56:40.155489+01:00 openSUSE-131-64-minimal kernel: [42374.242520] systemd[1]: segfault at 7f8d9e6519f8 ip 00007f8d9e6519f8 sp 00007fff4cee9868 error 15 in libc-2.18.so[7f8d9e651000+2000] 2015-02-19T12:56:40.739580+01:00 openSUSE-131-64-minimal systemd[1]: Caught <SEGV>, dumped core as pid 27762. 2015-02-19T12:56:40.780896+01:00 openSUSE-131-64-minimal systemd[1]: Freezing execution. </code> This seems to be the point the strange behaviour had started. As SEGFAULT in systemd? -- You are receiving this mail because: You are on the CC list for the bug.