Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp707546ybp; Fri, 11 Oct 2019 03:06:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqx6ogTQKPjAlcvbtpKnvoVvN8SzR41Gajf4qfmHSHAJDbQQHb1aLNB0mq6xRnLEM/WCtMt7 X-Received: by 2002:a17:906:cc90:: with SMTP id oq16mr12726195ejb.322.1570788386949; Fri, 11 Oct 2019 03:06:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570788386; cv=none; d=google.com; s=arc-20160816; b=ijm2k7uKcoLPh2AaYUMylCxx+lsz1rVzMDnZE2jkNyqDWr+/09V6e/5fcta2lgYda9 q/pOGqlHMh3WOWW/bcjMIxdr2an8wJcfRAGMwIq1AqBFzgBlK1bb5fl4cbw/qBalrBpN gAVY+Bxp/oH4LhWd2k0xcUnPNIAjradwTdX2xjWLNl5Vk+t+oLNg6xHsYO458iLA46oT s6UFVjs15vKtV6jYyOFRjKtxcv/u/HhjVdkRxMJr13lPd7STL2NVeRqoPe+drK5AioOw ZgRdV4MNUaHUfTEtABJNA0d/iPRA7zbV/hNbMicFTxGHJT6K9EP5JJeFWMNjzP/6rM4c 58yg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=AOrj24bNmQQFagvCAkAdHKLc6FVHDT1nVhXVmJ+HAVA=; b=bqgTE3Au9I6S3CYTSGfmuunDYv3fss0v4FYfERX8TvJHNhNk7oYFd2c3bNJILhRoN9 jDrNS7CSMFCDQLQO+s8pLQi/0+Ghc1n/j1uBMWx32tQcV99MnxpG3NOPuHpb88E28NJ9 y4oxy6Qvqdt+ZL+bhIlJpW25cFYadiJ8prycoe3MIf1nuujT4JKi4nm2by/wuuUbQwkV t2W1yNphEhVHyfBfw1KRpvJ8olqvOFjxkGrSRqBjxnTEfT7GGRtTMXXOmk6zgS7+hxZ6 L9kQXeX1sqOfd7CTaMH8uIZQVM56V71IbYkkEvQPFAfbzHUMLqcfh1VLi6pUZLlfYjL0 44ug== 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 k14si5484332ede.421.2019.10.11.03.06.02; Fri, 11 Oct 2019 03:06:26 -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 S1727653AbfJKKFn (ORCPT + 99 others); Fri, 11 Oct 2019 06:05:43 -0400 Received: from foss.arm.com ([217.140.110.172]:55194 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726808AbfJKKFm (ORCPT ); Fri, 11 Oct 2019 06:05:42 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D4EAF337; Fri, 11 Oct 2019 03:05:41 -0700 (PDT) Received: from bogus (e107155-lin.cambridge.arm.com [10.1.196.42]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B43803F703; Fri, 11 Oct 2019 03:05:40 -0700 (PDT) Date: Fri, 11 Oct 2019 11:05:31 +0100 From: Sudeep Holla To: Marek Szyprowski Cc: linux-arm-kernel@lists.infradead.org, Liviu Dudau , Lorenzo Pieralisi , LKML , Catalin Marinas , Will Deacon , Sudeep Holla Subject: Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure Message-ID: <20191011100521.GA5122@bogus> References: <33a83dce-e9f0-7814-923b-763d33e70257@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <33a83dce-e9f0-7814-923b-763d33e70257@samsung.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marek, On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: > Hi > > Recently I've got access to ARM Juno R1 board and did some tests with > current mainline kernel on it. I'm a bit surprised that enabling > CONFIG_PROVE_LOCKING causes a boot failure on this board. After enabling > this Kconfig option, I get no single message from the kernel, although I > have earlycon enabled. > I don't have Juno R1 but I tried defconfig + CONFIG_PROVE_LOCKING and it boots fine. So if you disable CONFIG_PROVE_LOCKING(i.e. defconfig) boots fine ? Are you using DTB from the mainline ? > I've did my test with default defconfig and current linux-next, > v5.4-rc1, v5.3 and v4.19. In all cases the result is the same. I'm > booting kernel using a precompiled uboot from Linaro release and TFTP > download. > OK, I use UEFI+GRUB but I don't think that should cause any issue. > Is this a known issue? Other ARM64 boards I have access to (Samsung TM2e > and RaspberryPi3) boots fine with the same kernel image. > Not that I am aware of. If you could send me the bootlog with defconfig I can take a look and see if I get any clue. -- Regards, Sudeep