From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Michael <phyre@rogers.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [bugzilla-daemon@bugzilla.kernel.org: [Bug 213481] e1000e hardware failure due to PCI patch in all kernels 5.10.36+ with Intel I219-V]
Date: Tue, 22 Jun 2021 07:58:02 -0500 [thread overview]
Message-ID: <20210622125802.GA3323179@bjorn-Precision-5520> (raw)
In-Reply-To: <CAJZ5v0gkETL83rm71LiJ8sed=UFn00_Sss8wJ20-+KQiJR0hew@mail.gmail.com>
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 <helgaas@kernel.org> wrote:
> >
> > 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!
> > 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.
next prev parent reply other threads:[~2021-06-22 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 22:02 [bugzilla-daemon@bugzilla.kernel.org: [Bug 213481] e1000e hardware failure due to PCI patch in all kernels 5.10.36+ with Intel I219-V] Bjorn Helgaas
2021-06-22 12:21 ` Rafael J. Wysocki
2021-06-22 12:58 ` Bjorn Helgaas [this message]
2021-06-22 13:01 ` 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=20210622125802.GA3323179@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=phyre@rogers.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).