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: Mon, 29 Apr 2013 18:51:40 +0000 [thread overview]
Message-ID: <bug-63935-502-mJRbLPw6Xo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63935-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 5182 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63935
--- Comment #6 from Dave Witbrodt <dawitbro@sbcglobal.net> ---
FWIW, I'm seeing this same firmware issue on a SUMO2 system:
[ 1.305718] [drm] Initialized drm 1.1.0 20060810
[ 1.305767] [drm] radeon kernel modesetting enabled.
[ 1.305964] [drm] initializing kernel modesetting (SUMO2 0x1002:0x9644
0x1849:0x9640).
[ 1.306030] [drm] register mmio base: 0xFEF00000
[ 1.306064] [drm] register mmio size: 262144
[ 1.306155] ATOM BIOS: General
[ 1.306231] radeon 0000:00:01.0: VRAM: 256M 0x0000000000000000 -
0x000000000FFFFFFF (256M used)
[ 1.306272] radeon 0000:00:01.0: GTT: 512M 0x0000000010000000 -
0x000000002FFFFFFF
[ 1.306315] mtrr: type mismatch for c0000000,10000000 old: write-back new:
write-combining
[ 1.306355] [drm] Detected VRAM RAM=256M, BAR=256M
[ 1.306389] [drm] RAM width 32bits DDR
[ 1.306520] [TTM] Zone kernel: Available graphics memory: 1885900 kiB
[ 1.306563] [TTM] Initializing pool allocator
[ 1.306601] [TTM] Initializing DMA pool allocator
[ 1.306659] [drm] radeon: 256M of VRAM memory ready
[ 1.306694] [drm] radeon: 512M of GTT memory ready.
[ 1.306730] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 1.306765] [drm] Driver supports precise vblank timestamp query.
[ 1.306839] radeon 0000:00:01.0: irq 41 for MSI/MSI-X
[ 1.306849] radeon 0000:00:01.0: radeon: using MSI.
[ 1.306901] [drm] radeon: irq initialized.
[ 1.307950] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 1.309023] [drm] Loading SUMO2 Microcode
[ 1.316957] [drm] PCIE GART of 512M enabled (table at 0x0000000000273000).
[ 1.317116] radeon 0000:00:01.0: WB enabled
[ 1.317148] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000010000c00 and cpu addr 0xffff88012a178c00
[ 1.317186] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000010000c0c and cpu addr 0xffff88012a178c0c
[ 1.317414] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc900106b2118
[ 1.334080] [drm] ring test on 0 succeeded in 1 usecs
[ 1.334176] [drm] ring test on 3 succeeded in 1 usecs
[ 2.281926] tsc: Refined TSC clocksource calibration: 2695.097 MHz
[ 2.376808] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 3.394476] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 4.412139] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 5.429805] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 6.447468] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 7.465130] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 8.482797] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 9.500460] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 10.518126] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 11.535793] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 11.555786] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[ 11.575783] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).
[ 11.576227] [drm] ib test on ring 0 succeeded in 0 usecs
[ 11.576294] [drm] ib test on ring 3 succeeded in 0 usecs
[ 11.577202] [drm] Radeon Display Connectors
[ 11.577236] [drm] Connector 0:
[ 11.577269] [drm] HDMI-A-1
[ 11.577302] [drm] HPD2
[ 11.577335] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c
0x644c
[ 11.578434] [drm] Encoders:
[ 11.578467] [drm] DFP1: INTERNAL_UNIPHY2
[ 11.578501] [drm] Connector 1:
[ 11.578533] [drm] VGA-1
[ 11.578566] [drm] HPD1
[ 11.578599] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c
0x643c
[ 11.578652] [drm] Encoders:
[ 11.578685] [drm] CRT1: INTERNAL_UNIPHY2
[ 11.578719] [drm] CRT1: NUTMEG
[ 11.595893] [drm] Internal thermal controller without fan control
[ 11.595949] [drm] radeon: power management initialized
[ 11.660512] [drm] fb mappable at 0xC0375000
[ 11.660542] [drm] vram apper at 0xC0000000
[ 11.660570] [drm] size 9216000
[ 11.660598] [drm] fb depth is 24
[ 11.660626] [drm] pitch is 7680
[ 11.660828] fbcon: radeondrmfb (fb0) is primary device
[ 11.738729] Console: switching to colour frame buffer device 240x75
[ 11.745079] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[ 11.745110] radeon 0000:00:01.0: registered panic notifier
[ 11.745140] [drm] Initialized radeon 2.33.0 20080528 for 0000:00:01.0 on
minor 0
This is on a machine I use as a file server, with no X Windows installed; on my
desktop machine (using Juniper), I have successfully built and run the same
kernel with the new JUNIPER_rlc.bin and CYPRESS_uvd.bin files (and the old
JUNIPER_me.bin and JUNIPER_pfp.bin files).
(Not trying to hijack this bug report; just throwing in some extra info that
seems related.) - DW
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6023 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-04-29 18:51 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 [this message]
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
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-mJRbLPw6Xo@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).