From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91231] [NV92] Psychonauts (native) segfaults on start when DRI3 enabled
Date: Sun, 05 Jul 2015 03:30:00 +0000 [thread overview]
Message-ID: <bug-91231-8800-RjiMNGxoe9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91231-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 378 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91231
--- Comment #2 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
The assertion is regarding PIPE_BIND_SCANOUT + nr_samples != 0. I suspect this
might be a dri st bug which only surfaces with the new mechanisms that dri3
enables.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1146 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:[~2015-07-05 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 3:28 [Bug 91231] New: [NV92] Psychonauts (native) segfaults on start when DRI3 enabled bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-91231-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-07-05 3:29 ` [Bug 91231] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-05 3:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-07-05 3:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-06 7:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-07 17:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-07 17:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-08 4:22 ` 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-91231-8800-RjiMNGxoe9@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.