Public bug reported: My StarFive VisionFive 2 board has two network interfaces of which I have only connected one to a switch. The systemd-networkd-wait- online.service always fails delaying boot by 150 s. The problem does not occur if both network interfaces are physically connected.
It does not make any sense to wait for the initialization of a network interface that is not physically connected. As described in https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net the physical link state can be determined via /sys/class/net/<iface>/carrier. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu6 Architecture: riscv64 CasperMD5json: { "result": "skip" } Date: Wed Dec 6 10:57:52 2023 InstallationDate: Installed on 2023-12-04 (2 days ago) InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204) Lspci-vt: -[0000:00]---00.0-[01]----00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller -[0001:00]---00.0-[01]----00.0 KIOXIA Corporation NVMe SSD Controller BG4 (DRAM-less) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug noble riscv64 ** Summary changed: - systemd-networkd-wait-online.service fails to complete + systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected -- 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/2045756 Title: systemd-networkd-wait-online.service fails to complete if one of the network interfaces is not physically connected Status in systemd package in Ubuntu: New Bug description: My StarFive VisionFive 2 board has two network interfaces of which I have only connected one to a switch. The systemd-networkd-wait- online.service always fails delaying boot by 150 s. The problem does not occur if both network interfaces are physically connected. It does not make any sense to wait for the initialization of a network interface that is not physically connected. As described in https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net the physical link state can be determined via /sys/class/net/<iface>/carrier. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3 Uname: Linux 6.5.0-9-generic riscv64 ApportVersion: 2.27.0-0ubuntu6 Architecture: riscv64 CasperMD5json: { "result": "skip" } Date: Wed Dec 6 10:57:52 2023 InstallationDate: Installed on 2023-12-04 (2 days ago) InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204) Lspci-vt: -[0000:00]---00.0-[01]----00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller -[0001:00]---00.0-[01]----00.0 KIOXIA Corporation NVMe SSD Controller BG4 (DRAM-less) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic root=UUID=2ee109fa-e475-473e-a8da-79f18ec0c1a3 ro SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp