Error on starting bridge (bug?) about netctl HOT 7 CLOSED

From http://lists.freedesktop.org/archives/systemd-devel/2014-February/017362.html:

Oh, and one reminder that kinda got lost when we announced 209: you have
to enable CONFIG_FHANDLE in your kernel to use systemd >= 209
successfully, otherwise udev won't find any devices.

Are you using a kernel without CONFIG_FHANDLE? In that case, enabling that option should fix your problem.

from netctl.

I believe so :)

root@dewy# zgrep CONFIG_FHANDLE /proc/config.gz
CONFIG_FHANDLE=y

I'm using stock kernel 3.13.7-1-ARCH.

from netctl.

update; I've seem to have hit https://bugs.archlinux.org/task/35810 for my bridges aswell... can this be related?

from netctl.

Same problem here on tap-devices not created by netctl, but with fastd. How do I fix this happen?

Else the quoted bug https://bugs.archlinux.org/task/35810 is still happening on bridge-devices.

from netctl.

I can't replicate any of this. Please dig a bit deeper. Make sure no other programs are trying to configure the interface of your profile.

from netctl.

It's a completely new installed Server. Just added a bridge without any
device and try to enable it, after a reboot the device waits for itself.
Am 23.04.2014 15:00 schrieb "Jouke Witteveen" [email protected]:

I can't replicate any of this. Please dig a bit deeper. Make sure no other
programs are trying to configure the interface of your profile.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/86#issuecomment-41157441
.

from netctl.

I believe @RubenKelevra is seeing a different bug than the one in this report. His bug was #87 (which is now fixed). The bug of @jstam84 I cannot replicate.

from netctl.