dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 75784] New: Octodad: Dadliest Catch - GPU crash on CAYMAN
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=75784 Priority: medium Bug ID: 75784 Assignee: dri-devel(a)lists.freedesktop.org Summary: Octodad: Dadliest Catch - GPU crash on CAYMAN Severity: normal Classification: Unclassified OS: All Reporter: v10lator(a)myway.de Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 95129 --> https://bugs.freedesktop.org/attachment.cgi?id=95129&action=edit dmesg messages This seems to be caused by R600_DEBUG=sb, with R600_DEBUG=nosb the game seems to run fine. Tested on a Radeon HD 6950. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 75766] New: Unigine: LLVM ERROR: Not supported instr: <MCInst 366 <MCOperand Expr:(LBB0_16)> <MCOperand Reg:24>>
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=75766 Priority: medium Bug ID: 75766 Assignee: dri-devel(a)lists.freedesktop.org Summary: Unigine: LLVM ERROR: Not supported instr: <MCInst 366 <MCOperand Expr:(LBB0_16)> <MCOperand Reg:24>> Severity: normal Classification: Unclassified OS: All Reporter: commiethebeastie(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa LLVM-3.5~svn197556 R600_LLVM_COMPILER=enabled ./valley Loading "libGPUMonitor_x64.so"... Loading "libGL.so.1"... Loading "libopenal.so.1"... Set 1920x1080 fullscreen video mode Set 1.00 gamma value Unigine engine http://unigine.com/ Binary: Linux 64bit GCC 4.4.5 Release Feb 14 2013 r11294 Features: OpenGL OpenAL XPad360 Joystick Flash Editor ---- System ---- System: Linux 3.13.0-14-generic x86_64 CPU: AMD FX(tm)-8120 Eight-Core Processor 4013MHz MMX+ SSE SSE2 SSE3 SSSE3 SSE41 SSE42 SSE4A SSE5 AVX HTT x8 GPU: Unknown GPU x1 System memory: 15983 MB Video memory: 256 MB Sync threads: 7 Async threads: 8 ---- MathLib ---- Set SSE2 simd processor ---- Sound ---- Renderer: OpenAL Soft OpenAL vendor: OpenAL Community OpenAL renderer: OpenAL Soft OpenAL version: 1.1 ALSOFT 1.14 Found AL_EXT_LINEAR_DISTANCE Found AL_EXT_OFFSET Found ALC_EXT_EFX Found EFX Filter Found EFX Reverb Found EAX Reverb Found QUAD16 format Found 51CHN16 format Found 61CHN16 format Found 71CHN16 format Maximum sources: 256 Maximum effect slots: 4 Maximum auxiliary sends: 2 ---- Render ---- GLRender::GLRender(): Unknown GPU OpenGL vendor: X.Org OpenGL renderer: Gallium 0.4 on AMD BARTS OpenGL version: 3.3 (Core Profile) Mesa 10.2.0-devel (git-cbacee2) OpenGL flags: Core Profile Found required GL_ARB_map_buffer_range Found required GL_ARB_vertex_array_object Found required GL_ARB_draw_instanced Found required GL_ARB_draw_elements_base_vertex Found required GL_ARB_transform_feedback Found required GL_ARB_half_float_vertex Found required GL_ARB_half_float_pixel Found required GL_ARB_framebuffer_object Found required GL_ARB_texture_multisample Found required GL_ARB_uniform_buffer_object Found required GL_ARB_geometry_shader4 Found optional GL_ARB_blend_func_extended Found optional GL_ARB_shader_bit_encoding Found optional GL_EXT_texture_compression_s3tc Found optional GL_ARB_texture_compression_rgtc Shading language: 3.30 Maximum texture size: 16384 Maximum texture units: 48 Maximum texture renders: 8 ---- Physics ---- Physics: Multi-threaded ---- PathFind ---- PathFind: Multi-threaded GPUMonitorPlugin::init(): can't initialize GPUMonitor EnginePlugins::init(): can't initialize "GPUMonitor" plugin ---- Interpreter ---- Version: 2.52 Loading "valley/unigine.cpp" 58ms Loading "valley/locale/unigine.en" dictionary Loading "core/materials/default/unigine_post.mat" 23 materials 50 shaders 7ms Loading "core/materials/default/unigine_render.mat" 47 materials 2368 shaders 11ms Loading "core/materials/default/unigine_mesh.mat" 5 materials 3386 shaders 16ms Loading "core/materials/default/unigine_mesh_lut.mat" 2 materials 1062 shaders 4ms Loading "core/materials/default/unigine_mesh_paint.mat" 2 materials 1158 shaders 7ms Loading "core/materials/default/unigine_mesh_tessellation.mat" 5 materials 3332 shaders 16ms Loading "core/materials/default/unigine_mesh_tessellation_paint.mat" 2 materials 2276 shaders 9ms Loading "core/materials/default/unigine_mesh_triplanar.mat" 1 material 112 shaders 2ms Loading "core/materials/default/unigine_mesh_overlap.mat" 1 material 300 shaders 3ms Loading "core/materials/default/unigine_mesh_terrain.mat" 1 material 813 shaders 4ms Loading "core/materials/default/unigine_mesh_layer.mat" 1 material 84 shaders 1ms Loading "core/materials/default/unigine_mesh_noise.mat" 1 material 106 shaders 2ms Loading "core/materials/default/unigine_mesh_stem.mat" 2 materials 2180 shaders 16ms Loading "core/materials/default/unigine_mesh_wire.mat" 1 material 45 shaders 1ms Loading "core/materials/default/unigine_terrain.mat" 1 material 1980 shaders 7ms Loading "core/materials/default/unigine_grass.mat" 2 materials 474 shaders 5ms Loading "core/materials/default/unigine_particles.mat" 1 material 109 shaders 2ms Loading "core/materials/default/unigine_billboard.mat" 1 material 51 shaders 1ms Loading "core/materials/default/unigine_billboards.mat" 2 materials 840 shaders 4ms Loading "core/materials/default/unigine_volume.mat" 6 materials 53 shaders 9ms Loading "core/materials/default/unigine_gui.mat" 1 material 82 shaders 0ms Loading "core/materials/default/unigine_water.mat" 1 material 533 shaders 24ms Loading "core/materials/default/unigine_sky.mat" 1 material 21 shaders 18ms Loading "core/materials/default/unigine_decal.mat" 1 material 99 shaders 1ms Loading "core/properties/unigine.prop" 2 properties 0ms Unigine Valley Benchmark 1.0 (1.0)Unigine~# world_load valley/valley Loading "valley/valley.cpp" 170ms Loading "valley/valley.mat" 72 materials 1615ms Loading "valley/sound/sound.prop" 142 properties 2ms Loading "valley/valley.world" 3153ms LLVM ERROR: Not supported instr: <MCInst 366 <MCOperand Expr:(LBB0_16)> <MCOperand Reg:24>> AL lib: ReleaseALC: 1 device not closed -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 75732] New: Memory leak with celestia
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=75732 Priority: medium Bug ID: 75732 Assignee: dri-devel(a)lists.freedesktop.org Summary: Memory leak with celestia Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rankincj(a)googlemail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa This bug might be a duplicate of #74549. However, WoW + Wine + Valgrind is currently proving to be an intractable problem, and so I've decided to Valgrind celestia instead (since at least I've managed to get THAT to running again on x86_64!!!!!!!) For this test, git HEAD was set to: commit 9bace99d77642f8fbd46b1f0be025ad758f83f5e Author: Zack Rusin <zackr(a)vmware.com> Date: Tue Jan 28 16:34:18 2014 -0500 gallivm: fix opcode and function nesting I executed the following command: $ valgrind --leak-check=full celestia and amidst all of the other issues that Valgrind complained about, it also happened to mention this: ==7446== 352 bytes in 1 blocks are possibly lost in loss record 8,803 of 9,718 ==7446== at 0x4C291D4: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==7446== by 0x4011C44: _dl_allocate_tls (dl-tls.c:296) ==7446== by 0xBEE8862: pthread_create@@GLIBC_2.2.5 (allocatestack.c:580) ==7446== by 0x22F18208: pipe_thread_create.constprop.7 (threads_posix.h:264) ==7446== by 0x22F18B47: radeon_drm_winsys_create (radeon_drm_winsys.c:661) ==7446== by 0x22BA18F5: create_screen (drm_target.c:38) ==7446== by 0x22F13876: dri2_init_screen (dri2.c:1044) ==7446== by 0x22BA295F: driCreateNewScreen2 (dri_util.c:158) ==7446== by 0x52DC260: dri2CreateScreen (dri2_glx.c:1240) ==7446== by 0x52B67E8: __glXInitialize (glxext.c:778) ==7446== by 0x52B31AA: GetGLXPrivScreenConfig.part.2 (glxcmds.c:174) ==7446== by 0x52B392F: glXChooseVisual (glxcmds.c:170) ==7446== ==7446== 360 bytes in 5 blocks are possibly lost in loss record 8,811 of 9,718 ==7446== at 0x4C291D4: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==7446== by 0xA24CEC6: g_malloc0 (in /usr/lib64/libglib-2.0.so.0.3800.2) ==7446== by 0x9FBC1D4: g_closure_new_simple (in /usr/lib64/libgobject-2.0.so.0.3800.2) ==7446== by 0x9FBD671: g_cclosure_new (in /usr/lib64/libgobject-2.0.so.0.3800.2) ==7446== by 0x781E83F: gtk_action_group_add_toggle_actions_full (in /usr/lib64/libgtk-x11-2.0.so.0.2400.22) ==7446== by 0x4623F5: main (in /usr/bin/celestia) -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 75699] New: mplayer crashes
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=75699 Priority: medium Bug ID: 75699 Assignee: dri-devel(a)lists.freedesktop.org Summary: mplayer crashes Severity: normal Classification: Unclassified OS: Linux (All) Reporter: slash(a)ac.auone-net.jp Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 95013 --> https://bugs.freedesktop.org/attachment.cgi?id=95013&action=edit backtrace If I play any file with mplayer -vo vdpau -vf flip, it crashes with sigsegv instantly. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 75602] New: Unigine Heaven/Vally: Multi monitor rendering does not work
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=75602 Priority: medium Bug ID: 75602 Assignee: dri-devel(a)lists.freedesktop.org Summary: Unigine Heaven/Vally: Multi monitor rendering does not work Severity: normal Classification: Unclassified OS: Linux (All) Reporter: knut.tidemann(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 94870 --> https://bugs.freedesktop.org/attachment.cgi?id=94870&action=edit Unigine vally output When trying to start the unigine demos with multiple monitors enabled (Wall 2x1 or any other of the options in the launch dialog), it will exit with a failure. It seems that Mesa is using the compatability context which is limited to OpenGL 3.0. I've attached the output log of Unigine Vally when started with multi monitor enabled. The demos run fine when only a single monitor is enabled. I'm currently using mesa-git g085f61b and linux 3.13.5 on Arch Linux with a Radeon 5730. The same issue can be seen when I try to enable dual output stereo 3D, which should start two separate windows that it will render to. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 75112] New: Meta Bug for HyperZ issues on r600g and radeonsi
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=75112 Priority: medium Bug ID: 75112 Assignee: dri-devel(a)lists.freedesktop.org Summary: Meta Bug for HyperZ issues on r600g and radeonsi Severity: normal Classification: Unclassified OS: All Reporter: andreas.boll.dev(a)gmail.com Hardware: All Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa This bug is for tracking all the outstanding HyperZ issues on r600g and radeonsi. -- You are receiving this mail because: You are the assignee for the bug.

1 42

[Bug 74766] New: no image output in Sonic Robo Blast 2 in OpenGL mode
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=74766 Priority: medium Bug ID: 74766 Assignee: dri-devel(a)lists.freedesktop.org Summary: no image output in Sonic Robo Blast 2 in OpenGL mode Severity: normal Classification: Unclassified OS: Linux (All) Reporter: thepouar(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.0 Component: Drivers/DRI/R600 Product: Mesa Created attachment 93729 --> https://bugs.freedesktop.org/attachment.cgi?id=93729&action=edit screenshot All I see is a bunch of gray and black rectangles in OpenGL mode -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 74765] New: weird glitches in firefox
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=74765 Priority: medium Bug ID: 74765 Assignee: dri-devel(a)lists.freedesktop.org Summary: weird glitches in firefox Severity: normal Classification: Unclassified OS: All Reporter: thepouar(a)gmail.com Hardware: Other Status: NEW Version: 10.0 Component: Drivers/DRI/R600 Product: Mesa Created attachment 93727 --> https://bugs.freedesktop.org/attachment.cgi?id=93727&action=edit screenshot of affected area -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 74726] New: r600g: unrecoverable GPU lockup after glDrawElements INVALID_ENUM
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=74726 Priority: medium Bug ID: 74726 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600g: unrecoverable GPU lockup after glDrawElements INVALID_ENUM Severity: normal Classification: Unclassified OS: All Reporter: edwin+mesa(a)etorok.net Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 93679 --> https://bugs.freedesktop.org/attachment.cgi?id=93679&action=edit corrupt.trace If you send a lot of invalid glDrawElements commands to Mesa it can cause a GPU lockup. Would it be possible to validate this Mesa side / or kernel CS checker side to avoid the GPU lockup? [1] If you replay the attached trace on r600g you get a GPU lockup, see attachments: * gpureset.log: dmesg when reboot is the only solution, no text console, no X, nothing works until a reboot * text_recovered.log: dmesg when I can kill the application and X, and get to a framebuffer text console. Starting X is impossible though, unless I reboot I've run the trace under valgrind, and I see no valgrind errors, but of course I see a lot of Mesa errors. The mesa errors shouldn't cause a GPU lockup though. I reproduced this with the 10.1 branch, but similar lockups happen on the 10.0.2 release too (if you force the version to 3.3), so it doesn't seem to be related to the 3.3 work on the 10.1 branch. Mesa built like this: $ ./configure --enable-dri --enable-glx-tls --enable-shared-glapi --enable-texture-float --enable-xa --disable-xvmc --disable-vdpau --with-gallium-drivers=r600,swrast LLVM_CONFIG=/usr/bin/llvm-config-3.4 --disable-dri3 --enable-debug OpenGL version: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0-rc1 (git-1e6bba5) OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.1.0-rc1 (git-1e6bba5) OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: kernel: $ uname -a Linux debian 3.14.0-rc1-00015-g7c4c62a #48 SMP PREEMPT Sat Feb 8 17:33:48 EET 2014 x86_64 GNU/Linux [1] There are some use-after-free bugs in the gltut tutorials when you press Escape: it frees some stuff, then calls glutLeaveMainLoop(), but freeglut still calls display(), causing use-after-frees. Of course its expected that the application itself might crash, or otherwise misbehave, but I was not expecting an unrecoverable GPU lockup. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 74539] New: [r600g] Memory leak when playing WoW with RV790
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=74539 Priority: medium Bug ID: 74539 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] Memory leak when playing WoW with RV790 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rankincj(a)googlemail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 93417 --> https://bugs.freedesktop.org/attachment.cgi?id=93417&action=edit dmesg log showing memory allocation failure. I am seeing a possible memory leak while playing WoW-64.exe with my RV790. The problem seems to happen after ~ 1 hour of play: [ 117.896993] fuse init (API version 7.22) [ 3326.401752] WoW-64.exe: page allocation failure: order:4, mode:0x10c0d0 [ 3326.407099] CPU: 7 PID: 31106 Comm: WoW-64.exe Not tainted 3.12.9 #1 [ 3326.412185] Hardware name: Gigabyte Technology Co., Ltd. EX58-UD3R/EX58-UD3R, BIOS FB 05/04/2009 [ 3326.419812] ffff8801afdcdbd0 ffffffff812d0071 0000000000000001 ffffffff810a0c50 [ 3326.426142] 0000000000000001 0000000000000000 ffffffff8164ff80 ffffffff8164f400 [ 3326.432429] 000000000010c0d0 ffffffff812cebb7 ffffffff8164f400 ffff880100000000 I *think* I can bisect this, although it might make some time: 9bace99d77642f8fbd46b1f0be025ad758f83f5e BAD f5bd5568abcc234c1c2b6a4bb67b880706f3caed GOOD -- You are receiving this mail because: You are the assignee for the bug.

1 42

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015