New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to bring up network bridge #15078
Comments
Please enable debugging logs for both udevd and networkd, and then provide the relevant logs again. By creating the following drop-in config, the debug logs are generated.
|
I have pretty much the same problem on a Raspberry Pi 3 Model B Rev 1.2 running Arch Linux ARM with systemd 245 (245.2-2-arch).
I replaced the contents of
so the network works and I can connect via ssh. Here are the logs with the above modifications and debugging enabled for udev and networkd after a reboot. Note that the time isn't set correctly when the system boots until systemd-timesyncd restores the time from a recorded timestamp but I can't be bothered to debug that right now. Output of journalctl -b -u systemd-networkd -u systemd-udevd-- Logs begin at Fri 2020-03-20 01:09:00 CET, end at Mon 2020-03-23 16:50:29 CET. -- |
Hello, I encountered exactly the same problem: after upgrading systemd from 244 to 245, the DHCP client of
Falling back to systemd 244 resolved that issue. Interestingly, whereas I encountered this issue on an Arch Linux Arm on Odroid XU4 powered by a kernel |
please provide the debug logs. |
I have provided my debug logs above. |
I figure this is something to do with udev code. Need to look further. |
Hmm... |
I'm having exact the same issue on a Rasperry Pi 1 with systemd 245 (also the 'new
Downgraded back to systemd 244 as a temp fix.. |
I tried to get the
So, I tried to rebuild
|
Here are the debug logs of
|
In my setup, I observe similar crash of systemd-udevd on ethernet interface.
Creating file /etc/systemd/network/90-ether.link with content removes the crash.
Same effect (no crash of systemd-udevd) is in case of commenting out or making empty line |
I finally managed to reproduce the
PR #15300 fixes this. |
The function sd_device_get_property_value has some paths where it exits without touching the n pointer. In those cases, n remained uninitialized until it was eventually read inside isempty where it caused the segmentation fault. Fixes #15078
The function sd_device_get_property_value has some paths where it exits without touching the n pointer. In those cases, n remained uninitialized until it was eventually read inside isempty where it caused the segmentation fault. Fixes systemd#15078 (cherry picked from commit 61fd7d6)
systemd version the issue has been seen with
Used distribution
Expected behaviour you didn't see
Unexpected behaviour you saw
Steps to reproduce the problem
Following configuration:
Relevant journal log:
The text was updated successfully, but these errors were encountered: