From: Heiner Kallweit <hkallweit1@gmail.com>
To: Gilberto Nunes <gilberto.nunes32@gmail.com>, netdev@vger.kernel.org
Subject: Re: Fwd: Problem with r8169 module
Date: Mon, 2 Nov 2020 09:14:06 +0100 [thread overview]
Message-ID: <c743770c-93a4-ad72-c883-faa0df4fa372@gmail.com> (raw)
In-Reply-To: <CAOKSTBuRw-H2VbADd6b0dw=cLBz+wwOCc7Bwz_pGve6_XHrqfw@mail.gmail.com>
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
>
next prev parent reply other threads:[~2020-11-02 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOKSTBtcsqFZTzvgF-HQGRmvcd=Qanq7r2PREB2qGmnSQZJ_-A@mail.gmail.com>
2020-11-02 3:36 ` Fwd: Problem with r8169 module Gilberto Nunes
2020-11-02 8:14 ` Heiner Kallweit [this message]
2020-11-02 13:20 ` Gilberto Nunes
2020-11-02 13:39 ` Heiner Kallweit
2020-11-02 16:29 ` Gilberto Nunes
2020-11-02 16:50 ` Heiner Kallweit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c743770c-93a4-ad72-c883-faa0df4fa372@gmail.com \
--to=hkallweit1@gmail.com \
--cc=gilberto.nunes32@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).