All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65095] New: BARTS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Date: Tue, 28 May 2013 20:32:20 +0000	[thread overview]
Message-ID: <bug-65095-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 65095
          Assignee: dri-devel@lists.freedesktop.org
           Summary: BARTS [drm:r600_uvd_init] *ERROR* UVD not responding,
                    trying to reset the VCPU!!!
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: spamjunkeater@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

UVD is not working on BARTS (HD6850) with Linux 3.10-rc2

I got
[drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
errors on log.

I believe it's same issue with bug ID 63935 (
https://bugs.freedesktop.org/show_bug.cgi?id=63935 )

Thanks.

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

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

             reply	other threads:[~2013-05-28 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 20:32 bugzilla-daemon [this message]
2013-05-28 23:11 ` [Bug 65095] BARTS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! 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-65095-502@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 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.