From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98457] [NVD9] GPU lockup after resume from hibernation with Nouveau driver and firmware-nonfree
Date: Fri, 04 Nov 2016 08:28:57 +0000 [thread overview]
Message-ID: <bug-98457-8800-LjFdflRssj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98457-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98457
--- Comment #1 from wadev-cl+VPiYnx/0HWmgEVkV9KA@public.gmane.org ---
I tried the trunk (of 2016-10-27) of mesa, libdrm and xf86-video-nouveau, no
dice.
I could not, however, try the kernel driver (which I presume is mainly for text
mode and probably comprises the framebuffer backend of the libdrm), as I am at
4.8.4 now and the nouveau kernel driver repository is fit for some such arcane
kernel version that it has been removed even from OpenVZ and such. :P
If anyone has some ideas on how to find an "edger" repository of the nouveau
kernel driver object that is ahead of the kernel.org state (if any), please let
me know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1585 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2016-11-04 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 8:29 [Bug 98457] New: [NVD9] GPU lockup after resume from hibernation with Nouveau driver and firmware-nonfree bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-98457-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-11-04 8:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-11-04 8:29 ` [Bug 98457] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-04 8:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-04 9:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 8:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 8:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 8:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-07 13:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:43 ` 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-98457-8800-LjFdflRssj@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