All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for Resolve suspend-resume racing with GuC destroy-context-worker (rev13)
Date: Tue, 9 Jan 2024 17:42:03 -0500	[thread overview]
Message-ID: <ZZ3Lu05dDTg_kxfk@intel.com> (raw)
In-Reply-To: <3e75cd48e9bd1a4d4dff72653d8892f587acdea0.camel@intel.com>

On Thu, Jan 04, 2024 at 05:39:16PM +0000, Teres Alexis, Alan Previn wrote:
> On Thu, 2024-01-04 at 10:57 +0000, Patchwork wrote:
> > Patch Details
> > Series: Resolve suspend-resume racing with GuC destroy-context-worker (rev13)
> > URL:    https://patchwork.freedesktop.org/series/121916/
> > State:  failure
> > Details:        https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_121916v13/index.html
> > CI Bug Log - changes from CI_DRM_14076_full -> Patchwork_121916v13_full
> > Summary
> > 
> > FAILURE
> alan:snip
> 
> 
> > Here are the unknown changes that may have been introduced in Patchwork_121916v13_full:
> > 
> > IGT changes
> > Possible regressions
> > 
> >   *   igt@gem_eio@wait-wedge-immediate:
> >      *   shard-mtlp: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14076/shard-mtlp-3/igt@gem_eio@wait-wedge-immediate.html> -> ABORT<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_121916v13/shard-mtlp-4/igt@gem_eio@wait-wedge-immediate.html>
> > 
> alan: from the code and dmesg, this is unrelated to guc context destruction flows.
> Its reading an MCR register that times out. Additionally, i believe this error is occuring during post-reset-init flows.
> So its definitely not doing any context destruction at this point (as reset would have happenned sooner).

yeap, it is indeed happening once in a while:

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7659/shard-mtlp-4/igt@gem_eio@wait-wedge-immediate.html

I was going to merge the series now, but then I noticed that Matt had taken care of that.
Thank you all.

> > Known issues
> > 
> 

      parent reply	other threads:[~2024-01-09 22:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28  4:55 [PATCH v9 0/2] Resolve suspend-resume racing with GuC destroy-context-worker Alan Previn
2023-12-28  4:55 ` Alan Previn
2023-12-28  4:55 ` [PATCH v9 1/2] drm/i915/guc: Flush context destruction worker at suspend Alan Previn
2023-12-28  4:55   ` Alan Previn
2023-12-28  4:55 ` [PATCH v9 2/2] drm/i915/guc: Close deregister-context race against CT-loss Alan Previn
2023-12-28  4:55   ` Alan Previn
2023-12-29 21:51   ` Alan Previn
2023-12-29 21:51     ` Alan Previn
2024-01-02 17:40 ` [PATCH v9 0/2] Resolve suspend-resume racing with GuC destroy-context-worker Teres Alexis, Alan Previn
2024-01-02 17:40   ` Teres Alexis, Alan Previn
2024-01-04  8:32 ` ✗ Fi.CI.SPARSE: warning for Resolve suspend-resume racing with GuC destroy-context-worker (rev13) Patchwork
2024-01-04  8:43 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-04 10:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-04 17:39   ` Teres Alexis, Alan Previn
2024-01-09 17:41     ` Matt Roper
2024-01-09 22:42     ` Rodrigo Vivi [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=ZZ3Lu05dDTg_kxfk@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=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 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.