Bug 22003 - Can full screen Xv using vsync refresh live happily with KMS?
Summary: Can full screen Xv using vsync refresh live happily with KMS?
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Jesse Barnes
QA Contact: Xorg Project Team
Keywords: NEEDINFO
Depends on:
Reported: 2009-05-30 06:55 UTC by Andy Burns
Modified: 2009-07-08 13:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Andy Burns 2009-05-30 06:55:00 UTC
Running rawhide just prior to Fefora 11 release, on G35 chipset I (and apparently others) noticed that full screen video froze X, but only if KMS was in use, everything was fine when booting with "nomodeset" on the kernel command line.


I notice that rawhide yesterday added a patch to disable vsync refresh for the intel driver 


The patch does stop X from freezing even with KMS, but video playback tearing is back which was only fixed in 2.7 itself.

Is there a better fix for this issue?
Comment 1 Jesse Barnes 2009-06-09 17:02:58 UTC
Yes, there have been several vblank sync related fixes and patches in git master recently, any chance you could try the git version?
Comment 2 Andy Burns 2009-06-10 14:05:00 UTC
I grabbed a tarball of master (10-JUN-2009 22:00) and tried to rebuild from the fedora SRPM using xf86-video-intel-master.tar.bz2 instead of xf86-video-intel-2.7.0.tar.bz2, with the relevant patches commented out of the .spec file

However I ran into a requirement for a newer libdrm than provided with Fedora 11, so I think I'll wait until a newer package turns up in Fedora updates-testing.
Comment 3 Jesse Barnes 2009-06-23 18:24:35 UTC
Any news here?
Comment 4 Jesse Barnes 2009-07-08 13:09:33 UTC
This should be fixed now:

commit 128c1c3b7d57b157604788f82bf9fd389839068f
Author: Carl Worth <cworth@cworth.org>
Date:   Wed Apr 29 14:43:56 2009 -0700

    Use libdrm to lookup pipe for tear-free sync of XV

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.