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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 2864FC433FE for ; Fri, 11 Nov 2022 11:16:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc: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=Fu8zBG+/GZq4bl9tTZvIwsD6m8vpvyZM1hTE2QU1PzQ=; b=R9rYVtpDHhmCgx j2H7U+3yiLpgPsRM9kmE9uS8u5ek/0ogW4dkyYgzQSXkiqLyry+37U2YfZBMSo/NRTHAcml0lGw6Z LiSsqH9KJBW4qAQjQ61u27vRXCey6gZHvfdSOzBgi1FI2qdJ3EsTqir8fKMRzEngl9Kv0xyLrcjz/ gdIF0lwtUeNFhKbTxvX0iT42Pq/eE2NQyN/RlOqyBqyige5zRs394hLrlxH4L1kllv+gNDLXDpDGi +ahBUMmi+ToR7y2RQBV+e+YDURxXUq0TiXuQkXJvW4/xhXyrAMo90rqLkuJvv8IV3HKL7+ZnAdx5P MBLDVpkZCxZZD3HGmxpw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1otS0Q-00FEQj-80; Fri, 11 Nov 2022 11:15:30 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1otS0M-00FEPY-IV for linux-arm-kernel@lists.infradead.org; Fri, 11 Nov 2022 11:15:28 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 08CB661F83; Fri, 11 Nov 2022 11:15:23 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 23C66C433C1; Fri, 11 Nov 2022 11:15:17 +0000 (UTC) Date: Fri, 11 Nov 2022 11:15:11 +0000 From: Catalin Marinas To: Amit Pundir Cc: Robin Murphy , Bjorn Andersson , Sibi Sankar , Manivannan Sadhasivam , Will Deacon , Linus Torvalds , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Dmitry Baryshkov Subject: Re: [GIT PULL] arm64 updates for 6.1-rc1 Message-ID: References: <20221005144116.2256580-1-catalin.marinas@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221111_031526_688985_CE19778B X-CRM114-Status: GOOD ( 27.25 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Nov 08, 2022 at 10:58:16PM +0530, Amit Pundir wrote: > On Tue, 25 Oct 2022 at 18:08, Amit Pundir wrote: > > On Wed, 12 Oct 2022 at 17:24, Catalin Marinas wrote: > > > On Sat, Oct 08, 2022 at 08:28:26PM +0530, Amit Pundir wrote: > > > > On Wed, 5 Oct 2022 at 20:11, Catalin Marinas wrote: > > > > > Will Deacon (2): > > > > > arm64: dma: Drop cache invalidation from arch_dma_prep_coherent() > > > > > > > > This patch broke AOSP on Dragonboard 845c (SDM845). I don't see any > > > > relevant crash in the attached log and device silently reboots into > > > > USB crash dump mode. The crash is fairly reproducible on db845c. I > > > > could trigger it twice in 5 reboots and it always crash at the same > > > > point during the boot process. Reverting this patch fixes the crash. > > > > > > > > I'm happy to test run any debug patche(s), that would help narrow > > > > down this breakage. [...] > > Further narrowed down the breakage to the userspace daemon rmtfs > > https://github.com/andersson/rmtfs. Is there anything specific in the > > userspace code that I should be paying attention to? Since you don't see anything in the logs like a crash and the system restarts, I suspect it's some deadlock and that's triggering the watchdog. We have an erratum (826319) but that's for Cortex-A53. IIUC SDM845 has Kryo 3xx series which based on some random google searches is derived from A75/A55. Unfortunately the MIDR_EL1 register doesn't match the Arm Ltd numbering, so I have no idea what CPUs these are by looking at the boot log. I wouldn't be surprised if you hit a similar bug, though I couldn't find anything close in the A55 errata notice. While we could revert commit c44094eee32f ("arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()"), if you hit a real hardware issue it may trigger in other scenario where we only do cache cleaning (without invalidate), like arch_sync_dma_for_device(). So I'd rather get to the bottom of this and potentially enable the workaround for this chipset. You could give it a quick try to by adding the MIDR ranges for SDM845 to struct midr_range workaround_clean_cache[]. After that I suggest you raise it with Qualcomm to investigate. Normally we ask for an erratum number to enable a workaround and it's only Qualcomm that can provide one here. -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel