Bug 65270 - CAICOS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Summary: CAICOS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VC...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-02 18:48 UTC by Gerben Welter
Modified: 2013-06-06 07:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg from 3.8.10-rc4 (68.20 KB, text/plain)
2013-06-02 18:48 UTC, Gerben Welter
no flags Details

Description Gerben Welter 2013-06-02 18:48:39 UTC
Created attachment 80163 [details]
dmesg from 3.8.10-rc4

This is on a HP ProBook 6560b running Ubuntu 13.04 with the Xorg edgers PPA and the Ubuntu Mainline Kernel PPA, currenty at 3.8.10-rc4. Here's an excerpt from the lines stating the problem. The full dmesg is attached.

[    1.491745] [drm] Initialized drm 1.1.0 20060810
[    1.520286] [drm] radeon kernel modesetting enabled.
[    1.521516] [drm] initializing kernel modesetting (CAICOS 0x1002:0x6760 0x103C:0x161B).
[    1.521544] [drm] register mmio base: 0xD4300000
[    1.521546] [drm] register mmio size: 131072
[    1.523743] [drm] Detected VRAM RAM=512M, BAR=256M
[    1.523747] [drm] RAM width 64bits DDR
[    1.525789] [drm] radeon: 512M of VRAM memory ready
[    1.525791] [drm] radeon: 512M of GTT memory ready.
[    1.525805] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    1.525806] [drm] Driver supports precise vblank timestamp query.
[    1.525879] [drm] radeon: irq initialized.
[    1.527852] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    1.528327] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[    1.528404] [drm] Loading CAICOS Microcode
[    1.547532] [drm] PCIE GART of 512M enabled (table at 0x0000000000273000).
[    1.564737] [drm] ring test on 0 succeeded in 2 usecs
[    1.564802] [drm] ring test on 3 succeeded in 1 usecs
[    2.733072] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    3.746322] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    4.759572] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    5.772824] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    6.786074] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    7.799327] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    8.812576] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[    9.825827] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   10.839074] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   11.852325] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   11.872197] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[   11.872205] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1).
[   11.872491] [drm] ib test on ring 0 succeeded in 0 usecs
[   11.872539] [drm] ib test on ring 3 succeeded in 0 usecs
Comment 1 Alex Deucher 2013-06-03 13:37:50 UTC
Make sure you've installed the updated rlc and uvd microcode and that it is available to the driver during boot (in your initrd, etc.).  You can grab the latest ucode here:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git
or here:
http://people.freedesktop.org/~agd5f/radeon_ucode/
You need BTC_rlc.bin and SUMO_uvd.bin for UVD on your chip.
Comment 2 Alex Deucher 2013-06-03 13:47:59 UTC
Is this a hybrid laptop with multiple GPUs?
Comment 3 Gerben Welter 2013-06-03 14:17:37 UTC
(In reply to comment #2)
> Is this a hybrid laptop with multiple GPUs?

No, this laptop has just the Radeon GPU.
Comment 4 Gerben Welter 2013-06-03 14:21:56 UTC
(In reply to comment #1)
> Make sure you've installed the updated rlc and uvd microcode and that it is
> available to the driver during boot (in your initrd, etc.).  You can grab
> the latest ucode here:
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git
> or here:
> http://people.freedesktop.org/~agd5f/radeon_ucode/
> You need BTC_rlc.bin and SUMO_uvd.bin for UVD on your chip.

Yeah, I grabbed those already otherwise the update of the initrd starts complaining they are missing.
Comment 5 Christian König 2013-06-05 18:10:31 UTC
(In reply to comment #4)
> (In reply to comment #1)
> > Make sure you've installed the updated rlc and uvd microcode and that it is
> > available to the driver during boot (in your initrd, etc.).  You can grab
> > the latest ucode here:
> > http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git
> > or here:
> > http://people.freedesktop.org/~agd5f/radeon_ucode/
> > You need BTC_rlc.bin and SUMO_uvd.bin for UVD on your chip.
> 
> Yeah, I grabbed those already otherwise the update of the initrd starts
> complaining they are missing.

You not only need the new one the initrd updater is complaining about, you also need the new RLC firmware. Otherwise the hardware would produce exactly the error you are describing.

Please double check that you got the right versions of the firmware files.
Comment 6 Gerben Welter 2013-06-05 19:11:25 UTC
(In reply to comment #5)
> You not only need the new one the initrd updater is complaining about, you
> also need the new RLC firmware. Otherwise the hardware would produce exactly
> the error you are describing.
> 
> Please double check that you got the right versions of the firmware files.

Ahh, I hadn't noticed the already present files had been updated. I redownloaded all the *.bin files and updated the initrd. UVD now intializes. Thank you for your help.
Comment 7 Gerben Welter 2013-06-05 19:12:39 UTC
Closing as invalid because of PEBCAK error.
Comment 8 Christian König 2013-06-06 07:22:37 UTC
No problem. We probably should print some checksum while loading the microcode to better catch such errors.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.