From: Andreas K. Huettel <andreas.huettel@ur.de>
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: Tue, 05 Oct 2021 15:43:08 +0200 [thread overview]
Message-ID: <2944777.ktpJ11cQ8Q@pinacolada> (raw)
In-Reply-To: <35dfc9e8-431c-362d-450e-4c6ac1e55434@molgen.mpg.de>
>
> What messages are new compared to the working Linux 5.10.59?
>
I've uploaded the full boot logs to https://dev.gentoo.org/~dilfridge/igb/
(both in a version with and without timestamps, for easy diff).
* I can't see anything that immediately points to the igb device (like a PCI id etc.) before the module is loaded.
* The main difference between the logs is many unrelated (?) i915 warnings in 5.10.59 because of the nonfunctional graphics.
The messages easily identifiable are:
huettel at pinacolada ~/tmp $ cat kernel-messages-5.10.59.txt |grep igb
Oct 5 15:11:18 dilfridge kernel: [ 2.090675] igb: Intel(R) Gigabit Ethernet Network Driver
Oct 5 15:11:18 dilfridge kernel: [ 2.090676] igb: Copyright (c) 2007-2014 Intel Corporation.
Oct 5 15:11:18 dilfridge kernel: [ 2.090728] igb 0000:01:00.0: enabling device (0000 -> 0002)
Oct 5 15:11:18 dilfridge kernel: [ 2.094438] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.097287] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.098492] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.098787] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.173386] igb 0000:01:00.0: added PHC on eth0
Oct 5 15:11:18 dilfridge kernel: [ 2.173391] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
Oct 5 15:11:18 dilfridge kernel: [ 2.173395] igb 0000:01:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 6c:b3:11:23:d4:4c
Oct 5 15:11:18 dilfridge kernel: [ 2.173991] igb 0000:01:00.0: eth0: PBA No: H47819-001
Oct 5 15:11:18 dilfridge kernel: [ 2.173994] igb 0000:01:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Oct 5 15:11:18 dilfridge kernel: [ 2.174199] igb 0000:01:00.1: enabling device (0000 -> 0002)
Oct 5 15:11:18 dilfridge kernel: [ 2.261029] igb 0000:01:00.1: added PHC on eth1
Oct 5 15:11:18 dilfridge kernel: [ 2.261034] igb 0000:01:00.1: Intel(R) Gigabit Ethernet Network Connection
Oct 5 15:11:18 dilfridge kernel: [ 2.261038] igb 0000:01:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 6c:b3:11:23:d4:4d
Oct 5 15:11:18 dilfridge kernel: [ 2.261772] igb 0000:01:00.1: eth1: PBA No: H47819-001
Oct 5 15:11:18 dilfridge kernel: [ 2.261776] igb 0000:01:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Oct 5 15:11:18 dilfridge kernel: [ 2.265376] igb 0000:01:00.1 enp1s0f1: renamed from eth1
Oct 5 15:11:18 dilfridge kernel: [ 2.282514] igb 0000:01:00.0 enp1s0f0: renamed from eth0
Oct 5 15:11:31 dilfridge kernel: [ 17.585202] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
huettel at pinacolada ~/tmp $ cat kernel-messages-5.14.9.txt |grep igb
Oct 5 02:38:31 dilfridge kernel: [ 2.108606] igb: Intel(R) Gigabit Ethernet Network Driver
Oct 5 02:38:31 dilfridge kernel: [ 2.108608] igb: Copyright (c) 2007-2014 Intel Corporation.
Oct 5 02:38:31 dilfridge kernel: [ 2.108622] igb 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Oct 5 02:38:31 dilfridge kernel: [ 2.108918] igb 0000:01:00.0 0000:01:00.0 (uninitialized): PCIe link lost
Oct 5 02:38:31 dilfridge kernel: [ 2.418724] igb 0000:01:00.0: PHY reset is blocked due to SOL/IDER session.
Oct 5 02:38:31 dilfridge kernel: [ 4.148163] igb 0000:01:00.0: The NVM Checksum Is Not Valid
Oct 5 02:38:31 dilfridge kernel: [ 4.154891] igb: probe of 0000:01:00.0 failed with error -5
Oct 5 02:38:31 dilfridge kernel: [ 4.154904] igb 0000:01:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Oct 5 02:38:31 dilfridge kernel: [ 4.155146] igb 0000:01:00.1 0000:01:00.1 (uninitialized): PCIe link lost
Oct 5 02:38:31 dilfridge kernel: [ 4.466904] igb 0000:01:00.1: PHY reset is blocked due to SOL/IDER session.
Oct 5 02:38:31 dilfridge kernel: [ 6.195528] igb 0000:01:00.1: The NVM Checksum Is Not Valid
Oct 5 02:38:31 dilfridge kernel: [ 6.200863] 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.
>
> Without any ideas about the issue, please bisect the issue to find the
> commit introducing the regression, so it can be reverted/fixed to not
> violate Linux? no-regression policy.
I'll start going through kernel versions (and later revisions) end of the week.
Thanks a lot,
Andreas
--
PD Dr. Andreas K. Huettel
Institute for Experimental and Applied Physics
University of Regensburg
93040 Regensburg
Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 981 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20211005/8dcdb430/attachment.asc>
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas K. Huettel" <andreas.huettel@ur.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
Jakub Kicinski <kubakici@wp.pl>
Subject: Re: [EXT] Re: [Intel-wired-lan] Intel I350 regression 5.10 -> 5.14 ("The NVM Checksum Is Not Valid") [8086:1521]
Date: Tue, 05 Oct 2021 15:43:08 +0200 [thread overview]
Message-ID: <2944777.ktpJ11cQ8Q@pinacolada> (raw)
In-Reply-To: <35dfc9e8-431c-362d-450e-4c6ac1e55434@molgen.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 4730 bytes --]
>
> What messages are new compared to the working Linux 5.10.59?
>
I've uploaded the full boot logs to https://dev.gentoo.org/~dilfridge/igb/
(both in a version with and without timestamps, for easy diff).
* I can't see anything that immediately points to the igb device (like a PCI id etc.) before the module is loaded.
* The main difference between the logs is many unrelated (?) i915 warnings in 5.10.59 because of the nonfunctional graphics.
The messages easily identifiable are:
huettel@pinacolada ~/tmp $ cat kernel-messages-5.10.59.txt |grep igb
Oct 5 15:11:18 dilfridge kernel: [ 2.090675] igb: Intel(R) Gigabit Ethernet Network Driver
Oct 5 15:11:18 dilfridge kernel: [ 2.090676] igb: Copyright (c) 2007-2014 Intel Corporation.
Oct 5 15:11:18 dilfridge kernel: [ 2.090728] igb 0000:01:00.0: enabling device (0000 -> 0002)
Oct 5 15:11:18 dilfridge kernel: [ 2.094438] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.097287] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.098492] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.098787] Modules linked in: igb(+) i915(+) iosf_mbi acpi_pad efivarfs
Oct 5 15:11:18 dilfridge kernel: [ 2.173386] igb 0000:01:00.0: added PHC on eth0
Oct 5 15:11:18 dilfridge kernel: [ 2.173391] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
Oct 5 15:11:18 dilfridge kernel: [ 2.173395] igb 0000:01:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 6c:b3:11:23:d4:4c
Oct 5 15:11:18 dilfridge kernel: [ 2.173991] igb 0000:01:00.0: eth0: PBA No: H47819-001
Oct 5 15:11:18 dilfridge kernel: [ 2.173994] igb 0000:01:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Oct 5 15:11:18 dilfridge kernel: [ 2.174199] igb 0000:01:00.1: enabling device (0000 -> 0002)
Oct 5 15:11:18 dilfridge kernel: [ 2.261029] igb 0000:01:00.1: added PHC on eth1
Oct 5 15:11:18 dilfridge kernel: [ 2.261034] igb 0000:01:00.1: Intel(R) Gigabit Ethernet Network Connection
Oct 5 15:11:18 dilfridge kernel: [ 2.261038] igb 0000:01:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 6c:b3:11:23:d4:4d
Oct 5 15:11:18 dilfridge kernel: [ 2.261772] igb 0000:01:00.1: eth1: PBA No: H47819-001
Oct 5 15:11:18 dilfridge kernel: [ 2.261776] igb 0000:01:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Oct 5 15:11:18 dilfridge kernel: [ 2.265376] igb 0000:01:00.1 enp1s0f1: renamed from eth1
Oct 5 15:11:18 dilfridge kernel: [ 2.282514] igb 0000:01:00.0 enp1s0f0: renamed from eth0
Oct 5 15:11:31 dilfridge kernel: [ 17.585202] igb 0000:01:00.0 enp1s0f0: igb: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
huettel@pinacolada ~/tmp $ cat kernel-messages-5.14.9.txt |grep igb
Oct 5 02:38:31 dilfridge kernel: [ 2.108606] igb: Intel(R) Gigabit Ethernet Network Driver
Oct 5 02:38:31 dilfridge kernel: [ 2.108608] igb: Copyright (c) 2007-2014 Intel Corporation.
Oct 5 02:38:31 dilfridge kernel: [ 2.108622] igb 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Oct 5 02:38:31 dilfridge kernel: [ 2.108918] igb 0000:01:00.0 0000:01:00.0 (uninitialized): PCIe link lost
Oct 5 02:38:31 dilfridge kernel: [ 2.418724] igb 0000:01:00.0: PHY reset is blocked due to SOL/IDER session.
Oct 5 02:38:31 dilfridge kernel: [ 4.148163] igb 0000:01:00.0: The NVM Checksum Is Not Valid
Oct 5 02:38:31 dilfridge kernel: [ 4.154891] igb: probe of 0000:01:00.0 failed with error -5
Oct 5 02:38:31 dilfridge kernel: [ 4.154904] igb 0000:01:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Oct 5 02:38:31 dilfridge kernel: [ 4.155146] igb 0000:01:00.1 0000:01:00.1 (uninitialized): PCIe link lost
Oct 5 02:38:31 dilfridge kernel: [ 4.466904] igb 0000:01:00.1: PHY reset is blocked due to SOL/IDER session.
Oct 5 02:38:31 dilfridge kernel: [ 6.195528] igb 0000:01:00.1: The NVM Checksum Is Not Valid
Oct 5 02:38:31 dilfridge kernel: [ 6.200863] 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.
>
> Without any ideas about the issue, please bisect the issue to find the
> commit introducing the regression, so it can be reverted/fixed to not
> violate Linux’ no-regression policy.
I'll start going through kernel versions (and later revisions) end of the week.
Thanks a lot,
Andreas
--
PD Dr. Andreas K. Huettel
Institute for Experimental and Applied Physics
University of Regensburg
93040 Regensburg
Germany
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2021-10-05 13:43 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
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 ` Andreas K. Huettel [this message]
2021-10-05 13:43 ` [EXT] " 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=2944777.ktpJ11cQ8Q@pinacolada \
--to=andreas.huettel@ur.de \
--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.