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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CEB55C4332F for ; Mon, 17 Oct 2022 19:25:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231193AbiJQTZa (ORCPT ); Mon, 17 Oct 2022 15:25:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231194AbiJQTZO (ORCPT ); Mon, 17 Oct 2022 15:25:14 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC26720F48 for ; Mon, 17 Oct 2022 12:24:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666034610; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ppFCDIP52kTXbWdVyG8sgqag9kDp+DU5BUqcmjHWKnY=; b=BNvFaIL3NtQ0Sm8YKQJb+yX9PJXJmz8p56INsBUIjlbvbXS12AsS5lWmZQuqzC1Z2x+BFC d0DRy8cTd7Tb3fFMSQxMD0bmDrOZAo4TCV8ySgx44PtE7vMUT56orxwnpd7D2dO+S7a1bS xPaI9Hp8oKJMIFQ6e4IfzIR7nE5HPQs= Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-260-Qy9DWyJmO1G2qMI7szGgRg-1; Mon, 17 Oct 2022 15:23:28 -0400 X-MC-Unique: Qy9DWyJmO1G2qMI7szGgRg-1 Received: by mail-io1-f71.google.com with SMTP id r12-20020a5e8e4c000000b006bc3030624fso7742814ioo.23 for ; Mon, 17 Oct 2022 12:23:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ppFCDIP52kTXbWdVyG8sgqag9kDp+DU5BUqcmjHWKnY=; b=C1VxVMnVCvJHg6epemQrOlgXFNK93cnZvwhNaDRrrJxCIijbx6k6S+3AHQQs03DhE7 NCNZvhJye6w3CxEuk9g14sqjthwqE4xchHPtyfzmJrjTlheCdo/9ED36ScTEzqO4Ik08 WEXzNT5gazSEGo2TVk4prr1aqtjDssyqYc0s2D/376BiDGPa9bApshVdvp+P7Ae/yrAa aLyO7Er57xWToTFc8ewGRQh++ftLj5yXQlV+5f7Tk/DaBdpQgJ0O43bgqp+TfSel6WsA J66OsbWcX+nxn7EWKd5hjmHSu1aad5EIK6vEEHDy56GrFZCLpIr/bhpo+p9x3FSYCkUP 85CA== X-Gm-Message-State: ACrzQf2LGiP7YGco0vi78TtGXj9nEqh3jqbBwHt77aSmcb2HGJlzmDwo avHyvh856Gm4PnUgOxqqsIlL0ZAeYoupKRVf0C6/bpAbmQpsyKIA7sZ3rGPWcJ8M61K2XGGK8XG NY4dn0A2dDACvevLJQFjLUQ== X-Received: by 2002:a6b:ba84:0:b0:6bb:e801:3d3c with SMTP id k126-20020a6bba84000000b006bbe8013d3cmr5225859iof.15.1666034607940; Mon, 17 Oct 2022 12:23:27 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5N7zu6VVcnyedWhPo4O7gvrWanOEux+ayHtBvhvFHfqHlDR2tQczGlDMnSbYR2EFkaNr/tIQ== X-Received: by 2002:a6b:ba84:0:b0:6bb:e801:3d3c with SMTP id k126-20020a6bba84000000b006bbe8013d3cmr5225840iof.15.1666034607677; Mon, 17 Oct 2022 12:23:27 -0700 (PDT) Received: from x1 (c-98-239-145-235.hsd1.wv.comcast.net. [98.239.145.235]) by smtp.gmail.com with ESMTPSA id u18-20020a92ccd2000000b002eb1137a774sm201137ilq.59.2022.10.17.12.23.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Oct 2022 12:23:27 -0700 (PDT) Date: Mon, 17 Oct 2022 15:23:25 -0400 From: Brian Masney To: Eric Chanudet , Parikshit Pareek Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Halaney , Shazad Hussain , Johan Hovold Subject: Re: [PATCH v5 0/3] arm64: dts: qcom: add dts for sa8540p-ride board Message-ID: References: <20221003125444.12975-1-quic_ppareek@quicinc.com> <20221004132816.ryhyo5ihwruxspl6@echanude> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221004132816.ryhyo5ihwruxspl6@echanude> User-Agent: Mutt/2.2.7 (2022-08-07) Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Tue, Oct 04, 2022 at 09:28:16AM -0400, Eric Chanudet wrote: > I followed the instructions above and linux-next-20220930 booted on the > QDrive3 to a prompt. It then hanged after a couple minutes and rebooted > in Sahara mode: > B - 1662280 - Sahara Init > B - 1665422 - Sahara Open > > There seems to be no trace from the kernel, this happened consistently > over 3 boots. > > I asked Brian, he mentioned he only booted to prompt so that may have > happened unbeknownst to him as well. Good catch, Eric! Parikshit: I found a way to reproduce the crash and isolated the issue to the qcom_q6v5_pas driver. Here's how you can reproduce the crash that we're seeing: 1) Use my instructions at [1] to build an upstream kernel with the arm64 defconfg. Today I used linux-next-20221017. 2) Copy the modules to the root filesystem. Before you reboot, mv /lib/modules/6.0.0-next-20221017-xxx to /lib/modules/6.0.0-next-20221017-xxx-old so that the modules are not automatically loaded on startup. 3) Reboot, and run lsmod and verify that no modules are loaded. 4) cd /lib/modules/6.0.0-next-20221017-xxx-old 5) Now load the modules that work as expected that are loaded with the upstream arm64 defconfig: insmod ./kernel/net/rfkill/rfkill.ko insmod ./kernel/arch/arm64/crypto/crct10dif-ce.ko insmod ./kernel/net/qrtr/qrtr.ko insmod ./kernel/drivers/phy/qualcomm/phy-qcom-snps-femto-v2.ko insmod ./kernel/drivers/soc/qcom/llcc-qcom.ko insmod ./kernel/drivers/soc/qcom/qmi_helpers.ko insmod ./kernel/drivers/remoteproc/qcom_sysmon.ko insmod ./kernel/drivers/remoteproc/qcom_q6v5.ko insmod ./kernel/drivers/rpmsg/qcom_glink_smem.ko insmod ./kernel/drivers/soc/qcom/socinfo.ko insmod ./kernel/drivers/remoteproc/qcom_pil_info.ko insmod ./kernel/drivers/remoteproc/qcom_common.ko insmod ./kernel/drivers/watchdog/qcom-wdt.ko insmod ./kernel/fs/fuse/fuse.ko insmod ./kernel/drivers/soc/qcom/mdt_loader.ko 6) Wait a few minutes to be sure that everything is working as expected on the board. 7) Make the board go BOOM: insmod ./kernel/drivers/remoteproc/qcom_q6v5_pas.ko We don't know how or have the tools to analyze the ramdumps from the Qualcomm firmware at Red Hat, so we're flying blind right now. [1] https://lore.kernel.org/lkml/YzsciFeYpvv%2F92CG@x1/ Brian