Problems with Ethernet, Networking and Systemd

XpYunkr · 2025-03-12 08:20:58

I have the problem that on a system, where previously the ethernet connection worked,
I have a connection up but it doesn't allow me connection to the internet.

I am using networkmanager and tried to disable systemd-networkd.service and systemd-networkd.socket.
Sadly even after disabling they still start up every time. An additioal problem is, that every time I have any
interaction with systemctl the command takes several seconds so I suspect it is stuck somewhere.

Running dmesg -W before that shows mainly:

[ 3109.953055] systemd-fstab-generator[11187]: Mount point  is not a valid path, ignoring.
[ 3241.211625] wlp0s20f3: disconnect from AP 9c:8c:d8:f2:ec:81 for new auth to 9c:8c:d8:f2:ec:91
[ 3241.255324] wlp0s20f3: authenticate with 9c:8c:d8:f2:ec:91 (local address=40:ec:99:b9:ac:ad)
[ 3241.256235] wlp0s20f3: send auth to 9c:8c:d8:f2:ec:91 (try 1/3)
[ 3241.282960] wlp0s20f3: authenticated
[ 3241.284213] wlp0s20f3: associate with 9c:8c:d8:f2:ec:91 (try 1/3)
[ 3241.392255] wlp0s20f3: associate with 9c:8c:d8:f2:ec:91 (try 2/3)
[ 3241.496236] wlp0s20f3: associate with 9c:8c:d8:f2:ec:91 (try 3/3)
[ 3241.600331] wlp0s20f3: association with 9c:8c:d8:f2:ec:91 timed out
[ 3243.894683] wlp0s20f3: authenticate with 9c:8c:d8:f2:ec:81 (local address=40:ec:99:b9:ac:ad)
[ 3243.895746] wlp0s20f3: send auth to 9c:8c:d8:f2:ec:81 (try 1/3)
[ 3243.926816] wlp0s20f3: authenticated
[ 3243.928221] wlp0s20f3: associate with 9c:8c:d8:f2:ec:81 (try 1/3)
[ 3244.032206] wlp0s20f3: associate with 9c:8c:d8:f2:ec:81 (try 2/3)
[ 3244.037152] wlp0s20f3: RX AssocResp from 9c:8c:d8:f2:ec:81 (capab=0x1421 status=0 aid=2)
[ 3244.049162] wlp0s20f3: associated
[ 3244.191661] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by 9c:8c:d8:f2:ec:81

The first line hints towards some characters that are not allowed in fstab, I am just not sure how to remove the incorrect
ones but also guess that it is unrelated to the issue at hand.

Filtering the for Networkmanager https://pastebin.com/d0eT9bEM yields the following in journalctl.

Services running https://pastebin.com/uW3RLRKg.

And here filtering for systemd-networkd.service

Mar 12 08:43:16 dellxps sudo[11906]:   geegee : TTY=pts/0 ; PWD=/home/geegee ; USER=root ; COMMAND=/usr/bin/systemctl stop systemd-networkd.service
Mar 12 08:41:51 dellxps systemd[1]: systemd-networkd.socket: Failed to queue service startup job: Unit systemd-networkd.service is masked.
Mar 12 08:41:48 dellxps systemd[1]: systemd-networkd.service: Consumed 1.596s CPU time, 14.7M memory peak.
Mar 12 08:41:48 dellxps systemd[1]: systemd-networkd.service: Failed with result 'watchdog'.
Mar 12 08:41:48 dellxps systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT
Mar 12 08:41:47 dellxps systemd[1]: systemd-networkd.service: Killing process 1194 (systemd-network) with signal SIGABRT.
Mar 12 08:41:47 dellxps systemd[1]: systemd-networkd.service: Watchdog timeout (limit 3min)!
Mar 12 08:41:04 dellxps systemd[1]: systemd-networkd.service: Got notification message from PID 1194, but reception is disabled
Mar 12 08:41:00 dellxps systemd[1]: systemd-networkd.service: Got notification message from PID 1194, but reception is disabled
Mar 12 08:41:00 dellxps systemd[1]: systemd-networkd.service: Got notification message from PID 1194, but reception is disabled
Mar 12 08:39:30 dellxps sudo[11492]:   geegee : TTY=pts/0 ; PWD=/home/geegee ; USER=root ; COMMAND=/usr/bin/systemctl mask systemd-networkd.service
Mar 12 08:36:08 dellxps sudo[11123]:   geegee : TTY=pts/0 ; PWD=/home/geegee ; USER=root ; COMMAND=/usr/bin/systemctl disable systemd-networkd.service
Mar 12 08:29:45 dellxps sudo[10474]:   geegee : TTY=pts/0 ; PWD=/home/geegee ; USER=root ; COMMAND=/usr/bin/systemctl disable systemd-networkd.service

lspci -v -d ::0200

shows nothing but according to nmtui I am connected to the ethernet.

The output of ip link is:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 40:ec:99:b9:ac:ad brd ff:ff:ff:ff:ff:ff
    altname wlx40ec99b9acad
4: enp56s0u2u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 84:3a:5b:a4:e6:30 brd ff:ff:ff:ff:ff:ff
    altname enx843a5ba4e630

And here the output of ip a:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 40:ec:99:b9:ac:ad brd ff:ff:ff:ff:ff:ff
    altname wlx40ec99b9acad
    inet 10.104.96.229/18 brd 10.104.127.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 2911sec preferred_lft 2911sec
    inet6 2001:7c0:921:0:2f7:2538:721f:3855/64 scope global dynamic noprefixroute
       valid_lft 3599sec preferred_lft 3599sec
    inet6 fe80::15a7:439c:d6f9:d08d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: enp56s0u2u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 84:3a:5b:a4:e6:30 brd ff:ff:ff:ff:ff:ff
    altname enx843a5ba4e630
    inet6 fe80::9f7c:6a7d:b165:e6e6/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Any input highly appreciated! I am way out of my depth regarding networking.

Head_on_a_Stick · 2025-03-12 16:13:20

XpYunkr wrote:

lspci -v -d ::0200
shows nothing

Sometimes the cards misidentify themselves so broaden it out a bit:

lspci -knn -d ::02xx

Or just pipe the output to grep like a caveperson :-)

Your list of services is somewhat vague — wpa_supplicant is listed but it shouldn't be enabled if you're using NM so check that.

Can we see the output of

ls -lR /etc/systemd/system

That should also reveal more about this rogue systemd-networkd.service. Hopefully.

Finally, filtering the journal can miss important context so please provide a full sample, preferably from as brief a boot as possible. Thanks.

XpYunkr · 2025-03-13 08:13:15

Thanks a lot!

Here the output of sudo journalctl -b | curl -F 'file=@-' 0x0.st:
http://0x0.st/8SRX.txt

Then running lspci -knn -d ::02xx:

00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
	Subsystem: Rivet Networks Dual Band Wi-Fi 6(802.11ax) Killer AX1650s 160MHz 2x2 [Cyclone Peak] [1a56:1651]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

and finally ls -lR /etc/systemd/system:
http://0x0.st/8SRq.txt

And at last I tried to disable and stop the wpa_supplicant but that lead to a quick network
disconnect but nothing was changed thereafter.

Arch Linux

#1 2025-03-12 08:20:58

Problems with Ethernet, Networking and Systemd

#2 2025-03-12 16:13:20

Re: Problems with Ethernet, Networking and Systemd

#3 2025-03-13 08:13:15

Re: Problems with Ethernet, Networking and Systemd

Board footer