From: Bjorn Helgaas <helgaas@kernel.org>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: "Schmid, Carsten" <Carsten_Schmid@mentor.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Richard Zhu <hongxing.zhu@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: Unhandled fault: imprecise external abort (0x1406) when loading xhci_pci.ko - uPD720202, PEX8605, iMX6Q and linux-4.19.25
Date: Thu, 22 Aug 2019 14:21:43 -0500 [thread overview]
Message-ID: <20190822192143.GK14450@google.com> (raw)
In-Reply-To: <CAGgoGu5WP1qQUf4HS8xWGXUuP0L9vM6HGz1OZoGBBh1B67ZYSg@mail.gmail.com>
On Thu, Aug 22, 2019 at 11:18:44AM +0200, Fawad Lateef wrote:
> In all crash cases (when loading/unloading the driver); system stays
> response, so I can look into any possible device status using PCIe
> registers of PEX8605 switch or iMX6 PCIe root hub. Please suggest if
> something I can check to better understand the issue.
You could collect the output of "sudo lspci -vvxxx" and see if the
switch or root port logged any errors. Collect it before and after
the crash and compare the two.
Bjorn
next prev parent reply other threads:[~2019-08-22 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGgoGu5FfLFzCf0QiAd8UcMrZ7gtLyapgT3TZ-Hx0dknWy4LMQ@mail.gmail.com>
[not found] ` <CAGgoGu4zP_7QpKHiXSkLfkb=zHEezBzstVfjQMQ4CO60+YubCw@mail.gmail.com>
2019-08-01 8:18 ` Unhandled fault: imprecise external abort (0x1406) when loading xhci_pci.ko - uPD720202, PEX8605, iMX6Q and linux-4.19.25 Fawad Lateef
2019-08-01 17:17 ` Bjorn Helgaas
2019-08-02 8:22 ` AW: " Schmid, Carsten
2019-08-02 10:56 ` Fawad Lateef
2019-08-22 9:18 ` Fawad Lateef
2019-08-22 9:34 ` AW: " Schmid, Carsten
2019-08-22 10:44 ` Fawad Lateef
2019-08-22 11:01 ` AW: " Schmid, Carsten
2019-08-22 19:21 ` Bjorn Helgaas [this message]
2019-08-02 10:55 ` Fawad Lateef
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=20190822192143.GK14450@google.com \
--to=helgaas@kernel.org \
--cc=Carsten_Schmid@mentor.com \
--cc=fawadlateef@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 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).