From: Bjorn Helgaas <bhelgaas@google.com>
To: Tanmay Inamdar <tinamdar@apm.com>
Cc: Duc Dang <dhdang@apm.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32
Date: Fri, 24 Jul 2015 17:42:58 -0500 [thread overview]
Message-ID: <20150724224258.GA23990@google.com> (raw)
I regularly see faults like this on an APM X-Gene:
U-Boot 2013.04-mustang_sw_1.14.14 (Dec 16 2014 - 15:59:33)
CPU0: APM ARM 64-bit Potenza Rev B0 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
...
Unhandled fault: synchronous external abort (0x96000010) at 0xffffff8000110034
Internal error: : 96000010 [#1] SMP
Modules linked in:
CPU: 0 PID: 3723 Comm: ... 4.1.0-smp-DEV #3
Hardware name: APM X-Gene Mustang board (DT)
task: ffffffc7dc1a4140 ti: ffffffc7dc118000 task.ti: ffffffc7dc118000
PC is at pci_generic_config_read32+0x4c/0xb8
LR is at pci_generic_config_read32+0x40/0xb8
pc : [<ffffffc00033b90c>] lr : [<ffffffc00033b900>] pstate: 600001c5
...
Call trace:
[<ffffffc00033b90c>] pci_generic_config_read32+0x4c/0xb8
[<ffffffc00033bf58>] pci_user_read_config_byte+0x60/0xc4
[<ffffffc0003496a8>] pci_read_config+0x15c/0x238
[<ffffffc0002393b4>] sysfs_kf_bin_read+0x68/0xa0
[<ffffffc00023896c>] kernfs_fop_read+0x9c/0x1ac
[<ffffffc0001c361c>] __vfs_read+0x44/0x128
[<ffffffc0001c3e28>] vfs_read+0x84/0x144
[<ffffffc0001c4764>] SyS_read+0x50/0xb0
# lspci
00:00.0 PCI bridge: Applied Micro Circuits Corp. Device e004 (rev 04)
01:00.0 Ethernet controller: Mellanox Technologies MT27520 Family
I first saw this on an ancient kernel and thought it was likely specific to
my environment, but I'm now using an almost unmodified v4.1 kernel and
still seeing it. Does anybody else see this? The box does have a PCI card
installed, but I haven't yet worked out what device's config space we're
trying to read.
Is there anything I can do to debug this? I'm not an arm64 guy, but my
impression is that this is a page fault, and the address seems to be in the
"cfg" area ioremapped by xgene_pcie_map_reg(), so I'm not sure this is
really a PCI issue -- maybe that page mapping got trashed by somebody else?
Bjorn
next reply other threads:[~2015-07-24 22:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 22:42 Bjorn Helgaas [this message]
2015-07-25 0:05 ` X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32 Duc Dang
2015-07-27 11:36 ` Catalin Marinas
2015-07-28 17:39 ` Duc Dang
2015-07-28 18:36 ` Bjorn Helgaas
2015-07-28 16:43 ` Bjorn Helgaas
2015-07-28 17:45 ` Duc Dang
2015-07-28 21:29 ` Bjorn Helgaas
2015-07-28 21:50 ` Duc Dang
2015-07-29 1:22 ` Bjorn Helgaas
2015-07-29 15:55 ` Bjorn Helgaas
2015-07-31 17:00 ` Duc Dang
2015-08-10 16:18 ` Bjorn Helgaas
2015-08-10 17:38 ` Catalin Marinas
[not found] ` <CADaLNDkUQHzGACfFmYDeJWnaNrKmJUDx4Rby60OWr4FzOjx3rA@mail.gmail.com>
2015-08-10 17:42 ` Bjorn Helgaas
2015-08-10 19:07 ` Duc Dang
2015-08-11 19:28 ` Bjorn Helgaas
2015-09-05 20:13 ` Jon Masters
2015-09-05 20:22 ` Jon Masters
2016-04-13 9:58 ` Sudeep Holla
2016-04-13 13:21 ` Bjorn Helgaas
2016-04-13 13:29 ` Sudeep Holla
2016-04-13 22:17 ` Jon Masters
2015-07-28 14:37 ` Dall, Elizabeth J
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=20150724224258.GA23990@google.com \
--to=bhelgaas@google.com \
--cc=dhdang@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tinamdar@apm.com \
/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).