Just to collect all the info, can you please re-run with sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
I assume this is a missing kernel feature (systemd only officially supports kernels ≤ 2 years old), so we'd need some fallback. Can you please step through with gdb and figure out which call fails in particular? I don't immediately see where this comes from -- readlinkat() is only called in some wrapper functions in src/basic/fs- util.c and copy_tree_at, neither of which are being called by networkd. So I sugguest to build a debug version with CFLAGS="-g -O0" (from upstream or the Debian package) and gdb through networkd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel Status in systemd package in Ubuntu: Confirmed Bug description: Knowing that a 3.4 based kernel is unsupported we have to get it working for a specific customer. Systemd itself boots up nicely already but networkd fails to configure a network device with the following configuration file in /etc/systemd/network $ cat /etc/systemd/network/enp1s0.network [Match] Name=enp1s0 [Network] DNS=8.8.8.8 Address=192.168.178.30 Gateway=192.168.178.1 This gives the following error messages $ sudo /lib/systemd/systemd-networkd Enumeration completed enp1s0: Could not bring up interface: Invalid argument enp1s0: Could not set route: Invalid argument ifupdown or NetworkManager is reliable able to get the same interface up and configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
