From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Camille Bordignon <camille.bordignon@easymile.com>
Cc: "Neftin, Sasha" <sasha.neftin@intel.com>,
Alexander Duyck <alexander.duyck@gmail.com>,
Netdev <netdev@vger.kernel.org>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] e1000e driver stuck at 10Mbps after reconnection
Date: Tue, 11 Sep 2018 17:31:47 +0900 [thread overview]
Message-ID: <20180911083147.GA31642@f2> (raw)
In-Reply-To: <20180907062851.GA7336@super_plancton>
On 2018/09/07 08:28, Camille Bordignon wrote:
> Le mercredi 08 août 2018 à 18:00:28 (+0300), Neftin, Sasha a écrit :
> > On 8/8/2018 17:24, Neftin, Sasha wrote:
> > > On 8/7/2018 09:42, Camille Bordignon wrote:
> > > > Le lundi 06 août 2018 à 15:45:29 (-0700), Alexander Duyck a écrit :
> > > > > On Mon, Aug 6, 2018 at 4:59 AM, Camille Bordignon
> > > > > <camille.bordignon@easymile.com> wrote:
> > > > > > Hello,
> > > > > >
> > > > > > Recently we experienced some issues with intel NIC (I219-LM
> > > > > > and I219-V).
> > > > > > It seems that after a wire reconnection, auto-negotation "fails" and
> > > > > > link speed drips to 10 Mbps.
> > > > > >
[...]
>
> I recently figured out that neither the previous patch nor commit
> 0b76aae741abb9d16d2c0e67f8b1e766576f897d fix this issue.
>
> In these cases, after reproducing the issue, when ethernet wire is connected
> kernel logs mention full speed (1000 Mbps) but actually it seems it is not.
> The problem persists.
>
Hmm, so the newer (post 4110e02eb45e) kernels are actually "better", in
that they accurately report that link speed is 10Mb/s.
In the end, do you know of a kernel version that doesn't exhibit the
problem of slower actual link speed?
I had a look at the code and I tried to reproduce the problem on the
hardware that I have (I217) but could not.
Also, out of curiosity, have you tried playing with the speed, autoneg
and advertise settings via ethtool -s to force the link to 1000Mb/s?
next prev parent reply other threads:[~2018-09-11 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 11:59 e1000e driver stuck at 10Mbps after reconnection Camille Bordignon
2018-08-06 22:45 ` Alexander Duyck
2018-08-07 6:42 ` Camille Bordignon
2018-08-08 14:24 ` [Intel-wired-lan] " Neftin, Sasha
2018-08-08 15:00 ` Neftin, Sasha
2018-08-14 9:14 ` Camille Bordignon
2018-09-07 6:28 ` Camille Bordignon
2018-09-11 8:31 ` Benjamin Poirier [this message]
2018-09-11 11:46 ` Camille Bordignon
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=20180911083147.GA31642@f2 \
--to=benjamin.poirier@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=camille.bordignon@easymile.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.neftin@intel.com \
/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).