Use non traceable api in display trace code
Subsystems (3)
cover Use non traceable api in display trace code
Nesting of tracing events should in general be avoided. Many of the display tracing events use the traceable versions of register read/writes. This patchset replaces them with non traceable versions and defines them if required.
This cleanup will be helpful to introduce reg rw tracing of the xe driver.
Radhakrishna Sripada (4):
drm/i915: Add a notrace version of intel_de_read_fw drm/i915: Add a dummy notrace version of intel_de_read64_2x32 drm/i915: Make intel_crtc_get_vblank_counter use no trace hw reads drm/i915: Make intel_get_crtc_scanline use no trace hw reads
drivers/gpu/drm/i915/display/intel_de.h | 17 ++++++++++++++++ drivers/gpu/drm/i915/display/intel_vblank.c | 22 +++++++++++---------- drivers/gpu/drm/i915/intel_uncore.h | 2 ++ 3 files changed, 31 insertions(+), 10 deletions(-)
Signature · 1 line
2.34.1
PATCH 1/4 drm/i915: Add a notrace version of intel_de_read_fw
Around the tracing infrastructure, certain registers are being read resulting in nested traces. Introduce the no trace version of intel_de_read_fw to be used in such scenarios.
--- drivers/gpu/drm/i915/display/intel_de.h | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/gpu/drm/i915/display/intel_de.h +10 -0
@@ -93,6 +93,16 @@ intel_de_wait_for_clear(struct drm_i915_private *i915, i915_reg_t reg,* therefore generally be serialised, by either the dev_priv->uncore.lock or * a more localised lock guarding all access to that bank of registers. */ +static inline u32 +intel_de_read_fw_notrace (struct drm_i915_private *i915,i915_reg_t reg) +{ +u32 val; + + val =intel_uncore_read_fw (&i915->uncore, reg); + +return val; +} +static inline u32 intel_de_read_fw (struct drm_i915_private *i915,i915_reg_t reg) {
Signature · 1 line
2.34.1
PATCH 2/4 drm/i915: Add a dummy notrace version of intel_de_read64_2x32
In reply to Radhakrishna Sripadaintel_de_read64_2x32 and hence intel_uncore_read64_2x32 do not use any of the tracing api's. It is however important to distinguish between the tracing and non tracing versions to avoid nesting of tracing events.
--- drivers/gpu/drm/i915/display/intel_de.h | 7 +++++++ drivers/gpu/drm/i915/intel_uncore.h | 2 ++ 2 files changed, 9 insertions(+)
drivers/gpu/drm/i915/display/intel_de.h +7 -0
@@ -22,6 +22,13 @@ intel_de_read8(struct drm_i915_private *i915, i915_reg_t reg)return intel_uncore_read8 (&i915->uncore, reg); } +static inline u64 +intel_de_read64_2x32_notrace (struct drm_i915_private *i915, +i915_reg_t lower_reg,i915_reg_t upper_reg) +{ +return intel_uncore_read64_2x32_notrace (&i915->uncore, lower_reg, upper_reg); +} +static inline u64 intel_de_read64_2x32 (struct drm_i915_private *i915,i915_reg_t lower_reg,i915_reg_t upper_reg)
drivers/gpu/drm/i915/intel_uncore.h +2 -0
@@ -484,6 +484,8 @@ intel_uncore_read64_2x32(struct intel_uncore *uncore,return (u64 )upper <<32 | lower; } +#define intel_uncore_read64_2x32_notrace (...) intel_uncore_read64_2x32(__VA_ARGS__) +static inline int intel_uncore_write_and_verify (struct intel_uncore *uncore,i915_reg_t reg,u32 val,u32 mask,u32 expected_val)
Signature · 1 line
2.34.1
PATCH 3/4 drm/i915: Make intel_crtc_get_vblank_counter use no trace hw reads
In reply to Radhakrishna Sripadaintel_crtc_get_vblank_counter is used in many places in the display tracing infrastructure. For a clean execution of the tracing assignment, ensure that any necessary HW reads would not further trigger another trace, to prevent nesting of trace events.
--- drivers/gpu/drm/i915/display/intel_vblank.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_vblank.c +4 -3
@@ -103,7 +103,7 @@ u32 i915_get_vblank_counter(struct drm_crtc *crtc)* we get a low value that's stable across two reads of the high * register. */ - frame =intel_de_read64_2x32 (dev_priv,PIPEFRAMEPIXEL (pipe),PIPEFRAME (pipe)); + frame =intel_de_read64_2x32_notrace (dev_priv,PIPEFRAMEPIXEL (pipe),PIPEFRAME (pipe)); pixel = frame &PIPE_PIXEL_MASK ; frame = (frame >>PIPE_FRAME_LOW_SHIFT ) &0xffffff ;
@@ -125,7 +125,7 @@ u32 g4x_get_vblank_counter(struct drm_crtc *crtc)if (!vblank->max_vblank_count)return 0 ; -return intel_de_read (dev_priv,PIPE_FRMCOUNT_G4X (pipe)); +return intel_de_read_notrace (dev_priv,PIPE_FRMCOUNT_G4X (pipe)); }static u32 intel_crtc_scanlines_since_frame_timestamp (struct intel_crtc *crtc)
@@ -324,7 +324,8 @@ static bool i915_get_crtc_scanoutpos(struct drm_crtc *_crtc,* We can split this into vertical and horizontal * scanout position. */ - position = (intel_de_read_fw (dev_priv,PIPEFRAMEPIXEL (pipe)) &PIPE_PIXEL_MASK ) >>PIPE_PIXEL_SHIFT ; + position = (intel_de_read_fw_notrace (dev_priv,PIPEFRAMEPIXEL (pipe)) & +PIPE_PIXEL_MASK ) >>PIPE_PIXEL_SHIFT ;/* convert to pixel counts */ vbl_start *= htotal;
Signature · 1 line
2.34.1
Re: [Intel-gfx] [PATCH 3/4] drm/i915: Make intel_crtc_get_vblank_counter use no trace hw reads
Quoted 4 lines · Radhakrishna Sripada
intel_crtc_get_vblank_counteris used in many places in the display tracing infrastructure. For a clean execution of the tracing assignment, ensure that any necessary HW reads would not further trigger another trace, to prevent nesting of trace events.
it's not clear what "nesting" means in this patch series. For me "nesting" would be if in the middle of a trace event it triggered another trace event. Given our current infra, I don't see how that would be possible.
Do you mean that certain register accesses are being reported twice since they are being recorded in 2 different layers like intel_de and intel_uncore? If so, can you add in the commit message what is the call chain you're seeing? The indirections in intel_de_read_fw() are not so easy to follow, but from a quick look I don't see that happening here.
intel_de_read_fw()
intel_uncore_read_fw()
__raw_uncore_read32() <-- no trace here
trace_i915_reg_rw()
What makes intel_de_read_fw() call special in this intel_vblank.c that is not the case in all the hundred other places this function is called?
The trace_i915_reg_rw() in intel_de_read_fw() was added exactly because __raw_uncore_read32() doesn't trace.
In xe, we should probably override the intel_de_read_fw() with a xe-specific function that just leaves the trace out, delegated to xe_mmio().
Btw, see the comment on top of intel_uncore_read_fw() that nobody reads and calls to those "raw" accessors are added, making the i915_reg_rw trace almost useless.
$ git grep intel_uncore_read_fw | wc -l 65
The _fw() suffix was meant as: you first take the forcewake, then you access a bunch of registers, then release the forcewake. The non-trace is a bad side effect with no clue on the name of the function, just a comment on top of it.
Lucas De Marchi
Quoted 42 lines
Suggested-by Maarten Lankhorst <[email protected]>Signed-off-by Radhakrishna Sripada <[email protected]>---
drivers/gpu/drm/i915/display/intel_vblank.c| 7 ++++---1 file changed, 4 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/display/intel_vblank.c +4
-3@@ -103,7 +103,7 @@ u32 i915_get_vblank_counter(struct drm_crtc *crtc)* we get a low value that's stable across two reads of the high * register. */ - frame =intel_de_read64_2x32 (dev_priv,PIPEFRAMEPIXEL (pipe),PIPEFRAME (pipe)); + frame =intel_de_read64_2x32_notrace (dev_priv,PIPEFRAMEPIXEL (pipe),PIPEFRAME (pipe)); pixel = frame &PIPE_PIXEL_MASK ; frame = (frame >>PIPE_FRAME_LOW_SHIFT ) &0xffffff ;@@ -125,7 +125,7 @@ u32 g4x_get_vblank_counter(struct drm_crtc *crtc)if (!vblank->max_vblank_count)return 0 ; -return intel_de_read (dev_priv,PIPE_FRMCOUNT_G4X (pipe)); +return intel_de_read_notrace (dev_priv,PIPE_FRMCOUNT_G4X (pipe)); }static u32 intel_crtc_scanlines_since_frame_timestamp (struct intel_crtc *crtc)@@ -324,7 +324,8 @@ static bool i915_get_crtc_scanoutpos(struct drm_crtc *_crtc,* We can split this into vertical and horizontal * scanout position. */ - position = (intel_de_read_fw (dev_priv,PIPEFRAMEPIXEL (pipe)) &PIPE_PIXEL_MASK ) >>PIPE_PIXEL_SHIFT ; + position = (intel_de_read_fw_notrace (dev_priv,PIPEFRAMEPIXEL (pipe)) & +PIPE_PIXEL_MASK ) >>PIPE_PIXEL_SHIFT ;/* convert to pixel counts */ vbl_start *= htotal;Signature · 1 line
2.34.1
Re: [Intel-gfx] [PATCH 3/4] drm/i915: Make intel_crtc_get_vblank_counter use no trace hw reads
Hi Lucas,
Quoted 16 lines
-----Original Message-----
From: De Marchi, Lucas <[email protected]>
Sent: Thursday, June 22, 2023 12:41 PM
To: Sripada, Radhakrishna <[email protected]>
Cc: [email protected]; Maarten Lankhorst <[email protected]>
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915: Makeintel_crtc_get_vblank_counteruse no trace hw readsQuoted 4 lines · Radhakrishna Sripada
intel_crtc_get_vblank_counteris used in many places in the display tracing infrastructure. For a clean execution of the tracing assignment, ensure that any necessary HW reads would not further trigger another trace, to prevent nesting of trace events.
Quoted 4 lines
it's not clear what "nesting" means in this patch series. For me "nesting" would be if in the middle of a trace event it triggered another trace event. Given our current infra, I don't see how that would be possible.
Intel_crtc_get_vblank_counter/intel_get_crtc_scanline is used at many of the trace events defined in intel_display_trace.h like intel_pipe_{en,dis}able, intel_pipe_crc during the assign phase to capture the current vblank and scanline values. However those functions indeed use traceable versions of register reads making a nested trace call.
<snip>
kworker/u29:0-153 [007] 402.314951: kernel_stack: => trace_event_raw_event_i915_reg_rw
=> __intel_get_crtc_scanline
=> intel_get_crtc_scanline
=> trace_event_raw_event_intel_plane_update_noarm => intel_plane_update_noarm
=> intel_crtc_planes_update_noarm
=> intel_update_crtc
=> skl_commit_modeset_enables
</snip>
Quoted 6 lines
Do you mean that certain register accesses are being reported twice since they are being recorded in 2 different layers like
intel_deandintel_uncore? If so, can you add in the commit message what is the call chain you're seeing? The indirections inintel_de_read_fw()are not so easy to follow, but from a quick look I don't see that happening here.
I haven't observed those style of reporting twice.
--Radhakrishna(RK) Sripada
Quoted 80 lines
intel_de_read_fw()
intel_uncore_read_fw()__raw_uncore_read32() <-- no trace here
trace_i915_reg_rw()What makes
intel_de_read_fw()call special in thisintel_vblank.cthat is not the case in all the hundred other places this function is called?The
trace_i915_reg_rw()inintel_de_read_fw()was added exactly because__raw_uncore_read32()doesn't trace.In xe, we should probably override the
intel_de_read_fw()with a xe-specific function that just leaves the trace out, delegated toxe_mmio().Btw, see the comment on top of
intel_uncore_read_fw()that nobody reads and calls to those "raw" accessors are added, making thei915_reg_rwtrace almost useless.$ git grep intel_uncore_read_fw | wc -l 65The
_fw()suffix was meant as: you first take the forcewake, then you access a bunch of registers, then release the forcewake. The non-trace is a bad side effect with no clue on the name of the function, just a comment on top of it.Lucas De Marchi
Review
Quoted 8 lines
Suggested-by Maarten Lankhorst <[email protected]>Signed-off-by Radhakrishna Sripada <[email protected]>---
drivers/gpu/drm/i915/display/intel_vblank.c| 7 ++++---1 file changed, 4 insertions(+), 3 deletions(-)(quoted diff) +0
-0
b/drivers/gpu/drm/i915/display/intel_vblank.cdrivers/gpu/drm/i915/display/intel_vblank.c u32 i915_get_vblank_counter(struct drm_crtc *crtc) · line 106
Quoted 8 lines
index
f5659ebd08eb..55f3389fa220100644drivers/gpu/drm/i915/display/intel_vblank.c +0
-1@@ -103,7 +103,7 @@ u32 i915_get_vblank_counter(struct drm_crtc *crtc)* we get a low value that's stable across two reads of the high * register. */ - frame = intel_de_read64_2x32(dev_priv, PIPEFRAMEPIXEL(pipe),PIPEFRAME(pipe));
drivers/gpu/drm/i915/display/intel_vblank.c u32 i915_get_vblank_counter(struct drm_crtc *crtc) · line 106
Quoted 1 line
drivers/gpu/drm/i915/display/intel_vblank.c +1
-0+ frame = intel_de_read64_2x32_notrace(dev_priv,PIPEFRAMEPIXEL(pipe), PIPEFRAME(pipe));
drivers/gpu/drm/i915/display/intel_vblank.c static bool i915_get_crtc_scanoutpos(struct drm_crtc
Quoted 13 lines
drivers/gpu/drm/i915/display/intel_vblank.c +1
-1pixel = frame &PIPE_PIXEL_MASK ; frame = (frame >>PIPE_FRAME_LOW_SHIFT ) &0xffffff ;@@ -125,7 +125,7 @@ u32 g4x_get_vblank_counter(struct drm_crtc *crtc)if (!vblank->max_vblank_count)return 0 ; -return intel_de_read (dev_priv,PIPE_FRMCOUNT_G4X (pipe)); +return intel_de_read_notrace (dev_priv,PIPE_FRMCOUNT_G4X (pipe)); }static u32 intel_crtc_scanlines_since_frame_timestamp (struct intel_crtc *crtc)@@ -324,7 +324,8 @@ static bool i915_get_crtc_scanoutpos(struct drm_crtc
*_crtc,drivers/gpu/drm/i915/display/intel_vblank.c static bool i915_get_crtc_scanoutpos(struct drm_crtc *_crtc,
Quoted 4 lines
drivers/gpu/drm/i915/display/intel_vblank.c +0
-1* We can split this into vertical and horizontal * scanout position. */ - position = (intel_de_read_fw(dev_priv, PIPEFRAMEPIXEL(pipe))&
PIPE_PIXEL_MASK) >>PIPE_PIXEL_SHIFT;drivers/gpu/drm/i915/display/intel_vblank.c static bool i915_get_crtc_scanoutpos(struct drm_crtc · line 327
Quoted 1 line
drivers/gpu/drm/i915/display/intel_vblank.c +1
-0+ position = (intel_de_read_fw_notrace(dev_priv,PIPEFRAMEPIXEL(pipe)) &
Quoted 7 lines
drivers/gpu/drm/i915/display/intel_vblank.c +1
-1+ PIPE_PIXEL_MASK) >> PIPE_PIXEL_SHIFT;/* convert to pixel counts */ vbl_start *= htotal; --2.34.1
PATCH 4/4 drm/i915: Make intel_get_crtc_scanline use no trace hw reads
In reply to Radhakrishna Sripadaintel_get_crtc_scanline is used in the display tracing infrastructure. Use no trace hw reads to avoid nested tracing calls.
--- drivers/gpu/drm/i915/display/intel_vblank.c | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-)
drivers/gpu/drm/i915/display/intel_vblank.c +8 -7
@@ -150,17 +150,17 @@ static u32 intel_crtc_scanlines_since_frame_timestamp(struct intel_crtc *crtc)* pipe frame time stamp. The time stamp value * is sampled at every start of vertical blank. */ - scan_prev_time =intel_de_read_fw (dev_priv, -PIPE_FRMTMSTMP (crtc->pipe)); + scan_prev_time =intel_de_read_fw_notrace (dev_priv, +PIPE_FRMTMSTMP (crtc->pipe));/* * The TIMESTAMP_CTR register has the current * time stamp value. */ - scan_curr_time =intel_de_read_fw (dev_priv,IVB_TIMESTAMP_CTR ); + scan_curr_time =intel_de_read_fw_notrace (dev_priv,IVB_TIMESTAMP_CTR ); - scan_post_time =intel_de_read_fw (dev_priv, -PIPE_FRMTMSTMP (crtc->pipe)); + scan_post_time =intel_de_read_fw_notrace (dev_priv, +PIPE_FRMTMSTMP (crtc->pipe)); }while (scan_post_time != scan_prev_time); return div_u64(mul_u32_u32(scan_curr_time - scan_prev_time,
@@ -217,7 +217,7 @@ static int __intel_get_crtc_scanline(struct intel_crtc *crtc)if (mode->flags &DRM_MODE_FLAG_INTERLACE ) vtotal /=2 ; - position =intel_de_read_fw (dev_priv,PIPEDSL (pipe)) &PIPEDSL_LINE_MASK ; + position =intel_de_read_fw_notrace (dev_priv,PIPEDSL (pipe)) &PIPEDSL_LINE_MASK ;/* * On HSW, the DSL reg (0x70000) appears to return 0 if we
@@ -236,7 +236,8 @@ static int __intel_get_crtc_scanline(struct intel_crtc *crtc)for (i =0 ; i <100 ; i++) {udelay (1 ); - temp =intel_de_read_fw (dev_priv,PIPEDSL (pipe)) &PIPEDSL_LINE_MASK ; + temp =intel_de_read_fw_notrace (dev_priv,PIPEDSL (pipe)) & +PIPEDSL_LINE_MASK ;if (temp != position) { position = temp;break ;
Signature · 1 line
2.34.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use non traceable api in display trace code
In reply to Radhakrishna Sripada== Series Details ==
== Series Details ==
Series: Use non traceable api in display trace code
URL : https://patchwork.freedesktop.org/series/119303/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use non traceable api in display trace code
Why is this going on what do I need to do to secure everything I’m tired of all my devices not working I didn’t ask for this I’ve learned a lot but I’m so frustrated
Quoted 8 lines · On Jun 13, 2023 at 9:02 PM, <Patchwork (mailto:[email protected]…
== Series Details == Series: Use non traceable api in display trace code URL : https://patchwork.freedesktop.org/series/119303/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use non traceable api in display trace code
In reply to PatchworkHow do I do that? I just need to fix all this
Like, how does the system make changes on it when it’s not even plugged in I factory reset it unplug it once you’re done next day it’s like all different settings of configuration files everything
Quoted 8 lines · On Jun 13, 2023 at 9:02 PM, <Patchwork (mailto:[email protected]…
== Series Details == Series: Use non traceable api in display trace code URL : https://patchwork.freedesktop.org/series/119303/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Use non traceable api in display trace code
In reply to Radhakrishna Sripada== Series Details ==
== Series Details ==
Series: Use non traceable api in display trace code
URL : https://patchwork.freedesktop.org/series/119303/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13269 -> Patchwork_119303v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/index.html
Participating hosts (40 -> 39)
------------------------------
Missing (1): fi-snb-2520m
Known issues
------------
Here are the changes found in Patchwork_119303v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@debugfs_test@basic-hwmon:
- bat-adlp-11: NOTRUN -> [SKIP][1] ([i915#7456])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@[email protected]
* igt@gem_tiled_pread_basic:
- bat-adlp-11: NOTRUN -> [SKIP][2] ([i915#3282])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@gem_tiled_pread_basic.html
* igt@i915_selftest@live@gt_mocs:
- bat-mtlp-6: [PASS][3] -> [DMESG-FAIL][4] ([i915#7059])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-mtlp-6/igt@i915_selftest@live@gt_mocs.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-mtlp-6/igt@i915_selftest@live@gt_mocs.html
* igt@i915_selftest@live@migrate:
- bat-mtlp-6: [PASS][5] -> [DMESG-FAIL][6] ([i915#7699])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-mtlp-6/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-mtlp-6/igt@i915_selftest@[email protected]
- bat-dg2-11: [PASS][7] -> [DMESG-WARN][8] ([i915#7699])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-dg2-11/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-dg2-11/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@slpc:
- bat-mtlp-6: [PASS][9] -> [DMESG-WARN][10] ([i915#6367])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-mtlp-6/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-mtlp-6/igt@i915_selftest@[email protected]
- bat-rpls-1: NOTRUN -> [DMESG-WARN][11] ([i915#6367])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-rpls-1/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@workarounds:
- bat-mtlp-6: [PASS][12] -> [DMESG-FAIL][13] ([i915#6763])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-mtlp-6/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-mtlp-6/igt@i915_selftest@[email protected]
* igt@i915_suspend@basic-s3-without-i915:
- bat-rpls-1: NOTRUN -> [ABORT][14] ([i915#6687] / [i915#7978])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-rpls-1/igt@[email protected]
* igt@kms_chamelium_frames@hdmi-crc-fast:
- bat-adlp-11: NOTRUN -> [SKIP][15] ([i915#7828]) +7 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- bat-adlp-11: NOTRUN -> [SKIP][16] ([i915#4103]) +1 similar issue
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@[email protected]
* igt@kms_force_connector_basic@prune-stale-modes:
- bat-adlp-11: NOTRUN -> [SKIP][17] ([i915#4093]) +3 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@[email protected]
* igt@kms_pipe_crc_basic@nonblocking-crc@pipe-d-dp-1:
- bat-dg2-8: [PASS][18] -> [FAIL][19] ([i915#7932])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-dg2-8/igt@kms_pipe_crc_basic@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-dg2-8/igt@kms_pipe_crc_basic@[email protected]
#### Possible fixes ####
* igt@core_auth@basic-auth:
- bat-adlp-11: [ABORT][20] ([i915#8011]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-adlp-11/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@[email protected]
* igt@i915_module_load@load:
- bat-adlp-11: [DMESG-WARN][22] ([i915#4423]) -> [PASS][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-adlp-11/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-adlp-11/igt@[email protected]
* igt@i915_selftest@live@requests:
- bat-mtlp-8: [DMESG-FAIL][24] ([i915#8497]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-mtlp-8/igt@i915_selftest@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-mtlp-8/igt@i915_selftest@[email protected]
- bat-rpls-1: [ABORT][26] ([i915#7911] / [i915#7920]) -> [PASS][27]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-rpls-1/igt@i915_selftest@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-rpls-1/igt@i915_selftest@[email protected]
- bat-mtlp-6: [DMESG-FAIL][28] ([i915#8497]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/bat-mtlp-6/igt@i915_selftest@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/bat-mtlp-6/igt@i915_selftest@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#4093]: https://gitlab.freedesktop.org/drm/intel/issues/4093
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4423]: https://gitlab.freedesktop.org/drm/intel/issues/4423
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6687]: https://gitlab.freedesktop.org/drm/intel/issues/6687
[i915#6763]: https://gitlab.freedesktop.org/drm/intel/issues/6763
[i915#7059]: https://gitlab.freedesktop.org/drm/intel/issues/7059
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#7911]: https://gitlab.freedesktop.org/drm/intel/issues/7911
[i915#7920]: https://gitlab.freedesktop.org/drm/intel/issues/7920
[i915#7932]: https://gitlab.freedesktop.org/drm/intel/issues/7932
[i915#7978]: https://gitlab.freedesktop.org/drm/intel/issues/7978
[i915#8011]: https://gitlab.freedesktop.org/drm/intel/issues/8011
[i915#8497]: https://gitlab.freedesktop.org/drm/intel/issues/8497
Build changes
-------------
* Linux: CI_DRM_13269 -> Patchwork_119303v1
CI-20190529: 20190529
CI_DRM_13269: c73de42e50dc07f5ae9342b28be76f2ee015e5af @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7327: 34e48b7d6402c3d7af19a40d8951eae017cf64df @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_119303v1: c73de42e50dc07f5ae9342b28be76f2ee015e5af @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
55a5a9655460 drm/i915: Make intel_get_crtc_scanline use no trace hw reads aed3fd3496c7 drm/i915: Make intel_crtc_get_vblank_counter use no trace hw reads f70762b01180 drm/i915: Add a dummy notrace version of intel_de_read64_2x32 94ddbaab004c drm/i915: Add a notrace version of intel_de_read_fw
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/index.html
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for Use non traceable api in display trace code
In reply to Radhakrishna Sripada== Series Details ==
== Series Details ==
Series: Use non traceable api in display trace code
URL : https://patchwork.freedesktop.org/series/119303/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13269_full -> Patchwork_119303v1_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (8 -> 7)
------------------------------
Missing (1): shard-rkl0
Known issues
------------
Here are the changes found in Patchwork_119303v1_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_basic@multigpu-create-close:
- shard-rkl: NOTRUN -> [SKIP][1] ([i915#7697]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-tglu: [PASS][2] -> [FAIL][3] ([i915#6268])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-tglu-9/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-2/igt@[email protected]
* igt@gem_eio@hibernate:
- shard-rkl: NOTRUN -> [ABORT][4] ([i915#7975] / [i915#8213])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-rkl: NOTRUN -> [FAIL][5] ([i915#2842])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-glk: [PASS][6] -> [FAIL][7] ([i915#2842])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk5/igt@gem_exec_fair@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@bcs0:
- shard-rkl: [PASS][8] -> [FAIL][9] ([i915#2842]) +3 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-rkl-6/igt@gem_exec_fair@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_reloc@basic-gtt-wc:
- shard-rkl: NOTRUN -> [SKIP][10] ([i915#3281]) +2 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-rkl: NOTRUN -> [SKIP][11] ([i915#2190])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gem_lmem_swapping@heavy-verify-multi-ccs:
- shard-glk: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4613])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk2/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-verify:
- shard-tglu: NOTRUN -> [SKIP][13] ([i915#4613])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-7/igt@[email protected]
* igt@gem_pread@snoop:
- shard-rkl: NOTRUN -> [SKIP][14] ([i915#3282])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gem_pxp@reject-modify-context-protection-off-1:
- shard-rkl: NOTRUN -> [SKIP][15] ([i915#4270])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gem_softpin@evict-snoop-interruptible:
- shard-rkl: NOTRUN -> [SKIP][16] ([fdo#109312])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [PASS][17] -> [ABORT][18] ([i915#5566])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-apl4/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-apl6/igt@[email protected]
* igt@gen9_exec_parse@bb-start-param:
- shard-rkl: NOTRUN -> [SKIP][19] ([i915#2527])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-tglu: [PASS][20] -> [FAIL][21] ([i915#3989] / [i915#454])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-tglu-2/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-6/igt@[email protected]
* igt@kms_big_fb@4-tiled-32bpp-rotate-270:
- shard-rkl: NOTRUN -> [SKIP][22] ([i915#5286])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-90:
- shard-rkl: NOTRUN -> [SKIP][23] ([fdo#111614] / [i915#3638])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip:
- shard-rkl: NOTRUN -> [SKIP][24] ([fdo#110723]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip.html
* igt@kms_big_joiner@basic:
- shard-tglu: NOTRUN -> [SKIP][25] ([i915#2705])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-7/igt@[email protected]
* igt@kms_ccs@pipe-a-bad-aux-stride-yf_tiled_ccs:
- shard-rkl: NOTRUN -> [SKIP][26] ([i915#3734] / [i915#5354] / [i915#6095])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_ccs@pipe-a-bad-aux-stride-yf_tiled_ccs.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs_cc:
- shard-rkl: NOTRUN -> [SKIP][27] ([i915#5354] / [i915#6095]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-rkl: NOTRUN -> [SKIP][28] ([i915#3886] / [i915#5354] / [i915#6095])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][29] ([fdo#109271] / [i915#3886]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk2/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-d-crc-primary-rotation-180-4_tiled_mtl_rc_ccs_cc:
- shard-rkl: NOTRUN -> [SKIP][30] ([i915#5354]) +7 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_ccs@pipe-d-crc-primary-rotation-180-4_tiled_mtl_rc_ccs_cc.html
* igt@kms_chamelium_color@ctm-blue-to-red:
- shard-rkl: NOTRUN -> [SKIP][31] ([fdo#111827])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_chamelium_hpd@dp-hpd:
- shard-rkl: NOTRUN -> [SKIP][32] ([i915#7828])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_content_protection@mei_interface:
- shard-rkl: NOTRUN -> [SKIP][33] ([i915#4579] / [i915#7118])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_content_protection@mei_interface.html
* igt@kms_cursor_crc@cursor-onscreen-512x170:
- shard-rkl: NOTRUN -> [SKIP][34] ([fdo#109279] / [i915#3359])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_cursor_edge_walk@64x64-left-edge@pipe-a-hdmi-a-1:
- shard-glk: [PASS][35] -> [DMESG-FAIL][36] ([i915#118])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk8/igt@kms_cursor_edge_walk@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk8/igt@kms_cursor_edge_walk@[email protected]
* igt@kms_cursor_legacy@short-busy-flip-before-cursor-toggle:
- shard-rkl: NOTRUN -> [SKIP][37] ([i915#4103])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-tglu: [PASS][38] -> [FAIL][39] ([i915#4767])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-tglu-3/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-10/igt@[email protected]
* igt@kms_flip@2x-flip-vs-blocking-wf-vblank:
- shard-rkl: NOTRUN -> [SKIP][40] ([fdo#111825]) +3 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][41] -> [FAIL][42] ([i915#79])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk9/igt@kms_flip@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk5/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-msflip-blt:
- shard-rkl: NOTRUN -> [SKIP][43] ([i915#3023]) +4 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-render:
- shard-rkl: NOTRUN -> [SKIP][44] ([fdo#111825] / [i915#1825]) +6 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbcpsr-tiling-4:
- shard-rkl: NOTRUN -> [SKIP][45] ([i915#5439])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-rkl: NOTRUN -> [SKIP][46] ([i915#3555] / [i915#4579])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-6/igt@[email protected]
* igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c:
- shard-rkl: NOTRUN -> [SKIP][47] ([fdo#109289]) +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_plane_scaling@plane-downscale-with-rotation-factor-0-5@pipe-a-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][48] ([i915#5176]) +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-3/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-b-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][49] ([i915#4579] / [i915#5176]) +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-b-hdmi-a-2.html
* igt@kms_plane_scaling@planes-downscale-factor-0-5-unity-scaling@pipe-b-vga-1:
- shard-snb: NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#4579]) +9 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-snb2/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-75@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][51] ([fdo#109271]) +11 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-snb4/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-a-hdmi-a-1:
- shard-glk: NOTRUN -> [SKIP][52] ([fdo#109271]) +52 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk2/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-a-hdmi-a-1.html
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-rkl: NOTRUN -> [SKIP][53] ([fdo#111068] / [i915#658]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_psr@basic:
- shard-rkl: NOTRUN -> [SKIP][54] ([i915#1072])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_scaling_modes@scaling-mode-full:
- shard-glk: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#4579]) +6 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk2/igt@[email protected]
* igt@kms_setmode@basic@pipe-a-hdmi-a-1:
- shard-snb: NOTRUN -> [FAIL][56] ([i915#5465]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-snb1/igt@kms_setmode@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-apl: [PASS][57] -> [ABORT][58] ([i915#180])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-apl1/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-apl6/igt@[email protected]
* igt@kms_vblank@pipe-c-wait-forked:
- shard-rkl: NOTRUN -> [SKIP][59] ([i915#4070] / [i915#6768])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend:
- shard-rkl: NOTRUN -> [SKIP][60] ([i915#4070] / [i915#533] / [i915#6768]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@[email protected]
* igt@perf@oa-exponents@0-rcs0:
- shard-glk: [PASS][61] -> [ABORT][62] ([i915#5213] / [i915#7941])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk2/igt@perf@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk6/igt@perf@[email protected]
* igt@v3d/v3d_submit_cl@multisync-out-syncs:
- shard-rkl: NOTRUN -> [SKIP][63] ([fdo#109315]) +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@v3d/[email protected]
* igt@v3d/v3d_submit_csd@single-out-sync:
- shard-tglu: NOTRUN -> [SKIP][64] ([fdo#109315] / [i915#2575])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-7/igt@v3d/[email protected]
* igt@vc4/vc4_perfmon@create-two-perfmon:
- shard-rkl: NOTRUN -> [SKIP][65] ([i915#7711]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-1/igt@vc4/[email protected]
#### Possible fixes ####
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-rkl: [FAIL][66] ([i915#6268]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-rkl-6/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-4/igt@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][68] ([i915#2842]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-apl7/igt@gem_exec_fair@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-apl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][70] ([i915#2842]) -> [PASS][71] +1 similar issue
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk1/igt@gem_exec_fair@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-rkl: [FAIL][72] ([i915#2842]) -> [PASS][73] +2 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-rkl-4/igt@gem_exec_fair@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_suspend@basic-s4-devices@smem:
- shard-tglu: [ABORT][74] ([i915#7975] / [i915#8213]) -> [PASS][75]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-tglu-10/igt@gem_exec_suspend@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-7/igt@gem_exec_suspend@[email protected]
* igt@i915_pm_rpm@dpms-mode-unset-lpsp:
- shard-rkl: [SKIP][76] ([i915#1397]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-rkl-1/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-7/igt@[email protected]
* igt@i915_pm_rpm@modeset-non-lpsp:
- {shard-dg1}: [SKIP][78] ([i915#1397]) -> [PASS][79] +2 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-dg1-19/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-dg1-15/igt@[email protected]
* igt@kms_async_flips@alternate-sync-async-flip@pipe-a-hdmi-a-2:
- shard-glk: [FAIL][80] ([i915#2521]) -> [PASS][81]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk9/igt@kms_async_flips@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk5/igt@kms_async_flips@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [FAIL][82] ([i915#2346]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-glk3/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-glk5/igt@[email protected]
* igt@kms_cursor_legacy@single-bo@pipe-b:
- {shard-dg1}: [INCOMPLETE][84] ([i915#8011] / [i915#8347]) -> [PASS][85] +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-dg1-19/igt@kms_cursor_legacy@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-dg1-18/igt@kms_cursor_legacy@[email protected]
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-idle@bcs0:
- shard-tglu: [WARN][86] ([i915#2681]) -> [FAIL][87] ([i915#2681] / [i915#3591])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-tglu-6/igt@i915_pm_rc6_residency@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-tglu-3/igt@i915_pm_rc6_residency@[email protected]
* igt@kms_fbcon_fbt@psr-suspend:
- shard-rkl: [SKIP][88] ([i915#3955]) -> [SKIP][89] ([fdo#110189] / [i915#3955])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-rkl-4/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-2/igt@[email protected]
* igt@kms_multipipe_modeset@basic-max-pipe-crc-check:
- shard-rkl: [SKIP][90] ([i915#4070] / [i915#4816]) -> [SKIP][91] ([i915#4816])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13269/shard-rkl-6/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/shard-rkl-4/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2705]: https://gitlab.freedesktop.org/drm/intel/issues/2705
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#3023]: https://gitlab.freedesktop.org/drm/intel/issues/3023
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4423]: https://gitlab.freedesktop.org/drm/intel/issues/4423
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4816]: https://gitlab.freedesktop.org/drm/intel/issues/4816
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5213]: https://gitlab.freedesktop.org/drm/intel/issues/5213
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5465]: https://gitlab.freedesktop.org/drm/intel/issues/5465
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7461]: https://gitlab.freedesktop.org/drm/intel/issues/7461
[i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697
[i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#7941]: https://gitlab.freedesktop.org/drm/intel/issues/7941
[i915#7975]: https://gitlab.freedesktop.org/drm/intel/issues/7975
[i915#8011]: https://gitlab.freedesktop.org/drm/intel/issues/8011
[i915#8213]: https://gitlab.freedesktop.org/drm/intel/issues/8213
[i915#8234]: https://gitlab.freedesktop.org/drm/intel/issues/8234
[i915#8247]: https://gitlab.freedesktop.org/drm/intel/issues/8247
[i915#8304]: https://gitlab.freedesktop.org/drm/intel/issues/8304
[i915#8347]: https://gitlab.freedesktop.org/drm/intel/issues/8347
Build changes
-------------
* Linux: CI_DRM_13269 -> Patchwork_119303v1
CI-20190529: 20190529
CI_DRM_13269: c73de42e50dc07f5ae9342b28be76f2ee015e5af @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7327: 34e48b7d6402c3d7af19a40d8951eae017cf64df @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_119303v1: c73de42e50dc07f5ae9342b28be76f2ee015e5af @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119303v1/index.html