From: yoma sophian <sophian.yoma@gmail.com>
To: qemu-devel@nongnu.org
Subject: qemu-system-aarch64 windows binary run Arm64 defconfig kernel not working
Date: Mon, 23 Mar 2020 16:15:50 +0800 [thread overview]
Message-ID: <CADUS3onjS+T-SSYC6ocKNm3oXsCpiQbDa0eJobhOnts3gZ_gEw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2434 bytes --]
hi all:
I try to use qemu-system-aarch64 windows binary for running arm64
defconfig kernel image but get Synchronous External Abort while
booting PCI devices.
The same Image that run on qemu-system-aarch64 linux binary is fine.
Is there any pci related kernel config need to be removed while using
qemu windows binary?
Appreciate ur help in advance.
=============================
My environment are:
1. the versionof qemu-system-aarch64 windows binary is 4.0.92
2. kernel image:
a. check out latest kernel from
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
b. make ARCH=arm64 defconfig
c. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j32
3. run qemu with attach "qemu_run.sh"
Boot up fail log is attached
"qemu_win10_binary_bootup_aarch64_defconfig_fail.log.tar.bz2"
============================
below is excerpt from log, where Synchronous External Abort happens.
============================
[ 2.453924] pci-host-generic 3f000000.pcie: ECAM at [mem
0x3f000000-0x3fffffff] for [bus 00-0f]
[ 2.461280] pci-host-generic 3f000000.pcie: PCI host bridge to bus 0000:00
[ 2.461855] pci_bus 0000:00: root bus resource [bus 00-0f]
[ 2.462188] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 2.462423] pci_bus 0000:00: root bus resource [mem 0x10000000-0x3efeffff]
[ 2.462677] pci_bus 0000:00: root bus resource [mem
0x8000000000-0xffffffffff]
[ 2.463565] Synchronous External Abort: synchronous external abort
(0x96000010) at 0xffff00000c000000
[ 2.464656] Internal error: : 96000010 [#1] PREEMPT SMP
[ 2.465093] Modules linked in:
[ 2.465411] Process swapper/0 (pid: 1, stack limit = 0x (ptrval))
[ 2.465810] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
4.14.128-00888-g15ac2b5e934a-dirty #8
[ 2.466077] Hardware name: linux,dummy-virt (DT)
[ 2.466315] task: (ptrval) task.stack: (ptrval)
[ 2.466556] PC is at pci_generic_config_read+0xa8/0xd8
[ 2.466748] LR is at pci_generic_config_read+0x44/0xd8
[ 2.466925] pc : [<ffff0000085960a4>] lr : [<ffff000008596040>]
pstate: 200001c5
[ 2.467169] sp : ffff00000804b8c0
[ 2.467304] x29: ffff00000804b8f0 x28: ffff00000804bac0
[ 2.467565] x27: 0000000000000001 x26: ffff80003d354e80
[ 2.467892] x25: ffff00000804bac0 x24: 0000000000000140
[ 2.468110] x23: ffff80003c5a0000 x22: 0000000000000000
[ 2.468347] x21: 0000000000000000 x20: 0000000000000004
[-- Attachment #2: qemu_win10_binary_bootup_aarch64_defconfig_fail.log.tar.bz2 --]
[-- Type: application/x-bzip, Size: 5692 bytes --]
[-- Attachment #3: qemu_run.sh.tar.bz2 --]
[-- Type: application/x-bzip, Size: 324 bytes --]
next reply other threads:[~2020-03-23 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 8:15 yoma sophian [this message]
2020-03-23 13:37 ` qemu-system-aarch64 windows binary run Arm64 defconfig kernel not working Peter Maydell
2020-03-23 16:16 ` yoma sophian
2020-03-23 17:05 ` Peter Maydell
2020-03-24 16:28 ` yoma sophian
2020-03-24 16:30 ` Peter Maydell
2020-03-26 17:17 ` yoma sophian
2020-04-03 16:05 ` yoma sophian
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=CADUS3onjS+T-SSYC6ocKNm3oXsCpiQbDa0eJobhOnts3gZ_gEw@mail.gmail.com \
--to=sophian.yoma@gmail.com \
--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).