Buildresult: powerpc-next/arm64-defconfig/arm64-gcc5 built on Jul 29 2020, 00:59

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jul 29 2020, 00:59
Duration:	0:05:44.384784
Builder:	ka3
Revision:	ppc64/kexec_file: fix kexec load failure with lack of memory hole (`eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f)`
Target:	powerpc-next/arm64-defconfig/arm64-gcc5
Branch:	powerpc-next
Compiler:	arm64-gcc5 (aarch64-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0 / GNU ld (GNU Binutils) 2.25.1)
Config:	defconfig (download)
Log:	Download original Possible warnings (8) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) arch/arm64/boot/dts/qcom/ipq6018.dtsi:127.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/qcom/ipq6018.dtsi:127.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) Full Log # git rev-parse -q --verify eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f^{commit} # git fetch -q -n -f git://gitlab.ozlabs.ibm.com/linuxppc/linux.git next-test # git rev-parse -q --verify eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f^{commit} eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # git checkout -q -f -B kisskb eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # git clean -qxdf # < git log -1 # commit eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # Author: Hari Bathini <hbathini@linux.ibm.com> # Date: Mon Jul 27 01:10:28 2020 +0530 # # ppc64/kexec_file: fix kexec load failure with lack of memory hole # # The kexec purgatory has to run in real mode. Only the first memory # block maybe accessible in real mode. And, unlike the case with panic # kernel, no memory is set aside for regular kexec load. Another thing # to note is, the memory for crashkernel is reserved at an offset of # 128MB. So, when crashkernel memory is reserved, the memory ranges to # load kexec segments shrink further as the generic code only looks for # memblock free memory ranges and in all likelihood only a tiny bit of # memory from 0 to 128MB would be available to load kexec segments. # # With kdump being used by default in general, kexec file load is likely # to fail almost always. This can be fixed by changing the memory hole # lookup logic for regular kexec to use the same method as kdump. This # would mean that most kexec segments will overlap with crashkernel # memory region. That should still be ok as the pages, whose destination # address isn't available while loading, are placed in an intermediate # location till a flush to the actual destination address happens during # kexec boot sequence. # # Signed-off-by: Hari Bathini <hbathini@linux.ibm.com> # Tested-by: Pingfan Liu <piliu@redhat.com> # Reviewed-by: Thiago Jung Bauermann <bauerman@linux.ibm.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # Link: https://lore.kernel.org/r/159579242226.5790.13933486642004084417.stgit@hbathini # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # < make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- defconfig # < make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- help # make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- olddefconfig # make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- arch/arm64/Makefile:26: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:34: LSE atomics not supported by binutils /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/qcom/ipq6018.dtsi:127.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/qcom/ipq6018.dtsi:127.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) Completed OK # rm -rf /kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 # Build took: 0:05:44.384784

© Michael Ellerman 2006-2018.