Netdev List
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: dima.ruinskiy@intel.com, anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com
Cc: Javier Herrera <javier.herrera@afronta.com>,
	vitaly.lifshits@intel.com, netdev@vger.kernel.org,
	regressions@lists.linux.dev, intel-wired-lan@lists.osuosl.org
Subject: Re: [REGRESSION] e1000e: heavy packet loss on Lenovo ThinkPad P14s Gen 5 (I219-LM, Meteor Lake) after K1 re-enable; fixed by disable-k1
Date: Thu, 24 Sep 2026 09:34:16 +0200	[thread overview]
Message-ID: <4f37f217-fb94-4d4b-a2aa-9df8069c62bb@leemhuis.info> (raw)
In-Reply-To: <CAKRuCQLWEcci9hPgNUmvq44Bd2H30T5_vP=exMjsknXMN5Yh9A@mail.gmail.com>

On 9/15/26 10:57, Javier Herrera wrote:
> 
> Since commit 578294b8b60d ("e1000e: Reconfigure PLL clock gate timeout and
> re-enable K1 on Meteor Lake") the integrated I219-LM in a Lenovo ThinkPad
> P14s Gen 5 (Intel variant, Core Ultra 9 185H) shows constant packet loss
> and erratic latency on the wired link. Wi-Fi and a USB-C RTL8152 adapter on
> the same cable, switch and router are fine, so the network itself is not
> the problem.
> 
> Setting the private flag "disable-k1" fixes it immediately, so this looks
> like another system where the PLL clock gate reconfiguration is not enough
> and the DMI quirk table introduced by that commit should be extended.
> [...]

Dima or e1000e maintainers, could you please submit and upstream a quirk
entry to resolve this regression? Ideally with a stable tag? Javier
afaics provided everything needed for this. Reminder, Linus rule of
thumb wrt to regressions is "generally fix them within a week,
preferably before the next rc.":
https://www.kernel.org/doc/html/latest/process/handling-regressions.html#on-how-quickly-regressions-should-be-fixed

Or is there some reason why the quirk entry is a bad idea here?

Sending this as things looked stalled from here; or was there some
progress to resolve this already which I missed?

Ciao, Thorsten

  reply	other threads:[~2026-09-24  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  8:57 [REGRESSION] e1000e: heavy packet loss on Lenovo ThinkPad P14s Gen 5 (I219-LM, Meteor Lake) after K1 re-enable; fixed by disable-k1 Javier Herrera
2026-09-24  7:34 ` Thorsten Leemhuis [this message]
2026-09-25 17:32   ` Tony Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2026-10-05 18:52 ghrafn

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=4f37f217-fb94-4d4b-a2aa-9df8069c62bb@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=anthony.l.nguyen@intel.com \
    --cc=dima.ruinskiy@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=javier.herrera@afronta.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=regressions@lists.linux.dev \
    --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