FS#45855 - [systemd] New install : networkd crash on boot after install avahi/nss-mdns

Attached to Project: Arch Linux
Opened by Benjamin Mollé (Delgon) - Friday, 31 July 2015, 14:49 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 04 August 2015, 06:31 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Florian Pritz (bluewind)
Evangelos Foutras (foutrelis)
Dave Reisner (falconindy)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Today (07/31/2015), I just installed Arch Linux on a new Raspberry.
I did a full update with pacman -Syu then I installed avahi and nss-mdns.
Since that moment, the raspberry doesn't get IP address on boot.

systemctl :
systemd-networkd.service loaded failed failed
systemd-networkd.socket loaded failed failed

journalctl :
Jul 31 14:06:33 observer-1 systemd[1]: Started Network Service.
Jul 31 14:06:33 observer-1 systemd-networkd[227]: eth0: DHCPv4 address 192.168.1.108/24 via 192.168.1.1
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Main process exited, code=killed, status=11/SEGV
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Unit entered failed state.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Failed with result 'signal'.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Jul 31 14:06:33 observer-1 systemd[1]: Stopped Network Service.
Jul 31 14:06:33 observer-1 systemd[1]: Starting Network Service...
Jul 31 14:06:33 observer-1 systemd-networkd[230]: Enumeration completed
Jul 31 14:06:33 observer-1 systemd[1]: Started Network Service.
Jul 31 14:06:33 observer-1 systemd-networkd[230]: eth0: DHCPv4 address 192.168.1.108/24 via 192.168.1.1
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Main process exited, code=killed, status=11/SEGV
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Unit entered failed state.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Failed with result 'signal'.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Jul 31 14:06:33 observer-1 systemd[1]: Stopped Network Service.
Jul 31 14:06:33 observer-1 systemd[1]: Starting Network Service...
Jul 31 14:06:33 observer-1 systemd-networkd[233]: Enumeration completed
Jul 31 14:06:33 observer-1 systemd[1]: Started Network Service.
Jul 31 14:06:33 observer-1 systemd-networkd[233]: eth0: DHCPv4 address 192.168.1.108/24 via 192.168.1.1
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Main process exited, code=killed, status=11/SEGV
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Unit entered failed state.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Failed with result 'signal'.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Jul 31 14:06:33 observer-1 systemd[1]: Stopped Network Service.
Jul 31 14:06:33 observer-1 systemd[1]: Starting Network Service...
Jul 31 14:06:33 observer-1 systemd-networkd[236]: Enumeration completed
Jul 31 14:06:33 observer-1 systemd[1]: Started Network Service.
Jul 31 14:06:33 observer-1 systemd-networkd[236]: eth0: DHCPv4 address 192.168.1.108/24 via 192.168.1.1
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Main process exited, code=killed, status=11/SEGV
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Unit entered failed state.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Failed with result 'signal'.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Jul 31 14:06:33 observer-1 systemd[1]: Stopped Network Service.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Jul 31 14:06:33 observer-1 systemd[1]: Failed to start Network Service.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Unit entered failed state.
Jul 31 14:06:33 observer-1 systemd[1]: systemd-networkd.service: Failed with result 'start-limit'.
Jul 31 14:06:34 observer-1 avahi-daemon[210]: Registering new address record for fe80::ba27:ebff:fe3c:363 on eth0.*.
Jul 31 14:06:34 observer-1 systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Jul 31 14:06:34 observer-1 systemd[1]: Failed to start Network Service.
Jul 31 14:06:34 observer-1 systemd[1]: systemd-networkd.socket: Unit entered failed state.
Jul 31 14:06:34 observer-1 systemd[1]: systemd-networkd.service: Failed with result 'start-limit'.


This problem appear the last week because I did the same installation on an other Raspberry Pi last Friday without system update and it still work.

Other fact :
- if I didn't upgrade the system after create the SD-card, it works too. But if I do pacman -Suy, the bug appear.
- if I put the SD-card on an other Rasp, it work on first boot, but after reboot, the bug comes back.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 04 August 2015, 06:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 224-1
Comment by Doug Newgard (Scimmia) - Saturday, 01 August 2015, 12:53 GMT
"Today (07/31/2015), I just installed Arch Linux on a new Raspberry."

No, you didn't. Arch Linux doesn't support the ARM architecures, so you installed a separate distro, Arch Linux ARM. Since I know there was someone else seeing this on x86, I'm going to leave this open, though.
Comment by Florian Pritz (bluewind) - Saturday, 01 August 2015, 13:00 GMT
This might have happened on ALARM, but I hit the same issue on my router. I'm currently bisecting, but that might take a while because my router is somewhat slow.

Backtrace:
#0 0xb7dfd426 in __strlen_sse2_bsf () from /usr/lib/libc.so.6
#1 0x80043088 in strempty () at ./src/basic/util.h:100
#2 message_append_basic (m=m@entry=0x800cf9c8, type=<optimized out>, p=0x9, stored=0x0) at src/libsystemd/sd-bus/bus-message.c:1567
#3 0x8004369e in sd_bus_message_append_basic (m=m@entry=0x800cf9c8, type=<optimized out>, p=<optimized out>) at src/libsystemd/sd-bus/bus-message.c:1655
#4 0x80043a92 in bus_message_append_ap (m=<optimized out>, types=0x80088867 "b", ap=0xbfffeda8 "") at src/libsystemd/sd-bus/bus-message.c:2444
#5 0x8003b8b7 in sd_bus_call_method_async.constprop.18 (bus=0x800be860, slot=0x0, destination=0x80088825 "org.freedesktop.hostname1", path=0x8008884b "/org/freedesktop/hostname1", interface=0x80088825 "org.freedesktop.hostname1", member=0x8008883f "SetHostname", callback=<optimized out>, userdata=0x800ca6a0, types=0x80088866 "sb", types=0x80088866 "sb", callback=<optimized out>, member=0x8008883f "SetHostname", interface=0x80088825 "org.freedesktop.hostname1", path=0x8008884b "/org/freedesktop/hostname1", destination=0x80088825 "org.freedesktop.hostname1", slot=0x0) at src/libsystemd/sd-bus/bus-convenience.c:89
#6 0x8005f45e in link_set_hostname (link=0x800ca6a0, hostname=0x9 <error: Cannot access memory at address 0x9>) at src/network/networkd-link.c:776
#7 0x8006caa1 in dhcp_lease_acquired (client=client@entry=0x800c20f0, link=link@entry=0x800ca6a0) at src/network/networkd-dhcp4.c:479
#8 0x8006cf59 in dhcp4_handler.lto_priv.348 (client=0x800c20f0, event=1, userdata=0x800ca6a0) at src/network/networkd-dhcp4.c:548
#9 0x8002e33e in client_notify () at src/libsystemd-network/sd-dhcp-client.c:358
#10 client_handle_message (client=client@entry=0x800c20f0, message=message@entry=0x800c0de4, len=len@entry=300) at src/libsystemd-network/sd-dhcp-client.c:1413
#11 0x8002ea7c in client_receive_message_raw (s=0x800cf510, fd=9, revents=1, userdata=0x800c20f0) at src/libsystemd-network/sd-dhcp-client.c:1610
#12 0x8006b2f0 in source_dispatch (s=s@entry=0x800cf510) at src/libsystemd/sd-event/sd-event.c:2124
#13 0x8006b646 in sd_event_dispatch (e=0x800bcc40) at src/libsystemd/sd-event/sd-event.c:2472
#14 sd_event_run (e=0x800bcc40, timeout=<optimized out>) at src/libsystemd/sd-event/sd-event.c:2500
#15 0x800686e5 in bus_event_loop_with_idle (name=0x80085de1 "org.freedesktop.network1", timeout=30000000, check_idle=0x80066bf0 <manager_check_idle>, userdata=0x800bcbf0, bus=0x800be860, e=0x800bcc40) at src/shared/bus-util.c:124
#16 manager_run (m=0x800bcbf0) at src/network/networkd-manager.c:538
#17 0x8000ce55 in main (argc=1, argv=0xbffff2a4) at src/network/networkd.c:116
Comment by Benjamin Mollé (Delgon) - Saturday, 01 August 2015, 13:01 GMT
Yes I installed a Arch Linux ARM, miss one word.
Comment by Florian Pritz (bluewind) - Saturday, 01 August 2015, 14:48 GMT
Bisect result:

a7d0ef446e5f28b37688743de22052abc8136a94 is the first bad commit
commit a7d0ef446e5f28b37688743de22052abc8136a94
Author: Susant Sahani <susant@redhat.com>
Date: Fri Jul 10 15:42:27 2015 +0530

networkd: DHCP override hostname

This patch enhances the DHCP client to send the hostname
reference
http://lists.freedesktop.org/archives/systemd-devel/2014-July/021550.html

Tested with
Example conf:

[Match]
Name=eth1

[Network]
DHCP=v4

[DHCP]
SendHostname=true
Hostname=test
Comment by Florian Pritz (bluewind) - Saturday, 01 August 2015, 14:57 GMT
https://github.com/systemd/systemd/issues/827
Comment by Evangelos Foutras (foutrelis) - Monday, 03 August 2015, 13:34 GMT
Should be fixed in systemd 224-1 (currently in [testing]).

Loading...