CI Bug Log - changes from CI_DRM_9092 -> Patchwork_18612

Summary

FAILURE

Serious unknown changes coming with Patchwork_18612 absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_18612, 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_18612/index.html

Possible new issues

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

IGT changes

Possible regressions

• igt@gem_exec_suspend@basic-s3:
  • fi-bsw-kefka: PASS -> DMESG-WARN

Known issues

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

IGT changes

Issues hit

• igt@kms_chamelium@hdmi-crc-fast:

  • fi-kbl-7500u: PASS -> FAIL (i915#1372)

• igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:

  • fi-byt-j1900: PASS -> DMESG-WARN (i915#1982)

• igt@vgem_basic@unload:

  • fi-kbl-x1275: PASS -> DMESG-WARN (i915#62 / i915#92)

Possible fixes

• igt@i915_pm_rpm@basic-pci-d3-state:

  • fi-bsw-kefka: DMESG-WARN (i915#1982) -> PASS

• igt@kms_busy@basic@flip:

  • fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92 / i915#95) -> PASS +1 similar issue

• igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:

  • fi-icl-u2: DMESG-WARN (i915#1982) -> PASS +2 similar issues

• igt@vgem_basic@unload:

  • fi-skl-guc: DMESG-WARN (i915#2203) -> PASS

Warnings

• igt@gem_exec_suspend@basic-s0:

  • fi-kbl-x1275: DMESG-WARN (i915#1982 / i915#62 / i915#92 / i915#95) -> DMESG-WARN (i915#62 / i915#92)

• igt@i915_pm_rpm@module-reload:

  • fi-kbl-x1275: DMESG-FAIL (i915#62) -> SKIP (fdo#109271)

• igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:

  • fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92 / i915#95) -> DMESG-WARN (i915#62 / i915#92) +4 similar issues

• igt@prime_vgem@basic-fence-flip:

  • fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92) -> DMESG-WARN (i915#62 / i915#92 / i915#95) +2 similar issues

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

Participating hosts (45 -> 39)

Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus

Build changes

• Linux: CI_DRM_9092 -> Patchwork_18612

CI-20190529: 20190529
CI_DRM_9092: 4e9a7e28ea34e4b14e66cbc53fc004e4a93f5168 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5797: 1a7ef7eb5e99c9a8f4ffbc13cdae399a01a9aa12 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18612: 573e3a0cb12237929f42c604daab6013e2f2cdff @ git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

573e3a0cb122 mm: remove alloc_vm_area
90dc709c8ef1 x86/xen: open code alloc_vm_area in arch_gnttab_valloc
31cb20191c3c xen/xenbus: use apply_to_page_range directly in xenbus_map_ring_pv
1f9fc4cfd84c drm/i915: use vmap in i915_gem_object_map
b692d6ffb709 drm/i915: stop using kmap in i915_gem_object_map
96b3d73ace0b drm/i915: use vmap in shmem_pin_map
d5f375c01071 zsmalloc: switch from alloc_vm_area to get_vm_area
53cab076613e mm: allow a NULL fn callback in apply_to_page_range
31a259dcbf9f mm: add a vmap_pfn function
c01ba7b7b91e mm: add a VM_MAP_PUT_PAGES flag for vmap
403e54bb3db2 mm: update the documentation for vfree