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 05:52:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0235446889==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id F192D6E67D for ; Thu, 3 Nov 2016 05:52:33 +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 --===============0235446889== Content-Type: multipart/alternative; boundary="147815235310.FB7079.5774"; charset="UTF-8" --147815235310.FB7079.5774 Date: Thu, 3 Nov 2016 05:52:33 +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 #127 from Chris Waters --- I've noticed that on my Win7 install if I up the memory clock a good (1700M= Hz+) bit I'll get the same exact artifacts as I would in Linux. Maybe the driver= is trying to switch to too high of a clock for memory? 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 standard clock should give us the stability of 150MHz. --=20 You are receiving this mail because: You are the assignee for the bug.= --147815235310.FB7079.5774 Date: Thu, 3 Nov 2016 05:52:33 +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 # 127 on bug 91880<= /a> from Chris Waters 
I've noticed that on my Win7 install if I up the memory clock =
a good (1700MHz+)
bit I'll get the same exact artifacts as I would in Linux. Maybe the driver=
 is
trying to switch to too high of a clock for memory?

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 standard
clock should give us the stability of 150MHz.

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