From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.FULL: failure for PF: threshold config fixes
Date: Mon, 2 Sep 2024 20:44:28 +0200 [thread overview]
Message-ID: <91b77dd0-1132-4abc-b913-54f24054c4bd@intel.com> (raw)
In-Reply-To: <172507210447.870668.13648793813923277783@2413ebb6fbb6>
On 31.08.2024 04:41, Patchwork wrote:
> == Series Details ==
>
> Series: PF: threshold config fixes
> URL : https://patchwork.freedesktop.org/series/138023/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-1867-876db6b8ef45d285316cc53b5cf44cbc39aa8758_full -> xe-pw-138023v1_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-138023v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-138023v1_full, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
>
>
> Participating hosts (4 -> 4)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-138023v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@xe_vm@munmap-style-unbind-userptr-one-partial:
> - shard-dg2-set2: [PASS][1] -> [DMESG-WARN][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1867-876db6b8ef45d285316cc53b5cf44cbc39aa8758/shard-dg2-434/igt@xe_vm@munmap-style-unbind-userptr-one-partial.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138023v1/shard-dg2-433/igt@xe_vm@munmap-style-unbind-userptr-one-partial.html
<3> [196.507166] xe 0000:03:00.0: [drm] *ERROR* GT0: GuC PC Start failed
<4> [196.507215] ------------[ cut here ]------------
<4> [196.507217] xe 0000:03:00.0: [drm] GT0: Failed to start GuC PC: -EIO
<4> [196.507231] WARNING: CPU: 11 PID: 1715 at
drivers/gpu/drm/xe/xe_guc.c:1138 xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507377] Workqueue: gt-ordered-wq gt_reset_worker [xe]
<4> [196.507427] RIP: 0010:xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507480] Call Trace:
<4> [196.507481] <TASK>
<4> [196.507483] ? show_regs+0x67/0x70
<4> [196.507487] ? __warn+0x94/0x1b0
<4> [196.507490] ? xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507527] ? report_bug+0x1b7/0x1d0
<4> [196.507531] ? handle_bug+0x46/0x80
<4> [196.507533] ? exc_invalid_op+0x19/0x70
<4> [196.507535] ? asm_exc_invalid_op+0x1b/0x20
<4> [196.507539] ? xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507576] ? cancel_work_sync+0x10/0x20
<4> [196.507579] xe_uc_start+0x28/0x30 [xe]
<4> [196.507635] do_gt_restart+0x110/0x670 [xe]
and this looks exactly as #2559
>
>
> #### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt:
> - {shard-bmg}: [FAIL][3] ([Intel XE#2333]) -> [INCOMPLETE][4]
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1867-876db6b8ef45d285316cc53b5cf44cbc39aa8758/shard-bmg-3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138023v1/shard-bmg-8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt.html
>
> * igt@xe_vm:
> - {shard-bmg}: NOTRUN -> [INCOMPLETE][5]
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138023v1/shard-bmg-4/igt@xe_vm.html
>
>
prev parent reply other threads:[~2024-09-02 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 13:20 [PATCH 0/2] PF: threshold config fixes Michal Wajdeczko
2024-08-30 13:20 ` [PATCH 1/2] drm/xe/pf: Add thresholds to the VF KLV config Michal Wajdeczko
2024-09-02 9:36 ` Piotr Piórkowski
2024-08-30 13:21 ` [PATCH 2/2] drm/xe/pf: Reset thresholds when releasing a VF config Michal Wajdeczko
2024-09-02 9:37 ` Piotr Piórkowski
2024-08-30 14:20 ` ✓ CI.Patch_applied: success for PF: threshold config fixes Patchwork
2024-08-30 14:20 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-30 14:21 ` ✓ CI.KUnit: success " Patchwork
2024-08-30 14:33 ` ✓ CI.Build: " Patchwork
2024-08-30 14:36 ` ✓ CI.Hooks: " Patchwork
2024-08-30 14:37 ` ✓ CI.checksparse: " Patchwork
2024-08-30 14:57 ` ✓ CI.BAT: " Patchwork
2024-08-31 2:41 ` ✗ CI.FULL: failure " Patchwork
2024-09-02 18:44 ` Michal Wajdeczko [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=91b77dd0-1132-4abc-b913-54f24054c4bd@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@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