All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650
Date: Thu, 18 Aug 2016 05:13:47 +0000	[thread overview]
Message-ID: <bug-153121-2300-yfPET09mtq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-153121-2300@https.bugzilla.kernel.org/>

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

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

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

--- Comment #28 from Kontantin Ivanov <kostyarin.ivanov@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.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-08-18  5:13 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15  8:52 [Bug 153121] New: UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650 bugzilla-daemon
2016-08-15  8:54 ` [Bug 153121] " bugzilla-daemon
2016-08-15  8:55 ` bugzilla-daemon
2016-08-15  8:55 ` bugzilla-daemon
2016-08-15  8:56 ` bugzilla-daemon
2016-08-15  8:57 ` bugzilla-daemon
2016-08-15  8:57 ` bugzilla-daemon
2016-08-15  8:58 ` bugzilla-daemon
2016-08-15  8:59 ` bugzilla-daemon
2016-08-15  9:01 ` bugzilla-daemon
2016-08-15  9:06 ` bugzilla-daemon
2016-08-15  9:07 ` bugzilla-daemon
2016-08-15  9:07 ` bugzilla-daemon
2016-08-15  9:22 ` bugzilla-daemon
2016-08-15  9:38 ` bugzilla-daemon
2016-08-15  9:41 ` bugzilla-daemon
2016-08-15  9:51 ` bugzilla-daemon
2016-08-15  9:54 ` bugzilla-daemon
2016-08-15 10:03 ` bugzilla-daemon
2016-08-15 10:56 ` bugzilla-daemon
2016-08-15 11:18 ` bugzilla-daemon
2016-08-16 14:01 ` bugzilla-daemon
2016-08-16 14:02 ` bugzilla-daemon
2016-08-16 14:03 ` bugzilla-daemon
2016-08-16 14:04 ` bugzilla-daemon
2016-08-16 14:05 ` bugzilla-daemon
2016-08-16 14:17 ` bugzilla-daemon
2016-08-16 14:18 ` bugzilla-daemon
2016-08-18  5:13 ` bugzilla-daemon [this message]
2016-08-18  6:18 ` bugzilla-daemon
2016-08-18  6:28 ` bugzilla-daemon
2016-08-18  6:28 ` bugzilla-daemon
2016-08-22 11:52 ` bugzilla-daemon
2016-08-22 11:54 ` bugzilla-daemon
2016-08-29  9:32 ` bugzilla-daemon
2016-09-02 16:22 ` bugzilla-daemon
2016-09-02 16:22 ` bugzilla-daemon
2016-09-02 16:26 ` bugzilla-daemon
2016-09-14 13:12 ` bugzilla-daemon
2016-09-14 13:20 ` bugzilla-daemon
2016-09-18 10:30 ` 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-153121-2300-yfPET09mtq@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.