From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Andi Shyti <andi.shyti@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
dri-devel@lists.freedesktop.org, igt-dev@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/selftests: Wait longer for request to start
Date: Tue, 01 Sep 2026 10:07:01 +0200 [thread overview]
Message-ID: <ae095644e460f5a278da56c4eb47a5aaac37b19e.camel@linux.intel.com> (raw)
In-Reply-To: <2fn7euzh5tuunytl5lgkefiitsjrprvsiqyphb77p5q4qz3enw@yj63s65lvdgw>
Hi Krzysztof,
On Tue, 2026-09-01 at 06:19 +0000, Krzysztof Karas wrote:
> Hi Janusz,
>
> On 2026-08-31 at 11:33:08 +0200, Janusz Krzysztofik wrote:
> > CI extreamly sporadically (five times over last six mohths) reported
> extreamly -> extremely, mohths -> months
Heh, thanks, those were results of my last minute polishing, apparently
with spell checker off, sorry.
>
> > failures of igt@i915_selftest@live@hangcheck on ARL-S machines. The
> > selftest was timing out while waiting up to 1 second for a request
> > supposed to trigger a GPU hang to be started. It occurred possible to
> > reproduce this issue manually by running the selftest in a loop for a
> > few hours.
> >
> > Among results from 5 occurrences reported by CI so far, and two manual
> > reproductions, two of them contained messages that suggested a
> > posssibility of the awaited request to actually start soon after
> > timeout. With the timeout extended from 1 to 2 seconds, it occurred no
> > longer possible to trigger the failure, even when running the test in a
> > loop for 10, then for 12 hours, on the same machine where it was failing
> > before in 2-3 hours.
> >
> > Assume the conditions that prevented the hang requests to start within 1
> > second were always transient, and 2 seconds is sufficient for those
> > requests to start effectively on machines in the CI environment. Fix
> > the issue by using that value as the timeout.
> >
> > Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/16624
> > Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c
> > index 00dfc37221fac..53f3ce5c33a47 100644
> > --- a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c
> > +++ b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c
> > @@ -278,7 +278,7 @@ static bool wait_until_running(struct hang *h, struct i915_request *rq)
> > 10) &&
> > wait_for(i915_seqno_passed(hws_seqno(h, rq),
> > rq->fence.seqno),
> > - 1000));
> > + 2000));
> > }
> >
> > static int igt_hang_sanitycheck(void *arg)
> > --
> > 2.54.0
> >
>
> Patch is trivial, so:
> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
Thank you :-)
>
> though, it would probably need a rebase, since it does not apply
> cleanly for CI build process.
Please note that was only a response from an attempt to apply the patch to
IGT sources (I sent a copy to igt-dev@lists.freedesktop.org).
Thanks,
Janusz
next prev parent reply other threads:[~2026-09-01 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 9:33 [PATCH] drm/i915/selftests: Wait longer for request to start Janusz Krzysztofik
2026-08-31 15:03 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2026-08-31 15:23 ` ✓ i915.CI.BAT: success " Patchwork
2026-08-31 20:21 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-01 10:43 ` Janusz Krzysztofik
2026-09-01 14:24 ` Ravali, JupallyX
2026-09-01 6:19 ` [PATCH] " Krzysztof Karas
2026-09-01 8:07 ` Janusz Krzysztofik [this message]
2026-09-01 12:57 ` ✓ i915.CI.Full: success for " Patchwork
2026-09-02 9:54 ` [PATCH] " Krzysztof Niemiec
2026-09-10 21:07 ` Andi Shyti
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=ae095644e460f5a278da56c4eb47a5aaac37b19e.camel@linux.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sebastian.brzezinka@intel.com \
--cc=tursulin@ursulin.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.