From: Hisashi T Fujinaka <htodd@twofifty.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521]
Date: Tue, 5 Oct 2021 11:20:28 -0700 (PDT) [thread overview]
Message-ID: <3db85012-3e16-ca2d-5742-d9ecd45eba7e@twofifty.com> (raw)
In-Reply-To: <b56c4c30-d393-96fb-182c-726a60a39eed@molgen.mpg.de>
On Tue, 5 Oct 2021, Paul Menzel wrote:
> Linux has a no-regression policy, meaning when userspace/hardware with an
> older Linux kernel worked than it *has to* work with a new version too. So
> besides fixing the firmware/system, it?s as important to find the commit
> introducing the regression and fix it.
I think you're looking at the wrong driver. igb is fairly stable and we
haven't been poking at it much. Most of the changes have been from the
community. Sasha is commiting to igc, not igb.
In any case, we don't have the hardware (motherboard or NIC) and any
bisection will have to be done by the issue submitter.
Todd Fujinaka todd.fujinaka at intel.com
next prev parent reply other threads:[~2021-10-05 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1823864.tdWV9SEqCh@kailua>
2021-10-04 14:48 ` [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521] Jakub Kicinski
2021-10-04 23:39 ` Hisashi T Fujinaka
2021-10-05 0:12 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-05 0:21 ` Hisashi T Fujinaka
2021-10-05 6:50 ` [Intel-wired-lan] " Sasha Neftin
2021-10-05 9:40 ` Paul Menzel
2021-10-05 18:20 ` Hisashi T Fujinaka [this message]
2021-10-05 9:34 ` Paul Menzel
2021-10-05 13:43 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-05 22:27 ` Jesse Brandeburg
2021-10-12 16:34 ` Andreas K. Huettel
2021-10-12 17:42 ` Paul Menzel
2021-10-12 17:58 ` Rafael J. Wysocki
2021-10-12 19:28 ` Andreas K. Huettel
2021-10-14 12:09 ` Rafael J. Wysocki
2021-10-15 14:00 ` Andreas K. Huettel
2021-10-15 18:42 ` Rafael J. Wysocki
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=3db85012-3e16-ca2d-5742-d9ecd45eba7e@twofifty.com \
--to=htodd@twofifty.com \
--cc=intel-wired-lan@osuosl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox