From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 105045] System freeze with nouveau
Date: Sun, 11 Feb 2018 18:23:02 +0000 [thread overview]
Message-ID: <bug-105045-8800-sWCHLCA22L@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105045-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 725 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #5 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Sergey Tereschenko from comment #4)
> Can i just apply that patch to 17.3 or better build everything from git?
You can just apply it. There's other stuff that's gone in though... I was just
pointing out one thing I did. A bunch of people had issues with 17.3 and
resizing stuff as I recall... other things too. I'd basically recommend running
mesa master -- mesa is not very good at backporting fixes. And master's very
rarely in a broken state.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1525 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:[~2018-02-11 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 17:09 [Bug 105045] New: System freeze with nouveau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-105045-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-02-11 17:24 ` [Bug 105045] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 17:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 17:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 17:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 18:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 18:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-02-11 18:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 19:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 19:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-12 20:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-28 9: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-105045-8800-sWCHLCA22L@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.