From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [01/25] dma-buf: add dma_resv_for_each_fence_unlocked v5
Date: Fri, 24 Sep 2021 11:08:42 +0100 [thread overview]
Message-ID: <28208650-7873-54b8-7da5-29e6cf12b01c@linux.intel.com> (raw)
In-Reply-To: <636b43d9-65e1-7b86-8589-745c83bf9734@gmail.com>
On 24/09/2021 10:13, Christian König wrote:
>
>
> Am 24.09.21 um 11:11 schrieb Tvrtko Ursulin:
>>
>> On 23/09/2021 14:05, Patchwork wrote:
>>
>> [snip]
>>
>>> *
>>>
>>> igt@gem_busy@busy@all:
>>>
>>> o fi-apl-guc: PASS
>>> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10630/fi-apl-guc/igt@gem_busy@busy@all.html>
>>>
>>> -> FAIL
>>> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21144/fi-apl-guc/igt@gem_busy@busy@all.html>
>>>
>>> +2 similar issues
>>
>> All seem to be the same failure:
>>
>> (gem_busy:874) igt_dummyload-CRITICAL: Test assertion failure function
>> igt_spin_factory, file ../lib/igt_dummyload.c:490:
>> (gem_busy:874) igt_dummyload-CRITICAL: Failed assertion:
>> gem_bo_busy(fd, spin->handle)
>>
>> Which is saying spinner which was just submitted is not immediately
>> reported as busy. And that sounds impossible. Must be a pretty basic
>> bug somewhere which I don't immediately see. Like unlocked iterator
>> failing to walk the fences or something.
>
> I was just to write a mail to you about this since I'm currently
> scratching my head what exactly goes wrong here.
>
> Is there an igt test which uses only vgem and currently fails which I
> could also run on AMD hardware?
Not that I am aware of but you could add debug and use trybot?
However, is the bug perhaps in "all fences" mode is there is no
exclusive fence? First iteration returns NULL and for loop aborts before
looking at the shared fences.
Regards,
Tvrtko
prev parent reply other threads:[~2021-09-24 10:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 7:55 [Intel-gfx] [PATCH 01/25] dma-buf: add dma_resv_for_each_fence_unlocked v5 Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 02/25] dma-buf: add dma_resv_for_each_fence Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 03/25] dma-buf: use new iterator in dma_resv_copy_fences Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 04/25] dma-buf: use new iterator in dma_resv_get_fences v3 Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 05/25] dma-buf: use new iterator in dma_resv_wait_timeout Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 06/25] dma-buf: use new iterator in dma_resv_test_signaled Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 07/25] drm/ttm: use the new iterator in ttm_bo_flush_all_fences Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 08/25] drm/amdgpu: use the new iterator in amdgpu_sync_resv Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 09/25] drm/amdgpu: use new iterator in amdgpu_ttm_bo_eviction_valuable Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 10/25] drm/amdgpu: use new iterator in amdgpu_vm_prt_fini Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 11/25] drm/msm: use new iterator in msm_gem_describe Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 12/25] drm/radeon: use new iterator in radeon_sync_resv Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 13/25] drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2 Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 14/25] drm/i915: use the new iterator in i915_gem_busy_ioctl v2 Christian König
2021-09-24 9:08 ` Tvrtko Ursulin
2021-09-23 7:55 ` [Intel-gfx] [PATCH 15/25] drm/i915: use the new iterator in i915_sw_fence_await_reservation v3 Christian König
2021-09-23 7:55 ` [Intel-gfx] [PATCH 16/25] drm/i915: use the new iterator in i915_request_await_object v2 Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 17/25] drm/i915: use new iterator in i915_gem_object_wait_reservation Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 18/25] drm/i915: use new iterator in i915_gem_object_wait_priority Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 19/25] drm/i915: use new cursor in intel_prepare_plane_fb Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 20/25] drm: use new iterator in drm_gem_fence_array_add_implicit v3 Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 21/25] drm: use new iterator in drm_gem_plane_helper_prepare_fb Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 22/25] drm/nouveau: use the new iterator in nouveau_fence_sync Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 23/25] drm/nouveau: use the new interator in nv50_wndw_prepare_fb Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 24/25] drm/etnaviv: use new iterator in etnaviv_gem_describe Christian König
2021-09-23 7:56 ` [Intel-gfx] [PATCH 25/25] drm/etnaviv: replace dma_resv_get_excl_unlocked Christian König
2021-09-23 12:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/25] dma-buf: add dma_resv_for_each_fence_unlocked v5 Patchwork
2021-09-23 12:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-09-23 13:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-09-24 9:11 ` Tvrtko Ursulin
2021-09-24 9:13 ` Christian König
2021-09-24 10:08 ` Tvrtko Ursulin [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=28208650-7873-54b8-7da5-29e6cf12b01c@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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