Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751341AbdISFu5 (ORCPT ); Tue, 19 Sep 2017 01:50:57 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:53466 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750867AbdISFuz (ORCPT ); Tue, 19 Sep 2017 01:50:55 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org D1F996028B Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=sboyd@codeaurora.org Date: Mon, 18 Sep 2017 22:50:37 -0700 From: Stephen Boyd To: Kevin Hilman Cc: Greg Kroah-Hartman , "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, stable@vger.kernel.org, andy.gross@linaro.org Subject: Re: [PATCH 4.4 00/31] 4.4.88-stable review Message-ID: <20170919055037.GH3349@codeaurora.org> References: <20170912165247.436880944@linuxfoundation.org> <59b8666e.cd5e1c0a.73fbf.2682@mx.google.com> <20170913010318.GB22427@kroah.com> <7hshfqdzyj.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7hshfqdzyj.fsf@baylibre.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2208 Lines: 53 On 09/13, Kevin Hilman wrote: > Greg Kroah-Hartman writes: > > > On Tue, Sep 12, 2017 at 03:57:50PM -0700, kernelci.org bot wrote: > >> stable-rc/linux-4.4.y boot: 450 boots: 1 failed, 446 passed with 3 offline (v4.4.87-32-gb8c205d85576) > >> > >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ > >> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ > >> > >> Tree: stable-rc > >> Branch: linux-4.4.y > >> Git Describe: v4.4.87-32-gb8c205d85576 > >> Git Commit: b8c205d855764e3db05a17ab4d03a19a5d609bdd > >> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> Tested: 68 unique boards, 21 SoC families, 34 builds out of 203 > >> > >> Boot Regressions Detected: > >> > >> arm: > >> > >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > >> qcom-apq8064-cm-qs600: > >> lab-baylibre-seattle: new failure (last pass: v4.4.85-16-gcd99a4f3f43b) > > > > Is this a real failure? > > I tried to boot this a few more times, and it's still failing so it > apprears it's a new regression. > > Added qcom maintainenrs to Cc to see if they have any ideas. > > These failures with CONFIG_PROVE_LOCKING seem to be more often related > to bootloader issues with kernel size than actual CONFIG_PROVE_LOCKING, > so I'm note exactly sure which is which here. > Usually when the kernel becomes too large we don't see any output on the console at all. That's because the decompressor overwrites something like the dtb or the initrd when it uncompresses the kernel and then serial console can't be found. In this case, it looks like it booted up and then got stuck when trying to run /init from the ramdisk? Or maybe it got stuck in some interrupt storm with mmc? There are some regulator warnings that seem to be ignored earlier for the mmc. [ 2.252965] s4: voltage operation not allowed [ 2.258505] mmci-pl18x 12400000.sdcc: Voltage switch failed No idea if that forebodes doom though. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project