Buildresult: powerpc-next/s390-defconfig/s390x-gcc8 built on Nov 16 2019, 01:56

kisskb

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

Status:	OK
Date/Time:	Nov 16 2019, 01:56
Duration:	0:02:28.955356
Builder:	ka4
Revision:	powerpc/powernv: Disable native PCIe port management (`942523fd67563ea677cc03fc97635893d4350749)`
Target:	powerpc-next/s390-defconfig/s390x-gcc8
Branch:	powerpc-next
Compiler:	s390x-gcc8 (s390-linux-gcc (GCC) 8.1.0 / GNU ld (GNU Binutils) 2.30)
Config:	defconfig (download)
Log:	Download original No warnings found in log. 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-8.1.0-nolibc/s390-linux/bin/s390-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-8.1.0-nolibc/s390-linux/bin/s390-linux-ld --version # < git log --format=%s --max-count=1 942523fd67563ea677cc03fc97635893d4350749 # < make -s -j 120 ARCH=s390 O=/kisskb/build/powerpc-next_s390-defconfig_s390x-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/s390-linux/bin/s390-linux- defconfig # make -s -j 120 ARCH=s390 O=/kisskb/build/powerpc-next_s390-defconfig_s390x-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.1.0-nolibc/s390-linux/bin/s390-linux- Completed OK # rm -rf /kisskb/build/powerpc-next_s390-defconfig_s390x-gcc8 # Build took: 0:02:28.955356

© Michael Ellerman 2006-2018.