[Bug 67876] linux v4.11-rc1 many drm:radeon_ttm_backend_bind ERROR failed to bind 2025 pages issued during boot

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Aug 7 18:15:30 PDT 2013


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

--- Comment #2 from jim.cromie at gmail.com ---
thank you Alex, the firmware page helped some.

Turns out I needed more than the CEDAR_smc.bin,
(which fwiw was never warned about)

[    1.756212] radeon 0000:01:00.0: radeon_uvd: Can't load firmware
"radeon/CYPRESS_uvd.bin"

which went away only after fetching that FW too.


So, having both FWs, I tested current master and it worked.
(I'll assume that means my bisect-bad would too)

$ uname -r
3.11.0-rc4-x2-00050-gb7bc9e7

[jimc at groucho bootlogs]$ dmesg| grep -E 'radeon|drm' 
[    1.741557] [drm] Initialized drm 1.1.0 20060810
[    1.773454] dynamic_debug:ddebug_add_module: 1 debug prints in module radeon
[    1.775402] [drm] radeon kernel modesetting enabled.
[    1.775714] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68E1
0x1787:0x3000).
[    1.775734] [drm] register mmio base: 0xFE9E0000
[    1.775735] [drm] register mmio size: 131072
[    1.776643] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 -
0x000000003FFFFFFF (1024M used)
[    1.776645] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 -
0x000000005FFFFFFF
[    1.776647] [drm] Detected VRAM RAM=1024M, BAR=256M
[    1.776648] [drm] RAM width 64bits DDR
[    1.776755] [drm] radeon: 1024M of VRAM memory ready
[    1.776757] [drm] radeon: 512M of GTT memory ready.
[    1.777788] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    1.778782] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[    1.778799] [drm] Loading CEDAR Microcode
[    1.788485] [drm] PCIE GART of 512M enabled (table at 0x000000000025D000).
[    1.788599] radeon 0000:01:00.0: WB enabled
[    1.788602] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff88021e466c00
[    1.788604] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff88021e466c0c
[    1.788607] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0xffffc9001101c418
[    1.788609] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    1.788610] [drm] Driver supports precise vblank timestamp query.
[    1.788632] radeon 0000:01:00.0: irq 42 for MSI/MSI-X
[    1.788644] radeon 0000:01:00.0: radeon: using MSI.
[    1.788667] [drm] radeon: irq initialized.
[    1.804943] [drm] ring test on 0 succeeded in 1 usecs
[    1.805001] [drm] ring test on 3 succeeded in 1 usecs
[    2.992422] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    4.013574] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    5.034731] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    6.055874] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    7.077016] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    8.098157] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[    9.119302] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   10.140429] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   11.161610] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   12.182794] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   12.202894] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[   12.202973] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).



Im a bit puzzled at the apparent need for 2 different CODENAME_ firmwares,
an also why theres no warning for missing CEDAR_smc.bin

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130808/91d8796e/attachment.html>


More information about the dri-devel mailing list