From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: nuke remaining legacy reg helpers (I915_READ/WRITE etc.) (rev2)
Date: Sat, 14 Nov 2020 15:38:05 -0500 [thread overview]
Message-ID: <20201114203805.GB1284090@intel.com> (raw)
In-Reply-To: <160530397761.20635.7847451500690336684@emeril.freedesktop.org>
On Fri, Nov 13, 2020 at 09:46:17PM -0000, Patchwork wrote:
> Patch Details
>
> Series: drm/i915: nuke remaining legacy reg helpers (I915_READ/WRITE etc.)
> (rev2)
> URL: https://patchwork.freedesktop.org/series/83762/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18899/index.html
>
> CI Bug Log - changes from CI_DRM_9326 -> Patchwork_18899
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_18899 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_18899, 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_18899/
> index.html
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in Patchwork_18899:
>
> IGT changes
>
> Possible regressions
>
> • igt@i915_selftest@live@execlists:
> □ fi-cml-s: PASS -> INCOMPLETE
false positive? I couldn't find anything in this series that could justify this.
But maybe my eyes are getting tricked?!
Did you use sed or coccinelle?
>
> New tests
>
> New tests have been introduced between CI_DRM_9326 and Patchwork_18899:
>
> New CI tests (1)
>
> • boot:
> □ Statuses : 40 pass(s)
> □ Exec time: [0.0] s
>
> Known issues
>
> Here are the changes found in Patchwork_18899 that come from known issues:
>
> IGT changes
>
> Issues hit
>
> • igt@gem_linear_blits@basic:
>
> □ fi-tgl-y: PASS -> DMESG-WARN (i915#402)
> • igt@i915_module_load@reload:
>
> □ fi-icl-u2: PASS -> DMESG-WARN (i915#1982)
>
> □ fi-bxt-dsi: PASS -> DMESG-WARN (i915#1635 / i915#1982)
>
> • igt@i915_pm_rpm@module-reload:
>
> □ fi-byt-j1900: PASS -> DMESG-WARN (i915#1982)
>
> □ fi-kbl-7500u: PASS -> DMESG-WARN (i915#203)
>
> • igt@kms_busy@basic@flip:
>
> □ fi-kbl-soraka: PASS -> DMESG-WARN (i915#1982)
>
> Possible fixes
>
> • igt@gem_huc_copy@huc-copy:
>
> □ fi-tgl-y: DMESG-WARN (i915#402) -> PASS +1 similar issue
> • igt@kms_chamelium@dp-crc-fast:
>
> □ fi-cml-u2: FAIL (i915#1161 / i915#262) -> PASS
> • igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
>
> □ {fi-kbl-7560u}: DMESG-WARN (i915#1982) -> PASS
> • igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
>
> □ fi-icl-u2: DMESG-WARN (i915#1982) -> PASS
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> Participating hosts (46 -> 40)
>
> Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bsw-kefka
> fi-bdw-samus
>
> Build changes
>
> • Linux: CI_DRM_9326 -> Patchwork_18899
>
> CI-20190529: 20190529
> CI_DRM_9326: 3048c2a1dcf02422e89930148ffad9e91d690499 @ git://
> anongit.freedesktop.org/gfx-ci/linux
> IGT_5850: 9748a4a0f93d108955d374a866e60cb962da9b5d @ git://
> anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_18899: 514c0c489a721a0e6a3bf49276ac22f7d00fa528 @ git://
> anongit.freedesktop.org/gfx-ci/linux
>
> == Linux commits ==
>
> 514c0c489a72 drm/i915: remove last traces of I915_READ(), I915_WRITE() and
> POSTING_READ()
> 2214a7d222dd drm/i915/irq: replace I915_READ()/WRITE() with intel_uncore_read()
> /write()
> f8e17dd5562f drm/i915/pm: replace I915_READ()/WRITE() with intel_uncore_read()/
> write()
> 6bc38ebd534e drm/i915/suspend: replace I915_READ()/WRITE() with intel_de_read()
> /write()
> 12f65d9478f7 drm/i915/debugfs: replace I915_READ() with intel_uncore_read()
> 2cc1e5948842 drm/i915/debugfs: remove the i915_cache_sharing debugfs file
> 5f3651b6bf1b drm/i915/cdclk: prefer intel_de_write() over I915_WRITE()
> 162d680cbbab drm/i915: remove last traces of I915_READ_FW() and I915_WRITE_FW()
> 60a0c55dfe27 drm/i915/debugfs: remove RPS autotuning details from
> i915_rps_boost_info
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-11-14 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 13:24 [Intel-gfx] [PATCH v2 0/9] drm/i915: nuke remaining legacy reg helpers (I915_READ/WRITE etc.) Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 1/9] drm/i915/debugfs: remove RPS autotuning details from i915_rps_boost_info Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 2/9] drm/i915: remove last traces of I915_READ_FW() and I915_WRITE_FW() Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 3/9] drm/i915/cdclk: prefer intel_de_write() over I915_WRITE() Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 4/9] drm/i915/debugfs: remove the i915_cache_sharing debugfs file Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 5/9] drm/i915/debugfs: replace I915_READ() with intel_uncore_read() Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 6/9] drm/i915/suspend: replace I915_READ()/WRITE() with intel_de_read()/write() Jani Nikula
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 7/9] drm/i915/pm: replace I915_READ()/WRITE() with intel_uncore_read()/write() Jani Nikula
2020-11-14 20:50 ` Rodrigo Vivi
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 8/9] drm/i915/irq: " Jani Nikula
2020-11-14 20:41 ` Rodrigo Vivi
2020-11-13 13:24 ` [Intel-gfx] [PATCH v2 9/9] drm/i915: remove last traces of I915_READ(), I915_WRITE() and POSTING_READ() Jani Nikula
2020-11-13 21:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: nuke remaining legacy reg helpers (I915_READ/WRITE etc.) (rev2) Patchwork
2020-11-13 21:46 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-11-14 20:38 ` Rodrigo Vivi [this message]
2020-11-18 11:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: nuke remaining legacy reg helpers (I915_READ/WRITE etc.) (rev3) Patchwork
2020-11-18 12:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-18 18:10 ` [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=20201114203805.GB1284090@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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