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: Tue, 16 Aug 2016 14:17:07 +0000 [thread overview]
Message-ID: <bug-153121-2300-OMTZY2vejO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-153121-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=153121
--- Comment #26 from Kontantin Ivanov <kostyarin.ivanov@gmail.com> ---
When I start glxgears (on integrated Intel graphic card) the gears shown
stdout is:
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
305 frames in 5.0 seconds = 60.822 FPS
301 frames in 5.0 seconds = 60.030 FPS
301 frames in 5.0 seconds = 60.023 FPS
stderr is:
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 545 requests (545 known processed) with 0 events remaining.
On the Radeon graphic card (DRI_PRIME=1) gears are not shown (black window).
stdout is:
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
17786 frames in 5.0 seconds = 3557.177 FPS
stderr is:
...
radeon: The kernel rejected CS, see dmesg for more information.
radeon: The kernel rejected CS, see dmesg for more information.
radeon: The kernel rejected CS, see dmesg for more information.
radeon: The kernel rejected CS, see dmesg for more information.
radeon: The kernel rejected CS, see dmesg for more information.
radeon: The kernel rejected CS, see dmesg for more information.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 105710 requests (105710 known processed) with 0 events remaining.
And `dmesg | tail` after `DRI_PRIME=1 glxgears` is
[ 576.200519] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[ 577.216465] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[ 578.232004] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying
to reset the VCPU!!!
[ 578.251966] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving
up!!!
[ 578.252025] [drm:evergreen_startup.part.13 [radeon]] *ERROR* radeon: error
initializing UVD (-1).
[ 588.249875] radeon 0000:01:00.0: ring 0 stalled for more than 10000msec
[ 588.249884] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000000005 last fence id 0x0000000000000006 on ring 0)
[ 588.250001] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed
(-35).
[ 588.250042] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed
testing IB on GFX ring (-35).
[ 588.250064] [drm:radeon_resume_kms [radeon]] *ERROR* ib ring test failed
(-35).
I remember that with some kernel the Radeon card shows the gears normally. Tell
me if I need to try all kernels one by one from current to latest.
That's all
Thank y'all for taking the time
--
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
next prev parent reply other threads:[~2016-08-16 14:17 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 [this message]
2016-08-16 14:18 ` bugzilla-daemon
2016-08-18 5:13 ` bugzilla-daemon
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-OMTZY2vejO@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.