From: arend.vanspriel@broadcom.com (Arend van Spriel)
To: linux-arm-kernel@lists.infradead.org
Subject: question about arm64 exception handling
Date: Thu, 28 Jun 2018 13:58:53 +0200 [thread overview]
Message-ID: <5B34CD7D.5090002@broadcom.com> (raw)
Hi Catalin,
I am looking at some issues we are seeing on a custom arm platform and I
had some questions regarding exception handling and hope you can help me
with that.
The platform has 4 cortex a53 cores running 4.1.51 kernel. On the
platform upon accessing our wifi devices over PCIe, we observe two issue
intermittently.
1) synchronous external abort
2) NMI watchdog
With the latter I notice el1_irq in the exception stack trace. Is that
due to the NMI watchdog or is this caused by another issue like our
crappy hardware ;-) ?
Regarding the SEA I noticed stuff has been added for that in 4.13. Is is
worth backporting that to obtain more info about that?
Regards,
Arend
next reply other threads:[~2018-06-28 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 11:58 Arend van Spriel [this message]
2018-06-28 16:13 ` question about arm64 exception handling James Morse
2018-07-02 10:34 ` Arend van Spriel
2018-07-02 10:53 ` James Morse
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=5B34CD7D.5090002@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.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).