[Bug 91066] New: problems with tearfree fullscreen video on secondary HDMI1 screen
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jun 23 00:52:55 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=91066
Bug ID: 91066
Summary: problems with tearfree fullscreen video on secondary
HDMI1 screen
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/intel
Assignee: chris at chris-wilson.co.uk
Reporter: kevmitch at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Created attachment 116665
--> https://bugs.freedesktop.org/attachment.cgi?id=116665&action=edit
xorg.0.log after triggeing BadDrawable errors
As originally described in Bug 91036.
My system is:
Mobile Ivy Bridge
Debian sid
xf86-video-intel=master(87b5ca2)
linux=4.0.5 or drm_intel master(be39a7e) (tried both)
xserver-xorg-core=2:1.17.1-2
xserver-xorg=1:7.7+9
mpv=git master(09eaaf3)
Running with sna acceleration and tearfree option on.
Dual screen desktop set up with
xrandr --output LVDS1 --mode 1920x1080 --rate 60 --output HDMI1 --mode
1920x1080 --rate 23.98 --set "Broadcast RGB" "Full" --right-of LVDS1
Play a 23.98 fps clip with mpv. Default configuration. Opengl output, no
hardware decoding
mpv --no-config --vo=opengl 1920x1080-23.80fps.mkv
Works fine until I go full screen on HDMI1. Then the image freezes or goes
black and I often (though not alwasy) get a ton of
[vo/opengl/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
in the terminal in which mpv is executing.
This is accompanied by a bunch of
[ 817.135] (EE) intel(0): [DRI2] DRI2SwapBuffers: drawable has no back or
front?
in Xorg.0.log (attached)
If I match the refresh rate
xrandr --output LVDS1 --mode 1920x1080 --rate 60 --output HDMI1 --mode
1920x1080 --rate 60 --set "Broadcast RGB" "Full" --right-of LVDS1
I get, but old frames often get displayed resulting in jerky back and forth
effect.
I don't see any of these problems with uxa acceleration.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150623/1203e2af/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list