drm/i915/guc: WA to address the Ringbuffer coherency issue
Subsystems (2)
PATCH 1/1 drm/i915/guc: WA to address the Ringbuffer coherency issue
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get commited to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA in i915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.
--- drivers/gpu/drm/i915/i915_guc_submission.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/gpu/drm/i915/i915_guc_submission.c +6 -0
@@ -601,6 +601,7 @@ static int guc_ring_doorbell(struct i915_guc_client *gc)*/ static void i915_guc_submit (struct drm_i915_gem_request *rq) { +struct drm_i915_private *dev_priv = rq->i915;unsigned int engine_id = rq->engine->id;struct intel_guc *guc = &rq->i915->guc;struct i915_guc_client *client = guc->execbuf_client;
@@ -608,6 +609,11 @@ static void i915_guc_submit(struct drm_i915_gem_request *rq)spin_lock (&client->wq_lock);guc_wq_item_append (client, rq); + +/* WA to flush out the pending GMADR writes to ring buffer. */ +if (i915_vma_is_map_and_fenceable (rq->ring->vma)) +POSTING_READ (GUC_STATUS ); + b_ret =guc_ring_doorbell (client); client->submissions[engine_id] +=1 ;
Signature · 6 lines
1.9.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 8 lines · On Fri, Oct 14, 2016 at 11:53:44PM +0530, [email protected] wrote:
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get commited to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
Please leave a blank line between paragraphs, or try to not leave so much whitespace at the end of a sentence.
Quoted 34 lines
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA ini915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.Cc Chris Wilson <[email protected]>Signed-off-by Sagar Arun Kamble <[email protected]>Signed-off-by Akash Goel <[email protected]>--- drivers/gpu/drm/i915/i915_guc_submission.c | 6 ++++++ 1 file changed, 6 insertions(+)drivers/gpu/drm/i915/i915_guc_submission.c +1
-0@@ -601,6 +601,7 @@ static int guc_ring_doorbell(struct i915_guc_client *gc)*/ static void i915_guc_submit (struct drm_i915_gem_request *rq) { +struct drm_i915_private *dev_priv = rq->i915;unsigned int engine_id = rq->engine->id;struct intel_guc *guc = &rq->i915->guc;struct i915_guc_client *client = guc->execbuf_client;
drivers/gpu/drm/i915/i915_guc_submission.c static void i915_guc_submit(struct drm_i915_gem_request *rq) · line 615
Quoted 7 lines
drivers/gpu/drm/i915/i915_guc_submission.c +4
-0@@ -608,6 +609,11 @@ static void i915_guc_submit(struct drm_i915_gem_request *rq)spin_lock (&client->wq_lock);guc_wq_item_append (client, rq); + +/* WA to flush out the pending GMADR writes to ring buffer. */ +if (i915_vma_is_map_and_fenceable (rq->ring->vma)) +POSTING_READ (GUC_STATUS );
Did you test POSTING_READ_FW() ?
Otherwise it makes an unfortunate amount of sense, and I feel justified in what I had to do in flush_gtt_write_domwin! :)
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 10 lines · Chris Wilson
Quoted 8 lines · On Fri, Oct 14, 2016 at 11:53:44PM +0530, [email protected] wrote:
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get commited to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
Quoted 3 lines
Please leave a blank line between paragraphs, or try to not leave so much whitespace at the end of a sentence.
I am sorry. Will be mindful of this from now.
Quoted 35 lines
Quoted 35 lines
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA ini915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.Cc Chris Wilson <[email protected]>Signed-off-by Sagar Arun Kamble <[email protected]>Signed-off-by Akash Goel <[email protected]>--- drivers/gpu/drm/i915/i915_guc_submission.c | 6 ++++++ 1 file changed, 6 insertions(+)drivers/gpu/drm/i915/i915_guc_submission.c +1
-0@@ -601,6 +601,7 @@ static int guc_ring_doorbell(struct i915_guc_client *gc)*/ static void i915_guc_submit (struct drm_i915_gem_request *rq) { +struct drm_i915_private *dev_priv = rq->i915;unsigned int engine_id = rq->engine->id;struct intel_guc *guc = &rq->i915->guc;struct i915_guc_client *client = guc->execbuf_client;@@ -608,6 +609,11 @@ static void i915_guc_submit(struct drm_i915_gem_request *rq)
Quoted 8 lines
drivers/gpu/drm/i915/i915_guc_submission.c static void i915_guc_submit(struct drm_i915_gem_request *rq) · line 615
Quoted 6 lines
drivers/gpu/drm/i915/i915_guc_submission.c +4
-0spin_lock (&client->wq_lock);guc_wq_item_append (client, rq); + +/* WA to flush out the pending GMADR writes to ring buffer. */ +if (i915_vma_is_map_and_fenceable (rq->ring->vma)) +POSTING_READ (GUC_STATUS );Did you test
POSTING_READ_FW()?
Sorry though we haven't explicitly tried POSTING_READ_FW() but it should work since, as per the __gen9_fw_ranges[] table, GuC registers (C000-Cxxx) do not lie in any Forcewake domain range.
Quoted 3 lines
Otherwise it makes an unfortunate amount of sense, and I feel justified in what I had to do in
flush_gtt_write_domwin! :)
Yes your hunch, expectedly, was spot on :).
Best regards
Akash
Quoted 2 lines
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v2 1/1 drm/i915/guc: WA to address the Ringbuffer coherency issue
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get committed to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in-flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA in i915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.
v2:
- Use POSTING_READ_FW instead of POSTING_READ as GuC register do not lie in any forcewake domain range and so the overhead of spinlock & search in the forcewake table is avoidable. (Chris)
--- drivers/gpu/drm/i915/i915_guc_submission.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/gpu/drm/i915/i915_guc_submission.c +6 -0
@@ -634,6 +634,7 @@ static int guc_ring_doorbell(struct i915_guc_client *gc)*/ static void i915_guc_submit (struct drm_i915_gem_request *rq) { +struct drm_i915_private *dev_priv = rq->i915;unsigned int engine_id = rq->engine->id;struct intel_guc *guc = &rq->i915->guc;struct i915_guc_client *client = guc->execbuf_client;
@@ -641,6 +642,11 @@ static void i915_guc_submit(struct drm_i915_gem_request *rq)spin_lock (&client->wq_lock);guc_wq_item_append (client, rq); + +/* WA to flush out the pending GMADR writes to ring buffer. */ +if (i915_vma_is_map_and_fenceable (rq->ring->vma)) +POSTING_READ_FW (GUC_STATUS ); + b_ret =guc_ring_doorbell (client); client->submissions[engine_id] +=1 ;
Signature · 6 lines
1.9.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 24 lines · On Tue, Oct 25, 2016 at 10:05:23PM +0530, [email protected] wrote:
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get committed to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in-flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA ini915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.
Quoted 8 lines
v2:
- UsePOSTING_READ_FWinstead ofPOSTING_READas GuC register do not lie in any forcewake domain range and so the overhead of spinlock & search in the forcewake table is avoidable. (Chris)Cc Chris Wilson <[email protected]>Signed-off-by Sagar Arun Kamble <[email protected]>Signed-off-by Akash Goel <[email protected]>
Thanks for respinning, reviewed and pushed.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 30 lines · Chris Wilson
Quoted 29 lines · On Tue, Oct 25, 2016 at 10:05:23PM +0530, [email protected] wrote:
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get committed to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in-flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA ini915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.v2:
- UsePOSTING_READ_FWinstead ofPOSTING_READas GuC register do not lie in any forcewake domain range and so the overhead of spinlock & search in the forcewake table is avoidable. (Chris)
Quoted 5 lines
Quoted 3 lines
Cc Chris Wilson <[email protected]>Signed-off-by Sagar Arun Kamble <[email protected]>Signed-off-by Akash Goel <[email protected]>Thanks for respinning, reviewed and pushed.
No CI run with GuC enabled, or even any CI run?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 32 lines · Tvrtko Ursulin
Quoted 30 lines · Chris Wilson
Quoted 29 lines · On Tue, Oct 25, 2016 at 10:05:23PM +0530, [email protected] wrote:
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get committed to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in-flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA ini915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.v2:
- UsePOSTING_READ_FWinstead ofPOSTING_READas GuC register do not lie in any forcewake domain range and so the overhead of spinlock & search in the forcewake table is avoidable. (Chris)
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Cc Chris Wilson <[email protected]>Signed-off-by Sagar Arun Kamble <[email protected]>Signed-off-by Akash Goel <[email protected]>Thanks for respinning, reviewed and pushed.
No CI run with GuC enabled, or even any CI run?
There were on previous versions. But yes, I am that confident that this is not broken and matches the failure we have seen in BAT for other GTT vs physical access (on different machines on different paths).
The only qualm I had was the use of is_mappable() to decide if we are writing through the GTT. ring->vma->obj->stolen might be better, or a ring->ggtt_writes flag. I wanted to fix the bug first, repaint later. -Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 37 lines · Chris Wilson
Quoted 36 lines · Tvrtko Ursulin
Quoted 34 lines · Chris Wilson
Quoted 32 lines · On Tue, Oct 25, 2016 at 10:05:23PM +0530, [email protected] wrote:
From: Akash Goel <[email protected]>
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are pinned in mappable aperture portion of GGTT and for ringbuffer pages allocated from Stolen memory, access can only be done through GMADR BAR. In case of GuC based submission, updates done in ringbuffer via GMADR may not get committed to memory by the time the Command streamer starts reading them, resulting in fetching of stale data.
For Host based submission, such problem is not there as the write to Ring Tail or ELSP register happens from the Host side prior to submission. Access to any GFX register from CPU side goes to GTTMMADR BAR and Hw already enforces the ordering between outstanding GMADR writes & new GTTMADR access. MMIO writes from GuC side do not go to GTTMMADR BAR as GuC communication to registers within GT is contained within GT, so ordering is not enforced resulting in a race, which can manifest in form of a hang.
To ensure the flush of in-flight GMADR writes, a POSTING READ is done to GuC register prior to doorbell ring.
There is already a similar WA ini915_gem_object_flush_gtt_write_domain(), which takes care of GMADR writes from User space to GEM buffers, but not the ringbuffer writes from KMD.
This WA is needed on all recent HW.v2:
- UsePOSTING_READ_FWinstead ofPOSTING_READas GuC register do not lie in any forcewake domain range and so the overhead of spinlock & search in the forcewake table is avoidable. (Chris)Cc Chris Wilson <[email protected]>Signed-off-by Sagar Arun Kamble <[email protected]>Signed-off-by Akash Goel <[email protected]>
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
Thanks for respinning, reviewed and pushed.
No CI run with GuC enabled, or even any CI run?
There were on previous versions. But yes, I am that confident that
No with the added code exercised afaict.
Quoted 6 lines
this is not broken and matches the failure we have seen in BAT for other GTT vs physical access (on different machines on different paths).
The only qualm I had was the use of
is_mappable()to decide if we are writing through the GTT.ring->vma->obj->stolenmight be better, or aring->ggtt_writesflag. I wanted to fix the bug first, repaint later.
It looks fine to me as well, and I know Akash tested it extensively.
However process and all that.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: warning for drm/i915/guc: WA to address the Ringbuffer coherency issue
In reply to [email protected]== Series Details ==
== Series Details ==
Series: drm/i915/guc: WA to address the Ringbuffer coherency issue
URL : https://patchwork.freedesktop.org/series/13807/
State : warning
== Summary ==
Series 13807v1 drm/i915/guc: WA to address the Ringbuffer coherency issue
https://patchwork.freedesktop.org/api/1.0/series/13807/revisions/1/mbox/
Test drv_module_reload_basic:
pass -> SKIP (fi-bdw-5557u)
Test kms_flip:
Subgroup basic-flip-vs-wf_vblank:
dmesg-warn -> PASS (fi-skl-6700k)
dmesg-warn -> PASS (fi-skl-6770hq)
Test kms_pipe_crc_basic:
Subgroup read-crc-pipe-a-frame-sequence:
dmesg-warn -> PASS (fi-ilk-650)
Subgroup read-crc-pipe-b:
dmesg-warn -> PASS (fi-ilk-650)
Subgroup suspend-read-crc-pipe-c:
incomplete -> PASS (fi-skl-6700k)
Test vgem_basic:
Subgroup unload:
skip -> PASS (fi-skl-6770hq)
pass -> SKIP (fi-hsw-4770)fi-bdw-5557u total:246 pass:230 dwarn:0 dfail:0 fail:0 skip:16 fi-bsw-n3050 total:246 pass:204 dwarn:0 dfail:0 fail:0 skip:42 fi-bxt-t5700 total:246 pass:216 dwarn:0 dfail:0 fail:0 skip:30 fi-byt-n2820 total:246 pass:210 dwarn:0 dfail:0 fail:1 skip:35 fi-hsw-4770 total:246 pass:223 dwarn:0 dfail:0 fail:0 skip:23 fi-hsw-4770r total:246 pass:224 dwarn:0 dfail:0 fail:0 skip:22 fi-ilk-650 total:246 pass:184 dwarn:0 dfail:0 fail:2 skip:60 fi-ivb-3520m total:246 pass:221 dwarn:0 dfail:0 fail:0 skip:25 fi-ivb-3770 total:246 pass:221 dwarn:0 dfail:0 fail:0 skip:25 fi-kbl-7200u total:246 pass:222 dwarn:0 dfail:0 fail:0 skip:24 fi-skl-6260u total:246 pass:232 dwarn:0 dfail:0 fail:0 skip:14 fi-skl-6700hq total:246 pass:223 dwarn:0 dfail:0 fail:0 skip:23 fi-skl-6700k total:246 pass:221 dwarn:1 dfail:0 fail:0 skip:24 fi-skl-6770hq total:246 pass:230 dwarn:1 dfail:0 fail:1 skip:14 fi-snb-2520m total:246 pass:210 dwarn:0 dfail:0 fail:0 skip:36 fi-snb-2600 total:246 pass:209 dwarn:0 dfail:0 fail:0 skip:37
fi-byt-j1900 failed to connect after reboot
Results at /archive/results/CI_IGT_test/Patchwork_2728/
38ecbe9082e477953fe165265c76e6c6061aeaf6 drm-intel-nightly: 2016y-10m-14d-16h-23m-48s UTC integration manifest 86dd25f drm/i915/guc: WA to address the Ringbuffer coherency issue
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: warning for drm/i915/guc: WA to address the Ringbuffer coherency issue (rev2)
In reply to [email protected]== Series Details ==
== Series Details ==
Series: drm/i915/guc: WA to address the Ringbuffer coherency issue (rev2)
URL : https://patchwork.freedesktop.org/series/13807/
State : warning
== Summary ==
Series 13807v2 drm/i915/guc: WA to address the Ringbuffer coherency issue
https://patchwork.freedesktop.org/api/1.0/series/13807/revisions/2/mbox/
Test drv_module_reload_basic:
pass -> DMESG-WARN (fi-skl-6700hq)
dmesg-warn -> PASS (fi-skl-6770hq)
Test gem_exec_suspend:
Subgroup basic-s3:
dmesg-warn -> PASS (fi-skl-6700hq)
dmesg-warn -> PASS (fi-skl-6770hq)
Test kms_frontbuffer_tracking:
Subgroup basic:
fail -> PASS (fi-skl-6770hq)
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-a:
dmesg-warn -> PASS (fi-skl-6700hq)
pass -> DMESG-WARN (fi-ilk-650)
Subgroup suspend-read-crc-pipe-b:
dmesg-warn -> PASS (fi-skl-6700hq)
Subgroup suspend-read-crc-pipe-c:
dmesg-warn -> PASS (fi-skl-6700hq)fi-bdw-5557u total:246 pass:231 dwarn:0 dfail:0 fail:0 skip:15 fi-bsw-n3050 total:246 pass:204 dwarn:0 dfail:0 fail:0 skip:42 fi-bxt-t5700 total:246 pass:216 dwarn:0 dfail:0 fail:0 skip:30 fi-byt-j1900 total:246 pass:215 dwarn:0 dfail:0 fail:0 skip:31 fi-byt-n2820 total:246 pass:211 dwarn:0 dfail:0 fail:0 skip:35 fi-hsw-4770 total:246 pass:224 dwarn:0 dfail:0 fail:0 skip:22 fi-hsw-4770r total:246 pass:223 dwarn:0 dfail:0 fail:0 skip:23 fi-ilk-650 total:246 pass:184 dwarn:1 dfail:0 fail:0 skip:61 fi-ivb-3520m total:246 pass:220 dwarn:0 dfail:0 fail:0 skip:26 fi-ivb-3770 total:246 pass:220 dwarn:0 dfail:0 fail:0 skip:26 fi-kbl-7200u total:246 pass:222 dwarn:0 dfail:0 fail:0 skip:24 fi-skl-6260u total:246 pass:232 dwarn:0 dfail:0 fail:0 skip:14 fi-skl-6700hq total:246 pass:222 dwarn:1 dfail:0 fail:0 skip:23 fi-skl-6700k total:246 pass:222 dwarn:1 dfail:0 fail:0 skip:23 fi-skl-6770hq total:246 pass:232 dwarn:0 dfail:0 fail:0 skip:14 fi-snb-2520m total:246 pass:209 dwarn:0 dfail:0 fail:0 skip:37 fi-snb-2600 total:246 pass:208 dwarn:0 dfail:0 fail:0 skip:38
3ce99d02d8f2b7d1414d20d5972f8e277b33693e drm-intel-nightly: 2016y-10m-25d-13h-55m-46s UTC integration manifest c503679 drm/i915/guc: WA to address the Ringbuffer coherency issue
Full results at https://intel-gfx-ci.01.org/CI/Patchwork_2814/
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_2814/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx