dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62681] linux-3.12.0 rc3 nouveau: screen corruption after resume
Date: Wed, 16 Oct 2013 15:53:24 +0000	[thread overview]
Message-ID: <bug-62681-2300-lghKiCzLJv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62681-2300@https.bugzilla.kernel.org/>

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

--- Comment #1 from Rich Coe <richcoe2@gmail.com> ---
I found https://bugs.freedesktop.org/show_bug.cgi?id=69982 
which suggests booting with nouveau.config=NvMSI=0 

I haven't tried it yet, as I've been currently running under 
boot parameter nouveau.noaccel=1, and the system hasn't crashed yet.

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

      reply	other threads:[~2013-10-16 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 16:37 [Bug 62681] New: linux-3.12.0 rc3 nouveau: screen corruption after resume bugzilla-daemon
2013-10-16 15:53 ` bugzilla-daemon [this message]

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-62681-2300-lghKiCzLJv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).