All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63935] New: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Date: Fri, 26 Apr 2013 00:07:24 +0000	[thread overview]
Message-ID: <bug-63935-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 63935
          Assignee: dri-devel@lists.freedesktop.org
           Summary: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding,
                    trying to reset the VCPU!!!
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: ben@b1c1l1.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: DRI CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 78493
  --> https://bugs.freedesktop.org/attachment.cgi?id=78493&action=edit
Longer dmesg output (drm.debug=0xe)

Using the code from drm-next-3.10-2 with linux-3.9-rc8, UVD does not initialize
on my TURKS chip in a MacBookPro8,2.

[    2.610025] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[    2.610055] [drm] register mmio base: 0xB0800000
[    2.610058] [drm] register mmio size: 131072
[    2.610092] radeon 0000:01:00.0: Invalid ROM contents
[    2.610128] radeon 0000:01:00.0: Invalid ROM contents
[    2.610149] ATOM BIOS: Apple
[    2.610225] [drm] GPU not posted. posting now...
[    2.627463] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 -
0x000000003FFFFFFF (1024M used)
[    2.627469] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 -
0x000000005FFFFFFF
[    2.632776] [drm] Detected VRAM RAM=1024M, BAR=256M
[    2.632783] [drm] RAM width 128bits DDR
[    2.632839] [TTM] Zone  kernel: Available graphics memory: 4042554 kiB
[    2.632842] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    2.632845] [TTM] Initializing pool allocator
[    2.632851] [TTM] Initializing DMA pool allocator
[    2.632886] [drm] radeon: 1024M of VRAM memory ready
[    2.632889] [drm] radeon: 512M of GTT memory ready.
[    2.632910] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    2.632913] [drm] Driver supports precise vblank timestamp query.
[    2.632962] radeon 0000:01:00.0: irq 45 for MSI/MSI-X
[    2.632973] radeon 0000:01:00.0: radeon: using MSI.
[    2.633008] [drm] radeon: irq initialized.
[    2.635037] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    2.635477] [drm] probing gen 2 caps for device 8086:101 = 2212c82/0
[    2.635484] [drm] PCIE gen 2 link speeds already enabled
[    2.635532] [drm] Loading TURKS Microcode
[    2.638103] [drm] PCIE GART of 512M enabled (table at 0x0000000000273000).
[    2.638226] radeon 0000:01:00.0: WB enabled
[    2.638231] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff880265785c00
[    2.638236] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff880265785c0c
[    2.638540] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc9000b932118
[    2.655105] [drm] ring test on 0 succeeded in 3 usecs
[    2.655172] [drm] ring test on 3 succeeded in 0 usecs
[    2.774845] ACPI: Deprecated procfs I/F for battery is loaded, please retry
with CONFIG_ACPI_PROCFS_POWER cleared
[    2.774856] ACPI: Battery Slot [BAT0] (battery present)
[    3.532304] tsc: Refined TSC clocksource calibration: 2200.015 MHz
[    3.532310] Switching to clocksource tsc
[    3.679502] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    4.698818] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    5.718146] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    6.737460] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    7.756774] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    8.776088] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    9.795419] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   10.814734] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   11.834049] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   12.853380] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   12.873372] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[   12.873377] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).

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

[-- Attachment #1.2: Type: text/html, Size: 5897 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-04-26  0:07 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  0:07 bugzilla-daemon [this message]
2013-04-26  0:12 ` [Bug 63935] TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.