dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 101575] Lockup for executing trivial-tess-gs_no-gs-inputs.shader_test
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101575 Bug ID: 101575 Summary: Lockup for executing trivial-tess-gs_no-gs-inputs.shader_test 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: Hi-Angel(a)yandex.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 132214 --> https://bugs.freedesktop.org/attachment.cgi?id=132214&action=edit Vertex, geometric, pixel shaders dump This test always fails: $ bin/shader_runner piglit/tests/spec/arb_tessellation_shader/execution/trivial-tess-gs_no-gs-inputs.shader_test -auto -fbo Probe color at (0,0) Expected: 0 255 0 0 Observed: 0 0 0 0 Test failure on line 60 PIGLIT: {"result": "fail" } but, in addition, often screen goes black, and kernel spews a message about lockup: [ 4093.695956] radeon 0000:01:00.0: ring 3 stalled for more than 10053msec [ 4093.695966] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000002be last fence id 0x00000000000002bf on ring 3) [ 4093.696032] radeon 0000:01:00.0: failed to get a new IB (-35) [ 4093.696079] [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to get ib ! [ 4093.703389] radeon 0000:01:00.0: Saved 1154 dwords of commands on ring 0. [ 4093.703406] radeon 0000:01:00.0: GPU softreset: 0x0000001D [ 4093.703410] radeon 0000:01:00.0: GRBM_STATUS = 0xA0631CA0 [ 4093.703413] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x18000003 [ 4093.703416] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 4093.703418] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 4093.703421] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 4093.703424] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000 [ 4093.703427] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00011000 [ 4093.703430] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00068402 [ 4093.703433] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80870243 [ 4093.703436] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483106 [ 4093.708782] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 4093.708836] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100 [ 4093.710004] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 4093.710006] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 4093.710008] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 4093.710010] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 4093.710012] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 4093.710014] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 4093.710015] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 4093.710017] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 4093.710019] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 4093.710021] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 4093.710039] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 4093.737953] [drm] PCIE GART of 1024M enabled (table at 0x000000000014C000). [ 4093.738076] radeon 0000:01:00.0: WB enabled [ 4093.738081] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8801b0eb0c00 [ 4093.738084] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8801b0eb0c0c [ 4093.738460] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9000181c418 [ 4093.755220] [drm] ring test on 0 succeeded in 1 usecs [ 4093.755229] [drm] ring test on 3 succeeded in 3 usecs [ 4093.932873] [drm] ring test on 5 succeeded in 1 usecs [ 4093.932878] [drm] UVD initialized successfully. [ 4093.951552] [drm] ib test on ring 0 succeeded in 0 usecs [ 4093.951589] [drm] ib test on ring 3 succeeded in 0 usecs [ 4095.109237] [drm] ib test on ring 5 succeeded ≈½ of lockups are leaving screen black, and require reboot. Attaching vs,gs,ps assembly, and R600_TRACE results from 2 different lockups. The 2 traces are identical except that 1-st one locks up at the start, and the other at the end. I've tried fixing it myself, but I have no slightest idea what to look at. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 101392] KWin crashes during window ALT+TAB window changing
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101392 Bug ID: 101392 Summary: KWin crashes during window ALT+TAB window changing Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: ecklm94(a)gmail.com A developer told me that this is a radeon_dri issue. Exact description and comments on the original bug report: https://bugs.kde.org/show_bug.cgi?id=381099 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 101374] Worms Clan Wars hangs on loading screen
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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

1 0

[Bug 100972] r600g: vaapi encoder SIGFPE
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100972 Bug ID: 100972 Summary: r600g: vaapi encoder SIGFPE 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: martin(a)serafean.cz QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131262 --> https://bugs.freedesktop.org/attachment.cgi?id=131262&action=edit possible fix (is 0 a valid value?) Program received signal SIGFPE, Arithmetic exception. 0x00007fffe5c86f07 in handleVAEncSequenceParameterBufferType (drv=0x5555557ec2b0, context=0x555555a42c70, buf=0x555555819000) at /var/tmp/paludis/media-libs-mesa-9999/work/mesa-9999/src/gallium/state_trackers/va/picture.c:374 374 in /var/tmp/paludis/media-libs-mesa-9999/work/mesa-9999/src/gallium/state_trackers/va/picture.c What happens is that h264->intra_idr_period is 0, which with current parenthesizing results in a division by 0. Command used : ffmpeg -loglevel debug -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i Elephants_Dream_HD.avi -vf format=nv12,hwupload -map 0:0 -map 0:1 -y -f matroska -bf 0 -c:v h264_vaapi ~/test.mkv -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 100953] [ARUBA] Light shaders is very bright in GRID Autosport on Radeon 8470D
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100953 Bug ID: 100953 Summary: [ARUBA] Light shaders is very bright in GRID Autosport on Radeon 8470D Product: Mesa Version: 17.1 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: russianneuromancer(a)ya.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131234 --> https://bugs.freedesktop.org/attachment.cgi?id=131234&action=edit GRID Autosport on Radeon 8470D Hello! Please look into attached screenshot. This issue is not reproducible on Radeon HD 6650M. Software: Kubuntu 17.0 x86_64 Linux 4.10 Mesa: 17.1.0rc2 libdrm: 2.4.80 xserver-xorg-video-radeon: 7.9.0 xserver-xorg-core: 1.19.3 Hardware: AMD A6-6400K with Radeon HD 8470D (ARUBA) -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 100865] Unigine Heaven 4 lockups GPU in wireframe mode
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100865 Bug ID: 100865 Summary: Unigine Heaven 4 lockups GPU in wireframe mode 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: marvin24(a)gmx.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131115 --> https://bugs.freedesktop.org/attachment.cgi?id=131115&action=edit dmesg output launched UH4 on RS880 / Kernel 4.10.10 with mesa git demo runs well until you press "F2" in order to activate wireframe mode, which causes GPU lockups tested mesa: 12, 13, 17, 17.1 and git - all same. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 100387] War Thunder game has visual errors, missing textures
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100387 Bug ID: 100387 Summary: War Thunder game has visual errors, missing textures 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: acelists(a)atlas.sk QA Contact: dri-devel(a)lists.freedesktop.org Using the War Thunder game on Slackware, Mesa git custom compiled, LLVM 4.0 and on a RV710 card (512MB video RAM) always produces visual errors. The errors are not the same at all runs but vary between these problems, e.g. sky being black, clouds being any color, water is some color without reflections, trees being blue. Plane/ground target models are mostly correct, but sometimes they are also white. The errors can be seen right in the hangar, but also when playing the game (in a mission). I have set the "Old videocard support" in the graphics options in the game. This has improved things to the state I describe. The game client shows "ultra low quality" in the right hand corner. I am using the low-res client (HD textures not downloaded) and the client often prompts to download hi-res textures which I decline. Other than this, the game runs correctly, albeit slow on this GPU (5-15FPS). In the console where I start the game (updater binary) there is a ton of output like: EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed ! EE r600_state_common.c:803 r600_shader_select - Failed to build shader variant (type=1) -1 The line numbers 183 and 803 are always the same. -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 99843] Geometry Shader - Incorrect Output
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99843 Bug ID: 99843 Summary: Geometry Shader - Incorrect Output Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: dan(a)jerber.co.uk QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 129684 --> https://bugs.freedesktop.org/attachment.cgi?id=129684&action=edit Typical output Hi, I am developing a cross-platform application. I have recently found an issue that is only present when it is tested on a Ubuntu machine. I have managed to find a minimal example that shows the issue as follows: The vertex shader: #version 150 in vec2 pos; void main(void) { gl_Position = vec4(pos, 0.0, 1.0); } The fragment shader: #version 150 out vec4 outColour; void main(void) { outColour = vec4(1.0f, 1.0f, 1.0f, 1.0f); } The geometry shader: #version 150 layout(points) in; layout(line_strip, max_vertices = 13) out; uniform mat4 vpMatrix; void main() { for(int i = 0; i < 13; i++) { float polygonAngle = (i * 30) + 90.0f; vec4 vertexPosition = vec4((sin(radians(polygonAngle)) * 0.5f) + gl_in[0].gl_Position.x, (cos(radians(polygonAngle)) * 0.5f) + gl_in[0].gl_Position.y, 0.0f, 1.0f); gl_Position = vpMatrix * vertexPosition; EmitVertex(); } EndPrimitive(); } The problem occurs when the shader program is used with multiple VBO's. For example: 3 separate VBO's are created with {-1.0f, 1.0f}, {1.0f, 1.0f}, {1.0f, -1.0f} as the data. Then, for each repaint: for(int i = 0; i < 3; i++) { Bind array buffer i. glDrawArrays(GL_POINTS, 0, 1); } This produces strange results for the third polygon (shown in the attached image Output.JPG). If tested on a Windows 10 machine (exactly the same hardware) or an OSX machine, the results are as expected (3 regular polygons with 12 sides). -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 96881] ViennaCL fails dense_blas-bench-opencl benchmark with doubles on AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=96881 Bug ID: 96881 Summary: ViennaCL fails dense_blas-bench-opencl benchmark with doubles on AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0) Product: Mesa Version: 11.2 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: ubizjak(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org The dense_blas-bench-opencl benchmark from ViennaCL suite fails with doubles on AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0): $ ./dense_blas-bench-opencl ---------------------------------------------- Device Info ---------------------------------------------- Name: AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0) Vendor: AMD Type: GPU Available: 1 Max Compute Units: 10 Max Work Group Size: 256 Global Mem Size: 1073741824 Local Mem Size: 32768 Local Mem Type: 1 Host Unified Memory: 1 Benchmark : BLAS ---------------- sCOPY : 64.3 GB/s sAXPY : 95.4 GB/s sDOT : 85.3 GB/s sGEMV-N : 20.8 GB/s sGEMV-T : 44.3 GB/s sGEMM-NN : 126 GFLOPs/s sGEMM-NT : 87.6 GFLOPs/s sGEMM-TN : 90.5 GFLOPs/s sGEMM-TT : 72.3 GFLOPs/s ---- Build Status = -2 ( Err = -11 ) Log: unsupported call to function __subdf3 in av_cpu Sources: #pragma OPENCL EXTENSION cl_khr_fp64 : enable __kernel void av_cpu( __global double * vec1, uint4 size1, ... It looks like DFmode (double) instructions are not enabled correctly in LLVM for targets that report cl_khr_fp64 extension. clinfo reports: Number of platforms 1 Platform Name Clover Platform Vendor Mesa Platform Version OpenCL 1.1 MESA 11.2.2 Platform Profile FULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions function suffix MESA Platform Name Clover Number of devices 1 Device Name AMD CYPRESS (DRM 2.43.0, LLVM 3.8.0) Device Vendor AMD Device Vendor ID 0x1002 Device Version OpenCL 1.1 MESA 11.2.2 Driver Version 11.2.2 Device OpenCL C Version OpenCL C 1.1 Device Type GPU Device Profile FULL_PROFILE Max compute units 10 Max clock frequency 850MHz Max work item dimensions 3 Max work item sizes 256x256x256 Max work group size 256 Preferred work group size multiple 64 Preferred / native vector sizes char 16 / 16 short 8 / 8 int 4 / 4 long 2 / 2 half 0 / 0 (n/a) float 4 / 4 double 2 / 2 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals No Infinity and NANs Yes Round to nearest Yes Round to zero No Round to infinity No IEEE754-2008 fused multiply-add No Support is emulated in software No Correctly-rounded divide and sqrt operations No Double-precision Floating-point support (cl_khr_fp64) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Correctly-rounded divide and sqrt operations No ... -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 99510] cl_khr_fp64 is reported as supported, but is not, on CAYMAN
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99510 Bug ID: 99510 Summary: cl_khr_fp64 is reported as supported, but is not, on CAYMAN Product: Mesa Version: 13.0 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 On CAYMAN, cl_khr_fp64 is listed as a supported extension in clinfo, and therefore also makes some kernels fail to compile due to their trying to compile in things that need cl_khr_fp64 support. This causes clpeak to fail with 'unsupported call to function __floatunsidf in compute_dp_v1'. If you need more information I will be happy to provide more. -- You are receiving this mail because: You are the assignee for the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019