From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Refactor Gen11+ SAGV support (rev3)
Date: Wed, 11 Mar 2020 14:20:22 +0000 [thread overview]
Message-ID: <38223266dea64ddb9861aa69b41ac4f6@intel.com> (raw)
In-Reply-To: <158393124993.13953.15733713681899245481@emeril.freedesktop.org>
[-- Attachment #1.1: Type: text/plain, Size: 7279 bytes --]
BAT failure is due to rather funny issue, with plane states, this is a true failure however
apparently now the reason is identified. The old code was lacking a proper plane state enumeration, which caused an issue once SAGV changes forced it to be executed in other place.
Best Regards,
Lisovskiy Stanislav
________________________________
From: Patchwork <patchwork@emeril.freedesktop.org>
Sent: Wednesday, March 11, 2020 2:54:09 PM
To: Lisovskiy, Stanislav
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for Refactor Gen11+ SAGV support (rev3)
== Series Details ==
Series: Refactor Gen11+ SAGV support (rev3)
URL : https://patchwork.freedesktop.org/series/74461/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8117 -> Patchwork_16922
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_16922 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_16922, 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_16922/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_16922:
### IGT changes ###
#### Possible regressions ####
* igt@kms_busy@basic@modeset:
- fi-skl-6700k2: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-skl-6700k2/igt@kms_busy@basic@modeset.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-skl-6700k2/igt@kms_busy@basic@modeset.html
- fi-skl-guc: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-skl-guc/igt@kms_busy@basic@modeset.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-skl-guc/igt@kms_busy@basic@modeset.html
- fi-kbl-7500u: [PASS][5] -> [INCOMPLETE][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-kbl-7500u/igt@kms_busy@basic@modeset.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-kbl-7500u/igt@kms_busy@basic@modeset.html
- fi-cfl-8109u: [PASS][7] -> [INCOMPLETE][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-cfl-8109u/igt@kms_busy@basic@modeset.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-cfl-8109u/igt@kms_busy@basic@modeset.html
* igt@kms_force_connector_basic@force-connector-state:
- fi-kbl-guc: [PASS][9] -> [DMESG-WARN][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-kbl-guc/igt@kms_force_connector_basic@force-connector-state.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-kbl-guc/igt@kms_force_connector_basic@force-connector-state.html
Known issues
------------
Here are the changes found in Patchwork_16922 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s0:
- fi-skl-6600u: [PASS][11] -> [INCOMPLETE][12] ([i915#1242] / [i915#198])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-skl-6600u/igt@gem_exec_suspend@basic-s0.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-skl-6600u/igt@gem_exec_suspend@basic-s0.html
- fi-skl-6770hq: [PASS][13] -> [INCOMPLETE][14] ([i915#1242] / [i915#198])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-skl-6770hq/igt@gem_exec_suspend@basic-s0.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-skl-6770hq/igt@gem_exec_suspend@basic-s0.html
- fi-cfl-8700k: [PASS][15] -> [INCOMPLETE][16] ([i915#1242])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-cfl-8700k/igt@gem_exec_suspend@basic-s0.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-cfl-8700k/igt@gem_exec_suspend@basic-s0.html
- fi-cfl-guc: [PASS][17] -> [INCOMPLETE][18] ([i915#1242])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-cfl-guc/igt@gem_exec_suspend@basic-s0.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-cfl-guc/igt@gem_exec_suspend@basic-s0.html
* igt@kms_busy@basic@modeset:
- fi-cml-s: [PASS][19] -> [INCOMPLETE][20] ([i915#283])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-cml-s/igt@kms_busy@basic@modeset.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-cml-s/igt@kms_busy@basic@modeset.html
- fi-cml-u2: [PASS][21] -> [INCOMPLETE][22] ([i915#283])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-cml-u2/igt@kms_busy@basic@modeset.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-cml-u2/igt@kms_busy@basic@modeset.html
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-apl-guc: [INCOMPLETE][23] ([fdo#103927]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-apl-guc/igt@i915_selftest@live@execlists.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-apl-guc/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@hangcheck:
- fi-apl-guc: [DMESG-WARN][25] -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8117/fi-apl-guc/igt@i915_selftest@live@hangcheck.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/fi-apl-guc/igt@i915_selftest@live@hangcheck.html
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[i915#1242]: https://gitlab.freedesktop.org/drm/intel/issues/1242
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#283]: https://gitlab.freedesktop.org/drm/intel/issues/283
Participating hosts (49 -> 40)
------------------------------
Missing (9): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-kbl-x1275 fi-skl-lmem fi-byt-clapper fi-kbl-r
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8117 -> Patchwork_16922
CI-20190529: 20190529
CI_DRM_8117: 39a97a79462bf47caf47d8e56e1027dcedb92bb9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5505: 8973d811f3fdfb4ace4aabab2095ce0309881648 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16922: f580b31fefefdc4e3175f47241c52a92d538821a @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
f580b31fefef drm/i915: Enable SAGV support for Gen12
a94ebc238e1b drm/i915: Restrict qgv points which don't have enough bandwidth.
c8c7805a79f0 drm/i915: Rename bw_state to new_bw_state
d423ddd36f1b drm/i915: Added required new PCode commands
7dc425c57481 drm/i915: Refactor intel_can_enable_sagv
6468178f6e57 drm/i915: Add intel_bw_get_*_state helpers
f4d2893b925e drm/i915: Introduce skl_plane_wm_level accessor.
aad38ffe3258 drm/i915: Start passing latency as parameter
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16922/index.html
[-- Attachment #1.2: Type: text/html, Size: 13691 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-11 14:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 16:11 [Intel-gfx] [PATCH v19 0/8] Refactor Gen11+ SAGV support Stanislav Lisovskiy
2020-03-09 16:11 ` [Intel-gfx] [PATCH v19 1/8] drm/i915: Start passing latency as parameter Stanislav Lisovskiy
2020-03-10 14:32 ` Ville Syrjälä
2020-03-10 14:54 ` Lisovskiy, Stanislav
2020-03-10 20:44 ` Ville Syrjälä
2020-03-11 9:16 ` Stanislav Lisovskiy
2020-03-09 16:11 ` [Intel-gfx] [PATCH v19 2/8] drm/i915: Introduce skl_plane_wm_level accessor Stanislav Lisovskiy
[not found] ` <20200311160727.GA13686@intel.com>
2020-03-13 8:42 ` Lisovskiy, Stanislav
2020-03-09 16:11 ` [Intel-gfx] [PATCH v19 3/8] drm/i915: Add intel_bw_get_*_state helpers Stanislav Lisovskiy
[not found] ` <20200311160854.GB13686@intel.com>
2020-03-13 8:49 ` Lisovskiy, Stanislav
2020-03-13 13:26 ` Ville Syrjälä
2020-03-13 13:57 ` Lisovskiy, Stanislav
2020-03-13 14:14 ` Ville Syrjälä
2020-03-09 16:12 ` [Intel-gfx] [PATCH v19 4/8] drm/i915: Refactor intel_can_enable_sagv Stanislav Lisovskiy
2020-03-11 9:13 ` Stanislav Lisovskiy
[not found] ` <20200311163130.GC13686@intel.com>
2020-03-18 11:52 ` Lisovskiy, Stanislav
2020-03-18 12:50 ` Ville Syrjälä
2020-03-19 13:09 ` Lisovskiy, Stanislav
2020-03-20 12:51 ` Lisovskiy, Stanislav
2020-03-23 14:18 ` Ville Syrjälä
2020-03-23 14:36 ` Lisovskiy, Stanislav
2020-03-23 14:50 ` Ville Syrjälä
2020-03-23 14:58 ` Lisovskiy, Stanislav
2020-03-09 16:12 ` [Intel-gfx] [PATCH v19 5/8] drm/i915: Added required new PCode commands Stanislav Lisovskiy
2020-03-09 16:12 ` [Intel-gfx] [PATCH v19 6/8] drm/i915: Rename bw_state to new_bw_state Stanislav Lisovskiy
2020-03-09 16:12 ` [Intel-gfx] [PATCH v19 7/8] drm/i915: Restrict qgv points which don't have enough bandwidth Stanislav Lisovskiy
2020-03-09 16:12 ` [Intel-gfx] [PATCH v19 8/8] drm/i915: Enable SAGV support for Gen12 Stanislav Lisovskiy
2020-03-09 16:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Refactor Gen11+ SAGV support Patchwork
2020-03-10 13:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-11 12:54 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Refactor Gen11+ SAGV support (rev3) Patchwork
2020-03-11 14:20 ` Lisovskiy, Stanislav [this message]
2020-03-11 19:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Refactor Gen11+ SAGV support (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=38223266dea64ddb9861aa69b41ac4f6@intel.com \
--to=stanislav.lisovskiy@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox