From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Jonathan Cavitt <jonathan.cavitt@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Subject: [PATCH dii-client v6 0/4] drm/i915: Define and use GuC and CTB TLB invalidation routines
Date: Thu, 5 Oct 2023 15:03:31 +0200 [thread overview]
Message-ID: <ZR60I2gMgjdlGaXX@ashyti-mobl2.lan> (raw)
In-Reply-To: <ZR6zVOy3GbvbuPIX@ashyti-mobl2.lan>
Hi,
> > CI changes
> >
> > Possible regressions
> >
> > • boot:
> > □ bat-dg1-5: PASS -> FAIL
> >
> > IGT changes
> >
> > Possible regressions
> >
> > • igt@kms_addfb_basic@addfb25-framebuffer-vs-set-tiling:
> >
> > □ bat-adlm-1: PASS -> INCOMPLETE
> > • igt@kms_busy@basic@flip:
> >
> > □ bat-adlp-11: PASS -> ABORT
> >
> > □ bat-adlp-6: PASS -> INCOMPLETE
> >
> > • igt@kms_busy@basic@modeset:
> >
> > □ bat-adlp-11: PASS -> DMESG-WARN
> > • igt@kms_force_connector_basic@force-connector-state:
> >
> > □ bat-rpls-1: PASS -> INCOMPLETE
>
> Although these failures appear very consistently, they don't look
> related to your patch. But still I wonder why they show up so
> consistently.
>
> Is anyone from the list able to provide some thoughts?
Please, ignore, they go through guc_ggtt_invalidate... the log
was hidden :-)
Andi
prev parent reply other threads:[~2023-10-05 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 22:07 [Intel-gfx] [PATCH dii-client v6 0/5] Subject: [PATCH dii-client v6 0/4] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-04 22:07 ` [Intel-gfx] [PATCH dii-client v6 1/5] drm/i915: Add GuC TLB Invalidation pci flags Jonathan Cavitt
2023-10-04 22:27 ` Michal Wajdeczko
2023-10-05 13:15 ` Jani Nikula
2023-10-04 22:07 ` [Intel-gfx] [PATCH dii-client v6 1/4] drm/i915: Add GuC TLB Invalidation pci tags Jonathan Cavitt
2023-10-04 22:07 ` [Intel-gfx] [PATCH dii-client v6 2/5] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-04 22:48 ` Michal Wajdeczko
2023-10-05 13:58 ` Andi Shyti
2023-10-04 22:07 ` [Intel-gfx] [PATCH dii-client v6 3/5] drm/i915: No TLB invalidation on wedged or suspended GT Jonathan Cavitt
2023-10-04 22:07 ` [Intel-gfx] [PATCH dii-client v6 4/5] drm/i915/gt: Increase sleep in gt_tlb selftest sanitycheck Jonathan Cavitt
2023-10-04 22:07 ` [Intel-gfx] [PATCH dii-client v6 5/5] drm/i915: Enable GuC TLB invalidations for MTL Jonathan Cavitt
2023-10-05 2:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Subject: [PATCH dii-client v6 0/4] drm/i915: Define and use GuC and CTB TLB invalidation routines Patchwork
2023-10-05 2:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-05 3:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-05 13:00 ` Andi Shyti
2023-10-05 13:03 ` Andi Shyti [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=ZR60I2gMgjdlGaXX@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@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