All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86181] New: Timeout setting UVD clocks
Date: Mon, 13 Oct 2014 20:00:58 +0000	[thread overview]
Message-ID: <bug-86181-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=86181

            Bug ID: 86181
           Summary: Timeout setting UVD clocks
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.16.3-2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: sterfield@gmail.com
        Regression: No

Created attachment 153551
  --> https://bugzilla.kernel.org/attachment.cgi?id=153551&action=edit
full dmesg

Hi,

I've bought recently a MSI R7 265 (lspci attached), and use it in build under
Debian testing.

I've tried to configure it in order to have H264 hardware decoding, but UVD
failed at boot time (dmesg attached).

I've tried to boot with dpm=0, the problem is still here.

As one user had problem with maybe overheating
(https://bugzilla.kernel.org/show_bug.cgi?id=60858), I changed the thermal
paste on my graphic card, but the problem persists.

I've dumped some registers, as it seems to be interesting :

root@steambox:~# radeontool regmatch 0x0718
0x0718  0x00000023 (35)
root@steambox:~# radeontool regmatch 0x071c
0x071c  0xc080001c (-1065353188)
root@steambox:~# radeontool regmatch 0x0720
0x0720  0x3168680e (828925966)

Thanks for your help !

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

             reply	other threads:[~2014-10-13 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 20:00 bugzilla-daemon [this message]
2014-10-13 20:01 ` [Bug 86181] Timeout setting UVD clocks 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-86181-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.