From: Sasha Neftin <sasha.neftin@intel.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 09:50:47 +0300 [thread overview]
Message-ID: <4111f2b7-cbac-3451-593f-a154aca65263@intel.com> (raw)
In-Reply-To: <7064659e-fe97-f222-5176-844569fb5281@twofifty.com>
On 10/5/2021 02:39, Hisashi T Fujinaka wrote:
> On Mon, 4 Oct 2021, Jakub Kicinski wrote:
>
>> On Mon, 04 Oct 2021 15:06:31 +0200 Andreas K. Huettel wrote:
>>> Dear all,
>>>
>>> I hope this is the right place to ask, if not please advise me where
>>> to go.
>>
>> Adding intel-wired-lan at lists.osuosl.org and Sasha as well.
>>
>>> I have a new Dell machine with both an Intel on-board ethernet
>>> controller
>>> ([8086:15f9]) and an additional 2-port extension card ([8086:1521]).
>>>
>>> The second adaptor, a "DeLock PCIe 2xGBit", worked fine as far as I
>>> could
>>> see with Linux 5.10.59, but fails to initialize with Linux 5.14.9.
>>>
>>> dilfridge ~ # lspci -nn
>>> [...]
>>> 01:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit
>>> Network Connection [8086:1521] (rev ff)
>>> 01:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit
>>> Network Connection [8086:1521] (rev ff)
>>> [...]
>>>
>>> dilfridge ~ # dmesg|grep igb
>>> [??? 2.069286] igb: Intel(R) Gigabit Ethernet Network Driver
>>> [??? 2.069288] igb: Copyright (c) 2007-2014 Intel Corporation.
>>> [??? 2.069305] igb 0000:01:00.0: can't change power state from D3cold
>>> to D0 (config space inaccessible)
>>> [??? 2.069624] igb 0000:01:00.0 0000:01:00.0 (uninitialized): PCIe
>>> link lost
>>> [??? 2.386659] igb 0000:01:00.0: PHY reset is blocked due to SOL/IDER
>>> session.
>>> [??? 4.115500] igb 0000:01:00.0: The NVM Checksum Is Not Valid
>>> [??? 4.133807] igb: probe of 0000:01:00.0 failed with error -5
>>> [??? 4.133820] igb 0000:01:00.1: can't change power state from D3cold
>>> to D0 (config space inaccessible)
>>> [??? 4.134072] igb 0000:01:00.1 0000:01:00.1 (uninitialized): PCIe
>>> link lost
>>> [??? 4.451602] igb 0000:01:00.1: PHY reset is blocked due to SOL/IDER
>>> session.
>>> [??? 6.180123] igb 0000:01:00.1: The NVM Checksum Is Not Valid
>>> [??? 6.188631] igb: probe of 0000:01:00.1 failed with error -5
>>>
>>> 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.
>
Agree. The driver starts work when the PCIe link in L0. Please, check
with Dell/DeLock what is PCIe link status and enumeration process
finished as properly.(probably you will need PCIe sniffer)
> Todd Fujinaka <todd.fujinaka@intel.com>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Neftin <sasha.neftin@intel.com>
To: Hisashi T Fujinaka <htodd@twofifty.com>, Jakub Kicinski <kubakici@wp.pl>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
"Neftin, Sasha" <sasha.neftin@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521]
Date: Tue, 5 Oct 2021 09:50:47 +0300 [thread overview]
Message-ID: <4111f2b7-cbac-3451-593f-a154aca65263@intel.com> (raw)
In-Reply-To: <7064659e-fe97-f222-5176-844569fb5281@twofifty.com>
On 10/5/2021 02:39, Hisashi T Fujinaka wrote:
> On Mon, 4 Oct 2021, Jakub Kicinski wrote:
>
>> On Mon, 04 Oct 2021 15:06:31 +0200 Andreas K. Huettel wrote:
>>> Dear all,
>>>
>>> I hope this is the right place to ask, if not please advise me where
>>> to go.
>>
>> Adding intel-wired-lan@lists.osuosl.org and Sasha as well.
>>
>>> I have a new Dell machine with both an Intel on-board ethernet
>>> controller
>>> ([8086:15f9]) and an additional 2-port extension card ([8086:1521]).
>>>
>>> The second adaptor, a "DeLock PCIe 2xGBit", worked fine as far as I
>>> could
>>> see with Linux 5.10.59, but fails to initialize with Linux 5.14.9.
>>>
>>> dilfridge ~ # lspci -nn
>>> [...]
>>> 01:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit
>>> Network Connection [8086:1521] (rev ff)
>>> 01:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit
>>> Network Connection [8086:1521] (rev ff)
>>> [...]
>>>
>>> dilfridge ~ # dmesg|grep igb
>>> [ 2.069286] igb: Intel(R) Gigabit Ethernet Network Driver
>>> [ 2.069288] igb: Copyright (c) 2007-2014 Intel Corporation.
>>> [ 2.069305] igb 0000:01:00.0: can't change power state from D3cold
>>> to D0 (config space inaccessible)
>>> [ 2.069624] igb 0000:01:00.0 0000:01:00.0 (uninitialized): PCIe
>>> link lost
>>> [ 2.386659] igb 0000:01:00.0: PHY reset is blocked due to SOL/IDER
>>> session.
>>> [ 4.115500] igb 0000:01:00.0: The NVM Checksum Is Not Valid
>>> [ 4.133807] igb: probe of 0000:01:00.0 failed with error -5
>>> [ 4.133820] igb 0000:01:00.1: can't change power state from D3cold
>>> to D0 (config space inaccessible)
>>> [ 4.134072] igb 0000:01:00.1 0000:01:00.1 (uninitialized): PCIe
>>> link lost
>>> [ 4.451602] igb 0000:01:00.1: PHY reset is blocked due to SOL/IDER
>>> session.
>>> [ 6.180123] igb 0000:01:00.1: The NVM Checksum Is Not Valid
>>> [ 6.188631] igb: probe of 0000:01:00.1 failed with error -5
>>>
>>> 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.
>
Agree. The driver starts work when the PCIe link in L0. Please, check
with Dell/DeLock what is PCIe link status and enumeration process
finished as properly.(probably you will need PCIe sniffer)
> Todd Fujinaka <todd.fujinaka@intel.com>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2021-10-05 6:50 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 ` [Intel-wired-lan] " Jakub Kicinski
2021-10-04 14:48 ` Jakub Kicinski
2021-10-04 23:39 ` [Intel-wired-lan] " Hisashi T Fujinaka
2021-10-04 23:39 ` Hisashi T Fujinaka
2021-10-05 0:12 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-05 0:12 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-05 0:21 ` [Intel-wired-lan] [EXT] " Hisashi T Fujinaka
2021-10-05 0:21 ` [EXT] Re: [Intel-wired-lan] " Hisashi T Fujinaka
2021-10-05 6:50 ` Sasha Neftin [this message]
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 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-05 13:43 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-05 22:27 ` [Intel-wired-lan] [EXT] " Jesse Brandeburg
2021-10-05 22:27 ` [EXT] Re: [Intel-wired-lan] " Jesse Brandeburg
2021-10-12 16:34 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-12 16:34 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-12 17:42 ` [Intel-wired-lan] [EXT] " Paul Menzel
2021-10-12 17:42 ` [EXT] Re: [Intel-wired-lan] " Paul Menzel
2021-10-12 17:58 ` [Intel-wired-lan] [EXT] " Rafael J. Wysocki
2021-10-12 17:58 ` [EXT] Re: [Intel-wired-lan] " Rafael J. Wysocki
2021-10-12 19:28 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-12 19:28 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-14 12:09 ` [Intel-wired-lan] [EXT] " Rafael J. Wysocki
2021-10-14 12:09 ` [EXT] Re: [Intel-wired-lan] " Rafael J. Wysocki
2021-10-15 14:00 ` [Intel-wired-lan] [EXT] " Andreas K. Huettel
2021-10-15 14:00 ` [EXT] Re: [Intel-wired-lan] " Andreas K. Huettel
2021-10-15 18:42 ` [Intel-wired-lan] [EXT] " Rafael J. Wysocki
2021-10-15 18:42 ` [EXT] Re: [Intel-wired-lan] " 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=4111f2b7-cbac-3451-593f-a154aca65263@intel.com \
--to=sasha.neftin@intel.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 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.