Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/2] RFC: runner: dump GPU error state on timeout
Date: Fri, 14 Jul 2023 17:39:44 +0200	[thread overview]
Message-ID: <20230714153946.36448-1-kamil.konieczny@linux.intel.com> (raw)

Create dump of GPU error state when test is interrupted by
executor due to per-test timeout or inactivity. In those cases
dump by kernel sysrq('G') may be empty so use drm error or dri
debug info.

Cc: Petri Latvala <adrinael@adrinael.net>
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>

Kamil Konieczny (2):
  runner/settings: add dump-gpu-on-timeout option
  runner/executor: write GPU error on timeout

 runner/executor.c | 68 +++++++++++++++++++++++++++++++++++++++++++++--
 runner/executor.h |  2 ++
 runner/settings.c | 12 ++++++++-
 runner/settings.h |  1 +
 4 files changed, 80 insertions(+), 3 deletions(-)

-- 
2.39.2



             reply	other threads:[~2023-07-14 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 15:39 Kamil Konieczny [this message]
2023-07-14 15:39 ` [igt-dev] [PATCH i-g-t 1/2] runner/settings: add dump-gpu-on-timeout option Kamil Konieczny
2023-09-19  7:20   ` Mauro Carvalho Chehab
2023-07-14 15:39 ` [igt-dev] [PATCH i-g-t 2/2] runner/executor: write GPU error on timeout Kamil Konieczny
2023-09-19  7:29   ` Mauro Carvalho Chehab
2023-09-19  8:09     ` Kamil Konieczny
2023-07-14 15:58 ` [igt-dev] ✗ GitLab.Pipeline: warning for RFC: runner: dump GPU error state " Patchwork
2023-07-14 16:29 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-07-14 17:01 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-14 18:30 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork

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=20230714153946.36448-1-kamil.konieczny@linux.intel.com \
    --to=kamil.konieczny@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.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