Comment # 6 on bug 1119649 from Martti Laaksonen

(In reply to david chang from comment #5)
> I quick compare these results and found some interesting differences.
> 
> -kernel version: 4.18.15-1-default
> +kernel version: 4.19.7-1-default
> 
> -       Supported ports: [ TP MII ]
> +       Supported ports: [ TP AUI BNC MII FIBRE ]
> Supported ports type has been changed.
> 
> -       Advertised auto-negotiation: Yes
> +       Advertised auto-negotiation: No
> Did you disable auto-negotiation? If not, what happen if turned it on?

No, didn't touch network device configuration, I let NetworkManager handle it.
But since you mentioned it, I checked the network connection configuration and
auto-negotiation was disabled in there. Not sure why it would then show
auto-negotiation as enabled with 4.18 kernel, though. Basially the only
difference between system configurations was (or should have been) the kernel
version, nothing else was changed.

I enabled auto-negotiation in NetworkManager connection configuration and ran
the same test set again, but I did not observe any noticeable improvement in
receive speed. I will attach those results too.

> -     tx_errors: 0
> +     tx_errors: 11
> -     rx_missed: 0
> +     rx_missed: 63536
> There is a slightly increase on tx_errors but a dramatically increase on
> rx_missed. This is strange.

>From what I have observed, those tx_errors seem to come quite early, perhaps
when the link brought up or right after.

> Could you provide the output of following command? (For identifying the chip
> type of r8169.)
> $ sudo journalctl -k|grep r8169

Dec 19 18:41:40 darkangel kernel: libphy: r8169: probed
Dec 19 18:41:40 darkangel kernel: r8169 0000:01:00.0 eth0: RTL8168h/8111h,
ec:8e:b5:5a:2c:f5, XID 54100880, IRQ 128
Dec 19 18:41:40 darkangel kernel: r8169 0000:01:00.0 eth0: jumbo features
[frames: 9200 bytes, tx checksumming: ko]
Dec 19 18:41:40 darkangel kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0
Dec 19 18:41:44 darkangel kernel: Generic PHY r8169-100:00: attached PHY driver
[Generic PHY] (mii_bus:phy_addr=r8169-100:00, irq=IGNORE)
Dec 19 18:41:44 darkangel kernel: r8169 0000:01:00.0 enp1s0: Link is Down
Dec 19 18:41:47 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Full - flow control off
Dec 19 18:41:47 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Down
Dec 19 18:41:50 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Full - flow control off
Dec 19 18:46:38 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Down
Dec 19 18:46:42 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Full - flow control off
Dec 19 18:47:21 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Down
Dec 19 18:47:38 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Full - flow control off
Dec 19 18:47:38 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Down
Dec 19 18:47:41 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Full - flow control off
Dec 19 18:48:55 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Down
Dec 19 18:49:14 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Down
Dec 19 18:49:17 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Half - flow control off
Dec 19 18:49:17 darkangel.localnet kernel: r8169 0000:01:00.0 enp1s0: Link is
Up - 1Gbps/Full - flow control off


Here's the kernel command line, in case that has any significance:
BOOT_IMAGE=/boot/vmlinuz-4.19.7-1-default
root=UUID=d92fac4d-cc81-4af7-a706-e7dade059609 resume=/dev/sda3 splash=silent
quiet showopts pci=noaer

That pci=noaer is for the Wi-Fi interface, otherwise kernel logs are flooded
with AER messages.