dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 110711] American Truck shows strange colored reflections
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110711 Bug ID: 110711 Summary: American Truck shows strange colored reflections Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: gr.muench(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144301 --> https://bugs.freedesktop.org/attachment.cgi?id=144301&action=edit ATS Menu There is strange colored noise on the chrome parts of the Truck, see screenshot. Wasnt sure if this was a game bug or a radeonsi one, so I didnt report, although it was there for several years. After I saw that a lot graphical issues in other games went away R600_DEBUG=zerovram I tried that here too and voila! For me, that looks like a general problem that was undiscovered for several years and needs examination. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 110658] MXGP3 (Steam, native Linux port, UE4): graphical glitches
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110658 Bug ID: 110658 Summary: MXGP3 (Steam, native Linux port, UE4): graphical glitches Product: Mesa Version: 19.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: mezin.alexander(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org In game the screen is sometimes too dark, when it shouldn't, sparks everywhere. In menus everything is OK. Screen capture: https://youtu.be/rr9DdFfII5E (glitches begin at 0:16) Also reported the issue to game developers, got no response so far. gpu: RX Vega 64 mesa: 19.0.3, also tested with 19.1 rc1, no changes linux 5.0 -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 110639] enc->enc_pic.enc_pic_order_cnt_type always zero even if pic->pic_order_cnt_type non-zero that application set
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110639 Bug ID: 110639 Summary: enc->enc_pic.enc_pic_order_cnt_type always zero even if pic->pic_order_cnt_type non-zero that application set Product: Mesa Version: 18.0 Hardware: ARM OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: wangfengjuan3(a)huawei.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144193 --> https://bugs.freedesktop.org/attachment.cgi?id=144193&action=edit glxinfo when process yuv encode to h264, player set pic_order_cnt_type non-zero value, but h264 SPS pic_order_cnt_type member always zero. I have found that enc->enc_pic.pc.enc_pic_order_cnt_type always print zero in mesa/src/gallium/drivers/radeon/radeon_vce_52.c:452. but add enc->enc_pic.pc.enc_pic_order_cnt_type = pic->pic_order_cnt_type;at fun get_pic_control_param in mesa/src/gallium/drivers/radeon/radeon_vce_52.c:92 can resove the bug. Please help to check and commit if the above method is right. ps: (gdb) bt #0 pic_control (enc=0xaaaaaacc2d30) at radeon_vce_52.c:527 #1 0x0000ffffbf1620b0 in config (enc=0xaaaaaacc2d30) at radeon_vce_52.c:452 #2 0x0000ffffbf164d34 in rvce_begin_frame (encoder=0xaaaaaacc2d30, source=0xaaaaaabfbc50, picture=0xaaaaaabe2828) at radeon_vce.c:292 #3 0x0000ffffbef076f0 in vlVaEndPicture (ctx=0xaaaaaaae0c80, context_id=2) at picture.c:700 #4 0x0000ffffbf695cb8 in vaEndPicture (dpy=0xaaaaaaae0b10, context=2) at va.c:1520 #5 0x0000aaaaaaaaf258 in avcenc_render_picture () at src/va_encode_impl.cpp:831 #6 0x0000aaaaaaab1030 in encode_picture (is_idr=1, slice_type=2) at src/va_encode_impl.cpp:1482 #7 0x0000aaaaaaab16e0 in vaapi_encode_yuv_to_h264 (frame_index=0) at src/va_encode_impl.cpp:1613 #8 0x0000aaaaaaab17a4 in vaapi_encode_frame (frame_index=0) at src/va_encode_impl.cpp:1640 #9 0x0000aaaaaaaabba4 in va_encode_frame (frame_index=0) at src/va_encode_api2.cpp:118 #10 0x0000aaaaaaab26dc in main (argc=5, argv=0xfffffffff678) at demo/test_va_encode.cpp:164 Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 110637] Enabling OpenCL in Libreoffice kills Vega 64
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110637 Bug ID: 110637 Summary: Enabling OpenCL in Libreoffice kills Vega 64 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: mezin.alexander(a)gmail.com Created attachment 144191 --> https://bugs.freedesktop.org/attachment.cgi?id=144191&action=edit kernel log Open LibreOffice, enable OpenCL in settings, restart it. Result: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=698, emitted seq=700 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process soffice.bin pid 2517 thread soffice.bi:cs0 pid 2545 amdgpu 0000:67:00.0: GPU reset begin! amdgpu 0000:67:00.0: GPU BACO reset amdgpu: [powerplay] Failed message: 0x5, input parameter: 0x2000000, error code: 0xffffffff amdgpu 0000:67:00.0: GPU reset succeeded, trying to resume [drm] PCIE GART of 512M enabled (table at 0x000000F400900000). [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost! [drm] PSP is resuming... [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE [drm] UVD and UVD ENC initialized successfully. [drm] VCE initialized successfully. [drm] recover vram bo from shadow start [drm] recover vram bo from shadow done [drm] Skip scheduling IBs! [drm] Skip scheduling IBs! amdgpu 0000:67:00.0: GPU reset(2) succeeded! [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! ... Also the same problem with multiple games, so probably not OpenCL-related, just the easiest way to trigger it. linux 5.1.arch1-1 (same results with 5.0.13, will also retest with 4.9) linux-firmware 20190502.92e17d0-1 (same results with 20190424.4b6cf2b-1) opencl-mesa 19.0.3-1 libdrm 2.4.98-1 libreoffice-fresh 6.2.3-2 GNOME on X.org with modesetting driver Sapphire Vega 64 Nitro+, no overclocking -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 110635] briefly flashing corruption when playing various OGL games
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110635 Bug ID: 110635 Summary: briefly flashing corruption when playing various OGL games Product: Mesa Version: git 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: tempel.julian(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I'm seeing briefly flashing corruption in various OGL games, mostly Dying Light and Counter-Strike Global Offensive Danger Zone. But I once also saw it in X-Plane 11. Happens with Mesa 18 and git and llvm 8 and git, but likely also even older versions in both cases. I was able to capture it by recording a video and then extracting an affected frame: https://abload.de/img/mpv-shot0001hkjyr.png Across the aforementioned games, the artifacts look akin or the same. Can also be brighter squares though. Hardware issue is unlikely, as radv / amdvlk never show this issue (and Windows driver neither). I fail to see a pattern when this corruption occurs, it seems like total chance to me while gaming. This is with an RX 580 on Arch. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 110614] [Regression] Freeze at desktop manager startup
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110614 Bug ID: 110614 Summary: [Regression] Freeze at desktop manager startup 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: raffarti(a)zoho.com QA Contact: dri-devel(a)lists.freedesktop.org Freeze at desktop manager startup (tested with sddm and lightdm). Bisected as commit 1cec049d4db1c4dcd121bad17df4a77273dd9bb1 Author: Julien Isorce <jisorce(a)oblong.com> Date: Tue Apr 23 14:28:48 2019 -0700 radeonsi: implement resource_get_info Re-use existing si_texture_get_offset. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110443 Signed-off-by: Julien Isorce <jisorce(a)oblong.com> Reviewed-by: Marek Olšák <marek.olsak(a)amd.com> commit a3c202de0a963c0562796cf75e3a9b3eedf1afad Author: Julien Isorce <jisorce(a)oblong.com> Date: Tue Apr 23 14:26:33 2019 -0700 gallium: add resource_get_info to pipe_screen Generic plumbing. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110443 Signed-off-by: Julien Isorce <jisorce(a)oblong.com> Reviewed-by: Marek Olšák <marek.olsak(a)amd.com> GPU: RX 480 OS: OpenSuse Tumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 110575] [R9 380X] Artifacts in CSGO
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110575 Bug ID: 110575 Summary: [R9 380X] Artifacts in CSGO Product: Mesa Version: git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: danylo.piliaiev(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144123 --> https://bugs.freedesktop.org/attachment.cgi?id=144123&action=edit example of artifacts Distro: Manjaro Kernel: 5.0.5 GPU: R9 380X Reproducible with: Mesa: git (07745f94948) LLVM: 9 (359393) Isn't reproducible with: Mesa: 19.0.3 LLVM: 8 Parts of the screen randomly become corrupted for 1 or 2 frames. It's not a rare event. Doesn't happen when capturing and/or replaying with apitrace. Doesn't happen when running OBS. Happens on new Sirocco map, didn't test on other. Sorry for the image quality - it was taken from video recorded with old phone, the grey squares on a tree branch are the artifacts in question but they could be completely different. I'm using https://pkgbuild.com/~lcarlier/mesa-git/x86_64/ for mesa and llvm builds. -- You are receiving this mail because: You are the assignee for the bug.

2 10

[Bug 110509] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110509 Bug ID: 110509 Summary: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: James.Dutton(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org AMD Vega 56 fails to reset: [ 188.771043] Evicting PASID 32782 queues [ 188.782094] Restoring PASID 32782 queues [ 214.563362] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=19285, emitted seq=19287 [ 214.563432] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ACOdyssey.exe pid 3761 thread ACOdyssey.exe pid 3761 [ 214.563439] amdgpu 0000:43:00.0: GPU reset begin! [ 214.563445] Evicting PASID 32782 queues [ 224.793032] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:49:crtc-0] hw_done or flip_done timed out How do I go about diagnosing this problem? -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 110472] Graphical Fault (Desktop Freeze) on Specific OpenGL Application
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

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

1 0

[Bug 110370] Rendering artifacts in Enter The Gungeon on Both RX 590 and Radeon 7
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110370 Bug ID: 110370 Summary: Rendering artifacts in Enter The Gungeon on Both RX 590 and Radeon 7 Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: Sonicadvance1(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I have rendering artifacts in Enter the Gungeon with RadeonSI. Bug was reproduced on both a Radeon 7 and an RX590 using Mesa git versions The game rendering is fairly simple and may not be too hard to track down. The rendering artifact is the shimmering around texture edges in the video I will provide. I've also attached a renderdoc capture of a frame in the game where the artifacting is occurring. Additionally the game is running very slowly due to massive amounts of futex usages, but I can trace back if those are coming game side or driver side. Video: https://drive.google.com/file/d/1NNA_lCY5FqzxpYtf1DIreZ8i7BKATTn9/view?usp=… RenderDoc capture: https://drive.google.com/file/d/1P1Dr2g4L8LpC7CBfVmriWX8X7F-mLx0w/view?usp=… -- You are receiving this mail because: You are the assignee for the bug.

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019