[Bug 104008] [BAT][CI] igt@* - fail - Failed assertion: poll(&pfd, 1, 0) == 1
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Apr 12 13:35:01 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=104008
Chris Wilson <chris at chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #15 from Chris Wilson <chris at chris-wilson.co.uk> ---
prime_vgem/basic-fence-flip timing loop was rewritten and should avoid this
problem
commit f43bb29c3e29143d8ad5fc70b82eccf5749d3958
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Thu Apr 4 08:01:04 2019 +0100
prime_vgem: Downgrade the severity of a single missed vblank on flipping
Not displaying the flip on the next vblank is bad, but not the end of
the world -- so long as that is only a temporary glitch. Give the vblank
a few more frames to complete, and warn instead of failing if it takes
more than one vblank interval to flip.
v2: Bump the warning to >1 missed flip, to spare us the noise.
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Reviewed-by: Daniel Vetter <daniel.vetter at ffwll.ch>
commit f539e21e934019f0196fee646f351b4e30a8c341
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Mon Apr 1 08:55:20 2019 +0100
prime_vgem: Replace nanosleep with igt_waitchildren_timeout
We want to use a child in order to detect an uninterruptable sleep (a
potential bug we might hit), but we can use igt_waitchildren_timeout()
to replace our risky self-signaling + nanosleep.
v2: Remove the now redundant signal() setup.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103182
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Reviewed-by: Daniel Vetter <daniel.vetter at ffwll.ch>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190412/754af21d/attachment.html>
More information about the intel-gfx-bugs
mailing list