From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Fix TLB invalidate issues with Broadwell (rev5)
Date: Mon, 11 Jul 2022 16:16:55 -0400 [thread overview]
Message-ID: <YsyFNxt50Sum6i/f@intel.com> (raw)
In-Reply-To: <20220711171123.3849fa64@maurocar-mobl2>
On Mon, Jul 11, 2022 at 05:11:23PM +0200, Mauro Carvalho Chehab wrote:
> On Mon, 11 Jul 2022 10:06:38 -0400
> Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>
> > On Mon, Jul 11, 2022 at 08:22:33AM -0000, Patchwork wrote:
> > > Patch Details
> > >
> > > Series: Fix TLB invalidate issues with Broadwell (rev5)
> > > URL: [1]https://patchwork.freedesktop.org/series/105167/
> > > State: failure
> > > Details:
> > > [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105167v5/index.ht
> > > ml
> > >
> > > CI Bug Log - changes from CI_DRM_11862 -> Patchwork_105167v5
> > >
> > > Summary
> > >
> > > FAILURE
> > >
> > > Serious unknown changes coming with Patchwork_105167v5 absolutely need
> > > to be
> > > verified manually.
> > >
> > > If you think the reported changes have nothing to do with the changes
> > > introduced in Patchwork_105167v5, 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_105167v5/index.html
> > >
> > > Participating hosts (45 -> 42)
> > >
> > > Additional (2): bat-rpls-1 bat-dg1-5
> > > Missing (5): fi-cml-u2 fi-hsw-4200u fi-icl-u2 fi-ctg-p8600 bat-jsl-3
> > >
> > > Possible new issues
> > >
> > > Here are the unknown changes that may have been introduced in
> > > Patchwork_105167v5:
> > >
> > > IGT changes
> > >
> > > Possible regressions
> > >
> > > * igt@i915_selftest@live@gem:
> > > + fi-elk-e7500: [3]PASS -> [4]DMESG-FAIL
> >
> > I also believe this is a false positive...
> > triggered a retest...
>
> Yeah, the latest test gave success:
>
> Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for Fix TLB invalidate issues with Broadwell (rev6)
> Date: Mon, 11 Jul 2022 14:53:40 -0000
> Reply-To: intel-gfx@lists.freedesktop.org
> Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
>
> == Series Details ==
>
> Series: Fix TLB invalidate issues with Broadwell (rev6)
> URL : https://patchwork.freedesktop.org/series/105167/
> State : success
>
> >
> > hoping to get this series merged today...
>
> Yeah, it would be great to have this merged, as it is a regression
> fix.
we got yet another false positive... I was tired and decided to ignore and move ahead.
but then I noticed that the author and sign-off-bys are not right... :(
please fix that... the author needs to sign-off-by...
>
> Regards,
> Mauro
next prev parent reply other threads:[~2022-07-11 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 6:50 [Intel-gfx] [PATCH v4 0/2] Fix TLB invalidate issues with Broadwell Mauro Carvalho Chehab
2022-07-11 6:50 ` [Intel-gfx] [PATCH v4 1/2] drm/i915/gt: Serialize GRDOM access between multiple engine resets Mauro Carvalho Chehab
2022-07-11 6:50 ` [Intel-gfx] [PATCH v4 2/2] drm/i915/gt: Serialize TLB invalidates with GT resets Mauro Carvalho Chehab
2022-07-11 8:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix TLB invalidate issues with Broadwell (rev5) Patchwork
2022-07-11 8:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-07-11 14:06 ` Rodrigo Vivi
2022-07-11 15:11 ` Mauro Carvalho Chehab
2022-07-11 20:16 ` Rodrigo Vivi [this message]
2022-07-11 14:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix TLB invalidate issues with Broadwell (rev6) Patchwork
2022-07-11 14:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-07-11 14:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-11 18:17 ` [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=YsyFNxt50Sum6i/f@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mauro.chehab@linux.intel.com \
--cc=mchehab@kernel.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