Thanks for the input.

Michael, do you know if your problem exhibits itself similarly? Does a
reboot allow you to connect, and then you lose connectivity after
suspending/resuming the laptop? Also I would be curious if we are
seeing any messages in the dmesg log as I would interpret us reporting
a bad connection speed, and not being able to pass traffic, as mostly
likely an issue with the link between the MAC and PHY. One possible
cause for that could be us not being able to reestablish the link
between the two following a power management event.

Thanks.

- Alex

On Thu, May 24, 2018 at 4:13 PM, Andre Ruiz <andre.r...@gmail.com> wrote:
>
> And, at least in my case, it works fine after a reboot, same port, same
> switch, same cable. It's only after a sleep that it won't work anymore.
>
> Andre
>
>
> On Thu, May 24, 2018 at 6:32 PM, Michael Yartys via E1000-devel
> <e1000-devel@lists.sourceforge.net> wrote:
>>
>> I've tested several cables, including ones that work flawlessly with other
>> machines.
>>
>> Here's what I'm advertising:
>>
>> [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: 1
>>         Transceiver: internal
>>         Auto-negotiation: on
>>         MDI-X: on (auto)
>>         Supports Wake-on: pumbg
>>         Wake-on: g
>>         Current message level: 0x00000007 (7)
>>                                drv probe link
>>         Link detected: yes
>>
>>
>>
>> -----------------------------------------------------------------------------------------------------
>>
>> Router log shows a lot of DHCP spam:
>>
>> Thu May 24 23:21:04 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:04 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:05 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:05 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:14 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:14 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:24 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:24 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:38 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:38 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:46 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:46 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:47 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:47 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:50 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:50 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:56 2018 daemon.info dnsmasq-dhcp[2703]:
>> DHCPDISCOVER(br-lan) 192.168.1.112 5c:26:0a:4b:03:24
>> Thu May 24 23:21:56 2018 daemon.info dnsmasq-dhcp[2703]: DHCPOFFER(br-lan)
>> 192.168.1.112 5c:26:0a:4b:03:24
>>
>>
>> -----------------------------------------------------------------------------------------------------
>>
>> I also need to emphasise that I can't connect to the network through
>> ethernet. It's not only an issue of speed, since there's no connectivity.
>>
>>
>> Michael
>>
>>
>> ------------------------------------------------------------------------------
>> 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&#174; Ethernet, visit
>> http://communities.intel.com/community/wired
>
>

------------------------------------------------------------------------------
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&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to