From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Samuel Dionne-Riel <samuel@dionne-riel.com>
Cc: Marc Zyngier <maz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Boot failure on gru-scarlet-inx with 5.9-rc2
Date: Wed, 2 Sep 2020 17:01:19 +0100 [thread overview]
Message-ID: <20200902160110.GA30014@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200901143356.0425d9ba@DUFFMAN>
On Tue, Sep 01, 2020 at 02:33:56PM -0400, Samuel Dionne-Riel wrote:
> On Tue, 1 Sep 2020 17:42:49 +0100
> Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
>
> > On Tue, Sep 01, 2020 at 04:37:42PM +0100, Marc Zyngier wrote:
> > > On 2020-09-01 04:45, Samuel Dionne-Riel wrote:
> > > > - if (pci_is_root_bus(bus->parent) && dev > 0)
> > > > + if (bus->primary == rockchip->root_bus_nr && dev > 0)
> >
> > Can you dump bus->primary when this condition is hit please ?
>
> With the following diff
>
> ---
> @@ -79,6 +79,8 @@ static int rockchip_pcie_valid_device(struct rockchip_pcie *rockchip,
> * do not read more than one device on the bus directly attached
> * to RC's downstream side.
> */
> + printk("[!!] // bus->parent (%d)\n", bus->parent);
Please print a pointer as a pointer and print both bus and bus->parent.
> + printk("[!!] bus->primary (%d) == rockchip->root_bus_nr (%d) && dev (%d) > 0\n", bus->primary, rockchip->root_bus_nr, dev);
> if (bus->primary == rockchip->root_bus_nr && dev > 0)
> return 0;
>
> --
>
> I get two kind of results
>
> [ 1.692913] [!!] // bus->parent (0)
> [ 1.692917] [!!] bus->primary (0) == rockchip->root_bus_nr (0) && dev (0) > 0
>
> and
>
> [ 1.693055] [!!] // bus->parent (-256794624)
> [ 1.693058] [!!] bus->primary (0) == rockchip->root_bus_nr (0) && dev (0) > 0
>
Looks like this is the condition that pci_is_root_bus(bus->parent) is
not hitting.
[...]
> > > > + /* HACK; ~equiv to last param of
> > > > pci_parse_request_of_pci_ranges */
> > > > + bus_res = (resource_list_first_type(&bridge->windows,
> > > > IORESOURCE_MEM))->res;
> >
> > IORESOURCE_MEM ? I am a bit puzzled by this hack, what is it supposed
> > to do ?
>
> It's not really supposed to do anything. I only needed access to
> bus_res for bus_res->start to keep as root_bus_nr. My complete lack of
> familiarity with all of this meant that I simply borrowed something
> that was in use in another function to give me the bus_res.
You are accessing a resource IORESOURCE_MEM that has nothing to do
with bus numbers.
s/IORESOURCE_MEM/IORESOURCE_BUS
should be better ;-)
Lorenzo
next prev parent reply other threads:[~2020-09-02 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 20:54 Boot failure on gru-scarlet-inx with 5.9-rc2 Samuel Dionne-Riel
2020-08-30 9:41 ` Marc Zyngier
2020-08-30 20:19 ` Samuel Dionne-Riel
2020-08-31 7:18 ` Samuel Dionne-Riel
2020-08-31 9:27 ` Marc Zyngier
2020-09-01 3:45 ` Samuel Dionne-Riel
2020-09-01 15:37 ` Marc Zyngier
2020-09-01 16:42 ` Lorenzo Pieralisi
2020-09-01 18:33 ` Samuel Dionne-Riel
2020-09-02 16:01 ` Lorenzo Pieralisi [this message]
2020-09-03 3:47 ` Samuel Dionne-Riel
2020-09-03 9:19 ` Lorenzo Pieralisi
2020-09-03 14:35 ` Rob Herring
2020-09-03 15:59 ` Marc Zyngier
2020-09-03 19:21 ` Samuel Dionne-Riel
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=20200902160110.GA30014@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=samuel@dionne-riel.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;
as well as URLs for NNTP newsgroup(s).