From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 81136] [NV92] Regression in Linux 3.15: GPU lockup after suspend
Date: Tue, 28 Oct 2014 01:59:56 +0000 [thread overview]
Message-ID: <bug-81136-8800-ilnkiaTMsV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-81136-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 900 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=81136
--- Comment #10 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Ed,
Considering that the workarounds mentioned do not work in your case and that
you have a different card (reporter has nv92, while yours is gk106) we can
safely conclude that you're having a different issue.
Please open another bug report and let us know if it is a regression, and if so
which commit broke it.
Agustín,
These two should be non-fatal and the fix for them is in 3.18. Should end up in
3.16, 3.17 as well.
> FAULT at 0x00e070
> FAULT at 0x00e074
Now this one, I have no idea. Do you get this error with 3.14 and dual monitors
?
> FAULT at 0x00e180
Linux 3.17 includes quite a few fixes in the area of s/r, can you give it a
try.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1742 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-10-28 1:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 0:35 [Bug 81136] New: [NV92] Regression in Linux 3.15: GPU lockup after suspend bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-81136-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-07-10 0:35 ` [Bug 81136] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-10 0:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10 7:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10 7:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10 9:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-11 4:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-16 5:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-25 21:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-27 22:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28 1:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-10-28 2:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28 3:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28 3:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-30 4:37 ` 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-81136-8800-ilnkiaTMsV@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