From: Sujaritha <sujaritha.sundaresan@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Patchwork <patchwork@emeril.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/guc: GuC suspend path cleanup
Date: Thu, 21 Mar 2019 12:41:17 -0700 [thread overview]
Message-ID: <293b004b-c721-6d59-c877-14467c452abb@intel.com> (raw)
In-Reply-To: <155319706730.26447.17646824149329779340@skylake-alporthouse-com>
On 3/21/19 12:37 PM, Chris Wilson wrote:
> Quoting Patchwork (2019-03-21 19:26:27)
>> == Series Details ==
>>
>> Series: drm/i915/guc: GuC suspend path cleanup
>> URL : https://patchwork.freedesktop.org/series/58370/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_5789 -> Patchwork_12553
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with Patchwork_12553 absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in Patchwork_12553, please notify your bug team to allow them
>> to document this new failure mode, which will reduce false positives in CI.
>>
>> External URL: https://patchwork.freedesktop.org/api/1.0/series/58370/revisions/1/mbox/
>>
>> Possible new issues
>> -------------------
>>
>> Here are the unknown changes that may have been introduced in Patchwork_12553:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>> * igt@gem_exec_suspend@basic-s3:
>> - fi-apl-guc: PASS -> DMESG-WARN
> That says we turned the guc off before completing the idle sequence, so
> the intel_uc_suspend() has to be after the flush_workqueues.
> -Chris
But shouldn't this be taken care of by the switch_to_kernel_context_sync ?
And would be better have uc_suspend after drain_delayed_work instead of
just after flush_workqueue ?
-Sujaritha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-21 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 17:14 [PATCH] drm/i915/guc: GuC suspend path cleanup Sujaritha Sundaresan
2019-03-21 17:49 ` Daniele Ceraolo Spurio
2019-03-21 17:54 ` Chris Wilson
2019-03-21 19:46 ` Sujaritha
2019-03-21 19:26 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-03-21 19:37 ` Chris Wilson
2019-03-21 19:41 ` Sujaritha [this message]
2019-03-21 20:08 ` Chris Wilson
2019-03-21 20:02 ` Sujaritha
2019-03-21 20:23 ` Chris Wilson
2019-03-21 20:28 ` Sujaritha
2019-03-21 20:38 ` [PATCH v2] " Sujaritha Sundaresan
2019-03-22 8:57 ` Chris Wilson
2019-03-22 9:39 ` Chris Wilson
2019-03-22 0:28 ` ✓ Fi.CI.BAT: success for drm/i915/guc: GuC suspend path cleanup (rev2) Patchwork
2019-03-22 18:12 ` ✓ Fi.CI.IGT: " 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=293b004b-c721-6d59-c877-14467c452abb@intel.com \
--to=sujaritha.sundaresan@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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.