public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Ro.CI.BAT: failure for series starting with [1/3] drm/i915/guc: fix GuC loading/submission check
Date: Wed, 8 Jun 2016 09:18:29 +0100	[thread overview]
Message-ID: <5757D4D5.5050701@intel.com> (raw)
In-Reply-To: <20160607200022.GA32344@nuc-i3427.alporthouse.com>

On 07/06/16 21:00, Chris Wilson wrote:
> On Tue, Jun 07, 2016 at 02:23:34PM +0100, Tvrtko Ursulin wrote:
>>
>> On 07/06/16 11:54, Dave Gordon wrote:
>>> On 07/06/16 09:43, Patchwork wrote:
>>>> == Series Details ==
>>>>
>>>> Series: series starting with [1/3] drm/i915/guc: fix GuC
>>>> loading/submission check
>>>> URL   : https://patchwork.freedesktop.org/series/8380/
>>>> State : failure
>>>>
>>>> == Summary ==
>>>>
>>>> Series 8380v1 Series without cover letter
>>>> http://patchwork.freedesktop.org/api/1.0/series/8380/revisions/1/mbox
>>>>
>>>> Test core_auth:
>>>>          Subgroup basic-auth:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>> Test drv_module_reload_basic:
>>>>                  pass       -> DMESG-WARN (ro-byt-n2820)
>>>
>>> Bug 93381 - [BAT BYT] dmesg WARNING in snd-hda
>>>
>>>> Test gem_exec_flush:
>>>>          Subgroup basic-batch-kernel-default-cmd:
>>>>                  pass       -> FAIL       (ro-byt-n2820)
>>>
>>> Bug 95372 - [BAT BYT] Sporadic failure from
>>> igt/gem_exec_flush@basic-batch-kernel-default-cmd
>>>
>>>>          Subgroup basic-uc-ro-default:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>>          Subgroup basic-wb-ro-before-default:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>> Test gem_exec_store:
>>>>          Subgroup basic-bsd:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>> Test gem_mmap_gtt:
>>>>          Subgroup basic-short:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>>          Subgroup basic-write-gtt:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>> Test gem_pwrite:
>>>>          Subgroup basic:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>> Test kms_addfb_basic:
>>>>          Subgroup addfb25-bad-modifier:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>>          Subgroup addfb25-yf-tiled:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>>          Subgroup bad-pitch-0:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>>          Subgroup bad-pitch-1024:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>>          Subgroup basic-x-tiled:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>>          Subgroup basic-y-tiled:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>>          Subgroup clobberred-modifier:
>>>>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>>>>          Subgroup tile-pitch-mismatch:
>>>>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>>>
>>> All the warnings on 'ro-skl-i7-6700hq' appear to be
>>> https://bugs.freedesktop.org/show_bug.cgi?id=95632
>>> "[BAT SKL] *ERROR* Potential atomic update failure on pipe A"
>>>
>>> So all issues accounted for, patchset ready for merge :)
>>>
>>> .Dave.
>>>
>>>> fi-bdw-i7-5557u  total:102  pass:93   dwarn:0   dfail:0   fail:0   skip:8
>>>> fi-hsw-i7-4770k  total:209  pass:190  dwarn:0   dfail:0   fail:0
>>>> skip:19
>>>> fi-skl-i7-6700k  total:209  pass:184  dwarn:0   dfail:0   fail:0
>>>> skip:25
>>>> fi-snb-i7-2600   total:209  pass:170  dwarn:0   dfail:0   fail:0
>>>> skip:39
>>>> ro-bdw-i5-5250u  total:102  pass:93   dwarn:0   dfail:0   fail:0   skip:8
>>>> ro-bdw-i7-5600u  total:102  pass:75   dwarn:0   dfail:0   fail:0
>>>> skip:26
>>>> ro-bsw-n3050     total:209  pass:168  dwarn:0   dfail:0   fail:2
>>>> skip:39
>>>> ro-byt-n2820     total:209  pass:168  dwarn:1   dfail:0   fail:3
>>>> skip:37
>>>> ro-hsw-i3-4010u  total:209  pass:186  dwarn:0   dfail:0   fail:0
>>>> skip:23
>>>> ro-hsw-i7-4770r  total:102  pass:82   dwarn:0   dfail:0   fail:0
>>>> skip:19
>>>> ro-ilk1-i5-650   total:204  pass:146  dwarn:0   dfail:0   fail:1
>>>> skip:57
>>>> ro-skl-i7-6700hq total:204  pass:172  dwarn:11  dfail:0   fail:0
>>>> skip:21
>>>> ro-snb-i7-2620M  total:102  pass:72   dwarn:0   dfail:0   fail:0
>>>> skip:29
>>>> fi-skl-i5-6260u failed to connect after reboot
>>>> ro-bdw-i7-5557U failed to connect after reboot
>>>> ro-ivb2-i7-3770 failed to connect after reboot
>>>> ro-ivb-i7-3770 failed to connect after reboot
>>>>
>>>> Results at /archive/results/CI_IGT_test/RO_Patchwork_1125/
>>>>
>>>> 55d1291 drm-intel-nightly: 2016y-06m-06d-16h-28m-05s UTC integration
>>>> manifest
>>>> 57871c9 drm/i915/guc: enable GuC loading & submission by default
>>>> 3fdd902 drm/i915/guc: disable GuC submission earlier during GuC (re)load
>>>> 5492d57 drm/i915/guc: fix GuC loading/submission check
>>
>> Merged, thanks for the patches and review.
>
> What review? This patch has not addressed my concerns at all.
>
> It is changes the default submission and makes Skylake slower for what
> benefit? The changelog still doesn't explain why we would want to take
> the risk and current regressions.
> -Chris

*"It's Intel POR"*

That means people higher up the foodchain have decided that the GuC is 
the future and the minions have just got to get on with it.

Of course, if it introduces real regressions we'll turn it off again 
until they're resolved, but we're more likely to discover any remaining 
issues with it on by default -- otherwise it's just not getting much 
exposure beyond the in-house validation.

Let's just hope they're all exposed and resolved before September!

.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-06-08  8:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  8:14 [PATCH 1/3] drm/i915/guc: fix GuC loading/submission check Dave Gordon
2016-06-07  8:14 ` [PATCH 2/3] drm/i915/guc: disable GuC submission earlier during GuC (re)load Dave Gordon
2016-06-07  9:51   ` Tvrtko Ursulin
2016-06-07 10:13     ` Dave Gordon
2016-06-07  8:14 ` [PATCH 3/3] drm/i915/guc: enable GuC loading & submission by default Dave Gordon
2016-06-07  9:53   ` Tvrtko Ursulin
2016-06-07  8:41 ` [PATCH 1/3] drm/i915/guc: fix GuC loading/submission check Tvrtko Ursulin
2016-06-09 11:04   ` Tvrtko Ursulin
2016-06-10 15:45     ` Dave Gordon
2016-06-10 16:21     ` [PATCH] drm/i915/guc: suppress GuC-related message on non-GuC platforms Dave Gordon
2016-06-13  9:00       ` Tvrtko Ursulin
2016-06-07  8:43 ` ✗ Ro.CI.BAT: failure for series starting with [1/3] drm/i915/guc: fix GuC loading/submission check Patchwork
2016-06-07 10:54   ` Dave Gordon
2016-06-07 13:23     ` Tvrtko Ursulin
2016-06-07 20:00       ` Chris Wilson
2016-06-08  8:18         ` Dave Gordon [this message]
2016-06-10 16:59 ` ✗ Ro.CI.BAT: failure for series starting with drm/i915/guc: suppress GuC-related message on non-GuC platforms (rev2) Patchwork
2016-06-10 18:14   ` Dave Gordon
2016-06-13  9:06     ` Tvrtko Ursulin

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=5757D4D5.5050701@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.intel.com \
    /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