From: Sasha Neftin <sasha.neftin@intel.com>
To: Andrew Lunn <andrew@lunn.ch>, Ricky Wu <en-wei.wu@canonical.com>
Cc: <netdev@vger.kernel.org>, <rickywu0421@gmail.com>,
<linux-kernel@vger.kernel.org>, <edumazet@google.com>,
<intel-wired-lan@lists.osuosl.org>, <kuba@kernel.org>,
<anthony.l.nguyen@intel.com>, <pabeni@redhat.com>,
<davem@davemloft.net>, "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Lifshits, Vitaly" <vitaly.lifshits@intel.com>,
naamax.meir <naamax.meir@linux.intel.com>,
"Avivi, Amir" <amir.avivi@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v2 2/2] e1000e: fix link fluctuations problem
Date: Wed, 8 May 2024 08:05:29 +0300 [thread overview]
Message-ID: <514e990b-50c6-419b-96f2-09c3d04a2fda@intel.com> (raw)
In-Reply-To: <83a2c15e-12ef-4a33-a1f1-8801acb78724@lunn.ch>
On 07/05/2024 15:31, Andrew Lunn wrote:
> On Fri, May 03, 2024 at 06:18:36PM +0800, Ricky Wu wrote:
>> As described in https://bugzilla.kernel.org/show_bug.cgi?id=218642,
>> Intel I219-LM reports link up -> link down -> link up after hot-plugging
>> the Ethernet cable.
>
> Please could you quote some parts of 802.3 which state this is a
> problem. How is this breaking the standard.
>
> Andrew
In I219-* parts used LSI PHY. This PHY is compliant with the 802.3 IEEE
standard if I recall correctly. Auto-negotiation and link establishment
are processed following the IEEE standard and could vary from platform
to platform but are not violent to the IEEE standard.
En-Wei, My recommendation is not to accept these patches. If you think
there is a HW/PHY problem - open a ticket on Intel PAE.
Sasha
next prev parent reply other threads:[~2024-05-08 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 10:18 [PATCH v2 2/2] e1000e: fix link fluctuations problem Ricky Wu
2024-05-07 12:31 ` Andrew Lunn
2024-05-08 5:05 ` Sasha Neftin [this message]
2024-05-09 9:13 ` [Intel-wired-lan] " Ruinskiy, Dima
2024-05-09 13:46 ` Andrew Lunn
2024-05-09 17:40 ` En-Wei WU
2024-05-10 9:55 ` Sasha Neftin
2024-05-10 12:32 ` Andrew Lunn
2024-05-13 6:04 ` Sasha Neftin
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=514e990b-50c6-419b-96f2-09c3d04a2fda@intel.com \
--to=sasha.neftin@intel.com \
--cc=amir.avivi@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=en-wei.wu@canonical.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rickywu0421@gmail.com \
--cc=vitaly.lifshits@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 read-only IMAP folder(s) and NNTP newsgroup(s).