[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <33a83dce-e9f0-7814-923b-763d33e70257@samsung.com>
Date: Fri, 11 Oct 2019 11:26:04 +0200
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: linux-arm-kernel@...ts.infradead.org
Cc: Liviu Dudau <liviu.dudau@....com>,
Sudeep Holla <sudeep.holla@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
LKML <linux-kernel@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>
Subject: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure
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'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.
Is this a known issue? Other ARM64 boards I have access to (Samsung TM2e
and RaspberryPi3) boots fine with the same kernel image.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Powered by blists - more mailing lists