Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > On Tue, Sep 13, 2016 at 02:51:27AM -0700, kernelci.org bot wrote: >> stable-rc boot: 279 boots: 6 failed, 270 passed with 3 offline (v4.7.3-60-ga08095be00af) >> >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.7.3-60-ga08095be00af/ >> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.7.3-60-ga08095be00af/ >> >> Tree: stable-rc >> Branch: local/linux-4.7.y >> Git Describe: v4.7.3-60-ga08095be00af >> Git Commit: a08095be00af2d23f2d79ebcfc20a5b5937acb9f >> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 58 unique boards, 17 SoC families, 28 builds out of 205 >> >> Boot Failures Detected: https://kernelci.org/boot/?v4.7.3-60-ga08095be00af&fail >> >> arm64: >> >> defconfig+CONFIG_LKDTM=y: >> qemu-aarch64,legacy: 1 failed lab >> >> defconfig+CONFIG_EXPERT=y+CONFIG_ACPI=y: >> qemu-aarch64,legacy: 1 failed lab >> >> defconfig+CONFIG_OF_UNITTEST=y: >> qemu-aarch64,legacy: 1 failed lab >> >> defconfig: >> qemu-aarch64,legacy: 1 failed lab >> >> defconfig+CONFIG_RANDOMIZE_BASE=y: >> qemu-aarch64,legacy: 1 failed lab >> These are due to a QEMU version problem and this lab needs a QEMU upgrade. You can ignore for now. >> arm: >> >> exynos_defconfig: >> exynos5422-odroidxu3_rootfs:nfs: 1 failed lab > > Any easy way for me to see what failed with these? > > I looked at the exynos failure, and it looks like the device booted just > fine, but no networking showed up. Is that a correct diagnosis? Yeah, looks like it. This is looking like something that we've seen before on exynos. I'll ask the owners of that lab/board to have a closer look. I'll let you know there's a real regression here. Kevin -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html