All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ismael Luceno <ismael@iodev.co.uk>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Intel e1000e driver bug on stable (6.9.x)
Date: Wed, 12 Jun 2024 22:33:19 +0200	[thread overview]
Message-ID: <ZmfcJsyCB6M3wr84@pirotess> (raw)

Hi,

I noticed that the NIC started to fail on a couple of notebooks [0]
[1] after upgrading to 6.9.1.

I tracked down the problem to commit 861e8086029e ("e1000e: move force
SMBUS from enable ulp function to avoid PHY loss issue", 2024-03-03),
included in all 6.9.x releases.

The fix is in commit bfd546a552e1 ("e1000e: move force SMBUS near
the end of enable_ulp function", 2024-05-28) from mainline.

The NIC fails right after boot on both systems I tried; I mention
because the description is a bit unclear about that on the fix, maybe
other systems are affected differently.

Best regards.


[0] HP ZBook 17 Gen 1 (D5D93AV) [8086:153a (rev 04)]
[1] Lenovo Thinkpad P15 Gen 1 [8086:0d4c]

             reply	other threads:[~2024-06-12 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 20:33 Ismael Luceno [this message]
2024-06-13  8:35 ` Intel e1000e driver bug on stable (6.9.x) Greg KH
2024-06-14  6:58   ` Linux regression tracking (Thorsten Leemhuis)
2024-06-14  9:10     ` Greg KH

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=ZmfcJsyCB6M3wr84@pirotess \
    --to=ismael@iodev.co.uk \
    --cc=linux-kernel@vger.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 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.