From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Arun Siluvery <arun.siluvery@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: warning for drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateClear (rev2)
Date: Mon, 6 Jun 2016 13:05:19 +0100 [thread overview]
Message-ID: <575566FF.7060403@linux.intel.com> (raw)
In-Reply-To: <57554A66.9030701@linux.intel.com>
On 06/06/16 11:03, Arun Siluvery wrote:
> On 06/06/2016 14:58, Patchwork wrote:
>> == Series Details ==
>>
>> Series: drm/i915/gen9: Add
>> WaVFEStateAfterPipeControlwithMediaStateClear (rev2)
>> URL : https://patchwork.freedesktop.org/series/8218/
>> State : warning
>>
>> == Summary ==
>>
>> Series 8218v2 drm/i915/gen9: Add
>> WaVFEStateAfterPipeControlwithMediaStateClear
>> http://patchwork.freedesktop.org/api/1.0/series/8218/revisions/2/mbox
>>
>> Test gem_basic:
>> Subgroup create-close:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Test gem_busy:
>> Subgroup basic-parallel-bsd:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Test gem_close_race:
>> Subgroup basic-threads:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Test gem_cs_tlb:
>> Subgroup basic-default:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Test gem_ctx_param:
>> Subgroup basic:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Test gem_exec_flush:
>> Subgroup basic-uc-set-default:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Test gem_flink_basic:
>> Subgroup basic:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Test gem_mmap_gtt:
>> Subgroup basic-small-copy-xy:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Subgroup basic-write:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Subgroup basic-write-gtt:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Test kms_addfb_basic:
>> Subgroup addfb25-x-tiled-mismatch:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Subgroup bad-pitch-65536:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Subgroup bo-too-small:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Subgroup no-handle:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>> Subgroup too-high:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Subgroup unused-modifier:
>> dmesg-warn -> PASS (ro-skl-i7-6700hq)
>> Subgroup unused-offsets:
>> pass -> DMESG-WARN (ro-skl-i7-6700hq)
>>
>
> All dmesg-warn are because of a single known issue,
>
> [BAT SKL] *ERROR* Potential atomic update failure on pipe A
> https://bugs.freedesktop.org/show_bug.cgi?id=95632
Merged, thanks for the patch and review.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-06 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 11:40 [PATCH] drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateClear Arun Siluvery
2016-06-03 12:04 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-06-03 12:15 ` Patchwork
2016-06-03 23:34 ` [PATCH] " Jeff McGee
2016-06-06 8:52 ` [RESEND_FOR_CI] " Arun Siluvery
2016-06-06 9:28 ` ✗ Ro.CI.BAT: warning for drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateClear (rev2) Patchwork
2016-06-06 10:03 ` Arun Siluvery
2016-06-06 12:05 ` Tvrtko Ursulin [this message]
2017-11-01 22:44 ` [PATCH] drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateClear Chris Wilson
2017-11-08 13:03 ` Joonas Lahtinen
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=575566FF.7060403@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=arun.siluvery@linux.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;
as well as URLs for NNTP newsgroup(s).