From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing Date: Thu, 03 Nov 2016 09:45:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0353907338==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 396EE6E690 for ; Thu, 3 Nov 2016 09:45:56 +0000 (UTC) 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 --===============0353907338== Content-Type: multipart/alternative; boundary="14781663561.c861E9.32493"; charset="UTF-8" --14781663561.c861E9.32493 Date: Thu, 3 Nov 2016 09:45:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D91880 --- Comment #128 from Jan Ziak <0xe2.0x9a.0x9b@gmail.com> --- (In reply to Chris Waters from comment #127) > Second question, is there any way to just force the memory clock to stay = at > 1500MHz? If the bug is caused by memory switching (and not the memory bei= ng > clocked way too high), then forcing the memory to stay at the max standard > clock should give us the stability of 150MHz. Some months ago, I thought it was just mclk switching. But today I am not so sure about it. Executing the following steps on my machine with an R9 390: - lock mclk to 1500MHz - start playing Mad Max via Steam - switch to the game map via gamepad or keyboard (https://www.google.sk/search?q=3Dmad+max+game+map&tbm=3Disch) results in noticeable screen image flickering. If I disable the lowest 300 MHz shader clock, so that the minimum shader cl= ock is 500 MHz and maximum is 1000 MHz, the flickering disappears. --=20 You are receiving this mail because: You are the assignee for the bug.= --14781663561.c861E9.32493 Date: Thu, 3 Nov 2016 09:45:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 128 on bug 91880<= /a> from Jan Ziak 
(In reply to Chris Waters from comment #127)
> Second question, is there any way to just force =
the memory clock to stay at
> 1500MHz? If the bug is caused by memory switching (and not the memory =
being
> clocked way too high), then forcing the memory to stay at the max stan=
dard
> clock should give us the stability of 150MHz.

Some months ago, I thought it was just mclk switching. But today I am not so
sure about it.

Executing the following steps on my machine with an R9 390:

- lock mclk to 1500MHz
- start playing Mad Max via Steam
- switch to the game map via gamepad or keyboard
(https://www.google.sk/search?q=3Dmad+max+game+map&tbm=3Disch)

results in noticeable screen image flickering.

If I disable the lowest 300 MHz shader clock, so that the minimum shader cl=
ock
is 500 MHz and maximum is 1000 MHz, the flickering disappears.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14781663561.c861E9.32493-- --===============0353907338== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0353907338==--