From: Jeff Layton <jlayton@kernel.org>
To: intel-gfx@lists.freedesktop.org
Cc: Krzysztof Karas <krzysztof.karas@intel.com>
Subject: Re: ✗ i915.CI.BAT: failure for ref_tracker: add ability to register a debugfs file for a ref_tracker_dir (rev9)
Date: Tue, 03 Jun 2025 09:23:23 -0400 [thread overview]
Message-ID: <fc99f9ee0495cbe4c989a774d002ae4afe761ea7.camel@kernel.org> (raw)
In-Reply-To: <174895473386.43118.3704275649238783088@1538d3639d33>
On Tue, 2025-06-03 at 12:45 +0000, Patchwork wrote:
> Patch Details
> Series: ref_tracker: add ability to register a debugfs file for a ref_tracker_dir (rev9)
> URL: https://patchwork.freedesktop.org/series/148490/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_148490v9/index.html
>
>
>
>
>
> CI Bug Log - changes from CI_DRM_16637 -> Patchwork_148490v9SummaryFAILURE
> Serious unknown changes coming with Patchwork_148490v9 absolutely need to be
> verified manually.
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_148490v9, 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.
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_148490v9/index.html
> Participating hosts (42 -> 42)Additional (1): bat-arlh-2
> Missing (1): fi-snb-2520m
> Possible new issuesHere are the unknown changes that may have been introduced in Patchwork_148490v9:
> IGT changesPossible regressions *
> igt@i915_pm_rpm@module-reload:bat-dg2-14: PASS -> DMESG-WARN +44 other tests dmesg-warnfi-bsw-nick: PASS -> DMESG-WARN +40 other tests dmesg-warnbat-kbl-2: PASS -> DMESG-WARN +40 other tests dmesg-warnbat-adlp-6: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@client:fi-elk-e7500: PASS -> DMESG-WARN +39 other tests dmesg-warnfi-kbl-guc: PASS -> DMESG-WARN +39 other tests dmesg-warnbat-adls-6: PASS -> DMESG-WARN +40 other tests dmesg-warnbat-dg1-7: PASS -> DMESG-WARN +15 other tests dmesg-warn
> *
> igt@i915_selftest@live@coherency:fi-kbl-x1275: PASS -> DMESG-WARN +39 other tests dmesg-warnbat-adlp-11: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@evict:fi-pnv-d510: PASS -> DMESG-WARN +39 other tests dmesg-warn
> *
> igt@i915_selftest@live@gem:fi-rkl-11600: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@gem_contexts:bat-arls-6: PASS -> DMESG-WARN +38 other tests dmesg-warnbat-arlh-3: PASS -> DMESG-WARN +38 other tests dmesg-warn
> *
> igt@i915_selftest@live@gt_engines:bat-dg1-6: PASS -> DMESG-WARN +44 other tests dmesg-warnfi-ilk-650: PASS -> DMESG-WARN +38 other tests dmesg-warn
> *
> igt@i915_selftest@live@gt_mocs:bat-twl-2: PASS -> DMESG-WARN +38 other tests dmesg-warn
> *
> igt@i915_selftest@live@gt_pm:fi-tgl-1115g4: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@gt_tlb:bat-adlp-9: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@guc_hang:bat-dg2-9: PASS -> DMESG-WARN +15 other tests dmesg-warn
> *
> igt@i915_selftest@live@guc_multi_lrc:bat-mtlp-8: PASS -> DMESG-WARN +38 other tests dmesg-warn
> *
> igt@i915_selftest@live@hangcheck:bat-atsm-1: PASS -> DMESG-WARN +41 other tests dmesg-warnbat-mtlp-9: PASS -> DMESG-WARN +20 other tests dmesg-warn
> *
> igt@i915_selftest@live@late_gt_pm:fi-cfl-8109u: PASS -> DMESG-WARN +38 other tests dmesg-warnfi-kbl-8809g: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@objects:fi-blb-e6850: PASS -> DMESG-WARN +38 other tests dmesg-warnfi-skl-6600u: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@perf:bat-dg2-11: PASS -> DMESG-WARN +42 other tests dmesg-warnfi-hsw-4770: PASS -> DMESG-WARN +39 other tests dmesg-warn
> *
> igt@i915_selftest@live@ring_submission:fi-ivb-3770: PASS -> DMESG-WARN +39 other tests dmesg-warnbat-dg2-8: PASS -> DMESG-WARN +15 other tests dmesg-warn
> *
> igt@i915_selftest@live@sanitycheck:fi-kbl-7567u: PASS -> DMESG-WARN +40 other tests dmesg-warnbat-twl-1: PASS -> DMESG-WARN +39 other tests dmesg-warnbat-apl-1: PASS -> DMESG-WARN +39 other tests dmesg-warnbat-arls-5: PASS -> DMESG-WARN +38 other tests dmesg-warnbat-rplp-1: PASS -> DMESG-WARN +40 other tests dmesg-warnbat-arlh-2: NOTRUN -> DMESG-WARN +22 other tests dmesg-warn
> *
> igt@i915_selftest@live@slpc:fi-cfl-guc: PASS -> DMESG-WARN +40 other tests dmesg-warnbat-mtlp-6: PASS -> DMESG-WARN +38 other tests dmesg-warn
> *
> igt@i915_selftest@live@vma:fi-cfl-8700k: PASS -> DMESG-WARN +40 other tests dmesg-warn
> *
> igt@i915_selftest@live@workarounds:fi-bsw-n3050: PASS -> DMESG-WARN +40 other tests dmesg-warn
> Warnings *
> igt@i915_module_load@reload:bat-twl-1: DMESG-WARN (i915#13736) -> DMESG-WARN
I'm very confused by this CI report, and I suspect that this may be a
bug in the i915 driver. The log above shows several instances of
messages like this:
<3> [414.085231] debugfs: File 'intel_wakeref@ffff88810f9c2308' in directory 'ref_tracker' already present!
...but if you look at the patch, it changes the code to only call
ref_tracker_dir_init() when the "class" pointer isn't set. Since the
containing object is zalloced, that should ensure that it only does
this once:
if (!wf->debug.class)
ref_tracker_dir_init(&wf->debug,
INTEL_REFTRACK_DEAD_COUNT, "intel_wakeref");
I think that the only way this could be happening is if the driver is
doing something like zeroing out the object that contains the struct
ref_tracker_dir and reinitializing it.
Does the i915 driver do that? Can we make it call
ref_tracker_dir_exit() before doing so? I don't think that practice is
safe if there are outstanding references at the time it occurs.
> *
> igt@i915_selftest@live:bat-arlh-3: DMESG-FAIL (i915#14243) -> DMESG-WARN +1 other test dmesg-warnbat-mtlp-9: DMESG-FAIL (i915#12061) -> DMESG-WARN
> *
> igt@i915_selftest@live@late_gt_pm:bat-twl-2: ABORT (i915#14357) -> DMESG-WARN +1 other test dmesg-warn
> *
> igt@i915_selftest@live@workarounds:bat-arls-5: DMESG-FAIL (i915#12061) -> DMESG-WARN +1 other test dmesg-warnbat-mtlp-6: DMESG-FAIL (i915#12061) -> DMESG-WARN +1 other test dmesg-warnbat-dg2-11: DMESG-FAIL (i915#12061) -> DMESG-WARN +1 other test dmesg-warnbat-arls-6: DMESG-FAIL (i915#12061) -> DMESG-WARN +1 other test dmesg-warn
> Known issuesHere are the changes found in Patchwork_148490v9 that come from known issues:
> IGT changesIssues hit *
> igt@fbdev@eof:bat-arlh-2: NOTRUN -> SKIP (i915#11345 / i915#11346) +3 other tests skip
> *
> igt@fbdev@info:bat-arlh-2: NOTRUN -> SKIP (i915#11346 / i915#1849)
> *
> igt@gem_lmem_swapping@basic:bat-arlh-2: NOTRUN -> SKIP (i915#10213 / i915#11346 / i915#11671) +3 other tests skip
> *
> igt@gem_mmap@basic:bat-arlh-2: NOTRUN -> SKIP (i915#11343 / i915#11346)
> *
> igt@gem_render_tiled_blits@basic:bat-arlh-2: NOTRUN -> SKIP (i915#10197 / i915#10211 / i915#11346 / i915#11725)
> *
> igt@gem_tiled_blits@basic:bat-arlh-2: NOTRUN -> SKIP (i915#11346 / i915#12637) +4 other tests skip
> *
> igt@gem_tiled_pread_basic:bat-arlh-2: NOTRUN -> SKIP (i915#10206 / i915#11346 / i915#11724)
> *
> igt@i915_pm_rps@basic-api:bat-arlh-2: NOTRUN -> SKIP (i915#10209 / i915#11346 / i915#11681)
> *
> igt@i915_selftest@live:bat-arlh-2: NOTRUN -> ABORT (i915#13723) +1 other test abort
> *
> igt@intel_hwmon@hwmon-read:bat-arlh-2: NOTRUN -> SKIP (i915#11346 / i915#11680 / i915#7707) +1 other test skip
> *
> igt@kms_addfb_basic@addfb25-y-tiled-small-legacy:bat-arlh-2: NOTRUN -> SKIP (i915#10200 / i915#11346 / i915#11666 / i915#12203)
> *
> igt@kms_addfb_basic@basic-x-tiled-legacy:bat-arlh-2: NOTRUN -> SKIP (i915#10200 / i915#11346 / i915#11666) +8 other tests skip
> *
> igt@kms_hdmi_inject@inject-audio:bat-arls-6: PASS -> FAIL (i915#13930)
> *
> igt@kms_psr@psr-primary-page-flip:bat-arlh-2: NOTRUN -> SKIP (i915#11346) +32 other tests skip
> *
> igt@kms_setmode@basic-clone-single-crtc:bat-arlh-2: NOTRUN -> SKIP (i915#10208 / i915#11346 / i915#8809)
> *
> igt@prime_vgem@basic-fence-read:bat-arlh-2: NOTRUN -> SKIP (i915#10212 / i915#11346 / i915#11726)
> *
> igt@prime_vgem@basic-read:bat-arlh-2: NOTRUN -> SKIP (i915#10214 / i915#11346 / i915#11726)
> *
> igt@prime_vgem@basic-write:bat-arlh-2: NOTRUN -> SKIP (i915#10216 / i915#11346 / i915#11723)
> Possible fixes * igt@i915_selftest@live@workarounds:bat-mtlp-9: DMESG-FAIL (i915#12061) -> PASS
> Build changes * Linux: CI_DRM_16637 -> Patchwork_148490v9
> CI-20190529: 20190529
> CI_DRM_16637: bea2a0d35dc29d6ae8a4e44506af9b563f012211 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_8392: 8392
> Patchwork_148490v9: bea2a0d35dc29d6ae8a4e44506af9b563f012211 @ git://anongit.freedesktop.org/gfx-ci/linux
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-06-03 13:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 11:27 [PATCH v13 0/9] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jeff Layton
2025-06-03 11:27 ` [PATCH v13 1/9] ref_tracker: don't use %pK in pr_ostream() output Jeff Layton
2025-06-03 11:27 ` [PATCH v13 2/9] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-06-03 11:27 ` [PATCH v13 3/9] ref_tracker: have callers pass output function to pr_ostream() Jeff Layton
2025-06-03 11:27 ` [PATCH v13 4/9] ref_tracker: add a static classname string to each ref_tracker_dir Jeff Layton
2025-06-03 11:27 ` [PATCH v13 5/9] ref_tracker: allow pr_ostream() to print directly to a seq_file Jeff Layton
2025-06-03 11:27 ` [PATCH v13 6/9] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir Jeff Layton
2025-06-03 11:27 ` [PATCH v13 7/9] ref_tracker: add a way to create a symlink to the ref_tracker_dir debugfs file Jeff Layton
2025-06-03 11:27 ` [PATCH v13 8/9] net: add symlinks to ref_tracker_dir for netns Jeff Layton
2025-06-03 11:27 ` [PATCH v13 9/9] ref_tracker: eliminate the ref_tracker_dir name field Jeff Layton
2025-06-03 12:20 ` ✗ Fi.CI.CHECKPATCH: warning for ref_tracker: add ability to register a debugfs file for a ref_tracker_dir (rev9) Patchwork
2025-06-03 12:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-06-03 12:45 ` ✗ i915.CI.BAT: failure " Patchwork
2025-06-03 13:23 ` Jeff Layton [this message]
2025-06-04 2:29 ` [PATCH v13 0/9] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jakub Kicinski
2025-06-04 2:38 ` Andrew Morton
2025-06-04 12:32 ` Jeff Layton
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=fc99f9ee0495cbe4c989a774d002ae4afe761ea7.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.karas@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 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.