From: "Peres, Martin" <martin.peres@intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and TGL (rev17)
Date: Fri, 17 Jan 2020 13:08:50 +0000 [thread overview]
Message-ID: <c2af4c9bb4cb462584e58da3aa3d41e3@intel.com> (raw)
In-Reply-To: 8857174f7e0f4c02885a17f45b7ece8f@intel.com
On 17/01/2020 12:43, Lisovskiy, Stanislav wrote:
> Looks like gem issue, lots of warns - gpu has gone wild.
>
> Not related to DBuf for sure.
Thanks, it has been re-reported!
Sorry for the delay,
Martin
>
>
> Best Regards,
>
> Lisovskiy Stanislav
>
> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160
> Espoo
> ------------------------------------------------------------------------
> *From:* Patchwork <patchwork@emeril.freedesktop.org>
> *Sent:* Friday, January 17, 2020 12:32:34 PM
> *To:* Lisovskiy, Stanislav
> *Cc:* intel-gfx@lists.freedesktop.org
> *Subject:* ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and
> TGL (rev17)
>
> == Series Details ==
>
> Series: Enable second DBuf slice for ICL and TGL (rev17)
> URL : https://patchwork.freedesktop.org/series/70059/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7758 -> Patchwork_16145
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_16145 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_16145, 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_16145/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in
> Patchwork_16145:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live_hangcheck:
> - fi-hsw-peppy: [PASS][1] -> [DMESG-FAIL][2]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-hsw-peppy/igt@i915_selftest@live_hangcheck.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-hsw-peppy/igt@i915_selftest@live_hangcheck.html
>
> * igt@runner@aborted:
> - fi-hsw-peppy: NOTRUN -> [FAIL][3]
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-hsw-peppy/igt@runner@aborted.html
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_16145 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@i915_selftest@live_gem_contexts:
> - fi-cfl-guc: [PASS][4] -> [INCOMPLETE][5] ([CI#80] /
> [fdo#106070] / [i915#424])
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-cfl-guc/igt@i915_selftest@live_gem_contexts.html
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-cfl-guc/igt@i915_selftest@live_gem_contexts.html
>
>
> #### Possible fixes ####
>
> * igt@gem_exec_create@basic:
> - fi-icl-dsi: [DMESG-WARN][6] ([i915#109]) -> [PASS][7]
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-icl-dsi/igt@gem_exec_create@basic.html
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-icl-dsi/igt@gem_exec_create@basic.html
>
> * igt@i915_pm_rpm@module-reload:
> - fi-skl-6770hq: [FAIL][8] ([i915#178]) -> [PASS][9]
> [8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
> [9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
>
> * igt@kms_chamelium@hdmi-hpd-fast:
> - fi-kbl-7500u: [FAIL][10] ([fdo#111096] / [i915#323]) ->
> [PASS][11]
> [10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
> [11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/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).
>
> [CI#80]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/80
> [fdo#106070]: https://bugs.freedesktop.org/show_bug.cgi?id=106070
> [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
> [i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
> [i915#178]: https://gitlab.freedesktop.org/drm/intel/issues/178
> [i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
> [i915#424]: https://gitlab.freedesktop.org/drm/intel/issues/424
> [i915#937]: https://gitlab.freedesktop.org/drm/intel/issues/937
>
>
> Participating hosts (47 -> 42)
> ------------------------------
>
> Additional (2): fi-kbl-soraka fi-byt-j1900
> Missing (7): fi-ilk-m540 fi-cml-s fi-hsw-4200u fi-byt-squawks
> fi-bsw-cyan fi-blb-e6850 fi-skl-6600u
>
>
> Build changes
> -------------
>
> * CI: CI-20190529 -> None
> * Linux: CI_DRM_7758 -> Patchwork_16145
>
> CI-20190529: 20190529
> CI_DRM_7758: d19270ce1f367fbfc1ff3b539bcb50e11ded181f @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5371: 1b2816124ec3dbd53b81725d39292f45d41d895b @
> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_16145: 2d8f148776282b98d6a2c465827bb866b827a0e7 @
> git://anongit.freedesktop.org/gfx-ci/linux
>
>
> == Kernel 32bit build ==
>
> Warning: Kernel 32bit buildtest failed:
> https://intel-gfx-ci.01.org/Patchwork_16145/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 122 modules
> ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
> scripts/Makefile.modpost:93: recipe for target '__modpost' failed
> make[1]: *** [__modpost] Error 1
> Makefile:1282: recipe for target 'modules' failed
> make: *** [modules] Error 2
>
>
> == Linux commits ==
>
> 2d8f14877628 drm/i915: Correctly map DBUF slices to pipes
> e059c200fd76 drm/i915: Manipulate DBuf slices properly
> a2c1ac67dd39 drm/i915: Introduce parameterized DBUF_CTL
> 8ff9e4936cec drm/i915: Move dbuf slice update to proper place
> ad232477876a drm/i915: Remove skl_ddl_allocation struct
>
> == Logs ==
>
> For more details see:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/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-17 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 9:50 [Intel-gfx] [PATCH v13 0/5] Enable second DBuf slice for ICL and TGL Stanislav Lisovskiy
2020-01-17 9:50 ` [Intel-gfx] [PATCH v13 1/5] drm/i915: Remove skl_ddl_allocation struct Stanislav Lisovskiy
2020-01-17 9:50 ` [Intel-gfx] [PATCH v13 2/5] drm/i915: Move dbuf slice update to proper place Stanislav Lisovskiy
2020-01-17 9:50 ` [Intel-gfx] [PATCH v13 3/5] drm/i915: Introduce parameterized DBUF_CTL Stanislav Lisovskiy
2020-01-17 18:41 ` Ville Syrjälä
2020-01-17 9:50 ` [Intel-gfx] [PATCH v13 4/5] drm/i915: Manipulate DBuf slices properly Stanislav Lisovskiy
2020-01-17 18:46 ` Ville Syrjälä
2020-01-17 19:06 ` Matt Roper
2020-01-20 8:36 ` Lisovskiy, Stanislav
2020-01-17 9:50 ` [Intel-gfx] [PATCH v13 5/5] drm/i915: Correctly map DBUF slices to pipes Stanislav Lisovskiy
2020-01-17 19:07 ` Ville Syrjälä
2020-01-17 10:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and TGL (rev17) Patchwork
2020-01-17 10:43 ` Lisovskiy, Stanislav
2020-01-17 13:08 ` Peres, Martin [this message]
2020-01-17 10:32 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-17 13:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-17 13:25 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-20 11:48 ` [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=c2af4c9bb4cb462584e58da3aa3d41e3@intel.com \
--to=martin.peres@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=stanislav.lisovskiy@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