‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 29 May 2018 5:12 PM, Alexander Duyck <alexander.du...@gmail.com> wrote:
> On Fri, May 25, 2018 at 11:33 AM, Michael Yartys > > michael.yar...@protonmail.com wrote: > > > I'm running OpenWrt on a NETGEAR R7800, and I'm trying to connect my laptop > > to one of the LAN ports. I've run the tests you suggested: > > > > [telia@lulz ~]$ uname -a > > > > Linux lulz 4.16.11-300.fc28.x86_64 #1 SMP Tue May 22 18:29:09 UTC 2018 > > x86_64 x86_64 x86_64 GNU/Linux > > > > [telia@lulz ~]$ dmesg | grep -e1000e > > > > [ 2.988320] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k > > > > [ 2.988322] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. > > > > [ 2.988559] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set > > to dynamic conservative mode > > > > [ 3.126959] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered > > PHC clock > > > > [ 3.247785] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) > > 5c:26:0a:4b:03:24 > > > > [ 3.247788] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection > > > > [ 3.247829] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 3041FF-0FF > > > > [ 3.249265] e1000e 0000:00:19.0 eno1: renamed from eth0 > > > > [ 121.168439] e1000e: eno1 NIC Link is Up 10 Mbps Full Duplex, Flow > > Control: Rx/Tx > > > > [ 121.168445] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO > > > > [ 316.483424] e1000e: eno1 NIC Link is Down > > Thanks for the info. > > > [telia@lulz ~]$ sudo ethtool eno1 > > > > Settings for eno1: > > > > 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: 10Mb/s > > > > Duplex: Full > > > > Port: Twisted Pair > > > > PHYAD: 2 > > > > Transceiver: internal > > > > Auto-negotiation: on > > > > MDI-X: off (auto) > > > > Supports Wake-on: pumbg > > > > Wake-on: g > > > > Current message level: 0x00000007 (7) > > > > drv probe link > > > > Link detected: yes > > > > [telia@lulz ~]$ sudo ethtool -S eno1 > > > > NIC statistics: > > > > rx_packets: 0 > > > > tx_packets: 90 > > > > rx_bytes: 0 > > > > tx_bytes: 14967 > > > > rx_broadcast: 0 > > > > tx_broadcast: 15 > > > > rx_multicast: 0 > > > > tx_multicast: 75 > > > > rx_errors: 0 > > > > tx_errors: 0 > > So it looks like it is not recognizing any packets as being received. > > I assume other devices don't have any issues when connected to the > > same port on the switch. If so we may be looking at a possible > > hardware issue as there should have been at least broadcast packets > > received when this connected to the switch. When connected at 10 full > > there should be some Rx packets seen. Hi First of all sorry for taking such a long time to get back to you. Yes, other devices connect just fine to the same port on the same switch. > > > I checked and my router is also seeing a 10/Full link. The web interface > > lists the port as: > > > > 10baseT > > > > full-duplex > > > > Michael > > Have you tried changing the advertise mode to eliminate the 10/full > > and 10/half options to see if that forces the link into a higher > > speed? You should be able to do that by running "ethtool -s eno1 > > advertise 0x2C". The part I am trying to figure out is if the lack of > > Rx is a side effect of the lower link speed or is the cause of the > > lower link speed. If we are able to renegotiate the link into either > > 100/Full or 1000/Full we could then determine if we still have Rx > > issues at those speeds. If we cannot get those speeds then I would > > suspect we are probably looking at something that may be wrong with > > the PHY that is causing the issues resulting in the lack of higher > > link speeds and problems receiving packets. > I tried "ethtool -s eno1 advertise 0x2C", but I could not get consistent results. After changing the advertise mode I immediately tried to unplug and plug the cable back in again. Unfortunately that did not work, but when I put my laptop into standby with the cable still plugged in it was able to get a connection when I turned it on again. I tried to reproduce this behaviour, but was unable to do so. I will keep testing to see if I can reproduce the scenario when it was able to connect. > Thanks. > > - Alex ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
