✓ Fi.CI.BAT: success for series starting with [01/37] uvd-resume

[Patchwork]

== Series Details ==

Series: series starting with [01/37] uvd-resume
URL   : https://patchwork.freedesktop.org/series/52518/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_5140 -> Trybot_3238 =

== Summary - WARNING ==

  Minor unknown changes coming with Trybot_3238 need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Trybot_3238, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/52518/revisions/1/mbox/

== Possible new issues ==

  Here are the unknown changes that may have been introduced in Trybot_3238:

  === IGT changes ===

    ==== Possible regressions ====

    igt at kms_chamelium@hdmi-edid-read:
      {fi-kbl-7567u}:     SKIP -> FAIL +3

    
    ==== Warnings ====

    igt at kms_busy@basic-flip-a:
      {fi-kbl-7567u}:     SKIP -> PASS +36

    igt at kms_pipe_crc_basic@hang-read-crc-pipe-b:
      fi-skl-guc:         PASS -> SKIP +2
      fi-apl-guc:         PASS -> SKIP +2
      fi-cfl-guc:         PASS -> SKIP +2

    
== Known issues ==

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

  === IGT changes ===

    ==== Issues hit ====

    igt at kms_pipe_crc_basic@suspend-read-crc-pipe-b:
      fi-icl-u:           PASS -> INCOMPLETE (fdo#107713)

    
    ==== Possible fixes ====

    igt at debugfs_test@read_all_entries:
      {fi-kbl-7567u}:     DMESG-WARN (fdo#105602) -> PASS

    igt at drv_module_reload@basic-reload-inject:
      {fi-kbl-7567u}:     DMESG-WARN (fdo#105602, fdo#108529) -> PASS +1

    igt at gem_exec_suspend@basic-s3:
      {fi-kbl-7567u}:     DMESG-WARN (fdo#105079, fdo#105602) -> PASS

    igt at pm_rpm@module-reload:
      {fi-kbl-7567u}:     DMESG-WARN (fdo#108529) -> PASS

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

  fdo#105079 https://bugs.freedesktop.org/show_bug.cgi?id=105079
  fdo#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
  fdo#107713 https://bugs.freedesktop.org/show_bug.cgi?id=107713
  fdo#108529 https://bugs.freedesktop.org/show_bug.cgi?id=108529


== Participating hosts (52 -> 45) ==

  Missing    (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-ctg-p8600 fi-glk-j4005 


== Build changes ==

    * Linux: CI_DRM_5140 -> Trybot_3238

  CI_DRM_5140: 68c169139ed5a6ab2aa72f84a0a7dcd0f1576717 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4714: cab148ca3ec904a94d0cd43476cf7e1f8663f906 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Trybot_3238: 8af459ce2eb73f3dfc66c5d038c4ff17669dcbad @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

8af459ce2eb7 ctx-create-ext-setparam
622fe3377843 set-vm
20b82985b582 drm/i915: Create/destroy VM (ppGTT) for use with contexts
2d959c2b5be6 drm/i915: Introduce the i915_user_extension_method
f6f81aa46238 timeline-lock
c9870e81d2d3 drm/i915: Move vma lookup to its own lock
ad847e03ded2 single-vma-list
6d2079ef4be4 drm/i915: Pull VM lists under the VM mutex.
f87f21b7293e drm/i915: Stop tracking MRU activity on VMA
edbc8012a411 drm/i915: Remove GPU reset dependence on struct_mutex
d8afe26cc649 drm/i915: Perform device reset under stop-machine
191debc674e0 drm/i915/guc: Disable global reset
6dd38fdacf7b drm/i915: Make all GPU resets atomic
129b0cae4b5d drm/i915: Pull all the reset functionality together into i915_reset.c
debf3f9b918d drm/i915: Differentiate between ggtt->mutex and ppgtt->mutex
e8cba7136ea8 drm/i915: Serialise concurrent calls to i915_gem_set_wedged()
e6172ac9174c drm/i915: Mark up Ironlake ips with rpm wakerefs
4dc6c8d47b97 drm/i915: Complain if hsw_get_pipe_config acquires the same power well twice
fa4ada835c2f drm/i915/dp: Markup pps lock power well
6c3a7ea8f227 drm/i915: Combined gt.awake/gt.power wakerefs
b8c9bc21ab5a drm/i915: Track the wakeref used to initialise display power domains
bd751824e0f0 drm/i915: Markup paired operations on display power domains
d1cca48df429 drm/i915: Syntatic sugar for using intel_runtime_pm
65fe973307b7 drm/i915: Markup paired operations on wakerefs
caf1819f3fd0 drm/i915: Track all held rpm wakerefs
3d3939aeb5df drm/i915: Remove debugfs/i915_ppgtt_info
78ece40152bc drm/i915: Report the number of closed vma held by each context in debugfs
fa2dce00b4c2 drm/i915: Cache the error string
68d94fc94eb6 drm/i915: Always try to reset the GPU on takeover
8a71094bddf0 drm/i915: Prevent machine hang from Broxton's vtd w/a and error capture
7ccc7c23db61 drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start
6e9b6a963c72 drm/i915: Return immediately if trylock fails for direct-reclaim
7af8ba7b096a drm/i915/icl: Mind the SFC units when resetting VD or VEBox engines
8066bacdbb09 drm/i915/icl: Record the valid VDBoxes with SFC capability
2ace3187628f drm/i915/selftests: Verify we can perform resets from atomic context
67a28819b326 drm/i915/selftests: Check we can recover a wedged device
29ab93584080 uvd-resume

== Logs ==

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