From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug report: Bad mode in FIQ handler detected on CPU0, code 0x56000000
Date: Thu, 9 Aug 2018 14:16:22 +0100 [thread overview]
Message-ID: <20180809131622.GC29785@arm.com> (raw)
In-Reply-To: <381494229.23979617.1533818858635.JavaMail.zimbra@redhat.com>
Hi Chunyu,
On Thu, Aug 09, 2018 at 08:47:38AM -0400, Chunyu Hu wrote:
> I hit an 100% panic when I executed:
>
> perf &
> perf top
>
> Logs are as below,
>
> [ 123.234492] Bad mode in FIQ handler detected on CPU0, code 0x56000000 -- SVC (AArch64)
Oh dear...
We don't support FIQ in Linux, since:
(a) It's seldom available on the non-secure side
(b) It's not necessarily "fast", despite the name
(c) We'd be opening up a can of worms if we allow FIQ to preempt IRQ. Better
off using SDEI or GIC priorities to implement NMIs.
(d) I don't think FIQs can be described in ACPI or DT
In this case, it looks like the PMU interrupt has been configured as a FIQ.
It should be possible to configure the GIC in firmware (not sure you have
EL3, so maybe in the bootloader) to treat this interrupt as an IRQ instead,
in which case perf top will work correctly as long as the ACPI tables / FDT
accurately describe the interrupt.
Will
next prev parent reply other threads:[~2018-08-09 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1426298268.23978174.1533818483053.JavaMail.zimbra@redhat.com>
2018-08-09 12:47 ` Bug report: Bad mode in FIQ handler detected on CPU0, code 0x56000000 Chunyu Hu
2018-08-09 13:16 ` Will Deacon [this message]
2018-08-10 6:30 ` Chunyu Hu
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=20180809131622.GC29785@arm.com \
--to=will.deacon@arm.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).