Buildresult: powerpc-next/arm64-defconfig/arm64-gcc5 built on Nov 16 2019, 00:45

kisskb

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

Status:	OK
Date/Time:	Nov 16 2019, 00:45
Duration:	0:05:43.418529
Builder:	blade4b
Revision:	powerpc/powernv: Disable native PCIe port management (`942523fd67563ea677cc03fc97635893d4350749)`
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 (3) include/linux/kernel.h:37:33: warning: 'clone_src_i_size' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] include/linux/spinlock.h:288:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] 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/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 942523fd67563ea677cc03fc97635893d4350749 # < make -s -j 24 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 24 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:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:38: LSE atomics not supported by binutils arch/arm64/Makefile:62: CROSS_COMPILE_COMPAT not defined or empty, the compat vDSO will not be built 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; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c: In function 'sh_mobile_i2c_isr': /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] pd->msg->buf[real_pos] = data; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:372:16: note: 'data' was declared here unsigned char data; ^ In file included from /kisskb/src/include/linux/rwsem.h:16:0, from /kisskb/src/include/linux/notifier.h:15, from /kisskb/src/include/linux/clk.h:14, from /kisskb/src/drivers/tty/serial/sh-sci.c:24: /kisskb/src/drivers/tty/serial/sh-sci.c: In function 'sci_dma_rx_submit': /kisskb/src/include/linux/spinlock.h:288:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] _raw_spin_unlock_irqrestore(lock, flags); \ ^ /kisskb/src/drivers/tty/serial/sh-sci.c:1351:16: note: 'flags' was declared here unsigned long flags; ^ Completed OK # rm -rf /kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 # Build took: 0:05:43.418529

© Michael Ellerman 2006-2018.