All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Lifshits, Vitaly" <vitaly.lifshits@intel.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: Mon, 21 Apr 2025 15:19:12 +0200	[thread overview]
Message-ID: <aAZF0JUKCF0UvfF6@mail-itl> (raw)
In-Reply-To: <d37a7c9e-7b3f-afc2-b010-e9785f39a785@intel.com>

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

On Mon, Apr 21, 2025 at 03:44:02PM +0300, Lifshits, Vitaly wrote:
> 
> 
> On 4/16/2025 3:43 PM, Marek Marczykowski-Górecki wrote:
> > On Wed, Apr 16, 2025 at 03:09:39PM +0300, Lifshits, Vitaly wrote:
> > > Can you please also share the output of ethtool -i? I would like to know the
> > > NVM version that you have on your device.
> > 
> > driver: e1000e
> > version: 6.14.1+
> > firmware-version: 1.1-4
> > expansion-rom-version:
> > bus-info: 0000:00:1f.6
> > supports-statistics: yes
> > supports-test: yes
> > supports-eeprom-access: yes
> > supports-register-dump: yes
> > supports-priv-flags: yes
> > 
> 
> Your firmware version is not the latest, can you check with the board
> manufacturer if there is a BIOS update to your system?

I can check, but still, it's a regression in the Linux driver - old
kernel did work perfectly well on this hw. Maybe new driver tries to use
some feature that is missing (or broken) in the old firmware?

> Also, you mentioned that on another system this issue doesn't reproduce, do
> they have the same firmware version?

The other one has also 1.1-4 firmware. And I re-checked, e1000e from
6.14.2 works fine there.

-- 
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-21 13:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 12:18 [Intel-wired-lan] [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2 Marek Marczykowski-Górecki
2025-04-14 12:18 ` Marek Marczykowski-Górecki
2025-04-14 12:38 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-04-14 12:38   ` Lifshits, Vitaly
2025-04-14 12:58   ` [Intel-wired-lan] " Marek Marczykowski-Górecki
2025-04-14 12:58     ` Marek Marczykowski-Górecki
2025-04-14 13:04     ` [Intel-wired-lan] " Lifshits, Vitaly
2025-04-14 13:04       ` Lifshits, Vitaly
2025-04-14 13:28       ` [Intel-wired-lan] " Marek Marczykowski-Górecki
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 [this message]
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
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=aAZF0JUKCF0UvfF6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.