On 6/28/25 1:24 PM, David C Rankin wrote:
On 6/28/25 12:09 PM, David C Rankin wrote:
The only other changes that look relevant and would be common
between LTS boot and 6.15.4 are the firmware and systemd (257.6-1 ->
257.7-1) updates. (this is my best educated guess). How would we
confirm this and then fix it?
Can I just downgrade systemd to test, or is that likely to break
things (https://wiki.archlinux.org/title/Downgrading_packages)?
The three packages I have in cache are:
systemd-257.6-1-x86_64.pkg.tar.zst
systemd-257.7-1-x86_64.pkg.tar.zst
systemd-libs-257.6-1-x86_64.pkg.tar.zst
systemd-libs-257.7-1-x86_64.pkg.tar.zst
systemd-sysvcompat-257.6-1-x86_64.pkg.tar.zst
systemd-sysvcompat-257.7-1-x86_64.pkg.tar.zst
If that won't hurt anything else, then we can at least rule-in/out
systemd. Seems like that should be okay, but I'd rather ask, than
compound the problem doing something that isn't advisable. If needed I
can use the package archive to downgrade back to the 25th.
It's not the systemd update. I downgraded and same result, e.g. the
interface is brought up and then brought back down by something?
# pacman -Q | grep systemd
systemd 257.6-1
systemd-libs 257.6-1
systemd-sysvcompat 257.6-1
The journal:
# journalctl -b --no-pager --full | grep enp5 | head -n50
**
******** boot
**
Jun 28 23:58:21 valkyrie systemd[1]: Expecting device
/sys/subsystem/net/devices/enp5s0...
Jun 28 23:58:27 valkyrie kernel: r8169 0000:05:00.0 enp5s0: renamed from
eth0
Jun 28 23:58:30 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jun 28 23:58:33 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Up -
1Gbps/Full - flow control rx/tx
Jun 28 23:58:33 valkyrie avahi-daemon[723]: Joining mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 28 23:58:33 valkyrie avahi-daemon[723]: New relevant interface
enp5s0.IPv4 for mDNS.
Jun 28 23:58:33 valkyrie avahi-daemon[723]: Registering new address
record for 192.168.6.14 on enp5s0.IPv4.
Jun 28 23:58:33 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jun 28 23:58:33 valkyrie avahi-daemon[723]: Interface enp5s0.IPv4 no
longer relevant for mDNS.
Jun 28 23:58:33 valkyrie avahi-daemon[723]: Leaving mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 28 23:58:33 valkyrie avahi-daemon[723]: Withdrawing address record
for 192.168.6.14 on enp5s0.
Jun 28 23:58:36 valkyrie named[812]: listening on IPv4 interface enp5s0,
192.168.6.14#53
**
******** manual activation
**
Jun 29 00:01:11 valkyrie avahi-daemon[723]: Joining mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 29 00:01:11 valkyrie avahi-daemon[723]: New relevant interface
enp5s0.IPv4 for mDNS.
Jun 29 00:01:11 valkyrie avahi-daemon[723]: Registering new address
record for 192.168.6.14 on enp5s0.IPv4.
Jun 29 00:01:12 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jun 29 00:01:14 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Up -
1Gbps/Full - flow control rx/tx
Jun 29 00:01:15 valkyrie avahi-daemon[723]: Joining mDNS multicast group
on interface enp5s0.IPv6 with address fe80::feaa:14ff:fe9e:3319.
Jun 29 00:01:15 valkyrie avahi-daemon[723]: New relevant interface
enp5s0.IPv6 for mDNS.
Jun 29 00:01:15 valkyrie avahi-daemon[723]: Registering new address
record for fe80::feaa:14ff:fe9e:3319 on enp5s0.*.
Again, manually bringing up the interface and restoring the default
route and starting dhcpd4 and all is fine. At least in my mind, that
pretty much leaves a problem created by the recent "churn" in the
firmware and some impact that has had at least on the Realtek r8169
binary parts.
Is it worth downgrading the firmware to check?
--
David C. Rankin, J.D.,P.E.
