dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67187] New: Radeon HD6950: UVD not responding, trying to reset the VCPU
Date: Mon, 22 Jul 2013 19:18:54 +0000	[thread overview]
Message-ID: <bug-67187-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 67187
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Radeon HD6950: UVD not responding, trying to reset the
                    VCPU
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: h.judt@gmx.at
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 82837
  --> https://bugs.freedesktop.org/attachment.cgi?id=82837&action=edit
dmesg.out

When I thought suspend/resume was finally working, I found these error messages
in dmesg. See file attached, it's dmesg with multiple suspend/resume cycles.
Note I'm using tuxonice patches, but that shouldn't matter. If retesting with
vanilla is required, I can do this of course.

Note: I have the fix from bug #66425 applied.

Linux-3.10.1.

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

[-- Attachment #1.2: Type: text/html, Size: 2649 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-07-22 19:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 19:18 bugzilla-daemon [this message]
2013-07-23  8:46 ` [Bug 67187] Radeon HD6950: UVD not responding, trying to reset the VCPU bugzilla-daemon
2013-07-23  9:00 ` bugzilla-daemon
2013-07-23 18:01 ` bugzilla-daemon
2013-07-25  7:06 ` bugzilla-daemon
2013-07-30  8:20 ` bugzilla-daemon
2013-07-30  8:29 ` bugzilla-daemon
2013-07-30 17:43 ` bugzilla-daemon
2013-08-05  7:31 ` bugzilla-daemon
2013-08-05 10:02 ` bugzilla-daemon
2013-08-05 11:37 ` bugzilla-daemon
2013-08-05 13:20 ` bugzilla-daemon
2013-08-07 10:12 ` bugzilla-daemon
2013-08-08 22:30 ` bugzilla-daemon
2013-08-08 22:37 ` bugzilla-daemon
2013-08-08 22:41 ` bugzilla-daemon
2013-08-09 18:26 ` bugzilla-daemon
2013-08-19 21:14 ` bugzilla-daemon
2013-10-13 20:50 ` bugzilla-daemon
2013-10-14  8:05 ` 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-67187-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 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).