From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: George Cherian <gcherian@caviumnetworks.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
bhelgaas@google.com, Jayachandran.Nair@cavium.com,
Robert.Richter@cavium.com,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Huang Ying <ying.huang@intel.com>
Subject: Re: [PATCH] PCI: Add quirk for Cavium Thunder-X2 PCIe erratum #173
Date: Thu, 22 Feb 2018 09:35:43 +0100 [thread overview]
Message-ID: <20180222083543.GA14945@wunner.de> (raw)
In-Reply-To: <20180221232040.GA52685@bhelgaas-glaptop.roam.corp.google.com>
On Wed, Feb 21, 2018 at 05:20:40PM -0600, Bjorn Helgaas wrote:
> On Wed, Feb 21, 2018 at 04:25:08PM +0530, George Cherian wrote:
> > I have found another configuration where this fails.
> > Following is the configuration
> > 1) Connected a PCIe Intel i40 card under the root port.
> > 2) unbind the i40 driver and bind with vfio-pci driver.
> > 3) Run lspci in a loop. "lspci -s xx:xx.xx -vvv"
> >
> > I get the same synchronous external abort.
> > In this case the vfio-pci driver probe it moves the device (i40) to
> > D3hot provided disable_idle_d3 is not set. lspci tries to do
> > the config_access which fails with synchronous external abort when
> > the root port transitions to D3hot.
>
> It *looks* like rpm_resume() should resume parent devices, i.e., the
> root port, but I don't know that code at all.
It does that unless the ignore_children flag is set, which only few
drivers do.
Sounds to me like another missing pci_config_pm_runtime_get() somewhere
but it's hard to tell without a stacktrace.
Thanks,
Lukas
next prev parent reply other threads:[~2018-02-22 8:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 7:00 [PATCH] PCI: Add quirk for Cavium Thunder-X2 PCIe erratum #173 George Cherian
2018-02-13 6:23 ` Jayachandran C
2018-02-13 15:09 ` Bjorn Helgaas
2018-02-14 11:28 ` George Cherian
2018-02-14 20:16 ` Bjorn Helgaas
2018-02-15 21:57 ` Rafael J. Wysocki
2018-02-15 23:39 ` Bjorn Helgaas
2018-02-16 12:40 ` Rafael J. Wysocki
2018-02-16 20:34 ` Bjorn Helgaas
2018-02-19 11:21 ` Rafael J. Wysocki
2018-02-19 20:36 ` Bjorn Helgaas
2018-02-20 1:54 ` Lukas Wunner
2018-02-20 10:58 ` Rafael J. Wysocki
2018-02-20 19:00 ` Bjorn Helgaas
2018-02-21 9:28 ` George Cherian
2018-02-21 9:54 ` Lukas Wunner
2018-02-21 10:55 ` George Cherian
2018-02-21 23:20 ` Bjorn Helgaas
2018-02-22 8:35 ` Lukas Wunner [this message]
2018-02-22 10:19 ` Rafael J. Wysocki
2018-02-22 13:13 ` George Cherian
2018-02-22 15:09 ` Bjorn Helgaas
2018-03-13 14:13 ` George Cherian
2018-02-19 19:08 ` Jon Masters
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=20180222083543.GA14945@wunner.de \
--to=lukas@wunner.de \
--cc=Jayachandran.Nair@cavium.com \
--cc=Robert.Richter@cavium.com \
--cc=bhelgaas@google.com \
--cc=gcherian@caviumnetworks.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=ying.huang@intel.com \
/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