FS#66433 - [systemd] systemd-networkd dhcpd

Attached to Project: Arch Linux
Opened by guggi (guggo) - Monday, 27 April 2020, 05:54 GMT
Last edited by freswa (frederik) - Wednesday, 24 June 2020, 22:13 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

systemd-networkd fails to raise network on boot.

init --version
systemd 245 (245.5-2-arch)

systemctl -l status systemd-neworkd
DHCP4 CLIENT: Failed to attach event: Device or resource busy

restarting systemd-networkd solves the issue.
after downgrading systemd to 245.5-1-arch the interfaces gets an ip assigned by dhcp on boot


This task depends upon

Closed by  freswa (frederik)
Wednesday, 24 June 2020, 22:13 GMT
Reason for closing:  Fixed
Comment by Christian Hesse (eworm) - Monday, 27 April 2020, 09:18 GMT
Nothing changed regarding network between 245.5-1 and 245.5-2. Are you sure this was not what ever rare issue unrelated to the update?
Comment by guggi (guggo) - Monday, 27 April 2020, 10:10 GMT
yes, as i said downgrading solved the issue.
Comment by fdavid (fdavid) - Tuesday, 28 April 2020, 21:21 GMT
I exeperienced also issues with dhcpcd after updating to systemd 245.5-2. The dhcp connection dropped regularly after a couple of minutes. A downgrade to 245.5-1 solved the issue.
Comment by Christoph Fink (peippo) - Saturday, 16 May 2020, 10:04 GMT
Here the downgrade to systemd{,-libs,-sysvcompat}-245.5-1 seemed to help at first, but after a few reboots it started to fail again. Not sure whether it is connected to a systemd upgrade, at all, really.

The entire issue started after I replaced my system drive and decided to do a clean-slate install, so might be connected to (missing) libs or config left over by previous versions?

I’m only experiencing this bug on the wireless interface (managed by iwd), and restarting the systemd-networkd service always resolves the issue. Might be timing issues between iwd and systemd-networkd? No idea how to investigate timing issues, though.

Happy to investigate this bug further, if someone can point me into the right directions.

WiFi chip:
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
   journal-systemd-networkd-iwd (3 KiB)
Comment by Christoph Fink (peippo) - Friday, 22 May 2020, 07:33 GMT
The issue resolved for me (mysteriously).

I went multiple times through the list packages I upgraded/installed/removed since the last unsuccessful reboot (see attached file), but could not find anything that could possibly relate to the issue.
   changed-packages (9.4 KiB)
Comment by fdavid (fdavid) - Saturday, 20 June 2020, 09:25 GMT
As for peippo the issue has also been solved for me.
Comment by guggi (guggo) - Wednesday, 24 June 2020, 19:03 GMT
I solved by switching from dhcpcd to iwd.

Loading...