dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 111236] VA-API radeonsi SIGSEGV __memmove_avx_unaligned
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=111236 Bug ID: 111236 Summary: VA-API radeonsi SIGSEGV __memmove_avx_unaligned Product: Mesa Version: 19.1 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: liewkj(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org Hardware: Ryzen 2500U Mobile APU Vega 8 OS: ArchLinux 5.2.3-arch1-1-ARCH GUI: GNOME/Wayland $ gst-play-1.0 /path/to/H264.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/kliew/Videos/Dark Phoenix.mp4 mesa: for the -simplifycfg-sink-common option: may only occur zero or one times! mesa: for the -global-isel-abort option: may only occur zero or one times! Redistribute latency... Redistribute latency... Segmentation fault (core dumped) Thread 4 "multiqueue0:src" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff5cc3700 (LWP 4886)] 0x00007ffff7f42c05 in __memmove_avx_unaligned () from /usr/lib/libc.so.6 (gdb) disas Dump of assembler code for function __memmove_avx_unaligned: 0x00007ffff7f42be0 <+0>: endbr64 0x00007ffff7f42be4 <+4>: mov rax,rdi 0x00007ffff7f42be7 <+7>: cmp rdx,0x20 0x00007ffff7f42beb <+11>: jb 0x7ffff7f42ca6 <__memmove_avx_unaligned_erms+86> 0x00007ffff7f42bf1 <+17>: cmp rdx,0x40 0x00007ffff7f42bf5 <+21>: ja 0x7ffff7f42d13 <__memmove_avx_unaligned_erms+195> 0x00007ffff7f42bfb <+27>: vmovdqu ymm0,YMMWORD PTR [rsi] 0x00007ffff7f42bff <+31>: vmovdqu ymm1,YMMWORD PTR [rsi+rdx*1-0x20] => 0x00007ffff7f42c05 <+37>: vmovdqu YMMWORD PTR [rdi],ymm0 0x00007ffff7f42c09 <+41>: vmovdqu YMMWORD PTR [rdi+rdx*1-0x20],ymm1 0x00007ffff7f42c0f <+47>: vzeroupper 0x00007ffff7f42c12 <+50>: ret End of assembler dump. (gdb) bt #0 0x00007ffff7f42c05 in __memmove_avx_unaligned () from /usr/lib/libc.so.6 #1 0x00007fffda85d3e3 in ?? () from /usr/lib/dri/radeonsi_dri.so #2 0x00007fffda85d4f7 in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x00007fffdb108133 in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x00007fffe77a4903 in ?? () from /usr/lib/dri/radeonsi_drv_video.so #5 0x00007ffff4976ffd in vaPutImage () from /usr/lib/libva.so.2 #6 0x00007ffff49f4c1e in ?? () from /usr/lib/gstreamer-1.0/libgstvaapi.so #7 0x00007ffff4a2ecf3 in ?? () from /usr/lib/gstreamer-1.0/libgstvaapi.so #8 0x00007ffff4a2f2bf in ?? () from /usr/lib/gstreamer-1.0/libgstvaapi.so #9 0x00007ffff4a2703b in ?? () from /usr/lib/gstreamer-1.0/libgstvaapi.so #10 0x00007ffff782fe53 in ?? () from /usr/lib/libgstbase-1.0.so.0 #11 0x00007ffff7835ee1 in ?? () from /usr/lib/libgstbase-1.0.so.0 #12 0x00007ffff7a3bcca in gst_pad_query () from /usr/lib/libgstreamer-1.0.so.0 #13 0x00007ffff7a3c3de in gst_pad_peer_query () from /usr/lib/libgstreamer-1.0.so.0 #14 0x00007ffff7a0a887 in gst_pad_peer_query_caps () from /usr/lib/libgstreamer-1.0.so.0 #15 0x00007ffff7835cd1 in ?? () from /usr/lib/libgstbase-1.0.so.0 -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 111235] radeonsi_drv_video.so should report support for packed headers
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=111235 Bug ID: 111235 Summary: radeonsi_drv_video.so should report support for packed headers 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: oreaus(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144894 --> https://bugs.freedesktop.org/attachment.cgi?id=144894&action=edit Proposed fix for mkv with vaapi Trying to encode using vaapi fails if the container is mkv. Changing the output format to .mp4 in the command works. How to reproduce: `ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i input.mp4 -vf 'hwupload' -vcodec h264_vaapi -bf 0 output.mkv` Output: `Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input Error initializing output stream 0:0 -- Conversion failed!` Expected: Works without error. Proposed: Patch attached. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 111111] Corrupted output with vaapi 10 bit -> 8 bit transcoding on AMD RAVEN
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=111111 Bug ID: 111111 Summary: Corrupted output with vaapi 10 bit -> 8 bit transcoding on AMD RAVEN 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: gregor(a)outlook.com QA Contact: dri-devel(a)lists.freedesktop.org Initially, I've filled ffmpeg bug since vaapi transcoding 10 bit > 8 bit was just failing, someone refereed to a "separated field of surfaces bug" which I couldn't find and offered patch which fixed the initial issue here: https://trac.ffmpeg.org/ticket/7764 After applying patch transcoding goes through with significant speed increase [from 2x to 7x] but the resulting output has flashing green overlay/glitch in upper half of the video. E.g from command" ffmpeg -threads 4 \ -init_hw_device vaapi=amd:/dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device amd -filter_hw_device amd \ -i trk.mkv \ -vf "scale_vaapi=format=nv12,hwupload" \ -c:v h264_vaapi -profile:v 578 \ -c:a copy -bf 0 -c:s copy \ -f mpegts -y plop.mkv Input is any 10 bit hevc video. Vainfo:libva info: VA-API version 1.6.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.6 (libva 2.6.0.pre1) vainfo: Driver version: Mesa Gallium driver 19.2.0-devel for AMD RAVEN (DRM 3.32.0, 5.2.0-gentoo, LLVM 8.0.0) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc mesa git AMD RAVEN APU 2200G -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=111077 Bug ID: 111077 Summary: link_shader and deserialize_glsl_program suddenly consume huge amount of RAM Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: roland(a)rptd.ch QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144715 --> https://bugs.freedesktop.org/attachment.cgi?id=144715&action=edit Valgrind massif log Since a recent update a few days ago an application which barely consumes 2G RAM at full load is very slow to load and compiling shaders causes over 16G RAM to be consumed when the app eventually crashes. I don't know what exactly in the update caused problems but certainly Mesa, the amdgpu driver and LLVM did get updates. I also tried using Mesa 19.x but the problem is the same. Driver is xf86-video-amdgpu-19.0.1 . LLVM is 7.0.x . I've already deleted the mesa shader cache and all caches the application creates. I've totally recompiled the system (GenToo) to make sure no strange problems can be around. I've also tried with a completely fresh user to run the app. Using valgrind --tool=massif the culprit seems to be ralloc_size which is called by the two above mentioned methods. I've attached a massif log of a couple of seconds running of the application and shutting it down before memory skyrockets even more. The app in question shows at that point of time only an empty scene with a simple shader doing a sky-box. The rest is Non OpenGL UI stuff. Classified this as blocker since as soon as you try loading more shaders not even 32G seems to be enough to cope with the rampaging glsl compiler. -- You are receiving this mail because: You are the assignee for the bug.

1 47

[Bug 111076] Building error after commit b52bf8f12a ("amd/common/gfx10: support new tbuffer encoding")
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=111076 Bug ID: 111076 Summary: Building error after commit b52bf8f12a ("amd/common/gfx10: support new tbuffer encoding") Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: other Status: NEW Severity: critical Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: issor.oruam(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Hi, I'm getting the following building error, even if I'm using prescribed LLVM8 and libdrm 2.4.99: external/mesa/src/amd/common/ac_llvm_build.c:1496:45: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_8_UINT' case V_008F0C_BUF_DATA_FORMAT_8: format = V_008F0C_IMG_FORMAT_8_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1497:47: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_8_8_UINT' case V_008F0C_BUF_DATA_FORMAT_8_8: format = V_008F0C_IMG_FORMAT_8_8_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1498:51: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_8_8_8_8_UINT' case V_008F0C_BUF_DATA_FORMAT_8_8_8_8: format = V_008F0C_IMG_FORMAT_8_8_8_8_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1499:46: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_16_UINT' case V_008F0C_BUF_DATA_FORMAT_16: format = V_008F0C_IMG_FORMAT_16_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1500:49: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_16_16_UINT' case V_008F0C_BUF_DATA_FORMAT_16_16: format = V_008F0C_IMG_FORMAT_16_16_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1501:55: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_16_16_16_16_UINT' case V_008F0C_BUF_DATA_FORMAT_16_16_16_16: format = V_008F0C_IMG_FORMAT_16_16_16_16_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1502:46: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_32_UINT' case V_008F0C_BUF_DATA_FORMAT_32: format = V_008F0C_IMG_FORMAT_32_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1503:49: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_32_32_UINT' case V_008F0C_BUF_DATA_FORMAT_32_32: format = V_008F0C_IMG_FORMAT_32_32_UINT; break; ^ external/mesa/src/amd/common/ac_llvm_build.c:1504:55: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_32_32_32_32_UINT' case V_008F0C_BUF_DATA_FORMAT_32_32_32_32: format = V_008F0C_IMG_FORMAT_32_32_32_32_UINT; break; ^ 9 errors generated. Could you please check if some include is missing or what library is supposed to provide those definitions? Mauro -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 110850] Vlc fails to decode video using vaapi
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110850 Bug ID: 110850 Summary: Vlc fails to decode video using vaapi Product: Mesa Version: 19.1 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: akarshanbiswas(a)fedoraproject.org QA Contact: dri-devel(a)lists.freedesktop.org Tested Mesa version: 19.1.0 rc4, 19.0.5 Operating System: Fedora 30 with kernel 5.1.6 VLC version: 3.0.7 Vetinari (revision 3.0.6-223-g5fc4822ace) GPU's tested: Both on Radeon RX550 and AMD APU a9-9410(stoney series) Testing on both Xorg and Wayland This bug is present since long time, selecting either vaapi video decoder or vaapi video decoder via drm in vlc--> toos --> preferences--> Input/Codecs --> hardware accelerated decoding fails and vlc switches to either vdpau or software decoding. (vdpau driver can't decode some hevc videos, vdpau is not supported on wayland) Steps to reproduce: 1) After selecting vaapi video decoder in vlc, run vlc on a terminal with the -v flag (for verbose) 2) play any media 3) Check the terminal ( Meanwhile vlc will try to switch to vdpau) Actual results: vlc's vaapi decoder fails with: ``` libva info: VA-API version 1.4.1 libva info: va_getDriverName() returns 0 libva info: User requested driver 'radeonsi' libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_4 libva info: va_openDriver() returns 0 [00007f4c78001f60] glconv_vaapi_x11 gl error: vaDeriveImage: operation failed [00007f4c7c062b30] main video output error: video output creation failed [00007f4c88056060] main decoder error: failed to create video output ``` Expected result: Vlc should play vaapi as it does in Intel GPUs. I have a vlc bug ticket which says that the driver is buggy here: https://trac.videolan.org/vlc/ticket/21194 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 110813] Vega hung on Surviving Mars game
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110813 Bug ID: 110813 Summary: Vega hung on Surviving Mars game 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: stalkerg(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 144414 --> https://bugs.freedesktop.org/attachment.cgi?id=144414&action=edit kernel log It happens every time after +-20 min of the gaming. (I have already many items on the map) it's happened last few months after update to kernel 5.0. Kernel - 5.1.6-gentoo GPU - Vega56 from glxinfo: Radeon RX Vega (VEGA10, DRM 3.30.0, 5.1.6-gentoo, LLVM 9.0.0) Mesa 19.2.0-devel (git-47a10edefb) Call trace and error log in attachment. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 110786] Adaptive sync (vrr, freesync): Cinnamon DE isn't blacklisted properly
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110786 Bug ID: 110786 Summary: Adaptive sync (vrr, freesync): Cinnamon DE isn't blacklisted properly 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: dron1885(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Hello, Despite the muffin being blacklisted, Cinnamon still use adaptive sync causing flicker and mouse stuttering. Adding cinnamon manually to 00-mesa-defaults.conf solves issue: <application name="cinnamon" executable="cinnamon"> <option name="adaptive_sync" value="false" /> </application> Not sure if issue existing on all Linux distros, but my Arch is affected. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 110719] Crash in radeon_drv_video.so when attempting to convert rgb video data
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110719 Bug ID: 110719 Summary: Crash in radeon_drv_video.so when attempting to convert rgb video data 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: oreaus(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Kernel 5.0.0 Mesa 19.2.0-devel (git-629806b55b) OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.27.0, 5.0.0, LLVM 8.0.0) I can reproduce the crash with this command: `ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i input.mp4 -vf 'format=rgb0,hwupload' -vcodec h264_vaapi -bf 0 output.mp4` The input video does not have to be rgb0 format, this command just tells it that it is to demonstrate the problem. av_hwframe_transfer_get_formats() reports rgb0 is supported but clearly there's a problem. This is the backtrace for h264_vaapi: Thread 1 "ffmpeg" received signal SIGSEGV, Segmentation fault. create (enc=0x555555ec73a0) at ../src/gallium/drivers/radeon/radeon_vce_52.c:188 188 RVCE_CS(enc->chroma->u.legacy.level[0].nblk_x * enc->chroma->bpe); // encRefPicChromaPitch (gdb) bt full #0 0x00007fffd740a407 in create (enc=0x555555ec73a0) at ../src/gallium/drivers/radeon/radeon_vce_52.c:188 begin = 0x7fffc060102c sscreen = 0x555555812020 #1 0x00007fffd73bfe13 in rvce_begin_frame (encoder=0x555555ec73a0, source=0x5555561c2ea0, picture=<optimized out>) at ../src/gallium/drivers/radeon/radeon_vce.c:291 fb = {usage = 4, res = 0x555555ed02f0} enc = 0x555555ec73a0 vid_buf = 0x5555561c2ea0 pic = <optimized out> need_rate_control = true #2 0x00007fffd72d32ed in vlVaEndPicture (ctx=<optimized out>, context_id=<optimized out>) at ../src/gallium/state_trackers/va/picture.c:655 drv = 0x55555580c6c0 context = 0x555555ec3180 coded_buf = 0x5555561e6360 surf = 0x5555561f0320 feedback = 0x555555a6eec0 screen = <optimized out> supported = <optimized out> realloc = <optimized out> format = <optimized out> #3 0x00007ffff085d820 in vaEndPicture () at /usr/lib/x86_64-linux-gnu/libva.so.2 #4 0x00007ffff6212e53 in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #5 0x00007ffff6213149 in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #6 0x00007ffff62137be in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #7 0x00007ffff5dbc6c7 in avcodec_encode_video2 () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #8 0x00007ffff5dbcaad in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #9 0x00007ffff5dbcc5a in avcodec_send_frame () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 and for hevc_vaapi: Thread 1 "ffmpeg" received signal SIGSEGV, Segmentation fault. 0x00007fffd7406f4f in radeon_uvd_enc_encode_params_hevc (enc=0x555555ec7040) at ../src/gallium/drivers/radeon/radeon_uvd_enc_1_1.c:972 972 enc->enc_pic.enc_params.allowed_max_bitstream_size = enc->bs_size; (gdb) bt full #0 0x00007fffd7406f4f in radeon_uvd_enc_encode_params_hevc (enc=0x555555ec7040) at ../src/gallium/drivers/radeon/radeon_uvd_enc_1_1.c:972 sscreen = 0x555555812020 #1 0x00007fffd7406f4f in encode (enc=0x555555ec7040) at ../src/gallium/drivers/radeon/radeon_uvd_enc_1_1.c:1104 #2 0x00007fffd72d3304 in vlVaEndPicture (ctx=<optimized out>, context_id=<optimized out>) at ../src/gallium/state_trackers/va/picture.c:656 drv = 0x55555580c6c0 context = 0x555555ec4420 coded_buf = 0x555555ec6180 surf = 0x5555561f0570 feedback = 0x5555557bd0c0 screen = <optimized out> supported = <optimized out> realloc = <optimized out> format = <optimized out> #3 0x00007ffff085d820 in vaEndPicture () at /usr/lib/x86_64-linux-gnu/libva.so.2 #4 0x00007ffff6212e53 in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #5 0x00007ffff6213149 in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #6 0x00007ffff62137be in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #7 0x00007ffff5dbc6c7 in avcodec_encode_video2 () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #8 0x00007ffff5dbcaad in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #9 0x00007ffff5dbcc5a in avcodec_send_frame () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 It seems the driver should support this format or at least just report only the formats it actually supports. Please note that this bug was discovered by a screen recorder implementing vaapi. Passing rgb data to the intel vaapi driver works as expected. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 110713] A Hat in Time: GPU hang with gallium nine
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110713 Bug ID: 110713 Summary: A Hat in Time: GPU hang with gallium nine 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: lolisamurai(a)tfwno.gf QA Contact: dri-devel(a)lists.freedesktop.org when using gallium nine, A Hat in Time locks up the entire system (requires a hard reboot) on certain scenes. I'm running a r9 270x with the amdgpu driver and mesa-git 110950.fc455797c1b-1 + llvm-svn 360675-1 this issue was discussed with the gallium nine guys here: https://github.com/iXit/wine-nine-standalone/issues/35 and they narrowed it down to radeonsi using AMD_DEBUG=mono fixes the issue this is the apitrace for gallium nine https://mega.nz/#!ZJhRhYaR!cVsMkRYkl6kPl0f43sMKu8NI4pvA4eE85cbLJyoQ-jE the hang happens on the very last part of the trace, when the green goo in the middle of the room is on screen. the area is chapter3, act6 and all other challenges that take place there playing back the trace also causes the same hang. playing back the trace with AMD_DEBUG=mono works correctly without any hangs other users report that turning off dynamic lights also fixes the issue another user reported a similar hang in chapter 1, act 4 with this apitrace https://kiwii.casa/downloads/d3d9.trace.xz -- 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