Re: qemu-system-aarch64 windows binary run Arm64 defconfig kernel not working

[Peter Maydell]

On Mon, 23 Mar 2020 at 16:16, yoma sophian <address@hidden> wrote:
>
> hi Peter:
> > Is it possible for you to try with a newer version of QEMU? That one
> > is a release candidate snapshot from before a release that we made
> > a year ago.
> With below qemu version, 4.2.0, the latest on the qemu windows download page,
> Synchronous External Abort still happen with the problem still hape

Hi; I can't reproduce this (Linux host) either with QEMU
head-of-git (commit 29e0855c5af62bbb0b) or with QEMU 4.2.0.
I used kernel commit 16fbf79b0f83bc7 (which is 5.6-rc7).

[...]
[    1.875186] io scheduler kyber registered
[    1.980486] pl061_gpio 9030000.pl061: PL061 GPIO chip registered
[    2.004922] pci-host-generic 4010000000.pcie: host bridge
/pcie@10000000 ranges:
[    2.007411] pci-host-generic 4010000000.pcie:       IO
0x003eff0000..0x003effffff -> 0x0000000000
[    2.009533] pci-host-generic 4010000000.pcie:      MEM
0x0010000000..0x003efeffff -> 0x0010000000
[    2.010493] pci-host-generic 4010000000.pcie:      MEM
0x8000000000..0xffffffffff -> 0x8000000000
[    2.013505] pci-host-generic 4010000000.pcie: ECAM at [mem
0x4010000000-0x401fffffff] for [bus 00-ff]
[    2.017734] pci-host-generic 4010000000.pcie: PCI host bridge to bus 0000:00
[    2.018963] pci_bus 0000:00: root bus resource [bus 00-ff]
[    2.019655] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    2.020104] pci_bus 0000:00: root bus resource [mem 0x10000000-0x3efeffff]
[    2.020578] pci_bus 0000:00: root bus resource [mem
0x8000000000-0xffffffffff]
[    2.024698] pci 0000:00:00.0: [1b36:0008] type 00 class 0x060000
[    2.038319] pci 0000:00:01.0: [1af4:1000] type 00 class 0x020000
[    2.039848] pci 0000:00:01.0: reg 0x10: [io  0x0000-0x001f]
[    2.040365] pci 0000:00:01.0: reg 0x14: [mem 0x00000000-0x00000fff]
[    2.041106] pci 0000:00:01.0: reg 0x20: [mem 0x00000000-0x00003fff
64bit pref]
[    2.041631] pci 0000:00:01.0: reg 0x30: [mem 0x00000000-0x0003ffff pref]
[    2.056259] pci 0000:00:01.0: BAR 6: assigned [mem
0x10000000-0x1003ffff pref]
[    2.057782] pci 0000:00:01.0: BAR 4: assigned [mem
0x8000000000-0x8000003fff 64bit pref]
[    2.058828] pci 0000:00:01.0: BAR 1: assigned [mem 0x10040000-0x10040fff]
[    2.059381] pci 0000:00:01.0: BAR 0: assigned [io  0x1000-0x101f]
[    2.096264] EINJ: ACPI disabled.
[    2.217421] virtio-pci 0000:00:01.0: enabling device (0000 -> 0003)
[    2.307843] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    2.338768] SuperH (H)SCI(F) driver initialized
[    2.346260] msm_serial: driver initialized
[...]

Your repro instructions said to use the upstream (torvalds)
kernel, but your log file says you were running:

[    0.000000] Linux version 4.14.128-00888-g15ac2b5e934a-dirty
(mtk20533@mtkslt1006) (Android (5220042 based on r346389c) clang
version 8.0.7 (https://android.googlesource.com/toolchain/clang
b55f2d4ebfd35bf643d27dbca1bb228957008617)
(https://android.googlesource.com/toolchain/llvm
3c393fe7a7e13b0fba4ac75a01aa683d7a5b11cd) (based on LLVM 8.0.7svn)) #8
SMP PREEMPT Thu Feb 20 17:45:16 CST 2020

which definitely isn't a recent upstream kernel.
Can you reproduce with an upstream kernel?

thanks
-- PMM