All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Robert Beckett" <bob.beckett@collabora.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: ttm for stolen region (rev2)
Date: Tue, 12 Apr 2022 15:48:56 -0000	[thread overview]
Message-ID: <164977853618.18365.16247663461304207772@emeril.freedesktop.org> (raw)
In-Reply-To: <20220412151838.1298956-1-bob.beckett@collabora.com>

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

== Series Details ==

Series: drm/i915: ttm for stolen region (rev2)
URL   : https://patchwork.freedesktop.org/series/102540/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11489 -> Patchwork_102540v2
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with Patchwork_102540v2 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_102540v2, 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_102540v2/index.html

Participating hosts (46 -> 47)
------------------------------

  Additional (3): fi-icl-u2 bat-adls-5 fi-pnv-d510 
  Missing    (2): fi-bsw-cyan fi-bdw-samus 

Possible new issues
-------------------

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

### IGT changes ###

#### Possible regressions ####

  * igt@runner@aborted:
    - fi-cfl-8700k:       NOTRUN -> [FAIL][1]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-cfl-8700k/igt@runner@aborted.html
    - fi-hsw-g3258:       NOTRUN -> [FAIL][2]
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-hsw-g3258/igt@runner@aborted.html
    - fi-bxt-dsi:         NOTRUN -> [FAIL][3]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-bxt-dsi/igt@runner@aborted.html
    - fi-adl-ddr5:        NOTRUN -> [FAIL][4]
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-adl-ddr5/igt@runner@aborted.html
    - fi-cfl-guc:         NOTRUN -> [FAIL][5]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-cfl-guc/igt@runner@aborted.html
    - fi-glk-j4005:       NOTRUN -> [FAIL][6]
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-glk-j4005/igt@runner@aborted.html

  
#### Warnings ####

  * igt@runner@aborted:
    - fi-apl-guc:         [FAIL][7] ([i915#4312]) -> [FAIL][8]
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11489/fi-apl-guc/igt@runner@aborted.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-apl-guc/igt@runner@aborted.html
    - fi-bdw-5557u:       [FAIL][9] ([i915#4312]) -> [FAIL][10]
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11489/fi-bdw-5557u/igt@runner@aborted.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-bdw-5557u/igt@runner@aborted.html

  
#### Suppressed ####

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@runner@aborted:
    - {fi-jsl-1}:         NOTRUN -> [FAIL][11]
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-jsl-1/igt@runner@aborted.html
    - {fi-ehl-2}:         NOTRUN -> [FAIL][12]
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-ehl-2/igt@runner@aborted.html

  
Known issues
------------

  Here are the changes found in Patchwork_102540v2 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
    - fi-pnv-d510:        NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#5341])
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-pnv-d510/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c.html

  * igt@prime_vgem@basic-userptr:
    - fi-pnv-d510:        NOTRUN -> [SKIP][14] ([fdo#109271]) +39 similar issues
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-pnv-d510/igt@prime_vgem@basic-userptr.html

  * igt@runner@aborted:
    - fi-rkl-11600:       NOTRUN -> [FAIL][15] ([i915#5602])
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-rkl-11600/igt@runner@aborted.html
    - fi-bsw-kefka:       NOTRUN -> [FAIL][16] ([i915#3690])
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-bsw-kefka/igt@runner@aborted.html
    - fi-cfl-8109u:       NOTRUN -> [FAIL][17] ([i915#5602])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-cfl-8109u/igt@runner@aborted.html
    - fi-icl-u2:          NOTRUN -> [FAIL][18] ([i915#3690])
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-icl-u2/igt@runner@aborted.html
    - fi-bsw-nick:        NOTRUN -> [FAIL][19] ([i915#3690])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-bsw-nick/igt@runner@aborted.html
    - fi-kbl-soraka:      NOTRUN -> [FAIL][20] ([i915#5602])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-kbl-soraka/igt@runner@aborted.html
    - fi-kbl-7500u:       NOTRUN -> [FAIL][21] ([i915#5602])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-kbl-7500u/igt@runner@aborted.html
    - fi-kbl-guc:         NOTRUN -> [FAIL][22] ([i915#5602])
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-kbl-guc/igt@runner@aborted.html
    - fi-rkl-guc:         NOTRUN -> [FAIL][23] ([i915#5602])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-rkl-guc/igt@runner@aborted.html
    - fi-tgl-1115g4:      NOTRUN -> [FAIL][24] ([i915#3690])
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-tgl-1115g4/igt@runner@aborted.html
    - fi-kbl-7567u:       NOTRUN -> [FAIL][25] ([i915#5602])
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-kbl-7567u/igt@runner@aborted.html
    - fi-skl-guc:         NOTRUN -> [FAIL][26] ([i915#5602])
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-skl-guc/igt@runner@aborted.html
    - fi-skl-6700k2:      NOTRUN -> [FAIL][27] ([i915#5602])
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-skl-6700k2/igt@runner@aborted.html
    - fi-bsw-n3050:       NOTRUN -> [FAIL][28] ([i915#3690])
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-bsw-n3050/igt@runner@aborted.html
    - fi-tgl-u2:          NOTRUN -> [FAIL][29] ([i915#3690])
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/fi-tgl-u2/igt@runner@aborted.html

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [i915#3690]: https://gitlab.freedesktop.org/drm/intel/issues/3690
  [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
  [i915#4897]: https://gitlab.freedesktop.org/drm/intel/issues/4897
  [i915#5341]: https://gitlab.freedesktop.org/drm/intel/issues/5341
  [i915#5602]: https://gitlab.freedesktop.org/drm/intel/issues/5602


Build changes
-------------

  * Linux: CI_DRM_11489 -> Patchwork_102540v2

  CI-20190529: 20190529
  CI_DRM_11489: 0e90e7484c1e92567d0c7a0c6b4cfcbc1bbd0015 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_6420: a3885810ccc0ce9e6552a20c910a0a322eca466c @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  Patchwork_102540v2: 102540v2 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

6dc5d68ada66 drm/i915: stolen memory use ttm backend
5a741abbe505 drm/i915: ttm backend dont provide mmap_offset for kernel buffers
441819a03ff4 drm/i915: ttm move/clear logic fix
1ae24ce27e84 drm/i915: sanitize mem_flags for stolen buffers
f4694b2f65f0 drm/i915: instantiate ttm ranger manager for stolen memory

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102540v2/index.html

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

      parent reply	other threads:[~2022-04-12 15:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 15:18 [PATCH v2 0/5] drm/i915: ttm for stolen region Robert Beckett
2022-04-12 15:18 ` [Intel-gfx] " Robert Beckett
2022-04-12 15:18 ` [PATCH v2 1/5] drm/i915: instantiate ttm ranger manager for stolen memory Robert Beckett
2022-04-12 15:18   ` [Intel-gfx] " Robert Beckett
2022-04-12 15:18   ` Robert Beckett
2022-04-12 15:18 ` [PATCH v2 2/5] drm/i915: sanitize mem_flags for stolen buffers Robert Beckett
2022-04-12 15:18   ` [Intel-gfx] " Robert Beckett
2022-04-12 15:18   ` Robert Beckett
2022-04-14 13:58   ` Thomas Hellström
2022-04-14 13:58     ` [Intel-gfx] " Thomas Hellström
2022-04-12 15:18 ` [PATCH v2 3/5] drm/i915: ttm move/clear logic fix Robert Beckett
2022-04-12 15:18   ` [Intel-gfx] " Robert Beckett
2022-04-12 15:18   ` Robert Beckett
2022-04-14 14:00   ` Thomas Hellström
2022-04-14 14:00     ` [Intel-gfx] " Thomas Hellström
2022-04-12 15:18 ` [PATCH v2 4/5] drm/i915: ttm backend dont provide mmap_offset for kernel buffers Robert Beckett
2022-04-12 15:18   ` [Intel-gfx] " Robert Beckett
2022-04-12 15:18   ` Robert Beckett
2022-04-14 14:05   ` Thomas Hellström
2022-04-14 14:05     ` [Intel-gfx] " Thomas Hellström
2022-04-14 16:13     ` Robert Beckett
2022-04-14 16:13       ` [Intel-gfx] " Robert Beckett
2022-04-27 10:14       ` Thomas Hellström
2022-04-27 10:14         ` [Intel-gfx] " Thomas Hellström
2022-04-12 15:18 ` [PATCH v2 5/5] drm/i915: stolen memory use ttm backend Robert Beckett
2022-04-12 15:18   ` [Intel-gfx] " Robert Beckett
2022-04-12 15:18   ` Robert Beckett
2022-04-12 15:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: ttm for stolen region (rev2) Patchwork
2022-04-12 15:48 ` Patchwork [this message]

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=164977853618.18365.16247663461304207772@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=bob.beckett@collabora.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.