From: "Navare, Manasi D" <manasi.d.navare@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Syrjala, Ville" <ville.syrjala@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display/vrr: Reset VRR capable property on a long hpd (rev4)
Date: Thu, 24 Feb 2022 19:00:24 +0000 [thread overview]
Message-ID: <ad720c43e70648409a06071c5c986357@intel.com> (raw)
In-Reply-To: <164572828646.32675.16216405999006999887@emeril.freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 4742 bytes --]
Hi,
I fixed the regression in this patch and resent it, it still has BAT failures, I wanted to understand if it failed to boot some of the machines again or the errors flagged here are the known errors.
Regards
Manasi
From: Patchwork <patchwork@emeril.freedesktop.org>
Sent: Thursday, February 24, 2022 10:45 AM
To: Navare, Manasi D <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915/display/vrr: Reset VRR capable property on a long hpd (rev4)
Patch Details
Series:
drm/i915/display/vrr: Reset VRR capable property on a long hpd (rev4)
URL:
https://patchwork.freedesktop.org/series/98801/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/index.html
CI Bug Log - changes from CI_DRM_11279 -> Patchwork_22394
Summary
FAILURE
Serious unknown changes coming with Patchwork_22394 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22394, 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_22394/index.html
Participating hosts (43 -> 32)
Missing (11): fi-kbl-soraka fi-cml-u2 fi-bsw-cyan fi-ilk-650 fi-apl-guc fi-kbl-7500u fi-kbl-x1275 fi-cfl-8109u fi-bsw-kefka fi-bdw-samus fi-skl-6600u
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_22394:
IGT changes
Possible regressions
* igt@gem_exec_suspend@basic-s0@smem:
* fi-skl-6700k2: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/fi-skl-6700k2/igt@gem_exec_suspend@basic-s0@smem.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/fi-skl-6700k2/igt@gem_exec_suspend@basic-s0@smem.html>
Known issues
Here are the changes found in Patchwork_22394 that come from known issues:
IGT changes
Issues hit
* igt@amdgpu/amd_basic@cs-multi-fence:
* fi-blb-e6850: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/fi-blb-e6850/igt@amdgpu/amd_basic@cs-multi-fence.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +17 similar issues
* igt@runner@aborted:
* fi-skl-6700k2: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/fi-skl-6700k2/igt@runner@aborted.html> (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)
Possible fixes
* igt@i915_selftest@live@hangcheck:
* bat-dg1-6: DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/bat-dg1-6/igt@i915_selftest@live@hangcheck.html> (i915#4494<https://gitlab.freedesktop.org/drm/intel/issues/4494> / i915#4957<https://gitlab.freedesktop.org/drm/intel/issues/4957>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/bat-dg1-6/igt@i915_selftest@live@hangcheck.html>
* igt@i915_selftest@live@requests:
* fi-blb-e6850: DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/fi-blb-e6850/igt@i915_selftest@live@requests.html> (i915#5026<https://gitlab.freedesktop.org/drm/intel/issues/5026>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/fi-blb-e6850/igt@i915_selftest@live@requests.html>
* igt@i915_selftest@live@workarounds:
* {bat-adlp-6}: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/bat-adlp-6/igt@i915_selftest@live@workarounds.html> (i915#5068<https://gitlab.freedesktop.org/drm/intel/issues/5068>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/bat-adlp-6/igt@i915_selftest@live@workarounds.html>
* igt@kms_flip@basic-flip-vs-modeset@a-edp1:
* {bat-adlp-6}: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/bat-adlp-6/igt@kms_flip@basic-flip-vs-modeset@a-edp1.html> (i915#3576<https://gitlab.freedesktop.org/drm/intel/issues/3576>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22394/bat-adlp-6/igt@kms_flip@basic-flip-vs-modeset@a-edp1.html>
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
Build changes
* Linux: CI_DRM_11279 -> Patchwork_22394
CI-20190529: 20190529
CI_DRM_11279: 5301cc85b3cc0eaa37405a117c77a35db7f4a76d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6356: b403d8e73c6888561eaec97835688313b0763ce9 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22394: 244f36e5190c176be3ec2fbc9fc18c63b8383621 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
244f36e5190c drm/i915/display/vrr: Reset VRR capable property on a long hpd
[-- Attachment #2: Type: text/html, Size: 20482 bytes --]
next prev parent reply other threads:[~2022-02-24 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 22:14 [Intel-gfx] [PATCH v5] drm/i915/display/vrr: Reset VRR capable property on a long hpd Manasi Navare
2022-02-24 18:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display/vrr: Reset VRR capable property on a long hpd (rev4) Patchwork
2022-02-24 18:44 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-24 19:00 ` Navare, Manasi D [this message]
2022-02-24 19:56 ` Saarinen, Jani
2022-02-25 8:36 ` Sarvela, Tomi P
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=ad720c43e70648409a06071c5c986357@intel.com \
--to=manasi.d.navare@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=tomi.p.sarvela@intel.com \
--cc=ville.syrjala@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