All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206225] nouveau: Screen distortion and lockup on resume
Date: Sat, 18 Jan 2020 19:20:28 +0000	[thread overview]
Message-ID: <bug-206225-2300-RKZssplLHK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206225-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206225

--- Comment #7 from Christoph Marz (derchiller-foren@online.de) ---
(In reply to Ilia Mirkin from comment #6)
> I see you have nouveau.config=PCRYPT=0 in your kernel config. Why did you
> add this -- was there some kind of issue with the engine? Did someone in
> #nouveau tell you to do it to help some issue?

Hello Ilia,

I had found a bug report (https://bugs.freedesktop.org/show_bug.cgi?id=58378)
dealing with a similar issue, and there you suggested to try that option
(https://bugs.freedesktop.org/show_bug.cgi?id=58378#c46), and it seemingly
solved the issue, so I gave it a try, but removed it after I noticed that it
had no effect at all.

>It's normally used for copy
> acceleration on G96 (which would, in turn, be used to copy off any vram data
> to ram on suspend).
> 
> The reason I ask is that starting with kernel 4.3, that will no longer have
> the effect of disabling PCRYPT. The new config to achieve that would be
> nouveau.config=cipher=0.

Ok, thanks for clarification. Copy acceleration sounds good, is there any
downside?

> Note that for G96, I don't think anything in firmware-misc-nonfree would
> affect it either way.

I will uninstall that package and report back.

BTW: No problems with 5.4.13 so far.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-01-18 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 16:03 [Bug 206225] New: nouveau: Screen distortion and lockup on resume bugzilla-daemon
2020-01-16 16:13 ` [Bug 206225] " bugzilla-daemon
2020-01-16 16:15 ` bugzilla-daemon
2020-01-16 16:20 ` bugzilla-daemon
2020-01-16 16:22 ` bugzilla-daemon
2020-01-18  8:26 ` bugzilla-daemon
2020-01-18 17:30 ` bugzilla-daemon
2020-01-18 19:20 ` bugzilla-daemon [this message]
2020-01-18 19:36 ` bugzilla-daemon
2020-01-19 14:50 ` bugzilla-daemon
2020-01-19 19:37 ` bugzilla-daemon
2020-01-19 20:42 ` bugzilla-daemon
2020-02-06 17:55 ` bugzilla-daemon

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-206225-2300-RKZssplLHK@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.