From: Hisashi T Fujinaka <htodd@twofifty.com>
To: "Andreas K. Huettel" <andreas.huettel@ur.de>
Cc: Jakub Kicinski <kubakici@wp.pl>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [EXT] Re: [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521]
Date: Mon, 4 Oct 2021 17:21:31 -0700 (PDT) [thread overview]
Message-ID: <caf054b-c155-7614-5e97-e5ed34bf4eee@twofifty.com> (raw)
In-Reply-To: <1763660.QCnGb9OGeP@pinacolada>
On Tue, 5 Oct 2021, Andreas K. Huettel wrote:
>>>>
>>>> Any advice on how to proceed? Willing to test patches and provide
>>>> additional debug info.
>> Sorry to reply from a non-Intel account. I would suggest first
>> contacting Dell, and then contacting DeLock. This sounds like an
>> issue with motherboard firmware and most of what I can help with
>> would be with the driver. I think the issues are probably before
>> things get to the driver.
>
> Ouch. OK. Can you think of any temporary workaround?
>
> (Other than downgrading to 5.10 again, which I can't since it fails
> at the graphics (i915) modesetting...)
This is completely unofficial because I don't really work on client
systems, but I'd try different NICs, different slots, and the BIOS
settings.
You also might try support@intel.com because they're much more used to
client system support.
Todd Fujinaka todd.fujinaka@intel.com
WARNING: multiple messages have this Message-ID (diff)
From: Hisashi T Fujinaka <htodd@twofifty.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [EXT] Re: Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521]
Date: Mon, 4 Oct 2021 17:21:31 -0700 (PDT) [thread overview]
Message-ID: <caf054b-c155-7614-5e97-e5ed34bf4eee@twofifty.com> (raw)
In-Reply-To: <1763660.QCnGb9OGeP@pinacolada>
On Tue, 5 Oct 2021, Andreas K. Huettel wrote:
>>>>
>>>> Any advice on how to proceed? Willing to test patches and provide
>>>> additional debug info.
>> Sorry to reply from a non-Intel account. I would suggest first
>> contacting Dell, and then contacting DeLock. This sounds like an
>> issue with motherboard firmware and most of what I can help with
>> would be with the driver. I think the issues are probably before
>> things get to the driver.
>
> Ouch. OK. Can you think of any temporary workaround?
>
> (Other than downgrading to 5.10 again, which I can't since it fails
> at the graphics (i915) modesetting...)
This is completely unofficial because I don't really work on client
systems, but I'd try different NICs, different slots, and the BIOS
settings.
You also might try support at intel.com because they're much more used to
client system support.
Todd Fujinaka todd.fujinaka at intel.com
next prev parent reply other threads:[~2021-10-05 0:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 13:06 Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521] Andreas K. Huettel
2021-10-04 14:48 ` Jakub Kicinski
2021-10-04 14:48 ` [Intel-wired-lan] " Jakub Kicinski
2021-10-04 23:39 ` Hisashi T Fujinaka
2021-10-04 23:39 ` Hisashi T Fujinaka
2021-10-05 0:12 ` [EXT] " Andreas K. Huettel
2021-10-05 0:12 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-05 0:21 ` Hisashi T Fujinaka [this message]
2021-10-05 0:21 ` Hisashi T Fujinaka
2021-10-05 6:50 ` [Intel-wired-lan] " Sasha Neftin
2021-10-05 6:50 ` Sasha Neftin
2021-10-05 9:40 ` Paul Menzel
2021-10-05 9:40 ` Paul Menzel
2021-10-05 18:20 ` Hisashi T Fujinaka
2021-10-05 18:20 ` Hisashi T Fujinaka
2021-10-05 9:34 ` Paul Menzel
2021-10-05 9:34 ` Paul Menzel
2021-10-05 13:43 ` [EXT] " Andreas K. Huettel
2021-10-05 13:43 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-05 22:27 ` [EXT] Re: [Intel-wired-lan] " Jesse Brandeburg
2021-10-05 22:27 ` [Intel-wired-lan] [EXT] " Jesse Brandeburg
2021-10-12 16:34 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-12 16:34 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-12 17:42 ` [EXT] Re: [Intel-wired-lan] " Paul Menzel
2021-10-12 17:42 ` [Intel-wired-lan] [EXT] " Paul Menzel
2021-10-12 17:58 ` [EXT] Re: [Intel-wired-lan] " Rafael J. Wysocki
2021-10-12 17:58 ` [Intel-wired-lan] [EXT] " Rafael J. Wysocki
2021-10-12 19:28 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-12 19:28 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-14 12:09 ` [EXT] Re: [Intel-wired-lan] " Rafael J. Wysocki
2021-10-14 12:09 ` [Intel-wired-lan] [EXT] " Rafael J. Wysocki
2021-10-15 14:00 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-15 14:00 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-15 18:42 ` [EXT] Re: [Intel-wired-lan] " Rafael J. Wysocki
2021-10-15 18:42 ` [Intel-wired-lan] [EXT] " 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=caf054b-c155-7614-5e97-e5ed34bf4eee@twofifty.com \
--to=htodd@twofifty.com \
--cc=andreas.huettel@ur.de \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kubakici@wp.pl \
--cc=netdev@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.