From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 88514] X segfaults when using prime offloading to nouveau card
Date: Sat, 17 Jan 2015 09:56:04 +0000 [thread overview]
Message-ID: <bug-88514-8800-FFV4rx6OVn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88514-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 621 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88514
--- Comment #10 from Chris Wilson <chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org> ---
Right, the bug is just that we attempted to dereference a DRI2ScreenPtr on a
GPU screen for which DRI2 was never initialised (due to NoAccel). So we have 2
bugs:
1. The code should be more robust and only add an offload_slave if DRI2 was
enabled on that Screen (or be prepared for lies).
2. Nouveau shouldn't be claiming to be an offload slave if it doesn't support
offloading (due to NoAccel).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1373 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-01-17 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 22:45 [Bug 88514] New: X segfaults when using prime offloading to nouveau card bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-88514-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-01-16 22:46 ` [Bug 88514] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-16 23:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-16 23:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-16 23:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 0:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 0:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 1:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 1:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 1:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 9:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-01-17 10:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 10:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-26 10:36 ` 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-88514-8800-FFV4rx6OVn@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.