From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 111724] New: NVE6 (GK106) memory re-clocking breaks GpuTest plot3d benchmark Date: Tue, 17 Sep 2019 14:31:43 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1697309253==" Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============1697309253== Content-Type: multipart/alternative; boundary="15687307051.36E3bCE.9244" Content-Transfer-Encoding: 7bit --15687307051.36E3bCE.9244 Date: Tue, 17 Sep 2019 14:31:45 +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=3D111724 Bug ID: 111724 Summary: NVE6 (GK106) memory re-clocking breaks GpuTest plot3d benchmark Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: not set Component: Driver/nouveau Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Reporter: mmenzyns-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org I have stepped upon a problem with NVE6 (GK106) in GpuTest https://www.geeks3d.com/gputest/ plot3d benchmark that occurs only in plot3d and nowhere else. There are visible glitches and when left for a longer time Nouveau seems to crash. The GPU has 4 profiles:=20 07: core 324 MHz memory 648 MHz 0a: core 324-862 MHz memory 1620 MHz 0d: core 549-1228 MHz memory 6008 MHz 0f: core 549-1228 MHz memory 6008 MHz The problem occurs when switching re-clocking profile directly from 648 MHz= to 6008 MHz skipping the 0xA 1620 MHz profile. If gone through 0xA profile everything works fine. If the memory re-clocking is disabled, it works fine. If there is 0xF profi= le set directly (breaking the benchmark) with memory re-clocking enabled, then= the nouveau gets unloaded, and nouveau gets loaded back with memory re-clocking disabled, when changing re-clocking profiles it still glitches. Which impli= es something that breaks this is only touched when the memory re-clocking is enabled. I have gone through all nouveau pmu scripts traces, checked every difference (of the scripts) with Nvidia driver and nothing seemed to affect this probl= em that has different values than Nvidia. Actual code which was changing the values for 0xf profile to be same as Nvidia is here: https://github.com/mmenzyns/nouveau/tree/linux-5.2_gk106_memory_issues. The scripts for the highest-profile should be almost identical between Nvidia a= nd Nouveau. --=20 You are receiving this mail because: You are the assignee for the bug.= --15687307051.36E3bCE.9244 Date: Tue, 17 Sep 2019 14:31:45 +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
Bug ID 111724
Summary NVE6 (GK106) memory re-clocking breaks GpuTest plot3d benchma= rk
Product xorg
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority not set
Component Driver/nouveau
Assignee nouveau@lists.freedesktop.org
Reporter mmenzyns@redhat.com
QA Contact xorg-team@lists.x.org

I have stepped upon a problem with NVE6 (GK106) in GpuTest
https://www.geeks3d.com/gputes=
t/ plot3d benchmark that occurs only in plot3d
and nowhere else. There are visible glitches and when left for a longer time
Nouveau seems to crash.

The GPU has 4 profiles:=20
07: core 324 MHz memory 648 MHz
0a: core 324-862 MHz memory 1620 MHz
0d: core 549-1228 MHz memory 6008 MHz
0f: core 549-1228 MHz memory 6008 MHz

The problem occurs when switching re-clocking profile directly from 648 MHz=
 to
6008 MHz skipping the 0xA 1620 MHz profile. If gone through 0xA profile
everything works fine.

If the memory re-clocking is disabled, it works fine. If there is 0xF profi=
le
set directly (breaking the benchmark) with memory re-clocking enabled, then=
 the
nouveau gets unloaded, and nouveau gets loaded back with memory re-clocking
disabled, when changing re-clocking profiles it still glitches. Which impli=
es
something that breaks this is only touched when the memory re-clocking is
enabled.

I have gone through all nouveau pmu scripts traces, checked every difference
(of the scripts) with Nvidia driver and nothing seemed to affect this probl=
em
that has different values than Nvidia. Actual code which was changing the
values for 0xf profile to be same as Nvidia is here:
https://github.com/mmenzyns/nouveau/tree/linux-5.2_gk106_memory_iss=
ues. The
scripts for the highest-profile should be almost identical between Nvidia a=
nd
Nouveau.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15687307051.36E3bCE.9244-- --===============1697309253== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1 --===============1697309253==--