From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759466AbcIMRku (ORCPT ); Tue, 13 Sep 2016 13:40:50 -0400 Received: from mail-pa0-f42.google.com ([209.85.220.42]:36849 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754771AbcIMRks (ORCPT ); Tue, 13 Sep 2016 13:40:48 -0400 From: Kevin Hilman To: Greg Kroah-Hartman Cc: "kernelci.org bot" , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah.kh@samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, stable@vger.kernel.org Subject: Re: [PATCH 4.7 00/59] 4.7.4-stable review Organization: BayLibre References: <20160912152128.765864031@linuxfoundation.org> <57d7cc1f.0d8d1c0a.df2d3.a693@mx.google.com> <20160913121238.GB18307@kroah.com> Date: Tue, 13 Sep 2016 10:40:46 -0700 In-Reply-To: <20160913121238.GB18307@kroah.com> (Greg Kroah-Hartman's message of "Tue, 13 Sep 2016 14:12:38 +0200") Message-ID: <7hh99jofz5.fsf@baylibre.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg Kroah-Hartman 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