From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 44380C54FCB for ; Thu, 23 Apr 2020 11:33:29 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 10B1220736 for ; Thu, 23 Apr 2020 11:33:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="hXNfJyq1" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 10B1220736 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=bJGnZ9x/yriCYe5u+ZhdnUdgkJh2psdLZcHrUY2IMoE=; b=hXNfJyq1i3kMel hzv7fUikYUjZw0X0s9lgcR/8s9OHNc3jZjIjTK2EIvnMW4wwGRkgZz+FWGk+iosnFFhS74Lt9K/p+ QkJv5EXxaJXhA6Mt8afMqinxq/jqJz6W/rWjAjyT1wPlcfnqytZ6LpfUC/Ytov9piTe/falOAZNOV BrHLtLFdH/16cPnzmt9A6DZHK0dtJ/yNtTwsePgULRWCZpCx3EB+xD0KCme3IVWUVpKFqfzRMM3/u x/tDwtYskYHXImbpRonJnNeJ2SAlAk+WHuySwhdaoZ6UVvkmK5FgT4SudirLSMrPzExu7cm5gG6Z1 Ls874EGI+Q2OEseKQLUg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jRa6f-0004eB-Ed; Thu, 23 Apr 2020 11:33:25 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jRa6c-0004cz-6p for linux-arm-kernel@lists.infradead.org; Thu, 23 Apr 2020 11:33:23 +0000 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 072F231B; Thu, 23 Apr 2020 04:33:21 -0700 (PDT) Received: from gaia (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 112023F68F; Thu, 23 Apr 2020 04:33:19 -0700 (PDT) Date: Thu, 23 Apr 2020 12:33:17 +0100 From: Catalin Marinas To: Tim Harvey Subject: Re: IMX8MM kernel panic on 5.5+ due to patch series 'Raspberry Pi 4 DMA addressing support' Message-ID: <20200423113317.GD4963@gaia> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200423_043322_292383_9C98431C X-CRM114-Status: GOOD ( 15.13 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Shawn Guo , Fabio Estevam , Nicolas Saenz Julienne , Linux ARM Mailing List , Christoph Hellwig Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Apr 22, 2020 at 10:44:33AM -0700, Tim Harvey wrote: > I'm seeing a kernel panic on an IMX8MM board using defconfig starting > with the patch series 'Raspberry Pi 4 DMA addressing support': > > 734f924 mm: refresh ZONE_DMA and ZONE_DMA32 comments in 'enum zone_type' > 1a8e1ce arm64: use both ZONE_DMA and ZONE_DMA32 > a573cdd arm64: rename variables used to calculate ZONE_DMA32's size > ae970dc arm64: mm: use arm64_dma_phys_limit instead of calling > max_zone_dma_phys() > > Strangely I don't see this panic on an ARM64 OcteonTX CPU (thunderx) > with defconfig so perhaps this has to do with some dt thing? > > I find that a573cdd ("arm64: rename variables used to calculate > ZONE_DMA32's size") breaks building arm64 defconfig due to renaming of > arm64_dma_phys_limit to arm64_dma32_phys_limit but > arm64_dma_phys_limit still used in includ/asm/processor.h > > The following patch resolves this build error and panic: So it means that commit 1a8e1ce causes the break for you. I haven't seen this problem on any other platform yet. A wrong DT could as well cause problems as this commit would change where some memory allocations come from. Can you run the kernel with memtest=1, just in case the DT is wrongly pointing to some non-RAM areas. -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel