From: Steven Price <steven.price@arm.com>
To: Chia-I Wu <olvaffe@gmail.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] panthor: dump task pid and comm on gpu errors
Date: Thu, 17 Jul 2025 16:24:12 +0100 [thread overview]
Message-ID: <5450eea4-def3-4b1c-9de7-6d6eb35b852a@arm.com> (raw)
In-Reply-To: <20250713030831.3227607-4-olvaffe@gmail.com>
On 13/07/2025 04:08, Chia-I Wu wrote:
> It is useful to know which tasks cause gpu errors.
>
> Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> drivers/gpu/drm/panthor/panthor_sched.c | 24 +++++++++++++++++++-----
> 1 file changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
> index 823b0fe678ba6..47912b06ec9d3 100644
> --- a/drivers/gpu/drm/panthor/panthor_sched.c
> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
> @@ -1364,8 +1364,12 @@ cs_slot_process_fatal_event_locked(struct panthor_device *ptdev,
> fatal = cs_iface->output->fatal;
> info = cs_iface->output->fatal_info;
>
> - if (group)
> + if (group) {
> + drm_warn(&ptdev->base, "CS_FATAL: pid=%d, comm=%s\n",
> + group->task_info.pid, group->task_info.comm);
> +
> group->fatal_queues |= BIT(cs_id);
> + }
>
> if (CS_EXCEPTION_TYPE(fatal) == DRM_PANTHOR_EXCEPTION_CS_UNRECOVERABLE) {
> /* If this exception is unrecoverable, queue a reset, and make
> @@ -1425,6 +1429,11 @@ cs_slot_process_fault_event_locked(struct panthor_device *ptdev,
> spin_unlock(&queue->fence_ctx.lock);
> }
>
> + if (group) {
> + drm_warn(&ptdev->base, "CS_FAULT: pid=%d, comm=%s\n",
> + group->task_info.pid, group->task_info.comm);
> + }
> +
> drm_warn(&ptdev->base,
> "CSG slot %d CS slot: %d\n"
> "CS_FAULT.EXCEPTION_TYPE: 0x%x (%s)\n"
> @@ -1641,11 +1650,15 @@ csg_slot_process_progress_timer_event_locked(struct panthor_device *ptdev, u32 c
>
> lockdep_assert_held(&sched->lock);
>
> - drm_warn(&ptdev->base, "CSG slot %d progress timeout\n", csg_id);
> -
> group = csg_slot->group;
> - if (!drm_WARN_ON(&ptdev->base, !group))
> + if (!drm_WARN_ON(&ptdev->base, !group)) {
> + drm_warn(&ptdev->base, "CSG_PROGRESS_TIMER_EVENT: pid=%d, comm=%s\n",
> + group->task_info.pid, group->task_info.comm);
> +
> group->timedout = true;
> + }
> +
> + drm_warn(&ptdev->base, "CSG slot %d progress timeout\n", csg_id);
>
> sched_queue_delayed_work(sched, tick, 0);
> }
> @@ -3227,7 +3240,8 @@ queue_timedout_job(struct drm_sched_job *sched_job)
> struct panthor_scheduler *sched = ptdev->scheduler;
> struct panthor_queue *queue = group->queues[job->queue_idx];
>
> - drm_warn(&ptdev->base, "job timeout\n");
> + drm_warn(&ptdev->base, "job timeout: pid=%d, comm=%s, seqno=%llu\n",
> + group->task_info.pid, group->task_info.comm, job->done_fence->seqno);
>
> drm_WARN_ON(&ptdev->base, atomic_read(&sched->reset.in_progress));
>
prev parent reply other threads:[~2025-07-17 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 3:08 [PATCH v2 0/3] panthor: print " Chia-I Wu
2025-07-13 3:08 ` [PATCH v2 1/3] panthor: set owner field for driver fops Chia-I Wu
2025-07-13 3:08 ` [PATCH v2 2/3] panthor: save task pid and comm in panthor_group Chia-I Wu
2025-07-13 5:10 ` kernel test robot
2025-07-17 15:24 ` Steven Price
2025-07-13 3:08 ` [PATCH v2 3/3] panthor: dump task pid and comm on gpu errors Chia-I Wu
2025-07-17 15:24 ` Steven Price [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=5450eea4-def3-4b1c-9de7-6d6eb35b852a@arm.com \
--to=steven.price@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®