Bug 103450 - [BDW] dEQP-VK.synchronization.*read*_image*fence_fd are flaky
Summary: [BDW] dEQP-VK.synchronization.*read*_image*fence_fd are flaky
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-25 11:33 UTC by Samuel Iglesias Gonsálvez
Modified: 2019-09-18 19:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Samuel Iglesias Gonsálvez 2017-10-25 11:33:11 UTC
Device: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2)  (0x1616)
Mesa HEAD: 767ca5bdf1 (master)
VK-GL-CTS HEAD: ab6b0ac1824ce0b091830042110cf3b3ea17e895 (master)

Command:

$ ./deqp-vk -n dEQP-VK.synchronization.*read*_image*fence_fd

How to reproduce it:

I run these in my updated Fedora GNOME 26 installation on my BDW laptop. The easiest way to reproduce it is to run them in a terminal and lock/unlock my GNOME session. Any time I do that, some tests fail. If I don't, they succeed.

Another easy way is to just run one of them in an infinite loop and repeat the aforementioned steps:

$ while(true); do ./deqp-vk -n dEQP-VK.synchronization.*read*_image* | grep "Passed" | grep -v "1/1" ; done

Also it is possible to reproduce it when executing a full cts run with piglit with concurrency mode enabled using dylan's wip/deqp-group-at-a-time branch. In that case, usually one or two tests fail.

Notes:

* There are no GPU hangs or any other kind of error in dmesg.
* These patches from Jason https://patchwork.freedesktop.org/series/31771/ (already landed in mesa master) improved the situation a lot, however it is still possible to reproduce this bug.
* I was not able to reproduce it either on SKL or KBL.
Comment 1 GitLab Migration User 2019-09-18 19:48:30 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/832.


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.