dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 68857] New: SNU OpenCL NAS Parallel Benchmarks don't work
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=68857 Priority: medium Bug ID: 68857 Assignee: dri-devel(a)lists.freedesktop.org Summary: SNU OpenCL NAS Parallel Benchmarks don't work Severity: normal Classification: Unclassified OS: Linux (All) Reporter: nat(a)ferrus.net Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa None of the benchmarks in the SNU OpenCL NAS Parallel Benchmarks are working. They're available from http://aces.snu.ac.kr/Center_for_Manycore_Programming/SNU_NPB_Suite.html I've got a Radeon 5830 and have installed Mesa from git using the instructions at http://dri.freedesktop.org/wiki/GalliumCompute/ Most of the benchmarks fail at Running pass 'AMDGPU DAG->DAG Pattern Instruction Selection' on function The FFT benchmark fails at error: parameter may not be qualified with an address space I do have some other test cases that are working for me, including the ones from http://cgit.freedesktop.org/~tstellar/opencl-example/ -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 68799] New: [APITRACE] Hyper-Z lockup with Falcon BMS 4.32u6 on CAYMAN
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=68799 Priority: medium Bug ID: 68799 Assignee: dri-devel(a)lists.freedesktop.org Summary: [APITRACE] Hyper-Z lockup with Falcon BMS 4.32u6 on CAYMAN Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sthalik(a)misaki.pl Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa apitrace file not attached due to size. http://ananke.laggy.pk/wine-preloader.trace.xz Causes lockup before finishing on CAYMAN 6970 and today's git unless HYPERZ is disabled. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 68792] New: Problems during playback of h264 files using UVD and VLC on AMD E-350 CPU
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=68792 Priority: medium Bug ID: 68792 Assignee: dri-devel(a)lists.freedesktop.org Summary: Problems during playback of h264 files using UVD and VLC on AMD E-350 CPU Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rvdb(a)cryptolab.net Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 84971 --> https://bugs.freedesktop.org/attachment.cgi?id=84971&action=edit vlc -vvv output log I have a small system with a E350 CPU in it and try to use a recent git pull of VLC, mesa and xfree86-video-ati, on a 3.11rc6 kernel, to run with VDPAU and the UVD chip on the CPU. VLC indeed manages to play H264 files in DVD resolution but : 1/ It seems to fail on color space matrix : [0x7ffa0f00c288] vdpau_chroma filter debug: using video mixer sharpness feature [0x7ffa0f00c288] vdpau_chroma filter error: video color space matrix failure: An invalid pointer was provided. Typically, this means that a NULL pointer was provided for an 'output' parameter. [0x7ffa0f00c288] vdpau_chroma filter debug: using video mixer 7 2/ it regularly spits "vo messages like this : [0x7ffa14001248] vdpau_display vout display debug: surface status: 2 3/ regularly, it spits "warning: picture is too late to be displayed (missing 113 ms)" messages 4/ regularly stalls with messages like this : [CODE][0x7f08e0c1f3f8] main input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 1000 ms [0x7f08e0c1f3f8] main input error: ES_OUT_RESET_PCR called [0x7f08a0001248] vdpau_display vout display debug: surface status: 2 [0x7f08d91e7188] main decoder warning: early picture skipped[/CODE] On the same system, mplayer from 2013/08/19 plays the same file, using VDPAU and UVD (checked watching the CPU usage) fine. I opened a bug on the VLC bug tracker (https://trac.videolan.org/vlc/ticket/9281) but according to them, the problem seems to come from the Galllium VDPAU state tracker as they should not get "surface status : 2" at this stage of their code (they obviously tested their VDPAU implementation using Nvidia binary driver, which does not use the VDPAU Gallium state tracker). Mplayer doesn't seem to have problem here as it seems to not even try to support CSC matrix generation or decoder capabilities. I'm sorry if this bug report is a bit of a mess. There may be several issues involved here, and some may be more VLC-related that mesa, but I don't know at all how to sort them out. The VLC devs at least seem to consider that the "surface status : 2" and CSC matrix generation problem are Gallium-related and need to be fixed before they can look into the problem if it's still there. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 68468] New: 9.2.0rc2 Locks Under Various Conditions (UVD, Stress)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=68468 Priority: medium Bug ID: 68468 Assignee: dri-devel(a)lists.freedesktop.org Summary: 9.2.0rc2 Locks Under Various Conditions (UVD, Stress) Severity: major Classification: Unclassified OS: Linux (All) Reporter: adam777(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/DRI/R600 Product: Mesa Using 9.2.0rc2 on a fully updated Arch Linux (running on [testing]), the system will lock under the following conditions: 1. When playing a movied in mpv using UVD video decoding, the system will lock as soon as mpv finish the initial loading process and playback is about to begin. 2. When playing a game in Wine, system will lock after a few seconds of launch. 3. From time to time, the system will lock for no apparent reason (for example, it happened when using Google Maps). All of the above (except UVD, of course) work fine under 9.1.6 Mesa Version: (for rc1, but rc2 have the same behavior) [adamdagan@admdgn ~]$ glxinfo | grep ^OpenGL | egrep 'version|renderer' OpenGL renderer string: Gallium 0.4 on AMD RV710 OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0-rc1 OpenGL core profile shading language version string: 1.40 OpenGL version string: 3.0 Mesa 9.2.0-rc1 OpenGL shading language version string: 1.30 -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 67888] New: R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67888 Priority: medium Bug ID: 67888 Assignee: dri-devel(a)lists.freedesktop.org Summary: R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace Severity: major Classification: Unclassified OS: Linux (All) Reporter: fossphreak(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 83811 --> https://bugs.freedesktop.org/attachment.cgi?id=83811&action=edit dmesg contents after GPU hangup occurred I had used apitrace to trace Trine 2 OpenGL calls. When I tried to profile the trace, display corruption and GPU hangup occurred. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 67849] New: continuos reboots
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67849 Priority: medium Bug ID: 67849 Assignee: dri-devel(a)lists.freedesktop.org Summary: continuos reboots Severity: critical Classification: Unclassified OS: Linux (All) Reporter: markurujapan(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/Radeon Product: Mesa I can't use opensource drivers with my apu a8 5600k(radeon 7650d) on linux. I tried with linux kernel 3.10, 3.11 rc, mesa, mesa git, xf86 ati, git..etc. The problem persist, every 20/30 minutes my apu suddenly reboot, it's so strange, because this doesn't happen with catalyst driver( but closed driver is so slow for me..). I don't know what is the origin of the problem. :( -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 67724] New: [r600g] WoW slowdown with HD6450
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67724 Priority: medium Bug ID: 67724 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] WoW slowdown with HD6450 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rankincj(a)googlemail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Playing WoW with Mesa-git recently, and I discovered that the frame rate had dropped by ~10 FPS. (From 25 FPS to 15 FPS). A git bisect identifies this commit: $ git bisect bad 6a2baf3a06125405aa648e208af782e53f1312c0 is the first bad commit commit 6a2baf3a06125405aa648e208af782e53f1312c0 Author: Paul Berry <stereotype441(a)gmail.com> Date: Mon Jun 10 14:01:45 2013 -0700 glsl/linker: Make update_array_sizes apply to just uniforms. Commit 586b4b5 (glsl: Also update implicit sizes of varyings at link time) extended update_array_sizes() to apply to both uniforms and shader ins/outs. However, doing creates problems for geometry shaders, because update_array_sizes() assumes that variables with matching names in different parts of the pipeline should have the same sizes. With the addition of geometry shaders, this is no longer true (e.g. both vertex and geometry shaders have a gl_ClipDistance output variable, but there's no reason these variables should have the same sizes). The original reason for commit 586b4b5 (avoid problems with gl_TexCoord being 0 length) has since been addressed by commit 6f53921 (linker: Ensure that unsized arrays have a size after linking). So go ahead and switch update_array_sizes() back to only acting on uniforms. Reviewed-by: Ian Romanick <ian.d.romanick(a)intel.com> Reviewed-by: Kenneth Graunke <kenneth(a)whitecape.org> :040000 040000 304adffc0a8c034063a526a7d693fe792399a7d9 77b9d43aacde4ec2172578b7158399d94f6e3b2e M src -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 67265] New: r600g causes KWin crashes with kernel 3.9
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67265 Priority: medium Bug ID: 67265 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600g causes KWin crashes with kernel 3.9 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: nikoli(a)lavabit.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.1 Component: Drivers/Gallium/r600 Product: Mesa With FOSS radeon driver kwin crashes after unlocking session when it was locked for several (8-10) hours. If it was locked only for several minutes it will not crash. Sometimes it does not crash even when locked for hours. No 3D apps are working until X is restarted. https://bugs.kde.org/show_bug.cgi?id=322773 Versions: [ebuild R ~] media-libs/mesa-9.1.4 USE="egl gallium gbm gles2 nptl openvg pax_kernel shared-glapi wayland xa xorg -bindist -classic -debug -gles1 -llvm -osmesa -pic (-r600-llvm-compiler) (-selinux) -vdpau -xvmc" PYTHON_SINGLE_TARGET="python2_7 -python2_6" PYTHON_TARGETS="python2_7 -python2_6" VIDEO_CARDS="r600 radeon -i915 -i965 -intel -nouveau -r100 -r200 -r300 (-radeonsi) -vmware" 0 kB [ebuild R ] x11-libs/libdrm-2.4.45 USE="libkms -static-libs" VIDEO_CARDS="radeon (-exynos) (-freedreno) -intel -nouveau (-omap) -vmware" 0 kB [ebuild R ] x11-base/xorg-server-1.13.4:0/1.13.4 USE="ipv6 nptl suid udev xorg xvfb -dmx -doc -kdrive -minimal (-selinux) -static-libs -tslib -xnest" 0 kB [ebuild R ] kde-base/kwin-4.10.4:4 USE="opengl (-aqua) -debug -gles" 0 kB [ebuild R ~] x11-drivers/xf86-video-ati-7.1.0 USE="udev -glamor" 0 kB [ebuild R ] dev-qt/qtgui-4.8.4-r1:4 USE="accessibility cups dbus exceptions gif glib mng qt3support tiff xinerama xv (-aqua) -c++0x -debug -egl -gtkstyle -nas -nis (-pch) -trace" 0 kB -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 67016] New: Lockup on piglit test vs-textureSize-compare with AMD 6950
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=67016 Priority: medium Bug ID: 67016 Assignee: dri-devel(a)lists.freedesktop.org Summary: Lockup on piglit test vs-textureSize-compare with AMD 6950 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: g02maran(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI I'm running kernel http://cgit.freedesktop.org/~agd5f/linux/?h=drm-fixes-3.11 with latest commit 444bddc4b9b3313a562cd3ba40f780fb82570f7d and mesa master with latest commit e4fdf1b008ce29c5b5a52985c586b61f35d31e4c When I run spec/glsl-1.30/execution/vs-textureSize-compare my system locks up. I can't reboot or ssh into it, I have the power cycle the machine to reset it. Nothing is printed to dmesg before it hangs. I have tried both with and without radeon.dpm=1, no difference. I did a bisect and it identified this commit: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.11&id=1c0110… -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 66964] New: GPU fault detected
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=66964 Priority: medium Bug ID: 66964 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU fault detected Severity: normal Classification: Unclassified OS: All Reporter: udovdh(a)xs4all.nl Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Hello, See https://bugs.freedesktop.org/show_bug.cgi?id=62959 as reference. I turned off RADEON_VA=0 and R600_DEBUG=nodma and after a while I got the output below (and a reboot) while surfing the web, checking videos from youtube, etc. I use git everything on A10-5800K which has ARUBA (Cayman) GPU with kernel.org 3.9.9. What is the cause? And how can we fix this? Jul 16 16:00:01 surfplank2 kernel: [178650.498628] radeon 0000:00:01.0: GPU fault detected: 147 0x0db67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498633] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00001EDB Jul 16 16:00:01 surfplank2 kernel: [178650.498635] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06071002 Jul 16 16:00:01 surfplank2 kernel: [178650.498638] radeon 0000:00:01.0: GPU fault detected: 147 0x0db67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498640] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498643] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498645] radeon 0000:00:01.0: GPU fault detected: 146 0x01f67104 Jul 16 16:00:01 surfplank2 kernel: [178650.498647] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498649] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498652] radeon 0000:00:01.0: GPU fault detected: 146 0x02067104 Jul 16 16:00:01 surfplank2 kernel: [178650.498654] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498656] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498658] radeon 0000:00:01.0: GPU fault detected: 146 0x02067104 Jul 16 16:00:01 surfplank2 kernel: [178650.498660] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498662] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498664] radeon 0000:00:01.0: GPU fault detected: 147 0x03b67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498667] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498669] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498671] radeon 0000:00:01.0: GPU fault detected: 147 0x03c67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498673] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498675] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498677] radeon 0000:00:01.0: GPU fault detected: 147 0x03c67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498679] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498681] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498683] radeon 0000:00:01.0: GPU fault detected: 147 0x03c67102 Jul 16 16:00:01 surfplank2 kernel: [178650.498685] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498687] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498690] radeon 0000:00:01.0: GPU fault detected: 146 0x02067104 Jul 16 16:00:01 surfplank2 kernel: [178650.498692] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498694] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06071004 Jul 16 16:00:01 surfplank2 kernel: [178650.498711] radeon 0000:00:01.0: GPU fault detected: 146 0x09767104 Jul 16 16:00:01 surfplank2 kernel: [178650.498713] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jul 16 16:00:01 surfplank2 kernel: [178650.498715] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Kind regards, Udo -- 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