From: John Harrison <john.c.harrison@intel.com>
To: <intel-gfx@lists.freedesktop.org>,
Patchwork <patchwork@emeril.freedesktop.org>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Improve anti-pre-emption w/a for compute workloads (rev8)
Date: Mon, 10 Oct 2022 12:44:59 -0700 [thread overview]
Message-ID: <5682621a-d507-39f2-58e1-5a646d31adc9@intel.com> (raw)
In-Reply-To: <166509481464.5838.16580429148593384568@emeril.freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 8068 bytes --]
On 10/6/2022 15:20, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* Improve anti-pre-emption w/a for compute workloads (rev8)
> *URL:* https://patchwork.freedesktop.org/series/100428/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/index.html
>
>
> CI Bug Log - changes from CI_DRM_12223 -> Patchwork_100428v8
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_100428v8 absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_100428v8, 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_100428v8/index.html
>
>
> Participating hosts (42 -> 40)
>
> Missing (2): fi-ctg-p8600 fi-hsw-4200u
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_100428v8:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@i915_selftest@live@migrate:
> o fi-apl-guc: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/fi-apl-guc/igt@i915_selftest@live@migrate.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-apl-guc/igt@i915_selftest@live@migrate.html>
>
The logs seems to suggest the test just stopped (with the actual dmesg0
link being corrupted at the end). Seems likely there was a kernel panic
followed by reboot. Given that this patch set is only affecting hang
detection and recovery and the migrate test is not supposed to hit any
hangs, it seems very unlikely this failure is related. Certainly, all
previous revisions of this patch set did not any problems with the
live@migrate test.
John.
> *
>
>
> Known issues
>
> Here are the changes found in Patchwork_100428v8 that come from known
> issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_exec_suspend@basic-s3@smem:
>
> o fi-rkl-11600: NOTRUN -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-rkl-11600/igt@gem_exec_suspend@basic-s3@smem.html>
> (fdo#103375 <https://bugs.freedesktop.org/show_bug.cgi?id=103375>)
> *
>
> igt@i915_selftest@live@gt_heartbeat:
>
> o fi-apl-guc: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html>
> -> DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html>
> (i915#5334 <https://gitlab.freedesktop.org/drm/intel/issues/5334>)
> *
>
> igt@i915_selftest@live@hangcheck:
>
> o fi-hsw-g3258: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/fi-hsw-g3258/igt@i915_selftest@live@hangcheck.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-hsw-g3258/igt@i915_selftest@live@hangcheck.html>
> (i915#3303
> <https://gitlab.freedesktop.org/drm/intel/issues/3303> /
> i915#4785 <https://gitlab.freedesktop.org/drm/intel/issues/4785>)
> *
>
> igt@kms_chamelium@common-hpd-after-suspend:
>
> o
>
> fi-rkl-11600: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-rkl-11600/igt@kms_chamelium@common-hpd-after-suspend.html>
> (fdo#111827 <https://bugs.freedesktop.org/show_bug.cgi?id=111827>)
>
> o
>
> bat-dg1-5: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-dg1-5/igt@kms_chamelium@common-hpd-after-suspend.html>
> (fdo#111827 <https://bugs.freedesktop.org/show_bug.cgi?id=111827>)
>
> *
>
> igt@kms_pipe_crc_basic@suspend-read-crc:
>
> o bat-dg1-5: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-dg1-5/igt@kms_pipe_crc_basic@suspend-read-crc.html>
> (i915#4078 <https://gitlab.freedesktop.org/drm/intel/issues/4078>)
> *
>
> igt@runner@aborted:
>
> o fi-hsw-g3258: NOTRUN -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-hsw-g3258/igt@runner@aborted.html>
> (fdo#109271
> <https://bugs.freedesktop.org/show_bug.cgi?id=109271> /
> i915#4312 <https://gitlab.freedesktop.org/drm/intel/issues/4312>)
>
>
> Possible fixes
>
> *
>
> igt@i915_pm_rpm@module-reload:
>
> o {bat-rpls-2}: DMESG-WARN
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/bat-rpls-2/igt@i915_pm_rpm@module-reload.html>
> (i915#5537
> <https://gitlab.freedesktop.org/drm/intel/issues/5537>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-rpls-2/igt@i915_pm_rpm@module-reload.html>
> *
>
> igt@i915_selftest@live@gt_engines:
>
> o bat-dg1-5: INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/bat-dg1-5/igt@i915_selftest@live@gt_engines.html>
> (i915#4418
> <https://gitlab.freedesktop.org/drm/intel/issues/4418>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-dg1-5/igt@i915_selftest@live@gt_engines.html>
> *
>
> igt@i915_selftest@live@gt_pm:
>
> o {bat-adln-1}: DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/bat-adln-1/igt@i915_selftest@live@gt_pm.html>
> (i915#4258
> <https://gitlab.freedesktop.org/drm/intel/issues/4258>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-adln-1/igt@i915_selftest@live@gt_pm.html>
> *
>
> igt@i915_selftest@live@requests:
>
> o {bat-rpls-1}: INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/bat-rpls-1/igt@i915_selftest@live@requests.html>
> (i915#4983
> <https://gitlab.freedesktop.org/drm/intel/issues/4983> /
> i915#6257
> <https://gitlab.freedesktop.org/drm/intel/issues/6257>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-rpls-1/igt@i915_selftest@live@requests.html>
> *
>
> igt@i915_suspend@basic-s3-without-i915:
>
> o
>
> fi-rkl-11600: INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/fi-rkl-11600/igt@i915_suspend@basic-s3-without-i915.html>
> (i915#5982
> <https://gitlab.freedesktop.org/drm/intel/issues/5982>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-rkl-11600/igt@i915_suspend@basic-s3-without-i915.html>
>
> o
>
> {bat-rpls-2}: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/bat-rpls-2/igt@i915_suspend@basic-s3-without-i915.html>
> (i915#6559
> <https://gitlab.freedesktop.org/drm/intel/issues/6559>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/bat-rpls-2/igt@i915_suspend@basic-s3-without-i915.html>
>
> {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_12223 -> Patchwork_100428v8
>
> CI-20190529: 20190529
> CI_DRM_12223: c53a5e48e0405a63cda64682304cd8b391025be3 @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGT_7002: 523844c74e7da6b39d856596c28a92f04172035f @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_100428v8: c53a5e48e0405a63cda64682304cd8b391025be3 @
> git://anongit.freedesktop.org/gfx-ci/linux
>
>
> Linux commits
>
> e774225914cc drm/i915: Improve long running compute w/a for GuC submission
> bfcef6af116f drm/i915: Make the heartbeat play nice with long
> pre-emption timeouts
> 4141fa7b0427 drm/i915: Fix compute pre-emption w/a to apply to compute
> engines
> eff9e2347441 drm/i915/guc: Limit scheduling properties to avoid overflow
>
[-- Attachment #2: Type: text/html, Size: 11934 bytes --]
next prev parent reply other threads:[~2022-10-10 19:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 21:38 [Intel-gfx] [PATCH v5 0/4] Improve anti-pre-emption w/a for compute workloads John.C.Harrison
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 1/4] drm/i915/guc: Limit scheduling properties to avoid overflow John.C.Harrison
2022-10-18 0:06 ` Ceraolo Spurio, Daniele
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 2/4] drm/i915: Fix compute pre-emption w/a to apply to compute engines John.C.Harrison
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 3/4] drm/i915: Make the heartbeat play nice with long pre-emption timeouts John.C.Harrison
2022-10-07 8:44 ` Tvrtko Ursulin
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 4/4] drm/i915: Improve long running compute w/a for GuC submission John.C.Harrison
2022-10-18 0:09 ` Ceraolo Spurio, Daniele
2022-10-06 21:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improve anti-pre-emption w/a for compute workloads (rev8) Patchwork
2022-10-06 21:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-06 22:20 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-10 19:44 ` John Harrison [this message]
2022-10-12 13:54 ` Tvrtko Ursulin
2022-10-12 15:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improve anti-pre-emption w/a for compute workloads (rev9) Patchwork
2022-10-12 15:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-12 15:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-12 23:55 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=5682621a-d507-39f2-58e1-5a646d31adc9@intel.com \
--to=john.c.harrison@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=tvrtko.ursulin@linux.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