dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91322] Usage of 'gallium' vaapi driver crashes radeon with inability to reset itself and scary pictures as if card has burned out
Date: Tue, 14 Jul 2015 16:26:10 +0000	[thread overview]
Message-ID: <bug-91322-502-KjHXXW5jKy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91322-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Sergey Kondakov <virtuousfox@gmail.com> ---
Ah, and I don't know if its normal or not and pertaining to that issue or not
(maybe that confuses something else in the driver). But I can't seem to get
vsync working. Earlier I used "EXAVsync" and that was that. But now even it
doesn't help and I'm getting stuff like:
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
20074 frames in 5.0 seconds = 4014.652 FPS

Doesn't work under both EXA and glamor. Don't quite know when it changed. 
It does work however with bleeding edge X stack + mesa 10.7~git and "TearFree"
option but with it
1) clock speed and voltage are always on maximum
2) mpv/bomi are slowly desynchronizing audio and video

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-07-14 16:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  6:23 [Bug 91322] Usage of 'gallium' vaapi driver crashes radeon with inability to reset itself and scary pictures as if card has burned out bugzilla-daemon
2015-07-13 14:01 ` bugzilla-daemon
2015-07-14 16:01 ` bugzilla-daemon
2015-07-14 16:02 ` bugzilla-daemon
2015-07-14 16:03 ` bugzilla-daemon
2015-07-14 16:04 ` bugzilla-daemon
2015-07-14 16:05 ` bugzilla-daemon
2015-07-14 16:05 ` bugzilla-daemon
2015-07-14 16:08 ` bugzilla-daemon
2015-07-14 16:26 ` bugzilla-daemon [this message]
2015-07-14 16:45 ` bugzilla-daemon
2015-07-14 17:01 ` bugzilla-daemon
2019-09-18 19:19 ` bugzilla-daemon

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-91322-502-KjHXXW5jKy@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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