[systemd-bugs] [Bug 89442] New: systemd-networkd: version 219 can't bring up any network device if there exists CANbus devices

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89442

            Bug ID: 89442
           Summary: systemd-networkd: version 219 can't bring up any
                    network device if there exists CANbus devices
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: mads at ab3.no
        QA Contact: systemd-bugs at lists.freedesktop.org

Created attachment 114025
  --> https://bugs.freedesktop.org/attachment.cgi?id=114025&action=edit
dmesg when booting with systemd.log_level=debug systemd.log_target=kmsg
log_buf_len=1M

I have an Atom NM10-based industrial PC with three e1000e devices and a PEAK
CANbus device (PCI ID 001c:0008) providing the interface can0. After updating
from 216 to 219, systemd-networkd is unable to get my e1000e-devices up and
running. I don't have any configuration for can0 within /etc/systemd/network.

Two files in /etc/systemd/network, 10-eth0.network and 10-eth1.network. System
booted with net.ifnames=0. No service is configured to do something with can0
or eth2.

# cat /etc/systemd/network/10-eth*
[Match]
Name=eth0

[Network]
Address=10.20.0.3/24
Gateway=10.20.0.1

[Match]
Name=eth1

[Network]
Address=10.30.0.3/24
Gateway=10.30.0.1

After booting, eth0 and eth1 are not configured nor upped. After `systemctl
restart systemd-networkd´, eth0 and eth1 are configured, but not upped. can0 is
not upped either.

systemd-networkd.afterboot.txt is systemd-networkd journal (with loglevel
debug) after boot, and systemd-networkd.afterrestartservice.txt is the journal
for `systemctl restart systemd-networkd´.

dmesg.txt is dmesg when booting with systemd.log_level=debug
systemd.log_target=kmsg log_buf_len=1M

The system doesn't have ipv6 enabled, so that triggers some error messages.


# systemctl --version
systemd 219
+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP -LIBCRYPTSETUP
-GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150305/bc7d1972/attachment.html>