Arch Linux ARM v7 kernel/bootcode update on Raspberry Pi 3 is breaking Networking.
I have 7 Pi's (5 Pi 3's, 2 originals), running arch 24/7. The last kernel/boot code update stopped
the networking starting on 2 of the 5 v3's.
In all cases, installed latest updates (pacman -Syu)
and then rebooted after kernel updates had installed. I was logged on to all machines remotely via ssh (they are all headless).
On the 2 machines in question the networking lights didn't come on to indicate a link. Tried powering off/on, still no joy.
I found I had to power on with network cable UNPLUGGED and then plug it in later. This allowed network to start and remote login via ssh.
Both Pi's are plugged into different Netgear gigabit routers.
I had the same issue around 8th July when there were 3 systemd updates in 1 day, but there may also have been kernel/bootcode updates as well. In that case one of the same Pi's was affected, and a different one also (but all PI 3's).
After the network starts up successfully further reboots seem to be ok, I've rebooted ok many times since 8th July, until today.
The machines aren't running out of storage as I purge the old packages regularly etc. I've been running these machines 24/7
since they were released (about a year or so), and the networking issues have only occurred twice, both in the last month. All are configured identically.
uname -a
Linux alarmpi 4.9.38-1-ARCH #1 SMP Sat Jul 22 02:48:38 UTC 2017 armv7l GNU/Linux
tail /proc/cpuinfo
processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : BCM2835
Revision : a02082
Serial : Redacted
I'm running sshd (obviously) with an override.conf file (so it starts even if network is slow to start, why is this not the default!!!)
[Unit]
After=ntpd.service
[Service]
Restart=always
RestartSec=5
ntpd is also running with an override.conf: (to ensure time syncs early from local ntpd server)
[Unit]
After=network.target
[Service]
ExecStartPre=/usr/bin/ntpd -gq
I probably can't reproduce this now I've got them running again, but given its happened to 4 machines on 2 occasions, it needs noting.
Regards
Andrew