netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lifshits, Vitaly" <vitaly.lifshits@intel.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	<netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
	<regressions@lists.linux.dev>, <stable@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2
Date: Wed, 16 Apr 2025 15:09:39 +0300	[thread overview]
Message-ID: <b5d72f51-3cd0-aeca-60af-41a20ad59cd5@intel.com> (raw)
In-Reply-To: <50da66d0-fe66-0563-4d34-7bd2e25695a4@intel.com>



>> And also ethtool output if useful:
>> Settings for ens7:
>>     Supported ports: [ TP ]
>>     Supported link modes:   10baseT/Half 10baseT/Full
>>                             100baseT/Half 100baseT/Full
>>                             1000baseT/Full
>>     Supported pause frame use: Symmetric Receive-only
>>     Supports auto-negotiation: Yes
>>     Supported FEC modes: Not reported
>>     Advertised link modes:  10baseT/Half 10baseT/Full
>>                             100baseT/Half 100baseT/Full
>>                             1000baseT/Full
>>     Advertised pause frame use: Symmetric Receive-only
>>     Advertised auto-negotiation: Yes
>>     Advertised FEC modes: Not reported
>>     Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>                                          100baseT/Half 100baseT/Full
>>                                          1000baseT/Full
>>     Link partner advertised pause frame use: No
>>     Link partner advertised auto-negotiation: Yes
>>     Link partner advertised FEC modes: Not reported
>>     Speed: 1000Mb/s
>>     Duplex: Full
>>     Auto-negotiation: on
>>     Port: Twisted Pair
>>     PHYAD: 1
>>     Transceiver: internal
>>     MDI-X: on (auto)
>>     Supports Wake-on: d
>>     Wake-on: d
>>          Current message level: 0x00000007 (7)
>>                                 drv probe link
>>     Link detected: yes
>>
>>

Can you please also share the output of ethtool -i? I would like to know 
the NVM version that you have on your device.

  parent reply	other threads:[~2025-04-16 12:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 12:18 [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2 Marek Marczykowski-Górecki
2025-04-14 12:38 ` Lifshits, Vitaly
2025-04-14 12:58   ` Marek Marczykowski-Górecki
2025-04-14 13:04     ` Lifshits, Vitaly
2025-04-14 13:28       ` Marek Marczykowski-Górecki
2025-04-16 12:09       ` Lifshits, Vitaly [this message]
2025-04-16 12:43         ` [Intel-wired-lan] " Marek Marczykowski-Górecki
2025-04-21 12:44           ` Lifshits, Vitaly
2025-04-21 13:19             ` Marek Marczykowski-Górecki
2025-04-21 13:28               ` Marek Marczykowski-Górecki
2025-05-08  6:26                 ` Lifshits, Vitaly
2025-05-08 22:41                   ` Marek Marczykowski-Górecki
2025-05-08 23:13                     ` Paul Menzel
2025-05-08 23:28                       ` Marek Marczykowski-Górecki
2025-05-09  0:17                         ` Marek Marczykowski-Górecki
2025-06-18 13:28                           ` Marek Marczykowski-Górecki
2025-06-18 13:41                             ` Christian Heusel
2025-06-19 12:20                               ` Lifshits, Vitaly
2025-06-19 14:49                                 ` Marek Marczykowski-Górecki
2025-04-14 14:27     ` Marek Marczykowski-Górecki

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=b5d72f51-3cd0-aeca-60af-41a20ad59cd5@intel.com \
    --to=vitaly.lifshits@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@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).