All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [v2] drm/i915: Check caller held wakerefs in assert_forcewakes_active (rev2)
Date: Thu, 04 Jul 2019 09:26:35 -0000	[thread overview]
Message-ID: <20190704092635.29488.42963@emeril.freedesktop.org> (raw)
In-Reply-To: <20190703155225.9501-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [v2] drm/i915: Check caller held wakerefs in assert_forcewakes_active (rev2)
URL   : https://patchwork.freedesktop.org/series/63151/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_6408 -> Patchwork_13523
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with Patchwork_13523 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_13523, 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_13523/

Possible new issues
-------------------

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

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live_hangcheck:
    - fi-kbl-r:           NOTRUN -> [DMESG-WARN][1]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-kbl-r/igt@i915_selftest@live_hangcheck.html
    - fi-skl-guc:         [PASS][2] -> [DMESG-WARN][3]
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-skl-guc/igt@i915_selftest@live_hangcheck.html
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-skl-guc/igt@i915_selftest@live_hangcheck.html
    - fi-cfl-8700k:       [PASS][4] -> [DMESG-WARN][5]
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-cfl-8700k/igt@i915_selftest@live_hangcheck.html
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-cfl-8700k/igt@i915_selftest@live_hangcheck.html
    - fi-whl-u:           [PASS][6] -> [DMESG-WARN][7]
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-whl-u/igt@i915_selftest@live_hangcheck.html
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-whl-u/igt@i915_selftest@live_hangcheck.html
    - fi-cfl-guc:         [PASS][8] -> [DMESG-WARN][9]
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-cfl-guc/igt@i915_selftest@live_hangcheck.html
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-cfl-guc/igt@i915_selftest@live_hangcheck.html
    - fi-cml-u:           NOTRUN -> [DMESG-WARN][10]
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-cml-u/igt@i915_selftest@live_hangcheck.html
    - fi-kbl-7500u:       [PASS][11] -> [DMESG-WARN][12]
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-kbl-7500u/igt@i915_selftest@live_hangcheck.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-kbl-7500u/igt@i915_selftest@live_hangcheck.html
    - fi-kbl-8809g:       [PASS][13] -> [DMESG-WARN][14]
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-kbl-8809g/igt@i915_selftest@live_hangcheck.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-kbl-8809g/igt@i915_selftest@live_hangcheck.html
    - fi-bxt-dsi:         [PASS][15] -> [DMESG-WARN][16]
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-bxt-dsi/igt@i915_selftest@live_hangcheck.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-bxt-dsi/igt@i915_selftest@live_hangcheck.html
    - fi-apl-guc:         [PASS][17] -> [DMESG-WARN][18]
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-apl-guc/igt@i915_selftest@live_hangcheck.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-apl-guc/igt@i915_selftest@live_hangcheck.html
    - fi-cml-u2:          [PASS][19] -> [DMESG-WARN][20]
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-cml-u2/igt@i915_selftest@live_hangcheck.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-cml-u2/igt@i915_selftest@live_hangcheck.html
    - fi-skl-6600u:       [PASS][21] -> [DMESG-WARN][22]
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-skl-6600u/igt@i915_selftest@live_hangcheck.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-skl-6600u/igt@i915_selftest@live_hangcheck.html
    - fi-bsw-n3050:       [PASS][23] -> [DMESG-WARN][24]
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-bsw-n3050/igt@i915_selftest@live_hangcheck.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-bsw-n3050/igt@i915_selftest@live_hangcheck.html
    - fi-skl-lmem:        [PASS][25] -> [DMESG-WARN][26]
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-skl-lmem/igt@i915_selftest@live_hangcheck.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-skl-lmem/igt@i915_selftest@live_hangcheck.html
    - fi-skl-6260u:       [PASS][27] -> [DMESG-WARN][28]
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-skl-6260u/igt@i915_selftest@live_hangcheck.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-skl-6260u/igt@i915_selftest@live_hangcheck.html

  * igt@runner@aborted:
    - fi-kbl-7500u:       NOTRUN -> [FAIL][29]
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-kbl-7500u/igt@runner@aborted.html
    - fi-cml-u2:          NOTRUN -> [FAIL][30]
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-cml-u2/igt@runner@aborted.html
    - fi-bxt-dsi:         NOTRUN -> [FAIL][31]
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-bxt-dsi/igt@runner@aborted.html
    - fi-cfl-8700k:       NOTRUN -> [FAIL][32]
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-cfl-8700k/igt@runner@aborted.html
    - fi-kbl-8809g:       NOTRUN -> [FAIL][33]
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-kbl-8809g/igt@runner@aborted.html

  
Known issues
------------

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_ctx_create@basic-files:
    - fi-icl-dsi:         [PASS][34] -> [INCOMPLETE][35] ([fdo#107713] / [fdo#109100])
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-icl-dsi/igt@gem_ctx_create@basic-files.html
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-icl-dsi/igt@gem_ctx_create@basic-files.html

  * igt@gem_exec_suspend@basic-s3:
    - fi-icl-u3:          [PASS][36] -> [DMESG-WARN][37] ([fdo#107724]) +1 similar issue
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-icl-u3/igt@gem_exec_suspend@basic-s3.html
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-icl-u3/igt@gem_exec_suspend@basic-s3.html
    - fi-blb-e6850:       [PASS][38] -> [INCOMPLETE][39] ([fdo#107718])
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html

  * igt@i915_selftest@live_contexts:
    - fi-skl-iommu:       [PASS][40] -> [INCOMPLETE][41] ([fdo#111050])
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-skl-iommu/igt@i915_selftest@live_contexts.html
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/fi-skl-iommu/igt@i915_selftest@live_contexts.html

  * igt@kms_chamelium@hdmi-hpd-fast:
    - fi-kbl-7500u:       [PASS][42] -> [FAIL][43] ([fdo#109485])
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6408/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/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#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
  [fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
  [fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
  [fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
  [fdo#111050]: https://bugs.freedesktop.org/show_bug.cgi?id=111050


Participating hosts (53 -> 47)
------------------------------

  Additional (2): fi-kbl-r fi-cml-u 
  Missing    (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus 


Build changes
-------------

  * Linux: CI_DRM_6408 -> Patchwork_13523

  CI_DRM_6408: ee60427a5d560ee44370d88f70db1497df9df979 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_5082: f7c51e6fbf8da0784b64a1edaee5266aa9b9f829 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_13523: a81e05e63cf25cc60552efb4fa36e6d0354c1211 @ git://anongit.freedesktop.org/gfx-ci/linux


== Kernel 32bit build ==

Warning: Kernel 32bit buildtest failed:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/build_32bit.log

  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  CHK     include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready  (#1)
  Building modules, stage 2.
  MODPOST 112 modules
ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
ERROR: "__divdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
scripts/Makefile.modpost:91: recipe for target '__modpost' failed
make[1]: *** [__modpost] Error 1
Makefile:1287: recipe for target 'modules' failed
make: *** [modules] Error 2


== Linux commits ==

a81e05e63cf2 drm/i915/gt: Ignore forcewake acquisition for posting_reads
44eaaa00a827 drm/i915/gt: Assume we hold forcewake for execlists resume
2a21d0a25bdf drm/i915/gt: Use caller provided forcewake for intel_mocs_init_engine
cae32317d674 drm/i915: Check caller held wakerefs in assert_forcewakes_active

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13523/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-07-04  9:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 15:52 [PATCH 1/4] drm/i915: Check caller held wakerefs in assert_forcewakes_active Chris Wilson
2019-07-03 15:52 ` [PATCH 2/4] drm/i915/gt: Use caller provided forcewake for intel_mocs_init_engine Chris Wilson
2019-07-03 15:52 ` [PATCH 3/4] drm/i915/gt: Assume we hold forcewake for execlists resume Chris Wilson
2019-07-03 15:52 ` [PATCH 4/4] drm/i915/gt: Ignore forcewake acquisition for posting_reads Chris Wilson
2019-07-03 18:46 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915: Check caller held wakerefs in assert_forcewakes_active Patchwork
2019-07-04  8:17 ` [PATCH v2] " Chris Wilson
2019-07-04  8:38   ` Tvrtko Ursulin
2019-07-04  9:26 ` Patchwork [this message]
2019-07-04  9:37 ` [PATCH v3] " Chris Wilson
2019-07-04 10:14 ` ✗ Fi.CI.BAT: failure for series starting with [v3] drm/i915: Check caller held wakerefs in assert_forcewakes_active (rev3) Patchwork
2019-07-04 10:20 ` [PATCH v4] drm/i915: Check caller held wakerefs in assert_forcewakes_active Chris Wilson
2019-07-04 12:12 ` ✓ Fi.CI.BAT: success for series starting with [v4] drm/i915: Check caller held wakerefs in assert_forcewakes_active (rev4) Patchwork
2019-07-04 22:46 ` ✗ Fi.CI.IGT: failure for series starting with [1/4] drm/i915: Check caller held wakerefs in assert_forcewakes_active Patchwork
2019-07-05 15:06 ` ✗ Fi.CI.IGT: failure for series starting with [v4] drm/i915: Check caller held wakerefs in assert_forcewakes_active (rev4) Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190704092635.29488.42963@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.