DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc Sune <marcdevel@gmail.com>
To: dev@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: [dpdk-dev] e1000: randomly loosing link change events triggered by the peer
Date: Sat, 26 Mar 2016 02:42:44 +0100	[thread overview]
Message-ID: <CA+3n-Tp6hTfKOykpPjEUHzkBn9ta67QXu2UgowWqXzeCOzTtUg@mail.gmail.com> (raw)

I found that in the current HEAD in master testing it with an I218-LM in
autoneg mode, when link is forced to be renegociated by the peer (e.g. via
ethtool on a peer Linux box) _some_ change events are lost.

It is quite random, but it seems to happen more while changing the speed
than when changing the duplex mode.

However, when one or more link change events have been lost and the phy
medium is disconnected and reconnected, the link speed and duplex mode are
then correctly updated.

Marc

             reply	other threads:[~2016-03-26  1:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26  1:42 Marc Sune [this message]
2016-03-28  1:54 ` Lu, Wenzhuo
2016-03-28 11:02   ` Marc
2016-03-29  1:19     ` Lu, Wenzhuo
2016-03-30  8:04       ` Marc

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=CA+3n-Tp6hTfKOykpPjEUHzkBn9ta67QXu2UgowWqXzeCOzTtUg@mail.gmail.com \
    --to=marcdevel@gmail.com \
    --cc=dev@dpdk.org \
    --cc=wenzhuo.lu@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).