From: Sudeep Holla <sudeep.holla@arm.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>, Duc Dang <dhdang@apm.com>,
Tanmay Inamdar <tinamdar@apm.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32
Date: Wed, 13 Apr 2016 14:29:15 +0100 [thread overview]
Message-ID: <570E49AB.1090509@arm.com> (raw)
In-Reply-To: <20160413132101.GA22699@localhost>
On 13/04/16 14:21, Bjorn Helgaas wrote:
> On Wed, Apr 13, 2016 at 10:58:18AM +0100, Sudeep Holla wrote:
>> Hi,
>>
>> (sorry for replying on the old thread, but I found it could be related
>> to the issue
>> I have now)
>>
>> On Tue, Jul 28, 2015 at 10:29 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
[...]
>>>>
>>>> Our latest U-Boot is 1.15.15, but U-Boot 1.15.12 is already a good
>>>> version to use. Are you running any PCIe traffic test when the error
>>>> happens?
>>>
>>> Nope, the machine was either idle or running a reboot test; no PCIe stress
>>> test or anything.
>>>
>>
>> Was there any conclusion on this ?
>> I am having similar issue[1] on my Juno with sky2 PCIe driver during reboot.
>
> We found that the unhandled faults occurred when using an extender
> card. After removing the extender card, we didn't see the faults any
> more.
>
Thanks for the response. It's not related then, I saw report referencing
reboot tests and hence linked them together. Sorry for the noise.
--
Regards,
Sudeep
>> [1] http://marc.info/?l=linux-netdev&m=146046999701956&w=2
next prev parent reply other threads:[~2016-04-13 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 22:42 X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32 Bjorn Helgaas
2015-07-25 0:05 ` 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 [this message]
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=570E49AB.1090509@arm.com \
--to=sudeep.holla@arm.com \
--cc=bhelgaas@google.com \
--cc=dhdang@apm.com \
--cc=helgaas@kernel.org \
--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).