Bug 108454 - [CI][SHARDS] igt@* - fail - Failed assertion: gem_bo_busy(fd, spin->handle)
Summary: [CI][SHARDS] igt@* - fail - Failed assertion: gem_bo_busy(fd, spin->handle)
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Andi
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-16 12:42 UTC by Martin Peres
Modified: 2019-02-19 14:11 UTC (History)
1 user (show)

See Also:
i915 platform: GLK
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2018-10-16 12:42:52 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4677/shard-glk3/igt@gem_exec_reloc@basic-gtt-read-active.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4677/shard-glk3/igt@kms_busy@extended-modeset-hang-newfb-render-c.html

Starting subtest: extended-modeset-hang-newfb-render-C
(kms_busy:15876) igt_dummyload-CRITICAL: Test assertion failure function igt_spin_batch_factory, file ../lib/igt_dummyload.c:319:
(kms_busy:15876) igt_dummyload-CRITICAL: Failed assertion: gem_bo_busy(fd, spin->handle)
Subtest extended-modeset-hang-newfb-render-C failed.
Comment 1 Chris Wilson 2018-10-16 13:10:25 UTC
No clue. Submission failed (or at least completely instantly which is against the concept of the spin batch) and nothing out of the ordinary was reported during, before, or after.
Comment 2 Francesco Balestrieri 2019-01-09 07:47:56 UTC
Happened twice two months ago, then never again. Closing.
Comment 3 Lakshmi 2019-02-19 08:49:15 UTC
Last seen IGT_4677_full (4 months / 2423 runs ago).
Closing this bug.
Comment 4 CI Bug Log 2019-02-19 14:11:23 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.