Hi
ethtool using 5.4
ethtool enp1s0f1
Settings for enp1s0f1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
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: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
ethtool using 5.9
ethtool enp1s0f1
Settings for enp1s0f1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
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: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
ethtool in 5.9.3
ethtool enp1s0f1
Settings for enp1s0f1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
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: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
In 5.9 the downshift occurs right away when I turn the laptop on.
5.4 dmesg
https://pastebin.pl/view/3eb41a4b
5.9.3 dmesg
https://pastebin.pl/view/c07f6c22
---
Gilberto Nunes Ferreira
Em seg., 2 de nov. de 2020 às 05:14, Heiner Kallweit
<hkallwe...@gmail.com> escreveu:
>
> On 02.11.2020 04:36, Gilberto Nunes wrote:
> > Hi there
> >
> > I am in trouble when using newer kernels than 5.4.x regarding Realtek NIC
> > r8169
> >
> > Kernel 5.9.2-050902-lowlatency (from
> > https://kernel.ubuntu.com/~kernel-ppa/mainline/ and also compiled from
> > kernel.org)
> >
> > Generic FE-GE Realtek PHY r8169-101:00: Downshift occurred from
> > negotiated speed 1Gbps to actual speed 100Mbps, check cabling!
> > r8169 0000:01:00.1 enp1s0f1: Link is Up - 100Mbps/Full (downshifted) -
> > flow control rx/tx
> >
> > Kernel 5.4.73-050473-lowlatency (from
> > https://kernel.ubuntu.com/~kernel-ppa/mainline/)
> >
> > IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f1: link becomes ready
> > r8169 0000:01:00.1 enp1s0f1: Link is Up - 1Gbps/Full - flow control rx/tx
> >
> > Cable is ok! I double check it....
> >
> The downshift hint didn't exist yet in 5.4. Can you check what the actual
> link speed is under 5.4 (e.g. using iperf3).
>
> Under 5.9:
> Does the downshift happen directly when the link is initially established,
> or after some time?
>
> If link speed actually differs, then please:
> - provide full dmesg log
> - ideally do a git bisect to find the offending commit
> (as issue most likely is chip version / system dependent)
>
> >
> >
> >
> >
> > ---
> > Gilberto Nunes Ferreira
> >
>
