Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for Fix TLB invalidate issues with Broadwell (rev4)
Date: Mon, 11 Jul 2022 08:31:22 +0200	[thread overview]
Message-ID: <20220711083122.0eb3026b@maurocar-mobl2> (raw)
In-Reply-To: <Ysg/wBwE5+TdaDFc@intel.com>

On Fri, 8 Jul 2022 10:31:28 -0400
Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:

> On Fri, Jul 08, 2022 at 06:00:52AM -0000, Patchwork wrote:
> >    Patch Details
> > 
> >    Series:  Fix TLB invalidate issues with Broadwell (rev4)
> >    URL:     [1]https://patchwork.freedesktop.org/series/105167/
> >    State:   failure
> >    Details:
> >    [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105167v4/index.ht
> >    ml
> > 
> >      CI Bug Log - changes from CI_DRM_11857_full -> Patchwork_105167v4_full
> > 
> > Summary
> > 
> >    FAILURE
> > 
> >    Serious unknown changes coming with Patchwork_105167v4_full absolutely
> >    need to be
> >    verified manually.
> > 
> >    If you think the reported changes have nothing to do with the changes
> >    introduced in Patchwork_105167v4_full, please notify your bug team to
> >    allow them
> >    to document this new failure mode, which will reduce false positives in
> >    CI.
> > 
> > Participating hosts (13 -> 13)
> > 
> >    No changes in participating hosts
> > 
> > Possible new issues
> > 
> >    Here are the unknown changes that may have been introduced in
> >    Patchwork_105167v4_full:
> > 
> >   IGT changes
> > 
> >     Possible regressions
> > 
> >      * igt@i915_selftest@live@perf:
> >           + shard-skl: [3]PASS -> [4]INCOMPLETE  
> 
> probably yet another false positive failure, but since the authorship-vs-sign-off
> needs to be fixed and resent we will end up testing it again.
> Sorry for not noticing yesterday before I had triggered the retest.
	
Yeah, that sounds to be a false-positive:

	Starting dynamic subtest: perf
	Starting dynamic subtest: perf
	Dmesg	
	<6> [1163.312914] [IGT] i915_selftest: starting dynamic subtest perf
	<5> [1164.217938] Setting dangerous option enable_psr - tainting kernel
	<5> [1164.217989] Setting dangerous option live_selftests - tainting kernel

Which didn't occur on the first run of the bot:

	Date: Thu, 07 Jul 2022 15:06:47 -0000
	From: Patchwork <patchwork@emeril.freedesktop.org>
	To: "Mauro Carvalho Chehab" <mchehab@kernel.org>
	Cc: intel-gfx@lists.freedesktop.org
	Subject: [Intel-gfx] ? Fi.CI.BAT: success for Fix TLB invalidate
		issues with Broadwell (rev4)

I'll re-send the series with the SOB/Author fix, collecting the A-B
and R-B received during review of rev4.

Thanks!
Mauro

      reply	other threads:[~2022-07-11  6:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  8:09 [Intel-gfx] [PATCH v3 0/2] Fix TLB invalidate issues with Broadwell Mauro Carvalho Chehab
2022-07-04  8:09 ` [Intel-gfx] [PATCH v3 1/2] drm/i915/gt: Serialize GRDOM access between multiple engine resets Mauro Carvalho Chehab
2022-07-04 15:20   ` Mauro Carvalho Chehab
2022-07-06 10:51   ` Andi Shyti
2022-07-07 21:27   ` Andrzej Hajda
2022-07-04  8:09 ` [Intel-gfx] [PATCH v3 2/2] drm/i915/gt: Serialize TLB invalidates with GT resets Mauro Carvalho Chehab
2022-07-04 15:20   ` Mauro Carvalho Chehab
2022-07-06 10:50   ` Andi Shyti
2022-07-07 21:28   ` Andrzej Hajda
2022-07-04 15:20 ` [Intel-gfx] [PATCH v3 0/2] Fix TLB invalidate issues with Broadwell Mauro Carvalho Chehab
2022-07-04 19:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix TLB invalidate issues with Broadwell (rev3) Patchwork
2022-07-04 19:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-07-04 19:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-05  0:53 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-07 14:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix TLB invalidate issues with Broadwell (rev4) Patchwork
2022-07-08 14:27   ` Rodrigo Vivi
2022-07-07 14:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-07-08 14:29   ` Rodrigo Vivi
2022-07-11  6:16     ` Mauro Carvalho Chehab
2022-07-07 15:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-08  6:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-08 14:31   ` Rodrigo Vivi
2022-07-11  6:31     ` Mauro Carvalho Chehab [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=20220711083122.0eb3026b@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mchehab@kernel.org \
    --cc=rodrigo.vivi@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