From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 33165] [NVA3, NVA8] gpu lockup during driver probe Date: Sun, 09 Mar 2014 22:53:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0192444982==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0192444982== Content-Type: multipart/alternative; boundary="1394405622.4A8c7.15084"; charset="us-ascii" --1394405622.4A8c7.15084 Date: Sun, 9 Mar 2014 22:53:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=33165 --- Comment #31 from Ilia Mirkin --- (In reply to comment #29) > Created attachment 95418 [details] [review] > another patch for gddr5 ram > > I made this patch using my mmiotrace, but it doesn't help either. Oh well. Indeed the values in your mmiotrace are different, but your and Andrew's mmiotrace are the only traces I've seen that actually have the writes to those 0x10fxyz registers. (A few other traces have writes to the similar-but-different DDR3 registers.) And yes, I definitely did want to use offsets[o] in my patch. Well, perhaps this 0x10f stuff has nothing to do with the issue. My observation was that it seemed like for all the people it was broken for had GDDR5 ram, which is why I went in this direction. -- You are receiving this mail because: You are the assignee for the bug. --1394405622.4A8c7.15084 Date: Sun, 9 Mar 2014 22:53:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 31 on bug 33165 from 
(In reply to comment #29)
> Created attachment 95418 [details] [review] [review]
> another patch for gddr5 ram
> 
> I made this patch using my mmiotrace, but it doesn't help either.

Oh well. Indeed the values in your mmiotrace are different, but your and
Andrew's mmiotrace are the only traces I've seen that actually have the writes
to those 0x10fxyz registers. (A few other traces have writes to the
similar-but-different DDR3 registers.)

And yes, I definitely did want to use offsets[o] in my patch.

Well, perhaps this 0x10f stuff has nothing to do with the issue. My observation
was that it seemed like for all the people it was broken for had GDDR5 ram,
which is why I went in this direction.

You are receiving this mail because:
  • You are the assignee for the bug.
--1394405622.4A8c7.15084-- --===============0192444982== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nouveau mailing list Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org http://lists.freedesktop.org/mailman/listinfo/nouveau --===============0192444982==--