From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 97620] [REGRESSION] KMS having issues after kernel upgrade (4.5.1-1 to 4.6.4-1) Date: Mon, 19 Sep 2016 05:34:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2110862927==" Return-path: In-Reply-To: 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 --===============2110862927== Content-Type: multipart/alternative; boundary="14742632691.6fB3abE.20579"; charset="UTF-8" --14742632691.6fB3abE.20579 Date: Mon, 19 Sep 2016 05:34:29 +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=3D97620 --- Comment #27 from Ilia Mirkin --- Looking at our VBIOS repo, we have a bunch (but not all) of GF104's that are missing the 0x2240c write as well as one GK107. Every other (GF100+) GPU se= ts 0x2240c. I guess it's not as reliable as we'd hoped. This is how I checked: for i in nv[cdef]?/*/*.rom nv1??/*/*.rom; do echo $i; nvbios $i |& grep 0x02240c; done And looked for files without a 'NV_REG R[0x02240c] &=3D 0xfffffffd |=3D 0x00000002' command. Although that in itself shouldn't be a major issue - rerunning the VBIOS shouldn't cause issues... Looking at a mmiotrace that came with one of those GF104 VBIOSes that are missing a 0x2240c write, it doesn't seem like the VBIOS gets executed there= , or at least not that script. It's late and I could have messed up though. --=20 You are receiving this mail because: You are the assignee for the bug.= --14742632691.6fB3abE.20579 Date: Mon, 19 Sep 2016 05:34:29 +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

Commen= t # 27 on bug 97620<= /a> from Ilia Mirkin 
Looking at our VBIOS repo, we have a bunch (but not all) of GF=
104's that are
missing the 0x2240c write as well as one GK107. Every other (GF100+) GPU se=
ts
0x2240c. I guess it's not as reliable as we'd hoped.

This is how I checked:

for i in nv[cdef]?/*/*.rom nv1??/*/*.rom; do echo $i; nvbios $i |& grep
0x02240c; done

And looked for files without a 'NV_REG   R[0x02240c] &=3D 0xfffffffd |=
=3D
0x00000002' command.

Although that in itself shouldn't be a major issue - rerunning the VBIOS
shouldn't cause issues...

Looking at a mmiotrace that came with one of those GF104 VBIOSes that are
missing a 0x2240c write, it doesn't seem like the VBIOS gets executed there=
, or
at least not that script. It's late and I could have messed up though.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14742632691.6fB3abE.20579-- --===============2110862927== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============2110862927==--