Buildresult: powerpc-next/ppc64le_defconfig+NO_KVM/powerpc-gcc5 built on Feb 14 2020, 02:01

kisskb

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

Status:	OK
Date/Time:	Feb 14 2020, 02:01
Duration:	0:03:00.287775
Builder:	ka1
Revision:	powerpc/xmon: Lower limits on nidump and ndump (`8e9ad2720cd1cf55530755362ad899f69e09fb9a)`
Target:	powerpc-next/ppc64le_defconfig+NO_KVM/powerpc-gcc5
Branch:	powerpc-next
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	ppc64le_defconfig+NO_KVM (download)
Log:	Download original Possible warnings (2) WARNING: vmlinux.o(.text+0x31d4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() WARNING: vmlinux.o(.text+0x33c8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() Full Log # git rev-parse -q --verify 8e9ad2720cd1cf55530755362ad899f69e09fb9a^{commit} 8e9ad2720cd1cf55530755362ad899f69e09fb9a already have revision, skipping fetch # git checkout -q -f -B kisskb 8e9ad2720cd1cf55530755362ad899f69e09fb9a # git clean -qxdf # < git log -1 # commit 8e9ad2720cd1cf55530755362ad899f69e09fb9a # Author: Michael Ellerman <mpe@ellerman.id.au> # Date: Wed Feb 12 22:11:00 2020 +1100 # # powerpc/xmon: Lower limits on nidump and ndump # # In xmon we have two variables that are used by the dump commands. # There's ndump which is the number of bytes to dump using 'd', and # nidump which is the number of instructions to dump using 'di'. # # ndump starts as 64 and nidump starts as 16, but both can be set by the # user. # # It's fairly common to be pasting addresses into xmon when trying to # debug something, and if you inadvertently double paste an address like # so: # # 0:mon> di c000000002101f6c c000000002101f6c # # The second value is interpreted as the number of instructions to dump. # # Luckily it doesn't dump 13 quintrillion instructions, the value is # limited to MAX_DUMP (128K). But as each instruction is dumped on a # single line, that's still a lot of output. If you're on a slow console # that can take multiple minutes to print. If you were "just popping in # and out of xmon quickly before the RCU/hardlockup detector fires" you # are now having a bad day. # # Things are not as bad with 'd' because we print 16 bytes per line, so # it's fewer lines. But it's still quite a lot. # # So shrink the maximum for 'd' to 64K (one page), which is 4096 lines. # For 'di' add a new limit which is the above / 4 - because instructions # are 4 bytes, meaning again we can dump one page. # # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 8e9ad2720cd1cf55530755362ad899f69e09fb9a # < make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_ppc64le_defconfig+NO_KVM_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- ppc64le_defconfig # Added to kconfig CONFIG_KVM_BOOK3S_64=n # Added to kconfig CONFIG_KVM=n # yes \n \| make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_ppc64le_defconfig+NO_KVM_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- oldconfig yes: standard output: Broken pipe # make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_ppc64le_defconfig+NO_KVM_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- WARNING: vmlinux.o(.text+0x31d4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() The function __boot_from_prom() references the function __init prom_init(). This is often because __boot_from_prom lacks a __init annotation or the annotation of prom_init is wrong. WARNING: vmlinux.o(.text+0x33c8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. Completed OK # rm -rf /kisskb/build/powerpc-next_ppc64le_defconfig+NO_KVM_ppc64le-gcc5 # Build took: 0:03:00.287775

© Michael Ellerman 2006-2018.