Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1706241yba; Fri, 17 May 2019 04:05:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqy3adLC4PXpGAE9DrqcvGaI0/e0Cr7qi8RUMUu4HeeyVrWAqO6F0Qi5O3IRjoEUvT0dr2Pl X-Received: by 2002:a62:ac0c:: with SMTP id v12mr59733422pfe.59.1558091108569; Fri, 17 May 2019 04:05:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558091108; cv=none; d=google.com; s=arc-20160816; b=w6vuIYQREGUY/UDPz+k05rEhp5qO3ilWlOfc0viCInCFkzStmG5ng2+4oExqzOb1l8 Gmg+5JEA3v9VsoSwdto6Y/QMmE+kA7lUH/MVNXelPAmc1aBNidLjKGx7xj+9W4Oo0lgR XmtHUXeEBtJTFVm/iQQfB53wRr7qhAryJzO/u+E4Smzj+qvRaDLRfUc7IbHYXKm2hUXC gehkBigFDr0hqrbug4K1sqMHinBRe3okDQsN3dc4Hax5Y6JUlJdMNrC4inPTeEQFPdRO 06MCIjw1AZRZfZZJ8G0WveHjlfP+Xns2ejqS48whYRlc+0D2dOjRfx755JiDgl1rdatW FmPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=yW2f+pvOM5ZwixtgeRRKZdV9MYgU7mi6tdpESXROrhY=; b=nge9dFKHKLj7WuvJfv+l2DuFsOBBi2mtkyyhE2fVoqt4ChirurUfJwVMFYRBd1ymDo zIjp6FTWKpSMwFT2eogymNov/5/Bm6rOJlw2LPSxDnEs8rSTyd08SB+SbwkukMr8h2Bl rrVHSWJ/ynYHeUu5M2OJF9f45xupSV90kXHViZ2yk09qmdSxGsFsGaPs7utGCPuimIkg pB1Kv3ImkC2+yWro6wBSB1RNN21wwxfU4AFYjgLa9cmSIOCrNkte2UAy5jLoyPtYvhmQ SzdE5JL9qqEv/wMibSnR+DHEBxwF2EcRExHBCI2WRyCh7ePOWW/KD1qpAB550LUf7kea HTjA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f126si7675419pgc.250.2019.05.17.04.04.53; Fri, 17 May 2019 04:05:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728808AbfEQJif (ORCPT + 99 others); Fri, 17 May 2019 05:38:35 -0400 Received: from eumx.net ([91.82.101.43]:54662 "EHLO legacy.eumx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727758AbfEQJif (ORCPT ); Fri, 17 May 2019 05:38:35 -0400 X-Greylist: delayed 1273 seconds by postgrey-1.27 at vger.kernel.org; Fri, 17 May 2019 05:38:34 EDT Subject: Re: next/master boot bisection: next-20190514 on rk3288-veyron-jaq To: Doug Anderson , "kernelci.org bot" Cc: Elaine Zhang , Daniel Lezcano , Tomeu Vizoso , Linux PM , Guillaume Tucker , mgalka@collabora.com, LKML , Eduardo Valentin , "open list:ARM/Rockchip SoC..." , Mark Brown , matthew.hart@linaro.org, Kevin Hilman , Enric Balletbo i Serra , Zhang Rui , Matthias Kaehlcke , Linux ARM , Heiko Stuebner References: <5cdae78b.1c69fb81.a32a9.870f@mx.google.com> From: Jack Mitchell Message-ID: Date: Fri, 17 May 2019 10:17:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-BW Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16/05/2019 22:38, Doug Anderson wrote: > Hi, > > From: kernelci.org bot > Date: Tue, May 14, 2019 at 9:06 AM > To: , , > , , > , , > , Elaine Zhang, Eduardo Valentin, Daniel > Lezcano > Cc: Heiko Stuebner, , > , , > Zhang Rui, > >> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >> * This automated bisection report was sent to you on the basis * >> * that you may be involved with the breaking commit it has * >> * found. No manual investigation has been done to verify it, * >> * and the root cause of the problem may be somewhere else. * >> * Hope this helps! * >> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * >> >> next/master boot bisection: next-20190514 on rk3288-veyron-jaq >> >> Summary: >> Start: 0a13f187b16a Add linux-next specific files for 20190514 >> Details: https://kernelci.org/boot/id/5cda7f2259b514876d7a3628 >> Plain log: https://storage.kernelci.org//next/master/next-20190514/arm/multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y/gcc-8/lab-collabora/boot-rk3288-veyron-jaq.txt >> HTML log: https://storage.kernelci.org//next/master/next-20190514/arm/multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y/gcc-8/lab-collabora/boot-rk3288-veyron-jaq.html >> Result: 691d4947face thermal: rockchip: fix up the tsadc pinctrl setting error >> >> Checks: >> revert: PASS >> verify: PASS >> >> Parameters: >> Tree: next >> URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git >> Branch: master >> Target: rk3288-veyron-jaq >> CPU arch: arm >> Lab: lab-collabora >> Compiler: gcc-8 >> Config: multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y >> Test suite: boot >> >> Breaking commit found: >> >> ------------------------------------------------------------------------------- >> commit 691d4947faceb8bd841900049e07c81c95ca4b0d >> Author: Elaine Zhang >> Date: Tue Apr 30 18:09:44 2019 +0800 >> >> thermal: rockchip: fix up the tsadc pinctrl setting error >> >> Explicitly use the pinctrl to set/unset the right mode >> instead of relying on the pinctrl init mode. >> And it requires setting the tshut polarity before select pinctrl. >> >> When the temperature sensor mode is set to 0, it will automatically >> reset the board via the Clock-Reset-Unit (CRU) if the over temperature >> threshold is reached. However, when the pinctrl initializes, it does a >> transition to "otp_out" which may lead the SoC restart all the time. >> >> "otp_out" IO may be connected to the RESET circuit on the hardware. >> If the IO is in the wrong state, it will trigger RESET. >> (similar to the effect of pressing the RESET button) >> which will cause the soc to restart all the time. >> >> Signed-off-by: Elaine Zhang >> Reviewed-by: Daniel Lezcano >> Signed-off-by: Eduardo Valentin > > I can confirm that the above commit breaks my jerry, though I haven't > dug into the details. :( Is anyone fixing? For now I'm just booting > with the revert. > > > -Doug I can also confirm that this breaks boot on our custom board which is very similar to the rk3288-Firefly. In my scenario the processor just seems to "hang", no reset occurs if that helps debug matters. Regards, Jack. > > _______________________________________________ > Linux-rockchip mailing list > Linux-rockchip@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-rockchip >