Nouveau - Mar 2016 - [Bug 94374] New: transparent window with DRI_PRIME=1, depending on size of used textures

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

            Bug ID: 94374
           Summary: transparent window with DRI_PRIME=1, depending on size
                    of used textures
           Product: Mesa
           Version: 11.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: peter.fiss at gmx.de
        QA Contact: nouveau at lists.freedesktop.org

Created attachment 122086
  --> https://bugs.freedesktop.org/attachment.cgi?id=122086&action=edit
the source code of the program (.tar,xz)

Here's the source code of a simple program, that reproduces incorrect
behavior
of PRIME. I actually wanted to try something different, but then I discovered
this bug. The program generates noise textures and displays them on a quad
using OpenGL 3.3. You can specify the size of the noise textures with the
program's first parameter.

The program runs fine on my Intel Ivy Bridge gpu and it also runs on my GeForce
GT 640M (Kepler) with nouveau and DRI_PRIME=1. When I increase the texture size
to 128 or something larger, the program's window sometimes (>= 50%
chance)
becomes transparent (see attached screenshot) when using DRI_PRIME=1. This
*never* happens with texture sizes of 64 or less. If I remove the use of
textures completely from the program, it always runs fine as well. DRI_PRIME=1
glxgears always works as expected.

My system is Arch Linux with mesa 11.1.2-1 and kernel 4.4.1-2. I'm sorry
that I
cannot install mesa-git since this is my computer for productive work.
Hopefully, someone else can reproduce the issue.

Steps to build the program:
- make sure you have SDL2 installed
- ./build.sh
- DRI_PRIME=1 ./a.out 512       <- might not work
- DRI_PRIME=1 ./a.out 64        <- always works for me

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/7d98e10d/attachment.html>

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

--- Comment #1 from peter.fiss at gmx.de ---
Created attachment 122087
  --> https://bugs.freedesktop.org/attachment.cgi?id=122087&action=edit
screenshot of the transparent window

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/88fd1617/attachment.html>

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

--- Comment #2 from Karol Herbst <freedesktop at karolherbst.de> ---
It doesn't seem to be transparted (check the window border of the window in
the
background. The new window simply contains the the background as the buffer and
moving around won't update the content ;)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/b0e481ad/attachment.html>

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

--- Comment #3 from peter.fiss at gmx.de ---
Yes, you are right. It's not true transparency. But the window doesn't
show the
image rendered by OpenGL.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/77d2c7b9/attachment.html>

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

--- Comment #4 from Karol Herbst <freedesktop at karolherbst.de> ---
well it works for me

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/51b41828/attachment.html>

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

--- Comment #5 from peter.fiss at gmx.de ---
Hm, did you try it multiple times with increasing texture sizes? Is there any
other potentially useful information I could provide?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/3f60ea5b/attachment.html>

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

--- Comment #6 from Karol Herbst <freedesktop at karolherbst.de> ---
I even tried with 2048 multiple times and it always worked (though I had to
wait a little with >=1024). Otherwise I have no idea how to debug such an
issue. I also have kepler gpu, but a GK106, and you a GK107, but that
shouldn't
change much.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160302/048a019a/attachment.html>

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

--- Comment #7 from Wolfgang Wallner <wolfgang-wallner at gmx.at> ---
I can reproduce the same error, but with Intel and AMD hardware.

This is what happens when I run DRI_PRIME=1 steam, and I found this bug report
when I searched for the symptoms. As I said, in my case it is not related to
nouveau, as I use a laptop with an Intel/AMD combination.

My system:

The hardware is a HP Pavillion with mux-less hybrid graphics: Intel Sandy
Bridge and AMD Radeon HD 6770

Kubuntu 15.10 with KDE backports
Mesa 11.0.2

My symptoms:

DRI_PRIME=1 glxgears    --> works
DRI_PRIME=1 ./a.out 64  --> works
DRI_PRIME=1 ./a.out 512 --> transparent window
DRI_PRIME=1 steam       --> transparent window

If I can provide any additional information, please let me know (I have now
idea about debugging graphical bugs, so I don't really know what to
provide).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160312/661a774e/attachment.html>

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

--- Comment #8 from Wolfgang Wallner <wolfgang-wallner at gmx.at> ---
For reasons not related to this bug I had to replace the HDD, and have
installed the current nightly image of Kubuntu 16.04 instead of the previously
used 15.10.

On the newly installed system, I cannot reproduce this bug, neither with steam
nor with the provided gpu memory test program:

DRI_PRIME=1 ./a.out 4096 runs fine

This system now uses Mesa 11.1.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160325/03371d5d/attachment.html>

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

--- Comment #9 from peter.fiss at gmx.de ---
Mesa 11.2.0-1 just rolled out on Arch. The issue is still the same for me.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160410/f501985f/attachment.html>

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

peter.fiss at gmx.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #10 from peter.fiss at gmx.de ---
This bug appears to be fixed. I know it was still present about a week ago with
Mesa 12.0.1, but today xf86-video-intel got upgraded (from
1:2.99.917+676+g26f8ab5-1 to 1:2.99.917+684+g6988b87-3, whatever these strange
version numbers are). Now I can no longer reproduce the issue. Since the
upgrade, the driver uses DRI3 by default. But even when I switch back to DRI2
manually, this is no longer an issue.

I'm closing this issue now, until it happens again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160731/5d9145fa/attachment.html>

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

--- Comment #11 from Dongmin Kim <kim135797531g at gmail.com> ---
* For note - Get the same issue at Ubuntu 16.04 LTS 64-bit.

- Intel Ivy-bridge & AMD HD 7650M Hybrid graphics
- DRI2 for default
- Kernel 4.4.0-53
- Mesa 11.2.0

It happened with texture sizes over than 256, but when I use DRI3, it never
happens anymore.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20161222/38bdd294/attachment.html>