From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Linux Regressions <regressions@lists.linux.dev>,
lukas.probsthain@googlemail.com,
Linux Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
intel-wired-lan@lists.osuosl.org, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] Regression of e1000e (I219-LM) from 6.1.90 to 6.6.30
Date: Tue, 14 May 2024 11:34:32 +0700 [thread overview]
Message-ID: <56463a97-eb90-4884-b2f5-c165f6c3516a@gmail.com> (raw)
In-Reply-To: <b2897fda-08e8-40de-b78a-86e92bde41db@lunn.ch>
On 5/14/24 00:17, Andrew Lunn wrote:
> On Mon, May 13, 2024 at 03:42:50PM +0700, Bagas Sanjaya wrote:
>> Hi,
>>
>> <lukas.probsthain@googlemail.com> reported on Bugzilla
>> (https://bugzilla.kernel.org/show_bug.cgi?id=218826) regression on his Thinkpad
>> T480 with Intel I219-LM:
>>
>>> After updating from kernel version 6.1.90 to 6.6.30, the e1000e driver exhibits a regression on a Lenovo Thinkpad T480 with an Intel I219-LM Ethernet controller.
>
> Could you try a git bisect between these two kernel versions? You
> might be able to limit it to drivers/net/ethernet/intel/e1000e, which
> only had around 15 patches.
>
The BZ reporter (Cc'ed) says that bisection is in progress. You may
want to log in to BZ to reach him.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2024-05-14 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 8:42 [Intel-wired-lan] Regression of e1000e (I219-LM) from 6.1.90 to 6.6.30 Bagas Sanjaya
2024-05-13 17:17 ` Andrew Lunn
2024-05-14 4:34 ` Bagas Sanjaya [this message]
2024-05-14 9:48 ` Thorsten Leemhuis
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=56463a97-eb90-4884-b2f5-c165f6c3516a@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.probsthain@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).