From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106519] Is it normal that the 4K video on the Vega 56 GPU played with loud turbine noise, 200% load of the desktop Core i7 CPU and at the same time playable with jerks and dropping frames?
Date: Wed, 16 May 2018 15:59:24 +0000 [thread overview]
Message-ID: <bug-106519-502-hJAr6RWaEW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106519-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1630 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106519
--- Comment #11 from mikhail.v.gavrilov@gmail.com ---
(In reply to Christian König from comment #10)
> Please provide the output of vainfo.
$ vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Mesa Gallium driver 18.1.0-rc3 for Radeon RX Vega
(VEGA10, DRM 3.25.0, 4.17.0-0.rc4.git2.1.fc29.x86_64, LLVM 6.0.0)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2746 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-16 15:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 20:59 [Bug 106519] Is it normal that the 4K video on the Vega 56 GPU played with loud turbine noise, 200% load of the desktop Core i7 CPU and at the same time playable with jerks and dropping frames? bugzilla-daemon
2018-05-14 21:00 ` bugzilla-daemon
2018-05-14 21:00 ` bugzilla-daemon
2018-05-15 7:09 ` bugzilla-daemon
2018-05-15 19:33 ` bugzilla-daemon
2018-05-15 20:02 ` bugzilla-daemon
2018-05-15 21:12 ` bugzilla-daemon
2018-05-15 21:14 ` bugzilla-daemon
2018-05-15 21:17 ` bugzilla-daemon
2018-05-15 21:19 ` bugzilla-daemon
2018-05-16 8:05 ` bugzilla-daemon
2018-05-16 15:59 ` bugzilla-daemon [this message]
2018-05-23 10:56 ` bugzilla-daemon
2018-05-24 3:44 ` bugzilla-daemon
2018-05-24 3:45 ` bugzilla-daemon
2018-05-24 3:49 ` bugzilla-daemon
2018-05-24 4:31 ` bugzilla-daemon
2018-05-24 17:06 ` bugzilla-daemon
2018-05-24 17:16 ` bugzilla-daemon
2018-05-24 17:24 ` bugzilla-daemon
2018-05-24 21:21 ` bugzilla-daemon
2018-08-05 13:14 ` bugzilla-daemon
2018-08-06 9:21 ` bugzilla-daemon
2018-08-06 15:57 ` bugzilla-daemon
2018-08-14 11:10 ` bugzilla-daemon
2018-08-14 11:13 ` bugzilla-daemon
2018-08-16 15:18 ` bugzilla-daemon
2018-10-09 19:04 ` 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-106519-502-hJAr6RWaEW@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;
as well as URLs for NNTP newsgroup(s).