From: Chrispine Tinega <dev@chrispinetinega.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Francesco Valla <francesco@valla.it>,
Chrispine Tinega <dev@chrispinetinega.com>
Subject: [PATCH v3 1/2] remoteproc: k3: Report a remote crash to the remoteproc core
Date: Mon, 23 Nov 2026 01:17:53 +0300 [thread overview]
Message-ID: <20261122221755.88160-2-dev@chrispinetinega.com> (raw)
In-Reply-To: <20261122221755.88160-1-dev@chrispinetinega.com>
A K3 remote core that faults can send RP_MBOX_CRASH over the mailbox,
but k3_rproc_mbox_callback() only logs it. The remoteproc core never
learns of the crash, so its recovery never runs, the crash is not
counted, and the core stays halted with every rpmsg channel to it dead.
Call rproc_report_crash(), which may be called from atomic context, when
the core is RPROC_RUNNING, that is when Linux booted it. The core then
moves to RPROC_CRASHED and the crash is counted. Where the driver leaves
recovery enabled, recovery stops the core and boots it again. Where
recovery is disabled, the core can still be stopped and started again
through sysfs.
In any other state, keep only logging the crash:
- An IPC-only core, RPROC_DETACHED or RPROC_ATTACHED, was not booted
by Linux. Once marked crashed, rproc_detach() refuses it, and the
drivers' remove paths skip the detach and leak its resources. The R5F
has no start or stop ops in this mode at all.
- Each K3 driver requests its mailbox before devm_rproc_add(). A crash
queued then would not be cancelled if probe failed, and the work
would run on a freed rproc. The state is never RPROC_RUNNING there.
Recovery on its own cannot yet restart an R5F: the reset the R5F needs
before it starts again is applied in its unprepare() op, which sysfs
stop calls and recovery does not. The R5F driver keeps recovery
disabled, so this does not change what happens there.
Signed-off-by: Chrispine Tinega <dev@chrispinetinega.com>
---
Changes in v3:
- Guard rproc_report_crash() with rproc->state == RPROC_RUNNING and keep
the dev_err() print in other states, so IPC-only cores do not lose
detach and a crash queued before devm_rproc_add() cannot run after a
failed probe. (Sashiko review, pointed out by Francesco)
Changes in v2:
- Drop the dev_err(). rproc_report_crash() already logs the crash
and names the core. (Francesco)
- Say in the commit message that recovery cannot yet restart an R5F.
(Francesco)
drivers/remoteproc/ti_k3_common.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/remoteproc/ti_k3_common.c b/drivers/remoteproc/ti_k3_common.c
index 4b6da3363..29ca51861 100644
--- a/drivers/remoteproc/ti_k3_common.c
+++ b/drivers/remoteproc/ti_k3_common.c
@@ -61,10 +61,16 @@ void k3_rproc_mbox_callback(struct mbox_client *client, void *data)
switch (msg) {
case RP_MBOX_CRASH:
/*
- * remoteproc detected an exception, but error recovery is not
- * supported. So, just log this for now
+ * Report only a crash of a core that Linux booted. Once the
+ * remoteproc core marks an IPC-only core crashed, it can no
+ * longer detach from it. The state is never RPROC_RUNNING
+ * before devm_rproc_add(), so a failed probe cannot leave
+ * crash work queued.
*/
- dev_err(dev, "K3 rproc %s crashed\n", rproc->name);
+ if (rproc->state == RPROC_RUNNING)
+ rproc_report_crash(rproc, RPROC_FATAL_ERROR);
+ else
+ dev_err(dev, "K3 rproc %s crashed\n", rproc->name);
break;
case RP_MBOX_ECHO_REPLY:
dev_info(dev, "received echo reply from %s\n", rproc->name);
--
2.53.0
next prev parent reply other threads:[~2026-11-22 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 22:17 [PATCH v3 0/2] remoteproc: k3: Recover a crashed remote core Chrispine Tinega
2026-11-22 22:17 ` Chrispine Tinega [this message]
2026-11-22 22:17 ` [PATCH v3 2/2] remoteproc: k3-m4: Enable crash recovery for a core Linux booted Chrispine Tinega
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=20261122221755.88160-2-dev@chrispinetinega.com \
--to=dev@chrispinetinega.com \
--cc=andersson@kernel.org \
--cc=francesco@valla.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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
all inboxes | Powered by JetHome®