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: Fri, 17 May 2013 10:42:38 +0000 [thread overview]
Message-ID: <bug-63935-502-WHXJVQQ4sF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63935-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2575 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63935
--- Comment #29 from Dave Witbrodt <dawitbro@sbcglobal.net> ---
(In reply to comment #28)
> Actually "radeonreg regs all" won't give you the UVD regs, cause it doesn't
> know about them yet. So could you guys give us a dump of the following regs,
> once with EFI and once in BIOS mode?
In comment 9 I mentioned that I did not see any BIOS settings that would allow
me to switch off EFI mode on my problematic SUMO2 machine. I will look again.
For now, this is the list of registers you requested:
# for reg in 0xef00 0xef04 0xef08 0xef0c 0xef10 0xef14 0xef18 0xef40 0xef44
0xef48 0xef4c 0xef50 0xef54 0xf400 0xf480 0xf498 0xf4a8 0xf4d4 0xf4d8 0xf4dc
0xf4e0 0xf4e4 0xf4e8 0xf4ec 0xf4f4 0xf500 0xf594 0xf598 0xf5b4 0xf5bC 0xf5dC
0xf5e4 0xf5e8 0xf5eC 0xf5f0 0xf5f4 0xf5f8 0xf660 0xf680 0xf684 0xf688 0xf68c
0xf690 0xF690 0xf694 0xF694 0xf698 0xf6a4 0xf6a8 0xf6bc 0xf6c0 0xf6c4 0xf6c8
0xf6cc 0xf6f4; do ./radeontool regmatch $reg; done
0xef00 0x00000000 (0)
0xef04 0x00000000 (0)
0xef08 0x00000080 (128)
0xef0c 0x00000000 (0)
0xef10 0x00000000 (0)
0xef14 0x00000000 (0)
0xef18 0x00000000 (0)
0xef40 0x00000000 (0)
0xef44 0x00000000 (0)
0xef48 0x04010040 (67174464)
0xef4c 0x02010002 (33619970)
0xef50 0x02010002 (33619970)
0xef54 0x02010002 (33619970)
0xf400 0x00000003 (3)
0xf480 0x00000000 (0)
0xf498 0x80090000 (-2146893824)
0xf4a8 0x00000000 (0)
0xf4d4 0x0100000d (16777229)
0xf4d8 0x00008000 (32768)
0xf4dc 0x00006600 (26112)
0xf4e0 0x0000e600 (58880)
0xf4e4 0x00020000 (131072)
0xf4e8 0x0002e600 (189952)
0xf4ec 0x00020000 (131072)
0xf4f4 0x00000030 (48)
0xf500 0x00000000 (0)
0xf594 0x00000000 (0)
0xf598 0x00302340 (3154752)
0xf5b4 0x00000000 (0)
0xf5bC 0x00000000 (0)
0xf5dC 0x00000000 (0)
0xf5e4 0x040c2040 (67903552)
0xf5e8 0x00000000 (0)
0xf5eC 0x040c2040 (67903552)
0xf5f0 0x00000000 (0)
0xf5f4 0x00000088 (136)
0xf5f8 0x00000000 (0)
0xf660 0x00000200 (512)
0xf680 0x00000000 (0)
0xf684 0x00000000 (0)
0xf688 0x00000000 (0)
0xf68c 0x00000000 (0)
0xf690 0x00000000 (0)
0xF690 0x00000000 (0)
0xf694 0x00000000 (0)
0xF694 0x00000000 (0)
0xf698 0x00000000 (0)
0xf6a4 0x01000101 (16777473)
0xf6a8 0x00000000 (0)
0xf6bc 0x00000000 (0)
0xf6c0 0x00000000 (0)
0xf6c4 0x02000000 (33554432)
0xf6c8 0x02000000 (33554432)
0xf6cc 0x02000000 (33554432)
0xf6f4 0x00000000 (0)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3563 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-05-17 10:42 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 [this message]
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
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-WHXJVQQ4sF@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