Bug 102581

Summary:	3D texture mipmapping broken
Product:	Mesa	Reporter:	Felix Potthast <mail>
Component:	Drivers/Gallium/radeonsi	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:	Default DRI bug account <dri-devel>
Severity:	normal
Priority:	medium
Version:	17.2
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Screenshot comparison Glxinfo output Test program

Description Felix Potthast 2017-09-07 11:19:29 UTC

Created attachment 134041 [details]
Screenshot comparison

When trying to display 
https://www.shadertoy.com/view/4llcR4
i get artifacts near horizon due to mipmapping (artifacts are absent with mipmapping disabled).
It works as expected with the proprietary driver (under Windows) on the same machine.
See attached image for Screenshot comparison.

So either mipmap generation or display seems to be erroneous for 3D textures.

My card is AMD Radeon HD 7870.

Comment 1 Michel Dänzer 2017-09-08 01:42:37 UTC

Please attach the corresponding glxinfo output.

FWIW, not seeing the problem on Kaveri with recent Git master.

Comment 2 Felix Potthast 2017-09-08 18:31:08 UTC

Created attachment 134096 [details]
Glxinfo output

Comment 3 Felix Potthast 2017-09-08 18:32:35 UTC

Added glxinfo attachment.
Also upgraded to Mesa 17.2, but the problem still exists, glxinfo log is from new version.

Comment 4 Nicolai Hähnle 2017-10-10 10:47:10 UTC

Maybe an SI-specific bug? Looks like the bottom part of the screenshot comparison for me on both Carrizo and Tonga (VI) with Git master.

Comment 5 Felix Potthast 2019-02-20 23:04:52 UTC

Created attachment 143426 [details]
Test program

The bug is still present for me with mesa 18.3.4-1
I wrote a little test program which compares an uploaded
3dtexture mipmap with the corresponding output of glGetTexImage.

It should output nothing, but on my desktop pc it outputs:

Error in level 2
Error in level 3
Error in level 4

Compile with "gcc test.c -o test -lglfw -lepoxy"

Comment 6 GitLab Migration User 2019-09-25 18:00:08 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1280.

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.