From: Shawn Guo <shawnguo@kernel.org>
To: Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, kernel@pengutronix.de, festevam@gmail.com,
linux-imx@nxp.com, Frank.Li@nxp.com, marcel.ziswiler@toradex.com,
qiangqing.zhang@nxp.com, s.hauer@pengutronix.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8qm: Add imx8qm's own pm to avoid panic during startup
Date: Wed, 6 Dec 2023 08:57:04 +0800 [thread overview]
Message-ID: <20231206005704.GL236001@dragon> (raw)
In-Reply-To: <20231110072531.1957891-1-xiaolei.wang@windriver.com>
On Fri, Nov 10, 2023 at 03:25:31PM +0800, Xiaolei Wang wrote:
> Add imx8qm's own pm, otherwise the following panic will
> occur during the startup process:
>
> Kernel panic - not syncing: Asynchronous SError Interrupt
> Hardware name: Freescale i.MX8QM MEK (DT)
> Workqueue: events_unbound deferred_probe_work_func
> Call trace:
> dump_backtrace+0x98/0xf0
> show_stack+0x18/0x24
> dump_stack_lvl+0x60/0xac
> dump_stack+0x18/0x24
> panic+0x340/0x3a0
> nmi_panic+0x8c/0x90
> arm64_serror_panic+0x6c/0x78
> do_serror+0x3c/0x78
> el1h_64_error_handler+0x38/0x50
> el1h_64_error+0x64/0x68
> fsl_edma_chan_mux+0x98/0xdc
> fsl_edma_probe+0x278/0x898
> platform_probe+0x68/0xd8
> really_probe+0x110/0x27c
> __driver_probe_device+0x78/0x12c
> driver_probe_device+0x3c/0x118
> __device_attach_driver+0xb8/0xf8
> bus_for_each_drv+0x84/0xe4
> __device_attach+0xfc/0x18c
> device_initial_probe+0x14/0x20
>
> Fixes: e4d7a330fb7a ("arm64: dts: imx8: add edma[0..3]")
> Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
Applied, thanks!
prev parent reply other threads:[~2023-12-06 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 7:25 [PATCH] arm64: dts: imx8qm: Add imx8qm's own pm to avoid panic during startup Xiaolei Wang
2023-12-06 0:57 ` Shawn Guo [this message]
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=20231206005704.GL236001@dragon \
--to=shawnguo@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=xiaolei.wang@windriver.com \
/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).