[Bug 66963] Rv6xx dpm problems

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun May 24 10:07:06 PDT 2015


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

--- Comment #261 from Armin Wehrfritz <dkxls23 at gmail.com> ---
I just tested dpm for the radeon RV635 card in my Thinkpad T500 with the kernel
4.0.4-2.g4f5e0d5-desktop x86_64 under OpenSUSE 13.2. 
I probably should mention that I have not tested to change
'power_dpm_force_performance_level' or 'power_dpm_state', so both of them are
at their default.

1) with radeon.dpm=1 the GPU will not be initialised correctly due to some
issues with the UVD, here the log:

[drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the
VCPU!!!
[drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!!
[drm:r600_startup [radeon]] *ERROR* radeon: failed initializing UVD (-1).
radeon 0000:01:00.0: ring 0 stalled for more than 10020msec
radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000000 last fence
id 0x0000000000000001 on ring 0)
[drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX
ring (-35).
[drm:radeon_device_init [radeon]] *ERROR* ib ring test failed (-35).



2) with radeon.dpm=1 and radeon.hard_reset=1 the GPU will be initialised
correctly and the system will bootup properly.
However, when opening google-chrome the GPU will lockup and the X-server
crashes, here the log:

radeon 0000:01:00.0: ring 0 stalled for more than 10465msec
radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000009ca0 last fence
id 0x0000000000009cc3 on ring 0)
radeon 0000:01:00.0: Saved 1113 dwords of commands on ring 0.
radeon 0000:01:00.0: GPU softreset: 0x00000008
radeon 0000:01:00.0:   R_008010_GRBM_STATUS      = 0xA0003030
radeon 0000:01:00.0:   R_008014_GRBM_STATUS2     = 0x00000003
radeon 0000:01:00.0:   R_000E50_SRBM_STATUS      = 0x200000C0
radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00020186
radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80028645
radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00004001
radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
radeon 0000:01:00.0:   R_008010_GRBM_STATUS      = 0xA0003030
radeon 0000:01:00.0:   R_008014_GRBM_STATUS2     = 0x00000003
radeon 0000:01:00.0:   R_000E50_SRBM_STATUS      = 0x200080C0
radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80100000
radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
radeon 0000:01:00.0: GPU pci config reset
radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
radeon 0000:01:00.0: Wait for MC idle timedout !
radeon 0000:01:00.0: Wait for MC idle timedout !
[drm] PCIE GART of 512M enabled (table at 0x0000000000254000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000c00 and
cpu addr 0xffff8800b4c0cc00
radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x00000000000521d0 and
cpu addr 0xffffc900058921d0
[drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xFFFFFFFF)
[drm:r600_resume [radeon]] *ERROR* r600 startup failed on resume
[drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
May 24 19:20:32 linux.site kernel: radeon 0000:01:00.0: ring 0 stalled for more
than 10034msec
May 24 19:20:32 linux.site kernel: radeon 0000:01:00.0: GPU lockup (current
fence id 0x0000000000009ca0 last fence id 0x0000000000009cc3 on ring 0)
...

I hope this helps to track down and fix this issue. If there is something I can
test or help otherwise, please let me know.

Cheers,
Armin

-- 
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/20150524/a6c455e9/attachment.html>


More information about the dri-devel mailing list