dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 90184] [r600g] GPU lockup when using kdenlive GPU acceleration
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=90184 Bug ID: 90184 Summary: [r600g] GPU lockup when using kdenlive GPU acceleration Product: Mesa Version: 10.5 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: paul(a)konecny.at QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 115343 --> https://bugs.freedesktop.org/attachment.cgi?id=115343&action=edit Journald output radeon ring 0 stalled for more than XXX msecs Hi, when grading a video with the new GPU-accelerated kdenlive frameworks branch I encounter a GPU lockup when I add three effects to a clip simultaneously (White balance(GPU), Saturation(GPU) and Deconvolution sharpen(GPU) ) and seek the timeline. I already filed a bugreport here https://bugs.kde.org/show_bug.cgi?id=346184 but I think the problem lies in the driver rather than the program because trying the same on Intel hardware slows the system but there is no crash / lockup. Fortunately I managed to recover the journal (is attached) I hope you can help me. Thanks! Hardware: HD 6970 (Cayman XT) Software: Archlinux Kernel 3.19.3 Mesa 10.5.4 Kdenlive stack: kdenlive frameworks git (PKGBUILD attached) mlt 0.9.6 (PKGBUILD attached) movit 1.1.3 GPU effects package (PKGBUILD attached) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 89619] Chrome crashes in 64 bit r600 driver while running google maps
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=89619 Bug ID: 89619 Summary: Chrome crashes in 64 bit r600 driver while running google maps Product: Mesa Version: unspecified 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: jrpstonecarver(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Sorry folks, I am new to this and will do my best. I first reported this bug to Google. They got all the data here: https://code.google.com/p/chromium/issues/detail?id=467821 and told me that this is a bug in the r600 driver. Back in December I updated from 32 bit Ubuntu 12.04 to 64 bit Ubuntu 14.04 and have had major stability issues with Chrome ever since, particularly while using Google Maps. This URL https://www.google.com/maps/place/Los+Gatos,+CA+95033/@37.1893925,-121.9894… was the first time I've managed to capture something that crashes chrome reliably, however. At their suggestion I tried running chrome with --disable-gpu and at least with a simple test the problem went away. I think these drivers are the default in Ubuntu now, but they seem to be causing me a lot of grief. You can pickup what Google got from the crash report Chrome sent to them from the bug listed above. And for the time being I will figure out how to run with --disable-gpu on all the time to see if that avoids my issue. Failing that I guess it's time to figure out how to go back to ATI's drivers. If there is additional data I can provide somehow, I am happy to try. I'm no wizard, but I will follow instructions and get whatever you need if possible. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 89029] System hangs and screen powers down and back up when setting "sky" texture on a surface in Tesseract/OctaForge
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=89029 Bug ID: 89029 Summary: System hangs and screen powers down and back up when setting "sky" texture on a surface in Tesseract/OctaForge Product: Mesa Version: 10.4 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: acerspyro(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org This is a bug that only happens in Tesseract / OctaForge (maybe affects other engines that I didn't test), but when I set a block's face to sky tex, my whole system hangs for about 15 seconds, then the screen goes to black, powers off, powers back on and the display is back, until it hangs entirely (the screen doesn't go blank this time). Using ATI Mobility Radeon HD5470 on an Acer Aspire 5742G-7353, OpenSUSE Tumbleweed. I couldn't get a backtrace due to my system being unrecoverable after the event. REISUB works, obviously. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 88574] VA-API on RV610 crashes my system
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88574 Bug ID: 88574 Summary: VA-API on RV610 crashes my system Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: user142(a)hotmail.com when I start VLC like this: export LIBVA_DRIVER_NAME=gallium vlc and then inside VLC select VA-API as hardware acceleration and then open a video, my screen goes black after a few seconds and my system becomes unresponsive and I have to force poweroff by long pressing the power button. I am using Arch Linux with the 3.18.2 Kernel and Mesa 10.4.2 My graphics card: Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 XT] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 88522] unreal effectscave demo locks up gpu
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88522 Bug ID: 88522 Summary: unreal effectscave demo locks up gpu 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: aaalmosss(a)gmail.com I tried the Effects Cave demo from here https://wiki.unrealengine.com/Linux_Demos and it doesn't render anything, just locks up the GPU, the kernel calls a softreset, then the next frame locks up again and so on and so forth, until I kill it from a text console. This is printed to dmesg each time (nothing on the console): [760734.139721] radeon 0000:01:00.0: ring 0 stalled for more than 10379msec [760734.139727] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000006cb14fc last fence id 0x0000000006cb14fb on ring 0) [760734.139734] radeon 0000:01:00.0: failed to get a new IB (-35) [760734.139736] [drm:radeon_cs_ib_fill] *ERROR* Failed to get ib ! [760734.276346] radeon 0000:01:00.0: Saved 663 dwords of commands on ring 0. [760734.276370] radeon 0000:01:00.0: GPU softreset: 0x00000009 [760734.276372] radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 [760734.276375] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 [760734.276377] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x80000003 [760734.276379] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [760734.276381] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [760734.276383] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [760734.276385] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 [760734.276388] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048006 [760734.276390] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 [760734.276392] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [760734.277882] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [760734.277936] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [760734.279096] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [760734.279098] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [760734.279100] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [760734.279102] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [760734.279104] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [760734.279107] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [760734.279109] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [760734.279111] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [760734.279113] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [760734.279116] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [760734.279147] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [760734.305227] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [760734.306448] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000). [760734.306543] radeon 0000:01:00.0: WB enabled [760734.306546] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88041e6dbc00 [760734.306548] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88041e6dbc0c [760734.307995] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900120b2118 [760734.324270] [drm] ring test on 0 succeeded in 2 usecs [760734.324281] [drm] ring test on 3 succeeded in 7 usecs [760734.501676] [drm] ring test on 5 succeeded in 2 usecs [760734.501685] [drm] UVD initialized successfully. [760744.513661] radeon 0000:01:00.0: ring 0 stalled for more than 10000msec [760744.513666] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000006cb1511 last fence id 0x0000000006cb1502 on ring 0) [760744.513672] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [760744.513677] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [760744.513678] radeon 0000:01:00.0: ib ring test failed (-35). [760744.522064] radeon 0000:01:00.0: GPU softreset: 0x00000009 [760744.522067] radeon 0000:01:00.0: GRBM_STATUS = 0xF7731828 [760744.522069] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000003 [760744.522072] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xFC000003 [760744.522074] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [760744.522076] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [760744.522078] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [760744.522080] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x400C0000 [760744.522083] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048006 [760744.522085] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 [760744.522087] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [760744.522255] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [760744.522310] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [760744.523469] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [760744.523471] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [760744.523475] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [760744.523477] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [760744.523479] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [760744.523481] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [760744.523483] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [760744.523486] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [760744.523488] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [760744.523490] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [760744.523525] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [760744.535154] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [760744.538833] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000). [760744.538926] radeon 0000:01:00.0: WB enabled [760744.538929] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88041e6dbc00 [760744.538931] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88041e6dbc0c [760744.540384] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900120b2118 [760744.556776] [drm] ring test on 0 succeeded in 2 usecs [760744.556787] [drm] ring test on 3 succeeded in 7 usecs [760744.734161] [drm] ring test on 5 succeeded in 2 usecs [760744.734170] [drm] UVD initialized successfully. [760744.734257] [drm] ib test on ring 0 succeeded in 0 usecs [760744.734340] [drm] ib test on ring 3 succeeded in 0 usecs [760744.885694] [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get create msg (-22). [760744.885701] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). [760744.885793] switching from power state: [760744.885797] ui class: none [760744.885798] internal class: boot [760744.885799] caps: [760744.885801] uvd vclk: 0 dclk: 0 [760744.885802] power level 0 sclk: 10000 mclk: 30000 vddc: 950 vddci: 950 [760744.885803] power level 1 sclk: 10000 mclk: 30000 vddc: 950 vddci: 950 [760744.885804] power level 2 sclk: 10000 mclk: 30000 vddc: 950 vddci: 950 [760744.885805] status: c b [760744.885806] switching to power state: [760744.885807] ui class: performance [760744.885808] internal class: none [760744.885808] caps: [760744.885809] uvd vclk: 0 dclk: 0 [760744.885810] power level 0 sclk: 10000 mclk: 15000 vddc: 950 vddci: 950 [760744.885811] power level 1 sclk: 60000 mclk: 100000 vddc: 1100 vddci: 1100 [760744.885812] power level 2 sclk: 86000 mclk: 110000 vddc: 1150 vddci: 1100 [760744.885813] status: r This is with AMD Barts (HD6850), kernel is 3.17.7, mesa 10.3.2 and 10.5-dev. I also tried the Realistic Rendering demo, and it works fine (with mesa 10.1 it was completely blue, but it has been fixed). -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 88263] Civilization Beyond Earth crashes on
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88263 Bug ID: 88263 Summary: Civilization Beyond Earth crashes on 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: oleid(a)mescharet.de Dear Mesa developers, as suggested in #87489 a new report. The game crashes when staring a new game or loading an existing. I can reach the menu, set up a new game and so on. As far as I can tell, llvm-svn is used for building the mesa-git package. I also tried running R600_DEBUG=llvm to make sure llvm is really used --- I'm not sure what's the default, nowadays (is it somewhere in the logs? I didn't find anything). I created an trace file of the game and enabled R600_DEBUG=vs,gs,ps As the trace file is rather huge, I put everything to the following google drive storage. You can find there also the debugging output generated by the above debug settings. https://drive.google.com/folderview?id=0BxSauDFlQdaFYTRaY3hrLXNvOVk&usp=sha… As the game crashes, I'm not certain, if the files are complete. If it is of any help, I can provide an apitrace of fglrx. It runs the game, albeit with graphic errors. Please let me know if I can provide more information. **** System: ATI Juniper PRO [Radeon HD 5750] ArchLinux AMD64 using mesa-git repository. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 87741] VA-API state tracker in radeon results in green screen.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=87741 Bug ID: 87741 Summary: VA-API state tracker in radeon results in green screen. Product: Mesa Version: 10.4 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: barz621(a)gmail.com Created attachment 111367 --> https://bugs.freedesktop.org/attachment.cgi?id=111367&action=edit dmesg As the title suggests. Exported LIBVA_DRIVER_NAME=gallium and using gst-vaapi you get a green screen while the sound plays. It seems that decoding works -UVD clocks change speed- but the video ends up green. Youtube and E19 using gst for video all have the same behavior. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 87568] WebGL can cause GPU reset
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=87568 Bug ID: 87568 Summary: WebGL can cause GPU reset Product: Mesa Version: 10.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: aaalmosss(a)gmail.com I was given this link: http://hunger.hu/webgl.html which was supposed to crash any video driver, and it really did a hiccup. Fortunately, after 1 second the kernel detected GPU lockup, and reinitialized everything just fine. As far as I can tell that javascript doesn't do anything sinister, just tries to render 200k triangles with a single glDrawElements() call. Shouldn't there be a protection against such simple overflows somewhere? -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 87071] LLVM triggered Diagnostic Handler: unsupported call to function S2KItSaltedSHA1Generator in gpg
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=87071 Bug ID: 87071 Summary: LLVM triggered Diagnostic Handler: unsupported call to function S2KItSaltedSHA1Generator in gpg Product: Mesa Version: 10.3 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: devurandom(a)gmx.net Mesa 10.3.4 / LLVM 3.5.0 / libclc 0.0.1_pre20141027 seems to be unable to compile the OpenCL function S2KItSaltedSHA1Generator from current John-The-Ripper Git [1]. The function is too long to quote here, but the signature is: inline void S2KItSaltedSHA1Generator(__global const uchar *password, int password_length, __global const uchar *salt, int count, __global uchar *key, int length) My hardware as reported by JTR is: # /usr/sbin/john -list=opencl-devices Platform #0 name: Default Platform version: OpenCL 1.1 MESA 10.3.4 Device #0 (0) name: AMD REDWOOD Device vendor: X.Org Device type: GPU (LE) Device version: OpenCL 1.1 MESA 10.3.4 Driver version: 10.3.4 Native vector widths: char 16, short 8, int 4, long 2 Preferred vector width: char 16, short 8, int 4, long 2 Global Memory: 1024.0 MB Local Memory: 32.0 KB (Local) Max memory alloc. size: 256.2 MB Max clock (MHz): 700 Max Work Group Size: 256 Parallel compute cores: 5 [1] https://github.com/magnumripper/JohnTheRipper/blob/bleeding-jumbo/src/openc… -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 87047] gputest pixmark tests fail on Barts
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=87047 Bug ID: 87047 Summary: gputest pixmark tests fail on Barts Product: Mesa Version: 10.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: aaalmosss(a)gmail.com The piano and the volplosion benchmarks don't render anything, and an incredible amount this is printed to the console: EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:157 r600_pipe_shader_create - translation from TGSI failed ! EE ../../../../../../src/gallium/drivers/r600/r600_state_common.c:758 r600_shader_select - Failed to build shader variant (type=1) -1 Mesa 10.3.2 -- 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 July 2017