* [PATCH] drm/i915/color: fix broken display in icl+
@ 2019-10-01 6:31 Swati Sharma
2019-10-01 6:56 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
` (3 more replies)
0 siblings, 4 replies; 9+ messages in thread
From: Swati Sharma @ 2019-10-01 6:31 UTC (permalink / raw)
To: intel-gfx; +Cc: jani.nikula, ankit.k.nautiyal
Premature gamma lut prepration and loading which was getting
reflected in first modeset causing different colors on
screen during boot.
Issue: In BIOS, gamma is disabled by default. However,
legacy_read_luts() was getting called even before the legacy_load_luts()
which was setting crtc_state->base.gamma_lut and gamma_lut was
programmed with junk values which led to visual artifacts (different
colored screens instead of usual black during boot).
Fix: Calling read_luts() only when gamma is enabled which will happen
after first modeset.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111809
Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
---
drivers/gpu/drm/i915/display/intel_display.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
index f1328c08f4ad..f89aa4bb9f42 100644
--- a/drivers/gpu/drm/i915/display/intel_display.c
+++ b/drivers/gpu/drm/i915/display/intel_display.c
@@ -10528,7 +10528,9 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc,
i9xx_get_pipe_color_config(pipe_config);
}
- intel_color_get_config(pipe_config);
+ if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) ||
+ (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable)))
+ intel_color_get_config(pipe_config);
power_domain = POWER_DOMAIN_PIPE_PANEL_FITTER(crtc->pipe);
WARN_ON(power_domain_mask & BIT_ULL(power_domain));
--
2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 9+ messages in thread* ✗ Fi.CI.CHECKPATCH: warning for drm/i915/color: fix broken display in icl+ 2019-10-01 6:31 [PATCH] drm/i915/color: fix broken display in icl+ Swati Sharma @ 2019-10-01 6:56 ` Patchwork 2019-10-01 7:23 ` ✓ Fi.CI.BAT: success " Patchwork ` (2 subsequent siblings) 3 siblings, 0 replies; 9+ messages in thread From: Patchwork @ 2019-10-01 6:56 UTC (permalink / raw) To: Swati Sharma; +Cc: intel-gfx == Series Details == Series: drm/i915/color: fix broken display in icl+ URL : https://patchwork.freedesktop.org/series/67429/ State : warning == Summary == $ dim checkpatch origin/drm-tip 5d9d27e6eccf drm/i915/color: fix broken display in icl+ -:31: WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 24) #31: FILE: drivers/gpu/drm/i915/display/intel_display.c:10531: + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || [...] + intel_color_get_config(pipe_config); -:31: CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around 'pipe_config->gamma_enable' #31: FILE: drivers/gpu/drm/i915/display/intel_display.c:10531: + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) -:32: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #32: FILE: drivers/gpu/drm/i915/display/intel_display.c:10532: + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) total: 0 errors, 1 warnings, 2 checks, 10 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/color: fix broken display in icl+ 2019-10-01 6:31 [PATCH] drm/i915/color: fix broken display in icl+ Swati Sharma 2019-10-01 6:56 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork @ 2019-10-01 7:23 ` Patchwork 2019-10-01 8:03 ` [PATCH] " Jani Nikula 2019-10-01 9:09 ` ✗ Fi.CI.IGT: failure for " Patchwork 3 siblings, 0 replies; 9+ messages in thread From: Patchwork @ 2019-10-01 7:23 UTC (permalink / raw) To: Swati Sharma; +Cc: intel-gfx == Series Details == Series: drm/i915/color: fix broken display in icl+ URL : https://patchwork.freedesktop.org/series/67429/ State : success == Summary == CI Bug Log - changes from CI_DRM_6979 -> Patchwork_14597 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/index.html Changes ------- No changes found Participating hosts (15 -> 44) ------------------------------ Additional (29): fi-kbl-soraka fi-bdw-gvtdvm fi-icl-u2 fi-apl-guc fi-snb-2520m fi-icl-u3 fi-skl-lmem fi-blb-e6850 fi-byt-n2820 fi-icl-guc fi-skl-6600u fi-hsw-4770r fi-bxt-dsi fi-cml-s fi-byt-j1900 fi-glk-dsi fi-bwr-2160 fi-ilk-650 fi-kbl-7500u fi-gdg-551 fi-elk-e7500 fi-skl-6700k2 fi-hsw-peppy fi-cfl-guc fi-whl-u fi-kbl-x1275 fi-cfl-8109u fi-skl-iommu fi-kbl-8809g Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_6979 -> Patchwork_14597 CI-20190529: 20190529 CI_DRM_6979: 46637a3b58ef5e2c0fb6e53b7c50bba8f5de3455 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5208: c0131b4f132acf287d9d05b0f5078003d3159e1c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_14597: 5d9d27e6eccf677042c217f7a1add0b2bb2935fe @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 5d9d27e6eccf drm/i915/color: fix broken display in icl+ == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] drm/i915/color: fix broken display in icl+ 2019-10-01 6:31 [PATCH] drm/i915/color: fix broken display in icl+ Swati Sharma 2019-10-01 6:56 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-10-01 7:23 ` ✓ Fi.CI.BAT: success " Patchwork @ 2019-10-01 8:03 ` Jani Nikula 2019-10-01 14:21 ` Ville Syrjälä 2019-10-01 9:09 ` ✗ Fi.CI.IGT: failure for " Patchwork 3 siblings, 1 reply; 9+ messages in thread From: Jani Nikula @ 2019-10-01 8:03 UTC (permalink / raw) To: Swati Sharma, intel-gfx; +Cc: ankit.k.nautiyal On Tue, 01 Oct 2019, Swati Sharma <swati2.sharma@intel.com> wrote: > Premature gamma lut prepration and loading which was getting > reflected in first modeset causing different colors on > screen during boot. > > Issue: In BIOS, gamma is disabled by default. However, > legacy_read_luts() was getting called even before the legacy_load_luts() > which was setting crtc_state->base.gamma_lut and gamma_lut was > programmed with junk values which led to visual artifacts (different > colored screens instead of usual black during boot). > > Fix: Calling read_luts() only when gamma is enabled which will happen > after first modeset. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111809 I'm confused. Is there a current problem upstream after the revert 1b8588741fdc ("Revert "drm/i915/color: Extract icl_read_luts()"")? Or does this fix a problem that only occurs in conjunction with the reverted commit? Then say so. Note inline. > Signed-off-by: Swati Sharma <swati2.sharma@intel.com> > --- > drivers/gpu/drm/i915/display/intel_display.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c > index f1328c08f4ad..f89aa4bb9f42 100644 > --- a/drivers/gpu/drm/i915/display/intel_display.c > +++ b/drivers/gpu/drm/i915/display/intel_display.c > @@ -10528,7 +10528,9 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc, > i9xx_get_pipe_color_config(pipe_config); > } > > - intel_color_get_config(pipe_config); > + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || > + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) > + intel_color_get_config(pipe_config); Put all of the conditions inside intel_color_get_config(). BR, Jani. > > power_domain = POWER_DOMAIN_PIPE_PANEL_FITTER(crtc->pipe); > WARN_ON(power_domain_mask & BIT_ULL(power_domain)); -- Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] drm/i915/color: fix broken display in icl+ 2019-10-01 8:03 ` [PATCH] " Jani Nikula @ 2019-10-01 14:21 ` Ville Syrjälä 2019-10-01 14:28 ` Sharma, Swati2 2019-10-01 14:31 ` Saarinen, Jani 0 siblings, 2 replies; 9+ messages in thread From: Ville Syrjälä @ 2019-10-01 14:21 UTC (permalink / raw) To: Jani Nikula; +Cc: intel-gfx, ankit.k.nautiyal On Tue, Oct 01, 2019 at 11:03:08AM +0300, Jani Nikula wrote: > On Tue, 01 Oct 2019, Swati Sharma <swati2.sharma@intel.com> wrote: > > Premature gamma lut prepration and loading which was getting > > reflected in first modeset causing different colors on > > screen during boot. > > > > Issue: In BIOS, gamma is disabled by default. However, > > legacy_read_luts() was getting called even before the legacy_load_luts() > > which was setting crtc_state->base.gamma_lut and gamma_lut was > > programmed with junk values which led to visual artifacts (different > > colored screens instead of usual black during boot). > > > > Fix: Calling read_luts() only when gamma is enabled which will happen > > after first modeset. > > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111809 > > I'm confused. Is there a current problem upstream after the revert > 1b8588741fdc ("Revert "drm/i915/color: Extract icl_read_luts()"")? > > Or does this fix a problem that only occurs in conjunction with the > reverted commit? Then say so. > > Note inline. > > > Signed-off-by: Swati Sharma <swati2.sharma@intel.com> > > --- > > drivers/gpu/drm/i915/display/intel_display.c | 4 +++- > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c > > index f1328c08f4ad..f89aa4bb9f42 100644 > > --- a/drivers/gpu/drm/i915/display/intel_display.c > > +++ b/drivers/gpu/drm/i915/display/intel_display.c > > @@ -10528,7 +10528,9 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc, > > i9xx_get_pipe_color_config(pipe_config); > > } > > > > - intel_color_get_config(pipe_config); > > + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || > > + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) > > + intel_color_get_config(pipe_config); > > Put all of the conditions inside intel_color_get_config(). In fact inside the .read_luts() since these checks are platform specific. Also this check is wrong for CHV since it has a separate enable knob for the CGM LUT (gamma_enable only deals with the legacy LUT). -- Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] drm/i915/color: fix broken display in icl+ 2019-10-01 14:21 ` Ville Syrjälä @ 2019-10-01 14:28 ` Sharma, Swati2 2019-10-01 14:36 ` Ville Syrjälä 2019-10-01 14:31 ` Saarinen, Jani 1 sibling, 1 reply; 9+ messages in thread From: Sharma, Swati2 @ 2019-10-01 14:28 UTC (permalink / raw) To: Ville Syrjälä, Jani Nikula; +Cc: intel-gfx, ankit.k.nautiyal On 01-Oct-19 7:51 PM, Ville Syrjälä wrote: > On Tue, Oct 01, 2019 at 11:03:08AM +0300, Jani Nikula wrote: >> On Tue, 01 Oct 2019, Swati Sharma <swati2.sharma@intel.com> wrote: >>> Premature gamma lut prepration and loading which was getting >>> reflected in first modeset causing different colors on >>> screen during boot. >>> >>> Issue: In BIOS, gamma is disabled by default. However, >>> legacy_read_luts() was getting called even before the legacy_load_luts() >>> which was setting crtc_state->base.gamma_lut and gamma_lut was >>> programmed with junk values which led to visual artifacts (different >>> colored screens instead of usual black during boot). >>> >>> Fix: Calling read_luts() only when gamma is enabled which will happen >>> after first modeset. >>> >>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111809 >> >> I'm confused. Is there a current problem upstream after the revert >> 1b8588741fdc ("Revert "drm/i915/color: Extract icl_read_luts()"")? >> >> Or does this fix a problem that only occurs in conjunction with the >> reverted commit? Then say so. >> >> Note inline. >> >>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com> >>> --- >>> drivers/gpu/drm/i915/display/intel_display.c | 4 +++- >>> 1 file changed, 3 insertions(+), 1 deletion(-) >>> >>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c >>> index f1328c08f4ad..f89aa4bb9f42 100644 >>> --- a/drivers/gpu/drm/i915/display/intel_display.c >>> +++ b/drivers/gpu/drm/i915/display/intel_display.c >>> @@ -10528,7 +10528,9 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc, >>> i9xx_get_pipe_color_config(pipe_config); >>> } >>> >>> - intel_color_get_config(pipe_config); >>> + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || >>> + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) >>> + intel_color_get_config(pipe_config); >> >> Put all of the conditions inside intel_color_get_config(). > > In fact inside the .read_luts() since these checks are platform > specific. > > Also this check is wrong for CHV since it has a separate > enable knob for the CGM LUT (gamma_enable only deals with the > legacy LUT) > Inside read_luts() I already have. But the issue is first read_lut() will happen before load_lut() and it will replace crtc_state->base.gamma_lut and gamma_lut will be programmed with junk values which led to multiple colored screens. So we need a check to call intel_color_get_config() itself. -- ~Swati Sharma _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] drm/i915/color: fix broken display in icl+ 2019-10-01 14:28 ` Sharma, Swati2 @ 2019-10-01 14:36 ` Ville Syrjälä 0 siblings, 0 replies; 9+ messages in thread From: Ville Syrjälä @ 2019-10-01 14:36 UTC (permalink / raw) To: Sharma, Swati2; +Cc: Jani Nikula, intel-gfx, ankit.k.nautiyal On Tue, Oct 01, 2019 at 07:58:39PM +0530, Sharma, Swati2 wrote: > On 01-Oct-19 7:51 PM, Ville Syrjälä wrote: > > On Tue, Oct 01, 2019 at 11:03:08AM +0300, Jani Nikula wrote: > >> On Tue, 01 Oct 2019, Swati Sharma <swati2.sharma@intel.com> wrote: > >>> Premature gamma lut prepration and loading which was getting > >>> reflected in first modeset causing different colors on > >>> screen during boot. > >>> > >>> Issue: In BIOS, gamma is disabled by default. However, > >>> legacy_read_luts() was getting called even before the legacy_load_luts() > >>> which was setting crtc_state->base.gamma_lut and gamma_lut was > >>> programmed with junk values which led to visual artifacts (different > >>> colored screens instead of usual black during boot). > >>> > >>> Fix: Calling read_luts() only when gamma is enabled which will happen > >>> after first modeset. > >>> > >>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111809 > >> > >> I'm confused. Is there a current problem upstream after the revert > >> 1b8588741fdc ("Revert "drm/i915/color: Extract icl_read_luts()"")? > >> > >> Or does this fix a problem that only occurs in conjunction with the > >> reverted commit? Then say so. > >> > >> Note inline. > >> > >>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com> > >>> --- > >>> drivers/gpu/drm/i915/display/intel_display.c | 4 +++- > >>> 1 file changed, 3 insertions(+), 1 deletion(-) > >>> > >>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c > >>> index f1328c08f4ad..f89aa4bb9f42 100644 > >>> --- a/drivers/gpu/drm/i915/display/intel_display.c > >>> +++ b/drivers/gpu/drm/i915/display/intel_display.c > >>> @@ -10528,7 +10528,9 @@ static bool haswell_get_pipe_config(struct intel_crtc *crtc, > >>> i9xx_get_pipe_color_config(pipe_config); > >>> } > >>> > >>> - intel_color_get_config(pipe_config); > >>> + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & POST_CSC_GAMMA_ENABLE)) || > >>> + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) > >>> + intel_color_get_config(pipe_config); > >> > >> Put all of the conditions inside intel_color_get_config(). > > > > In fact inside the .read_luts() since these checks are platform > > specific. > > > > Also this check is wrong for CHV since it has a separate > > enable knob for the CGM LUT (gamma_enable only deals with the > > legacy LUT) > > Inside read_luts() I already have. But the issue is first read_lut() > will happen before load_lut() and it will replace > crtc_state->base.gamma_lut and gamma_lut will be programmed with junk > values which led to multiple colored screens. So we need a check to call > intel_color_get_config() itself. That doesn't make sense. If you're already checking these then adding a second check won't change anything. Also state readout is meant to just blindly readout the hardware state. If the LUT used by the BIOS is enabled and not something we want to use then we need to sanitize it after the readout. -- Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] drm/i915/color: fix broken display in icl+ 2019-10-01 14:21 ` Ville Syrjälä 2019-10-01 14:28 ` Sharma, Swati2 @ 2019-10-01 14:31 ` Saarinen, Jani 1 sibling, 0 replies; 9+ messages in thread From: Saarinen, Jani @ 2019-10-01 14:31 UTC (permalink / raw) To: Ville Syrjälä, Nikula, Jani, Palli, Tapani Cc: intel-gfx@lists.freedesktop.org, Nautiyal, Ankit K HI, > -----Original Message----- > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ville Syrjälä > Sent: tiistai 1. lokakuuta 2019 17.21 > To: Nikula, Jani <jani.nikula@intel.com> > Cc: intel-gfx@lists.freedesktop.org; Nautiyal, Ankit K <ankit.k.nautiyal@intel.com> > Subject: Re: [Intel-gfx] [PATCH] drm/i915/color: fix broken display in icl+ > > On Tue, Oct 01, 2019 at 11:03:08AM +0300, Jani Nikula wrote: > > On Tue, 01 Oct 2019, Swati Sharma <swati2.sharma@intel.com> wrote: > > > Premature gamma lut prepration and loading which was getting > > > reflected in first modeset causing different colors on screen during > > > boot. > > > > > > Issue: In BIOS, gamma is disabled by default. However, > > > legacy_read_luts() was getting called even before the > > > legacy_load_luts() which was setting crtc_state->base.gamma_lut and > > > gamma_lut was programmed with junk values which led to visual > > > artifacts (different colored screens instead of usual black during boot). > > > > > > Fix: Calling read_luts() only when gamma is enabled which will > > > happen after first modeset. > > > > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111809 > > > > I'm confused. Is there a current problem upstream after the revert > > 1b8588741fdc ("Revert "drm/i915/color: Extract icl_read_luts()"")? > > > > Or does this fix a problem that only occurs in conjunction with the > > reverted commit? Then say so. > > > > Note inline. > > > > > Signed-off-by: Swati Sharma <swati2.sharma@intel.com> > > > --- > > > drivers/gpu/drm/i915/display/intel_display.c | 4 +++- > > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c > > > b/drivers/gpu/drm/i915/display/intel_display.c > > > index f1328c08f4ad..f89aa4bb9f42 100644 > > > --- a/drivers/gpu/drm/i915/display/intel_display.c > > > +++ b/drivers/gpu/drm/i915/display/intel_display.c > > > @@ -10528,7 +10528,9 @@ static bool haswell_get_pipe_config(struct > intel_crtc *crtc, > > > i9xx_get_pipe_color_config(pipe_config); > > > } > > > > > > - intel_color_get_config(pipe_config); > > > + if ((INTEL_GEN(dev_priv) >= 11 && (pipe_config->gamma_mode & > POST_CSC_GAMMA_ENABLE)) || > > > + (INTEL_GEN(dev_priv) >= 9 && (pipe_config->gamma_enable))) > > > + intel_color_get_config(pipe_config); > > > > Put all of the conditions inside intel_color_get_config(). > > In fact inside the .read_luts() since these checks are platform specific. > > Also this check is wrong for CHV since it has a separate enable knob for the CGM LUT > (gamma_enable only deals with the legacy LUT). Could this be also reason that on BSW I was able to see some color issue with BSW on latest drm-tip still with Tapani? > > -- > Ville Syrjälä > Intel > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
* ✗ Fi.CI.IGT: failure for drm/i915/color: fix broken display in icl+ 2019-10-01 6:31 [PATCH] drm/i915/color: fix broken display in icl+ Swati Sharma ` (2 preceding siblings ...) 2019-10-01 8:03 ` [PATCH] " Jani Nikula @ 2019-10-01 9:09 ` Patchwork 3 siblings, 0 replies; 9+ messages in thread From: Patchwork @ 2019-10-01 9:09 UTC (permalink / raw) To: Swati Sharma; +Cc: intel-gfx == Series Details == Series: drm/i915/color: fix broken display in icl+ URL : https://patchwork.freedesktop.org/series/67429/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6979_full -> Patchwork_14597_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_14597_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_14597_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_14597_full: ### IGT changes ### #### Possible regressions #### * igt@i915_selftest@mock_vma: - shard-skl: [PASS][1] -> [DMESG-WARN][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl9/igt@i915_selftest@mock_vma.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl5/igt@i915_selftest@mock_vma.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * {igt@gem_eio@kms}: - shard-glk: [PASS][3] -> [DMESG-WARN][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-glk1/igt@gem_eio@kms.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-glk2/igt@gem_eio@kms.html Known issues ------------ Here are the changes found in Patchwork_14597_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_isolation@bcs0-s3: - shard-skl: [PASS][5] -> [INCOMPLETE][6] ([fdo#104108]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl9/igt@gem_ctx_isolation@bcs0-s3.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl10/igt@gem_ctx_isolation@bcs0-s3.html * igt@gem_ctx_isolation@rcs0-s3: - shard-apl: [PASS][7] -> [DMESG-WARN][8] ([fdo#108566]) +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-apl1/igt@gem_ctx_isolation@rcs0-s3.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-apl8/igt@gem_ctx_isolation@rcs0-s3.html * igt@gem_eio@in-flight-contexts-1us: - shard-hsw: [PASS][9] -> [FAIL][10] ([fdo#105957]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-hsw5/igt@gem_eio@in-flight-contexts-1us.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-hsw7/igt@gem_eio@in-flight-contexts-1us.html * igt@gem_exec_balancer@smoke: - shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#110854]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb2/igt@gem_exec_balancer@smoke.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb3/igt@gem_exec_balancer@smoke.html * igt@gem_exec_schedule@preempt-other-chain-bsd: - shard-iclb: [PASS][13] -> [SKIP][14] ([fdo#111325]) +8 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb5/igt@gem_exec_schedule@preempt-other-chain-bsd.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb4/igt@gem_exec_schedule@preempt-other-chain-bsd.html * igt@gem_tiled_swapping@non-threaded: - shard-kbl: [PASS][15] -> [DMESG-WARN][16] ([fdo#108686]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-kbl2/igt@gem_tiled_swapping@non-threaded.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-kbl2/igt@gem_tiled_swapping@non-threaded.html * igt@gem_userptr_blits@map-fixed-invalidate-busy: - shard-glk: [PASS][17] -> [DMESG-WARN][18] ([fdo#111870]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-glk5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-glk8/igt@gem_userptr_blits@map-fixed-invalidate-busy.html * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup: - shard-snb: [PASS][19] -> [DMESG-WARN][20] ([fdo#111870]) +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-snb1/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy: - shard-apl: [PASS][21] -> [DMESG-WARN][22] ([fdo#109385] / [fdo#111870]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-apl3/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-apl1/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html * igt@gem_userptr_blits@sync-unmap: - shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([fdo#111870]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-kbl1/igt@gem_userptr_blits@sync-unmap.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-kbl7/igt@gem_userptr_blits@sync-unmap.html - shard-hsw: [PASS][25] -> [DMESG-WARN][26] ([fdo#111870]) [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-hsw7/igt@gem_userptr_blits@sync-unmap.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-hsw4/igt@gem_userptr_blits@sync-unmap.html * igt@kms_cursor_crc@pipe-b-cursor-128x128-onscreen: - shard-skl: [PASS][27] -> [FAIL][28] ([fdo#103232]) [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl2/igt@kms_cursor_crc@pipe-b-cursor-128x128-onscreen.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl6/igt@kms_cursor_crc@pipe-b-cursor-128x128-onscreen.html * igt@kms_cursor_legacy@all-pipes-torture-bo: - shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([fdo#107122]) [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-kbl3/igt@kms_cursor_legacy@all-pipes-torture-bo.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-kbl7/igt@kms_cursor_legacy@all-pipes-torture-bo.html * igt@kms_cursor_legacy@flip-vs-cursor-legacy: - shard-skl: [PASS][31] -> [FAIL][32] ([fdo#102670]) [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-legacy.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-legacy.html * igt@kms_flip@dpms-vs-vblank-race-interruptible: - shard-glk: [PASS][33] -> [FAIL][34] ([fdo#111609]) [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-glk3/igt@kms_flip@dpms-vs-vblank-race-interruptible.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-glk7/igt@kms_flip@dpms-vs-vblank-race-interruptible.html * igt@kms_flip@flip-vs-expired-vblank-interruptible: - shard-skl: [PASS][35] -> [FAIL][36] ([fdo#105363]) [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl2/igt@kms_flip@flip-vs-expired-vblank-interruptible.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl9/igt@kms_flip@flip-vs-expired-vblank-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite: - shard-iclb: [PASS][37] -> [FAIL][38] ([fdo#103167]) +6 similar issues [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence: - shard-skl: [PASS][39] -> [FAIL][40] ([fdo#103191]) [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl2/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence.html [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl6/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence.html * igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min: - shard-skl: [PASS][41] -> [FAIL][42] ([fdo#108145]) [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl2/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl6/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min.html * igt@kms_psr@psr2_sprite_plane_move: - shard-iclb: [PASS][43] -> [SKIP][44] ([fdo#109441]) +2 similar issues [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb7/igt@kms_psr@psr2_sprite_plane_move.html * igt@prime_busy@hang-bsd2: - shard-iclb: [PASS][45] -> [SKIP][46] ([fdo#109276]) +20 similar issues [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb4/igt@prime_busy@hang-bsd2.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb7/igt@prime_busy@hang-bsd2.html #### Possible fixes #### * igt@gem_close@many-handles-one-vma: - shard-snb: [INCOMPLETE][47] ([fdo#105411]) -> [PASS][48] [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-snb5/igt@gem_close@many-handles-one-vma.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-snb1/igt@gem_close@many-handles-one-vma.html * igt@gem_eio@unwedge-stress: - shard-snb: [FAIL][49] ([fdo#109661]) -> [PASS][50] [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-snb4/igt@gem_eio@unwedge-stress.html [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-snb6/igt@gem_eio@unwedge-stress.html * igt@gem_exec_schedule@preempt-queue-bsd1: - shard-iclb: [SKIP][51] ([fdo#109276]) -> [PASS][52] +22 similar issues [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb5/igt@gem_exec_schedule@preempt-queue-bsd1.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd1.html * igt@gem_exec_schedule@reorder-wide-bsd: - shard-iclb: [SKIP][53] ([fdo#111325]) -> [PASS][54] +4 similar issues [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb2/igt@gem_exec_schedule@reorder-wide-bsd.html [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb3/igt@gem_exec_schedule@reorder-wide-bsd.html * igt@gem_userptr_blits@coherency-sync: - shard-snb: [DMESG-WARN][55] ([fdo#111870]) -> [PASS][56] [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-snb7/igt@gem_userptr_blits@coherency-sync.html [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-snb1/igt@gem_userptr_blits@coherency-sync.html * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy: - shard-glk: [DMESG-WARN][57] ([fdo#111870]) -> [PASS][58] +1 similar issue [57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-glk2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html [58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-glk4/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html * igt@gem_userptr_blits@sync-unmap: - shard-iclb: [DMESG-WARN][59] ([fdo#111870]) -> [PASS][60] [59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb8/igt@gem_userptr_blits@sync-unmap.html [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb2/igt@gem_userptr_blits@sync-unmap.html * igt@i915_pm_rpm@system-suspend-modeset: - shard-apl: [INCOMPLETE][61] ([fdo#103927]) -> [PASS][62] +1 similar issue [61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-apl3/igt@i915_pm_rpm@system-suspend-modeset.html [62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-apl3/igt@i915_pm_rpm@system-suspend-modeset.html * igt@i915_selftest@live_gem_contexts: - shard-hsw: [DMESG-FAIL][63] ([fdo#111692]) -> [PASS][64] [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-hsw4/igt@i915_selftest@live_gem_contexts.html [64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-hsw8/igt@i915_selftest@live_gem_contexts.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size: - shard-skl: [FAIL][65] ([fdo#102670]) -> [PASS][66] [65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl10/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html [66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl8/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt: - shard-iclb: [FAIL][67] ([fdo#103167]) -> [PASS][68] +5 similar issues [67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html [68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-render: - shard-iclb: [INCOMPLETE][69] ([fdo#107713]) -> [PASS][70] [69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-render.html [70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-render.html * igt@kms_frontbuffer_tracking@fbc-suspend: - shard-apl: [DMESG-WARN][71] ([fdo#108566]) -> [PASS][72] +7 similar issues [71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html [72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu: - shard-skl: [FAIL][73] ([fdo#103167]) -> [PASS][74] [73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl4/igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu.html [74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl1/igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu.html * igt@kms_plane@plane-panning-bottom-right-pipe-a-planes: - shard-skl: [FAIL][75] ([fdo#103166]) -> [PASS][76] [75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl4/igt@kms_plane@plane-panning-bottom-right-pipe-a-planes.html [76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl1/igt@kms_plane@plane-panning-bottom-right-pipe-a-planes.html * igt@kms_plane_alpha_blend@pipe-a-coverage-7efc: - shard-skl: [FAIL][77] ([fdo#108145]) -> [PASS][78] [77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl4/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html [78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl1/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html * igt@kms_plane_multiple@atomic-pipe-b-tiling-y: - shard-skl: [DMESG-WARN][79] ([fdo#106885]) -> [PASS][80] [79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl1/igt@kms_plane_multiple@atomic-pipe-b-tiling-y.html [80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl10/igt@kms_plane_multiple@atomic-pipe-b-tiling-y.html * igt@kms_psr@psr2_cursor_mmap_cpu: - shard-iclb: [SKIP][81] ([fdo#109441]) -> [PASS][82] +2 similar issues [81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb8/igt@kms_psr@psr2_cursor_mmap_cpu.html [82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html * igt@kms_setmode@basic: - shard-apl: [FAIL][83] ([fdo#99912]) -> [PASS][84] [83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-apl7/igt@kms_setmode@basic.html [84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-apl4/igt@kms_setmode@basic.html * igt@kms_vblank@pipe-b-query-forked-hang: - shard-hsw: [INCOMPLETE][85] ([fdo#103540]) -> [PASS][86] [85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-hsw8/igt@kms_vblank@pipe-b-query-forked-hang.html [86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-hsw1/igt@kms_vblank@pipe-b-query-forked-hang.html * igt@perf@polling: - shard-skl: [FAIL][87] ([fdo#110728]) -> [PASS][88] [87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl2/igt@perf@polling.html [88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-skl9/igt@perf@polling.html * igt@perf@short-reads: - shard-kbl: [FAIL][89] ([fdo#103183]) -> [PASS][90] [89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-kbl1/igt@perf@short-reads.html [90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-kbl1/igt@perf@short-reads.html #### Warnings #### * igt@gem_mocs_settings@mocs-reset-bsd2: - shard-iclb: [FAIL][91] ([fdo#111330]) -> [SKIP][92] ([fdo#109276]) +1 similar issue [91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-iclb1/igt@gem_mocs_settings@mocs-reset-bsd2.html [92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-iclb3/igt@gem_mocs_settings@mocs-reset-bsd2.html * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup: - shard-apl: [DMESG-WARN][93] ([fdo#109385]) -> [DMESG-WARN][94] ([fdo#109385] / [fdo#111870]) +1 similar issue [93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-apl7/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html [94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-apl4/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html * igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes: - shard-kbl: [INCOMPLETE][95] ([fdo#103665]) -> [DMESG-WARN][96] ([fdo#108566]) [95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-kbl3/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html [96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/shard-kbl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#102670]: https://bugs.freedesktop.org/show_bug.cgi?id=102670 [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166 [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103183]: https://bugs.freedesktop.org/show_bug.cgi?id=103183 [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191 [fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232 [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540 [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665 [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 [fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108 [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363 [fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411 [fdo#105957]: https://bugs.freedesktop.org/show_bug.cgi?id=105957 [fdo#106885]: https://bugs.freedesktop.org/show_bug.cgi?id=106885 [fdo#107122]: https://bugs.freedesktop.org/show_bug.cgi?id=107122 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#108686]: http == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14597/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2019-10-01 14:36 UTC | newest] Thread overview: 9+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-10-01 6:31 [PATCH] drm/i915/color: fix broken display in icl+ Swati Sharma 2019-10-01 6:56 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-10-01 7:23 ` ✓ Fi.CI.BAT: success " Patchwork 2019-10-01 8:03 ` [PATCH] " Jani Nikula 2019-10-01 14:21 ` Ville Syrjälä 2019-10-01 14:28 ` Sharma, Swati2 2019-10-01 14:36 ` Ville Syrjälä 2019-10-01 14:31 ` Saarinen, Jani 2019-10-01 9:09 ` ✗ Fi.CI.IGT: failure for " Patchwork
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.