From: Robert Hancock <hancock@sedsystems.ca>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Richard Zhu <hongxing.zhu@nxp.com>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: iMX6 5.2-rc3 boot failure due to "PCI: imx6: Allow asynchronous probing"
Date: Tue, 11 Jun 2019 17:05:03 -0600 [thread overview]
Message-ID: <857036e0-769b-11bd-2083-5451670bd645@sedsystems.ca> (raw)
In-Reply-To: <CAOMZO5C9fu_h5Ct-rbSuTQ149JFT6tH-iN_r8dnYaDxE7gL+UQ@mail.gmail.com>
On 2019-06-11 2:40 p.m., Fabio Estevam wrote:
> Hi Robert,
>
> On Tue, Jun 11, 2019 at 4:02 PM Robert Hancock <hancock@sedsystems.ca> wrote:
>
>>> [ 13.193578] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000
>>> ranges:
>>> [ 13.200635] imx6q-pcie 1ffc000.pcie: IO 0x01f80000..0x01f8ffff ->
>>> 0x00000000
>>> [ 13.201454] imx-sdma 20ec000.sdma: loaded firmware 3.3
>
> Does this problem happen if you don't load an external SDMA firmware?
Based on some tests, it appears that may help - however it is hard to be
conclusive since the behavior is somewhat random, it doesn't fail every
time. The first few times I booted this version, I didn't see the
problem, but after that it was consistently happening every time until I
reverted the patch.
Is there potentially a dependency where the PCIe controller doesn't like
some other activity that's occurring on the iMX during its
initialization sequence?
--
Robert Hancock
Senior Software Developer
SED Systems, a division of Calian Ltd.
Email: hancock@sedsystems.ca
next prev parent reply other threads:[~2019-06-11 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 0:28 iMX6 5.2-rc3 boot failure due to "PCI: imx6: Allow asynchronous probing" Robert Hancock
2019-06-11 16:47 ` Robert Hancock
2019-06-11 20:40 ` Fabio Estevam
2019-06-11 23:05 ` Robert Hancock [this message]
2019-06-14 13:02 ` Fabio Estevam
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=857036e0-769b-11bd-2083-5451670bd645@sedsystems.ca \
--to=hancock@sedsystems.ca \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.