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: Tue, 21 May 2013 02:14:25 +0000 [thread overview]
Message-ID: <bug-63935-502-OJMel85EfK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63935-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 8365 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63935
--- Comment #35 from Austin Lund <austin.lund@gmail.com> ---
(In reply to comment #34)
>
> Can you tell us a bit about your system?
>
> 1) What kind of hardware are you using -- can you show us the error
> messages from you log files?
Machine is a MacBookpro 8,2.
lspci -v -s 01:00.0:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Whistler [Radeon HD 6600M/6700M/7600M Series] (prog-if 00 [VGA controller])
Subsystem: Apple Inc. MacBookPro8,2 [Core i7, 15", Late 2011]
Flags: bus master, fast devsel, latency 0, IRQ 49
Memory at 90000000 (64-bit, prefetchable) [size=256M]
Memory at b0800000 (64-bit, non-prefetchable) [size=128K]
I/O ports at 2000 [size=256]
Expansion ROM at b0820000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon
Kernel modules: radeon
Abridged log output:
May 21 10:21:12 lund-macbookpro kernel: ACPI: Video Device [GFX0] (multi-head:
yes rom: no post: no)
May 21 10:21:12 lund-macbookpro kernel: input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/LNXVIDEO:00/input/input9
May 21 10:21:12 lund-macbookpro kernel: ACPI: Video Device [IGPU] (multi-head:
yes rom: no post: no)
May 21 10:21:12 lund-macbookpro kernel: input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input10
May 21 10:21:12 lund-macbookpro kernel: EXT4-fs (sda5): mounted filesystem with
ordered data mode. Opts: (null)
May 21 10:21:12 lund-macbookpro kernel: [drm] Initialized i915 1.6.0 20080730
for 0000:00:02.0 on minor 0
May 21 10:21:12 lund-macbookpro kernel: snd_hda_intel 0000:00:1b.0: enabling
device (0000 -> 0002)
May 21 10:21:12 lund-macbookpro kernel: [drm] initializing kernel modesetting
(TURKS 0x1002:0x6741 0x106B:0x00E2).
May 21 10:21:12 lund-macbookpro kernel: snd_hda_intel 0000:00:1b.0: irq 48 for
MSI/MSI-X
May 21 10:21:12 lund-macbookpro kernel: [drm] register mmio base: 0xB0800000
May 21 10:21:12 lund-macbookpro kernel: [drm] register mmio size: 131072
May 21 10:21:12 lund-macbookpro kernel: vga_switcheroo: enabled
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: Invalid ROM
contents
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: Invalid ROM
contents
May 21 10:21:12 lund-macbookpro kernel: ATOM BIOS: Apple
May 21 10:21:12 lund-macbookpro kernel: [drm] GPU not posted. posting now...
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: VRAM: 1024M
0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: GTT: 512M
0x0000000040000000 - 0x000000005FFFFFFF
May 21 10:21:12 lund-macbookpro kernel: [drm] Detected VRAM RAM=1024M, BAR=256M
May 21 10:21:12 lund-macbookpro kernel: [drm] RAM width 128bits DDR
May 21 10:21:12 lund-macbookpro kernel: [TTM] Zone kernel: Available graphics
memory: 4053880 kiB
May 21 10:21:12 lund-macbookpro kernel: [TTM] Zone dma32: Available graphics
memory: 2097152 kiB
May 21 10:21:12 lund-macbookpro kernel: [TTM] Initializing pool allocator
May 21 10:21:12 lund-macbookpro kernel: [TTM] Initializing DMA pool allocator
May 21 10:21:12 lund-macbookpro kernel: [drm] radeon: 1024M of VRAM memory
ready
May 21 10:21:12 lund-macbookpro kernel: [drm] radeon: 512M of GTT memory ready.
May 21 10:21:12 lund-macbookpro kernel: [drm] Supports vblank timestamp caching
Rev 1 (10.10.2010).
May 21 10:21:12 lund-macbookpro kernel: [drm] Driver supports precise vblank
timestamp query.
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: irq 49 for
MSI/MSI-X
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: radeon: using MSI.
May 21 10:21:12 lund-macbookpro kernel: [drm] radeon: irq initialized.
May 21 10:21:12 lund-macbookpro kernel: [drm] GART: num cpu pages 131072, num
gpu pages 131072
May 21 10:21:12 lund-macbookpro kernel: [drm] probing gen 2 caps for device
8086:101 = 2212c82/0
May 21 10:21:12 lund-macbookpro kernel: [drm] PCIE gen 2 link speeds already
enabled
May 21 10:21:12 lund-macbookpro kernel: [drm] Loading TURKS Microcode
May 21 10:21:12 lund-macbookpro kernel: [drm] PCIE GART of 512M enabled (table
at 0x0000000000273000).
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: WB enabled
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: fence driver on
ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88025f667c00
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: fence driver on
ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88025f667c0c
May 21 10:21:12 lund-macbookpro kernel: radeon 0000:01:00.0: fence driver on
ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc9001c6b2118
May 21 10:21:12 lund-macbookpro kernel: input: HDA Intel PCH SPDIF In as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input12
May 21 10:21:12 lund-macbookpro kernel: input: HDA Intel PCH Headphone as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input13
May 21 10:21:12 lund-macbookpro kernel: input: HDA Intel PCH Line as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
May 21 10:21:12 lund-macbookpro kernel: [drm] ring test on 0 succeeded in 2
usecs
May 21 10:21:12 lund-macbookpro kernel: [drm] ring test on 3 succeeded in 1
usecs
May 21 10:21:13 lund-macbookpro kernel: [drm] Enabling RC6 states: RC6 on, RC6p
off, RC6pp off
May 21 10:21:13 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:14 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:16 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:17 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:18 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:19 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:20 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:21 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:22 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:23 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, trying to reset the VCPU!!!
May 21 10:21:23 lund-macbookpro kernel: [drm:r600_uvd_init] *ERROR* UVD not
responding, giving up!!!
May 21 10:21:23 lund-macbookpro kernel: [drm:evergreen_startup] *ERROR* radeon:
error initializing UVD (-1).
May 21 10:21:23 lund-macbookpro kernel: [drm] ib test on ring 0 succeeded in 0
usecs
May 21 10:21:23 lund-macbookpro kernel: [drm] ib test on ring 3 succeeded in 0
usecs
May 21 10:21:23 lund-macbookpro kernel: [drm] radeon atom DIG backlight
initialized
> 2) Are you using the necessary firmware for your system to allow this new
> support to work? (Most distributions haven't packaged it yet, so most of us
> have to download the new firmware directly; see comment 2.)
$ md5sum TURKS*
158f8e21ccf228ef063888c4f637fbf0 TURKS_mc.bin
8012e24b187c6b1ba17fa48691c3b048 TURKS_me.bin
25f26ba407a9bb13528b903c617209c8 TURKS_pfp.bin
> 3) Is your system built around a newer EFI motherboard, or do have a
> traditional non-EFI BIOS?
Apple's EFI. There is a BIOS compatibility mode, but I'm unable to do gpu
switching in that mode.
>
> There may still be some question of whether us users are doings something
> wrong -- although I personally have 2 systems that initialize UVD correctly
> and only 1 (EFI) system giving me trouble -- but if you have the firmware
> which enables this new UVD support, then maybe you could offer to do some
> register dumps if Christian or one of the other developers thinks it would
> be helpful to them?
Would this be the same as others have done above?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 9480 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-21 2:14 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 [this message]
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-OJMel85EfK@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).