Bug 13782 - xf86-video-intel 2.2.0: XV double buffering unsynchronized
Summary: xf86-video-intel 2.2.0: XV double buffering unsynchronized
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.3 (2007.09)
Hardware: Other All
: medium normal
Assignee: Wang Zhenyu
QA Contact: Xorg Project Team
URL: http://bugs.debian.org/cgi-bin/bugrep...
Keywords: NEEDINFO
Depends on:
Reported: 2007-12-22 05:31 UTC by Brice Goglin
Modified: 2008-02-29 15:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Brice Goglin 2007-12-22 05:31:16 UTC
Reported recently by Bastian Blank on the Debian BTS.

"Since the update to 2.2.0 of the intel driver I regulary got weird
breaks in the video output from mplayer via xvideo. One part of the
picture comes from a different input frame. Best seen in a fast moving

His config and log is available at the URL above. He's using a
945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)

Michel replied
> The intel driver's textured video Xv adaptor has always had this
> problem, regardless of EXA or XAA.
and told him to try the overlay adaptor but he got bug#13108 then.
Comment 1 Michael Fu 2008-01-03 22:25:40 UTC
Brice, 13108 was fixed now. would you please ask Bastian to try Michel's suggestions?
Comment 2 Jesse Barnes 2008-01-04 15:25:02 UTC
Yeah, if overlay works we can mark this one a duplicate; I think we already have a bug on sync to vblank vs. textured video.
Comment 3 Benjamin Close 2008-01-11 02:38:49 UTC
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 4 Michael Fu 2008-01-17 21:30:25 UTC
Brice, any response?
Comment 5 Brice Goglin 2008-01-17 23:19:43 UTC
No reply yet, I am pinging him again.
Comment 6 Michael Fu 2008-01-28 19:24:45 UTC
if still no response from the original bug reporter,we probably need to close this bug then...
Comment 7 Brice Goglin 2008-01-29 00:50:54 UTC
Bastian confirms that the crash is fixed. But, the output is broken. I am waiting for more information.
Comment 8 Brice Goglin 2008-01-30 14:39:51 UTC
Bastian added "git from today looks much better. Even the async problems in the
textured video are less problematic."
Comment 9 Michael Fu 2008-01-30 18:18:55 UTC
good. could we have Bastian added to the cc?
Comment 10 Michael Fu 2008-02-14 05:04:43 UTC
I'll mark this bug as fixed according to comment# 7 and 8. 

Brice, please ask Bastian to open a new bug here if he still have a broken display , using the repository tip. thanks.
Comment 11 Brice Goglin 2008-02-14 05:14:00 UTC
Which bug on "sync to vblank vs. textured video" was Jesse talking about in #2? Why don't you mark as a duplicate of it instead of marking as fixed?
Comment 12 Brice Goglin 2008-02-27 04:31:29 UTC
bug#11311 is probably similar but only talks about i965 while Bastian has this bug on i945. I am reopening to get a proper "fixed as duplicate". Thanks.
Comment 13 Michael Fu 2008-02-29 15:14:05 UTC
Brice, I marked this bug as "resolved" because from comment# 7 of this bug, you said Bastian said (:( ) "the crash was fixed, but the output is still broken". I didn't say the whole problem for him was resolved, and instead want him to open a new bug for his "output is broken" issue, as it's likely another bug. Jesse's comment in comment# 2 isn't the proof I used to close this bug.

Again, I still hope that Bastian could open a new bug himself for the "output is broken" issue. Besides, I do hope he can show up in our concersation. :)

Comment 14 Brice Goglin 2008-02-29 15:20:02 UTC
Well, Bastian's original bug is about sync to vblank vs. textured video. And this one isn't fixed. Only the crash using overlay is fixed. But, using the overlay is only a workaround. Is it that hard to find the duplicate that Jesse talked about in #2?
Comment 15 Michael Fu 2008-02-29 15:42:37 UTC
pinged Jesse, and wait for his response...

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.