[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=153121

Kontantin Ivanov <kostyarin.ivanov at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |low

--- Comment #28 from Kontantin Ivanov <kostyarin.ivanov at gmail.com> ---
Hah. Now, when I update my kernel to 4.8-rc2 (4.8.0-040800rc2) the error
messages in dmesg are also present

[    6.361530] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[    7.376047] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[    8.390569] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[    9.405078] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   10.419596] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   11.434111] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   12.448626] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   13.463148] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   14.477689] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   15.492208] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[   15.512208] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving
up!!!
[   16.535049] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed
out.
[   16.535153] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed
testing IB on GFX ring (-110).
[   16.535235] [drm:radeon_device_init [radeon]] *ERROR* ib ring test failed
(-110).


But it appears only on system start and never again. When I start

DRI_PRIME=1 glxinfo and DRI_PRIME=1 glxgears

the programs are started without delay and without error messages in both
stderr and dmesg.

What is interesting? Ok, see here:

glxinfo | grep -i opengl | egrep -i '(version|renderer)'

OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile 
OpenGL version string: 2.1 Mesa 11.2.0
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.2.0
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

DRI_PRIME=1 glxinfo | grep -i opengl | egrep -i '(version|renderer)'

OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile 
OpenGL version string: 2.1 Mesa 11.2.0
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.2.0
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

Both graphic cards (DRI_PRIME=0 and DRI_PRIME=1) looks like are the same card
Intel(R) Ironlake Mobile.

But let's render something:

glxgears

Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
304 frames in 5.0 seconds = 60.605 FPS
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 1263 requests (1263 known processed) with 0 events remaining.

DRI_PRIME=1 glxgears

Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
8731 frames in 5.0 seconds = 1746.049 FPS
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 24162 requests (24162 known processed) with 0 events remaining.

Ha-ha, FPS is different and DRI_PRIME=1 looks like more powerful.

I changed importance of this bug to low.

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