Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98030] Stuttering video playback in totem after update to 1.19-rc1
Date: Thu, 13 Oct 2016 21:39:49 +0000	[thread overview]
Message-ID: <bug-98030-8800-CD6Kkfx196@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98030-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1375 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98030

--- Comment #3 from Mario Kleiner <mario.kleiner-TdbV1Z3I5XE0NhjG498hmQ@public.gmane.org> ---
Ok, i think this is related: On 1.19-rc1 (current git master) under DRI2,
windowed OpenGL apps like glxgears get stuck unless i press keys on the
keyboard or move the mouse to create input events. KDE Plasma 5, being OpenGL
driven afaik, has the same problem.

If otoh i run applications which use fullscreen kms page-flipped windows, e.g.,
Gnome shell, or regular fullscreen GL apps, they work fine under DRI2. If i use
DRI3/Present everything works fine. This both with a server built to use the
new input-threads and also built without input-threads. This happens at least
on nouveau-ddx and ati/amdgpu-ddx.

I just retested glxgears, my own app and totem under gdb, and without me
providing mouse/keyboard input, they all get stuck in the
DRI2GetBuffersWithFormat request to the X-Server, waiting for a reply. That
gets called when Mesa needs new renderbuffers for a new frame after a
swapbuffers request, e.g., when glxgears or totem calls glClear().

So far so bad. So something gets stuck in the servers dispatch loop, but
"external" input events from the kernel (evdev, kms-pageflip completion
events?) gets it unstuck?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2175 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2016-10-13 21:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 15:11 [Bug 98030] New: Stuttering video playback in totem after update to 1.19-rc1 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-98030-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-10-03 21:30   ` [Bug 98030] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-03 21:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-13 21:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-10-14  3:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-14  3:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-14  8:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-14  8:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-14  9:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-19  2:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98030-8800-CD6Kkfx196@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox