From: "Peres, Martin" <martin.peres@intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and TGL (rev20)
Date: Tue, 21 Jan 2020 09:06:44 +0000 [thread overview]
Message-ID: <b10bc0effc4e48aa8a60976773fb8b68@intel.com> (raw)
In-Reply-To: ce6a9cf5c7a6452eb643ff5633484378@intel.com
Thanks for notifying us!
Re-reporting queued.
Martin
On 21/01/2020 10:58, Lisovskiy, Stanislav wrote:
> Looks, like needs one more bug to be reported, again some gem/gpu
> related issue..
>
>
> Best Regards,
>
> Lisovskiy Stanislav
>
> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160
> Espoo
> ------------------------------------------------------------------------
> *From:* Patchwork <patchwork@emeril.freedesktop.org>
> *Sent:* Tuesday, January 21, 2020 2:26:31 AM
> *To:* Lisovskiy, Stanislav
> *Cc:* intel-gfx@lists.freedesktop.org
> *Subject:* ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and
> TGL (rev20)
>
> == Series Details ==
>
> Series: Enable second DBuf slice for ICL and TGL (rev20)
> URL : https://patchwork.freedesktop.org/series/70059/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7781 -> Patchwork_16174
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_16174 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_16174, 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_16174/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in
> Patchwork_16174:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live_gt_engines:
> - fi-skl-lmem: [PASS][1] -> [INCOMPLETE][2]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-skl-lmem/igt@i915_selftest@live_gt_engines.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-skl-lmem/igt@i915_selftest@live_gt_engines.html
>
>
> #### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_parallel@basic:
> - {fi-ehl-1}: NOTRUN -> [FAIL][3]
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-ehl-1/igt@gem_exec_parallel@basic.html
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_16174 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@gem_close_race@basic-threads:
> - fi-byt-j1900: [PASS][4] -> [TIMEOUT][5] ([fdo#112271] /
> [i915#816])
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-byt-j1900/igt@gem_close_race@basic-threads.html
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-byt-j1900/igt@gem_close_race@basic-threads.html
>
> * igt@i915_selftest@live_uncore:
> - fi-skl-lmem: [PASS][6] -> [DMESG-FAIL][7] ([i915#889])
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-skl-lmem/igt@i915_selftest@live_uncore.html
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-skl-lmem/igt@i915_selftest@live_uncore.html
>
> * igt@i915_selftest@live_workarounds:
> - fi-skl-lmem: [PASS][8] -> [DMESG-WARN][9] ([i915#889]) +3
> similar issues
> [8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-skl-lmem/igt@i915_selftest@live_workarounds.html
> [9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-skl-lmem/igt@i915_selftest@live_workarounds.html
>
>
> #### Possible fixes ####
>
> * igt@gem_exec_gttfill@basic:
> - {fi-ehl-1}: [INCOMPLETE][10] ([i915#937]) -> [PASS][11]
> [10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-ehl-1/igt@gem_exec_gttfill@basic.html
> [11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-ehl-1/igt@gem_exec_gttfill@basic.html
>
> * igt@i915_selftest@live_blt:
> - fi-hsw-4770: [DMESG-FAIL][12] ([i915#725]) -> [PASS][13]
> [12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-hsw-4770/igt@i915_selftest@live_blt.html
> [13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-hsw-4770/igt@i915_selftest@live_blt.html
>
>
> #### Warnings ####
>
> * igt@gem_exec_parallel@contexts:
> - fi-byt-n2820: [TIMEOUT][14] ([fdo#112271]) ->
> [INCOMPLETE][15] ([i915#45])
> [14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-byt-n2820/igt@gem_exec_parallel@contexts.html
> [15]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-byt-n2820/igt@gem_exec_parallel@contexts.html
>
>
> {name}: This element is suppressed. This means it is ignored when
> computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
> [i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
> [i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
> [i915#816]: https://gitlab.freedesktop.org/drm/intel/issues/816
> [i915#889]: https://gitlab.freedesktop.org/drm/intel/issues/889
> [i915#937]: https://gitlab.freedesktop.org/drm/intel/issues/937
>
>
> Participating hosts (50 -> 40)
> ------------------------------
>
> Missing (10): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan
> fi-kbl-7500u fi-ctg-p8600 fi-ivb-3770 fi-byt-clapper fi-bsw-nick
> fi-skl-6700k2
>
>
> Build changes
> -------------
>
> * CI: CI-20190529 -> None
> * Linux: CI_DRM_7781 -> Patchwork_16174
>
> CI-20190529: 20190529
> CI_DRM_7781: 3f2b341ae1fde67f823aeb715c6f489affdef8b1 @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5374: 83c32e859202e43ff6a8cca162c76fcd90ad6e3b @
> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_16174: 553ba35fe574cc3b10b3fc35b9cfed78478bb38f @
> git://anongit.freedesktop.org/gfx-ci/linux
>
>
> == Linux commits ==
>
> 553ba35fe574 drm/i915: Correctly map DBUF slices to pipes
> bffb7bb18a34 drm/i915: Manipulate DBuf slices properly
> 3f955aa5a554 drm/i915: Introduce parameterized DBUF_CTL
> 5e3da7956ba6 drm/i915: Move dbuf slice update to proper place
> 4b13ffbbc2da drm/i915: Remove skl_ddl_allocation struct
>
> == Logs ==
>
> For more details see:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-21 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 12:20 [Intel-gfx] [PATCH v15 0/5] Enable second DBuf slice for ICL and TGL Stanislav Lisovskiy
2020-01-20 12:20 ` [Intel-gfx] [PATCH v15 1/5] drm/i915: Remove skl_ddl_allocation struct Stanislav Lisovskiy
2020-01-20 12:21 ` [Intel-gfx] [PATCH v15 2/5] drm/i915: Move dbuf slice update to proper place Stanislav Lisovskiy
2020-01-20 12:21 ` [Intel-gfx] [PATCH v15 3/5] drm/i915: Introduce parameterized DBUF_CTL Stanislav Lisovskiy
2020-01-21 19:22 ` Ville Syrjälä
2020-01-20 12:21 ` [Intel-gfx] [PATCH v15 4/5] drm/i915: Manipulate DBuf slices properly Stanislav Lisovskiy
2020-01-20 12:21 ` [Intel-gfx] [PATCH v15 5/5] drm/i915: Correctly map DBUF slices to pipes Stanislav Lisovskiy
2020-01-21 0:26 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and TGL (rev20) Patchwork
2020-01-21 8:58 ` Lisovskiy, Stanislav
2020-01-21 9:06 ` Peres, Martin [this message]
2020-01-21 9:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-22 3:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=b10bc0effc4e48aa8a60976773fb8b68@intel.com \
--to=martin.peres@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stanislav.lisovskiy@intel.com \
--cc=tomi.p.sarvela@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).