On Fri, 21 Feb 2014 10:24:39 +0100 Thomas Bächler <thomas@archlinux.org> wrote:

Am 20.02.2014 17:33, schrieb Dave Reisner:

...

Hi all,

I'm working on packaging the systemd 209 release, and I expect to have pkgrel=1 into [testing] in a few hours, barring any unforseen problems. It's a huge release (nearly 2000 commits since 208), and I don't anticipate that this will make it into [core].

This version works fine on my desktop, but fails on my laptop. The initramfs works fine. While booting up the system, systemd hangs and this appears in the journal:

systemd[1]: Assertion '(x->type == SOURCE_MONOTONIC && y->type == SOURCE_MONOTONIC) || (x->type == SOURCE_REALTIME && y->type == SOURCE_REALTIME)' failed at src/libsystemd/sd-event/sd-event.c:264, function latest_time_prioq_compare(). Aborting. systemd[1]: Caught <ABRT>, dumped core as pid 317.

As long this is turning into a thread about newly introduced issues in systemd... Udev 209 now tries to rename (I guess) all interfaces, including virtual: $ journalctl -u systemd-udevd.service PRIORITY=3 -o cat Could not apply link config to br0 Could not apply link config to vethQEP978 Could not apply link config to vethDR7OA5 Could not apply link config to vethW1QM0I Could not apply link config to vethC4240S Those are bridge and veth interfaces created by lxc userspace tools (2 containers/2 ifaces per container). Is this intended? Thanks, -- Leonid Isaev GPG key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D