All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	"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: AW: Unhandled fault: imprecise external abort (0x1406) when loading xhci_pci.ko - uPD720202, PEX8605, iMX6Q and linux-4.19.25
Date: Thu, 22 Aug 2019 11:01:50 +0000	[thread overview]
Message-ID: <bb206643df9346e7830dbf08ec458d18@SVR-IES-MBX-03.mgc.mentorg.com> (raw)
In-Reply-To: <CAGgoGu5vH0LZsJDyTag2aWqicrTboLFHdYJ=0pWAsjuNp-J-BA@mail.gmail.com>

> 
> Occasionally we see crash at boot too without even reaching stage of
> loading xhci-pci.ko driver.
> 
> Log is below. Is this can be because of again uPD connected on PCIe
> bus (through PCIe switch)?
> 
> [    8.263117] Unhandled fault: imprecise external abort (0x1406) at 0xfaf06a5b

Looks like a hardware issue on your board, like PCIe accesses sometimes fail.
Out of my scope, sorry.

Anyway, try with PM disabled.

Best regards
Carsten

  reply	other threads:[~2019-08-22 11:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 21:49 Unhandled fault: imprecise external abort (0x1406) when loading xhci_pci.ko - uPD720202, PEX8605, iMX6Q and linux-4.19.25 Fawad Lateef
2019-07-31 21:51 ` Fwd: " Fawad Lateef
2019-08-01  8:18   ` 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                 ` Schmid, Carsten [this message]
2019-08-22 19:21             ` Bjorn Helgaas
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=bb206643df9346e7830dbf08ec458d18@SVR-IES-MBX-03.mgc.mentorg.com \
    --to=carsten_schmid@mentor.com \
    --cc=fawadlateef@gmail.com \
    --cc=helgaas@kernel.org \
    --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 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.