|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [ovmf test] 124074: regressions - FAIL
flight 124074 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/124074/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt 6 libvirt-build fail REGR. vs. 124058 version targeted for testing: ovmf 0b37c75e6944f3d3ded7bef1e10cf4df72386616 baseline version: ovmf a05a8a5aa17da4bc7144706a9931d68beec1a61f Last test of basis 124058 2018-06-11 03:10:30 Z 0 days Testing same since 124074 2018-06-11 16:41:40 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Benjamin You <benjamin.you@xxxxxxxxx> Dandan Bi <dandan.bi@xxxxxxxxx> Derek Lin <derek.lin2@xxxxxxx> Laszlo Ersek <lersek@xxxxxxxxxx> Michael Zimmermann <sigmaepsilon92@xxxxxxxxx> Yonghong Zhu <yonghong.zhu@xxxxxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt pass build-i386-libvirt fail build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 0b37c75e6944f3d3ded7bef1e10cf4df72386616 Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Sun Jun 10 20:03:35 2018 +0200 ArmVirtPkg: switch to KVM safe IoLib implementation Switch to the new IoLib implementation that will only use KVM safe instructions to perform MMIO memory accesses. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Leif Lindholm <leif.lindholm@xxxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> commit 4134f2bddcb68d2e20ed000cdf54abf3f1140904 Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Thu Jun 7 12:44:12 2018 +0200 MdePkg/BaseIoLibIntrinsic: make BaseIoLibIntrinsic safe for ArmVirt/KVM KVM on ARM refuses to decode load/store instructions used to perform I/O to emulated devices, and instead relies on the exception syndrome information to describe the operand register, access size, etc. This is only possible for instructions that have a single input/output register (as opposed to ones that increment the offset register, or load/store pair instructions, etc). Otherwise, QEMU crashes with the following error error: kvm run failed Function not implemented R00=01010101 R01=00000008 R02=00000048 R03=08000820 R04=00000120 R05=7faaa0e0 R06=7faaa0dc R07=7faaa0e8 R08=7faaa0ec R09=7faaa088 R10=000000ff R11=00000080 R12=ff000000 R13=7fccfe08 R14=7faa835f R15=7faa887c PSR=800001f3 N--- T svc32 QEMU: Terminated and KVM produces a warning such as the following in the kernel log kvm [17646]: load/store instruction decoding not implemented The IoLib implementation provided by MdePkg/Library/BaseIoLibIntrinsic is based on C code, and when LTO is in effect, the MMIO accesses could be merged with, e.g., manipulations of the loop counter, producing opcodes that KVM does not support for emulated MMIO. So let's add a special ArmVirt flavor of this library that implements that actual load/store operations in assembler, ensuring that the instructions involved can be emulated by KVM. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Leif Lindholm <leif.lindholm@xxxxxxxxxx> Acked-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx> commit 5163d89398c541ab03e8f6f6ab6ed479e95b4be9 Author: Derek Lin <derek.lin2@xxxxxxx> Date: Wed May 9 17:03:21 2018 +0800 BaseTools: Remove dsc nested include checking. The dsc nested include checking make unexpected build error when building project A and switch to project B. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Derek Lin <derek.lin2@xxxxxxx> Reviewed-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx> commit a683ceca800e9d10c999d463444aa92945be0a70 Author: Michael Zimmermann <sigmaepsilon92@xxxxxxxxx> Date: Thu Jun 7 07:47:20 2018 +0200 ArmPkg/CompilerIntrinsicsLib: fix GCC8 warning for __aeabi_memcpy aliases This was the warning (shown for __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8): ArmPkg/Library/CompilerIntrinsicsLib/memcpy.c:42:6: error: '__aeabi_memcpy8' alias between functions of incompatible types 'void(void*, const void *, size_t)' {aka 'void(void *, const void *, unsigned int)'} and 'void *(void *, const void *, size_t)' {aka 'void *(void *, const void *, unsigned int)'} [-Werror=attribute-alias] void __aeabi_memcpy8(void *dest, const void *src, size_t n); ArmPkg/Library/CompilerIntrinsicsLib/memcpy.c:19:7: note: aliased declaration here void *__memcpy(void *dest, const void *src, size_t n) The problem is the different return type (void vs void*). So reshuffle the code so the prototypes match between the aliases. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Michael Zimmermann <sigmaepsilon92@xxxxxxxxx> [ardb: change prototype of internal __memcpy() and drop extra wrapper] Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> commit 9dca2105ad960c9946d7cc2ece40f65e1999dac7 Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Thu Jun 7 11:06:47 2018 +0200 MdeModulePkg/EmmcDxe: demote DEBUG print to DEBUG_BLKIO Lower the priority of the DEBUG print in EmmcReadWrite(), which is emitted for each read or write operation to the eMMC device, which clutters up the log output of builds created with DEBUG_INFO enabled. Suggested-by: Pipat Methavanitpong <methavanitpong.pipat@xxxxxxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> commit 271d8cd7df0c346f19803938d98fe7cbb7b63be4 Author: Benjamin You <benjamin.you@xxxxxxxxx> Date: Mon Jun 4 11:23:21 2018 +0800 CorebootModulePkg/CbSupportDxe: Remove SCI_EN setting Current implemenation sets PM1_CNT.SCI_EN bit at ReadyToBoot event. However, this should not be done because this causes OS to skip triggering FADT.SMI_CMD, which leads to the functions implemented in the SMI handler being omitted. This issue was identified by Matt Delco <delco@xxxxxxxxxx>. The fix does the following: - The SCI_EN bit setting is removed from CbSupportDxe driver. - Some additional checks are added in CbParseFadtInfo() in CbParseLib.c to output some error message and ASSERT (FALSE) if ALL of the following conditions are met: 1) HARDWARE_REDUCED_ACPI is not set; 2) SMI_CMD field is zero; 3) SCI_EN bit is zero; which indicates the ACPI enabling status is inconsistent: SCI is not enabled but the ACPI table does not provide a means to enable it through FADT->SMI_CMD. This may cause issues in OS. Cc: Maurice Ma <maurice.ma@xxxxxxxxx> Cc: Prince Agyeman <prince.agyeman@xxxxxxxxx> Cc: Matt Delco <delco@xxxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Benjamin You <benjamin.you@xxxxxxxxx> Reviewed-by: Maurice Ma <maurice.ma@xxxxxxxxx> Reviewed-by: Matt Delco <delco@xxxxxxxxxx> commit f75c7478280b96d191e86856c0b1c49ff711c284 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Tue Jun 5 09:20:05 2018 +0800 ShellPkg/UefiShellAcpiViewCommandLib: Fix ECC issues 1. Separate variable definition and initialization. 2. Make the variable naming following Edk2 rule. V2: Remove the updates of guard macros in header files. Cc: Sami Mujawar <sami.mujawar@xxxxxxx> Cc: Evan Lloyd <evan.lloyd@xxxxxxx> Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx> Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit a6eaba4d7f23262ab8e8502b476bdf5249a54ad4 Author: Dandan Bi <dandan.bi@xxxxxxxxx> Date: Mon Jun 4 09:14:51 2018 +0800 ShellPkg/UefiShellAcpiViewCommandLib: Fix ECC issues Make the function comments follow EDK2 coding style. Cc: Sami Mujawar <sami.mujawar@xxxxxxx> Cc: Evan Lloyd <evan.lloyd@xxxxxxx> Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx> Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit 64285f15264906c761b5a6772b5b590b32caa03c Author: Yonghong Zhu <yonghong.zhu@xxxxxxxxx> Date: Thu Jun 7 13:06:44 2018 +0800 BaseTools/UPT: Update the import statement to use StringUtils The patch 5a57246eab80 Rename String to StringUtils, but it didn't update the UPT Tool for the import statement which cause UPT tool break. Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx> Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |