Bug 102804

Summary: Unexpected incomplete framebuffer in _mesa_meta_GenerateMipmap() GLES
Product: Mesa Reporter: Dorian Fevrier <fevrier.dorian>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED NOTOURBUG QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium    
Version: 17.0   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: apitrace file

Description Dorian Fevrier 2017-09-16 13:51:56 UTC 
Created attachment 134272 [details]
apitrace file

I can reproduce a bug:

Please report at https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa
Mesa 17.0.7 implementation error: Unexpected incomplete framebuffer in _mesa_meta_GenerateMipmap()

Here is my hardware:

Linux trigoss 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 18.2 Sonya

Mesa DRI Intel(R) Ivybridge Mobile  - OpenGL ES 3.0 Mesa 17.0.7 : Intel Open Source Technology Center

It's GLES

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Ivybridge Mobile  (0x166)
    Version: 17.0.7
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.0.7
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

I provide the apitrace file, please use apitrace like this to reproduce the problem:

apitrace replay ./mupen64plus.trace

I hope this help. :)

The executed code is here:

https://github.com/mupen64plus/mupen64plus-video-rice/blob/ae9b5f191cfab2e9aa3c71dad3f9399e6a855606/src/OGLTexture.cpp#L145

It's an emulator so it's not "nice" code, sorry for this

But from a personal side, if you could tell me what is the problem (what it mean by incomplete framebuffer? size? color type? which one?)

Tell me if you need more information. Can I setup mesa to provide more information (verbose?).
Comment 1 Tapani Pälli 2017-09-21 06:06:57 UTC 
I'm seeing a different error with current Mesa master:

--- 8< ---
glretrace: main/teximage.c:806: init_teximage_fields_ms: Assertion `img->_BaseFormat != -1' failed.
--- 8< ---

As a first thought, could you try using glTexImage2D instead of glTexSubImage2D for texture upload? I think the base level of texture is not defined properly if 
glTexStorage2D has not been used to defined the texture.
Comment 2 Dorian Fevrier 2017-09-21 10:29:54 UTC 
Thanks, I will test that!

First little thing, I realize I don't use our `OPENGL_CHECK_ERRORS` macro after `glGenerateMipmap()`. Maybe there is more infos in it.

Second: Is not `glTexSubImage2D()` supposed to generate an error if `glTexImage2D()` hasn't been called before?

http://docs.gl/es2/glTexSubImage2D#errors
Comment 3 Tapani Pälli 2017-09-21 11:46:33 UTC 
(In reply to Dorian Fevrier from comment #2)
> Thanks, I will test that!
> 
> First little thing, I realize I don't use our `OPENGL_CHECK_ERRORS` macro
> after `glGenerateMipmap()`. Maybe there is more infos in it.
> 
> Second: Is not `glTexSubImage2D()` supposed to generate an error if
> `glTexImage2D()` hasn't been called before?
> 
> http://docs.gl/es2/glTexSubImage2D#errors

I did try this on my own test app and it does causes following error:

Mesa: User error: GL_INVALID_OPERATION in glTexSubImage2D(invalid texture level 0)
Comment 4 Tapani Pälli 2017-09-25 07:15:29 UTC 
Based on the discussion and documentation I'm resolving this as NOTOURBUG, you need to first specify texture content before using glTexSubImage2D (which is using to 'respecify content' as reads in the spec).
Comment 5 Dorian Fevrier 2017-09-25 08:32:41 UTC 
Thanks Tapani,

I didn't had the time to test yet. I'm surprise GL_INVALID_OPERATION didn't popup with glTexSubImage2D() on my side like it seems to have pop on your side. I will try with `export MESA_DEBUG=1` to see if there is a difference between our `OPENGL_CHECK_ERRORS` macro and mesa output.

What you say would mean Mesa 17.0.7 raise an implementation error but the master seems to have "fixed" it stating it's an OpenGL error.

I will test.
Comment 6 thanos17997@gmail.com (Spammer; Account disabled) 2019-04-12 07:28:15 UTC 
You have to seen the all setting of device to visit here http://fixwindows10connections.com and fix connections for bluetooth audio devices and wireless displays in windows.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.