[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-05-06 Thread Patchwork 
== Series Details ==

Series: drm/i915/dmc: Load DMC on DG2 (rev4)
URL   : https://patchwork.freedesktop.org/series/103625/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11618 -> Patchwork_103625v4


Summary
---

  **SUCCESS**

  No regressions found.

  External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103625v4/index.html

Participating hosts (35 -> 34)
--

  Missing(1): fi-bsw-cyan 

Known issues


  Here are the changes found in Patchwork_103625v4 that come from known issues:

### IGT changes ###

 Issues hit 

  * igt@i915_selftest@live@hangcheck:
- fi-snb-2600:[PASS][1] -> [INCOMPLETE][2] ([i915#3921])
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11618/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103625v4/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html

  
  [i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921


Build changes
-

  * Linux: CI_DRM_11618 -> Patchwork_103625v4

  CI-20190529: 20190529
  CI_DRM_11618: 07c7d578e3b8a85c79e9a7f8dace075192d5fd91 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_6468: cffa5fffe9acddf49565b4caeeb5e3355ff2ea44 @ 
https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  Patchwork_103625v4: 07c7d578e3b8a85c79e9a7f8dace075192d5fd91 @ 
git://anongit.freedesktop.org/gfx-ci/linux


### Linux commits

f59f3563ba3e drm/i915/dmc: Load DMC on DG2

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103625v4/index.html

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-04-16 Thread Sarvela, Tomi P 
This week I've been working to get the Public CI work more reliably
on bat-* machines which are hosted on a different site.

The BAT for IGT, IGTPW, CI_DRM and Patchwork seems to be stabilized
pretty well, and probably Trybot/TrybotIGT will be added soon enough.
This isn't a promise that even one DG2 is always present on testing: the
pre-production platforms are as fickle as ever. If DG2 results are needed,
and none of the DG2 machines were successfully rebooted with the
dGPU present, best I can do is 're-test the series'.

For FULL, we can't enable all the builds on all shards because lack of
machine hours. DG2 has hundreds of more tests than the next worst shard,
the tests take more time, and we have less DG2s than the next worst shard.
In the end, we probably end up here with a w/a: DG2-specific blacklist for
the most commonly hanging, and longest lasting tests.

Regards,

Tomi


> From: De Marchi, Lucas 
> 
> On Thu, Apr 14, 2022 at 08:54:49PM +, Anusha Srivatsa wrote:
> >HI,
> >
> >The result here says SUCCESS but closer look  shows that it never ran on any
> DG2. Wanted to know if something went wrong at the system side and if it
> needs to be revived. The patch is simply loading DMC and shouldn’t cause
> the system to not boot up at all.
> >
> >Any info in this regard will be very useful.
> 
> I think the issue is less about the feedback saying "SUCCESS" and more
> about "why was it not tested on DG2 and we have no clue what happened?".
> 
> Not gating a "SUCCESS" message is needed for platforms that are unstable
> due to not been completed yet: otherwise almost all patches series would
> return "FAIL" and it would be even more useless.
> 
> So, as DG2 is one of those platforms, I think it's ok to have this
> behavior. But it's not very good to simply have no results and no
> feedback on what really happened.
> 
> Lucas De Marchi
> 
> >
> >Thanks,
> >Anusha
> >
> >From: Patchwork 
> >Sent: Thursday, April 14, 2022 11:04 AM
> >To: Srivatsa, Anusha 
> >Cc: intel-gfx@lists.freedesktop.org
> >Subject: ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)
> >
> >Patch Details
> >Series:
> >
> >drm/i915/dmc: Load DMC on DG2 (rev4)
> >
> >URL:
> >
> >https://patchwork.freedesktop.org/series/102630/
> >
> >State:
> >
> >success
> >
> >Details:
> >
> >https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html
> >
> >CI Bug Log - changes from CI_DRM_11500 -> Patchwork_102630v4
> >Summary
> >
> >SUCCESS
> >
> >No regressions found.
> >
> >External URL: https://intel-gfx-ci.01.org/tree/drm-
> tip/Patchwork_102630v4/index.html
> >
> >Participating hosts (48 -> 45)
> >
> >Additional (2): bat-adlm-1 fi-pnv-d510
> >Missing (5): bat-dg2-8 fi-bsw-cyan fi-icl-u2 bat-dg2-9 fi-bdw-samus
> >
> >Known issues
> >
> >Here are the changes found in Patchwork_102630v4 that come from known
> issues:
> >
> >IGT changes
> >Issues hit
> >
> >  *   igt@i915_selftest@live@execlists:
> >
> > *   fi-bsw-nick: PASS tip/CI_DRM_11500/fi-bsw-nick/igt@i915_selftest@l...@execlists.html> ->
> INCOMPLETE tip/Patchwork_102630v4/fi-bsw-
> nick/igt@i915_selftest@l...@execlists.html>
> (i915#2940)
> >
> >  *   igt@i915_selftest@live@hangcheck:
> >
> > *   fi-snb-2600: PASS tip/CI_DRM_11500/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html> ->
> INCOMPLETE tip/Patchwork_102630v4/fi-snb-
> 2600/igt@i915_selftest@l...@hangcheck.html>
> (i915#3921)
> >
> >  *   igt@i915_selftest@live@requests:
> >
> > *   fi-blb-e6850: PASS tip/CI_DRM_11500/fi-blb-e6850/igt@i915_selftest@l...@requests.html> ->
> DMESG-FAIL tip/Patchwork_102630v4/fi-blb-
> e6850/igt@i915_selftest@l...@requests.html>
> (i915#4528)
> >
> >  *   igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
> >
> > *   fi-pnv-d510: NOTRUN -> SKIP tip/Patchwork_102630v4/fi-pnv-d510/igt@kms_pipe_crc_basic@compare-
> crc-sanitycheck-pipe-c.html>
> (fdo#109271 /
> i915#5341)
> >
> >  *   igt@prime_vgem@basic-userptr:
> >
> > *   fi-pnv-d510: NOTRUN -> SKIP tip/Patchwork_102630v4/fi-pnv-d510/igt@prime_vgem@basic-
> userptr.html>
> (fdo#109271) +39
> similar issues
> >
> >  *   igt@runner@aborted:
> >
> > *   fi-bsw-nick: NOTRUN -> FAIL tip/Patchwork_102630v4/fi-bsw-nick/igt@run...@aborted.html>
> (fdo#109271 /
>

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-04-15 Thread Lucas De Marchi 

On Thu, Apr 14, 2022 at 09:37:14PM -0700, Lucas De Marchi wrote:

On Thu, Apr 14, 2022 at 08:54:49PM +, Anusha Srivatsa wrote:

HI,

The result here says SUCCESS but closer look  shows that it never ran on any 
DG2. Wanted to know if something went wrong at the system side and if it needs 
to be revived. The patch is simply loading DMC and shouldn’t cause the system 
to not boot up at all.

Any info in this regard will be very useful.


I think the issue is less about the feedback saying "SUCCESS" and more
about "why was it not tested on DG2 and we have no clue what happened?".

Not gating a "SUCCESS" message is needed for platforms that are unstable
due to not been completed yet: otherwise almost all patches series would
return "FAIL" and it would be even more useless.

So, as DG2 is one of those platforms, I think it's ok to have this
behavior. But it's not very good to simply have no results and no
feedback on what really happened.


So I got a local system with DG2 to check and results were not good,
which may explain the CI behavior.

Running BAT with the command below (should be roughly equivalent to what
CI uses)

$ sudo ./build/runner/igt_runner --piglit-style-dmesg 
--dmesg-warn-level 4 \
--disk-usage-limit 20M --per-test-timeout 180 \
-o -s -b tests/intel-ci/blacklist-pre-merge.txt \
--test-list tests/intel-ci/fast-feedback.testlist \
build/tests ~/igt-results

When trying this with DMC, the machine rebooted when reached the
kms_busy test. Resuming with igt_resume, the machine froze on
igt@i915_pm_rpm@basic-rte (I think, not really sure it was this, but it
was one of the pm-related patches).

If enabling DMC depends on a newer IFWI, it's likely CI system doesn't
have it. Same for the system I tried since I didn't try updating.
Either that or there still seems to be something missing. Can you try
the command above locally to make sure it at least completes?

thanks
Lucas De Marchi



Lucas De Marchi



Thanks,
Anusha

From: Patchwork 
Sent: Thursday, April 14, 2022 11:04 AM
To: Srivatsa, Anusha 
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

Patch Details
Series:

drm/i915/dmc: Load DMC on DG2 (rev4)

URL:

https://patchwork.freedesktop.org/series/102630/

State:

success

Details:

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

CI Bug Log - changes from CI_DRM_11500 -> Patchwork_102630v4
Summary

SUCCESS

No regressions found.

External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

Participating hosts (48 -> 45)

Additional (2): bat-adlm-1 fi-pnv-d510
Missing (5): bat-dg2-8 fi-bsw-cyan fi-icl-u2 bat-dg2-9 fi-bdw-samus

Known issues

Here are the changes found in Patchwork_102630v4 that come from known issues:

IGT changes
Issues hit

*   igt@i915_selftest@live@execlists:

   *   fi-bsw-nick: 
PASS
 -> 
INCOMPLETE
 (i915#2940)

*   igt@i915_selftest@live@hangcheck:

   *   fi-snb-2600: 
PASS
 -> 
INCOMPLETE
 (i915#3921)

*   igt@i915_selftest@live@requests:

   *   fi-blb-e6850: 
PASS
 -> 
DMESG-FAIL
 (i915#4528)

*   igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:

   *   fi-pnv-d510: NOTRUN -> 
SKIP
 (fdo#109271 / 
i915#5341)

*   igt@prime_vgem@basic-userptr:

   *   fi-pnv-d510: NOTRUN -> 
SKIP
 (fdo#109271) +39 similar issues

*   igt@runner@aborted:

   *   fi-bsw-nick: NOTRUN -> 
FAIL
 (fdo#109271 / 
i915#3428 / 
i915#4312)
   *   fi-bdw-5557u: NOTRUN

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-04-14 Thread Lucas De Marchi 

On Thu, Apr 14, 2022 at 08:54:49PM +, Anusha Srivatsa wrote:

HI,

The result here says SUCCESS but closer look  shows that it never ran on any 
DG2. Wanted to know if something went wrong at the system side and if it needs 
to be revived. The patch is simply loading DMC and shouldn’t cause the system 
to not boot up at all.

Any info in this regard will be very useful.


I think the issue is less about the feedback saying "SUCCESS" and more
about "why was it not tested on DG2 and we have no clue what happened?".

Not gating a "SUCCESS" message is needed for platforms that are unstable
due to not been completed yet: otherwise almost all patches series would
return "FAIL" and it would be even more useless.

So, as DG2 is one of those platforms, I think it's ok to have this
behavior. But it's not very good to simply have no results and no
feedback on what really happened.

Lucas De Marchi



Thanks,
Anusha

From: Patchwork 
Sent: Thursday, April 14, 2022 11:04 AM
To: Srivatsa, Anusha 
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

Patch Details
Series:

drm/i915/dmc: Load DMC on DG2 (rev4)

URL:

https://patchwork.freedesktop.org/series/102630/

State:

success

Details:

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

CI Bug Log - changes from CI_DRM_11500 -> Patchwork_102630v4
Summary

SUCCESS

No regressions found.

External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

Participating hosts (48 -> 45)

Additional (2): bat-adlm-1 fi-pnv-d510
Missing (5): bat-dg2-8 fi-bsw-cyan fi-icl-u2 bat-dg2-9 fi-bdw-samus

Known issues

Here are the changes found in Patchwork_102630v4 that come from known issues:

IGT changes
Issues hit

 *   igt@i915_selftest@live@execlists:

*   fi-bsw-nick: 
PASS
 -> 
INCOMPLETE
 (i915#2940)

 *   igt@i915_selftest@live@hangcheck:

*   fi-snb-2600: 
PASS
 -> 
INCOMPLETE
 (i915#3921)

 *   igt@i915_selftest@live@requests:

*   fi-blb-e6850: 
PASS
 -> 
DMESG-FAIL
 (i915#4528)

 *   igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:

*   fi-pnv-d510: NOTRUN -> 
SKIP
 (fdo#109271 / 
i915#5341)

 *   igt@prime_vgem@basic-userptr:

*   fi-pnv-d510: NOTRUN -> 
SKIP
 (fdo#109271) +39 similar issues

 *   igt@runner@aborted:

*   fi-bsw-nick: NOTRUN -> 
FAIL
 (fdo#109271 / 
i915#3428 / 
i915#4312)
*   fi-bdw-5557u: NOTRUN -> 
FAIL
 (i915#4312)
*   fi-blb-e6850: NOTRUN -> 
FAIL
 (fdo#109271 / 
i915#2403 / 
i915#4312)

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Build changes

 *   Linux: CI_DRM_11500 -> Patchwork_102630v4

CI-20190529: 20190529
CI_DRM_11500: 91c829bc09be35f3e9a6674274969c72f60b5e22 @ 
git://anongit.freedesktop.org/gfx-ci/linux
IGT_6420: a3885810ccc0ce9e6552a20c910a0a322eca466c @ 
https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_102630v4: 91c829bc09be35f3e9a6674274969c72f60b5e22 @ 
git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

16f68d87628e drm/i915/dmc:

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-04-14 Thread Srivatsa, Anusha 
HI,

The result here says SUCCESS but closer look  shows that it never ran on any 
DG2. Wanted to know if something went wrong at the system side and if it needs 
to be revived. The patch is simply loading DMC and shouldn’t cause the system 
to not boot up at all.

Any info in this regard will be very useful.

Thanks,
Anusha

From: Patchwork 
Sent: Thursday, April 14, 2022 11:04 AM
To: Srivatsa, Anusha 
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

Patch Details
Series:

drm/i915/dmc: Load DMC on DG2 (rev4)

URL:

https://patchwork.freedesktop.org/series/102630/

State:

success

Details:

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

CI Bug Log - changes from CI_DRM_11500 -> Patchwork_102630v4
Summary

SUCCESS

No regressions found.

External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

Participating hosts (48 -> 45)

Additional (2): bat-adlm-1 fi-pnv-d510
Missing (5): bat-dg2-8 fi-bsw-cyan fi-icl-u2 bat-dg2-9 fi-bdw-samus

Known issues

Here are the changes found in Patchwork_102630v4 that come from known issues:

IGT changes
Issues hit

  *   igt@i915_selftest@live@execlists:

 *   fi-bsw-nick: 
PASS
 -> 
INCOMPLETE
 (i915#2940)

  *   igt@i915_selftest@live@hangcheck:

 *   fi-snb-2600: 
PASS
 -> 
INCOMPLETE
 (i915#3921)

  *   igt@i915_selftest@live@requests:

 *   fi-blb-e6850: 
PASS
 -> 
DMESG-FAIL
 (i915#4528)

  *   igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:

 *   fi-pnv-d510: NOTRUN -> 
SKIP
 (fdo#109271 / 
i915#5341)

  *   igt@prime_vgem@basic-userptr:

 *   fi-pnv-d510: NOTRUN -> 
SKIP
 (fdo#109271) +39 similar 
issues

  *   igt@runner@aborted:

 *   fi-bsw-nick: NOTRUN -> 
FAIL
 (fdo#109271 / 
i915#3428 / 
i915#4312)
 *   fi-bdw-5557u: NOTRUN -> 
FAIL
 (i915#4312)
 *   fi-blb-e6850: NOTRUN -> 
FAIL
 (fdo#109271 / 
i915#2403 / 
i915#4312)

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Build changes

  *   Linux: CI_DRM_11500 -> Patchwork_102630v4

CI-20190529: 20190529
CI_DRM_11500: 91c829bc09be35f3e9a6674274969c72f60b5e22 @ 
git://anongit.freedesktop.org/gfx-ci/linux
IGT_6420: a3885810ccc0ce9e6552a20c910a0a322eca466c @ 
https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_102630v4: 91c829bc09be35f3e9a6674274969c72f60b5e22 @ 
git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

16f68d87628e drm/i915/dmc: Load DMC on DG2

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-04-14 Thread Patchwork 
== Series Details ==

Series: drm/i915/dmc: Load DMC on DG2 (rev4)
URL   : https://patchwork.freedesktop.org/series/102630/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11500 -> Patchwork_102630v4


Summary
---

  **SUCCESS**

  No regressions found.

  External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html

Participating hosts (48 -> 45)
--

  Additional (2): bat-adlm-1 fi-pnv-d510 
  Missing(5): bat-dg2-8 fi-bsw-cyan fi-icl-u2 bat-dg2-9 fi-bdw-samus 

Known issues


  Here are the changes found in Patchwork_102630v4 that come from known issues:

### IGT changes ###

 Issues hit 

  * igt@i915_selftest@live@execlists:
- fi-bsw-nick:[PASS][1] -> [INCOMPLETE][2] ([i915#2940])
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11500/fi-bsw-nick/igt@i915_selftest@l...@execlists.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-bsw-nick/igt@i915_selftest@l...@execlists.html

  * igt@i915_selftest@live@hangcheck:
- fi-snb-2600:[PASS][3] -> [INCOMPLETE][4] ([i915#3921])
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11500/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-snb-2600/igt@i915_selftest@l...@hangcheck.html

  * igt@i915_selftest@live@requests:
- fi-blb-e6850:   [PASS][5] -> [DMESG-FAIL][6] ([i915#4528])
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11500/fi-blb-e6850/igt@i915_selftest@l...@requests.html
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-blb-e6850/igt@i915_selftest@l...@requests.html

  * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
- fi-pnv-d510:NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#5341])
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-pnv-d510/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html

  * igt@prime_vgem@basic-userptr:
- fi-pnv-d510:NOTRUN -> [SKIP][8] ([fdo#109271]) +39 similar issues
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-pnv-d510/igt@prime_v...@basic-userptr.html

  * igt@runner@aborted:
- fi-bsw-nick:NOTRUN -> [FAIL][9] ([fdo#109271] / [i915#3428] / 
[i915#4312])
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-bsw-nick/igt@run...@aborted.html
- fi-bdw-5557u:   NOTRUN -> [FAIL][10] ([i915#4312])
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-bdw-5557u/igt@run...@aborted.html
- fi-blb-e6850:   NOTRUN -> [FAIL][11] ([fdo#109271] / [i915#2403] / 
[i915#4312])
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/fi-blb-e6850/igt@run...@aborted.html

  
  {name}: This element is suppressed. This means it is ignored when computing
  the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
  [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
  [i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
  [i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
  [i915#2403]: https://gitlab.freedesktop.org/drm/intel/issues/2403
  [i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
  [i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
  [i915#3428]: https://gitlab.freedesktop.org/drm/intel/issues/3428
  [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
  [i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
  [i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
  [i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
  [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
  [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
  [i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
  [i915#4897]: https://gitlab.freedesktop.org/drm/intel/issues/4897
  [i915#5341]: https://gitlab.freedesktop.org/drm/intel/issues/5341
  [i915#5650]: https://gitlab.freedesktop.org/drm/intel/issues/5650


Build changes
-

  * Linux: CI_DRM_11500 -> Patchwork_102630v4

  CI-20190529: 20190529
  CI_DRM_11500: 91c829bc09be35f3e9a6674274969c72f60b5e22 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_6420: a3885810ccc0ce9e6552a20c910a0a322eca466c @ 
https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  Patchwork_102630v4: 91c829bc09be35f3e9a6674274969c72f60b5e22 @ 
git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

16f68d87628e drm/i915/dmc: Load DMC on DG2

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v4/index.html