dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 103634] nv_conditional_render tests hang the gpu (HD 5750)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103634 Bug ID: 103634 Summary: nv_conditional_render tests hang the gpu (HD 5750) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sroland(a)vmware.com QA Contact: dri-devel(a)lists.freedesktop.org Nearly all of piglit's nv_conditional_render tests (I think 10 out of 12, I'd rather not retry them all since it sometimes brings down the box after the gpu reset) immediately hang the gpu - nv_conditional_render-begin-xxx are the two exceptions (which pass). GPU is Juniper, HD 5750. I'm not sure if this is even a regression, as I never ran piglit on this box before, and at least with mesa 17.1.8 it hangs all the same as current git master. If the kernel version matters, I tried some 4.9 and some 4.13 kernel. [ 749.782315] radeon 0000:01:00.0: ring 0 stalled for more than 10224msec [ 749.782319] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000004081 last fence id 0x0000000000004 ... [ 771.466593] radeon 0000:01:00.0: Saved 882 dwords of commands on ring 0. [ 771.906456] radeon 0000:01:00.0: GPU softreset: 0x0000001D [ 771.906458] radeon 0000:01:00.0: GRBM_STATUS = 0xA0001828 [ 771.906459] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000003 [ 771.906460] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 771.906461] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 [ 771.906462] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 771.906463] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 771.906464] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 771.906465] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000006 [ 771.906466] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80008E47 [ 771.906468] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 771.914331] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 771.914382] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100 [ 771.915528] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 771.915529] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 771.915530] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 771.915531] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 771.915532] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 771.915533] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 771.915534] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 771.915535] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 771.915536] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 771.915538] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 771.915554] radeon 0000:01:00.0: GPU reset succeeded, trying to resume -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 103371] glxinfo -l shows GL_INVALID_ENUM
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103371 Bug ID: 103371 Summary: glxinfo -l shows GL_INVALID_ENUM Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: marvin24(a)gmx.de QA Contact: dri-devel(a)lists.freedesktop.org glxinfo -l gives GL_INVALID_ENUM for GL_MAX_GEOMETRY_UNIFORM_BLOCKS, GL_MAX_COMBINED_GEOMETRY_UNIFORM_COMPONENTS, GL_MAX_VERTEX_OUTPUT_COMPONENTS, and GL_MAX_FRAGMENT_INPUT_COMPONENTS; see output below. HW is RS880. Maybe uncritcal but ugly. OpenGL limits: GL_MAX_ATTRIB_STACK_DEPTH = 16 GL_MAX_CLIENT_ATTRIB_STACK_DEPTH = 16 GL_MAX_CLIP_PLANES = 8 GL_MAX_ELEMENTS_VERTICES = 3000 GL_MAX_ELEMENTS_INDICES = 3000 GL_MAX_EVAL_ORDER = 30 GL_MAX_LIGHTS = 8 GL_MAX_LIST_NESTING = 64 GL_MAX_MODELVIEW_STACK_DEPTH = 32 GL_MAX_NAME_STACK_DEPTH = 64 GL_MAX_PIXEL_MAP_TABLE = 256 GL_MAX_PROJECTION_STACK_DEPTH = 32 GL_MAX_TEXTURE_STACK_DEPTH = 10 GL_MAX_TEXTURE_SIZE = 8192 GL_MAX_3D_TEXTURE_SIZE = 2048 GL_MAX_ARRAY_TEXTURE_LAYERS = 2048 GL_MAX_VIEWPORT_DIMS = 8192, 8192 GL_ALIASED_LINE_WIDTH_RANGE = 1, 8192 GL_SMOOTH_LINE_WIDTH_RANGE = 1, 8192 GL_ALIASED_POINT_SIZE_RANGE = 1, 8192 GL_SMOOTH_POINT_SIZE_RANGE = 0, 8192 GL_MAX_CUBE_MAP_TEXTURE_SIZE_ARB = 8192 GL_MAX_RECTANGLE_TEXTURE_SIZE_NV = 8192 GL_MAX_TEXTURE_UNITS_ARB = 8 GL_MAX_TEXTURE_LOD_BIAS_EXT = 16 GL_MAX_TEXTURE_MAX_ANISOTROPY_EXT = 16 GL_MAX_DRAW_BUFFERS_ARB = 8 GL_MAX_DUAL_SOURCE_DRAW_BUFFERS = 1 GL_MAX_RENDERBUFFER_SIZE = 8192 GL_MAX_COLOR_ATTACHMENTS = 8 GL_MAX_SAMPLES = 8 GL_MAX_TRANSFORM_FEEDBACK_BUFFERS = 4 GL_MAX_TRANSFORM_FEEDBACK_INTERLEAVED_COMPONENTS = 128 GL_MAX_TRANSFORM_FEEDBACK_SEPARATE_ATTRIBS = 4 GL_MAX_TRANSFORM_FEEDBACK_SEPARATE_COMPONENTS = 128 GL_MAX_COLOR_TEXTURE_SAMPLES = 8 GL_MAX_DEPTH_TEXTURE_SAMPLES = 8 GL_MAX_INTEGER_SAMPLES = 1 GL_MAX_VERTEX_UNIFORM_BLOCKS = 12 GL_MAX_FRAGMENT_UNIFORM_BLOCKS = 12 Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_GEOMETRY_UNIFORM_BLOCKS) GL_MAX_COMBINED_UNIFORM_BLOCKS = 48 GL_MAX_UNIFORM_BUFFER_BINDINGS = 48 GL_MAX_UNIFORM_BLOCK_SIZE = 65536 GL_MAX_COMBINED_VERTEX_UNIFORM_COMPONENTS = 212992 GL_MAX_COMBINED_FRAGMENT_UNIFORM_COMPONENTS = 212992 Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_COMBINED_GEOMETRY_UNIFORM_COMPONENTS) GL_UNIFORM_BUFFER_OFFSET_ALIGNMENT = 256 GL_MAX_VERTEX_ATTRIB_RELATIVE_OFFSET = 2047 GL_MAX_VERTEX_ATTRIB_BINDINGS = 16 GL_NUM_COMPRESSED_TEXTURE_FORMATS = 10 GL_COMPRESSED_RGB_S3TC_DXT1_EXT GL_COMPRESSED_RGBA_S3TC_DXT3_EXT GL_COMPRESSED_RGBA_S3TC_DXT5_EXT GL_COMPRESSED_RGB8_ETC2 GL_COMPRESSED_RGBA8_ETC2_EAC GL_COMPRESSED_R11_EAC GL_COMPRESSED_RG11_EAC GL_COMPRESSED_SIGNED_R11_EAC GL_COMPRESSED_SIGNED_RG11_EAC GL_COMPRESSED_RGB8_PUNCHTHROUGH_ALPHA1_ETC2 GL_VERTEX_PROGRAM_ARB: GL_MAX_PROGRAM_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_NATIVE_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_TEMPORARIES_ARB = 256 GL_MAX_PROGRAM_NATIVE_TEMPORARIES_ARB = 256 GL_MAX_PROGRAM_PARAMETERS_ARB = 4096 GL_MAX_PROGRAM_NATIVE_PARAMETERS_ARB = 4096 GL_MAX_PROGRAM_ATTRIBS_ARB = 16 GL_MAX_PROGRAM_NATIVE_ATTRIBS_ARB = 16 GL_MAX_PROGRAM_ADDRESS_REGISTERS_ARB = 1 GL_MAX_PROGRAM_NATIVE_ADDRESS_REGISTERS_ARB = 1 GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB = 4096 GL_MAX_PROGRAM_ENV_PARAMETERS_ARB = 256 GL_FRAGMENT_PROGRAM_ARB: GL_MAX_PROGRAM_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_NATIVE_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_TEMPORARIES_ARB = 256 GL_MAX_PROGRAM_NATIVE_TEMPORARIES_ARB = 256 GL_MAX_PROGRAM_PARAMETERS_ARB = 4096 GL_MAX_PROGRAM_NATIVE_PARAMETERS_ARB = 4096 GL_MAX_PROGRAM_ATTRIBS_ARB = 32 GL_MAX_PROGRAM_NATIVE_ATTRIBS_ARB = 32 GL_MAX_PROGRAM_ADDRESS_REGISTERS_ARB = 0 GL_MAX_PROGRAM_NATIVE_ADDRESS_REGISTERS_ARB = 0 GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB = 4096 GL_MAX_PROGRAM_ENV_PARAMETERS_ARB = 256 GL_MAX_PROGRAM_ALU_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_TEX_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_TEX_INDIRECTIONS_ARB = 16384 GL_MAX_PROGRAM_NATIVE_ALU_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_NATIVE_TEX_INSTRUCTIONS_ARB = 16384 GL_MAX_PROGRAM_NATIVE_TEX_INDIRECTIONS_ARB = 16384 GL_VERTEX_SHADER_ARB: GL_MAX_VERTEX_UNIFORM_COMPONENTS_ARB = 16384 GL_MAX_VARYING_FLOATS_ARB = 128 GL_MAX_VERTEX_ATTRIBS_ARB = 16 GL_MAX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS_ARB = 16 GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS_ARB = 48 GL_MAX_TEXTURE_COORDS_ARB = 8 Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_VERTEX_OUTPUT_COMPONENTS) GL_FRAGMENT_SHADER_ARB: GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB = 16384 GL_MAX_TEXTURE_COORDS_ARB = 8 GL_MAX_TEXTURE_IMAGE_UNITS_ARB = 16 Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_FRAGMENT_INPUT_COMPONENTS) -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 103297] Rendering issue in cemu BOTW game for pre gcn hardware
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103297 Bug ID: 103297 Summary: Rendering issue in cemu BOTW game for pre gcn hardware Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: johann.maxime(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 134866 --> https://bugs.freedesktop.org/attachment.cgi?id=134866&action=edit screenshot of botw Using cemu emulator on Ubuntu 17.04 with wine lastest mesa git build give graphical glitch on pre gcn hardware. In my case I use AMD TURKS (HD 7670M). The Legend Of Zelda Breath Of The Wild has heavy graphical issues. Some other games works perfectly (Mario Kart 8 for example). -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 103066] Empire boundaries do not show up in Stellaris.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103066 Bug ID: 103066 Summary: Empire boundaries do not show up in Stellaris. Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: dstephanoshachter(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org When I play Stellaris, I can not see the empire boundaries. The whole galaxy just looks like a grey blob. It looks just like Bug 95530. I am using an AMD Radeon HD 6970, mesa 17.2.1, and fedora 26. I'm not sure what kind of debug info is useful, but the bug is completely reproducible so I can get any info needed. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 102709] War Thunder crashes after logging in to the game. (GL_INVALID_ENUM)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102709 Bug ID: 102709 Summary: War Thunder crashes after logging in to the game. (GL_INVALID_ENUM) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: balalic.enver(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 134200 --> https://bugs.freedesktop.org/attachment.cgi?id=134200&action=edit GlxInfo On my Radeon HD6950, War Thunder crashes after logging in to the game, if using LIBGL_DEBUG=verbose and MESA_DEBUG=1 when starting the game, it spams the following in the console: Mesa: User error: GL_INVALID_ENUM in glTexStorage2D(internalformat = GL_COMPRESSED_RGBA_S3TC_DXT5_EXT) Mesa: User error: GL_INVALID_ENUM in glCompressedTexSubImage2D(format) and a couple of the messages are a bit different: Mesa: User error: GL_INVALID_ENUM in glTexStorage2D(internalformat = GL_COMPRESSED_SRGB_ALPHA_S3TC_DXT5_EXT) Mesa: User error: GL_INVALID_ENUM in glCompressedTexSubImage2D(format) Using Fedora Rawhide, Mesa 17.3.0-devel, LLVM 6.0.0, packages from che COPR repo. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 102595] clpeak
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102595 Bug ID: 102595 Summary: clpeak Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: benjiwiebe14(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org When I run 'clpeak --global-bandwidth' I get: [benji@benji-pc clpeak]$ ./clpeak --global-bandwidth Platform: Clover Device: AMD CAYMAN (DRM 2.50.0 / 4.13.0+, LLVM 6.0.0) Driver version : 17.3.0-devel (Linux x64) Compute units : 12 Clock frequency : 880 MHz Global memory bandwidth (GBPS) float : radeon: Failed to allocate a buffer: radeon: size : 1073741824 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: flags : 4 radeon: Failed to allocate a buffer: radeon: size : 1073741824 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: flags : 4 Segmentation fault (core dumped) And in dmesg: [55959.960796] clpeak[16731]: segfault at 1c ip 00007f3d77e5a42a sp 00007fff93152570 error 4 in pipe_r600.so[7f3d77d53000+1c2000] The clpeak compute-* and kernel-latency tests work fine, and transfer-bandwidth fails with a (I believe) unrelated error message, seemingly due to me running Linux-git. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 102387] Assertion failure with UE4Editor and sb enabled
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102387 Bug ID: 102387 Summary: Assertion failure with UE4Editor and sb enabled Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: gw.fossdev(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 133745 --> https://bugs.freedesktop.org/attachment.cgi?id=133745&action=edit TGSI and byte code of the buggy shader When running UE4Editor (4.17) on BARTS with -opengl3 and mesa (1e696b9) is compiled in debug mode I get the following assertion failure on one shader (attached), that then leads to UE4Editor shutting down: error at : MUL_IEEE R17.x.5F(a)R124.x, R14.x.5F(a)R124.x, R90.x.22||F(a)R2.w : expected operand value R90.x.22||F(a)R2.w, gpr contains t39||FP(a)R2.w sb/sb_ra_checker.cpp:46:run: Assertion `sh.errors.empty()' failed. Sometimes it happens right away, when loading the assets, sometimes I have to load a specific level. I guess it depends on what assets are actually displayed. If I disable the assertion then I can use UE4Editor (I still need to add a patch to work around to a problem introduced by another shader that for some bug in UE4 exceeds the limits of the GPRs, but this has nothing to do which this assertion failure). Best, Gert -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 102013] GTK3 tooltips are corrupted after updating to mesa 17.0.7
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102013 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #22 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- 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/608. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 101787] colours all messed up
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101787 Bug ID: 101787 Summary: colours all messed up Product: Mesa Version: 17.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/R100 Assignee: dri-devel(a)lists.freedesktop.org Reporter: mad_fer_it(a)msn.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 132682 --> https://bugs.freedesktop.org/attachment.cgi?id=132682&action=edit a screen of the bug as the title said i have problems with colours...everytime i try to watch a video with a desktop player that actually use gstreamer colours gets all messed up as you can see from the screen...reported it on federa forums but they told me it could be a video driver issue since terminal is giving me radeon: The kernel rejected CS, see dmesg for more information (-22). i am using fedora 26 with mesa 17.1.4 and an ati radeon 4570 hd...anything i can do to solve the problem? -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 101712] [Turks PRO/Radeon HD 6570/7570/8550] CPU lockup after ring 0 stalled
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101712 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #8 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- 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/606. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019