netdev - Re: [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b56c4c30-d393-96fb-182c-726a60a39eed@molgen.mpg.de>
Date:   Tue, 5 Oct 2021 11:40:18 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Sasha Neftin <sasha.neftin@...el.com>
Cc:     netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
        Hisashi T Fujinaka <htodd@...fifty.com>,
        Jakub Kicinski <kubakici@...pl>,
        "Andreas K. Huettel" <andreas.huettel@...de>
Subject: Re: [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM
 Checksum Is Not Valid") [8086:1521]

Dear Sasha,


Am 05.10.21 um 08:50 schrieb Sasha Neftin:
> 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@...ts.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)

Of course, it’d be great to fix potential firmware bugs, but to suggest 
to a consumer to work with Dell to fix the problem is unfortunately not 
a realistic solution if Andreas does not own thousands of the 
problematic system.

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.


Kind regards,

Paul