From: Adam Lee <adam.lee@canonical.com>
To: Myron Stowe <myron.stowe@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Amos Kong <kongjianjun@gmail.com>,
Myron Stowe <myron.stowe@redhat.com>,
Thomas Renninger <trenn@suse.de>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH] pci: check PCI_EXP_FLAGS_SLOT before setting hotplug bridge
Date: Wed, 20 Nov 2013 15:09:30 +0800 [thread overview]
Message-ID: <20131120070930.GD3821@adam-laptop> (raw)
In-Reply-To: <CAL-B5D2WtALi5RMX9JQQmVUShLEN947cdvr7jjnpfCXS3zmPVw@mail.gmail.com>
On Tue, Nov 19, 2013 at 11:08:06AM -0700, Myron Stowe wrote:
> On Mon, Nov 18, 2013 at 10:57 PM, Adam Lee <adam.lee@canonical.com> wrote:
> > On Mon, Nov 18, 2013 at 10:38:17AM -0700, Bjorn Helgaas wrote:
> >> [+cc Myron, Amos, Thomas, Ben]
> >>
> >> On Mon, Nov 18, 2013 at 2:40 AM, Adam Lee <adam.lee@canonical.com> wrote:
> >> > This patch adds the PCI_EXP_FLAGS_SLOT check back before setting
> >> > hotplug bridge, which is omitted by an API switching commit,
> >> > 59875ae489609b2267548dc85160c5f0f0c6f9d4 "PCI/core: Use PCI Express
> >> > Capability accessors".
> >> >
> >> > Some Lenovo laptops hang in booting without this fix.
> >>
> >> What kernel version hangs? I suspect you might be missing 6d3a1741f1
> >> ("PCI: Support PCIe Capability Slot registers only for ports with
> >> slots"), because it *looks* like the current kernel should work
> >> correctly even without your patch.
> >
> > No, patching 6d3a1741f1 and d3694d4fa3 doesn't fix the hang.
>
> Did you actually try it? This patch did solve a problem that I
> encountered (see below).
On Tue, Nov 19, 2013 at 10:40:09AM -0700, Bjorn Helgaas wrote:
> >
> > It hangs in acpi_evaluate_integer() from
> > 59875ae489609b2267548dc85160c5f0f0c6f9d4 "PCI/core: Use PCI Express
> > Capability accessors" and before
> > ac212b6980d8d5eda705864fc5a8ecddc6d6eacc "ACPI / processor: Use common
> > hotplug infrastructure", 3.4~3.11. (double confirmed)
^^^^^^^^ should be 3.7~3.10
> I don't understand what you're saying here. We're talking about this path:
>
> set_pcie_hotplug_bridge
> pcie_capability_read_dword(dev, PCI_EXP_SLTCAP, ...)
> pcie_capability_reg_implemented(dev, PCI_EXP_SLTCAP)
> pcie_cap_has_sltctl(dev)
>
> This path doesn't invoke acpi_evaluate_integer(). How does a hang
> there relate to the patch you posted? Are you saying you bisected the
> hang to one of the commits you mentioned?
Bjorn and Myron,
Yes, I did try, and those two commits are both coming from bisect, it is weird.
But good news, I tried the new series containing three patches, it fixed that
hang.(backported to 3.8, pcie_flags_reg is fine)
Great thanks.
--
Adam Lee
prev parent reply other threads:[~2013-11-20 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 9:40 [PATCH] pci: check PCI_EXP_FLAGS_SLOT before setting hotplug bridge Adam Lee
2013-11-18 17:38 ` Bjorn Helgaas
2013-11-19 5:57 ` Adam Lee
2013-11-19 17:40 ` Bjorn Helgaas
2013-11-19 18:08 ` Myron Stowe
2013-11-20 7:09 ` Adam Lee [this message]
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=20131120070930.GD3821@adam-laptop \
--to=adam.lee@canonical.com \
--cc=ben@decadent.org.uk \
--cc=bhelgaas@google.com \
--cc=kongjianjun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=myron.stowe@gmail.com \
--cc=myron.stowe@redhat.com \
--cc=trenn@suse.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 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).