Re: [Xen-devel] Xen GCC coverage ARM64 testing - Unexpected Trap: Data Abort

[Viktor Mitin <viktor.mitin.19@xxxxxxxxx>]

Hi Julien,

Please find trace log below:

root@h3ulcb:~# xencov reset
(XEN) Data Abort Trap. Syndrome=0x7
(XEN) Walking Hypervisor VA 0x361700 on CPU3 via TTBR 0x0000000078266000
(XEN) 0TH[0x0] = 0x0000000078265f7f
(XEN) 1ST[0x0] = 0x0000000078262f7f
(XEN) 2ND[0x1] = 0x004000007825ff7f
(XEN) 3RD[0x161] = 0x00600000781e1f7e
(XEN) CPU3: Unexpected Trap: Data Abort
(XEN) ----[ Xen-4.13-unstable  arm64  debug=y Not tainted ]----
(XEN) CPU:    3
(XEN) PC:     000000000027bd10 gcov_info_reset+0/0x100
(XEN) LR:     000000000027bbd8
(XEN) SP:     000080037ff07c80
(XEN) CPSR:   60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN)    X0: 0000000000361698  X1: 00000000003b0d80  X2: 0000000000000047
(XEN)    X3: 0000000000000020  X4: 0000000000000000  X5: 0000000000000040
(XEN)    X6: 000000000000003f  X7: 0000000000000000  X8: 00000000003b2e40
(XEN)    X9: 0000000000000000 X10: 0000000000000000 X11: 0000000000000000
(XEN)   X12: 0000000000000000 X13: 0000000000000000 X14: 0000000000000000
(XEN)   X15: 0000ffffa12a5d00 X16: 0000000000000023 X17: 0000ffffa12670a0
(XEN)   X18: 0000000000000530 X19: 00000000003b0ba8 X20: 0000000000361698
(XEN)   X21: 00000000003b0c18 X22: 00000000003fb820 X23: 000000000031e698
(XEN)   X24: 0000ffffc598aac0 X25: 0000000000000124 X26: 000000000000001d
(XEN)   X27: ffff000008b11000 X28: ffff8006e98e8000  FP: ffff00000e8abd50
(XEN)
(XEN) VTCR_EL2: 80043594
(XEN)  VTTBR_EL2: 000100073ffc5000
(XEN)
(XEN)  SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 000000008078663f
(XEN)  TTBR0_EL2: 0000000078266000
(XEN)
(XEN) ESR_EL2: 96000007
(XEN)  HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000361700
(XEN)
(XEN) Xen stack trace from sp=000080037ff07c80:
(XEN) 00000000003b0ba8 0000ffffa1451010 00000000003ad558 000000000027b674
(XEN) 0000000000000000 0000ffffa1451010 000000000026b1ac 0000ffffa1451010
(XEN) 000000000026a280 000000000026a1c4 000080037ff07eb0 00000000003f44f0
(XEN) 00000000003f4c80 000080037ff07f30 000000005a000ea1 0000ffffc598aac0
(XEN) 0000000000000124 000000000028aa5c 000080037ffc7000 00000000003b8a78
(XEN) 00000000002a8cd8 000000097e6cf99f 000000000028b12c 000000000028b090
(XEN) 00000000003b8f38 000080037feed000 000080037ffc7000 000000000028baec
(XEN) 000080037ffc7000 000080037feed000 00000000003a6a28 000000000025d898
(XEN) 00000000003a8700 0000000000000003 00000000003acdd0 0000000000000003
(XEN) 000080037ffd8308 00000000002b0cc0 00000000003f5118 0000001200000014
(XEN) 0000000000000002 ffffffffffffffff 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 000000005a000ea1 000080037ff07eb0 ffff000008b11000 0000000020000145
(XEN) 00000000002abd64 ffff000009169000 ffff8006edb15668 ffff8006ec193c00
(XEN) 000080037ff07fb8 000080037feeddf0 00000000002c342c ffff000009169000
(XEN) 00000000002c3430 9393004760000249 0000ffffa1451010 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) ffff00000e8abe00 0000000000000000 0000000000000000 0000000000000200
(XEN) 0101010101010101 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000ffffa12b2d98 0000ffffa12a5d00 0000000000000023 0000ffffa12670a0
(XEN) 0000000000000530 ffff8006edb15668 ffff8006ec193c00 ffff8006ec193c00
(XEN) 0000ffffc598aac0 0000000000305000 0000ffffc598aac0 0000000000000124
(XEN) 000000000000001d ffff000008b11000 ffff8006e98e8000 ffff00000e8abd50
(XEN) ffff000008551a10 ffffffffffffffff ffff0000080c1eec 5a000ea120000145
(XEN) 0000000080000000 0000000000000000 0000000000000000 ffff8006e98e8000
(XEN) ffff00000e8abd50 0000ffffa13664dc 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000027bd10>] gcov_info_reset+0/0x100 (PC)
(XEN) [<000000000027bbd8>] gcov.c#gcov_reset_all_counters+0x3c/0x78 (LR)
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 3:
(XEN) CPU3: Unexpected Trap: Data Abort
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) PSCI cpu off failed for CPU0 err=-3
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

Thanks

On Thu, May 2, 2019 at 6:17 PM Julien Grall <julien.grall@xxxxxxx> wrote:
>
> Hi,
>
> On 5/2/19 3:50 PM, Viktor Mitin wrote:
> > Adding Xen maintainers to this email CC.
> >
> > Thanks
> >
> > On Thu, May 2, 2019 at 5:08 PM Viktor Mitin <viktor.mitin.19@xxxxxxxxx> 
> > wrote:
> >>
> >> Hi All,
> >>
> >> Please be aware that we have tried Xen ARM64 build with
> >> CONFIG_COVERAGE feature enabled. The build environment is next:
> >> Xen Versions tested: xen-4.12-stable, xen-4.13-staging
> >> Board: H3ULCB, R-Car H3 Ver.2.0
> >> Poky: Yocto Project Reference Distro 2.4.2
> >> Compiler: aarch64-poky-linux-gcc (Linaro GCC 7.2-2017.11) 7.2.1
> >>
> >> Both Xen versions (4.12 and staging) return "Unexpected Trap: Data
> >> Abort" issue in case of 'xencov reset' or 'xencov read' calls:
> >>
> >> root@h3ulcb:~# xencov reset
> >> (XEN) Data Abort Trap. Syndrome=0x7
>
> Per the value, the syndrome is invalid. As I will not open a zip (see
> below why), could you post the full stack trace?
>
> >> (XEN) Walking Hypervisor VA 0x361700 on CPU3 via TTBR 0x0000000078266000
> >> (XEN) 0TH[0x0] = 0x0000000078265f7f
> >> (XEN) 1ST[0x0] = 0x0000000078262f7f
> >> (XEN) 2ND[0x1] = 0x004000007825ff7f
> >> (XEN) 3RD[0x161] = 0x00600000781e1f7e
> >> (XEN) CPU3: Unexpected Trap: Data Abort
> >>
> >> Attaching the next log files (zipped in
> >> xen_with_config_coverage_logs.zip) with the details:
>
> Please don't send a 54KB attachment on the mailing list. This is using
> up space for every one on the ML. Instead you should upload somewhere
> (e.g pastebin).
>
> But I am afraid, I am not going to open any archive sent on the mailing
> list. Please upload file separately. However....
>
> >> - all the run-time exception details (rcarh3_config_coverage_trap.log);
> >> - xen package build log file with compilation options (compilation.log);
>
> This is not necessary.
>
> >> - xen hypervisor .config file used for the build (xen_dot_config.log);
> >>
> >> Please share any comments or ideas about the issue.
>
> GCOV on Arm has never been tested. So it might be possible there might
> be some issues with it.
>
> Cheers,
>
> --
> Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel