From: JIANG Muhui <1926759@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1926759] Re: WFI instruction results in unhandled CPU exception
Date: Fri, 30 Apr 2021 13:17:33 -0000 [thread overview]
Message-ID: <161978865386.14105.13909923994406085028.malone@wampee.canonical.com> (raw)
In-Reply-To: 161978229375.10342.16262082750544447119.malonedeb@gac.canonical.com
cmd： ~/qemu-5.1.0/arm-linux-user/qemu-arm ~/test2
QEMU version: qemu-arm version 5.1.0
Sorry that I didn't test it on the latest version of QEMU.
** Attachment added: "test2"
https://bugs.launchpad.net/qemu/+bug/1926759/+attachment/5493873/+files/test2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1926759
Title:
WFI instruction results in unhandled CPU exception
Status in QEMU:
New
Bug description:
Hi
I refer to the WFI instruction. The bytecode is 0xe320f003. After the
execution, qemu exit with the following crash log.
qemu: unhandled CPU exception 0x10001 - aborting
R00=00000001 R01=40800b34 R02=40800b3c R03=000102ec
R04=00010a28 R05=00010158 R06=00087460 R07=00010158
R08=00000000 R09=00000000 R10=00085b7c R11=408009f4
R12=40800a08 R13=408009f0 R14=0001057c R15=000102f8
PSR=60000010 -ZC- A usr32
qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x7f5c21d0fa12
WFI aims to enter a low-power state and wait for interrupt. The raised
exception seems not a right behavior. I can provide a testcase if you
needed. Many thanks.
Regards
Muhui
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1926759/+subscriptions
next prev parent reply other threads:[~2021-04-30 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 11:31 [Bug 1926759] [NEW] WFI instruction results in unhandled CPU exception JIANG Muhui
2021-04-30 13:06 ` [Bug 1926759] " Peter Maydell
2021-04-30 13:07 ` Peter Maydell
2021-04-30 13:17 ` JIANG Muhui [this message]
2021-04-30 13:40 ` Peter Maydell
2021-04-30 13:52 ` Peter Maydell
2021-04-30 14:54 ` JIANG Muhui
2021-04-30 15:09 ` Peter Maydell
2021-04-30 17:51 ` Peter Maydell
2021-05-16 14:29 ` Thomas Huth
2021-08-25 7:06 ` Thomas Huth
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=161978865386.14105.13909923994406085028.malone@wampee.canonical.com \
--to=1926759@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).