| Message ID | 20200218230822.66801-1-jose.souza@intel.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | drm/i915/tgl: Remove require_force_probe protection | expand |
On Tue, Feb 18, 2020 at 03:08:22PM -0800, José Roberto de Souza wrote: > We have a few TGL machines in our CI and it is mostly green with > failures in tests that will not impact future Linux installations. > Also there is no warnings, errors, flickering or any visual defects > while doing ordinary tasks like browsing and editing documents in a > dual monitor setup. > > As a reminder i915.require_force_probe was created to protect > future Linux installation's iso images that might contain a > kernel from the enabling time of the new platform. Without this > protection most of linux installation was recommending > nomodeset option during installation that was getting stick > there after installation. > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html > Cc: James Ausmus <james.ausmus@intel.com> > Cc: Jani Saarinen <jani.saarinen@intel.com> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com> > Cc: Jani Nikula <jani.nikula@intel.com> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com> > --- > drivers/gpu/drm/i915/i915_pci.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c > index 24b1f0ce8743..2146b9a865ba 100644 > --- a/drivers/gpu/drm/i915/i915_pci.c > +++ b/drivers/gpu/drm/i915/i915_pci.c > @@ -822,7 +822,6 @@ static const struct intel_device_info tgl_info = { > GEN12_FEATURES, > PLATFORM(INTEL_TIGERLAKE), > .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D), > - .require_force_probe = 1, > .display.has_modular_fia = 1, > .engine_mask = > BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | BIT(VCS2), > -- > 2.25.1 >
On Tue, Feb 18, 2020 at 3:07 PM José Roberto de Souza <jose.souza@intel.com> wrote: > > We have a few TGL machines in our CI and it is mostly green with > failures in tests that will not impact future Linux installations. > Also there is no warnings, errors, flickering or any visual defects > while doing ordinary tasks like browsing and editing documents in a > dual monitor setup. > > As a reminder i915.require_force_probe was created to protect > future Linux installation's iso images that might contain a > kernel from the enabling time of the new platform. Without this > protection most of linux installation was recommending > nomodeset option during installation that was getting stick > there after installation. > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html > Cc: James Ausmus <james.ausmus@intel.com> > Cc: Jani Saarinen <jani.saarinen@intel.com> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > Cc: Jani Nikula <jani.nikula@intel.com> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> Also, I think it would be good to have this in 5.6 rather than 5.7. Yes, it's late in the merge window, but it falls in the case of "New device IDs and quirks are also accepted." of the stable kernel rules, so could as well just go directly to this kernel. Rodrigo, is it possible? thanks Lucas De Marchi > --- > drivers/gpu/drm/i915/i915_pci.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c > index 24b1f0ce8743..2146b9a865ba 100644 > --- a/drivers/gpu/drm/i915/i915_pci.c > +++ b/drivers/gpu/drm/i915/i915_pci.c > @@ -822,7 +822,6 @@ static const struct intel_device_info tgl_info = { > GEN12_FEATURES, > PLATFORM(INTEL_TIGERLAKE), > .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D), > - .require_force_probe = 1, > .display.has_modular_fia = 1, > .engine_mask = > BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | BIT(VCS2), > -- > 2.25.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Tue, Mar 03, 2020 at 12:26:34PM -0800, Lucas De Marchi wrote: > On Tue, Feb 18, 2020 at 3:07 PM José Roberto de Souza > <jose.souza@intel.com> wrote: > > > > We have a few TGL machines in our CI and it is mostly green with > > failures in tests that will not impact future Linux installations. > > Also there is no warnings, errors, flickering or any visual defects > > while doing ordinary tasks like browsing and editing documents in a > > dual monitor setup. > > > > As a reminder i915.require_force_probe was created to protect > > future Linux installation's iso images that might contain a > > kernel from the enabling time of the new platform. Without this > > protection most of linux installation was recommending > > nomodeset option during installation that was getting stick > > there after installation. > > > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html > > Cc: James Ausmus <james.ausmus@intel.com> > > Cc: Jani Saarinen <jani.saarinen@intel.com> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > Cc: Jani Nikula <jani.nikula@intel.com> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com> > > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> > > Also, I think it would be good to have this in 5.6 rather than 5.7. > Yes, it's late in the merge window, but it falls in the case of "New > device IDs and quirks are also accepted." of the stable kernel rules, > so could as well just go directly to this kernel. Rodrigo, is it > possible? Jani is on charge of the 5.6 so I will defer this decision to him. But in general we always refused to do this because this is a enabling kind of thing and not a fix per say. Okay, you might argue that it is a device ID and that would be accepted on stable so why not also on fixes cycle, but my fear is that we haven't properly validated that on 5.6 without the many changes, fixes and workarounds that are only going towards 5.7 and not 5.6. > > thanks > Lucas De Marchi > > > --- > > drivers/gpu/drm/i915/i915_pci.c | 1 - > > 1 file changed, 1 deletion(-) > > > > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c > > index 24b1f0ce8743..2146b9a865ba 100644 > > --- a/drivers/gpu/drm/i915/i915_pci.c > > +++ b/drivers/gpu/drm/i915/i915_pci.c > > @@ -822,7 +822,6 @@ static const struct intel_device_info tgl_info = { > > GEN12_FEATURES, > > PLATFORM(INTEL_TIGERLAKE), > > .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D), > > - .require_force_probe = 1, > > .display.has_modular_fia = 1, > > .engine_mask = > > BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | BIT(VCS2), > > -- > > 2.25.1 > > > > _______________________________________________ > > Intel-gfx mailing list > > Intel-gfx@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > > > -- > Lucas De Marchi
On Tue, 2020-03-03 at 12:39 -0800, Rodrigo Vivi wrote: > On Tue, Mar 03, 2020 at 12:26:34PM -0800, Lucas De Marchi wrote: > > On Tue, Feb 18, 2020 at 3:07 PM José Roberto de Souza > > <jose.souza@intel.com> wrote: > > > We have a few TGL machines in our CI and it is mostly green with > > > failures in tests that will not impact future Linux > > > installations. > > > Also there is no warnings, errors, flickering or any visual > > > defects > > > while doing ordinary tasks like browsing and editing documents in > > > a > > > dual monitor setup. > > > > > > As a reminder i915.require_force_probe was created to protect > > > future Linux installation's iso images that might contain a > > > kernel from the enabling time of the new platform. Without this > > > protection most of linux installation was recommending > > > nomodeset option during installation that was getting stick > > > there after installation. > > > > > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html > > > Reference: > > > https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html > > > Cc: James Ausmus <james.ausmus@intel.com> > > > Cc: Jani Saarinen <jani.saarinen@intel.com> > > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > > Cc: Jani Nikula <jani.nikula@intel.com> > > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com> > > > > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> > > > > Also, I think it would be good to have this in 5.6 rather than 5.7. > > Yes, it's late in the merge window, but it falls in the case of > > "New > > device IDs and quirks are also accepted." of the stable kernel > > rules, > > so could as well just go directly to this kernel. Rodrigo, is it > > possible? > > Jani is on charge of the 5.6 so I will defer this decision to him. > > But in general we always refused to do this because this is a > enabling > kind of thing and not a fix per say. Okay, you might argue that it is > a device ID and that would be accepted on stable so why not also on > fixes cycle, but my fear is that we haven't properly validated that > on 5.6 without the many changes, fixes and workarounds that are > only going towards 5.7 and not 5.6. Also we are blocked until https://gitlab.freedesktop.org/drm/intel/issues/1233 is fixed, Joonas and Jon Bloomfield advised that. > > > thanks > > Lucas De Marchi > > > > > --- > > > drivers/gpu/drm/i915/i915_pci.c | 1 - > > > 1 file changed, 1 deletion(-) > > > > > > diff --git a/drivers/gpu/drm/i915/i915_pci.c > > > b/drivers/gpu/drm/i915/i915_pci.c > > > index 24b1f0ce8743..2146b9a865ba 100644 > > > --- a/drivers/gpu/drm/i915/i915_pci.c > > > +++ b/drivers/gpu/drm/i915/i915_pci.c > > > @@ -822,7 +822,6 @@ static const struct intel_device_info > > > tgl_info = { > > > GEN12_FEATURES, > > > PLATFORM(INTEL_TIGERLAKE), > > > .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | > > > BIT(PIPE_D), > > > - .require_force_probe = 1, > > > .display.has_modular_fia = 1, > > > .engine_mask = > > > BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | > > > BIT(VCS2), > > > -- > > > 2.25.1 > > > > > > _______________________________________________ > > > Intel-gfx mailing list > > > Intel-gfx@lists.freedesktop.org > > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > > > > > -- > > Lucas De Marchi
On Tue, Mar 3, 2020 at 12:38 PM Rodrigo Vivi <rodrigo.vivi@intel.com> wrote: > > On Tue, Mar 03, 2020 at 12:26:34PM -0800, Lucas De Marchi wrote: > > On Tue, Feb 18, 2020 at 3:07 PM José Roberto de Souza > > <jose.souza@intel.com> wrote: > > > > > > We have a few TGL machines in our CI and it is mostly green with > > > failures in tests that will not impact future Linux installations. > > > Also there is no warnings, errors, flickering or any visual defects > > > while doing ordinary tasks like browsing and editing documents in a > > > dual monitor setup. > > > > > > As a reminder i915.require_force_probe was created to protect > > > future Linux installation's iso images that might contain a > > > kernel from the enabling time of the new platform. Without this > > > protection most of linux installation was recommending > > > nomodeset option during installation that was getting stick > > > there after installation. > > > > > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html > > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html > > > Cc: James Ausmus <james.ausmus@intel.com> > > > Cc: Jani Saarinen <jani.saarinen@intel.com> > > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > > Cc: Jani Nikula <jani.nikula@intel.com> > > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com> > > > > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> > > > > Also, I think it would be good to have this in 5.6 rather than 5.7. > > Yes, it's late in the merge window, but it falls in the case of "New > > device IDs and quirks are also accepted." of the stable kernel rules, > > so could as well just go directly to this kernel. Rodrigo, is it > > possible? > > Jani is on charge of the 5.6 so I will defer this decision to him. > > But in general we always refused to do this because this is a enabling > kind of thing and not a fix per say. Okay, you might argue that it is > a device ID and that would be accepted on stable so why not also on > fixes cycle, but my fear is that we haven't properly validated that > on 5.6 without the many changes, fixes and workarounds that are > only going towards 5.7 and not 5.6. oh.. never mind, checking now the log and we did have several fixes going to 5.7 and not 5.6. So, let's merge this in dinq only. Thanks Lucas De Marchi > > > > > thanks > > Lucas De Marchi > > > > > --- > > > drivers/gpu/drm/i915/i915_pci.c | 1 - > > > 1 file changed, 1 deletion(-) > > > > > > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c > > > index 24b1f0ce8743..2146b9a865ba 100644 > > > --- a/drivers/gpu/drm/i915/i915_pci.c > > > +++ b/drivers/gpu/drm/i915/i915_pci.c > > > @@ -822,7 +822,6 @@ static const struct intel_device_info tgl_info = { > > > GEN12_FEATURES, > > > PLATFORM(INTEL_TIGERLAKE), > > > .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D), > > > - .require_force_probe = 1, > > > .display.has_modular_fia = 1, > > > .engine_mask = > > > BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | BIT(VCS2), > > > -- > > > 2.25.1 > > > > > > _______________________________________________ > > > Intel-gfx mailing list > > > Intel-gfx@lists.freedesktop.org > > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > > > > > > > -- > > Lucas De Marchi
On Tue, 03 Mar 2020, Lucas De Marchi <lucas.de.marchi@gmail.com> wrote: > On Tue, Mar 3, 2020 at 12:38 PM Rodrigo Vivi <rodrigo.vivi@intel.com> wrote: >> >> On Tue, Mar 03, 2020 at 12:26:34PM -0800, Lucas De Marchi wrote: >> > On Tue, Feb 18, 2020 at 3:07 PM José Roberto de Souza >> > <jose.souza@intel.com> wrote: >> > > >> > > We have a few TGL machines in our CI and it is mostly green with >> > > failures in tests that will not impact future Linux installations. >> > > Also there is no warnings, errors, flickering or any visual defects >> > > while doing ordinary tasks like browsing and editing documents in a >> > > dual monitor setup. >> > > >> > > As a reminder i915.require_force_probe was created to protect >> > > future Linux installation's iso images that might contain a >> > > kernel from the enabling time of the new platform. Without this >> > > protection most of linux installation was recommending >> > > nomodeset option during installation that was getting stick >> > > there after installation. >> > > >> > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html >> > > Reference: https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html >> > > Cc: James Ausmus <james.ausmus@intel.com> >> > > Cc: Jani Saarinen <jani.saarinen@intel.com> >> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> >> > > Cc: Jani Nikula <jani.nikula@intel.com> >> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> >> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com> >> > >> > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> >> > >> > Also, I think it would be good to have this in 5.6 rather than 5.7. >> > Yes, it's late in the merge window, but it falls in the case of "New >> > device IDs and quirks are also accepted." of the stable kernel rules, >> > so could as well just go directly to this kernel. Rodrigo, is it >> > possible? >> >> Jani is on charge of the 5.6 so I will defer this decision to him. >> >> But in general we always refused to do this because this is a enabling >> kind of thing and not a fix per say. Okay, you might argue that it is >> a device ID and that would be accepted on stable so why not also on >> fixes cycle, but my fear is that we haven't properly validated that >> on 5.6 without the many changes, fixes and workarounds that are >> only going towards 5.7 and not 5.6. > > oh.. never mind, checking now the log and we did have several fixes going > to 5.7 and not 5.6. > > So, let's merge this in dinq only. Agreed. BR, Jani. > > Thanks > Lucas De Marchi > >> >> > >> > thanks >> > Lucas De Marchi >> > >> > > --- >> > > drivers/gpu/drm/i915/i915_pci.c | 1 - >> > > 1 file changed, 1 deletion(-) >> > > >> > > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c >> > > index 24b1f0ce8743..2146b9a865ba 100644 >> > > --- a/drivers/gpu/drm/i915/i915_pci.c >> > > +++ b/drivers/gpu/drm/i915/i915_pci.c >> > > @@ -822,7 +822,6 @@ static const struct intel_device_info tgl_info = { >> > > GEN12_FEATURES, >> > > PLATFORM(INTEL_TIGERLAKE), >> > > .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D), >> > > - .require_force_probe = 1, >> > > .display.has_modular_fia = 1, >> > > .engine_mask = >> > > BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | BIT(VCS2), >> > > -- >> > > 2.25.1 >> > > >> > > _______________________________________________ >> > > Intel-gfx mailing list >> > > Intel-gfx@lists.freedesktop.org >> > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx >> > >> > >> > >> > -- >> > Lucas De Marchi
On Thu, 2020-02-20 at 19:03 +0000, Patchwork wrote: > == Series Details == > > Series: drm/i915/tgl: Remove require_force_probe protection > URL : https://patchwork.freedesktop.org/series/73613/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_7963_full -> Patchwork_16613_full > ==================================================== > > Summary > ------- > > **FAILURE** > > Serious unknown changes coming with Patchwork_16613_full absolutely > need to be > verified manually. > > If you think the reported changes have nothing to do with the > changes > introduced in Patchwork_16613_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_16613_full: > > ### IGT changes ### > > #### Possible regressions #### > > * igt@gem_exec_balancer@hang: > - shard-tglb: [PASS][1] -> [FAIL][2] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-tglb2/igt@gem_exec_balancer@hang.html > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-tglb1/igt@gem_exec_balancer@hang.html > This change would not cause this issue. Based on today: https://intel-gfx-ci.01.org/tree/drm-tip/bat-all.html We only have 2 failures: - i915_selftest@live@gt_lrc failling in all TGLs this issue will not affect user installations - suspend tests failling in tgl-y but that is not i915 fault So pushed to dinq, thanks for the review and ack, Lucas and Rodrigo. > > New tests > --------- > > New tests have been introduced between CI_DRM_7963_full and > Patchwork_16613_full: > > ### New IGT tests (54) ### > > * igt@i915_pm_backlight@bad-brightness: > - Statuses : 3 pass(s) 4 skip(s) > - Exec time: [0.0, 0.03] s > > * igt@i915_pm_backlight@fade: > - Statuses : 3 pass(s) 4 skip(s) > - Exec time: [0.0, 2.60] s > > * igt@i915_pm_backlight@fade_with_dpms: > - Statuses : 3 pass(s) 5 skip(s) > - Exec time: [0.0, 5.00] s > > * igt@i915_pm_backlight@fade_with_suspend: > - Statuses : 3 pass(s) 4 skip(s) > - Exec time: [0.0, 4.50] s > > * igt@i915_pm_lpsp@edp-native: > - Statuses : 8 skip(s) > - Exec time: [0.0, 0.04] s > > * igt@i915_pm_lpsp@edp-panel-fitter: > - Statuses : 8 skip(s) > - Exec time: [0.0, 0.05] s > > * igt@i915_pm_lpsp@non-edp: > - Statuses : 1 pass(s) 7 skip(s) > - Exec time: [0.0, 0.12] s > > * igt@i915_pm_lpsp@screens-disabled: > - Statuses : 1 pass(s) 7 skip(s) > - Exec time: [0.0, 0.04] s > > * igt@i915_pm_rc6_residency@media-rc6-accuracy: > - Statuses : 7 skip(s) > - Exec time: [0.0] s > > * igt@i915_pm_rc6_residency@rc6-accuracy: > - Statuses : 8 pass(s) > - Exec time: [3.00] s > > * igt@i915_pm_rpm@cursor: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 45.52] s > > * igt@i915_pm_rpm@cursor-dpms: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 36.78] s > > * igt@i915_pm_rpm@debugfs-forcewake-user: > - Statuses : 7 pass(s) > - Exec time: [10.41, 14.24] s > > * igt@i915_pm_rpm@debugfs-read: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 80.93] s > > * igt@i915_pm_rpm@dpms-lpsp: > - Statuses : 3 pass(s) 5 skip(s) > - Exec time: [0.0, 0.81] s > > * igt@i915_pm_rpm@dpms-mode-unset-lpsp: > - Statuses : 3 pass(s) 4 skip(s) > - Exec time: [0.0, 9.74] s > > * igt@i915_pm_rpm@dpms-mode-unset-non-lpsp: > - Statuses : 4 pass(s) 4 skip(s) > - Exec time: [0.0, 4.13] s > > * igt@i915_pm_rpm@dpms-non-lpsp: > - Statuses : 4 pass(s) 3 skip(s) > - Exec time: [0.0, 0.16] s > > * igt@i915_pm_rpm@drm-resources-equal: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 9.64] s > > * igt@i915_pm_rpm@fences: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 14.70] s > > * igt@i915_pm_rpm@fences-dpms: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 12.82] s > > * igt@i915_pm_rpm@gem-evict-pwrite: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 3.96] s > > * igt@i915_pm_rpm@gem-execbuf: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 15.30] s > > * igt@i915_pm_rpm@gem-execbuf-stress: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 42.82] s > > * igt@i915_pm_rpm@gem-execbuf-stress-pc8: > - Statuses : 1 incomplete(s) 7 skip(s) > - Exec time: [0.0, 0.00] s > > * igt@i915_pm_rpm@gem-idle: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 9.09] s > > * igt@i915_pm_rpm@gem-pread: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 6.33] s > > * igt@i915_pm_rpm@i2c: > - Statuses : 7 pass(s) > - Exec time: [0.95, 11.18] s > > * igt@i915_pm_rpm@legacy-planes: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 169.80] s > > * igt@i915_pm_rpm@legacy-planes-dpms: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 146.58] s > > * igt@i915_pm_rpm@modeset-lpsp: > - Statuses : 3 pass(s) 5 skip(s) > - Exec time: [0.0, 4.93] s > > * igt@i915_pm_rpm@modeset-lpsp-stress: > - Statuses : 3 pass(s) 5 skip(s) > - Exec time: [0.0, 49.59] s > > * igt@i915_pm_rpm@modeset-lpsp-stress-no-wait: > - Statuses : 3 pass(s) 5 skip(s) > - Exec time: [0.0, 18.02] s > > * igt@i915_pm_rpm@modeset-non-lpsp: > - Statuses : 4 pass(s) 4 skip(s) > - Exec time: [0.0, 3.93] s > > * igt@i915_pm_rpm@modeset-non-lpsp-stress: > - Statuses : 4 pass(s) 4 skip(s) > - Exec time: [0.0, 7.29] s > > * igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait: > - Statuses : 4 pass(s) 4 skip(s) > - Exec time: [0.0, 5.43] s > > * igt@i915_pm_rpm@modeset-pc8-residency-stress: > - Statuses : 8 skip(s) > - Exec time: [0.0] s > > * igt@i915_pm_rpm@modeset-stress-extra-wait: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 73.83] s > > * igt@i915_pm_rpm@pc8-residency: > - Statuses : 8 skip(s) > - Exec time: [0.0] s > > * igt@i915_pm_rpm@pm-caching: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 19.89] s > > * igt@i915_pm_rpm@pm-tiling: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 16.86] s > > * igt@i915_pm_rpm@reg-read-ioctl: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 7.98] s > > * igt@i915_pm_rpm@sysfs-read: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 3.87] s > > * igt@i915_pm_rpm@system-suspend: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 9.06] s > > * igt@i915_pm_rpm@system-suspend-devices: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 13.38] s > > * igt@i915_pm_rpm@system-suspend-execbuf: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 86.04] s > > * igt@i915_pm_rpm@system-suspend-modeset: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 13.66] s > > * igt@i915_pm_rpm@universal-planes: > - Statuses : 7 pass(s) > - Exec time: [2.94, 226.06] s > > * igt@i915_pm_rpm@universal-planes-dpms: > - Statuses : 7 pass(s) 1 skip(s) > - Exec time: [0.0, 195.48] s > > * igt@i915_pm_rps@min-max-config-idle: > - Statuses : 8 pass(s) > - Exec time: [0.11, 0.66] s > > * igt@i915_pm_rps@min-max-config-loaded: > - Statuses : 1 fail(s) 7 pass(s) > - Exec time: [0.32, 3.02] s > > * igt@i915_pm_rps@reset: > - Statuses : 1 fail(s) 7 pass(s) > - Exec time: [3.52, 3.67] s > > * igt@i915_pm_rps@waitboost: > - Statuses : 1 fail(s) 7 pass(s) > - Exec time: [2.52, 2.65] s > > * igt@i915_pm_sseu@full-enable: > - Statuses : 4 pass(s) 4 skip(s) > - Exec time: [0.0, 0.01] s > > > > Known issues > ------------ > > Here are the changes found in Patchwork_16613_full that come from > known issues: > > ### IGT changes ### > > #### Issues hit #### > > * igt@gem_exec_schedule@preempt-queue-bsd1: > - shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#109276]) +11 > similar issues > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@gem_exec_schedule@preempt-queue-bsd1.html > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb5/igt@gem_exec_schedule@preempt-queue-bsd1.html > > * igt@gem_exec_schedule@reorder-wide-bsd: > - shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#112146]) +1 > similar issue > [5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb3/igt@gem_exec_schedule@reorder-wide-bsd.html > [6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb1/igt@gem_exec_schedule@reorder-wide-bsd.html > > * igt@gem_partial_pwrite_pread@write-snoop: > - shard-hsw: [PASS][7] -> [FAIL][8] ([i915#694]) +2 > similar issues > [7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-hsw6/igt@gem_partial_pwrite_pread@write-snoop.html > [8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-hsw4/igt@gem_partial_pwrite_pread@write-snoop.html > > * igt@gem_vm_create@isolation: > - shard-glk: [PASS][9] -> [FAIL][10] ([i915#314]) > [9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-glk6/igt@gem_vm_create@isolation.html > [10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-glk3/igt@gem_vm_create@isolation.html > > * igt@gem_workarounds@suspend-resume-context: > - shard-apl: [PASS][11] -> [DMESG-WARN][12] ([i915#180]) > +2 similar issues > [11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-apl2/igt@gem_workarounds@suspend-resume-context.html > [12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-apl4/igt@gem_workarounds@suspend-resume-context.html > > * igt@i915_pm_dc@dc5-dpms: > - shard-iclb: [PASS][13] -> [FAIL][14] ([i915#447]) > [13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@i915_pm_dc@dc5-dpms.html > [14]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb3/igt@i915_pm_dc@dc5-dpms.html > > * igt@i915_pm_dc@dc6-psr: > - shard-iclb: [PASS][15] -> [FAIL][16] ([i915#454]) > [15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb4/igt@i915_pm_dc@dc6-psr.html > [16]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb4/igt@i915_pm_dc@dc6-psr.html > > * igt@i915_pm_rpm@gem-execbuf-stress-pc8 (NEW): > - shard-snb: [SKIP][17] ([fdo#109271]) -> > [INCOMPLETE][18] ([i915#82]) > [17]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-snb5/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html > [18]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-snb6/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html > > * igt@i915_selftest@live_gtt: > - shard-kbl: [PASS][19] -> [TIMEOUT][20] ([fdo#112271]) > [19]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-kbl7/igt@i915_selftest@live_gtt.html > [20]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-kbl4/igt@i915_selftest@live_gtt.html > > * igt@kms_flip@flip-vs-absolute-wf_vblank: > - shard-tglb: [PASS][21] -> [FAIL][22] ([i915#488]) > [21]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-tglb5/igt@kms_flip@flip-vs-absolute-wf_vblank.html > [22]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-tglb3/igt@kms_flip@flip-vs-absolute-wf_vblank.html > > * igt@kms_flip@flip-vs-suspend: > - shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#180]) > [23]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-kbl3/igt@kms_flip@flip-vs-suspend.html > [24]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-kbl7/igt@kms_flip@flip-vs-suspend.html > > * igt@kms > _frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu: > - shard-skl: [PASS][25] -> [FAIL][26] ([i915#49]) > [25]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl1/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu.html > [26]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu.html > > * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min: > - shard-skl: [PASS][27] -> [FAIL][28] ([fdo#108145]) > [27]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl1/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html > [28]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl5/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html > > * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: > - shard-skl: [PASS][29] -> [FAIL][30] ([fdo#108145] / > [i915#265]) > [29]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl10/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html > [30]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl1/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html > > * igt@kms_plane_lowres@pipe-a-tiling-y: > - shard-glk: [PASS][31] -> [FAIL][32] ([i915#899]) > [31]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-glk9/igt@kms_plane_lowres@pipe-a-tiling-y.html > [32]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-glk4/igt@kms_plane_lowres@pipe-a-tiling-y.html > > * igt@kms_psr@psr2_cursor_mmap_cpu: > - shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +1 > similar issue > [33]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html > [34]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb4/igt@kms_psr@psr2_cursor_mmap_cpu.html > > * igt@perf_pmu@init-busy-vcs1: > - shard-iclb: [PASS][35] -> [SKIP][36] ([fdo#112080]) +4 > similar issues > [35]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb2/igt@perf_pmu@init-busy-vcs1.html > [36]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb7/igt@perf_pmu@init-busy-vcs1.html > > > #### Possible fixes #### > > * {igt@gem_ctx_persistence@close-replace-race}: > - shard-iclb: [FAIL][37] ([i915#1241]) -> [PASS][38] > [37]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@gem_ctx_persistence@close-replace-race.html > [38]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb3/igt@gem_ctx_persistence@close-replace-race.html > - shard-apl: [FAIL][39] ([i915#1241]) -> [PASS][40] > [39]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-apl4/igt@gem_ctx_persistence@close-replace-race.html > [40]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-apl1/igt@gem_ctx_persistence@close-replace-race.html > > * {igt@gem_exec_schedule@implicit-both-bsd2}: > - shard-iclb: [SKIP][41] ([fdo#109276] / [i915#677]) -> > [PASS][42] > [41]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb8/igt@gem_exec_schedule@implicit-both-bsd2.html > [42]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb2/igt@gem_exec_schedule@implicit-both-bsd2.html > > * igt@gem_exec_schedule@pi-distinct-iova-bsd: > - shard-iclb: [SKIP][43] ([i915#677]) -> [PASS][44] +1 > similar issue > [43]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@gem_exec_schedule@pi-distinct-iova-bsd.html > [44]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb3/igt@gem_exec_schedule@pi-distinct-iova-bsd.html > > * igt@gem_exec_schedule@preemptive-hang-bsd: > - shard-iclb: [SKIP][45] ([fdo#112146]) -> [PASS][46] +1 > similar issue > [45]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@gem_exec_schedule@preemptive-hang-bsd.html > [46]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb7/igt@gem_exec_schedule@preemptive-hang-bsd.html > > * igt@gem_ppgtt@flink-and-close-vma-leak: > - shard-glk: [FAIL][47] ([i915#644]) -> [PASS][48] > [47]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-glk8/igt@gem_ppgtt@flink-and-close-vma-leak.html > [48]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-glk7/igt@gem_ppgtt@flink-and-close-vma-leak.html > - shard-apl: [FAIL][49] ([i915#644]) -> [PASS][50] > [49]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-apl1/igt@gem_ppgtt@flink-and-close-vma-leak.html > [50]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-apl6/igt@gem_ppgtt@flink-and-close-vma-leak.html > > * igt@gem_wait@write-busy-vcs1: > - shard-iclb: [SKIP][51] ([fdo#112080]) -> [PASS][52] +4 > similar issues > [51]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb8/igt@gem_wait@write-busy-vcs1.html > [52]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb2/igt@gem_wait@write-busy-vcs1.html > > * igt@kms_cursor_crc@pipe-a-cursor-size-change: > - shard-snb: [SKIP][53] ([fdo#109271]) -> [PASS][54] +1 > similar issue > [53]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-snb4/igt@kms_cursor_crc@pipe-a-cursor-size-change.html > [54]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-snb6/igt@kms_cursor_crc@pipe-a-cursor-size-change.html > > * igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy: > - shard-hsw: [FAIL][55] ([i915#96]) -> [PASS][56] > [55]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-hsw8/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html > [56]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html > > * igt@kms_fbcon_fbt@fbc-suspend: > - shard-kbl: [DMESG-WARN][57] ([i915#180]) -> [PASS][58] > [57]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html > [58]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-kbl6/igt@kms_fbcon_fbt@fbc-suspend.html > > * igt@kms_flip@flip-vs-expired-vblank-interruptible: > - shard-skl: [FAIL][59] ([i915#79]) -> [PASS][60] > [59]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl5/igt@kms_flip@flip-vs-expired-vblank-interruptible.html > [60]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl4/igt@kms_flip@flip-vs-expired-vblank-interruptible.html > > * igt@kms_flip@flip-vs-suspend-interruptible: > - shard-hsw: [INCOMPLETE][61] ([i915#61]) -> [PASS][62] > [61]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-hsw2/igt@kms_flip@flip-vs-suspend-interruptible.html > [62]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-hsw1/igt@kms_flip@flip-vs-suspend-interruptible.html > > * igt@kms_frontbuffer_tracking@psr-1p-rte: > - shard-tglb: [SKIP][63] ([i915#668]) -> [PASS][64] > [63]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-tglb5/igt@kms_frontbuffer_tracking@psr-1p-rte.html > [64]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-tglb3/igt@kms_frontbuffer_tracking@psr-1p-rte.html > > * {igt@kms_hdr@bpc-switch-dpms}: > - shard-skl: [FAIL][65] ([i915#1188]) -> [PASS][66] > [65]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl2/igt@kms_hdr@bpc-switch-dpms.html > [66]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl1/igt@kms_hdr@bpc-switch-dpms.html > > * igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes: > - shard-apl: [DMESG-WARN][67] ([i915#180]) -> [PASS][68] > +2 similar issues > [67]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-apl1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html > [68]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-apl3/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html > > * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: > - shard-skl: [FAIL][69] ([fdo#108145] / [i915#265]) -> > [PASS][70] > [69]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl2/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html > [70]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl9/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html > > * igt@kms_psr2_su@frontbuffer: > - shard-iclb: [SKIP][71] ([fdo#109642] / [fdo#111068]) -> > [PASS][72] > [71]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb4/igt@kms_psr2_su@frontbuffer.html > [72]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb2/igt@kms_psr2_su@frontbuffer.html > > * igt@kms_psr@no_drrs: > - shard-iclb: [FAIL][73] ([i915#173]) -> [PASS][74] > [73]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@kms_psr@no_drrs.html > [74]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb7/igt@kms_psr@no_drrs.html > > * igt@kms_psr@psr2_sprite_mmap_gtt: > - shard-iclb: [SKIP][75] ([fdo#109441]) -> [PASS][76] +2 > similar issues > [75]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb1/igt@kms_psr@psr2_sprite_mmap_gtt.html > [76]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html > > * igt@kms_setmode@basic: > - shard-apl: [FAIL][77] ([i915#31]) -> [PASS][78] > [77]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-apl2/igt@kms_setmode@basic.html > [78]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-apl7/igt@kms_setmode@basic.html > > * igt@kms_vblank@pipe-a-ts-continuation-suspend: > - shard-skl: [INCOMPLETE][79] ([i915#69]) -> [PASS][80] > [79]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-skl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html > [80]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-skl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html > > * igt@perf@short-reads: > - shard-kbl: [TIMEOUT][81] ([fdo#112271] / [i915#51]) -> > [PASS][82] > [81]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-kbl6/igt@perf@short-reads.html > [82]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-kbl1/igt@perf@short-reads.html > > * igt@prime_vgem@fence-wait-bsd2: > - shard-iclb: [SKIP][83] ([fdo#109276]) -> [PASS][84] +8 > similar issues > [83]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-iclb8/igt@prime_vgem@fence-wait-bsd2.html > [84]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-iclb2/igt@prime_vgem@fence-wait-bsd2.html > > > #### Warnings #### > > * igt@gem_eio@in-flight-suspend: > - shard-kbl: [INCOMPLETE][85] ([fdo#103665]) -> [DMESG- > WARN][86] ([i915#180]) > [85]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-kbl6/igt@gem_eio@in-flight-suspend.html > [86]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-kbl1/igt@gem_eio@in-flight-suspend.html > > * igt@gem_tiled_blits@interruptible: > - shard-hsw: [FAIL][87] ([i915#818]) -> [FAIL][88] > ([i915#694]) > [87]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7963/shard-hsw1/igt@gem_tiled_blits@interruptible.html > [88]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16613/shard-hsw8/igt@gem_tiled_blits@interruptible.html > > > {name}: This element is suppressed. This means it is ignored when > computing > the status of the difference (SUCCESS, WARNING, or > FAILURE). > > [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665 > [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 > [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 > [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 > [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 > [fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642 > [fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068 > [fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080 > [fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146 > [fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271 > [i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188 > [i915#1197]: https://gitlab.freedesktop.org/drm/intel/issues/1197 > [i915#1239]: https://gitlab.freedesktop.org/drm/intel/issues/1239 > [i915#1241]: https://gitlab.freedesktop.org/drm/intel/issues/1241 > [i915#173]: https://gitlab.freedesktop.org/drm/intel/issues/173 > [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 > [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 > [i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31 > [i915#314]: https://gitlab.freedesktop.org/drm/intel/issues/314 > [i915#447]: https://gitlab.freedesktop.org/drm/intel/issues/447 > [i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454 > [i915#488]: https://gitlab.freedesktop.org/drm/intel/issues/488 > [i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49 > [i915#51]: https://gitlab.freedesktop.org/drm/intel/issues/51 > [i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61 > [i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644 > [i915#668]: https://gitlab.freedesktop.org/drm/intel/issues/668 > [i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677 > [i915#679]: https://gitlab.freedesktop.org/drm/intel/issues/679 > [i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69 > [i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694 > [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79 > [i915#818]: https://gitlab.freedesktop.org/drm/intel/issues/818 > [i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82 > [i915#899]: https://gitlab.freedesktop.org/drm/intel/issues/899 > [i915#96]: https://gitlab.freedesktop.org/drm/intel/issues/96 > > > Participating hosts (10 -> 10) > ------------------------------ > > No changes in participating hosts > > > Build changes > ------------- > > * CI: CI-20190529 -> None > * Linux: CI_DRM_7963 -> Patchwork_16613 > > CI-20190529: 20190529 > CI_DRM_7963: e0d737598eb749378a5dc4ed3dfafc6f79d512cb @ > git://anongit.freedesktop.org/gfx-ci/linux > IGT_5448: 116020b1f83c1b3994c76882df7f77b6731d78ba @ > git://anongit.freedesktop.org/xorg/app/intel-gpu-tools > Patchwork_16613: e94302377fad504b417c64381216bf424da11f5e @ > 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_16613/index.html
diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c index 24b1f0ce8743..2146b9a865ba 100644 --- a/drivers/gpu/drm/i915/i915_pci.c +++ b/drivers/gpu/drm/i915/i915_pci.c @@ -822,7 +822,6 @@ static const struct intel_device_info tgl_info = { GEN12_FEATURES, PLATFORM(INTEL_TIGERLAKE), .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D), - .require_force_probe = 1, .display.has_modular_fia = 1, .engine_mask = BIT(RCS0) | BIT(BCS0) | BIT(VECS0) | BIT(VCS0) | BIT(VCS2),
We have a few TGL machines in our CI and it is mostly green with failures in tests that will not impact future Linux installations. Also there is no warnings, errors, flickering or any visual defects while doing ordinary tasks like browsing and editing documents in a dual monitor setup. As a reminder i915.require_force_probe was created to protect future Linux installation's iso images that might contain a kernel from the enabling time of the new platform. Without this protection most of linux installation was recommending nomodeset option during installation that was getting stick there after installation. Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-tgl-u.html Reference: https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglb.html Cc: James Ausmus <james.ausmus@intel.com> Cc: Jani Saarinen <jani.saarinen@intel.com> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Cc: Jani Nikula <jani.nikula@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Signed-off-by: José Roberto de Souza <jose.souza@intel.com> --- drivers/gpu/drm/i915/i915_pci.c | 1 - 1 file changed, 1 deletion(-)