You are not logged in.
I have 2 ethernet devices on my machine. One is able to connect to my network. The other fails to connect. Drilling down revealed that the failing ethernet device is not even able to acquire arp addresses of other network nodes. Further, tcpdump on target machines reveals that the arping requests are not leaving the failing ethernet device. However, the local machine (with the failing device) shows arping/ping requests in tcpdump (and no replies). When (regular) ping is used the arp table gets populated with an "incomplete" entry (unlike with the good ethernet device). Also, this is on a dual-boot machine and the failing ethernet device works in Windows.
###################
kernel: 5.6.14.arch1-1
$ lspci -v
...
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05)
Subsystem: Dell Ethernet Connection I217-LM
Flags: bus master, fast devsel, latency 0, IRQ 39, NUMA node 0
Memory at f7100000 (32-bit, non-prefetchable) [size=128K]
Memory at f7139000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f020 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
...
$ lsmod | grep e1000
e1000e 299008 0
###########################
$ ip a show enp0s25
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d8:9e:f3:XXXXXXXX brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 scope global enp0s25
valid_lft forever preferred_lft forever
inet6 XXXXXXXXX scope link
valid_lft forever preferred_lft forever
#(some output anonymized)
###########################
$ ip r
default via 192.168.137.1 dev enp0s20u5
192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.100
192.168.137.0/24 dev enp0s20u5 proto kernel scope link src 192.168.137.53
# enp0s25 is the bad eth, and enp0s20u5 is the good one
# I have dhcp/gateway on the good device and I need the static route shown for the bad device
Not sure what other info would be useful. Thanks!
Last edited by Shmibble (2020-05-25 22:33:20)
Offline
More data...
$ ip -s l show enp0s25
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether d8:9e:f3:XXXXX brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
2102 29 0 0 0 0
Offline
Output from ethtool (enp0s25 broken device, enp0s20u5 working device)
$ ethtool enp0s20u5 ; ethtool enp0s25 ; diff <(ethtool enp0s20u5) <(ethtool enp0s25 )
Settings for enp0s20u5:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: Not reported
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Link partner advertised FEC modes: No
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: on
Port: MII
PHYAD: 16
Transceiver: internal
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
Settings for enp0s25:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
1,2c1,2
< Settings for enp0s20u5:
< Supported ports: [ TP MII ]
---
> Settings for enp0s25:
> Supported ports: [ TP ]
4a5
> 1000baseT/Full
9a11
> 1000baseT/Full
13,16d14
< Link partner advertised link modes: Not reported
< Link partner advertised pause frame use: No
< Link partner advertised auto-negotiation: No
< Link partner advertised FEC modes: No
20,21c18,19
< Port: MII
< PHYAD: 16
---
> Port: Twisted Pair
> PHYAD: 1
22a21
> MDI-X: on (auto)
Offline
$ dmesg |grep e1000
[ 19.355100] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 19.355101] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 19.355298] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 19.431930] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 19.498487] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) d8:9e:f3:XXXXXX
[ 19.498488] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 19.498526] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 19.871745] e1000e 0000:00:19.0 enp0s25: renamed from eth0
[ 125.893558] e1000e 0000:00:19.0 enp0s25: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 125.893561] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Offline
$ sudo lspci -vvv
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05)
Subsystem: Dell Ethernet Connection I217-LM
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 39
NUMA node: 0
Region 0: Memory at f7100000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f7139000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at f020 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00478 Data: 0000
Capabilities: [e0] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: e1000e
Kernel modules: e1000e
Offline
Seems to be the same issue as discussed here: https://bbs.archlinux.org/viewtopic.php?id=191981
i.e. rebooting after running Windows (without full power-down) leaves some state in the device that causes the malfunction. Full power down fixes the problem as does the reset command given at the end of the linked discussion.
Note that `ip l set down` must be run on the device before the reset command will work.
Last edited by Shmibble (2020-05-25 22:32:11)
Offline