dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105145 Bug ID: 105145 Summary: vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically Product: Mesa Version: git Hardware: All OS: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: k.philipp(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org When decoding interlaced video with VAAPI and least when using the radeonsi driver, it is impossible to postproc-deinterlace a frame from a surface that was used with vaExportSurfaceHandle() before. This effectively means that it is impossible to dynamically switch on deinterlacing mid-stream, i.e. after an *interlaced* frame has been shown unprocessed with vaExportSurfaceHandle. Try for example with mpv from git: mpv -vo gpu --hwdec=vaapi /path/to/interlaced/video.mkv (add --gpu-context=wayland when running under Wayland, else vaapi will not work) give it a few seconds and then switch on deinterlacing with the 'd' key. You will see the error mesage "vaRenderPicture() failed (invalid VASurfaceID)" and not get any deinterlacing. Having deinterlacing enabled from the beginning (e.g. with "--deinterlace=yes") works, since no unprocesssed surface is exported then. The chain of events seems to be: - Create surfaces for decoding. They are marked interlaced by default on radeonsi. (see https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/radeonsi/si… - PREFERS_INTERLACED is always returned as true) - Export the decoded surfaces with vaExportSurfaceHandle() and present them to the user. This has the side-effect of making the surfaces non-interlaced (see https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/va/s…) - Now we want to turn on postproc. - Create surfaces for postproc. They are, again, marked interlaced by default - Trying to deinterlace gives VA_STATUS_ERROR_INVALID_SURFACE_ID since it thinks that the source surface is not interlaced, and that the destination surface is - both of which is wrong (see https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/va/p…) Reporting this against the radeonsi driver since I couldn't test with anything else, but the issue may really be in how vlVaExportSurfaceHandle works on all drivers. On a related note, since the radeonsi driver by default generates interlaced surfaces when using vaCreateSurfaces, vlVaExportSurfaceHandle making them progressive seems to be the only reason it correctly bob-deinterlaces at the moment (MADI seems to be fine because it uses another code path). At least after all output surfaces have been exported once, before that it just blits. I also consider this a bug that could now be solved at the same time. If not, I can open a new ticket for that. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 105140] clearing related crash in Dying Light
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105140 Bug ID: 105140 Summary: clearing related crash in Dying Light 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: notasas(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org util_format_write_4f() gets called with a pipe_format PIPE_FORMAT_Z24_UNORM_S8_UINT that has no pack_rgba_float() Thread 9 "gallium_drv:0" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f78b1397700 (LWP 30748)] #0 0x0000000000000000 in ?? () #1 0x00007f78baf0e547 in util_format_write_4f (format=PIPE_FORMAT_Z24_UNORM_S8_UINT, src=0x1eb422c, src_stride=0, dst=0x7f78b13963a0, dst_stride=0, x=0, y=0, w=1, h=1) at util/u_format.c:337 #2 0x00007f78bafd5853 in util_pack_color (rgba=0x1eb422c, format=PIPE_FORMAT_Z24_UNORM_S8_UINT, uc=0x7f78b13963a0) at ../../../../src/gallium/auxiliary/util/u_pack_color.h:433 #3 0x00007f78bafd5ad0 in si_set_clear_color (rtex=0x141f56e0, surface_format=PIPE_FORMAT_Z24_UNORM_S8_UINT, color=0x1eb422c) at si_clear.c:89 #4 0x00007f78bafd69f3 in si_do_fast_color_clear (sctx=0x1d60690, buffers=0x7f78b1396474, color=0x1eb422c) at si_clear.c:508 #5 0x00007f78bafd6b29 in si_clear (ctx=0x1d60690, buffers=4, color=0x1eb422c, depth=0, stencil=0) at si_clear.c:527 #6 0x00007f78baf344e7 in tc_batch_execute (job=job@entry=0x1eb4180, thread_index=thread_index@entry=0) at util/u_threaded_context.c:96 #7 0x00007f78badbb03f in util_queue_thread_func (input=input@entry=0x1e81550) at u_queue.c:271 #8 0x00007f78badbabc7 in impl_thrd_routine (p=<optimized out>) at ../../include/c11/threads_posix.h:87 #9 0x00007f78ce8e06ba in start_thread (arg=0x7f78b1397700) at pthread_create.c:333 #10 0x00007f78c734241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 105089] radeonsi GPU lockup / crash with wine [The Witcher 3]
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105089 Bug ID: 105089 Summary: radeonsi GPU lockup / crash with wine [The Witcher 3] Product: Mesa Version: 17.3 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: housegregory299(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Hi I have GPU lockup after few minutes of playing The Witcher 3 (the quest is Ciri's story: The King of the wolves) I use wine vanilla with patch: https://raw.githubusercontent.com/wine-compholio/wine-staging/master/patche… I also tried various wine vanilla and wine staging from 2.22 to 3.1. My specs are: Radeon R7 350 (02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] (rev 87)) Xorg 1.19.3 Linux 4.14.12 mesa-17.3.1 (I had same issue with mesa-git) llvm-5.0 OpenGL renderer string: AMD CAPE VERDE (DRM 3.19.0 / 4.14.12-gentoo, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.1 OpenGL core profile shading language version string: 4.50 Maybe I should do some tests here, but I don't know which of these. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 104696] line_smooth in the endpoints is not take effect
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104696 Bug ID: 104696 Summary: line_smooth in the endpoints is not take effect Product: Mesa Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: yhang01(a)163.com QA Contact: dri-devel(a)lists.freedesktop.org When use line_smooth, if it's a oblique line and make the wide bigger you will find the line_smooth is effect in the middle of the line but in the end of line it's like a line not use line_smooth, but if we use the swrast the line is look good. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 104604] [amdgpu/radeon][regression, CIK] Prefetch the compute shader to TC L2 (4a4ff66dbe) causes GPU VM errors when running OpenCL kernels on Hawaii
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104604 Bug ID: 104604 Summary: [amdgpu/radeon][regression, CIK] Prefetch the compute shader to TC L2 (4a4ff66dbe) causes GPU VM errors when running OpenCL kernels on Hawaii Product: Mesa Version: 17.1 Hardware: All OS: All Status: NEW Severity: critical Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: vedran(a)miletic.net QA Contact: dri-devel(a)lists.freedesktop.org Commit 4a4ff66dbe radeonsi: also prefetch compute shaders enabled prefetching the compute shader to TC L2 for CIK+. This causes GPU VM errors on Hawaii, Kabini, and likely other CIK GPUs when running certain OpenCL programs (it seems that the key is to call clCreateContext() twice or more, see below) with Clover, both with amdgpu and radeon kernel drivers. I have tested with 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT GL [FirePro W9100] [1002:67a0] on Fedora rawhide (28) with kernel 4.15.0-0.rc7.git2.1.fc28.x86_64. I'll minimize the example program that causes this (right now using GROMACS tests, but that's unnecessarily complex), and provide the details (grepped + full dmesg) in the comments for both amdgpu and radeon kernel drivers. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 104597] Compton weird colors
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104597 Bug ID: 104597 Summary: Compton weird colors 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: haagch(a)frickel.club QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136675 --> https://bugs.freedesktop.org/attachment.cgi?id=136675&action=edit Desktop with compton --backend glx RX 480, mesa master. Running compton --backend glx produces the effect in the attached image. The colors are corrupted, but some applications look correct. There is one situation where I have seen a similar effect not involving compton and that is kwin's window preview of SteamVR's vrmonitor: https://www.youtube.com/watch?v=IHHQS_Q5uqE. All other window previews work correctly, it's only the vrmonitor that's broken. But that's enough to say it's not a compton specific problem. -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 104596] GPU hang with janusvr (non-VR mode too)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104596 Bug ID: 104596 Summary: GPU hang with janusvr (non-VR mode too) 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: haagch(a)frickel.club QA Contact: dri-devel(a)lists.freedesktop.org RX 480, mesa master, drm-next-4.16-wip d9c47236f500494614a0d3a8e24d70e3c4da9efd (I'll have to try with mainline too) To reproduce Download JanusVR: http://downloads.janusvr.com/janusvr_linux.tar.gz Run ./janusvr -render 2d Click on the VR Sites Subreddit Tile. GPU hang -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 104481] GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104481 Bug ID: 104481 Summary: GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video Product: Mesa Version: git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: luis.p.mendes(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136527 --> https://bugs.freedesktop.org/attachment.cgi?id=136527&action=edit dmesg and iomem data from lockup obtained with glretrace I am getting GPU lockups while playing video on Kodi, but it also happened with other applications that play video, while OpenGL seems to be stable. The system seem to be more sensitive to VP9 encoded videos. The freeze happens both on amd64 as well as on armv7l platforms. I am also able to reproduce GPU hangs on amd64 while replaying a glretrace obtained with kodi on arm platform. The arm dmesg and traces show a clear GPU lockup, while amd64 dmesg isn't so clear, but the user experience is just the same, complete graphical system freeze, while machine is still working with ssh or remote connections. Please find amd64 logs in attachments, including iomem, dmesg and gdb traces. In both platforms I am using Ubuntu 17.10 with Mate desktop, and lightdm session manager, with libdrm-2.4.89, mesa-17.4 at commit "radv: Implement binning on GFX9." - 6a36bfc64d2096aa338958c4605f5fc6372c07b8 and kernel https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.16 at commit "drm/amdgpu: Correct the IB size of bo update mapping." - 104bd2ca1124dfd9aa904d5f5a96253ef2b580f6. Please note that the system was more stable a few weeks ago with drm-next-4.16 based on kernel 4.15-rc2, and a previous mesa version, I don't remember the actual commits, but despite it was more stable, both on arm as well as on amd64, both systems still crashed similarly, it just got more evident with these new versions. There are two distinct crash behaviours on amd64: the ones that I obtained while playing a video with kodi on amd64 and those that I obtained on amd64 by replaying an apitrace from the arm platform while playing a VP9 video with kodi. The first kind of crashes is detailed with logs kodi-processes_and_backtraces.txt and kodi-amdgpu_lockup_dmesg_and_iomem.txt. The second kind of crashes is detailed with logs glretrace-processes_and_backtraces.txt and glretrace-amdgpu_lockup_dmesg_and_iomem.txt. For some strange reason the amd64 platform is complaining about polaris11 firmware files, but they are in /lib/firmware and they taken by cloning https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git. I am using the same firmware files on armv7l and the same graphics card and it doesn't complain with the firmware. I can also provide the apitrace trace file, but it takes around 1GB of data. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 104456] unsupported feature 'separate color planes' in VCE x264 high profile
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104456 Bug ID: 104456 Summary: unsupported feature 'separate color planes' in VCE x264 high profile Product: Mesa Version: 17.3 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: janpieter.sollie(a)dommel.be QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136495 --> https://bugs.freedesktop.org/attachment.cgi?id=136495&action=edit mplayer decoding output The VAAPI encoder using Tonga and Fiji cards produces a correct stream when using the Baseline or Main profile, but using the High profile, the VCE uses the separate color planes feature, which produces an unplayable stream. I tried looking through the code, but couldn't find anything which looks like the root of the error. View attachment for mplayer output -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 104362] GPU fault detected on wine-nine Path of Exile
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104362 Bug ID: 104362 Summary: GPU fault detected on wine-nine Path of Exile 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: grantipak(a)gmail.com Created attachment 136347 --> https://bugs.freedesktop.org/attachment.cgi?id=136347&action=edit dmesg log When i start game Path of Exile on wine-nine computer freez. I can`t switch in kernel console. When i connect on ssh i can get dmesg output. Radeon HD 7950 (TAHITI) kernel 4.13.4 - 4.14.6 kernel module AMDGPU Mesa 17.2.1 - 17.3.1 wine-nine 2.20 - 2.21 -- You are receiving this mail because: You are the assignee for the bug.

1 31

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019