From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751901AbdLAA3r (ORCPT ); Thu, 30 Nov 2017 19:29:47 -0500 Received: from mail-pf0-f169.google.com ([209.85.192.169]:46510 "EHLO mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125AbdLAA3p (ORCPT ); Thu, 30 Nov 2017 19:29:45 -0500 X-Google-Smtp-Source: AGs4zMYH7EqeFHUMTCpp35IQ9PcoWvDhAmgkrioBaZwYgpKHt70Sdj08tOoauVJ1Z7NPWCjd6o4M5g== 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, shuahkh@osg.samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org, stable@vger.kernel.org, kernelci@free-electrons.com Subject: Re: [PATCH 4.14 000/193] 4.14.3-stable review Organization: BayLibre References: <20171128100613.638270407@linuxfoundation.org> <5a1d7f8d.89ce1c0a.19604.d3a7@mx.google.com> <20171128155257.GA9556@kroah.com> Date: Thu, 30 Nov 2017 16:29:31 -0800 In-Reply-To: <20171128155257.GA9556@kroah.com> (Greg Kroah-Hartman's message of "Tue, 28 Nov 2017 16:52:57 +0100") Message-ID: <7hbmjjuw7o.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, Nov 28, 2017 at 07:23:57AM -0800, kernelci.org bot wrote: >> stable-rc/linux-4.14.y boot: 239 boots: 11 failed, 197 passed with 31 offline (v4.14.2-194-g9ff910a1edbf) >> >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.2-194-g9ff910a1edbf/ >> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.2-194-g9ff910a1edbf/ >> >> Tree: stable-rc >> Branch: linux-4.14.y >> Git Describe: v4.14.2-194-g9ff910a1edbf >> Git Commit: 9ff910a1edbfe3044963b615a4fb2d29f611579d >> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 94 unique boards, 24 SoC families, 21 builds out of 189 >> >> Boot Regressions Detected: >> >> arm: >> >> at91_dt_defconfig: >> at91rm9200ek_rootfs:nfs: >> lab-free-electrons: failing since 1 day (last pass: v4.14.2 - first fail: v4.14.2-181-g684cdd60a58a) >> >> sunxi_defconfig: >> sun5i-gr8-chip-pro: >> lab-free-electrons: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> >> arm64: >> >> defconfig: >> meson-gxl-s905d-p230: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> meson-gxl-s905x-khadas-vim: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> meson-gxl-s905x-nexbox-a95x: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> meson-gxl-s905x-p212: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> >> defconfig+CONFIG_LKDTM=y: >> meson-gxl-s905d-p230: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> meson-gxl-s905x-khadas-vim: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) >> meson-gxl-s905x-p212: >> lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a) > > That's a lot of new failures, did I break something? > Nope, most of it was a lab config in my lab. One of the patches I requested for stable added a reserved memory region which conflicted with how my lab was loading the initrd, causing all of those meson-* failures in my lab. As Mark pointed out, a subsequent linux-4.14.y build booted fine on all those boards. The lab-free-electrons failures aren't now, and they (now Cc'd) are looking into those (I hope.) Kevin