From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks
Date: Fri, 5 Nov 2021 17:18:47 +0000 [thread overview]
Message-ID: <ecfe7caafb8a474186fadc8e1c786558@intel.com> (raw)
In-Reply-To: <99e04830-a92b-11bb-ece9-a5c6065b802b@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
Filed below issue and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/4445
igt@i915_selftest@live@migrate - dmesg-warn - WARNING: held lock freed!
Lakshmi.
From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Sent: Thursday, November 4, 2021 11:40 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks
On 11/5/21 00:01, Patchwork wrote:
Patch Details
Series:
series starting with [1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks
URL:
https://patchwork.freedesktop.org/series/96593/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21521/index.html
CI Bug Log - changes from CI_DRM_10841 -> Patchwork_21521
Summary
FAILURE
Serious unknown changes coming with Patchwork_21521 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21521, 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_21521/index.html
Participating hosts (38 -> 35)
Additional (2): fi-tgl-1115g4 fi-tgl-u2
Missing (5): bat-dg1-6 bat-dg1-5 fi-bsw-cyan fi-icl-u2 bat-adlp-4
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_21521:
IGT changes
Possible regressions
* igt@i915_selftest@live@migrate:
* fi-bsw-nick: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10841/fi-bsw-nick/igt@i915_selftest@live@migrate.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21521/fi-bsw-nick/igt@i915_selftest@live@migrate.html>
Lakshmi, this failure is unrelated.
[-- Attachment #2: Type: text/html, Size: 13925 bytes --]
next prev parent reply other threads:[~2021-11-05 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 21:58 [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks Thomas Hellström
2021-11-04 21:58 ` [Intel-gfx] [PATCH 2/2] HAX: drm/i915/selftest: Temporarily avoid tainting the kernel on engine reset failure Thomas Hellström
2021-11-04 22:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks Patchwork
2021-11-04 23:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-05 6:40 ` Thomas Hellström
2021-11-05 17:18 ` Vudum, Lakshminarayana [this message]
2021-11-05 16:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-05 18:40 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=ecfe7caafb8a474186fadc8e1c786558@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.