Skip to contentSkip to conversation

e1000e hardware failure due to PCI patch in all kernels 5.10.36+ with Intel I219-V]

[email protected]: Bjorn Helgaas 2 participants 4 messages Jun 21, 2021 – Jun 22, 2021 PCI

lore
Share & tools
lore
#0 lore raw

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.

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.

#1 lore raw
Quoted 4 lines · Bjorn Helgaas

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.

Do you want me to push the revert?

Quoted 25 lines

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.

#2 lore raw
Quoted 7 lines · Rafael J. Wysocki
Quoted 4 lines · Bjorn Helgaas

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.

Quoted 1 line

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 25 lines
Quoted 25 lines

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.

#3 lore raw
Quoted 8 lines · Bjorn Helgaas
Quoted 6 lines · Rafael J. Wysocki
Quoted 4 lines · Bjorn Helgaas

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.

Quoted 8 lines
Quoted 1 line

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

Sounds good.

Quoted 1 line

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!

Will do, thanks!