Bug#728026: systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

2013-12-11 Thread Ben Hutchings
Control: tag -1 upstream fixed-upstream Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=61781 Control: notfound -1 linux/3.11 Control: notfound -1 linux/3.12 Control: found -1 3.11~rc4-1~exp1 On Sat, 2013-11-02 at 17:31 +0100, Michael Stapelberg wrote: > control: reassign -1 src:

Bug#728026: userspace apps using epoll_wait have their memory corrupted

2013-12-11 Thread Ben Hutchings
On Thu, 2013-12-12 at 02:40 +0100, Timur Bakeyev wrote: > I do believe, that: > > > Package: linux-image-3.11-0.bpo.2-amd64 > Source: linux > Version: 3.11.8-1~bpo70+1 > Installed-Size: 125379 > Maintainer: Debian Kernel Team > Architecture: amd64 > Provides: linux-modules-3.11-0.bpo.2-amd64 >

Bug#728026: userspace apps using epoll_wait have their memory corrupted

2013-12-11 Thread Timur Bakeyev
I do believe, that: Package: linux-image-3.11-0.bpo.2-amd64 Source: linux Version: 3.11.8-1~bpo70+1 Installed-Size: 125379 Maintainer: Debian Kernel Team Architecture: amd64 Provides: linux-modules-3.11-0.bpo.2-amd64 Is also affected by this bug. The visible effect for me was that after 'apt-get

Bug#728026: systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

2013-11-02 Thread Michael Stapelberg
control: reassign -1 src:linux linux/3.11 control: found -1 linux/3.12 control: retitle -1 userspace apps using epoll_wait have their memory corrupted control: noowner -1 Hi, Axel and I looked into this yesterday and realized that systemd segfaults (as visible in the “journalctl” output after rep

Bug#728026:

2013-11-02 Thread Mathieu LOUIS
Apparently this is a kernel issue caused by https://bugzilla.kernel.org/show_bug.cgi?id=61781 . Like mentioned in the bug report, rolling back to kernel 3.10 solved the issue for me.

Bug#728026: systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

2013-10-27 Thread Axel Beckert
Package: systemd Version: 204-3 Severity: grave Justification: no more able to shutdown system except by turning off power Dear Systemd Maintainers, first sorry for the late bug report. The following happened the first time on 13th of September 2013 (i.e. shortly after the 204-3 upload while bein