From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "De Marchi, Lucas" <lucas.demarchi@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dmc: Do not try loading wrong DMC version
Date: Fri, 25 Feb 2022 18:37:17 +0000 [thread overview]
Message-ID: <3c206c7b9f60402996cf96f66e67aae3@intel.com> (raw)
In-Reply-To: <20220225160440.s7yxd7tgnj7azocl@ldmartin-desk2>
Re-reported after addressing all the failures. See below for bug id's.
-----Original Message-----
From: De Marchi, Lucas <lucas.demarchi@intel.com>
Sent: Friday, February 25, 2022 8:05 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/dmc: Do not try loading wrong DMC version
On Fri, Feb 25, 2022 at 08:47:05AM +0000, Patchwork wrote:
>== Series Details ==
>
>Series: drm/i915/dmc: Do not try loading wrong DMC version
>URL : https://patchwork.freedesktop.org/series/100664/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_11279_full -> Patchwork_22393_full
>====================================================
>
>Summary
>-------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_22393_full absolutely
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_22393_full, please notify your bug team to
> allow them to document this new failure mode, which will reduce false positives in CI.
>
>
>
>Participating hosts (11 -> 11)
>------------------------------
>
> No changes in participating hosts
>
>Possible new issues
>-------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_22393_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
> * igt@gem_eio@in-flight-suspend:
> - shard-skl: [PASS][1] -> [INCOMPLETE][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/shard-skl8/igt@gem_eio@in-flight-suspend.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-skl6/ig
> t@gem_eio@in-flight-suspend.html
>
Lakshmi: This is related to https://gitlab.freedesktop.org/drm/intel/-/issues/4843
igt@gem_eio@in-flight-suspend - incomplete - PM: suspend entry (deep)
> * igt@kms_flip@busy-flip@a-hdmi-a1:
> - shard-glk: [PASS][3] -> [FAIL][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/shard-glk1/igt@kms_flip@busy-flip@a-hdmi-a1.html
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-glk8/ig
> t@kms_flip@busy-flip@a-hdmi-a1.html
this could only be a regression if it was in another display_ver == 12.
Those are not.
Lakshmi: This is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/4628
igt@kms_flip@busy-flip@.* - fail - Failed assertion: do_page_flip(o, new_fb_id, 0) == -16,error: 0 != -16
>
>
>#### Warnings ####
>
> * igt@i915_pm_dc@dc3co-vpb-simulation:
> - shard-skl: [SKIP][5] ([fdo#109271] / [i915#658]) -> [INCOMPLETE][6]
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11279/shard-skl10/igt@i915_pm_dc@dc3co-vpb-simulation.html
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-skl6/ig
> t@i915_pm_dc@dc3co-vpb-simulation.html
>
>
>#### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
> - {shard-tglu}: NOTRUN -> [DMESG-WARN][7] +1 similar issue
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-tglu-1/
> igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes.html
this one woruld be suspicious, but the DMC issue there is caused by an earlier error. Checking another run for this same machine, both are loading the same DMC:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11276/shard-tglu-1/boot9.txt
<7>[ 6.100322] i915 0000:00:02.0: [drm:intel_dmc_ucode_init [i915]] Loading i915/tgl_dmc_ver2_12.bin
<7>[ 6.101182] i915 0000:00:02.0: [drm:intel_fbc_init [i915]] Sanitized enable_fbc value: 1
<7>[ 6.102264] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM0 latency 3 (3.0 usec)
<7>[ 6.102480] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM1 latency 54 (54.0 usec)
<7>[ 6.102592] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM2 latency 54 (54.0 usec)
<7>[ 6.102712] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM3 latency 54 (54.0 usec)
<7>[ 6.102820] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM4 latency 54 (54.0 usec)
<7>[ 6.102977] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM5 latency 73 (73.0 usec)
<7>[ 6.103040] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM6 latency 110 (110.0 usec)
<7>[ 6.103176] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM7 latency 115 (115.0 usec)
<6>[ 6.104018] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
and https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22393/shard-tglu-1/boot16.txt
<7>[ 6.108031] i915 0000:00:02.0: [drm:intel_dmc_ucode_init [i915]] Loading i915/tgl_dmc_ver2_12.bin
<7>[ 6.109333] i915 0000:00:02.0: [drm:intel_fbc_init [i915]] Sanitized enable_fbc value: 1
<7>[ 6.110644] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM0 latency 3 (3.0 usec)
<7>[ 6.111192] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM1 latency 54 (54.0 usec)
<7>[ 6.111311] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM2 latency 54 (54.0 usec)
<6>[ 6.111481] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
<7>[ 6.111479] i915 0000:00:02.0: [drm:intel_print_wm_latency [i915]] Gen9 Plane WM3 latency 54 (54.0 usec
Can't be caused by this series.
Lakshmi: This is related to https://gitlab.freedesktop.org/drm/intel/-/issues/5122
Few tests - dmesg-warn/incomplete - i915 raw-wakerefs=1 wakelocks=1 on cleanup, WARNING: .* at drivers/gpu/drm/i915/intel_runtime_pm.c:\d+ intel_runtime_pm_driver_release
Lucas De Marchi
next prev parent reply other threads:[~2022-02-25 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 21:09 [Intel-gfx] [PATCH] drm/i915/dmc: Do not try loading wrong DMC version Lucas De Marchi
2022-02-23 21:15 ` Matt Roper
2022-02-24 17:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-02-24 18:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-25 8:47 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-25 12:55 ` Ramalingam C
2022-02-25 16:04 ` Lucas De Marchi
2022-02-25 18:37 ` Vudum, Lakshminarayana [this message]
2022-02-25 16:57 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=3c206c7b9f60402996cf96f66e67aae3@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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