[arch-general] 5.10.5 - network card r8169 not activated on cold start?
David C. Rankin
drankinatty at gmail.com
Wed Jan 13 01:15:18 UTC 2021
Sorry for the lapse in posts, but when Arch changed list delivery to the
cloud service, my ISP bounced all mails from the new IP.
New issue, after an extended power-outage caused by a rare snow storm in
north-east Texas, I had to boot from cold start after the power being out for
2 days. On boot, the network device enp5s0 did not get started. Viewing the
logs, the r8169 device was never started. The cold boot log is:
Jan 12 07:51:38 valkyrie systemd: Timed out waiting for device
Jan 12 07:51:38 valkyrie systemd: Dependency failed for dhcpcd on enp5s0.
Jan 12 07:51:38 valkyrie systemd: dhcpcd at enp5s0.service: Job
dhcpcd at enp5s0.service/start failed with result 'dep
Jan 12 07:51:38 valkyrie systemd: sys-subsystem-net-devices-enp5s0.device:
device/start failed with result 'timeout'.
I have been using this same Arch server for 5-6 years now and I haven't ever
had an issue with the device not coming up. Granted for a majority of the last
5 years the box has only been rebooted, save an except for a drive
Since the device was not activated by the kernel, there was no chance of
using ip link to start the device.
Then on reboot, the device is found and configured without a problem:
Jan 12 08:38:16 valkyrie kernel: r8169 0000:05:00.0 enp5s0: renamed from eth0
Jan 12 08:38:19 valkyrie systemd: Starting dhcpcd on enp5s0...
Jan 12 08:38:20 valkyrie dhcpcd: enp5s0: waiting for carrier
Jan 12 08:38:20 valkyrie dhcpcd: enp5s0: carrier acquired
Jan 12 08:38:20 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jan 12 08:38:20 valkyrie dhcpcd: enp5s0: IAID 14:9e:33:19
<snip IPv6 chatter>
Jan 12 08:38:24 valkyrie dhcpcd: enp5s0: soliciting a DHCP lease
Jan 12 08:38:25 valkyrie dhcpcd: enp5s0: offered 192.168.6.135 from
Jan 12 08:38:25 valkyrie dhcpcd: enp5s0: probing address 192.168.6.135/24
Jan 12 08:38:30 valkyrie dhcpcd: enp5s0: leased 192.168.6.135 for 28800
Having never had this problem since the 2015-08-21 install on this box, my
question is "is anyone else seeing this, or anything similar, now?" I did not
have any issue with the other 4 Arch boxes I brought up after power returned,
so, as far as I have seen, this has been limited to the r8169 card.
David C. Rankin, J.D.,P.E.
More information about the arch-general