From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63935] TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Date: Sun, 02 Jun 2013 10:20:28 +0000 [thread overview]
Message-ID: <bug-63935-502-ZAjGIXGqia@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63935-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 925 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63935
--- Comment #52 from zsolt barat <zsolt@softmonsters.com> ---
(In reply to comment #48)
> (In reply to comment #47)
> >
> > I can confirm that the patch works on boot, also on a mac 8,2 with drm-next
> > and patches, but fails on suspend resume. It reappears on resume.
> > Please reopen the bug.
>
> I have a MacbookPro8,2 and this doesn't happen to me. My pci ID for the
> radeon is 1002:6741 and subsystem 106b:00e2. Is it the same message in the
> dmesg log?
Hi, I have a slightly different PCI-ID for my ATI graphics card. According to
lspci -nn it's: 1002:6760
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI
Seymour [Radeon HD 6400M/7400M Series] [1002:6760]
According to dmesg:
[drm] initializing kernel modesetting (CAICOS 0x1002:0x6760 0x106B:0x00E1).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1932 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
next prev parent reply other threads:[~2013-06-02 10:20 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 0:07 [Bug 63935] New: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! bugzilla-daemon
2013-04-26 0:12 ` [Bug 63935] " bugzilla-daemon
2013-04-26 0:18 ` bugzilla-daemon
2013-04-26 1:10 ` bugzilla-daemon
2013-04-26 6:28 ` bugzilla-daemon
2013-04-26 6:29 ` bugzilla-daemon
2013-04-29 18:51 ` bugzilla-daemon
2013-05-04 18:01 ` bugzilla-daemon
2013-05-08 23:59 ` bugzilla-daemon
2013-05-09 14:44 ` bugzilla-daemon
2013-05-10 9:53 ` bugzilla-daemon
2013-05-10 11:46 ` bugzilla-daemon
2013-05-16 0:47 ` bugzilla-daemon
2013-05-16 12:43 ` bugzilla-daemon
2013-05-16 12:46 ` bugzilla-daemon
2013-05-16 13:09 ` bugzilla-daemon
2013-05-16 15:45 ` bugzilla-daemon
2013-05-16 19:06 ` bugzilla-daemon
2013-05-16 20:12 ` bugzilla-daemon
2013-05-16 20:25 ` bugzilla-daemon
2013-05-16 21:16 ` bugzilla-daemon
2013-05-16 21:17 ` bugzilla-daemon
2013-05-16 21:17 ` bugzilla-daemon
2013-05-16 21:18 ` bugzilla-daemon
2013-05-16 23:01 ` bugzilla-daemon
2013-05-17 0:03 ` bugzilla-daemon
2013-05-17 0:04 ` bugzilla-daemon
2013-05-17 0:05 ` bugzilla-daemon
2013-05-17 8:49 ` bugzilla-daemon
2013-05-17 10:42 ` bugzilla-daemon
2013-05-17 17:35 ` bugzilla-daemon
2013-05-17 17:35 ` bugzilla-daemon
2013-05-17 17:36 ` bugzilla-daemon
2013-05-21 0:24 ` bugzilla-daemon
2013-05-21 1:45 ` bugzilla-daemon
2013-05-21 2:14 ` bugzilla-daemon
2013-05-21 16:06 ` bugzilla-daemon
2013-05-22 15:06 ` bugzilla-daemon
2013-05-22 15:52 ` bugzilla-daemon
2013-05-22 16:13 ` bugzilla-daemon
2013-05-22 17:20 ` bugzilla-daemon
2013-05-23 8:16 ` bugzilla-daemon
2013-05-23 8:33 ` bugzilla-daemon
2013-05-23 15:44 ` bugzilla-daemon
2013-05-24 12:01 ` bugzilla-daemon
2013-05-25 0:01 ` bugzilla-daemon
2013-05-26 23:43 ` bugzilla-daemon
2013-05-27 21:34 ` bugzilla-daemon
2013-05-27 22:40 ` bugzilla-daemon
2013-05-28 1:38 ` bugzilla-daemon
2013-05-28 1:58 ` bugzilla-daemon
2013-05-28 8:11 ` bugzilla-daemon
2013-06-02 10:20 ` bugzilla-daemon [this message]
2013-06-03 1:40 ` bugzilla-daemon
2013-06-26 21:37 ` bugzilla-daemon
2013-06-29 18:49 ` bugzilla-daemon
2013-06-30 9:48 ` bugzilla-daemon
2013-07-14 12:12 ` bugzilla-daemon
2013-08-23 3:46 ` bugzilla-daemon
2013-08-23 3:50 ` 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-63935-502-ZAjGIXGqia@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).