From: Brian Masney <bmasney@redhat.com>
To: Eric Chanudet <echanude@redhat.com>,
Parikshit Pareek <quic_ppareek@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Halaney <ahalaney@redhat.com>,
Shazad Hussain <quic_shazhuss@quicinc.com>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH v5 0/3] arm64: dts: qcom: add dts for sa8540p-ride board
Date: Mon, 17 Oct 2022 15:23:25 -0400 [thread overview]
Message-ID: <Y02rrdFqN1X2PC4t@x1> (raw)
In-Reply-To: <20221004132816.ryhyo5ihwruxspl6@echanude>
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
next prev parent reply other threads:[~2022-10-17 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 12:54 [PATCH v5 0/3] arm64: dts: qcom: add dts for sa8540p-ride board Parikshit Pareek
2022-10-03 12:54 ` [PATCH v5 1/3] dt-bindings: arm: qcom: Document additional sa8540p device Parikshit Pareek
2022-10-03 12:54 ` [PATCH v5 2/3] arm64: dts: qcom: sa8295p: move common nodes to dtsi Parikshit Pareek
2022-10-03 13:28 ` Krzysztof Kozlowski
2022-10-17 18:52 ` Bjorn Andersson
2022-10-03 12:54 ` [PATCH v5 3/3] arm64: dts: qcom: introduce sa8540p-ride dts Parikshit Pareek
2022-10-03 13:29 ` Krzysztof Kozlowski
2022-10-03 17:31 ` [PATCH v5 0/3] arm64: dts: qcom: add dts for sa8540p-ride board Brian Masney
2022-10-03 19:33 ` Andrew Halaney
2022-10-04 13:28 ` Eric Chanudet
2022-10-04 15:50 ` Andrew Halaney
2022-10-17 19:23 ` Brian Masney [this message]
2022-11-04 19:53 ` Brian Masney
2022-10-03 21:05 ` Konrad Dybcio
2022-10-06 2:54 ` Parikshit Pareek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y02rrdFqN1X2PC4t@x1 \
--to=bmasney@redhat.com \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=echanude@redhat.com \
--cc=johan@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_ppareek@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).