Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/pf: Drop 2GiB limit of fair LMEM allocation
Date: Fri, 22 Nov 2024 17:29:21 +0100	[thread overview]
Message-ID: <ff3175ed-9522-4abb-882a-dc45f9d5edce@intel.com> (raw)
In-Reply-To: <173225031401.1553344.11278327773482720772@b555e5b46a47>



On 22.11.2024 05:38, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/pf: Drop 2GiB limit of fair LMEM allocation
> URL   : https://patchwork.freedesktop.org/series/141673/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2257-e46649e7764a9f6868ccbcba7b8b23b413303380_full -> xe-pw-141673v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-141673v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-141673v1_full, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   
> 
> Participating hosts (4 -> 4)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-141673v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####

all unrelated

> 
>   * igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy:
>     - shard-bmg:          NOTRUN -> [DMESG-WARN][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-bmg-4/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html
> 
>   * igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-dp2:
>     - shard-bmg:          NOTRUN -> [FAIL][2]
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-bmg-1/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-dp2.html
> 
>   * igt@kms_flip@flip-vs-suspend-interruptible@b-dp4:
>     - shard-dg2-set2:     NOTRUN -> [DMESG-FAIL][3]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-dg2-436/igt@kms_flip@flip-vs-suspend-interruptible@b-dp4.html
> 
>   * igt@kms_pm_backlight@fade-with-dpms:
>     - shard-lnl:          [PASS][4] -> [DMESG-WARN][5] +1 other test dmesg-warn
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2257-e46649e7764a9f6868ccbcba7b8b23b413303380/shard-lnl-7/igt@kms_pm_backlight@fade-with-dpms.html
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-lnl-4/igt@kms_pm_backlight@fade-with-dpms.html
> 
>   * igt@xe_drm_fdinfo@utilization-others-full-load:
>     - shard-lnl:          [PASS][6] -> [FAIL][7] +1 other test fail
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2257-e46649e7764a9f6868ccbcba7b8b23b413303380/shard-lnl-3/igt@xe_drm_fdinfo@utilization-others-full-load.html
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-lnl-2/igt@xe_drm_fdinfo@utilization-others-full-load.html
> 
>   * igt@xe_fault_injection@inject-fault-probe-function-wait_for_lmem_ready:
>     - shard-adlp:         [PASS][8] -> [DMESG-WARN][9]
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2257-e46649e7764a9f6868ccbcba7b8b23b413303380/shard-adlp-3/igt@xe_fault_injection@inject-fault-probe-function-wait_for_lmem_ready.html
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-adlp-1/igt@xe_fault_injection@inject-fault-probe-function-wait_for_lmem_ready.html
> 
>   * igt@xe_fault_injection@vm-bind-fail-xe_pt_update_ops_prepare:
>     - shard-lnl:          NOTRUN -> [FAIL][10]
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-lnl-4/igt@xe_fault_injection@vm-bind-fail-xe_pt_update_ops_prepare.html
> 
>   * igt@xe_oa@invalid-map-oa-buffer:
>     - shard-adlp:         NOTRUN -> [SKIP][11] +2 other tests skip
>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141673v1/shard-adlp-2/igt@xe_oa@invalid-map-oa-buffer.html
> 
>   

      reply	other threads:[~2024-11-22 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 17:57 [PATCH] drm/xe/pf: Drop 2GiB limit of fair LMEM allocation Michal Wajdeczko
2024-11-21 18:30 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-21 18:30 ` ✓ CI.checkpatch: " Patchwork
2024-11-21 18:32 ` ✓ CI.KUnit: " Patchwork
2024-11-21 18:50 ` ✓ CI.Build: " Patchwork
2024-11-21 18:52 ` ✓ CI.Hooks: " Patchwork
2024-11-21 18:54 ` ✓ CI.checksparse: " Patchwork
2024-11-21 19:17 ` ✓ Xe.CI.BAT: " Patchwork
2024-11-22  3:24 ` [PATCH] " K V P, Satyanarayana
2024-11-22  4:38 ` ✗ Xe.CI.Full: failure for " Patchwork
2024-11-22 16:29   ` Michal Wajdeczko [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=ff3175ed-9522-4abb-882a-dc45f9d5edce@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox