All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99400] [nouveau] garbled rendering with glamor on G71
Date: Mon, 30 Jan 2017 19:51:12 +0000	[thread overview]
Message-ID: <bug-99400-8800-SQN3Jdqqf1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99400-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 584 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99400

--- Comment #19 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
OH! DUH!

apitrace: warning: glMapBufferRange: MAP_COHERENT_BIT|MAP_WRITE_BIT unsupported
<https://git.io/vV9kM>

Right, so you need to run this with
MESA_EXTENSION_OVERRIDE=-GL_ARB_buffer_storage. Or find some way to force
glamor to disable it. apitrace doesn't like it. I'm sure that's why the
textures are garbage.

-- 
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: 1393 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-01-30 19:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 15:21 [Bug 99400] New: [nouveau] garbled rending with glamor on G71 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-99400-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-13 15:26   ` [Bug 99400] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:26   ` [Bug 99400] [nouveau] garbled rendering " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 15:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 16:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 18:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-13 19:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-14  0:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-16 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-16 16:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-17 11:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-27 15:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 15:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30  9:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 12:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 12:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 19:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-30 19:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-01-31  9:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-31 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-02  6:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-18 22:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20  8:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20 11:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20 18:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-20 18:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26  2:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 13:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 14:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:44   ` 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-99400-8800-SQN3Jdqqf1@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.