All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 59168] [nvc1/Quardro1000M|nvc3/Quadro2000M] graphic garbage/corruption/noise on resume
Date: Mon, 03 Mar 2014 02:08:08 +0000	[thread overview]
Message-ID: <bug-59168-8800-TDFXQB42OU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59168-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1206 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=59168

--- Comment #42 from Laurence Lee <rubyjedi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Created attachment 94996
  --> https://bugs.freedesktop.org/attachment.cgi?id=94996&action=edit
Remove NVDEV_ENGINE_COPY1 from GF116 to mirror GF106

Since Michael Weirauch reports this issue has been resolved for his card (0xc3,
according to his dmesg uploads), and the issue remains on Doug Brunner and my
card (0xcf), and that both cards once used the same code-base and functioned
correctly in the Linux 3.4 Kernels, I went on a hunch.

By changing the 0xc3 definition to 0xcf (forcing my card to be recognized as a
GF106), I was able to reproduce Michael's suspend/resume success with my own
card.

Having discovered that THAT works, it became a mission to figure out what was
different between the 0xc3 (GF106, working) and 0xcf (GF116, non-working).

By removing the declaration of NVDEV_ENGINE_COPY1 from the 0xcf case, as this
patch does, the suspend/resume issue no longer affects my card.

I have submitted this patch for your review, and sincerely hope it is accepted.
Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2224 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-03-03  2:08 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 14:36 [Bug 59168] New: [nvc3/Quadro2000M] graphic garbage/corruption/noise on resume bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-59168-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-01-09 14:39   ` [Bug 59168] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-17  8:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-01 10:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-01 10:37   ` [Bug 59168] [nvc1/Quardro1000M|nvc3/Quadro2000M] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-01 10:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-01 10:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-07  8:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-07  9:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-07 16:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-13 11:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-13 12:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 10:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 10:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 16:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 17:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 19:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 20:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 21:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 21:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 21:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-19 21:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-20  8:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-20  8:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-21  7:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-21 21:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-22  1:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-22  7:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-22 12:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-26 14:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-26 16:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-27  9:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-12  7:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-12 11:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-20  9:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-29 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-03  7:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-04 12:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 13:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-04  9:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19  6:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03  1:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03  1:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09  9:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-03  2:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-03-03  2:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-03  3:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-03  3:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-03  5:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-04  7:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-04 11:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-11 13:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 18:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-08  1:27   ` 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-59168-8800-TDFXQB42OU@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.