systemd 245 broke dhcp on some devices.

[kad]

I upgraded my Odroid U3 to the latest state and after reboot noticed that eth0 wasn't able to properly configure by systemd-networkd.

$this->bbcode_second_pass_code('', '
Mar 28 22:04:59 u3 systemd-udevd[277]: Using default interface naming scheme 'v245'.
Mar 28 22:04:59 u3 systemd-udevd[277]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 28 22:05:00 u3 systemd-udevd[272]: Worker [277] terminated by signal 11 (SEGV)
Mar 28 22:05:00 u3 systemd-udevd[272]: eth0: Worker [277] failed
Mar 28 22:05:00 u3 systemd-networkd[286]: eth0: IPv6 successfully enabled
Mar 28 22:05:00 u3 systemd-networkd[286]: eth0: DHCP4 CLIENT: Failed to set IAID+DUID: Device or resource busy
Mar 28 22:05:00 u3 systemd-networkd[286]: eth0: Failed
Mar 28 22:05:00 u3 systemd-coredump[333]: Process 277 (systemd-udevd) of user 0 dumped core.

Stack trace of thread 277:
#0 0x00000000004b77c0 n/a (systemd-udevd + 0x2f7c0)
')

Quick search on the net found similar issue on main archlinux bugzilla which was closed with "we don't support ARM devices":
https://bugs.archlinux.org/task/65798

However it looks like the bug is not only for ARM devices, but in general for some subset of devices, as people observe similar crashes with bridge interfaces: https://github.com/systemd/systemd/issues/15078

Any opinions, what will be best way for now to prevent systems with automatic upgrades to become unbootable with archlinuxarm?
I was lucky to catch that on the device where I have serial console and can do something, but there are bunch of remote devices.
I reverted back to systemd v244, and adding systemd* to IgnorePkg in pacman.conf until upstream systemd will fix that?
Any better options for workarround?

[slydder]

Note that there are a lot of issues with systemd 245.
Example: https://github.com/systemd/systemd/issues/15225 which was also reproduced on archlinuxarm.

I also update my Odroid C1 remotely and because of the world wide restrictions happening I can not access it easily, so updating systemd is becoming a Russian roulette.