Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT: failure for drm/i915: Fix FIFO underruns caused by missing cumulative bpp W/A
Date: Thu, 7 Apr 2022 09:59:09 +0000	[thread overview]
Message-ID: <a11c4289efd94d86bd0c1d84e7f60491@intel.com> (raw)
In-Reply-To: <164932340676.14670.10840435382668991086@emeril.freedesktop.org>

gt@i915_selftest@live@coherency failure on bdw, sure doesn't have anything with this patch :D

Restarted test run in hopes..

Best Regards,

Lisovskiy Stanislav

Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo

________________________________________
From: Patchwork <patchwork@emeril.freedesktop.org>
Sent: Thursday, April 7, 2022 12:23:26 PM
To: Lisovskiy, Stanislav
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Fix FIFO underruns caused by missing cumulative bpp W/A

Patch Details
Series: drm/i915: Fix FIFO underruns caused by missing cumulative bpp W/A
URL:    https://patchwork.freedesktop.org/series/102322/
State:  failure
Details:        https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/index.html
CI Bug Log - changes from CI_DRM_11469 -> Patchwork_22807
Summary

FAILURE

Serious unknown changes coming with Patchwork_22807 absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22807, 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_22807/index.html

Participating hosts (50 -> 45)

Missing (5): shard-tglu fi-bsw-cyan fi-ctg-p8600 fi-pnv-d510 fi-bdw-samus

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_22807:

IGT changes
Possible regressions

  *   igt@i915_selftest@live@coherency:
     *   fi-bdw-5557u: NOTRUN -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-bdw-5557u/igt@i915_selftest@live@coherency.html>

Known issues

Here are the changes found in Patchwork_22807 that come from known issues:

IGT changes
Issues hit

  *   igt@amdgpu/amd_basic@semaphore:

     *   fi-hsw-4770: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-hsw-4770/igt@amdgpu/amd_basic@semaphore.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#109315<https://bugs.freedesktop.org/show_bug.cgi?id=109315>) +17 similar issues
  *   igt@amdgpu/amd_cs_nop@fork-compute0:

     *   fi-blb-e6850: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-blb-e6850/igt@amdgpu/amd_cs_nop@fork-compute0.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +17 similar issues
  *   igt@kms_chamelium@vga-edid-read:

     *   fi-bdw-5557u: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-bdw-5557u/igt@kms_chamelium@vga-edid-read.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827<https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +8 similar issues
  *   igt@kms_setmode@basic-clone-single-crtc:

     *   fi-bdw-5557u: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-bdw-5557u/igt@kms_setmode@basic-clone-single-crtc.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +14 similar issues

Possible fixes

  *   igt@gem_exec_suspend@basic-s3@smem:

     *   fi-bdw-5557u: INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11469/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html> (i915#146<https://gitlab.freedesktop.org/drm/intel/issues/146>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html>
  *   igt@i915_selftest@live@hangcheck:

     *   fi-hsw-4770: INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11469/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html> (i915#4785<https://gitlab.freedesktop.org/drm/intel/issues/4785>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html>
  *   igt@i915_selftest@live@requests:

     *   fi-blb-e6850: DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11469/fi-blb-e6850/igt@i915_selftest@live@requests.html> (i915#4528<https://gitlab.freedesktop.org/drm/intel/issues/4528>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-blb-e6850/igt@i915_selftest@live@requests.html>

Warnings

  *   igt@core_hotunplug@unbind-rebind:

     *   fi-tgl-1115g4: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11469/fi-tgl-1115g4/igt@core_hotunplug@unbind-rebind.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>) -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-tgl-1115g4/igt@core_hotunplug@unbind-rebind.html> (i915#5577<https://gitlab.freedesktop.org/drm/intel/issues/5577>)
  *   igt@runner@aborted:

     *   fi-glk-j4005: FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11469/fi-glk-j4005/igt@runner@aborted.html> (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312> / i915#5257<https://gitlab.freedesktop.org/drm/intel/issues/5257> / k.org#202321<https://bugzilla.kernel.org/show_bug.cgi?id=202321>) -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-glk-j4005/igt@runner@aborted.html> (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312> / i915#5257<https://gitlab.freedesktop.org/drm/intel/issues/5257>)

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Build changes

  *   Linux: CI_DRM_11469 -> Patchwork_22807

CI-20190529: 20190529
CI_DRM_11469: d95bb535e8e80c0484bb6f13d1875efcdb084862 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6415: c3b690bd5f7fb1fb7ed786ab0f3b815930a6a55f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22807: b2b7dace2671214005e79582b62db58c64273533 @ git://anongit.freedesktop.org/gfx-ci/linux

== Kernel 32bit build ==

Warning: Kernel 32bit buildtest failed:
https://intel-gfx-ci.01.org/Patchwork_22807/build_32bit.log

CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
CHK include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready (#1)
MODPOST modules-only.symvers
ERROR: modpost: "__udivdi3" [drivers/gpu/drm/i915/i915.ko] undefined!
scripts/Makefile.modpost:134: recipe for target 'modules-only.symvers' failed
make1<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-bdw-5557u/igt@i915_selftest@live@coherency.html>: [modules-only.symvers] Error 1
make1<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22807/fi-bdw-5557u/igt@i915_selftest@live@coherency.html>: Deleting file 'modules-only.symvers'
Makefile:1749: recipe for target 'modules' failed
make: *** [modules] Error 2

== Linux commits ==

b2b7dace2671 drm/i915: Fix FIFO underruns caused by missing cumulative bpp W/A


  reply	other threads:[~2022-04-07  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  8:42 [Intel-gfx] [PATCH] drm/i915: Fix FIFO underruns caused by missing cumulative bpp W/A Stanislav Lisovskiy
2022-04-07  8:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-04-07  9:23 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-07  9:59   ` Lisovskiy, Stanislav [this message]
2022-04-07  9:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2022-04-07 11:10 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2022-04-07 11:24   ` Lisovskiy, Stanislav
2022-04-07 12:04     ` Ville Syrjälä
2022-04-07 11:39   ` Lisovskiy, Stanislav
2022-04-07 13:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix FIFO underruns caused by missing cumulative bpp W/A (rev2) Patchwork
2022-04-07 13:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-07 13:39 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " 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=a11c4289efd94d86bd0c1d84e7f60491@intel.com \
    --to=stanislav.lisovskiy@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