mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2019-09-18T20:18:29Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/925Black screen when attempting startx2019-09-18T20:18:29ZBugzilla Migration UserBlack screen when attempting startx## Submitted by Alex Kempshall
Assigned to **mes..@..op.org**
**[Link to original bug (#106835)](https://bugs.freedesktop.org/show_bug.cgi?id=106835)**
## Description
Since installing mesa-18.0.4.tar.xz provided by my distro I get...## Submitted by Alex Kempshall
Assigned to **mes..@..op.org**
**[Link to original bug (#106835)](https://bugs.freedesktop.org/show_bug.cgi?id=106835)**
## Description
Since installing mesa-18.0.4.tar.xz provided by my distro I get a black screen when using startx.
The environment I see this on is
Slackware64-Current running in virtualbox.
I have two work arounds
1.
Don't maximise the virtualbox window
2.
add nomodeset as a kernel parameter when booting.
I have downloaded the Mesa git repository and bisected the code and will attach the bisect log
Please advise me if you require any other information.https://gitlab.freedesktop.org/mesa/mesa/-/issues/924Warn about mipmap-incomplete texture being used2019-09-18T20:18:27ZBugzilla Migration UserWarn about mipmap-incomplete texture being used## Submitted by Ruslan Kabatsayev
Assigned to **mes..@..op.org**
**[Link to original bug (#105901)](https://bugs.freedesktop.org/show_bug.cgi?id=105901)**
## Description
Usage of textures with incomplete mipmap is a common OpenGL ...## Submitted by Ruslan Kabatsayev
Assigned to **mes..@..op.org**
**[Link to original bug (#105901)](https://bugs.freedesktop.org/show_bug.cgi?id=105901)**
## Description
Usage of textures with incomplete mipmap is a common OpenGL pitfall [1], since by default GL_TEXTURE_MIN_FILTER is GL_NEAREST_MIPMAP_LINEAR. Thus it'd be very useful if Mesa called debug callbacks on such errors.
A test case can be found in the attachment. When run, it first tries to draw a full-screen textured quad with a mipmap-incomplete texture, and on a key press it toggles TEXTURE_MIN_FILTER between NEAREST and NEAREST_MIPMAP_LINEAR.
Binary nvidia driver gives me a useful debug notification, leading to the following output from the test program on each frame with mipmap-incomplete texture use:
> debug callback called, notification: Texture state usage warning: Texture 1 has no mipmaps, while its min filter requires mipmap.
It would be very useful if Mesa also did this. Currently (as of 17.2) it doesn't emit any relevant messages.
[1]: https://www.opengl.org/archives/resources/features/KilgardTechniques/oglpitfall/
Version: 17.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/923Mesa-utils -8.4 - glxinfo report has a blank value in GL_NUM_SHADING_LANGUAGE...2019-09-18T20:18:21ZBugzilla Migration UserMesa-utils -8.4 - glxinfo report has a blank value in GL_NUM_SHADING_LANGUAGE_VERSIONS subsection and also the aligniment below 4.3 seems not correct## Submitted by Arun Sivaraman
Assigned to **mes..@..op.org**
**[Link to original bug (#105285)](https://bugs.freedesktop.org/show_bug.cgi?id=105285)**
## Description
Created attachment 137681
glxinfo
Hi
The latest version of gl...## Submitted by Arun Sivaraman
Assigned to **mes..@..op.org**
**[Link to original bug (#105285)](https://bugs.freedesktop.org/show_bug.cgi?id=105285)**
## Description
Created attachment 137681
glxinfo
Hi
The latest version of glxinfo displays a blank Value under GL_NUM_SHADING_LANGUAGE_VERSIONS sections, As per the report GL_NUM_SHADING_LANGUAGE_VERSIONS has 26 including the blank else it should be 25. Also, the alignment of GL_VERTEX_PROGRAM_ARB, GL_FRAGMENT_PROGRAM_ARB looks to be under 4.3. I am not sure if its correct. Please confirm
**Attachment 137681**, "glxinfo":
![Screenshot_at_2018-02-28_09-25-34](/uploads/610fd1c7a89bd4f8a81cb58a9b21881c/Screenshot_at_2018-02-28_09-25-34.png)https://gitlab.freedesktop.org/mesa/mesa/-/issues/922Buffer overflow in gallium/auxiliary/hud/hud_cpufreq.c2019-09-18T20:18:18ZBugzilla Migration UserBuffer overflow in gallium/auxiliary/hud/hud_cpufreq.c## Submitted by ves..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#105274)](https://bugs.freedesktop.org/show_bug.cgi?id=105274)**
## Description
It is possible to overflow cpufreq_info::name and cpufreq_info:...## Submitted by ves..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#105274)](https://bugs.freedesktop.org/show_bug.cgi?id=105274)**
## Description
It is possible to overflow cpufreq_info::name and cpufreq_info::sysfs_filename inside add_object function. It require to somehow(ex. inside chroot) create custom directory inside `/sys/devices/system/cpu/` named like cpu0`<custom_data_here>`` and it will pass:
if (sscanf(dp->d_name, "cpu%d\n", &cpu_index) != 1)
continue;
inside hud_get_num_cpufreq function.https://gitlab.freedesktop.org/mesa/mesa/-/issues/921vsync(?) artifact2019-09-18T20:18:14ZBugzilla Migration Uservsync(?) artifact## Submitted by Frank
Assigned to **mes..@..op.org**
**[Link to original bug (#105243)](https://bugs.freedesktop.org/show_bug.cgi?id=105243)**
## Description
Created attachment 137594
Example 1
Hi all! Since about two years (esti...## Submitted by Frank
Assigned to **mes..@..op.org**
**[Link to original bug (#105243)](https://bugs.freedesktop.org/show_bug.cgi?id=105243)**
## Description
Created attachment 137594
Example 1
Hi all! Since about two years (estimated) I really often encounter an artifact which seems like a vsync issue – that is a border due to displaying two frames partly at the same time. This border goes across my screen and always has the same position (a year ago it was more like an upside-down parable, but now it’s a line). I add two screen-shots so you see how it looks. It occurs both in videos, when the camera is moving slowly, and also sometimes if I scroll through text. It is not persistent, but about appears every some seconds.
Video-wise, some sources (like Netflix in Firefox) run smooth, if I recall this correctly – but as far as I remember, all videos I play with Totem/Gnome-MPV/VLC are exposed to that issue – which is also true for watching SkyGo via Firefox (in contrast to Netflix).
I don’t really know where I should file this bug report, so I’ll try here on Mesa, as this happens on both an Intel, as on an AMD system:
Dell XPS 15 9550
• Intel® HD Graphics 530 (Skylake GT2) / NV117 (gnome-control-center output)
• Nouveau for the NVidia card (but I don’t use that card explicitly, so it shouldn’t be used at all, I assume)
• Fedora 24-27
• Wayland
• Mesa 17.2 (but as I said, this occurs since about two years)
AMD APU HTPC
• AMD® A8-7600 radeon r7, 10 compute cores 4c+6g x 4
• Tested with Debian Stretch, Debian Testing & Fedora 27
• Wayland
**Attachment 137594**, "Example 1":
![Bildschirmfoto_von_Â_2018-02-25_19-04-29Â_](/uploads/ffcd8225cef42c6f7e9ceb40f3bfc002/Bildschirmfoto_von_Â_2018-02-25_19-04-29Â_.png)
Version: 17.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/920Libclc warnings "Linking two modules of different data layouts" with LLVM 5 a...2019-09-18T20:18:11ZBugzilla Migration UserLibclc warnings "Linking two modules of different data layouts" with LLVM 5 and 6## Submitted by Luke A. Guest
Assigned to **mes..@..op.org**
**[Link to original bug (#104766)](https://bugs.freedesktop.org/show_bug.cgi?id=104766)**
## Description
Created attachment 136939
Full compile log
I tried to compile l...## Submitted by Luke A. Guest
Assigned to **mes..@..op.org**
**[Link to original bug (#104766)](https://bugs.freedesktop.org/show_bug.cgi?id=104766)**
## Description
Created attachment 136939
Full compile log
I tried to compile libclc against LLVM 6 and got these warnings, then I tried LLVM 5 (branch release_50 in llvm/clang/compiler-rt) and got them still.
This is the end of the build log:
WARNING: Linking two modules of different data layouts: 'nvptx64--nvidiacl/lib/shared/vload_half_helpers.ll.bc' is '' whereas 'llvm-link' is 'e-i64:64-v16:16-v32:32-n16:32:64'
WARNING: Linking two modules of different data layouts: 'nvptx64--nvidiacl/lib/shared/vstore_half_helpers.ll.bc' is '' whereas 'llvm-link' is 'e-i64:64-v16:16-v32:32-n16:32:64'
WARNING: Linking two modules of different data layouts: 'nvptx64--nvidiacl/lib/subnormal_helper_func.ll.bc' is '' whereas 'llvm-link' is 'e-i64:64-v16:16-v32:32-n16:32:64'
LLVM-LINK r600--/lib/builtins.link.cedar.bc
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vload_half_helpers.ll.cedar.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vstore_half_helpers.ll.cedar.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/subnormal_helper_func.ll.cedar.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
LLVM-LINK r600--/lib/builtins.link.cypress.bc
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vload_half_helpers.ll.cypress.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vstore_half_helpers.ll.cypress.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/subnormal_helper_func.ll.cypress.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
LLVM-LINK r600--/lib/builtins.link.barts.bc
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vload_half_helpers.ll.barts.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vstore_half_helpers.ll.barts.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/subnormal_helper_func.ll.barts.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-i64:64-v16:16-v32:32-n16:32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
LLVM-LINK r600--/lib/builtins.link.cayman.bc
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vload_half_helpers.ll.cayman.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/shared/vstore_half_helpers.ll.cayman.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'r600--/lib/subnormal_helper_func.ll.cayman.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
LLVM-LINK amdgcn--/lib/builtins.link.tahiti.bc
WARNING: Linking two modules of different data layouts: 'amdgcn--/lib/shared/vload_half_helpers.ll.tahiti.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'amdgcn--/lib/shared/vstore_half_helpers.ll.tahiti.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'amdgcn--/lib/subnormal_helper_func.ll.tahiti.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
LLVM-LINK amdgcn--amdhsa/lib/builtins.link.bc
WARNING: Linking two modules of different data layouts: 'amdgcn--amdhsa/lib/shared/vload_half_helpers.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'amdgcn--amdhsa/lib/shared/vstore_half_helpers.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'amdgcn--amdhsa/lib/subnormal_helper_func.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
LLVM-LINK amdgcn-mesa-mesa3d/lib/builtins.link.tahiti.bc
WARNING: Linking two modules of different data layouts: 'amdgcn-mesa-mesa3d/lib/shared/vload_half_helpers.ll.tahiti.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'amdgcn-mesa-mesa3d/lib/shared/vstore_half_helpers.ll.tahiti.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'amdgcn-mesa-mesa3d/lib/subnormal_helper_func.ll.tahiti.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
OPT nvptx64--nvidiacl/lib/builtins.opt.bc
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-p1:64:64-p2:64:64-p3:32:32-p4:64:64-p5:32:32-i64:64-v16:16-v24:32-v32:32-v48:64-v96:128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64'
OPT r600--/lib/builtins.opt.cedar.bc
OPT r600--/lib/builtins.opt.cypress.bc
OPT r600--/lib/builtins.opt.barts.bc
OPT r600--/lib/builtins.opt.cayman.bc
OPT amdgcn--/lib/builtins.opt.tahiti.bc
OPT amdgcn--amdhsa/lib/builtins.opt.bc
OPT amdgcn-mesa-mesa3d/lib/builtins.opt.tahiti.bc
LLVM-LINK nvptx--nvidiacl/lib/builtins.link.bc
WARNING: Linking two modules of different data layouts: 'nvptx--nvidiacl/lib/shared/vload_half_helpers.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v32:32-n16:32:64'
WARNING: Linking two modules of different data layouts: 'nvptx--nvidiacl/lib/shared/vstore_half_helpers.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v32:32-n16:32:64'
WARNING: Linking two modules of different data layouts: 'nvptx--nvidiacl/lib/subnormal_helper_func.ll.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v32:32-n16:32:64'
WARNING: Linking two modules of different data layouts: 'generic--/lib/subnormal_use_default.bc' is '' whereas 'llvm-link' is 'e-p:32:32-i64:64-v16:16-v32:32-n16:32:64'
PREPARE-BUILTINS built_libs/cedar-r600--.bc
PREPARE-BUILTINS built_libs/cypress-r600--.bc
PREPARE-BUILTINS built_libs/barts-r600--.bc
PREPARE-BUILTINS built_libs/cayman-r600--.bc
OPT nvptx--nvidiacl/lib/builtins.opt.bc
PREPARE-BUILTINS built_libs/nvptx64--nvidiacl.bc
PREPARE-BUILTINS built_libs/amdgcn--amdhsa.bc
PREPARE-BUILTINS built_libs/tahiti-amdgcn--.bc
PREPARE-BUILTINS built_libs/tahiti-amdgcn-mesa-mesa3d.bc
PREPARE-BUILTINS built_libs/nvptx--nvidiacl.bc
Using this build of clang/llvm:
~/opt/mesa-debug/bin/llvm-config --version
5.0.1
**Attachment 136939**, "Full compile log":
[log.make.txt](/uploads/e45b905d68d8d94f3dded5f80dfe8e01/log.make.txt)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/918Commit 26aee6f4d5 causes crash-loop on android-x86 (surfaceflinger to exit wi...2019-09-18T20:18:00ZBugzilla Migration UserCommit 26aee6f4d5 causes crash-loop on android-x86 (surfaceflinger to exit with status 1)## Submitted by maurossi `@issor.oruam`
Assigned to **mes..@..op.org**
**[Link to original bug (#102227)](https://bugs.freedesktop.org/show_bug.cgi?id=102227)**
## Description
Created attachment 133516
logcat
In attachement a log...## Submitted by maurossi `@issor.oruam`
Assigned to **mes..@..op.org**
**[Link to original bug (#102227)](https://bugs.freedesktop.org/show_bug.cgi?id=102227)**
## Description
Created attachment 133516
logcat
In attachement a logcat/dmesg of not working build on AMD Turks, with
surfaceflinger not liking the egl+gallium_dri combination
and exiting at init in an infinite loop.
[ 29.182766] init: Starting service 'surfaceflinger'...
[ 29.280027] init: Service 'surfaceflinger' (pid 2773) exited with status 1
[ 29.282251] init: Service 'surfaceflinger' (pid 2773) killing any
children in process group
[ 29.284439] init: Service 'zygote' is being killed...
The first bad commit is:
26aee6f4d5a28350e1f6becfc485ce929c4126f9 Android: rework LLVM build support
As a proposal the following two commits can be reverted in mesa 17.2.0rc4
git revert d31a2b4d49274ca362097a9707d9e9a48ea58063
[detached HEAD 455978c029] Revert "Android: Add LLVM support for Android O"
1 file changed, 1 insertion(+), 4 deletions(-)
git revert 26aee6f4d5a28350e1f6becfc485ce929c4126f9
[detached HEAD 70f3377e4e] Revert "Android: rework LLVM build support"
8 files changed, 23 insertions(+), 27 deletions(-)
This will give a working build for nouveau, r600 and all other gallium_dri drivers.
Tested with nougat-x86 on AMD Turks (HD76xx) and Nvidia NVD9 (GT610)
Kind regards
Mauro Rossi
android-x86 team
**Attachment 133516**, "logcat":
[logcat_HD76xx_NOK.txt](/uploads/01db9f26aba58543ca456a2e396a4cd5/logcat_HD76xx_NOK.txt)
Version: 17.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/917st/va raises segmentation fault while using videotestsrc with gstreamer2019-09-18T20:17:57ZBugzilla Migration Userst/va raises segmentation fault while using videotestsrc with gstreamer## Submitted by gur..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#100075)](https://bugs.freedesktop.org/show_bug.cgi?id=100075)**
## Description
Created attachment 130082
gdb backtrace log
gst-launch-1.0 vid...## Submitted by gur..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#100075)](https://bugs.freedesktop.org/show_bug.cgi?id=100075)**
## Description
Created attachment 130082
gdb backtrace log
gst-launch-1.0 videotestsrc \! video/x-raw, format=RGBx \! vaapisink
Running the pipeline causes causes a blank window to open and segmentation fault occurs.
~~**Attachment 130082**~~, "gdb backtrace log":
[vaapi-error.log](/uploads/c2623d2c32bfdb74d0df07ef66ecd930/vaapi-error.log)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/916Segmentation fault when using VAAPI acceleration in VLC after installing oiba...2019-09-18T20:17:53ZBugzilla Migration UserSegmentation fault when using VAAPI acceleration in VLC after installing oibaf's optimized drivers## Submitted by les..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#98275)](https://bugs.freedesktop.org/show_bug.cgi?id=98275)**
## Description
VLC media player 2.2.4 Weatherwax (revision 2.2.3-37-g888b7e89)
[...## Submitted by les..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#98275)](https://bugs.freedesktop.org/show_bug.cgi?id=98275)**
## Description
VLC media player 2.2.4 Weatherwax (revision 2.2.3-37-g888b7e89)
[00000000017c1088] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[00000000017d5b38] core playlist: stopping playback
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
Segmentation fault
dmesg:
[138451.878863] vlc[10533]: segfault at 7fcf170d3000 ip 00007fcf54540034 sp 00007fcf260a9080 error 4 in libLLVM-3.9.so.1[7fcf53f2f000+287b000]https://gitlab.freedesktop.org/mesa/mesa/-/issues/915[VDPAU]: artifacts when trying video sharpening and noise-reduction before CSC2019-09-18T20:17:52ZBugzilla Migration User[VDPAU]: artifacts when trying video sharpening and noise-reduction before CSC## Submitted by Nayan Deshmukh
Assigned to **mes..@..op.org**
**[Link to original bug (#97525)](https://bugs.freedesktop.org/show_bug.cgi?id=97525)**
## Description
When we apply noise reduction or sharpness filters before CSC, it...## Submitted by Nayan Deshmukh
Assigned to **mes..@..op.org**
**[Link to original bug (#97525)](https://bugs.freedesktop.org/show_bug.cgi?id=97525)**
## Description
When we apply noise reduction or sharpness filters before CSC, it leads to various chroma effects. I had submitted patches for this change to the list and had a discussion of the possible reasons for this. I attaching a link to our conversation.
https://lists.freedesktop.org/archives/mesa-dev/2016-August/125735.htmlhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/914Odd video decode tearing2019-09-18T20:17:50ZBugzilla Migration UserOdd video decode tearing## Submitted by jos..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#97048)](https://bugs.freedesktop.org/show_bug.cgi?id=97048)**
## Description
Created attachment 125256
Screen Shot
Videos seem to have a weir...## Submitted by jos..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#97048)](https://bugs.freedesktop.org/show_bug.cgi?id=97048)**
## Description
Created attachment 125256
Screen Shot
Videos seem to have a weird video decode tearing and I finally got a good example! In the video, there's a bottom bar which is the previous frame, as well as a square in the middle.
**Attachment 125256**, "Screen Shot":
![unusual_screen_tearing](/uploads/1fc99fffa60712604c7af536a5fb080d/unusual_screen_tearing.png)
Version: 11.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/91210 bit h264 OMX UVD decode outputs NV122019-09-18T20:17:44ZBugzilla Migration User10 bit h264 OMX UVD decode outputs NV12## Submitted by Andy Furniss
Assigned to **mes..@..op.org**
**[Link to original bug (#92570)](https://bugs.freedesktop.org/show_bug.cgi?id=92570)**
## Description
No idea if this a Mesa OMX issue or UVD or gstreamer -
GPU is R9 2...## Submitted by Andy Furniss
Assigned to **mes..@..op.org**
**[Link to original bug (#92570)](https://bugs.freedesktop.org/show_bug.cgi?id=92570)**
## Description
No idea if this a Mesa OMX issue or UVD or gstreamer -
GPU is R9 285 Tonga.
In theory this should be able to h/w decode 10 bit h264 - and the h/w does seem to process it.
The problem is that something is assuming/expecting/indicating that the output is NV12, so the output is corrupted.
Here's a snip of a debug output from doing -
GST_DEBUG=*:4 gst-launch-1.0 -f filesrc location=A-10bit-h264.mkv ! matroskademux ! h264parse ! omxh264dec ! filesink location=out.yuv
0:00:00.364695565 660 0x22310f0 INFO GST_EVENT gstevent.c:679:gst_event_new_caps: creating caps event video/x-h264, level=(string)4.1, profile=(string)high-10, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1920, height=(int)1080, framerate=(fraction)30000/1001, parsed=(boolean)true
`<snip>`
gstpad.c:5881:gst_pad_start_task:<omxh264dec-omxh264dec0:src> created task 0x22f85f0
0:00:00.366822661 660 0x2231590 INFO GST_EVENT
gstevent.c:679:gst_event_new_caps: creating caps event video/x-raw, format=(string)NV12, width=(int)1920, height=(int)1080, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1, chroma-site=(string)mpeg2, colorimetry=(string)bt709, framerate=(fraction)30000/1001
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/911wglCreatePbufferARB handle attrib error2019-09-18T20:17:42ZBugzilla Migration UserwglCreatePbufferARB handle attrib error## Submitted by zeif
Assigned to **mes..@..op.org**
**[Link to original bug (#92020)](https://bugs.freedesktop.org/show_bug.cgi?id=92020)**
## Description
HPBUFFERARB WINAPI
wglCreatePbufferARB(HDC hCurrentDC,
...## Submitted by zeif
Assigned to **mes..@..op.org**
**[Link to original bug (#92020)](https://bugs.freedesktop.org/show_bug.cgi?id=92020)**
## Description
HPBUFFERARB WINAPI
wglCreatePbufferARB(HDC hCurrentDC,
int iPixelFormat,
int iWidth,
int iHeight,
const int *piAttribList)
{
//......
for (piAttrib = piAttribList; *piAttrib; piAttrib++) {
switch (*piAttrib) {
case WGL_PBUFFER_LARGEST_ARB:
piAttrib++;
useLargest = *piAttrib;
break;
default:
SetLastError(ERROR_INVALID_DATA);
return 0;// <-- delete this
}
}
//.....
}
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/910gallium xvmc tries to symlink non existing libraries on OpenBSD2020-08-31T05:08:47ZBugzilla Migration Usergallium xvmc tries to symlink non existing libraries on OpenBSD## Submitted by Jonathan Gray
Assigned to **mes..@..op.org**
**[Link to original bug (#91385)](https://bugs.freedesktop.org/show_bug.cgi?id=91385)**
## Description
The gallium xvmc Makefile assumes the system uses Linux style libr...## Submitted by Jonathan Gray
Assigned to **mes..@..op.org**
**[Link to original bug (#91385)](https://bugs.freedesktop.org/show_bug.cgi?id=91385)**
## Description
The gallium xvmc Makefile assumes the system uses Linux style library names with
libfoo.so.major.minor.revision with symlinks to libfoo.so.major.minor and libfoo.so.major.
On OpenBSD libtool creates libfoo.so.major.minor even if revision is specified and ld.so will find the appropriate library if libfoo.so or libfoo.so.major is dlopen'd.
gmake[5]: Entering directory '/usr/users/jsg/src/mesa/src/gallium/targets/xvmc'
dest_dir=//usr/X11R6/lib; \
for i in r600; do \
j=libXvMCgallium.so; \
k=libXvMC${i}.so; \
l=${k}.1.0.0; \
ln -f ${dest_dir}/${j}.1.0.0 \
${dest_dir}/${l}; \
ln -sf ${l} \
${dest_dir}/${k}.1.0; \
ln -sf ${l} \
${dest_dir}/${k}.1; \
ln -sf ${l} \
${dest_dir}/${k}; \
done; \
rm -f ${dest_dir}/libXvMCgallium.*
ln: //usr/X11R6/lib/libXvMCgallium.so.1.0.0: No such file or directory
$ find src/gallium/ -name "*XvMC*"
src/gallium/targets/xvmc-softpipe/.libs/libXvMCsoftpipe.lai
src/gallium/targets/xvmc-softpipe/.libs/libXvMCsoftpipe.so.1.0
src/gallium/targets/xvmc-softpipe/.libs/libXvMCsoftpipe.la
src/gallium/targets/xvmc-softpipe/libXvMCsoftpipe.la
src/gallium/targets/xvmc-r300/.libs/libXvMCr300.so.1.0
src/gallium/targets/xvmc-r300/.libs/libXvMCr300.lai
src/gallium/targets/xvmc-r300/.libs/libXvMCr300.la
src/gallium/targets/xvmc-r300/libXvMCr300.la
src/gallium/targets/xvmc-r600/.libs/libXvMCr600.lai
src/gallium/targets/xvmc-r600/.libs/libXvMCr600.so.1.0
src/gallium/targets/xvmc-r600/.libs/libXvMCr600.la
src/gallium/targets/xvmc-r600/libXvMCr600.la
src/gallium/targets/xvmc/.deps/libXvMCgallium_la-dummy.Plo
src/gallium/targets/xvmc/.deps/libXvMCgallium_la-target.Plo
src/gallium/targets/xvmc/.libs/libXvMCgallium_la-target.o
src/gallium/targets/xvmc/.libs/libXvMCgallium.so.1.0
src/gallium/targets/xvmc/.libs/libXvMCgallium.lai
src/gallium/targets/xvmc/.libs/libXvMCgallium.la
src/gallium/targets/xvmc/libXvMCgallium.la
src/gallium/targets/xvmc/libXvMCgallium_la-target.lo
It seems the Makefile has already wrongly installed
libXvMCr600.so and libXvMCr600.so.1 into the prefix
and correctly installed libXvMCr600.so.1.0 when the error occurs.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/909Mesa 10.4.0-devel implementation error: unexpected format GL_DEPTH24_STENCIL8...2019-09-18T20:17:38ZBugzilla Migration UserMesa 10.4.0-devel implementation error: unexpected format GL_DEPTH24_STENCIL8 in _mesa_choose_tex_format()## Submitted by big..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#86480)](https://bugs.freedesktop.org/show_bug.cgi?id=86480)**
## Description
Trying to get Starcraft 1 running on Lubuntu, using Wine 1.7.31, ...## Submitted by big..@..il.com
Assigned to **mes..@..op.org**
**[Link to original bug (#86480)](https://bugs.freedesktop.org/show_bug.cgi?id=86480)**
## Description
Trying to get Starcraft 1 running on Lubuntu, using Wine 1.7.31, I get this error in the console:
Mesa 10.4.0-devel implementation error: unexpected format GL_DEPTH24_STENCIL8 in _mesa_choose_tex_format()
The screen goes black, sometimes with dark blue on a diagonal half. The sound does seem to be working fine though.
Renderer: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
Version: 1.3 Mesa 10.4.0-devel
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=79841https://gitlab.freedesktop.org/mesa/mesa/-/issues/908glClear can hang when the window being rendered is concurrently closed2019-09-18T20:17:35ZBugzilla Migration UserglClear can hang when the window being rendered is concurrently closed## Submitted by Steven Stewart-Gallus
Assigned to **mes..@..op.org**
**[Link to original bug (#85712)](https://bugs.freedesktop.org/show_bug.cgi?id=85712)**
## Description
Created attachment 108740
Callstack
**Attachment 108740...## Submitted by Steven Stewart-Gallus
Assigned to **mes..@..op.org**
**[Link to original bug (#85712)](https://bugs.freedesktop.org/show_bug.cgi?id=85712)**
## Description
Created attachment 108740
Callstack
**Attachment 108740**, "Callstack":
[file_85712.txt](/uploads/6d5a4b34ab8eae2ed784de9e9ccb765b/file_85712.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/907Blender game engine "Motion Blur" filter doesn't work2019-09-18T20:17:32ZBugzilla Migration UserBlender game engine "Motion Blur" filter doesn't work## Submitted by khalidsrri
Assigned to **mes..@..op.org**
**[Link to original bug (#83580)](https://bugs.freedesktop.org/show_bug.cgi?id=83580)**
## Description
Created attachment 105854
Test file with Motion Blur
Hi ,
I use bot...## Submitted by khalidsrri
Assigned to **mes..@..op.org**
**[Link to original bug (#83580)](https://bugs.freedesktop.org/show_bug.cgi?id=83580)**
## Description
Created attachment 105854
Test file with Motion Blur
Hi ,
I use both Windows 7 and Ubuntu 14.04
I have a problem with "Motion blur" in the Blender game engine
After I asked Blender Community they told me that may be there are a problem with Accumulation buffer (glAccum function) , Which necessary for this feature to work
I tested it in three different Blender version , but doesn't work .
it worked very well in Win7 and in another computer with Linux Mint and different Graphical card
GPU : Intel HD
CPU : Intel Celeron P4600
There are a .blend file attached with Motion Blur filter
To test it open the file and press P
**Attachment 105854**, "Test file with Motion Blur":
[motionblur.blend](/uploads/e6bc7b9afd6d4972921db5dabc427cf3/motionblur.blend)
Version: 10.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/905Heap-buffer-overflow WRITE in memcpy_texture2019-09-18T20:17:24ZBugzilla Migration UserHeap-buffer-overflow WRITE in memcpy_texture## Submitted by Abhishek Arya
Assigned to **mes..@..op.org**
**[Link to original bug (#75814)](https://bugs.freedesktop.org/show_bug.cgi?id=75814)**
## Description
I am running into this when launching chrome built with AddressSan...## Submitted by Abhishek Arya
Assigned to **mes..@..op.org**
**[Link to original bug (#75814)](https://bugs.freedesktop.org/show_bug.cgi?id=75814)**
## Description
I am running into this when launching chrome built with AddressSanitizer memory debugging tool on Ubuntu Saucy.
=================================================================
==3110==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000018101 at pc 0x4897f6 bp 0x7fff8f1918e0 sp 0x7fff8f191098
WRITE of size 4 at 0x603000018101 thread T0 (content_shell)
#0 0x4897f5 in __interceptor_memcpy /usr/local/google/work/chromium/src/third_party/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:374
#1 0x7f3481c6a9f5 in memcpy /usr/include/x86_64-linux-gnu/bits/string3.h:51
#2 0x7f3481c6a9f5 in memcpy_texture /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/main/texstore.c:960
#3 0x7f3481c6fd84 in _mesa_texstore_memcpy /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/main/texstore.c:3855
#4 0x7f3481c6fd84 in _mesa_texstore /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/main/texstore.c:3874
#5 0x7f3481c70051 in store_texsubimage /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/main/texstore.c:4022
#6 0x7f348169f179 in st_TexSubImage /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/state_tracker/st_cb_texture.c:789
#7 0x7f348169fc02 in st_TexImage /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/state_tracker/st_cb_texture.c:813
#8 0x7f3481c5e8eb in teximage /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/main/teximage.c:3166
#9 0x7f3481c5fb5f in _mesa_TexImage2D /build/buildd/mesa-9.2.1/build/dri/src/mesa/libdricore/../../../../../src/mesa/main/teximage.c:3205
#10 0x85ca65e in gfx::(anonymous namespace)::CustomTexImage2D(unsigned int, int, int, int, int, int, unsigned int, unsigned int, void const*) /b/build/slave/ASAN_Release/build/src/out/Release/../../ui/gl/gl_gl_api_implementation.cc:131
#11 0x85faba4 in gfx::GLApiBase::glTexImage2DFn(unsigned int, int, int, int, int, int, unsigned int, unsigned int, void const*) /b/build/slave/ASAN_Release/build/src/out/Release/gen/ui/gl/gl_bindings_autogen_gl.cc:3283
#12 0x84fa97e in gpu::gles2::TextureManager::CreateDefaultAndBlackTextures(unsigned int, unsigned int*) /b/build/slave/ASAN_Release/build/src/out/Release/../../gpu/command_buffer/service/texture_manager.cc:922
#13 0x84f975e in gpu::gles2::TextureManager::Initialize() /b/build/slave/ASAN_Release/build/src/out/Release/../../gpu/command_buffer/service/texture_manager.cc:881
#14 0x83c6f4a in gpu::gles2::ContextGroup::Initialize(gpu::gles2::GLES2Decoder*, gpu::gles2::DisallowedFeatures const&) /b/build/slave/ASAN_Release/build/src/out/Release/../../gpu/command_buffer/service/context_group.cc:240
#15 0x83f3500 in gpu::gles2::GLES2DecoderImpl::Initialize(scoped_refptr<gfx::GLSurface> const&, scoped_refptr<gfx::GLContext> const&, bool, gfx::Size const&, gpu::gles2::DisallowedFeatures const&, std::vector<int, std::allocator`<int>` > const&) /b/build/slave/ASAN_Release/build/src/out/Release/../../gpu/command_buffer/service/gles2_cmd_decoder.cc:2257
#16 0x7fd1a2e in content::GpuCommandBufferStub::OnInitialize(base::FileDescriptor, IPC::Message*) /b/build/slave/ASAN_Release/build/src/out/Release/../../content/common/gpu/gpu_command_buffer_stub.cc:499
#17 0x7fe1018 in DispatchToMethod<content::GpuCommandBufferStub, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message *), base::FileDescriptor, IPC::Message &> /b/build/slave/ASAN_Release/build/src/out/Release/../../base/tuple.h:803
#18 0x7fe1018 in bool IPC::SyncMessageSchema<Tuple1<base::FileDescriptor>, Tuple2<bool&, gpu::Capabilities&> >::DispatchDelayReplyWithSendParams<content::GpuCommandBufferStub, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message*)>(bool, Tuple1<base::FileDescriptor> const&, IPC::Message const*, content::GpuCommandBufferStub*, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message*)) /b/build/slave/ASAN_Release/build/src/out/Release/../../ipc/ipc_message_utils.h:845
#19 0x7fce175 in DispatchDelayReply<content::GpuCommandBufferStub, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message *)> /b/build/slave/ASAN_Release/build/src/out/Release/../../content/common/gpu/gpu_messages.h:507
#20 0x7fce175 in content::GpuCommandBufferStub::OnMessageReceived(IPC::Message const&) /b/build/slave/ASAN_Release/build/src/out/Release/../../content/common/gpu/gpu_command_buffer_stub.cc:188
#21 0x7f8a613 in content::MessageRouter::RouteMessage(IPC::Message const&) /b/build/slave/ASAN_Release/build/src/out/Release/../../content/common/message_router.cc:49
#22 0x7fb741f in content::GpuChannel::HandleMessage() /b/build/slave/ASAN_Release/build/src/out/Release/../../content/common/gpu/gpu_channel.cc:753
#23 0x68df68 in Run /b/build/slave/ASAN_Release/build/src/out/Release/../../base/callback.h:401
#24 0x68df68 in base::MessageLoop::RunTask(base::PendingTask const&) /b/build/slave/ASAN_Release/build/src/out/Release/../../base/message_loop/message_loop.cc:447
#25 0x690554 in DeferOrRunPendingTask /b/build/slave/ASAN_Release/build/src/out/Release/../../base/message_loop/message_loop.cc:459
#26 0x690554 in base::MessageLoop::DoWork() /b/build/slave/ASAN_Release/build/src/out/Release/../../base/message_loop/message_loop.cc:573
#27 0x69a46c in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) /b/build/slave/ASAN_Release/build/src/out/Release/../../base/message_loop/message_pump_default.cc:32
#28 0x68cbab in base::MessageLoop::RunHandler() /b/build/slave/ASAN_Release/build/src/out/Release/../../base/message_loop/message_loop.cc:397
#29 0x6c7584 in base::RunLoop::Run() /b/build/slave/ASAN_Release/build/src/out/Release/../../base/run_loop.cc:49
#30 0x68aea2 in base::MessageLoop::Run() /b/build/slave/ASAN_Release/build/src/out/Release/../../base/message_loop/message_loop.cc:290
#31 0x6d8b8fe in content::GpuMain(content::MainFunctionParams const&) /b/build/slave/ASAN_Release/build/src/out/Release/../../content/gpu/gpu_main.cc:343
#32 0x5ef614 in content::RunNamedProcessTypeMain(std::string const&, content::MainFunctionParams const&, content::ContentMainDelegate*) /b/build/slave/ASAN_Release/build/src/out/Release/../../content/app/content_main_runner.cc:474
#33 0x5f0ea7 in content::ContentMainRunnerImpl::Run() /b/build/slave/ASAN_Release/build/src/out/Release/../../content/app/content_main_runner.cc:794
#34 0x5ed6af in content::ContentMain(int, char const**, content::ContentMainDelegate*) /b/build/slave/ASAN_Release/build/src/out/Release/../../content/app/content_main.cc:35
#35 0x4b3c87 in main /b/build/slave/ASAN_Release/build/src/out/Release/../../content/shell/app/shell_main.cc:35
#36 0x7f348cc6cde4 in __libc_start_main /build/buildd/eglibc-2.17/csu/libc-start.c:260
#37 0x4b3aec in _start (/mnt/scratch0/clusterfuzz/slave-bot/builds/chromium-browser-asan_linux-release/revisions/asan-linux-release-254392/content_shell+0x4b3aec)
0x603000018101 is located 0 bytes to the right of 1-byte region [0x603000018100,0x603000018101)
allocated by thread T0 (content_shell) here:
#0 0x49c478 in __interceptor_posix_memalign /usr/local/google/work/chromium/src/third_party/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:132
#1 0x7f34821920fc in os_malloc_aligned /build/buildd/mesa-9.2.1/build/dri/src/gallium/drivers/llvmpipe/../../../../../../src/gallium/auxiliary/os/os_memory_stdc.h:58
#2 0x7f34821920fc in alloc_image_data /build/buildd/mesa-9.2.1/build/dri/src/gallium/drivers/llvmpipe/../../../../../../src/gallium/drivers/llvmpipe/lp_texture.c:777
SUMMARY: AddressSanitizer: heap-buffer-overflow /usr/local/google/work/chromium/src/third_party/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:374 __interceptor_memcpy
Shadow bytes around the buggy address:
0x0c067fffafd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c067fffafe0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c067fffaff0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c067fffb000: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c067fffb010: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c067fffb020:[01]fa fa fa fa fa 00 00 00 00 fa fa 00 00 00 00
0x0c067fffb030: fa fa 00 00 00 00 fa fa 00 00 00 00 fa fa fd fd
0x0c067fffb040: fd fd fa fa fd fd fd fd fa fa 00 00 00 00 fa fa
0x0c067fffb050: 00 00 00 00 fa fa 00 00 00 00 fa fa fd fd fd fd
0x0c067fffb060: fa fa 00 00 00 00 fa fa fd fd fd fa fa fa fd fd
0x0c067fffb070: fd fd fa fa fd fd fd fd fa fa fd fd fd fd fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Contiguous container OOB:fc
ASan internal: fe
==3110==ABORTING
[3093:3093:0305/220856:13103432475:ERROR:command_buffer_proxy_impl.cc(160)] Could not send GpuCommandBufferMsg_Initialize.https://gitlab.freedesktop.org/mesa/mesa/-/issues/904Blitting a partial region to the front buffer produces corrupted display2019-09-18T20:17:22ZBugzilla Migration UserBlitting a partial region to the front buffer produces corrupted display## Submitted by Federico Mena Quintero `@federico`
Assigned to **mes..@..op.org**
**[Link to original bug (#75545)](https://bugs.freedesktop.org/show_bug.cgi?id=75545)**
## Description
For the original bug behind this, please see ...## Submitted by Federico Mena Quintero `@federico`
Assigned to **mes..@..op.org**
**[Link to original bug (#75545)](https://bugs.freedesktop.org/show_bug.cgi?id=75545)**
## Description
For the original bug behind this, please see https://bugzilla.gnome.org/show_bug.cgi?id=674208
In Gnome apps, including gnome-shell, Clutter and Cogl try to avoid doing a full-screen update on every rendered frame by just doing a glBlitFramebuffer() of the dirty region from the back buffer to the front buffer. The idea is that with software rendering, Mesa will do an XPutImage() of small regions, instead of the whole screen, to minimize the amount of data transferred to the (possibly remote) X server. However, this is broken in drisw, and has been for a couple of years now.
This piglit test exposes the bug (needs to be run with LIBGL_ALWAYS_SOFTWARE=1):
http://lists.freedesktop.org/archives/piglit/2014-February/009701.html
Version: 9.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/902glinfo causes X11 to freeze2019-09-18T20:17:10ZBugzilla Migration Userglinfo causes X11 to freeze## Submitted by Matthew Cline
Assigned to **mes..@..op.org**
**[Link to original bug (#66633)](https://bugs.freedesktop.org/show_bug.cgi?id=66633)**
## Description
Created attachment 82104
xorg.conf
I tried using the program glin...## Submitted by Matthew Cline
Assigned to **mes..@..op.org**
**[Link to original bug (#66633)](https://bugs.freedesktop.org/show_bug.cgi?id=66633)**
## Description
Created attachment 82104
xorg.conf
I tried using the program glinfo of the glxinfo package. A new window appeared, but only the window-manager decoration parts; the actual content was blank. The mouse and keyboard no longer responded. A few seconds later the screen filled with a repeating wavy grey pattern. I've found no relevant information in any log files. The console-only program glxinfo from the same package works fine.
I'm using Mageia 3, with the following relevant packages:
x11-server-xorg-1.13.4-2
x11-driver-video-nv-2.1.20-3 (the NVidia driver)
mesa-9.1.3-1.1 (OpenGL)
glxinfo-8.1.0-1
**Attachment 82104**, "xorg.conf":
[xorg.conf](/uploads/9e350865906e6a1a256996c2df3f1835/xorg.conf)
Version: 9.1