Intel Eth drops IP and deactivates randomly

Hi All,

having an issue with my ethernet connection, it will randomly disable its self and I can't get it to come back except doing a full reboot.

  • Tried the good old unplug and replug the cable
  • Restarted the NetworkManager service
  • Swapped up to kernel 5.5 from 5.4
  • Checked Bios config but no changes there. Mobo has an intel and a killer network port, I have the killer network port disabled via bios and only use the intel.
  • It comes back fine after every reboot, no one else having issues on my network. Router config hasn't changed. I did check it was up to date but nothing on that end.

I am also having issues pulling logs as I am not sure exactly where to look.
This is kinda what I am looking through.

[@rommi ~]$ inxi -in
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 04:d9:f5:60:f4:2c 
           IP v4: 192.168.72.100/24 type: dynamic noprefixroute scope: global 
           IP v6: fe80::d94c:598f:9000:8828/64 type: noprefixroute scope: link 

logs in journelctl that show it going down

Apr 05 17:59:08 rommi NetworkManager[3365819]: <info>  [1586073548.2926] device (enp4s0): driver 'igb' does not support carrier detection.
Apr 05 17:59:08 rommi NetworkManager[3365819]: <info>  [1586073548.2927] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 05 17:59:08 rommi NetworkManager[3365819]: <info>  [1586073548.2929] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Apr 05 17:59:08 rommi avahi-daemon[1018]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::d94c:598f:9000:8828.
Apr 05 17:59:08 rommi avahi-daemon[1018]: New relevant interface enp4s0.IPv6 for mDNS.
Apr 05 17:59:08 rommi avahi-daemon[1018]: Registering new address record for fe80::d94c:598f:9000:8828 on enp4s0.*.
Apr 05 17:59:08 rommi kdeconnectd[3606]: "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/ActiveConnection/8"
Apr 05 17:59:08 rommi kded5[3490]: "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/ActiveConnection/8"
Apr 05 17:59:08 rommi kded5[3490]: plasma-nm: Unhandled active connection state change:  1
Apr 05 17:59:53 rommi NetworkManager[3365819]: <warn>  [1586073593.2614] dhcp4 (enp4s0): request timed out
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2614] dhcp4 (enp4s0): state changed unknown -> timeout
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2614] device (enp4s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2616] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 05 17:59:53 rommi NetworkManager[3365819]: <warn>  [1586073593.2620] device (enp4s0): Activation: failed for connection 'Wired connection 1'
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2621] device (enp4s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 05 17:59:53 rommi avahi-daemon[1018]: Withdrawing address record for fe80::d94c:598f:9000:8828 on enp4s0.
Apr 05 17:59:53 rommi avahi-daemon[1018]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::d94c:598f:9000:8828.
Apr 05 17:59:53 rommi avahi-daemon[1018]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2877] dhcp4 (enp4s0): canceled DHCP transaction
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2877] dhcp4 (enp4s0): state changed timeout -> done
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2897] policy: auto-activating connection 'Wired connection 1' (bcc8518f-6a20-3848-ad82-1ea9495e437b)
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2901] device (enp4s0): Activation: starting connection 'Wired connection 1' (bcc8518f-6a20-3848-ad82-1ea9495e437b)
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2903] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2905] manager: NetworkManager state is now CONNECTING
Apr 05 17:59:53 rommi NetworkManager[3365819]: <warn>  [1586073593.2906] device (enp4s0): set-link: unable to retrieve link negotiation
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2906] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2908] device (enp4s0): driver 'igb' does not support carrier detection.
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2909] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 05 17:59:53 rommi NetworkManager[3365819]: <info>  [1586073593.2910] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Apr 05 17:59:53 rommi avahi-daemon[1018]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::d94c:598f:9000:8828.
Apr 05 17:59:53 rommi avahi-daemon[1018]: New relevant interface enp4s0.IPv6 for mDNS.
Apr 05 17:59:53 rommi avahi-daemon[1018]: Registering new address record for fe80::d94c:598f:9000:8828 on enp4s0.*.
Apr 05 17:59:53 rommi kded5[3490]: "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/ActiveConnection/9"
Apr 05 17:59:53 rommi kdeconnectd[3606]: "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/ActiveConnection/9"
Apr 05 17:59:53 rommi kded5[3490]: plasma-nm: Unhandled active connection state change:  1
Apr 05 18:00:12 rommi kwin_x11[3567]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 56899, resource id: 98566221, major code: 2 (ChangeWindowAttributes), minor code: 0
Apr 05 18:00:23 rommi audit[3365819]: USYS_CONFIG pid=3365819 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-update uuid=bcc8518f-6a20-3848-ad82-1ea9495e437b name=576972656420636>
Apr 05 18:00:23 rommi NetworkManager[3365819]: <info>  [1586073623.1003] audit: op="connection-update" uuid="bcc8518f-6a20-3848-ad82-1ea9495e437b" name="Wired connection 1" args="ipv4.ign>
Apr 05 18:00:23 rommi kded5[3490]: plasma-nm: virtual void SecretAgent::SaveSecrets(const NMVariantMapMap&, const QDBusObjectPath&)
Apr 05 18:00:23 rommi kernel: audit: type=1111 audit(1586073623.096:740): pid=3365819 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-update uuid=bcc8518f-6a20-3848-ad82-1ea9495e4>
Apr 05 18:00:23 rommi kded5[3490]: plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/1"
lines 1265-1290/1290 (END)

any advice or places to look for more detailed logging would be great thanks.

Full Hardware List if needed.
I am also fully up to date on stable

Hello,

Disable IPV6 and mac address randomization ... Reboot the system and test again.

1 Like

thanks i will give it a go.

Have you rebooted your router and tested an alternate cat6 or better cable.

I would suggest resetting your router to the factory defaults.

Also be sure to test kernel 5.6 and kernels 4.19, 4.14, and 4.9. Sometimes your adapter works better on older kernels. Even kernel 4.4 is worth testing as some people have to go back that far to get good connectivity with your adapter.

1 Like

have been looking at the router but it's all good. I updated its packages and had already swapped cat6 cables. I even tested a different termination point to see if that was the issue.
Plus router logs don't show the physical connection as dropping on that interface until the PC deactivates the interface on its end.

Having to go backward would be hard as I have a Ryzen 3xxx and Navi card, so have to stay above 5.3 if I want them to work. I will be keen to test 5.6 once it drops in stable.

I guess if it goes on after testing 5.6 I can always try and get the killer network port stable.

Have had the same issue since September 2019

[borche@borche-pc ~]$ inxi -in
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi 
           IF: wlo1 state: down mac: 92:63:da:60:f9:4e 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 
           IF: enp3s0f1 state: up speed: 100 Mbps duplex: half mac: 80:fa:5b:58:50:28 
           IP v4: 192.168.5.4/24 type: noprefixroute scope: global 
           IP v6: fe80::82fa:5bff:fe58:5028/64 scope: link 

have tried different hardware , kernels 4.14 to 5.5 (for some reason 5.6 does not download) , turning off ipv6 , using old timeshift backups, still the Ethernet randomly deactivates.

Before using the nuclear option and reinstalling everything running kubuntu of a live usb for a few hours see if the same issue happens to see it's a hardware or software issue

just an update it went down again ran this

[borche@borche-pc ~]$ journalctl | grep r8168
Apr 11 11:57:45 borche-pc kernel: r8168 Gigabit Ethernet driver 8.048.00-NAPI loaded
Apr 11 11:57:45 borche-pc kernel: r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
Apr 11 11:57:45 borche-pc kernel: r8168  Copyright (C) 2019  Realtek NIC software team <nicfae@realtek.com> 
Apr 11 11:57:46 borche-pc kernel: r8168 0000:03:00.1 enp3s0f1: renamed from eth0
Apr 11 11:57:50 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 11:57:51 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 11:57:52 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:08:37 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:08:39 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:08:52 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:08:54 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:11:31 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:11:33 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:11:35 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:11:36 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:11:47 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:11:49 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:12:03 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:12:05 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:12:08 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:12:10 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:31:09 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:31:11 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:31:23 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:31:25 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:31:35 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:31:37 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 12:31:42 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 12:31:45 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:01:56 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:01:58 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:04:49 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:04:51 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:05:07 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:05:09 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:09:16 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:09:18 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:09:43 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:09:45 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:10:26 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:10:28 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:10:39 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:10:45 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:10:50 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:10:52 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:11:01 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:11:03 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:11:07 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:11:08 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:11:10 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:11:12 borche-pc kernel: r8168: enp3s0f1: link up
Apr 11 13:12:04 borche-pc kernel: r8168: enp3s0f1: link down
Apr 11 13:12:07 borche-pc kernel: r8168: enp3s0f1: link up

so i am guessing it's something to do with the r8168 driver

You are using a totally different adapter than the OP. You should not highjack others threads with dissimilar issues. Your adapter has hundreds of posts on the forum about how to solve the reliability issues with the r6168 adapter. Your adapters speed is also set incorrectly.

How is that hijacking? Dissimilar? i think the r8186 randomly deactivating is similar.

And i have already tried the speed setting and that's not the problem still keeps on happening, have tried the auto and manual.

Did you even read the OP's outputs.

You have completely different network adapters.

For the OP, with an Intel adapter if you can not test an older kernel I would suggest testing a real time kernel. You may also want to test downgrading the linux-firmware package.

Have you tried setting a static IP address?

1 Like

I know they are different adapters.

On the laptop, server pc and the network printer they are all using static addresses only trying a dynamic address from the DHCP to test it out.

Tried setting static IP's but only after it goes down. Setting a static won't bring it back up, or if it does it doesn't show internet access. I will test static from the start.

I am currently testing on 5.6 and sadly similar issues.

Any idea's on how i can get some more focused logging around whats going on with it?

Run the command below to output a live log session of your current networking state:

journalctl -fu NetworkManager 

Let the command run in the terminal and log all current network activity.

Try reinitiating your network connection while the logging is taking place.

Log at least 50 lines of output around when you are trying to initiate a connection to your network.

Post important excerpts from the log pertaining to network events..

1 Like

thanks I will give it a try

1 Like

looks like no more issues since the last 2 updates to DHCP. so i am guessing that was the issue. Could also have been something in the kernel as well.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by