On Tue, Jun 22, 2021 at 02:21:06PM +0200, Rafael J. Wysocki wrote:

On Tue, Jun 22, 2021 at 12:02 AM Bjorn Helgaas [off-list ref] wrote:

quoted

FYI.  Looks like 4514d991d992 ("PCI: PM: Do not read power state in
pci_enable_device_flags()") appeared in v5.13-rc1, so it would be nice
to fix before v5.13.

I think let's revert it for now and revisit.

Sounds good.

Do you want me to push the revert?

Sure, it'd be great if you could.  I'm traveling and don't have as
much time as usual this week.  Thanks!

quoted

https://bugzilla.kernel.org/show_bug.cgi?id=213481

Initial report:

  On the 4.19 kernel, this works perfect.  It also works perfectly in
  Windows.  If I reboot into 4.19, there is no problem with networking,
  however in 5.10, there is ZERO network connectivity.  The link NEVER
  comes up.  You can't assign an IP address to the interface.


From comment #2:

  If I revert commit 4514d991d99211f225d83b7e640285f29f0755d0 (
  https://github.com/torvalds/linux/commit/4514d991d99211f225d83b7e640285f29f0755d0)
  from the 5.10.36 kernel, I do NOT have this hardware failure
  message.  This commit relates to PCI power state.

  It would appear something about this change that the e1000e driver
  is not handling properly on this system, causing the card to not
  work.

  As mentioned this is in current kernel versions (5.13, 5.11, and
  5.10.36+).  Given that this is a regression, a breaking change for
  the usability of these cards, and we know exactly what causes it for
  a hopefully easy fix, I've upped the severity.