From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757961AbdJQAdj (ORCPT ); Mon, 16 Oct 2017 20:33:39 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:51774 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757946AbdJQAdh (ORCPT ); Mon, 16 Oct 2017 20:33:37 -0400 X-Google-Smtp-Source: ABhQp+QSuK5kCYQiSFrogtCI9iF6NQGPu8cxBIU49Q2E0oTGCfkzpBVfy2ySziu7+UJQSklZM482RA== Date: Tue, 17 Oct 2017 08:33:29 +0800 From: Leo Yan To: Mark Rutland Cc: Robin Murphy , Catalin Marinas , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, ard.biesheuvel@linaro.org Subject: Re: ARM64: Regression with commit e3067861ba66 ("arm64: add basic VMAP_STACK support") Message-ID: <20171017003329.GC19504@leoy-ThinkPad-T440> References: <20171010142725.GA24797@leoy-linaro> <20171010154558.GJ27659@leverpostej> <20171016011723.GB12470@leoy-linaro> <20171016134819.jv3udrcwsedc4cgs@lakrids.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171016134819.jv3udrcwsedc4cgs@lakrids.cambridge.arm.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 On Mon, Oct 16, 2017 at 02:48:19PM +0100, Mark Rutland wrote: > Hi Leo, > > On Mon, Oct 16, 2017 at 09:17:23AM +0800, Leo Yan wrote: > > On Tue, Oct 10, 2017 at 05:03:44PM +0100, Robin Murphy wrote: > > > On 10/10/17 16:45, Mark Rutland wrote: > > > > On Tue, Oct 10, 2017 at 10:27:25PM +0800, Leo Yan wrote: > > > >> I work mainline kernel on Hikey620 board, I find it's easily to > > > >> introduce the panic and report the log as below. So I bisect the kernel > > > >> and finally narrow down the commit e3067861ba66 ("arm64: add basic > > > >> VMAP_STACK support") which introduce this issue. > > > >> > > > >> I tried to remove 'select HAVE_ARCH_VMAP_STACK' from > > > >> arch/arm64/Kconfig, then I can see the panic issue will dismiss. So > > > >> could you check this and have insight for this issue? > > > > > > > > Given the stuff in the backtrace, my suspicion is something is trying to > > > > perform DMA to/from the stack, getting junk addresses form the attempted > > > > virt<->phys conversions. > > > > > > > > Could you try enabling both VMAP_STACK and CONFIG_DEBUG_VIRTUAL? > > > > > > CONFIG_DMA_API_DEBUG should scream about drivers trying to use stack > > > addresses either way, too. > > > > Thanks for suggestions, Mark & Robin. > > > > I enabled these debugging configs but cannot get clue from it; but > > occasionally found this issue is quite likely related with CA53 errata, > > especialy ERRATA_A53_855873 is the relative one. So I changed to use > > ARM-TF mainline code with ERRATA fixing, this issue can be dismissed. > > Thanks for the update. > > Just to confirm, with the updated firmware you no longer see the issue? Yes. > I can't immediately see how that would be related. > > Thanks, > Mark. From mboxrd@z Thu Jan 1 00:00:00 1970 From: leo.yan@linaro.org (Leo Yan) Date: Tue, 17 Oct 2017 08:33:29 +0800 Subject: ARM64: Regression with commit e3067861ba66 ("arm64: add basic VMAP_STACK support") In-Reply-To: <20171016134819.jv3udrcwsedc4cgs@lakrids.cambridge.arm.com> References: <20171010142725.GA24797@leoy-linaro> <20171010154558.GJ27659@leverpostej> <20171016011723.GB12470@leoy-linaro> <20171016134819.jv3udrcwsedc4cgs@lakrids.cambridge.arm.com> Message-ID: <20171017003329.GC19504@leoy-ThinkPad-T440> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 16, 2017 at 02:48:19PM +0100, Mark Rutland wrote: > Hi Leo, > > On Mon, Oct 16, 2017 at 09:17:23AM +0800, Leo Yan wrote: > > On Tue, Oct 10, 2017 at 05:03:44PM +0100, Robin Murphy wrote: > > > On 10/10/17 16:45, Mark Rutland wrote: > > > > On Tue, Oct 10, 2017 at 10:27:25PM +0800, Leo Yan wrote: > > > >> I work mainline kernel on Hikey620 board, I find it's easily to > > > >> introduce the panic and report the log as below. So I bisect the kernel > > > >> and finally narrow down the commit e3067861ba66 ("arm64: add basic > > > >> VMAP_STACK support") which introduce this issue. > > > >> > > > >> I tried to remove 'select HAVE_ARCH_VMAP_STACK' from > > > >> arch/arm64/Kconfig, then I can see the panic issue will dismiss. So > > > >> could you check this and have insight for this issue? > > > > > > > > Given the stuff in the backtrace, my suspicion is something is trying to > > > > perform DMA to/from the stack, getting junk addresses form the attempted > > > > virt<->phys conversions. > > > > > > > > Could you try enabling both VMAP_STACK and CONFIG_DEBUG_VIRTUAL? > > > > > > CONFIG_DMA_API_DEBUG should scream about drivers trying to use stack > > > addresses either way, too. > > > > Thanks for suggestions, Mark & Robin. > > > > I enabled these debugging configs but cannot get clue from it; but > > occasionally found this issue is quite likely related with CA53 errata, > > especialy ERRATA_A53_855873 is the relative one. So I changed to use > > ARM-TF mainline code with ERRATA fixing, this issue can be dismissed. > > Thanks for the update. > > Just to confirm, with the updated firmware you no longer see the issue? Yes. > I can't immediately see how that would be related. > > Thanks, > Mark.