Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT: failure for drm/i915/mtl: Add OAG 32 bit format support for MTL (rev4)
Date: Mon, 12 Dec 2022 14:03:07 -0800	[thread overview]
Message-ID: <Y5elG53efVUN/I8e@unerlige-ril> (raw)
In-Reply-To: <167069218001.23484.3918258440682791895@emeril.freedesktop.org>

On Sat, Dec 10, 2022 at 05:09:40PM +0000, Patchwork wrote:
>   Patch Details
>
>Series:  drm/i915/mtl: Add OAG 32 bit format support for MTL (rev4)
>URL:     [1]https://patchwork.freedesktop.org/series/111512/
>State:   failure
>Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111512v4/index.html
>
>          CI Bug Log - changes from CI_DRM_12491 -> Patchwork_111512v4
>
>Summary
>
>   FAILURE
>
>   Serious unknown changes coming with Patchwork_111512v4 absolutely need to
>   be
>   verified manually.
>
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_111512v4, 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_111512v4/index.html
>
>Participating hosts (41 -> 5)
>
>   ERROR: It appears as if the changes made in Patchwork_111512v4 prevented
>   too many machines from booting.
>
>   Missing (36): fi-kbl-soraka fi-rkl-11600 fi-rkl-guc bat-adls-5 bat-dg1-5
>   fi-bdw-gvtdvm fi-icl-u2 bat-adlp-6 fi-pnv-d510 bat-rpls-2 fi-skl-6600u
>   fi-snb-2600 fi-bsw-n3050 fi-adl-ddr5 bat-dg2-8 bat-adlm-1 bat-dg2-9
>   fi-hsw-4770 bat-atsm-1 fi-ivb-3770 bat-jsl-3 fi-elk-e7500 bat-dg2-11
>   fi-bsw-nick fi-skl-6700k2 fi-kbl-7567u bat-kbl-2 bat-adlp-9 fi-skl-guc
>   fi-glk-j4005 fi-ehl-2 fi-jsl-1 fi-cfl-guc bat-adlp-4 fi-kbl-8809g
>   fi-bsw-kefka

This looks like a false alarm. I loaded this on an ADLP and KBL and I 
don't see any issues.  This does not happen on rev2. Diff between rev2 
and rev3 is a change in commit message. rev4 is just a rerun.

I will post a rebased version to see if this resolves.

Regards,
Umesh

>
>Known issues

      reply	other threads:[~2022-12-12 22:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  3:01 [Intel-gfx] [PATCH v3 0/4] drm/i915/mtl: Add OAG 32 bit format support for MTL Umesh Nerlige Ramappa
2022-12-10  3:01 ` [Intel-gfx] [PATCH v3 1/4] drm/i915/mtl: Resize noa_wait BO size to save restore GPR regs Umesh Nerlige Ramappa
2022-12-10  3:01 ` [Intel-gfx] [PATCH v3 2/4] drm/i915/mtl: Add Wa_14015846243 to fix OA vs CS timestamp mismatch Umesh Nerlige Ramappa
2022-12-10  3:01 ` [Intel-gfx] [PATCH v3 3/4] drm/i915/mtl: Update OA mux whitelist for MTL Umesh Nerlige Ramappa
2022-12-10  3:01 ` [Intel-gfx] [PATCH v3 4/4] drm/i915/mtl: Add OA support by enabling 32 bit OAG formats " Umesh Nerlige Ramappa
2022-12-12  5:55   ` Upadhyay, Tejas
2022-12-10  3:20 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Add OAG 32 bit format support for MTL (rev3) Patchwork
2022-12-10  3:31 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-12-10 16:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Add OAG 32 bit format support for MTL (rev4) Patchwork
2022-12-10 17:09 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-12-12 22:03   ` Umesh Nerlige Ramappa [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=Y5elG53efVUN/I8e@unerlige-ril \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=intel-gfx@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