From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ CI.BAT: failure for drm/xe: Invalidate media_gt TLBs in PT code (rev2)
Date: Tue, 20 Aug 2024 20:09:45 +0000 [thread overview]
Message-ID: <ZsT4CYbG3eSGnaT8@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <172417800506.700411.7337988742670153679@2413ebb6fbb6>
On Tue, Aug 20, 2024 at 06:20:05PM +0000, Patchwork wrote:
> Patch Details
>
> Series: drm/xe: Invalidate media_gt TLBs in PT code (rev2)
> URL: [1]https://patchwork.freedesktop.org/series/137419/
> State: failure
> Details:
> [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-137419v2/index.html
>
> CI Bug Log - changes from xe-1800-aadc820a10ab50bd57179c0feb238bedde6a9d3b_BAT
> -> xe-pw-137419v2_BAT
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with xe-pw-137419v2_BAT absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-137419v2_BAT, 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 (9 -> 9)
>
> No changes in participating hosts
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> xe-pw-137419v2_BAT:
>
> IGT changes
>
> Possible regressions
>
> * igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-invalidate:
> + bat-lnl-1: [3]PASS -> [4]DMESG-WARN
While this failure is related to TLB timeouts, honestly don't think it
is related. The timeout is on the primary GT, tried to recreate this on
a LNL in RIL without any luck (i.e. this test works). I've seen several
TLB timeouts in the past on LNL is CI too, we likely have another issue
going on which needs to be debugged.
Matt
>
> Known issues
>
> Here are the changes found in xe-pw-137419v2_BAT that come from known
> issues:
>
> IGT changes
>
> Warnings
>
> * igt@kms_frontbuffer_tracking@basic:
> + bat-adlp-7: [5]DMESG-WARN ([6]Intel XE#324) -> [7]DMESG-FAIL
> ([8]Intel XE#324)
>
> Build changes
>
> * Linux: xe-1800-aadc820a10ab50bd57179c0feb238bedde6a9d3b ->
> xe-pw-137419v2
>
> IGT_7979: 403645635240cf6b72455731d0f086278b05e456 @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-1800-aadc820a10ab50bd57179c0feb238bedde6a9d3b:
> aadc820a10ab50bd57179c0feb238bedde6a9d3b
> xe-pw-137419v2: 137419v2
>
> References
>
> 1. https://patchwork.freedesktop.org/series/137419/
> 2. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-137419v2/index.html
> 3. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1800-aadc820a10ab50bd57179c0feb238bedde6a9d3b/bat-lnl-1/igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-invalidate.html
> 4. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-137419v2/bat-lnl-1/igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-invalidate.html
> 5. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1800-aadc820a10ab50bd57179c0feb238bedde6a9d3b/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
> 6. https://gitlab.freedesktop.org/drm/xe/kernel/issues/324
> 7. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-137419v2/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
> 8. https://gitlab.freedesktop.org/drm/xe/kernel/issues/324
next prev parent reply other threads:[~2024-08-20 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 16:16 [PATCH v2] drm/xe: Invalidate media_gt TLBs in PT code Matthew Brost
2024-08-20 17:41 ` ✓ CI.Patch_applied: success for drm/xe: Invalidate media_gt TLBs in PT code (rev2) Patchwork
2024-08-20 17:41 ` ✓ CI.checkpatch: " Patchwork
2024-08-20 17:43 ` ✓ CI.KUnit: " Patchwork
2024-08-20 17:55 ` ✓ CI.Build: " Patchwork
2024-08-20 17:57 ` ✓ CI.Hooks: " Patchwork
2024-08-20 17:58 ` ✓ CI.checksparse: " Patchwork
2024-08-20 18:20 ` ✗ CI.BAT: failure " Patchwork
2024-08-20 20:09 ` Matthew Brost [this message]
2024-08-20 22:26 ` ✗ CI.FULL: " Patchwork
2024-08-21 3:33 ` [PATCH v2] drm/xe: Invalidate media_gt TLBs in PT code Ghimiray, Himal Prasad
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=ZsT4CYbG3eSGnaT8@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@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