Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1994210rwb; Fri, 11 Nov 2022 03:36:59 -0800 (PST) X-Google-Smtp-Source: AA0mqf4elmT3fhIic2+IHHUn8HPd7uc5tQaJ5Glc/45uk0TWQ4MND2HeEwSSTVhmrXLBEHMC7yNX X-Received: by 2002:a62:6d82:0:b0:562:c9d0:2c8c with SMTP id i124-20020a626d82000000b00562c9d02c8cmr2282201pfc.44.1668166619416; Fri, 11 Nov 2022 03:36:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668166619; cv=none; d=google.com; s=arc-20160816; b=pWkpKlgDfyQgndy8V5E8r3cSG1L/rpS2ZPVXkMFI/M7+40ZWP461AvUbPXew3s8OEp 4+4veHXL6u82xEHMMzzW6u/+0RYB8DOm3xUEghA+Ara9T7plcLN2V/fzhjgyaTOKIx6F 6wpEzY9qoRoDHTS7Rszor5Bv+28uzT1xzvBY40BMIvtJX4R2z9dfvnRnR8HEnNGYoUx5 hUC+p0VsZWOp/JoT0MtF37G7blef62vmiPjnNs+ptrDFxwVdbjhJrAU8bjmvxffh9F5i dbzBtS/YD6dnrylhKe0Y12kuGIFk3EoVvmHjXh9bqXGy77uBxZI43LNRxjsBQ/bXX+g2 loJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=CN5Of4cH8FabphI8+bEplECYkQHnNzxTog4IVx41LWA=; b=Xy80VQ/Jjs3A9zCbPehdsmFvs+nwkB+1683ljmh1HMB40tJ25/soXu4VyBv9umYOlJ HQGexK+rG8aWjo2FiVJjYUwWrQNM+8/jeWn/I/UCX8vJ9BjpIedeWgG78kdOKuJl3j+U Yx5qUdbfmkCrTmgmXniV0/LXv2iovKHbURkkBrT1kf905sCQ4uutnm4rEO9XxINt0jQb cU1f+8PHarlU63IxDW8+9ECFH9DoymUj7RMKT+GYZwoLWhJxYMaeboQ3wOqJI/bRh9ez fLKpizMdeH5fBzTS0G44p3vW9Dwyq0gdS0NulBUtZFgaaapPBRGXEcFFDT6G1vwYWhsW JkSQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g127-20020a625285000000b00543bc7e5bc9si1872069pfb.361.2022.11.11.03.36.47; Fri, 11 Nov 2022 03:36:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233067AbiKKLP2 (ORCPT + 92 others); Fri, 11 Nov 2022 06:15:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35112 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230377AbiKKLP0 (ORCPT ); Fri, 11 Nov 2022 06:15:26 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5282E6711D for ; Fri, 11 Nov 2022 03:15:25 -0800 (PST) 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 ams.source.kernel.org (Postfix) with ESMTPS id CC551B825C4 for ; 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-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.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