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 92936] Tonga powerplay isssues
Date: Tue, 17 May 2016 10:41:31 +0000	[thread overview]
Message-ID: <bug-92936-502-JpVNIQSdMW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92936-502@http.bugs.freedesktop.org/>


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

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

--- Comment #20 from Andy Furniss <adf.lists@gmail.com> ---
Though UVD seems to work for normal samples upto 2160p now, with an extreme
test I can lock GPU using it with powerplay=1 on low/auto but not (so far) =0.

With this sample there is also a corruption issue even with powerplay=0.

The sample decodes perfectly every time at full speed (player) with powerplay=1
and clocks forced high.

Tested with mpv mainly, but kodi, mplayer, decoding to ram with ffmpeg, gst omx
or gst vaapi all give similar results. Similar = decoding to ram may avoid the
lock (which always happens with players) but will be corrupt on auto. It is
still possible to lock decoding to ram.

Historically with a "normal" 2160p60 I have seen this rarely, but something
seems to have become more efficient so that 2160p60 that needed clocks forced
high will work on auto now.

The issue with this sample exists on older kernels as well as current.

The Sample is rather large and 4080x4096, it is "free" for testing AIUI as the
source images are from vqeg.

I thought I would upload it as I notice Leo Liu works on UVD and has a tonga.

It's 300 meg for 8.6 seconds! made to level 5.2 cbr (but is > 5.2 due to frame
size/num refs)

https://drive.google.com/file/d/0BxP5-S1t9VEEWGREeXlrQkZfaDQ/view?usp=sharing

Testing on a 1920x1080 screen with mpv -fs --hwdec=vdpau it will hang quickly
though GPU is still OK at this point. I could even run a gl Unigine bench  OK
(though mem clock is stuck low).

Trying to switch vt or quit X would hang display.

pkill -9 mpv won't instantly lock display (I use non compositing desktop), but
touching gl even glxinfo will then lock display.

Waiting 2 minutes before sysrq will give attached hung task trace.

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

[-- Attachment #1.2: Type: text/html, Size: 2742 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

  parent reply	other threads:[~2016-05-17 10:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 10:50 [Bug 92936] Tonga powerplay isssues bugzilla-daemon
2015-11-13 15:53 ` bugzilla-daemon
2015-11-13 20:10 ` bugzilla-daemon
2015-11-15 14:29 ` bugzilla-daemon
2015-12-10 12:06 ` bugzilla-daemon
2015-12-12 23:54 ` bugzilla-daemon
2015-12-19 12:16 ` bugzilla-daemon
2015-12-19 12:41 ` bugzilla-daemon
2016-01-25 21:34 ` bugzilla-daemon
2016-02-05  4:13 ` bugzilla-daemon
2016-02-05 10:41 ` bugzilla-daemon
2016-02-05 14:07 ` bugzilla-daemon
2016-02-05 22:24 ` bugzilla-daemon
2016-02-06 22:26 ` bugzilla-daemon
2016-02-08 22:56 ` bugzilla-daemon
2016-02-08 23:01 ` bugzilla-daemon
2016-02-08 23:01 ` bugzilla-daemon
2016-02-11 18:30 ` bugzilla-daemon
2016-02-11 18:36 ` bugzilla-daemon
2016-02-11 20:07 ` bugzilla-daemon
2016-05-17 10:08 ` bugzilla-daemon
2016-05-17 10:41 ` bugzilla-daemon [this message]
2016-05-17 10:42 ` bugzilla-daemon
2016-07-16 14:42 ` bugzilla-daemon
2016-11-07  5:12 ` bugzilla-daemon
2016-11-07 10:17 ` bugzilla-daemon
2018-11-30 17:27 ` 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-92936-502-JpVNIQSdMW@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