Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 drm/i915/ttm: Async migration (rev7)
Date: Mon, 22 Nov 2021 18:01:46 +0000	[thread overview]
Message-ID: <ab57256075dd4dacbba4e189c7fc7614@intel.com> (raw)
In-Reply-To: <591c2917-43a0-0eb4-e923-b50096aa30e6@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

We have https://gitlab.freedesktop.org/drm/intel/-/issues/4547 for the regression on SKL.
Few tests - fail - This test was killed due to a kernel taint, INFO: task kworker/.* blocked for more than 30 seconds.

Thanks,
Lakshmi.

From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Sent: Monday, November 22, 2021 6:54 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/ttm: Async migration (rev7)



On 11/22/21 15:02, Patchwork wrote:
Patch Details
Series:

drm/i915/ttm: Async migration (rev7)

URL:

https://patchwork.freedesktop.org/series/96798/

State:

failure

Details:

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21651/index.html

CI Bug Log - changes from CI_DRM_10913 -> Patchwork_21651
Summary

FAILURE

Serious unknown changes coming with Patchwork_21651 absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21651, 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_21651/index.html

Participating hosts (43 -> 34)

Missing (9): bat-dg1-6 fi-tgl-u2 bat-dg1-5 fi-icl-u2 fi-bsw-cyan bat-adlp-6 bat-adlp-4 bat-jsl-2 bat-jsl-1

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21651:

IGT changes
Possible regressions

  *   igt@gem_exec_suspend@basic-s3:

     *   fi-skl-6600u: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10913/fi-skl-6600u/igt@gem_exec_suspend@basic-s3.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21651/fi-skl-6600u/igt@gem_exec_suspend@basic-s3.html>


Lakshmi,

This failure is unrelated, and occurs on the same machine with a more or less identical signature on CI_DRM_10901

Thanks,
Thomas

[-- Attachment #2: Type: text/html, Size: 14058 bytes --]

  reply	other threads:[~2021-11-22 18:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  8:22 [Intel-gfx] [PATCH v6 0/6] drm/i915/ttm: Async migration Thomas Hellström
2021-11-22  8:22 ` [Intel-gfx] [PATCH v6 1/6] drm/i915: Add support for moving fence waiting Thomas Hellström
2021-11-22 15:54   ` kernel test robot
2021-11-22 19:39   ` kernel test robot
2021-11-22  8:22 ` [Intel-gfx] [PATCH v6 2/6] drm/i915/ttm: Move the i915_gem_obj_copy_ttm() function Thomas Hellström
2021-11-22  8:22 ` [Intel-gfx] [PATCH v6 3/6] drm/i915/ttm: Drop region reference counting Thomas Hellström
2021-11-22  8:22 ` [Intel-gfx] [PATCH v6 4/6] drm/i915/ttm: Correctly handle waiting for gpu when shrinking Thomas Hellström
2021-11-22  8:22 ` [Intel-gfx] [PATCH v6 5/6] drm/i915/ttm: Implement asynchronous TTM moves Thomas Hellström
2021-11-22  8:22 ` [Intel-gfx] [PATCH v6 6/6] drm/i915/ttm: Update i915_gem_obj_copy_ttm() to be asynchronous Thomas Hellström
2021-11-22 13:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev7) Patchwork
2021-11-22 14:02 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-22 14:54   ` Thomas Hellström
2021-11-22 18:01     ` Vudum, Lakshminarayana [this message]
2021-11-22 16:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-22 20:35 ` [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=ab57256075dd4dacbba4e189c7fc7614@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox