[Intel-gfx] Intel-gfx Digest, Vol 141, Issue 541
Vudum, Lakshminarayana
lakshminarayana.vudum at intel.com
Fri Oct 18 18:13:59 UTC 2019
-----Original Message-----
From: Intel-gfx <intel-gfx-bounces at lists.freedesktop.org> On Behalf Of intel-gfx-request at lists.freedesktop.org
Sent: Friday, October 18, 2019 7:30 PM
To: intel-gfx at lists.freedesktop.org
Subject: Intel-gfx Digest, Vol 141, Issue 541
Send Intel-gfx mailing list submissions to
intel-gfx at lists.freedesktop.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
or, via email, send a message with subject or body 'help' to
intel-gfx-request at lists.freedesktop.org
You can reach the person managing the list at
intel-gfx-owner at lists.freedesktop.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Intel-gfx digest..."
Today's Topics:
1. ✗ Fi.CI.BAT: failure for drm/i915/dsb: Remove PIN_MAPPABLE
from the DSB object VMA (rev2) (Patchwork)
2. ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Split
memory_region initialisation into its own file (Patchwork)
3. Re: [RFC PATCH] drm/i915: Restore full symmetry in
i915_driver_modeset_probe/remove (Michal Wajdeczko)
4. Re: [PATCH 3/4] drm/edid: Fix HDMI VIC handling (Shankar, Uma)
5. Re: [PATCH] drm/i915: Split memory_region initialisation into
its own file (Matthew Auld)
6. ✗ Fi.CI.BAT: failure for drm/i915/selftests: Add the mock
engine to the gt->engine[] (Patchwork)
7. Re: ✗ Fi.CI.IGT: failure for drm/i915: Correct the PCH
type in irq postinstall (rev2) (Matt Roper)
----------------------------------------------------------------------
Message: 1
Date: Fri, 18 Oct 2019 15:44:54 -0000
From: Patchwork <patchwork at emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin at linux.intel.com>
Cc: intel-gfx at lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dsb: Remove
PIN_MAPPABLE from the DSB object VMA (rev2)
Message-ID: <20191018154454.27987.82459 at emeril.freedesktop.org>
Content-Type: text/plain; charset="utf-8"
== Series Details ==
Series: drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA (rev2)
URL : https://patchwork.freedesktop.org/series/68162/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7129 -> Patchwork_14883 ====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_14883 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_14883, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_14883:
### IGT changes ###
#### Possible regressions ####
* igt at i915_selftest@live_execlists:
- fi-kbl-soraka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-kbl-soraka/igt@i915_selftest@live_execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-kbl-soraka/igt@i915_selftest@live_execlists.html
Known issues
------------
Here are the changes found in Patchwork_14883 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt at gem_mmap_gtt@basic-copy:
- fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-icl-u3/igt@gem_mmap_gtt@basic-copy.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-icl-u3/igt@gem_mmap_gtt@basic-copy.html
#### Possible fixes ####
* igt at gem_ctx_switch@rcs0:
- {fi-icl-guc}: [INCOMPLETE][5] ([fdo#107713]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-icl-guc/igt@gem_ctx_switch@rcs0.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-icl-guc/igt@gem_ctx_switch@rcs0.html
* igt at gem_flink_basic@flink-lifetime:
- fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-icl-u3/igt@gem_flink_basic@flink-lifetime.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-icl-u3/igt@gem_flink_basic@flink-lifetime.html
* igt at i915_selftest@live_execlists:
- fi-skl-6260u: [INCOMPLETE][9] ([fdo#111934]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-skl-6260u/igt@i915_selftest@live_execlists.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-skl-6260u/igt@i915_selftest@live_execlists.html
- fi-kbl-r: [INCOMPLETE][11] -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-kbl-r/igt@i915_selftest@live_execlists.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-kbl-r/igt@i915_selftest@live_execlists.html
* igt at kms_chamelium@hdmi-edid-read:
- fi-icl-u2: [FAIL][13] ([fdo#109483]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-icl-u2/igt@kms_chamelium@hdmi-edid-read.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-icl-u2/igt@kms_chamelium@hdmi-edid-read.html
* igt at kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][15] ([fdo#111407]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7129/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600
[fdo#111747]: https://bugs.freedesktop.org/show_bug.cgi?id=111747
[fdo#111934]: https://bugs.freedesktop.org/show_bug.cgi?id=111934
Participating hosts (50 -> 45)
------------------------------
Additional (1): fi-bdw-5557u
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7129 -> Patchwork_14883
CI-20190529: 20190529
CI_DRM_7129: 2f5e510f557189eb9b63db41e0a44e60b4b7abff @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5232: bb5735423eaf6fdbf6b2f94ef0b8520e74eab993 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14883: 11b8597acf1f928df7fae99abadc5d4274256764 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
11b8597acf1f drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14883/index.html
------------------------------
Message: 2
Date: Fri, 18 Oct 2019 15:49:01 -0000
From: Patchwork <patchwork at emeril.freedesktop.org>
To: "Chris Wilson" <chris at chris-wilson.co.uk>
Cc: intel-gfx at lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Split
memory_region initialisation into its own file
Message-ID: <20191018154901.27986.84682 at emeril.freedesktop.org>
Content-Type: text/plain; charset="utf-8"
== Series Details ==
Series: drm/i915: Split memory_region initialisation into its own file
URL : https://patchwork.freedesktop.org/series/68200/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
36c94b0bae3b drm/i915: Split memory_region initialisation into its own file
-:202: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#202:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 274 lines checked
------------------------------
Message: 3
Date: Fri, 18 Oct 2019 17:52:26 +0200
From: "Michal Wajdeczko" <michal.wajdeczko at intel.com>
To: intel-gfx at lists.freedesktop.org, "Janusz Krzysztofik"
<janusz.krzysztofik at linux.intel.com>
Cc: Michał Winiarski <michal.winiarski at intel.com>, Piotr Piórkowski
<piotr.piorkowski at intel.com>, "Tomasz Lis" <tomasz.lis at intel.com>,
"Jani Nikula" <jani.nikula at intel.com>, Ville Syrjälä
<ville.syrjala at linux.intel.com>, "Chris Wilson"
<chris at chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [RFC PATCH] drm/i915: Restore full symmetry
in i915_driver_modeset_probe/remove
Message-ID: <op.z9u41odsxaggs7 at mwajdecz-mobl1.ger.corp.intel.com>
Content-Type: text/plain; charset=iso-8859-15; format=flowed;
delsp=yes
On Fri, 18 Oct 2019 12:07:10 +0200, Janusz Krzysztofik <janusz.krzysztofik at linux.intel.com> wrote:
> Commit 2d6f6f359fd8 ("drm/i915: add i915_driver_modeset_remove()")
> claimed removal of asymmetry in probe() and remove() calls, however,
> it didn't take care of calling intel_irq_uninstall() on driver remove.
> That doesn't hurt as long as we still call it from
> intel_modeset_driver_remove() but in order to have full symmetry we
> should call it again from i915_driver_modeset_remove().
>
> Note that it's safe to call intel_irq_uninstall() twice thanks to
> commit b318b82455bd ("drm/i915: Nuke drm_driver irq vfuncs"). We may
> only want to mention the case we are adding in a related FIXME comment
> provided by that commit. While being at it, update the name of
> function mentioned as calling it out of sequence as that name has been
> changed meanwhile by commit 78dae1ac35dd ("drm/i915: Propagate
> "_remove" function name suffix down").
>
> Suggested-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik at linux.intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
> ---
Reviewed-by: Michal Wajdeczko <michal.wajdeczko at intel.com> but please see below
> drivers/gpu/drm/i915/i915_drv.c | 2 ++
> drivers/gpu/drm/i915/i915_irq.c | 8 ++++----
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c
> b/drivers/gpu/drm/i915/i915_drv.c index dd9613e45723..4ae9bfa96290
> 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -452,6 +452,8 @@ static void i915_driver_modeset_remove(struct
> drm_i915_private *i915)
> intel_modeset_driver_remove(i915);
> + intel_irq_uninstall(i915);
> +
> intel_bios_driver_remove(i915);
I'm wondering if this is a good location for this call as in
i915_driver_modeset_probe() we call it before intel_vga_register() so likely cleanup should be done after intel_vga_unregister()
it also looks that we missed to call intel_bios_driver_remove() on the error path in i915_driver_modeset_probe()
but let's fix it in a separate patch
> vga_switcheroo_unregister_client(pdev);
> diff --git a/drivers/gpu/drm/i915/i915_irq.c
> b/drivers/gpu/drm/i915/i915_irq.c index bc83f094065a..0160283860a6
> 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -4515,10 +4515,10 @@ void intel_irq_uninstall(struct
> drm_i915_private
> *dev_priv)
> int irq = dev_priv->drm.pdev->irq;
> /*
> - * FIXME we can get called twice during driver load
> - * error handling due to intel_modeset_cleanup()
> - * calling us out of sequence. Would be nice if
> - * it didn't do that...
> + * FIXME we can get called twice during driver probe
> + * error handling as well as during driver remove due to
> + * intel_modeset_driver_remove() calling us out of sequence.
> + * Would be nice if it didn't do that...
> */
> if (!dev_priv->drm.irq_enabled)
> return;
------------------------------
Message: 4
Date: Fri, 18 Oct 2019 16:02:34 +0000
From: "Shankar, Uma" <uma.shankar at intel.com>
To: Ville Syrjala <ville.syrjala at linux.intel.com>,
"dri-devel at lists.freedesktop.org" <dri-devel at lists.freedesktop.org>
Cc: "intel-gfx at lists.freedesktop.org"
<intel-gfx at lists.freedesktop.org>, "Wayne Lin" <waynelin at amd.com>
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/edid: Fix HDMI VIC handling
Message-ID:
<E7C9878FBA1C6D42A1CA3F62AEB6945F822764CF at BGSMSX104.gar.corp.intel.com>
Content-Type: text/plain; charset="utf-8"
>-----Original Message-----
>From: Intel-gfx <intel-gfx-bounces at lists.freedesktop.org> On Behalf Of
>Ville Syrjala
>Sent: Friday, October 4, 2019 7:49 PM
>To: dri-devel at lists.freedesktop.org
>Cc: intel-gfx at lists.freedesktop.org; Wayne Lin <waynelin at amd.com>
>Subject: [Intel-gfx] [PATCH 3/4] drm/edid: Fix HDMI VIC handling
>
>From: Ville Syrjälä <ville.syrjala at linux.intel.com>
>
>Extract drm_mode_hdmi_vic() to correctly calculate the final HDMI VIC for us.
>Currently this is being done a bit differently between the AVI and HDMI infoframes.
>Let's get both to agree on this.
>
>We need to allow the case where a mode is both 3D and has a HDMI VIC.
>Currently we'll just refuse to generate the HDMI infoframe when we
>really should be setting HDMI VIC to 0 and instead enabling 3D stereo signalling.
>
>If the sink doesn't even support the HDMI infoframe we should not be
>picking the HDMI VIC in favor of the CEA VIC, because then we'll end up
>not sending either VIC in the end.
Looks good to me.
Reviewed-by: Uma Shankar <uma.shankar at intel.com>
>Cc: Wayne Lin <waynelin at amd.com>
>Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
>---
> drivers/gpu/drm/drm_edid.c | 37 +++++++++++++++++++++----------------
> 1 file changed, 21 insertions(+), 16 deletions(-)
>
>diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
>index
>495b7fb4d9ef..c7f9f7ca75a2 100644
>--- a/drivers/gpu/drm/drm_edid.c
>+++ b/drivers/gpu/drm/drm_edid.c
>@@ -5160,11 +5160,25 @@ drm_hdmi_infoframe_set_hdr_metadata(struct
>hdmi_drm_infoframe *frame, }
>EXPORT_SYMBOL(drm_hdmi_infoframe_set_hdr_metadata);
>
>+static u8 drm_mode_hdmi_vic(struct drm_connector *connector,
>+ const struct drm_display_mode *mode) {
>+ bool has_hdmi_infoframe = connector ?
>+ connector->display_info.has_hdmi_infoframe : false;
>+
>+ if (!has_hdmi_infoframe)
>+ return 0;
>+
>+ /* No HDMI VIC when signalling 3D video format */
>+ if (mode->flags & DRM_MODE_FLAG_3D_MASK)
>+ return 0;
>+
>+ return drm_match_hdmi_mode(mode);
>+}
>+
> static u8 drm_mode_cea_vic(struct drm_connector *connector,
> const struct drm_display_mode *mode) {
>- u8 vendor_if_vic = drm_match_hdmi_mode(mode);
>- bool is_s3d = mode->flags & DRM_MODE_FLAG_3D_MASK;
> u8 vic;
>
> /*
>@@ -5173,7 +5187,7 @@ static u8 drm_mode_cea_vic(struct drm_connector
>*connector,
> * VIC in AVI infoframes. Lets check if this mode is present in
> * HDMI 1.4b 4K modes
> */
>- if (drm_valid_hdmi_vic(vendor_if_vic) && !is_s3d)
>+ if (drm_mode_hdmi_vic(connector, mode))
> return 0;
>
> vic = drm_match_cea_mode(mode);
>@@ -5433,8 +5447,6 @@
>drm_hdmi_vendor_infoframe_from_display_mode(struct
>hdmi_vendor_infoframe *frame,
> bool has_hdmi_infoframe = connector ?
> connector->display_info.has_hdmi_infoframe : false;
> int err;
>- u32 s3d_flags;
>- u8 vic;
>
> if (!frame || !mode)
> return -EINVAL;
>@@ -5442,8 +5454,9 @@
>drm_hdmi_vendor_infoframe_from_display_mode(struct
>hdmi_vendor_infoframe *frame,
> if (!has_hdmi_infoframe)
> return -EINVAL;
>
>- vic = drm_match_hdmi_mode(mode);
>- s3d_flags = mode->flags & DRM_MODE_FLAG_3D_MASK;
>+ err = hdmi_vendor_infoframe_init(frame);
>+ if (err < 0)
>+ return err;
>
> /*
> * Even if it's not absolutely necessary to send the infoframe @@
> -5454,15
>+5467,7 @@ drm_hdmi_vendor_infoframe_from_display_mode(struct
>hdmi_vendor_infoframe *frame,
> * mode if the source simply stops sending the infoframe when
> * it wants to switch from 3D to 2D.
> */
>-
>- if (vic && s3d_flags)
>- return -EINVAL;
>-
>- err = hdmi_vendor_infoframe_init(frame);
>- if (err < 0)
>- return err;
>-
>- frame->vic = vic;
>+ frame->vic = drm_mode_hdmi_vic(connector, mode);
> frame->s3d_struct = s3d_structure_from_display_mode(mode);
>
> return 0;
>--
>2.21.0
>
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx at lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/intel-gfx
------------------------------
Message: 5
Date: Fri, 18 Oct 2019 17:10:35 +0100
From: Matthew Auld <matthew.william.auld at gmail.com>
To: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Intel Graphics Development <intel-gfx at lists.freedesktop.org>,
Matthew Auld <matthew.auld at intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Split memory_region
initialisation into its own file
Message-ID:
<CAM0jSHOKHkfD7nZyVM1eAsmFSB4tx7RKq2rqc8sHY9aNS8NHyQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Fri, 18 Oct 2019 at 13:48, Chris Wilson <chris at chris-wilson.co.uk> wrote:
>
> Pull the memory region bookkeeping into its file. Let's start clean
> and see how long it lasts!
>
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.auld at intel.com>
Much better,
Reviewed-by: Matthew Auld <matthew.auld at intel.com>
------------------------------
Message: 6
Date: Fri, 18 Oct 2019 16:17:44 -0000
From: Patchwork <patchwork at emeril.freedesktop.org>
To: "Chris Wilson" <chris at chris-wilson.co.uk>
Cc: intel-gfx at lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/selftests:
Add the mock engine to the gt->engine[]
Message-ID: <20191018161744.27985.22626 at emeril.freedesktop.org>
Content-Type: text/plain; charset="utf-8"
== Series Details ==
Series: drm/i915/selftests: Add the mock engine to the gt->engine[]
URL : https://patchwork.freedesktop.org/series/68201/
State : failure
== Summary ==
Applying: drm/i915/selftests: Add the mock engine to the gt->engine[] Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/gt/mock_engine.c
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.
------------------------------
Message: 7
Date: Fri, 18 Oct 2019 09:30:27 -0700
From: Matt Roper <matthew.d.roper at intel.com>
To: intel-gfx at lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Correct
the PCH type in irq postinstall (rev2)
Message-ID: <20191018163027.GF13581 at mdroper-desk1.amr.corp.intel.com>
Content-Type: text/plain; charset=us-ascii
On Fri, Oct 18, 2019 at 04:01:56AM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Correct the PCH type in irq postinstall (rev2)
> URL : https://patchwork.freedesktop.org/series/68116/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7122_full -> Patchwork_14860_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_14860_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_14860_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
The failures below are both GEM selftest failures unrelated to the PCH changes here. Applied to dinq; thanks for the patch.
>
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_14860_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt at gem_persistent_relocs@forked-interruptible-thrash-inactive:
> - shard-kbl: [PASS][1] -> [TIMEOUT][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-kbl1/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-kbl6/ig
> t at gem_persistent_relocs@forked-interruptible-thrash-inactive.html
(gem_persistent_relocs:1348) CRITICAL: Failed assertion: test == 0xdeadbeef
(gem_persistent_relocs:1348) CRITICAL: mismatch in buffer 0: 0x00000000 instead of 0xdeadbeef at offset 192
Seems similar to https://bugs.freedesktop.org/show_bug.cgi?id=112037
even though that bug is reported as resolved?
> * igt at gem_persistent_relocs@forked-interruptible-thrashing:
> - shard-iclb: [PASS][3] -> [FAIL][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb8/igt@gem_persistent_relocs@forked-interruptible-thrashing.html
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb3/i
> gt at gem_persistent_relocs@forked-interruptible-thrashing.html
<3> [666.513462] BUG: sleeping function called from invalid context at kernel/sched/completion.c:99 <3> [666.513471] in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 2066, name: gem_persistent_ <4> [666.513985] INFO: lockdep is turned off.
<3> [666.513991] Preemption disabled at:
<4> [666.513992] [<0000000000000000>] 0x0
<4> [666.514004] CPU: 2 PID: 2066 Comm: gem_persistent_ Tainted: G UD 5.4.0-rc3-CI-Patchwork_14860+ #1
<4> [666.514015] Hardware name: /NUC7i5BNB, BIOS BNKBL357.86A.0054.2017.1025.1822 10/25/2017 <4> [666.514026] Call Trace:
<4> [666.514036] dump_stack+0x67/0x9b
<4> [666.514046] ___might_sleep+0x178/0x260 <4> [666.514055] wait_for_completion+0x37/0x1a0 <4> [666.514067] virt_efi_query_variable_info+0x161/0x1b0
<4> [666.514077] efi_query_variable_store+0xb3/0x1a0
<4> [666.514087] ? efivar_entry_set_safe+0x19c/0x220 <4> [666.514096] ? efi_delete_dummy_variable+0x90/0x90
<4> [666.514103] efivar_entry_set_safe+0x19c/0x220 <4> [666.514112] ? efi_pstore_write+0x10b/0x150 <4> [666.514119] efi_pstore_write+0x10b/0x150 <4> [666.514132] pstore_dump+0x127/0x340 <4> [666.514142] kmsg_dump+0x87/0x1c0 <4> [666.514150] oops_end+0x3e/0x90 <4> [666.514158] do_trap+0x80/0x100 <4> [666.514217] ? __i915_vma_unbind.part.39+0x207/0x460 [i915] <4> [666.514227] do_invalid_op+0x23/0x30 <4> [666.514283] ? __i915_vma_unbind.part.39+0x207/0x460 [i915] <4> [666.514293] invalid_op+0x23/0x30 <4> [666.514345] RIP: 0010:__i915_vma_unbind.part.39+0x207/0x460 [i915] <4> [666.514355] Code: 48 96 db e0 48 8b 35 00 6a 1d 00 49 c7 c0 da ec 4a a0 b9 7e 04 00 00 48 c7 c2 80 0c 45 a0 48 c7 c7 52 19 37 a0 e8 19 92 e2 e0 <0f> 0b 48 c7 c1 da ec 4a a0 ba 84 04 00 00 48 c7 c6 80 0c 45 a0 48 <4> [666.514375] RSP: 0018:ffffc9000039fc78 EFLAGS: 00010286 <4> [666.514382] RAX: 000000000000000c RBX: ffff888275b00988 RCX: 0000000000000000 <4> [666.514391] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff88827596a800 <4> [666.514399] RBP: ffff8882677a4f00 R08: 000000000014ce79 R09: ffff888251014000 <4> [666.514408] R10: ffffc9000039fc10 R11: ffff88827596a800 R12: ffff88813fc76648 <4> [666.514419] R13: ffffc9000039fcd0 R14: ffff88813fc76440 R15: ffffc9000039fcd0 <4> [666.514479] ? __i915_vma_unbind.part.39+0x207/0x460 [i915] <4> [666.514533] i915_vma_unbind+0x2d/0x50 [i915] <4> [666.514585] i915_gem_object_unbind+0x11c/0x250 [i915] <4> [666.514637] i915_gem_shrink+0x297/0x5f0 [i915] <4> [666.514684] ? i915_drop_caches_set+0x141/0x250 [i915] <4> [666.514725] i915_drop_caches_set+0x141/0x250 [i915] <4> [666.514737] simple_attr_write+0xb0/0xd0 <4> [666.514747] full_proxy_write+0x51/0x80 <4> [666.514757] vfs_write+0xb9/0x1d0 <4> [666.514765] ksys_write+0x9f/0xe0 <4> [666.514774] do_syscall_64+0x4f/0x210 <4> [666.514782] entry_SYSCALL_64_after_hwframe+0x49/0xbe
<4> [666.514790] RIP: 0033:0x7f7235a54281 <4> [666.514796] Code: c3 0f 1f 84 00 00 00 00 00 48 8b 05 59 8d 20 00 c3 0f 1f 84 00 00 00 00 00 8b 05 8a d1 20 00 85 c0 75 16 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 d4 53 <4> [666.514815] RSP: 002b:00007fff5621f168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 <4> [666.514825] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7235a54281 <4> [666.514835] RDX: 0000000000000003 RSI: 00007fff5621f1c0 RDI: 0000000000000008 <4> [666.514846] RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000 <4> [666.514856] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff5621f1c0 <4> [666.514866] R13: 0000000000000008 R14: 00007fff5621f1c0 R15: 0000000000000000
I don't see any obvious fdo bugs that match this?
Matt
>
Matt, I have reported this issue here https://bugs.freedesktop.org/show_bug.cgi?id=112068
Lakshmi.
>
> #### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * {igt at kms_cursor_crc@pipe-d-cursor-128x42-sliding}:
> - {shard-tglb}: NOTRUN -> [FAIL][5] +4 similar issues
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-tglb1/i
> gt at kms_cursor_crc@pipe-d-cursor-128x42-sliding.html
>
> * {igt at kms_cursor_crc@pipe-d-cursor-512x170-offscreen}:
> - {shard-tglb}: NOTRUN -> [SKIP][6] +2 similar issues
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-tglb5/i
> gt at kms_cursor_crc@pipe-d-cursor-512x170-offscreen.html
>
>
> New tests
> ---------
>
> New tests have been introduced between CI_DRM_7122_full and Patchwork_14860_full:
>
> ### New Piglit tests (3) ###
>
> * spec at arb_texture_compression@fbo-generatemipmap-formats:
> - Statuses : 1 incomplete(s)
> - Exec time: [0.0] s
>
> * spec at arb_texture_compression_bptc@fbo-generatemipmap-formats float:
> - Statuses : 1 incomplete(s)
> - Exec time: [0.0] s
>
> * spec at arb_texture_compression_bptc@fbo-generatemipmap-formats unorm:
> - Statuses : 1 incomplete(s)
> - Exec time: [0.0] s
>
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_14860_full that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt at gem_exec_schedule@preempt-queue-chain-bsd2:
> - shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276]) +12 similar issues
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb1/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html
> [8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb8/i
> gt at gem_exec_schedule@preempt-queue-chain-bsd2.html
>
> * igt at gem_exec_schedule@preempt-queue-contexts-chain-bsd:
> - shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#111325]) +3 similar issues
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb7/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html
> [10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb1/i
> gt at gem_exec_schedule@preempt-queue-contexts-chain-bsd.html
>
> * igt at gem_userptr_blits@dmabuf-unsync:
> - shard-snb: [PASS][11] -> [DMESG-WARN][12] ([fdo#111870])
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-snb5/igt@gem_userptr_blits@dmabuf-unsync.html
> [12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-snb2/ig
> t at gem_userptr_blits@dmabuf-unsync.html
>
> * igt at gem_userptr_blits@sync-unmap-after-close:
> - shard-apl: [PASS][13] -> [DMESG-WARN][14] ([fdo#109385] / [fdo#111870])
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-apl8/igt@gem_userptr_blits@sync-unmap-after-close.html
> [14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-apl4/ig
> t at gem_userptr_blits@sync-unmap-after-close.html
>
> * igt at i915_pm_rpm@i2c:
> - shard-glk: [PASS][15] -> [FAIL][16] ([fdo#104097])
> [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-glk4/igt@i915_pm_rpm@i2c.html
> [16]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-glk8/ig
> t at i915_pm_rpm@i2c.html
>
> * igt at kms_color@pipe-b-ctm-blue-to-red:
> - shard-skl: [PASS][17] -> [DMESG-WARN][18] ([fdo#106107])
> [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-skl5/igt@kms_color@pipe-b-ctm-blue-to-red.html
> [18]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-skl9/ig
> t at kms_color@pipe-b-ctm-blue-to-red.html
>
> * igt at kms_flip@2x-flip-vs-expired-vblank:
> - shard-glk: [PASS][19] -> [FAIL][20] ([fdo#105363])
> [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-glk7/igt@kms_flip@2x-flip-vs-expired-vblank.html
> [20]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-glk9/ig
> t at kms_flip@2x-flip-vs-expired-vblank.html
>
> * igt at kms_flip@2x-modeset-vs-vblank-race:
> - shard-glk: [PASS][21] -> [FAIL][22] ([fdo#111609])
> [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-glk7/igt@kms_flip@2x-modeset-vs-vblank-race.html
> [22]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-glk9/ig
> t at kms_flip@2x-modeset-vs-vblank-race.html
>
> * igt at kms_flip@flip-vs-expired-vblank-interruptible:
> - shard-skl: [PASS][23] -> [FAIL][24] ([fdo#105363])
> [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-skl5/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
> [24]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-skl2/ig
> t at kms_flip@flip-vs-expired-vblank-interruptible.html
>
> * igt at kms_frontbuffer_tracking@fbc-1p-rte:
> - shard-iclb: [PASS][25] -> [FAIL][26] ([fdo#103167] / [fdo#110378]) +1 similar issue
> [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-rte.html
> [26]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb4/i
> gt at kms_frontbuffer_tracking@fbc-1p-rte.html
>
> * igt at kms_frontbuffer_tracking@fbc-rgb565-draw-blt:
> - shard-iclb: [PASS][27] -> [FAIL][28] ([fdo#103167]) +4 similar issues
> [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-blt.html
> [28]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb2/i
> gt at kms_frontbuffer_tracking@fbc-rgb565-draw-blt.html
>
> * igt at kms_plane_alpha_blend@pipe-a-constant-alpha-min:
> - shard-skl: [PASS][29] -> [FAIL][30] ([fdo#108145])
> [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-skl3/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
> [30]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-skl6/ig
> t at kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
>
> * igt at kms_psr@psr2_sprite_plane_move:
> - shard-iclb: [PASS][31] -> [SKIP][32] ([fdo#109441]) +2 similar issues
> [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
> [32]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb3/i
> gt at kms_psr@psr2_sprite_plane_move.html
>
> * igt at kms_vblank@pipe-a-ts-continuation-suspend:
> - shard-apl: [PASS][33] -> [DMESG-WARN][34] ([fdo#108566]) +5 similar issues
> [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-apl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
> [34]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-apl3/ig
> t at kms_vblank@pipe-a-ts-continuation-suspend.html
>
> * igt at kms_vblank@pipe-b-ts-continuation-dpms-rpm:
> - shard-iclb: [PASS][35] -> [INCOMPLETE][36] ([fdo#107713]) +1 similar issue
> [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb4/igt@kms_vblank@pipe-b-ts-continuation-dpms-rpm.html
> [36]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb1/i
> gt at kms_vblank@pipe-b-ts-continuation-dpms-rpm.html
>
>
> #### Possible fixes ####
>
> * igt at gem_exec_schedule@preempt-queue-bsd1:
> - shard-iclb: [SKIP][37] ([fdo#109276]) -> [PASS][38] +17 similar issues
> [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb3/igt@gem_exec_schedule@preempt-queue-bsd1.html
> [38]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb4/i
> gt at gem_exec_schedule@preempt-queue-bsd1.html
>
> * igt at gem_exec_schedule@reorder-wide-bsd:
> - shard-iclb: [SKIP][39] ([fdo#111325]) -> [PASS][40] +6 similar issues
> [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb2/igt@gem_exec_schedule@reorder-wide-bsd.html
> [40]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb3/i
> gt at gem_exec_schedule@reorder-wide-bsd.html
>
> * igt at gem_userptr_blits@map-fixed-invalidate-busy-gup:
> - shard-apl: [INCOMPLETE][41] ([fdo#103927]) -> [PASS][42] +4 similar issues
> [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-apl3/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
> [42]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-apl3/ig
> t at gem_userptr_blits@map-fixed-invalidate-busy-gup.html
>
> * igt at gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup:
> - shard-snb: [DMESG-WARN][43] ([fdo#111870]) -> [PASS][44]
> [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
> [44]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-snb7/ig
> t at gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
>
> * igt at gem_userptr_blits@sync-unmap-after-close:
> - shard-hsw: [DMESG-WARN][45] ([fdo#111870]) -> [PASS][46]
> [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-hsw7/igt@gem_userptr_blits@sync-unmap-after-close.html
> [46]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-hsw7/ig
> t at gem_userptr_blits@sync-unmap-after-close.html
>
> * igt at i915_selftest@live_execlists:
> - shard-skl: [DMESG-FAIL][47] -> [PASS][48]
> [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-skl9/igt@i915_selftest@live_execlists.html
> [48]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-skl1/ig
> t at i915_selftest@live_execlists.html
>
> * igt at i915_suspend@sysfs-reader:
> - shard-apl: [DMESG-WARN][49] ([fdo#108566]) -> [PASS][50] +3 similar issues
> [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-apl2/igt@i915_suspend@sysfs-reader.html
> [50]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-apl1/ig
> t at i915_suspend@sysfs-reader.html
>
> * igt at kms_atomic@crtc_invalid_params:
> - shard-snb: [SKIP][51] ([fdo#109271]) -> [PASS][52]
> [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-snb7/igt@kms_atomic@crtc_invalid_params.html
> [52]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-snb7/ig
> t at kms_atomic@crtc_invalid_params.html
>
> * igt at kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
> - shard-hsw: [FAIL][53] ([fdo#105767]) -> [PASS][54]
> [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
> [54]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-hsw4/ig
> t at kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
>
> * igt at kms_flip@flip-vs-expired-vblank:
> - shard-apl: [FAIL][55] ([fdo#105363]) -> [PASS][56]
> [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-apl6/igt@kms_flip@flip-vs-expired-vblank.html
> [56]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-apl7/ig
> t at kms_flip@flip-vs-expired-vblank.html
>
> * igt at kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render:
> - shard-iclb: [FAIL][57] ([fdo#103167]) -> [PASS][58] +2 similar issues
> [57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html
> [58]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb1/i
> gt at kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html
>
> * igt at kms_plane_alpha_blend@pipe-a-coverage-7efc:
> - shard-skl: [FAIL][59] ([fdo#108145]) -> [PASS][60]
> [59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-skl4/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
> [60]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-skl8/ig
> t at kms_plane_alpha_blend@pipe-a-coverage-7efc.html
>
> * igt at kms_setmode@basic:
> - shard-apl: [FAIL][61] ([fdo#99912]) -> [PASS][62]
> [61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-apl4/igt@kms_setmode@basic.html
> [62]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-apl4/ig
> t at kms_setmode@basic.html
>
>
> #### Warnings ####
>
> * igt at gem_ctx_isolation@vcs1-nonpriv:
> - shard-iclb: [SKIP][63] ([fdo#109276]) -> [FAIL][64] ([fdo#111329])
> [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7122/shard-iclb7/igt@gem_ctx_isolation@vcs1-nonpriv.html
> [64]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14860/shard-iclb1/i
> gt at gem_ctx_isolation@vcs1-nonpriv.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
> [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
> [fdo#104097]: https://bugs.freedesktop.org/show_bug.cgi?id=104097
> [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
> [fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
> [fdo#105767]: https://bugs.freedesktop.org/show_bug.cgi?id=105767
> [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
> [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#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
> [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
> [fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385
> [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
> [fdo#110378]: https://bugs.freedesktop.org/show_bug.cgi?id=110378
> [fdo#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548
> [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
> [fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329
> [fdo#111609]: https://bugs.freedesktop.org/show_bug.cgi?id=111609
> [fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832
> [fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850
> [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
> [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
>
>
> Participating hosts (11 -> 11)
> ------------------------------
>
> No changes in participating hosts
>
>
> Build changes
> -------------
>
> * CI: CI-20190529 -> None
> * Linux: CI_DRM_7122 -> Patchwork_14860
>
> CI-20190529: 20190529
> CI_DRM_7122: c2f6bdc09f8f046cd38e3c39c92e14e6033dbd44 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5232: bb5735423eaf6fdbf6b2f94ef0b8520e74eab993 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_14860: 44f036318c26aba453888e79cedbe7f64b54bde7 @ 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_14860/index.html
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
(916) 356-2795
------------------------------
Subject: Digest Footer
_______________________________________________
Intel-gfx mailing list
Intel-gfx at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
------------------------------
End of Intel-gfx Digest, Vol 141, Issue 541
*******************************************
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
More information about the Intel-gfx
mailing list