[Bug 96767] ThinkPad T450: RetroArch refuses to go back into windowed mode after fullscreen
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Oct 12 20:40:10 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=96767
--- Comment #38 from Diego Viola <diego.viola at gmail.com> ---
(In reply to Chris Wilson from comment #37)
> (In reply to Diego Viola from comment #34)
> > Is this patch no longer relevant for this problem?
> >
> > https://bugs.freedesktop.org/attachment.cgi?id=121524
>
> We fixed that bug in Xorg.
>
> commit e43abdce964f5ed9689cf908af8c305b39a5dd36
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date: Wed Feb 3 09:54:46 2016 +0000
>
> dri2: Unblock Clients on Drawable release
>
> If the Window is destroyed by another client, such as the window
> manager, the original client may be blocked by DRI2 awaiting a vblank
> event. When this happens, DRI2DrawableGone forgets to unblock that
> client and so the wait never completes.
>
> Note Present/xshmfence is also suspectible to this race.
>
> Testcase: dri2-race/manager
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> Cc: Ville Syrjälä <ville.syrjala at linux.intel.com>
> Reviewed-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
Yes, I remember now. I still think xf86-video-intel+sna+dri2 shouldn't give
different results than modesetting+glamor+dri2 for this use case, although I
still get this bug even with Linux 4.8.1 and I've been bisecting from Linux 4.0
and up.
That said, I realize you are busy and I'd hate to distract you with this. This
seems like the last bug that I know of when it comes to RetroArch on Intel and
I'd love for this to be fixed.
Thanks for all of your help so far.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161012/c797dfbf/attachment.html>
More information about the intel-gfx-bugs
mailing list