From: "Andreas K. Huettel" <andreas.huettel@ur.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
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, 12 Oct 2021 18:34:35 +0200 [thread overview]
Message-ID: <2801801.e9J7NaK4W3@kailua> (raw)
In-Reply-To: <c75203e9-0ef4-20bd-87a5-ad0846863886@intel.com>
> > 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)
>
> This line is missing below, it indicates that the kernel couldn't or
> didn't power up the PCIe for some reason. We're looking for something
> like ACPI or PCI patches (possibly PCI-Power management) to be the
> culprit here.
>
So I did a git bisect from linux-v5.10 (good) to linux-v5.14.11 (bad).
The result was:
dilfridge /usr/src/linux-git # git bisect bad
6381195ad7d06ef979528c7452f3ff93659f86b1 is the first bad commit
commit 6381195ad7d06ef979528c7452f3ff93659f86b1
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Mon May 24 17:26:16 2021 +0200
ACPI: power: Rework turning off unused power resources
[...]
I tried naive reverting of this commit on top of 5.14.11. That applies nearly cleanly,
and after a reboot the additional ethernet interfaces show up with their MAC in the
boot messages.
(Not knowing how safe that experiment was, I did not go further than single mode and
immediately rebooted into 5.10 afterwards.)
--
PD Dr. Andreas K. Huettel
Institute for Experimental and Applied Physics
University of Regensburg
93040 Regensburg
Germany
e-mail andreas.huettel@ur.de
http://www.akhuettel.de/
http://www.physik.uni-r.de/forschung/huettel/
WARNING: multiple messages have this Message-ID (diff)
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, 12 Oct 2021 18:34:35 +0200 [thread overview]
Message-ID: <2801801.e9J7NaK4W3@kailua> (raw)
In-Reply-To: <c75203e9-0ef4-20bd-87a5-ad0846863886@intel.com>
> > 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)
>
> This line is missing below, it indicates that the kernel couldn't or
> didn't power up the PCIe for some reason. We're looking for something
> like ACPI or PCI patches (possibly PCI-Power management) to be the
> culprit here.
>
So I did a git bisect from linux-v5.10 (good) to linux-v5.14.11 (bad).
The result was:
dilfridge /usr/src/linux-git # git bisect bad
6381195ad7d06ef979528c7452f3ff93659f86b1 is the first bad commit
commit 6381195ad7d06ef979528c7452f3ff93659f86b1
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Mon May 24 17:26:16 2021 +0200
ACPI: power: Rework turning off unused power resources
[...]
I tried naive reverting of this commit on top of 5.14.11. That applies nearly cleanly,
and after a reboot the additional ethernet interfaces show up with their MAC in the
boot messages.
(Not knowing how safe that experiment was, I did not go further than single mode and
immediately rebooted into 5.10 afterwards.)
--
PD Dr. Andreas K. Huettel
Institute for Experimental and Applied Physics
University of Regensburg
93040 Regensburg
Germany
e-mail andreas.huettel at ur.de
http://www.akhuettel.de/
http://www.physik.uni-r.de/forschung/huettel/
next prev parent reply other threads:[~2021-10-12 16:34 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 ` [EXT] Re: [Intel-wired-lan] " Hisashi T Fujinaka
2021-10-05 0:21 ` [Intel-wired-lan] [EXT] " 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 ` Andreas K. Huettel [this message]
2021-10-12 16:34 ` 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=2801801.e9J7NaK4W3@kailua \
--to=andreas.huettel@ur.de \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kubakici@wp.pl \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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.