netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Vitaly Lifshits <vitaly.lifshits@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Cc: regressions@lists.linux.dev, stable@vger.kernel.org,
	Sasha Levin <sashal@kernel.org>
Subject: [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2
Date: Mon, 14 Apr 2025 14:18:25 +0200	[thread overview]
Message-ID: <Z_z9EjcKtwHCQcZR@mail-itl> (raw)

[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]

Hi,

After updating to 6.14.2, the ethernet adapter is almost unusable, I get
over 30% packet loss.
Bisect says it's this commit:

    commit 85f6414167da39e0da30bf370f1ecda5a58c6f7b
    Author: Vitaly Lifshits <vitaly.lifshits@intel.com>
    Date:   Thu Mar 13 16:05:56 2025 +0200

        e1000e: change k1 configuration on MTP and later platforms
        
        [ Upstream commit efaaf344bc2917cbfa5997633bc18a05d3aed27f ]
        
        Starting from Meteor Lake, the Kumeran interface between the integrated
        MAC and the I219 PHY works at a different frequency. This causes sporadic
        MDI errors when accessing the PHY, and in rare circumstances could lead
        to packet corruption.
        
        To overcome this, introduce minor changes to the Kumeran idle
        state (K1) parameters during device initialization. Hardware reset
        reverts this configuration, therefore it needs to be applied in a few
        places.
        
        Fixes: cc23f4f0b6b9 ("e1000e: Add support for Meteor Lake")
        Signed-off-by: Vitaly Lifshits <vitaly.lifshits@intel.com>
        Tested-by: Avigail Dahan <avigailx.dahan@intel.com>
        Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
        Signed-off-by: Sasha Levin <sashal@kernel.org>

     drivers/net/ethernet/intel/e1000e/defines.h |  3 ++
     drivers/net/ethernet/intel/e1000e/ich8lan.c | 80 +++++++++++++++++++++++++++--
     drivers/net/ethernet/intel/e1000e/ich8lan.h |  4 ++
     3 files changed, 82 insertions(+), 5 deletions(-)

My system is Novacustom V540TU laptop with Intel Core Ultra 5 125H. And
the e1000e driver is running in a Xen HVM (with PCI passthrough).
Interestingly, I have also another one with Intel Core Ultra 7 155H
where the issue does not happen. I don't see what is different about
network adapter there, they look identical on lspci (but there are
differences about other devices)...

I see the commit above was already backported to other stable branches
too...

#regzbot introduced: 85f6414167da39e0da30bf370f1ecda5a58c6f7b

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-04-14 12:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 12:18 Marek Marczykowski-Górecki [this message]
2025-04-14 12:38 ` [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2 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       ` [Intel-wired-lan] " Lifshits, Vitaly
2025-04-16 12:43         ` 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=Z_z9EjcKtwHCQcZR@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --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 NNTP newsgroup(s).