You are not logged in.

#1 2020-12-28 19:29:54

Alm
Member
Registered: 2010-09-15
Posts: 64

Wired connection dropping repeatedly

Hello,

Since a few weeks, I've been experiencing issues with my wired connection.
It will drop randomly for a few seconds and then come back up, and that keeps happening on and on.

dmesg|egrep 'enp'
[    2.217968] alx 0000:03:00.0 enp3s0: renamed from eth0
[    5.535093] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[    5.535303] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[  187.014601] alx 0000:03:00.0 enp3s0: Link Down
[  190.498602] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  291.486612] alx 0000:03:00.0 enp3s0: Link Down
[  295.012464] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  317.576804] alx 0000:03:00.0 enp3s0: Link Down
[  321.042174] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  323.278425] alx 0000:03:00.0 enp3s0: Link Down
[  326.746961] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  366.544537] alx 0000:03:00.0 enp3s0: Link Down
[  370.108847] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  475.394566] alx 0000:03:00.0 enp3s0: Link Down
[  478.871948] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  498.516032] alx 0000:03:00.0 enp3s0: Link Down
[  502.017337] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
[  504.204474] alx 0000:03:00.0 enp3s0: Link Down
[  507.721856] alx 0000:03:00.0 enp3s0: NIC Up: 1 Gbps Full
...

Rebooting sometimes fixes the issue, but not systematically.
Also I've seen the speed cap drop to 100 Mbps instead of the full 1 Gbps; this happens randomly as well, but when it does it cannot be forced back to 1 Gbps.

Any ideas about how to proceed?
Thanks in advance.


See, you're unpacking.

Offline

#2 2020-12-28 21:15:23

seth
Member
Registered: 2012-09-03
Posts: 18,977

Re: Wired connection dropping repeatedly

Conflicting services? (#1 reason for this)

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Online

#3 2020-12-28 22:02:18

Alm
Member
Registered: 2010-09-15
Posts: 64

Re: Wired connection dropping repeatedly

Thank you seth, here's the output:

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
cronie.service                           | multi-user.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dhcpcd.service                           | multi-user.target.wants
dirmngr.socket                           | sockets.target.wants
docker.service                           | multi-user.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
httpd.service                            | multi-user.target.wants
mysqld.service                           | multi-user.target.wants
ntpd.service                             | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants

I don't see anything that would have been added recently though...


See, you're unpacking.

Offline

#4 2020-12-28 22:09:40

seth
Member
Registered: 2012-09-03
Posts: 18,977

Re: Wired connection dropping repeatedly

There's only dhcpcd, so you're good here.
Please post the complete system journal of a boot covering such incident to get us some context.

Also, rule #1: it's always the cable - check it's seating on both ends (eg. a broken latch can cause this)

Online

Board footer

Powered by FluxBB