From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression: 442ec4c04d1: PCI: dwc: all: Split struct pcie_port into host-only and core structures
Date: Mon, 08 May 2017 18:48:48 +0200 [thread overview]
Message-ID: <1494262128.2322.22.camel@pengutronix.de> (raw)
In-Reply-To: <20170508164440.GB12665@collabora.com>
Am Montag, den 08.05.2017, 18:44 +0200 schrieb Peter Senna Tschudin:
> On Mon, May 08, 2017 at 06:34:08PM +0200, Lucas Stach wrote:
> > Am Montag, den 08.05.2017, 17:02 +0200 schrieb Peter Senna Tschudin:
> > > Hello Kishon,
> > >
> > > Our iMX6 hardware (imx6q-b850v3.dts) is not booting with latest
> > > linux-next and I could bisect until:
> > >
> > > commit 442ec4c04d1235f8c664a74004dae54a7a574d18
> > > Author: Kishon Vijay Abraham I <kishon@ti.com>
> > > Date: Wed Feb 15 18:48:14 2017 +0530
> > >
> > > PCI: dwc: all: Split struct pcie_port into host-only and core structures
> > >
> > > Which seem to be causing our issues. Our device (imx6q-b850v3.dts) boots
> > > fine with 4.10, and also boots if we disable pcie with:
> >
> > Are you sure about this bisect? It seems more likely that the secondary
> > bus scanning goes wrong. It seems Lorenzo Pieralisi's cfg space
> > non-posting patches landed in next, so the root cause of this might just
> > be the driver hooking the wrong fault code now.
> >
> > Async and synchronous aborts are different fault codes on ARM. Can you
> > see of removing the "16 +" in hook_fault_code() in
> > drivers/pci/dwc/pci-imx6.c fixes this issue?
>
> changing it to:
>
> hook_fault_code(6, imx6q_pcie_abort_handler, SIGBUS, 0,
> "imprecise external abort");
>
> made no difference, problem persists...
Can you test if 8 or 10 works?
Regards,
Lucas
next prev parent reply other threads:[~2017-05-08 16:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 15:02 Regression: 442ec4c04d1: PCI: dwc: all: Split struct pcie_port into host-only and core structures Peter Senna Tschudin
2017-05-08 15:13 ` Joao Pinto
2017-05-08 15:20 ` Kishon Vijay Abraham I
2017-05-08 15:31 ` Joao Pinto
2017-05-08 15:46 ` Kishon Vijay Abraham I
2017-05-08 15:39 ` Kishon Vijay Abraham I
2017-05-08 15:50 ` Kishon Vijay Abraham I
2017-05-08 17:15 ` Peter Senna Tschudin
2017-05-08 16:13 ` Peter Senna Tschudin
2017-05-08 16:34 ` Lucas Stach
2017-05-08 16:44 ` Peter Senna Tschudin
2017-05-08 16:48 ` Lucas Stach [this message]
2017-05-08 16:58 ` Peter Senna Tschudin
2017-05-08 17:55 ` Lorenzo Pieralisi
2017-05-08 20:33 ` Peter Senna Tschudin
2017-05-09 16:27 ` Lorenzo Pieralisi
2017-05-08 18:23 ` Lorenzo Pieralisi
2017-05-09 1:30 ` Fabio Estevam
2017-05-09 6:34 ` Peter Senna Tschudin
2017-05-09 10:21 ` Fabio Estevam
2017-05-10 13:17 ` Peter Senna Tschudin
2017-05-10 13:27 ` Fabio Estevam
2017-05-10 13:32 ` Lucas Stach
2017-05-10 14:14 ` Peter Senna Tschudin
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=1494262128.2322.22.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 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).