From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 73378] [drm:radeon_uvd_send_upll_ctlreq] *ERROR* Timeout setting UVD clocks! Date: Wed, 28 Jan 2015 20:44:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0268938564==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 61C3F6E467 for ; Wed, 28 Jan 2015 12:44:25 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0268938564== Content-Type: multipart/alternative; boundary="1422477865.E5BB2.4294"; charset="UTF-8" --1422477865.E5BB2.4294 Date: Wed, 28 Jan 2015 20:44:25 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D73378 --- Comment #18 from Chernovsky Oleg --- (In reply to Alex Deucher from comment #16) > (In reply to Christian K=C3=B6nig from comment #14) > > (In reply to =C3=96yvind Saether from comment #13) > > > on 3.18.1, could this be because the card is factory overclocked? > >=20 > > Yes, that's possible. If you activate UVD you must downclock the system > > clock for it to work reliable. Not sure if we have implemented that > > correctly for SI. >=20 > We already handle it. SI has UVD power states which also include validat= ed > sclk and mclk levels that are often different than the performance state.= =20 > The driver switches to those states when UVD is used. At driver load time > (when the ring and IB tests are done), the hw is still in the boot state > (which has really low clocks) anyway. Hm-m, just tried drm-next-3.20 branch and: [ 365.200918] [drm:radeon_uvd_send_upll_ctlreq [radeon]] *ERROR* Timeout setting UVD clocks! [ 365.200922] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: failed to ra= ise UVD clocks (-110). [ 365.200928] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). Both on cold start and resume from suspend, Pitcairn, Mesa 10.4.3 Ah yes, the card is factory overclocked (at least box states so) It's not very painful for me but if I can help somehow, I'm in --=20 You are receiving this mail because: You are the assignee for the bug. --1422477865.E5BB2.4294 Date: Wed, 28 Jan 2015 20:44:25 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 18 on bug 73378<= /a> from = Chernovsky Oleg 
(In reply to Alex Deucher from comment #16)
> (In reply to Christian K=C3=B6nig from comment #14)
> > (In reply to =C3=96yvind Saether from comment #13)
> > > on 3.18.1, could this be because the card is factory overclo=
cked?
> >=20
> > Yes, that's possible. If you activate UVD you must downclock the =
system
> > clock for it to work reliable. Not sure if we have implemented th=
at
> > correctly for SI.
>=20
> We already handle it.  SI has UVD power states which also include vali=
dated
> sclk and mclk levels that are often different than the performance sta=
te.=20
> The driver switches to those states when UVD is used.  At driver load =
time
> (when the ring and IB tests are done), the hw is still in the boot sta=
te
> (which has really low clocks) anyway.

Hm-m, just tried drm-next-3.20 branch and:

[  365.200918] [drm:radeon_uvd_send_upll_ctlreq [radeon]] *ERROR* Timeout
setting UVD clocks!
[  365.200922] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: failed to ra=
ise
UVD clocks (-110).
[  365.200928] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed
testing IB on ring 5 (-110).


Both on cold start and resume from suspend, Pitcairn, Mesa 10.4.3
Ah yes, the card is factory overclocked (at least box states so)

It's not very painful for me but if I can help somehow, I'm in

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1422477865.E5BB2.4294-- --===============0268938564== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0268938564==--