From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33165] [NVA3, NVA8] gpu lockup during driver probe
Date: Sun, 09 Mar 2014 22:53:42 +0000 [thread overview]
Message-ID: <bug-33165-8800-TpwCyLQKOK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-33165-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=33165
--- Comment #31 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(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.
[-- Attachment #1.2: Type: text/html, Size: 2012 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-03-09 22:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 19:06 [Bug 33165] New: Nouveau + nvidia GT240 = unworkable bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-33165-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-01-17 16:53 ` [Bug 33165] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-31 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 18:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 18:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 18:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 21:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-22 5:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-22 19:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-20 18:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 3:19 ` [Bug 33165] [NVA3] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 20:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 22:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 9:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 9:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 14:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 14:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 15:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 15:48 ` [Bug 33165] [NVA3, NVA8] gpu lockup during driver probe bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 17:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 14:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 22:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-17 20:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 11:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 11:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 13:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 16:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 16:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 22:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-04-12 2:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-04 8:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-15 3:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-16 20:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-17 8:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-17 8:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-18 16:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-18 16:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-20 0:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-14 17:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-14 17:05 ` [Bug 33165] [NVA3] GDDR5 vram -> flickering screen (previously GPU lockup) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-33165-8800-TpwCyLQKOK@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox