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: Tue, 31 Jan 2017 12:37:26 +0000	[thread overview]
Message-ID: <bug-99400-8800-jhj5iur4JD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99400-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #21 from Olivier Fourdan <fourdan-eaOCjQ5FDoY@public.gmane.org> ---
(In reply to Olivier Fourdan from comment #20)
> 
> I cannot load the file on nouveau where it was captured, it says
> 
>  | 2 @0 eglGetPlatformDisplayEXT(platform = EGL_PLATFORM_GBM_KHR,
> native_display = 0x26926b0, attrib_list = {}) = 0x26d8250
>  | 2: warning: unsupported eglGetPlatformDisplayEXT call
> error: failed to create OpenGL 3.1 context.

Quick follow up on this, this is because of the way glamor works, it first
creates an EGL context with some config attributes (which include the OpenGL
version 3.1) and if it fails, it retries with no config attributes:

https://cgit.freedesktop.org/xorg/xserver/tree/glamor/glamor_egl.c#n819

or for Xwayland:

https://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayland/xwayland-glamor.c#n310

So back to apitrace, as the config attributes specifies OpenGL 3.1, it fails
and apitrace just stops there. So I changed Xwayland to not do the first call
(which on this HW returns NULL anyway) and now apitrace is a happy buddy, I can
replay the trace on nouveau as well.

Same links, updated files:

https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.log
https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.trace

> For example frame 8932 (toward the end) is interesting imho, [...]

Let's forget about this, now that the new trace can replay on both intel and
nouveau.

The problem I see is rather that I see no problem in apitrace, the frames look
fine, AFAICT.

And yet the rendering was wrong on screen when I captured the trace...

-- 
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: 3026 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-31 12:37 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
2017-01-31  9:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-31 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
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-jhj5iur4JD@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.