All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for The xe_sa_manager based GuC Buffer Cache (rev3)
Date: Sun, 19 Jan 2025 00:08:44 +0100	[thread overview]
Message-ID: <582004f8-d3b2-4ada-9c7b-e75323ce39cc@intel.com> (raw)
In-Reply-To: <173690755415.3792291.15182563029458684105@b555e5b46a47>



On 15.01.2025 03:19, Patchwork wrote:
> == Series Details ==
> 
> Series: The xe_sa_manager based GuC Buffer Cache (rev3)
> URL   : https://patchwork.freedesktop.org/series/142458/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2486-172fa6a9ff822aef630db23984a76f7984698198_full -> xe-pw-142458v3_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-142458v3_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-142458v3_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-142458v3_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_async_flips@alternate-sync-async-flip:
>     - shard-dg2-set2:     NOTRUN -> [INCOMPLETE][1] +1 other test incomplete
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-dg2-434/igt@kms_async_flips@alternate-sync-async-flip.html
> 
>   * igt@kms_cursor_crc@cursor-suspend:
>     - shard-dg2-set2:     [PASS][2] -> [ABORT][3]
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2486-172fa6a9ff822aef630db23984a76f7984698198/shard-dg2-434/igt@kms_cursor_crc@cursor-suspend.html
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-dg2-432/igt@kms_cursor_crc@cursor-suspend.html
> 
>   * igt@kms_flip@2x-flip-vs-expired-vblank@ad-dp2-hdmi-a3:
>     - shard-bmg:          [PASS][4] -> [FAIL][5]
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2486-172fa6a9ff822aef630db23984a76f7984698198/shard-bmg-7/igt@kms_flip@2x-flip-vs-expired-vblank@ad-dp2-hdmi-a3.html
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-bmg-3/igt@kms_flip@2x-flip-vs-expired-vblank@ad-dp2-hdmi-a3.html
> 
>   * igt@kms_flip@blocking-wf_vblank@a-hdmi-a2:
>     - shard-dg2-set2:     NOTRUN -> [FAIL][6] +2 other tests fail
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-dg2-432/igt@kms_flip@blocking-wf_vblank@a-hdmi-a2.html
> 
>   * igt@kms_flip@flip-vs-suspend@d-dp2:
>     - shard-dg2-set2:     NOTRUN -> [ABORT][7] +1 other test abort
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-dg2-432/igt@kms_flip@flip-vs-suspend@d-dp2.html
> 
>   * igt@kms_plane_lowres@tiling-4@pipe-c-dp-4:
>     - shard-dg2-set2:     [PASS][8] -> [DMESG-WARN][9]
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2486-172fa6a9ff822aef630db23984a76f7984698198/shard-dg2-434/igt@kms_plane_lowres@tiling-4@pipe-c-dp-4.html
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-dg2-434/igt@kms_plane_lowres@tiling-4@pipe-c-dp-4.html
> 
>   * igt@kms_rotation_crc@multiplane-rotation-cropping-top:
>     - shard-dg2-set2:     [PASS][10] -> [INCOMPLETE][11] +1 other test incomplete
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2486-172fa6a9ff822aef630db23984a76f7984698198/shard-dg2-433/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html
>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-dg2-464/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html

all above are unrelated

> 
>   * igt@xe_module_load@many-reload:
>     - shard-bmg:          [PASS][12] -> [ABORT][13]
>    [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2486-172fa6a9ff822aef630db23984a76f7984698198/shard-bmg-2/igt@xe_module_load@many-reload.html
>    [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142458v3/shard-bmg-6/igt@xe_module_load@many-reload.html

this looks serious but it's also unrelated

<4> [201.260763] Oops: general protection fault, probably for
non-canonical address 0x6b6b6b6b6b6b6b6b: 0000 [#1] PREEMPT SMP NOPTI
<4> [201.260782] CPU: 12 UID: 0 PID: 3932 Comm: kworker/u64:108 Tainted:
G        W          6.13.0-rc7-xe+ #1
<4> [201.260793] Tainted: [W]=WARN
<4> [201.260796] Hardware name: ASUS System Product Name/PRIME Z790-P
WIFI, BIOS 1656 04/18/2024
<4> [201.260804] Workqueue: xe-dp i915_digport_work_func [xe]
<4> [201.260981] RIP: 0010:drm_dp_dpcd_access+0xbf/0x160
[drm_display_helper]
<4> [201.261007] Code: d2 74 19 83 fa 92 74 14 ba 02 00 00 00 be 58 02
00 00 bf f4 01 00 00 e8 df a9 d7 e1 49 8b 87 68 08 00 00 48 8d 75 b8 4c
89 ff <ff> d0 0f 1f 00 89 c2 85 c0 78 be f6 45 bd 03 74 a8 ba fb ff ff ff
<4> [201.261019] RSP: 0018:ffffc900055cbc88 EFLAGS: 00010246
<4> [201.261025] RAX: 6b6b6b6b6b6b6b6b RBX: 0000000000000003 RCX:
0000000000000000
<4> [201.261032] RDX: 0000000000000000 RSI: ffffc900055cbc90 RDI:
ffff88813eb82350
<4> [201.261037] RBP: ffffc900055cbcd8 R08: 0000000000000000 R09:
0000000000000000
<4> [201.261043] R10: 0000000000000000 R11: 0000000000000000 R12:
0000000000000001
<4> [201.261049] R13: ffff88813eb82ad8 R14: 00000000fffffffa R15:
ffff88813eb82350
<4> [201.261055] FS:  0000000000000000(0000) GS:ffff88885f200000(0000)
knlGS:0000000000000000
<4> [201.261062] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [201.261068] CR2: 000076a2989a7f70 CR3: 000000014e0b0006 CR4:
0000000000f72ef0
<4> [201.261075] PKRU: 55555554
<4> [201.261079] Call Trace:
<4> [201.261082]  <TASK>
<4> [201.261086]  ? show_regs+0x6c/0x80
<4> [201.261094]  ? die_addr+0x37/0xa0
<4> [201.261100]  ? exc_general_protection+0x1c1/0x440
<4> [201.261110]  ? asm_exc_general_protection+0x27/0x30
<4> [201.261121]  ? drm_dp_dpcd_access+0xbf/0x160 [drm_display_helper]
<4> [201.261144]  ? drm_dp_dpcd_access+0xb1/0x160 [drm_display_helper]
<4> [201.261167]  drm_dp_dpcd_probe+0x41/0x100 [drm_display_helper]
<4> [201.261190]  intel_dp_read_dprx_caps+0x85/0xa0 [xe]
<4> [201.261330]  intel_dp_hpd_pulse+0xb6/0x6a0 [xe]
<4> [201.261449]  i915_digport_work_func+0xc9/0x170 [xe]
<4> [201.261553]  process_one_work+0x21c/0x740
<4> [201.261561]  worker_thread+0x1db/0x3c0
<4> [201.261566]  ? __pfx_worker_thread+0x10/0x10
<4> [201.261571]  kthread+0xf3/0x130
<4> [201.261575]  ? __pfx_kthread+0x10/0x10
<4> [201.261579]  ret_from_fork+0x44/0x70
<4> [201.261584]  ? __pfx_kthread+0x10/0x10
<4> [201.261588]  ret_from_fork_asm+0x1a/0x30
<4> [201.261594]  </TASK>




      reply	other threads:[~2025-01-18 23:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 19:41 [PATCH v2 00/11] The xe_sa_manager based GuC Buffer Cache Michal Wajdeczko
2024-12-20 19:41 ` [PATCH v2 01/11] drm/xe/sa: Always call drm_suballoc_manager_fini() Michal Wajdeczko
2024-12-20 19:41 ` [PATCH v2 02/11] drm/xe/sa: Drop redundant NULL assignments Michal Wajdeczko
2024-12-20 19:41 ` [PATCH v2 03/11] drm/xe/sa: Improve error message on init failure Michal Wajdeczko
2024-12-20 19:41 ` [PATCH v2 04/11] drm/xe/sa: Tidy up coding style in init() Michal Wajdeczko
2024-12-20 19:41 ` [PATCH v2 05/11] drm/xe/sa: Allow making suballocations using custom gfp flags Michal Wajdeczko
2024-12-20 19:41 ` [PATCH v2 06/11] drm/xe/sa: Allow creating suballocator with custom guard size Michal Wajdeczko
2024-12-20 19:42 ` [PATCH v2 07/11] drm/xe/sa: Minor header cleanups Michal Wajdeczko
2024-12-20 19:42 ` [PATCH v2 08/11] drm/xe/guc: Introduce the GuC Buffer Cache Michal Wajdeczko
2024-12-20 21:15   ` Matthew Brost
2024-12-20 19:42 ` [PATCH v2 09/11] drm/xe/pf: Use GuC Buffer Cache during VFs provisioning Michal Wajdeczko
2024-12-20 21:23   ` Matthew Brost
2024-12-20 19:42 ` [PATCH v2 10/11] drm/xe/kunit: Allow to replace xe_managed_bo_create_pin_map() Michal Wajdeczko
2025-01-14 12:01   ` Michał Winiarski
2024-12-20 19:42 ` [PATCH v2 11/11] drm/xe/kunit: Add KUnit tests for GuC Buffer Cache Michal Wajdeczko
2025-01-14 12:04   ` Michał Winiarski
2025-01-14 19:21   ` [PATCH v3 " Michal Wajdeczko
2024-12-20 19:47 ` ✓ CI.Patch_applied: success for The xe_sa_manager based GuC Buffer Cache (rev2) Patchwork
2024-12-20 19:47 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-20 19:49 ` ✓ CI.KUnit: success " Patchwork
2024-12-20 20:14 ` ✓ CI.Build: " Patchwork
2024-12-20 20:17 ` ✓ CI.Hooks: " Patchwork
2024-12-20 20:20 ` ✓ CI.checksparse: " Patchwork
2024-12-20 20:53 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-22  0:59 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-14 21:53 ` ✓ CI.Patch_applied: success for The xe_sa_manager based GuC Buffer Cache (rev3) Patchwork
2025-01-14 21:54 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-14 21:55 ` ✓ CI.KUnit: success " Patchwork
2025-01-14 22:13 ` ✓ CI.Build: " Patchwork
2025-01-14 22:15 ` ✓ CI.Hooks: " Patchwork
2025-01-14 22:17 ` ✓ CI.checksparse: " Patchwork
2025-01-14 22:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-15  2:19 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-18 23:08   ` 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=582004f8-d3b2-4ada-9c7b-e75323ce39cc@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.