Buildresult: powerpc-next/ppc64le_defconfig+NO_KPROBES/powerpc-gcc5 built on Nov 16 2019, 01:27

kisskb

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

Status:	OK
Date/Time:	Nov 16 2019, 01:27
Duration:	0:01:40.179850
Builder:	ka4
Revision:	powerpc/powernv: Disable native PCIe port management (`942523fd67563ea677cc03fc97635893d4350749)`
Target:	powerpc-next/ppc64le_defconfig+NO_KPROBES/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_KPROBES (download)
Log:	Download original Possible warnings (3) include/linux/kernel.h:37:33: warning: 'clone_src_i_size' may be used uninitialized in this function [-Wmaybe-uninitialized] WARNING: vmlinux.o(.text+0x31e4): 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 942523fd67563ea677cc03fc97635893d4350749^{commit} 942523fd67563ea677cc03fc97635893d4350749 already have revision, skipping fetch # git checkout -q -f -B kisskb 942523fd67563ea677cc03fc97635893d4350749 # git clean -qxdf # < git log -1 # commit 942523fd67563ea677cc03fc97635893d4350749 # Author: Oliver O'Halloran <oohall@gmail.com> # Date: Wed Nov 13 20:40:35 2019 +1100 # # powerpc/powernv: Disable native PCIe port management # # On PowerNV the PCIe topology is (currently) managed by the powernv # platform code in cooperation with firmware. The PCIe-native service # drivers bypass both and this can cause problems. # # Historically this hasn't been a big deal since the only port service # driver that saw much use was the AER driver. The AER driver relies on # a kernel service to report when errors occur rather than acting # autonomously so it's fairly easy to ignore. On PowerNV (and pseries) # AER events are handled through EEH, which ignores the AER service, so # it's never been an issue. # # Unfortunately, the hotplug port service driver (pciehp) does act # autonomously and conflicts with the platform specific hotplug # driver (pnv_php). The main issue is that pciehp claims the interrupt # associated with the PCIe capability which in turn prevents pnv_php # from claiming it. # # This results in hotplug events being handled by pciehp which does not # notify firmware when the PCIe topology changes, and does not # setup/teardown the arch specific PCI device structures (pci_dn) when # the topology changes. The end result is that hot-added devices cannot # be enabled and hot-removed devices may not be fully torn-down on # removal. # # We can fix these problems by setting the "pcie_ports_disabled" flag # during platform initialisation. The flag indicates the platform owns # the PCIe ports which stops the portbus driver from being registered. # # Fixes: 66725152fb9f ("PCI/hotplug: PowerPC PowerNV PCI hotplug driver") # Signed-off-by: Oliver O'Halloran <oohall@gmail.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # Link: https://lore.kernel.org/r/20191113094035.22394-1-oohall@gmail.com # < /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 942523fd67563ea677cc03fc97635893d4350749 # < make -s -j 120 ARCH=powerpc O=/kisskb/build/powerpc-next_ppc64le_defconfig+NO_KPROBES_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- ppc64le_defconfig # Added to kconfig CONFIG_KPROBES=n # yes \n \| make -s -j 120 ARCH=powerpc O=/kisskb/build/powerpc-next_ppc64le_defconfig+NO_KPROBES_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 120 ARCH=powerpc O=/kisskb/build/powerpc-next_ppc64le_defconfig+NO_KPROBES_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- In file included from /kisskb/src/include/linux/list.h:9:0, from /kisskb/src/include/linux/wait.h:7, from /kisskb/src/include/linux/wait_bit.h:8, from /kisskb/src/include/linux/fs.h:6, from /kisskb/src/fs/btrfs/send.c:7: /kisskb/src/fs/btrfs/send.c: In function 'process_extent': /kisskb/src/include/linux/kernel.h:37:33: warning: 'clone_src_i_size' may be used uninitialized in this function [-Wmaybe-uninitialized] #define IS_ALIGNED(x, a) (((x) & ((typeof(x))(a) - 1)) == 0) ^ /kisskb/src/fs/btrfs/send.c:5088:6: note: 'clone_src_i_size' was declared here u64 clone_src_i_size; ^ WARNING: vmlinux.o(.text+0x31e4): 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_KPROBES_ppc64le-gcc5 # Build took: 0:01:40.179850

© Michael Ellerman 2006-2018.