From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Resolve suspend-resume racing with GuC destroy-context-worker (rev8)
Date: Fri, 1 Dec 2023 05:10:56 +0000 [thread overview]
Message-ID: <31bde6dcbe6d037664d1dc65fd6640f8af0d77f2.camel@intel.com> (raw)
In-Reply-To: <170139720876.19689.7886447817422892743@emeril.freedesktop.org>
On Fri, 2023-12-01 at 02:20 +0000, Patchwork wrote:
> Patch Details
> Series: Resolve suspend-resume racing with GuC destroy-context-worker (rev8)
> URL: https://patchwork.freedesktop.org/series/121916/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_121916v8/index.html
alan:snip
> Here are the unknown changes that may have been introduced in Patchwork_121916v8:
>
> IGT changes
> Possible regressions
>
> * igt@i915_selftest@live@requests:
> * bat-mtlp-6: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13956/bat-mtlp-6/igt@i915_selftest@live@requests.html> -> DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_121916v8/bat-mtlp-6/igt@i915_selftest@live@requests.html>
alan: inspecting the selftest code that is failing WRT changes in this targets, i really dont see any relation.
the series is changing how we handle context deregistratoin either thru the regular context-close or through the
flushing during suspend... however the selftest reporting a reset would be an issue where the context is not
closed (because it would be hanging) - also its a kernel context - which should not get closed.
I will run another retest after i verify trybot sees no issue.
prev parent reply other threads:[~2023-12-01 5:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 0:20 [Intel-gfx] [PATCH v7 0/2] Resolve suspend-resume racing with GuC destroy-context-worker Alan Previn
2023-11-30 0:20 ` [Intel-gfx] [PATCH v7 1/2] drm/i915/guc: Flush context destruction worker at suspend Alan Previn
2023-11-30 0:20 ` [Intel-gfx] [PATCH v7 2/2] drm/i915/guc: Close deregister-context race against CT-loss Alan Previn
2023-11-30 21:18 ` Rodrigo Vivi
2023-12-01 0:09 ` Teres Alexis, Alan Previn
2023-12-01 0:10 ` Teres Alexis, Alan Previn
2023-12-06 21:47 ` Daniele Ceraolo Spurio
2023-11-30 7:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Resolve suspend-resume racing with GuC destroy-context-worker (rev7) Patchwork
2023-12-01 1:33 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Resolve suspend-resume racing with GuC destroy-context-worker (rev8) Patchwork
2023-12-01 2:20 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-12-01 5:10 ` Teres Alexis, Alan Previn [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=31bde6dcbe6d037664d1dc65fd6640f8af0d77f2.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@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