You are not logged in.

#1 2019-09-23 13:27:23

keibak
Member
Registered: 2017-05-24
Posts: 26

No more wired connections

Since yesterday wired connections stopped working. NetworkManager tries to activate the connection, but drops it immediatelly and tries to reconnect.

Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.7943] device (enp0s31f6): Activation: starting connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.7944] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.8838] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.8844] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.8856] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.8878] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.8880] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 23 15:22:56  NetworkManager[585]: <info>  [1569244976.8925] device (enp0s31f6): Activation: successful, device activated.
Sep 23 15:23:02  NetworkManager[585]: <info>  [1569244982.8858] device (enp0s31f6): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:02  NetworkManager[585]: <info>  [1569244982.9796] device (enp0s31f6): carrier: link connected
Sep 23 15:23:02  NetworkManager[585]: <info>  [1569244982.9798] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:02  NetworkManager[585]: <info>  [1569244982.9806] policy: auto-activating connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:02  NetworkManager[585]: <info>  [1569244982.9812] device (enp0s31f6): Activation: starting connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:02  NetworkManager[585]: <info>  [1569244982.9813] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:03  NetworkManager[585]: <info>  [1569244983.0705] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:03  NetworkManager[585]: <info>  [1569244983.0710] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:03  NetworkManager[585]: <info>  [1569244983.0722] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:03  NetworkManager[585]: <info>  [1569244983.0750] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:03  NetworkManager[585]: <info>  [1569244983.0752] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:03  NetworkManager[585]: <info>  [1569244983.0797] device (enp0s31f6): Activation: successful, device activated.
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.0724] device (enp0s31f6): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.1663] device (enp0s31f6): carrier: link connected
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.1664] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.1672] policy: auto-activating connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.1677] device (enp0s31f6): Activation: starting connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.1677] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.2589] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.2608] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.2656] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.2763] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.2772] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:09  NetworkManager[585]: <info>  [1569244989.2857] device (enp0s31f6): Activation: successful, device activated.
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.2621] device (enp0s31f6): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.3662] device (enp0s31f6): carrier: link connected
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.3664] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.3670] policy: auto-activating connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.3673] device (enp0s31f6): Activation: starting connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.3674] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.4561] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.4565] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.4577] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.4593] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.4595] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:15  NetworkManager[585]: <info>  [1569244995.4638] device (enp0s31f6): Activation: successful, device activated.
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.4578] device (enp0s31f6): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.5463] device (enp0s31f6): carrier: link connected
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.5464] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.5470] policy: auto-activating connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.5474] device (enp0s31f6): Activation: starting connection 'Fixed IP' (7a4d0899-0220-4ceb-b0cc-2bf89cef6d05)
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.5475] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.6375] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.6381] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.6398] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.6412] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.6414] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 23 15:23:21  NetworkManager[585]: <info>  [1569245001.6462] device (enp0s31f6): Activation: successful, device activated.

This only happens to LAN connections. WLAN works flawless.

Offline

#2 2019-09-23 13:50:50

seth
Member
Registered: 2012-09-03
Posts: 12,937

Re: No more wired connections

Seems there's a bug in NM (maybe the kernel), see https://bbs.archlinux.org/viewtopic.php … 7#p1864967
Didn't find any upstream issues for now, though.

Ethernet chip?

Offline

#3 2019-09-23 14:34:34

keibak
Member
Registered: 2017-05-24
Posts: 26

Re: No more wired connections

seth wrote:

Seems there's a bug in NM (maybe the kernel), see https://bbs.archlinux.org/viewtopic.php … 7#p1864967
Didn't find any upstream issues for now, though.

Ethernet chip?

LAN is done by some generic Intel HW:

Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V

My setup is similar to the one linked in the post above: UEFI, 2*Disks, one with Linux and Windows 10.

But I wouldn't suspect a Fastboot setting here as no changes were made in that context.

The issues appeared closely after the kernel update to version 5.3.
Unfortunatelly above logs is mostly all I've got. dmesg doesn't seem helpful here:

[  220.652452] audit: type=1130 audit(1569245026.269:204): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  220.664395] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  224.299857] audit: type=1111 audit(1569245029.917:205): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  224.309946] audit: type=1111 audit(1569245029.927:206): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.693009] audit: type=1111 audit(1569245031.306:207): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=device-disconnect interface="enp0s31f6" ifindex=3 pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.754498] audit: type=1111 audit(1569245031.369:208): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.771431] audit: type=1111 audit(1569245031.386:209): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.792322] audit: type=1111 audit(1569245031.406:210): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.815959] audit: type=1111 audit(1569245031.429:211): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.830784] audit: type=1111 audit(1569245031.446:212): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  226.410561] audit: type=1111 audit(1569245032.022:213): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  226.875001] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  226.875073] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[  231.004852] audit: type=1131 audit(1569245036.616:214): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  449.938556] audit: type=1111 audit(1569245255.523:215): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.355642] audit: type=1111 audit(1569245259.939:216): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=40a0afc2-c0b0-39af-9e6c-6fae41138cf8 name=44484350202845646F72617329 pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.458271] audit: type=1111 audit(1569245260.042:217): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.474055] audit: type=1111 audit(1569245260.059:218): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.489201] audit: type=1111 audit(1569245260.072:219): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.503383] audit: type=1111 audit(1569245260.086:220): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.523262] audit: type=1111 audit(1569245260.106:221): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  460.490720] audit: type=1111 audit(1569245266.075:222): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  460.501672] audit: type=1111 audit(1569245266.088:223): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  461.355336] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  461.355414] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready

Offline

#4 2019-09-23 14:38:06

ntldr
Member
Registered: 2017-01-04
Posts: 44

Re: No more wired connections

keibak wrote:
seth wrote:

Seems there's a bug in NM (maybe the kernel), see https://bbs.archlinux.org/viewtopic.php … 7#p1864967
Didn't find any upstream issues for now, though.

Ethernet chip?

LAN is done by some generic Intel HW:

Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V

My setup is similar to the one linked in the post above: UEFI, 2*Disks, one with Linux and Windows 10.

But I wouldn't suspect a Fastboot setting here as no changes were made in that context.

The issues appeared closely after the kernel update to version 5.3.
Unfortunatelly above logs is mostly all I've got. dmesg doesn't seem helpful here:

[  220.652452] audit: type=1130 audit(1569245026.269:204): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  220.664395] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  224.299857] audit: type=1111 audit(1569245029.917:205): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  224.309946] audit: type=1111 audit(1569245029.927:206): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.693009] audit: type=1111 audit(1569245031.306:207): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=device-disconnect interface="enp0s31f6" ifindex=3 pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.754498] audit: type=1111 audit(1569245031.369:208): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.771431] audit: type=1111 audit(1569245031.386:209): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.792322] audit: type=1111 audit(1569245031.406:210): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.815959] audit: type=1111 audit(1569245031.429:211): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  225.830784] audit: type=1111 audit(1569245031.446:212): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  226.410561] audit: type=1111 audit(1569245032.022:213): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  226.875001] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  226.875073] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[  231.004852] audit: type=1131 audit(1569245036.616:214): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  449.938556] audit: type=1111 audit(1569245255.523:215): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.355642] audit: type=1111 audit(1569245259.939:216): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=40a0afc2-c0b0-39af-9e6c-6fae41138cf8 name=44484350202845646F72617329 pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.458271] audit: type=1111 audit(1569245260.042:217): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.474055] audit: type=1111 audit(1569245260.059:218): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.489201] audit: type=1111 audit(1569245260.072:219): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.503383] audit: type=1111 audit(1569245260.086:220): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  454.523262] audit: type=1111 audit(1569245260.106:221): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  460.490720] audit: type=1111 audit(1569245266.075:222): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  460.501672] audit: type=1111 audit(1569245266.088:223): pid=585 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics arg="refresh-rate-ms" pid=874 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  461.355336] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  461.355414] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready

Hey there,

I'd also start to suspect that this issue is indeed 5.3 kernel I wouldn't be surprised given the fact that Wireguard ipv6 makes systems freeze on several people's PCs so..

Offline

#5 2019-09-23 14:41:13

seth
Member
Registered: 2012-09-03
Posts: 12,937

Re: No more wired connections

You're both using e1000e, so yes: try the lts kernel behavior.

Offline

#6 2019-09-23 14:58:09

ntldr
Member
Registered: 2017-01-04
Posts: 44

Re: No more wired connections

seth wrote:

You're both using e1000e, so yes: try the lts kernel behavior.

I installed LTS kernel and works 100% I get my connection now like I used to before 5.3 kernel. I also tried linux-zen to see if it's any different there but no same issues as normal linux kernel. Also wireguard works perfectly in LTS kernel like it used to before kernel 5.3.

Offline

#7 2019-09-23 14:59:48

keibak
Member
Registered: 2017-05-24
Posts: 26

Re: No more wired connections

ntldr wrote:
seth wrote:

You're both using e1000e, so yes: try the lts kernel behavior.

I installed LTS kernel and works 100% I get my connection now like I used to before 5.3 kernel. I also tried linux-zen to see if it's any different there but no same issues as normal linux kernel. Also wireguard works perfectly in LTS kernel like it used to before kernel 5.3.

Thanks for testing and sharing.

Offline

#8 2019-09-23 15:24:27

seth
Member
Registered: 2012-09-03
Posts: 12,937

Re: No more wired connections

https://git.kernel.org/pub/scm/linux/ke … 00e?h=v5.3
The last 6 commits are in 5.3 but not 5.2, I'd suggest to build the module and see whether any of the patches causes this behavior (the first one reverts a fix for cyclic resets what already sounds supicious enough)

Offline

#9 2019-09-23 15:27:52

ntldr
Member
Registered: 2017-01-04
Posts: 44

Re: No more wired connections

seth wrote:

https://git.kernel.org/pub/scm/linux/ke … 00e?h=v5.3
The last 6 commits are in 5.3 but not 5.2, I'd suggest to build the module and see whether any of the patches causes this behavior (the first one reverts a fix for cyclic resets what already sounds supicious enough)

are you suggesting that we should install

1 aur/e1000e-dkms 3.5.1-1 (+6 0.03%) 
    Intel e1000e Ethernet adapter driver (latest version from Intel) (DKMS version)

and see if it makes any difference?

Offline

#10 2019-09-23 15:37:58

seth
Member
Registered: 2012-09-03
Posts: 12,937

Re: No more wired connections

No, that's some older out-of-tree module.

https://wiki.archlinux.org/index.php/Co … nel_module
Use the current kernel sources and revert the linked patches (in reverse order)

Offline

#11 2019-09-24 17:03:47

bbrownkzo
Member
Registered: 2008-12-30
Posts: 8

Re: No more wired connections

Just wanted to add to this discussion.  I also noticed that I had no network connection after I had done a system update.  After reading this post and several others, and since I have an Intel motherboard that uses the Intel e1000e Ethernet adapter driver, I decided to downgrade the kernel and headers from linux-5.3.1 to linux-5.2.13.  After downgrading and rebooting my system was able to restore my internet connection.  Does anyone know if a bug report has been issued on this problem or not?

Offline

#12 2019-09-24 18:00:31

ntldr
Member
Registered: 2017-01-04
Posts: 44

Re: No more wired connections

bbrownkzo wrote:

Just wanted to add to this discussion.  I also noticed that I had no network connection after I had done a system update.  After reading this post and several others, and since I have an Intel motherboard that uses the Intel e1000e Ethernet adapter driver, I decided to downgrade the kernel and headers from linux-5.3.1 to linux-5.2.13.  After downgrading and rebooting my system was able to restore my internet connection.  Does anyone know if a bug report has been issued on this problem or not?

I decided to do the same but for those who want to use different kernel meantime LTS and CK kernels are uneffected. ZEN is effected as well I'm going to wait for new kernel release till then I won't update kernel.

Offline

#13 2019-09-24 18:03:54

bbrownkzo
Member
Registered: 2008-12-30
Posts: 8

Re: No more wired connections

Thanks for the reply.  I too will wait for the next kernel release to see if the problem has been resolved or not.

Offline

#14 2019-09-25 06:03:19

Miranda
Member
Registered: 2019-09-25
Posts: 1

Re: No more wired connections

Yup, both me and my partner are running e1000e drivers and have the same issue.

As a workaround (a bit of a silly one compared to rolling back), I've found that disabling the connection, disconnecting the interface, re-enabling the interface, and re-enabling the connection seems to work for me
This can be done with:

nmcli c d "<connection>"
nmcli d d "<device>"
nmcli d c "<device>"
nmcli c u "<connection>"

So, has anyone found a bug report for this on the bugzilla? I can't seem to find anything.


Edit: Welp, never mind. The above bash commands don't help, it was just happenstance. It's more just random at bootup, really.

Last edited by Miranda (2019-09-26 04:48:08)

Offline

#15 2019-09-25 09:32:49

keibak
Member
Registered: 2017-05-24
Posts: 26

Re: No more wired connections

Miranda wrote:

So, has anyone found a bug report for this on the bugzilla? I can't seem to find anything.

Sadly no, kernel's bugzilla hasn't mentioned e1000e in the current month very often.

Offline

#16 2019-09-26 10:26:26

the_angry_angel
Member
Registered: 2019-09-26
Posts: 1

Re: No more wired connections

FWIW this morning I started experiencing this issue. I've temporarily switched from NetworkManager to systemd-networkd and I'm having none of the symptoms. I've not had time to dig any further or try downgrading NM+kernels yet as I need to get on with some work this morning.. Incase it helps anyone or they have time before I circle back to digging into this.

Offline

#17 2019-09-26 16:20:19

bbrownkzo
Member
Registered: 2008-12-30
Posts: 8

Re: No more wired connections

I have been doing some testing with our problem.  It appears that if one stops the 'network'.service and then restarts the 'network'.service after the computer has been booted up that the wired connection will work.  At first I thought the problem was the network manager that I was using, netctl.  I replaced netctl with wicd thinking that might solve the problem.  However, the same results occurred with wicd.  Since I have only tested stopping and starting wicd.service, my next step will be to reinstalled netctl and try stopping and starting netctl.service.  I will post the results of that after testing.

Offline

#18 2019-09-26 16:20:22

hamelg
Member
From: France
Registered: 2008-06-19
Posts: 116

Re: No more wired connections

The same here.

Here, after upgrading the kernel the network device has been renamed :

5.2.14.arch2-1 : eth0
5.3.1.arch1-1 : enp24s0
My nic adapter :  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
driver : r8169

My network setup is managed by netctl scripts. I've had to rename my interface in the network profile file then execute a netctl reenable <my_eth0_profile>.

EDIT :
It's my fault.
I remember yesterday i have cleaned up the folder /etc/udev/rules.d. I have deleted the file 80-net-setup-link.rules, i was thinking it was useless. It explains the device renaming.
Please ignore my message.

Last edited by hamelg (2019-09-26 16:42:43)

Offline

#19 2019-09-27 18:19:50

bbrownkzo
Member
Registered: 2008-12-30
Posts: 8

Re: No more wired connections

This is a follow-up to my post from yesterday:

I uninstalled wicd and reinstalled netctl.  I was able to start netctl and the wired lan interface manually under kernel 5.2.13-1,  However when I upgraded to kernel 5.3.1-1 I could not get netctl to start or connect to the wired lan interface. After making sure that the network device name had not changed I decided to post the following error messages.

This is the message from the systemctl journal:

 systemctl status netctl@mynetwork.service
● netctl@mynetwork.service - Networking for netctl profile mynetwork
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-09-27 09:54:31 EDT; 42s ago
     Docs: man:netctl.profile(5)
  Process: 620 ExecStart=/usr/lib/netctl/network start mynetwork (code=exited, status=1/FAILURE)
 Main PID: 620 (code=exited, status=1/FAILURE)

Sep 27 09:54:26 Intel64 systemd[1]: Starting Networking for netctl profile mynetwork...
Sep 27 09:54:26 Intel64 network[620]: Starting network profile 'mynetwork'...
Sep 27 09:54:31 Intel64 network[620]: No connection found on interface '<device>' (timeout)
Sep 27 09:54:31 Intel64 network[620]: Failed to bring the network up for profile 'mynetwork'
Sep 27 09:54:31 Intel64 systemd[1]: netctl@mynetwork.service: Main process exited, code=exited, status=1/FAILURE
Sep 27 09:54:31 Intel64 systemd[1]: netctl@mynetwork.service: Failed with result 'exit-code'.
Sep 27 09:54:31 Intel64 systemd[1]: Failed to start Networking for netctl profile mynetwork.

This is the message from journactl:

A start job for unit system-netctl.slice has finished successfully.
-- 
-- The job identifier is 697.
Sep 27 09:54:26 Intel64 systemd[1]: Starting Networking for netctl profile mynetwork...
-- Subject: A start job for unit netctl@mynetwork.service has begun execution
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- A start job for unit netctl@mynetwork.service has begun execution.
-- 
-- The job identifier is 696.
Sep 27 09:54:26 Intel64 network[620]: Starting network profile 'mynetwork'...
Sep 27 09:54:31 Intel64 network[620]: No connection found on interface '<device>' (timeout)
Sep 27 09:54:31 Intel64 network[620]: Failed to bring the network up for profile 'mynetwork'
Sep 27 09:54:31 Intel64 systemd[1]: netctl@mynetwork.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- An ExecStart= process belonging to unit netctl@mynetwork.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Sep 27 09:54:31 Intel64 kernel: e1000e: <device> NIC Link is Down
Sep 27 09:54:31 Intel64 kernel: audit: type=1130 audit(1569592471.631:30): pid=1 uid=0 auid=4294967295 ses=4294967295 m>
Sep 27 09:54:31 Intel64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@mynetwork c>
Sep 27 09:54:31 Intel64 sudo[609]: pam_unix(sudo:session): session closed for user root
Sep 27 09:54:31 Intel64 systemd[1]: netctl@mynetwork.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- The unit netctl@mynetwork.service has entered the 'failed' state with result 'exit-code'.
Sep 27 09:54:31 Intel64 systemd[1]: Failed to start Networking for netctl profile mynetwork.
-- Subject: A start job for unit netctl@mynetwork.service has failed
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- A start job for unit netctl@mynetwork.service has finished with a failure.
-- 
-- The job identifier is 696 and the job result is failed.
Sep 27 09:54:31 Intel64 systemd[1]: Reached target Network.
-- Subject: A start job for unit network.target has finished successfully
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- A start job for unit network.target has finished successfully.
-- 

From the above error messages, the results that I received from testing with the wicd networking manager, and the results shown by Miranda

Miranda wrote:

I've found that disabling the connection, disconnecting the interface, re-enabling the interface, and re-enabling the connection seems to work for me
This can be done with:

nmcli c d "<connection>"
nmcli d d "<device>"
nmcli d c "<device>"
nmcli c u "<connection>"

The conclusion that I draw from the testing with wicd and that even trying to manually start netctl under kernel 5.3.1-1 that there is a conflict between netctl and kernel 5.3.1-1.

Any comments or suggestions would be appreciated.

Last edited by bbrownkzo (2019-09-29 11:59:10)

Offline

#20 2019-09-27 18:47:12

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,141
Website

Re: No more wired connections

Please edit your post to use code tags, not quote tags, for the terminal output.

https://wiki.archlinux.org/index.php/Co … s_and_code


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#21 2019-09-29 16:19:43

bbrownkzo
Member
Registered: 2008-12-30
Posts: 8

Re: No more wired connections

One last comment about our problem, I was able to find an old usb wireless network dongle in my stash of old parts and pieces.  After playing around with this for a while I must amend my above statement about netctl:

  netctl is NOT the problem.

By using my old wireless dongle I was able to start a connection to the internet through the wireless connection using netctl and kernel 5.3.1-1.  However, again, I was not able to start a connection to the internet using netctl and the Intel network controller.  Again, it would appear that there is a conflict between the driver e1000e and kernel 5.3.1-1.

Sorry for all the confusion from the above......

Offline

#22 2019-09-30 08:07:17

kadafax
Member
Registered: 2017-03-25
Posts: 4

Re: No more wired connections

Same problem here on a pretty popular simple Dell workstation (OptiPlex 5050):
5.2.14 = Ethernet connection OK
5.3.1 = No Ethernet connection

NIC:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V

Network is managed by netctl.
I have wireguard-dkms and tools installed.

Offline

#23 2019-09-30 08:55:41

Lazarus555
Member
Registered: 2013-07-22
Posts: 22

Re: No more wired connections

Same here:

NIC:
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)

Driver:
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k

Also using netctl.
LTS fixes the problem.

Offline

#24 2019-09-30 10:25:47

Lazarus555
Member
Registered: 2013-07-22
Posts: 22

Re: No more wired connections

I reported the bug to kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=205047

Offline

#25 2019-10-01 12:02:28

athos
Member
Registered: 2016-01-30
Posts: 7

Re: No more wired connections

Same here:5.3.1 is broken. Back to 5.2.14 where wired internet is working.

Offline

Board footer

Powered by FluxBB