From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: "Z.Q. Hou" <Zhiqiang.Hou@nxp.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Kishon Vijay Abraham I <kishon@ti.com>,
Michael Walle <michael@walle.cc>,
Gustavo Pimentel <Gustavo.Pimentel@synopsys.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Ard Biesheuvel <ardb@kernel.org>, PCI <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] PCI: dwc: Added link up check in map_bus of dw_child_pcie_ops
Date: Thu, 8 Oct 2020 22:21:24 +0530 [thread overview]
Message-ID: <CA+G9fYufopBTRdqdHy=m17mc2N2Y8o-bcqAz_nON7X6ZYAb7Ug@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+uFJp5Vt=u2ZFhGCTTM62mb_1rKOz_Dj2=ez5bKJad1Q@mail.gmail.com>
On Thu, 8 Oct 2020 at 20:42, Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Oct 8, 2020 at 9:47 AM Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > On Fri, 2 Oct 2020 at 14:59, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > >
> > > On Thu, 1 Oct 2020 at 22:16, Michael Walle <michael@walle.cc> wrote:
> > > >
> > > > Am 2020-10-01 15:32, schrieb Kishon Vijay Abraham I:
> > > >
> > > > > Meanwhile would it be okay to add linkup check atleast for DRA7X so
> > > > > that
> > > > > we could have it booting in linux-next?
> > > >
> > > > Layerscape SoCs (at least the LS1028A) are also still broken in
> > > > linux-next,
> > > > did I miss something here?
> > >
> > > I have been monitoring linux next boot and functional testing on nxp devices
> > > for more than two week and still the problem exists on nxp-ls2088.
> > >
> > > Do you mind checking the possibilities to revert bad patches on linux next tree
> > > and continue to work on fixes please ?
> > >
> > > suspected bad commit: [ I have not bisected this problem ]
> > > c2b0c098fbd1 ("PCI: dwc: Use generic config accessors")
> > >
> > > crash log snippet:
> > > [ 1.563008] SError Interrupt on CPU5, code 0xbf000002 -- SError
> > > [ 1.563010] CPU: 5 PID: 1 Comm: swapper/0 Not tainted
> > > 5.9.0-rc7-next-20201001 #1
> > > [ 1.563011] Hardware name: Freescale Layerscape 2088A RDB Board (DT)
> > > [ 1.563013] pstate: 20000085 (nzCv daIf -PAN -UAO -TCO BTYPE=--)
> > > [ 1.563014] pc : pci_generic_config_read+0x44/0xe8
> > > [ 1.563015] lr : pci_generic_config_read+0x2c/0xe8
> >
> >
> > This reported issue is gone now on Linux next master branch.
I am taking this verdict back.
I have seen the boot pass and the reported issue is gone but after checking
all 20 test jobs the 4 boot passes without the above reported error.
and later the 16 boot failed with the reported error.
> > I am not sure which is a fix commit.
>
> There isn't one, better double check that. We're still waiting on
> respinning of the revert patch.
>
> BTW, why is the kernelci NXP lab almost always down? I have a branch
> now to test things and I'm not done breaking the DWC driver. :)
Now the NXP LAVA lab is back online after upgrade.
LKFT running daily testing on device "nxp-ls2088" [1]
You can monitor and check results on Linaro Linux next project [2]
[1] https://lavalab.nxp.com/scheduler/device_type/nxp-ls2088
[2] https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20201008/?results_layout=table&failures_only=false#!?details=995,999#test-results
- Naresh
next prev parent reply other threads:[~2020-10-08 16:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 5:41 [PATCH] PCI: dwc: Added link up check in map_bus of dw_child_pcie_ops Zhiqiang Hou
2020-09-16 20:28 ` Rob Herring
2020-09-18 11:02 ` Z.q. Hou
2020-09-18 11:14 ` Michael Walle
2020-09-21 14:48 ` Z.q. Hou
2020-09-18 12:47 ` Bjorn Helgaas
2020-09-21 16:31 ` Z.q. Hou
2020-09-18 15:27 ` Rob Herring
2020-09-24 4:24 ` Z.q. Hou
2020-09-28 9:39 ` Lorenzo Pieralisi
2020-09-29 4:05 ` Z.q. Hou
2020-09-29 15:24 ` Gustavo Pimentel
2020-09-29 17:11 ` Rob Herring
2020-09-30 13:22 ` Kishon Vijay Abraham I
2020-09-30 15:01 ` Rob Herring
2020-10-01 13:32 ` Kishon Vijay Abraham I
2020-10-01 16:46 ` Michael Walle
2020-10-02 9:29 ` Naresh Kamboju
2020-10-08 14:46 ` Naresh Kamboju
2020-10-08 15:12 ` Rob Herring
2020-10-08 16:51 ` Naresh Kamboju [this message]
2020-10-08 15:08 ` Lorenzo Pieralisi
2020-10-12 16:31 ` Kishon Vijay Abraham I
2020-10-12 4:41 ` Z.q. Hou
2020-10-19 16:13 ` Lorenzo Pieralisi
2020-10-20 8:07 ` Kishon Vijay Abraham I
2020-10-12 4:22 ` Z.q. Hou
2020-10-20 9:48 ` Lorenzo Pieralisi
2020-10-13 9:15 ` Lorenzo Pieralisi
2020-10-14 11:13 ` Lorenzo Pieralisi
2020-10-14 12:37 ` Rob Herring
2020-10-15 22:47 ` Bjorn Helgaas
2020-10-16 11:59 ` Lorenzo Pieralisi
2020-10-19 5:24 ` Z.q. Hou
2020-10-19 5:41 ` Kishon Vijay Abraham I
2020-10-20 2:13 ` Z.q. Hou
2020-10-20 9:12 ` Lorenzo Pieralisi
2020-10-20 9:55 ` Lorenzo Pieralisi
2020-10-21 8:47 ` Z.q. Hou
2020-10-22 6:20 ` Richard Zhu
2020-10-19 16:26 ` Lorenzo Pieralisi
2020-10-20 10:19 ` Lorenzo Pieralisi
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='CA+G9fYufopBTRdqdHy=m17mc2N2Y8o-bcqAz_nON7X6ZYAb7Ug@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=Gustavo.Pimentel@synopsys.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=ardb@kernel.org \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=michael@walle.cc \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).