dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 104804] A gpu lockup occurred on E6760 while using qtcreator
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104804 Bug ID: 104804 Summary: A gpu lockup occurred on E6760 while using qtcreator Product: Mesa Version: 11.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: appenper(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136980 --> https://bugs.freedesktop.org/attachment.cgi?id=136980&action=edit lspci output [ 695.093933] radeon 0000:01:00.0: ring 0 stalled for more than 10150msec [ 695.100523] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000befe last fence id 0x000000000000bf3e on ring 0) [ 695.100673] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100676] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100678] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100681] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100691] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100695] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100701] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100707] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100710] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100712] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100715] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100721] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100723] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100727] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100730] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100734] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100737] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100741] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100744] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100747] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100749] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100753] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100756] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100759] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.100762] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.100766] radeon 0000:01:00.0: failed to get a new IB (-35) [ 695.119228] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 695.968594] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib ! [ 696.004823] radeon 0000:01:00.0: Saved 2034 dwords of commands on ring 0. [ 696.004856] radeon 0000:01:00.0: GPU softreset: 0x00000008 [ 696.004861] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003828 [ 696.004866] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 696.004871] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 696.004876] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 696.004880] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 696.004885] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 696.004889] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00004100 [ 696.004894] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00020182 [ 696.004899] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80028243 [ 696.004903] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 696.054035] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00004001 [ 696.054093] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 696.055256] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 696.055260] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 696.055265] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 696.055269] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 696.055274] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 696.055278] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 696.055282] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 696.055286] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 696.055290] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 696.055295] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 696.055332] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 696.067624] [drm] PCIE gen 2 link speeds already enabled [ 696.129090] [drm] PCIE GART of 1024M enabled (table at 0x0000000000162000). [ 696.129270] radeon 0000:01:00.0: WB enabled [ 696.129277] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffffffc4eaa7bc00 [ 696.129283] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffffffc4eaa7bc0c [ 696.151289] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffff8018332118 [ 696.168311] [drm] ring test on 0 succeeded in 2 usecs [ 696.168328] [drm] ring test on 3 succeeded in 7 usecs [ 696.345018] [drm] ring test on 5 succeeded in 2 usecs [ 696.345031] [drm] UVD initialized successfully. [ 696.379172] [drm] ib test on ring 0 succeeded in 0 usecs [ 696.379236] [drm] ib test on ring 3 succeeded in 0 usecs [ 696.530311] [drm] ib test on ring 5 succeeded Sometimes when using qtcreator for a while a gpu lockup error occurred, on this basis, we guess that this gpulock error caused by qtcreator's welcome plugin, so we use a script to test the qtcreator's Welcome plugin as follows: while true do for i in `seq 100` do qtcreator -test Welcome & done wait done The time of the error is random, and sometimes appear once a half hour, sometimes half a day, that is , not a fixed time. Currently we have tried a lot of ways to deal with cpu and gpu out of sync. E.g: dpm=0/pm_method=profile. Pipeline timeout. Use GTT for stream resources. OS Details: kernel 4.4 with 4.9drm. xorg-server 1.18.3 xf86-video-ati 1:7.7 libdrm 2.4.65 mesa 11.2.0 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 104790] When using OpenGL 4.x some applications crash
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104790 Bug ID: 104790 Summary: When using OpenGL 4.x some applications crash 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: lei.pero(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136962 --> https://bugs.freedesktop.org/attachment.cgi?id=136962&action=edit screenshot of artifact with compatibility profile While enabling GL 4.x core profiles on Radeon HD 6770 (Juniper), applications such as genymotion and most wine games crash without any error. WHen using 4.xCOMPAT profile instead of core, they do not crash, however, some games in wine have serious graphical corruption (such as in atachment). This is with mesa-git (with all commits to this date) and earlier versions, just to report it so it can be solved before enabling core profiles by default. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 104770] GL_ARB_compute_shader advertised but none-functional / piglit tests failing on CAYMAN.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104770 Bug ID: 104770 Summary: GL_ARB_compute_shader advertised but none-functional / piglit tests failing on CAYMAN. 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: v10lator(a)myway.de QA Contact: dri-devel(a)lists.freedesktop.org I tried Alien: Isolation but the issues which should be solved by GL_ARB_compute_shader are still present. Also the following piglit tests are failing when running "./piglit run tests/all -t compute_shader results/compute_shader": spec@arb_compute_shader@execution@multiple-texture-reading spec@arb_compute_shader@indirect-compute spec@arb_compute_shader@zero-dispatch-size -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 104744] [r600] Total War: Warhammer black textures and flickering.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104744 Bug ID: 104744 Summary: [r600] Total War: Warhammer black textures and flickering. 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: freedesktop(a)lanig.email QA Contact: dri-devel(a)lists.freedesktop.org A friend of mine installed Ubuntu to play the non-cross-platform game Total War: Warhammer with me. Unfortunately he had issues with black empty spaces where textures should be. But it worked for me without any issues with RadeonSI(RX 480). Then I recommended adding the Padoka PPA and to update the system. That was a big fail. As a reward he also got heavy flickering additionally. He also mentioned weird colors where the black missing textures were before with activated graphics options. So I would like to report mainly that the current version seems to be worse than the one delivered with Ubuntu, at least for this particular game. He can't really provide further help and I can't access the system in any way. But I hope that an r600 developer who owns such GPU could hopefully have a look in the issue. His System: Ubuntu 17.10 Intel Core i5 2500 AMD Radeon HD 6950 2GiB 16 GiB RAM Thanks anyway to whoever reads this - these GPUs might be old but such occurrences don't make a good impression at all to people who are trying out Linux. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 104592] [r600g] Rejected CS when using dolphin's GPU texture decoder
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104592 Bug ID: 104592 Summary: [r600g] Rejected CS when using dolphin's GPU texture decoder 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: megwattt(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136672 --> https://bugs.freedesktop.org/attachment.cgi?id=136672&action=edit Apitrace of dolphin Dolphin emulator's GPU texture decoder is now supported, as it requires compute shaders. It however misrender and the line "The kernel rejected CS, see dmesg for more information" is repetitively printed. I have the folowwing lines repeated in dmesg: "[ 4885.617750] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [ 4885.624044] radeon 0000:01:00.0: evergreen_cs_track_check:982 mask 0x000000FF | 0x000000FF no cb for 1 [ 4885.624047] radeon 0000:01:00.0: evergreen_packet3_check:1908 invalid cmd stream" I have attached an apitrace of dolphin. The trace renders fine on Skylake. It seems that the first rejected CS is at frame 0, call 2731. (glDrawRangeElementsBaseVertex()) Tested on HD 5770. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 104591] [r600g] Compute demos and pigilt tests broken on REDWOOD, works fine on JUNIPER
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104591 Bug ID: 104591 Summary: [r600g] Compute demos and pigilt tests broken on REDWOOD, works fine on JUNIPER 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: megwattt(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136671 --> https://bugs.freedesktop.org/attachment.cgi?id=136671&action=edit "pigilt run -t compute" left:REDWOOD right:JUNIPER Some games and demos which use compute shaders misrender on my HD 5670 (REDWOOD), but works fine on my HD 5770 (JUNIPER). Tested with various Ogre demos and Supertuxkart. When running pigilt's compute tests ("pigilt run -t compute") 19 tests doesn't pass on REDWOOD but pass on JUNIPER. The comparison between those 2 pigilt runs is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 103911] r600/eg: egd_tables.h missing from 17.2.x tarballs
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103911 Bug ID: 103911 Summary: r600/eg: egd_tables.h missing from 17.2.x tarballs Product: Mesa Version: 17.2 Hardware: Other OS: OpenBSD Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: jsg(a)openbsd.org QA Contact: dri-devel(a)lists.freedesktop.org The src/gallium/drivers/r600/egd_tables.h file is missing from the Mesa 17.2.x tarballs. This has needlessly introduced a build time requirement of python. I can not easily test the dist targets myself as they break in srg/egl when wayland is not present. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 103900] [SUMO][TURKS] Launching War Thunder make GPU stuck, and then system is hard lockup
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103900 Bug ID: 103900 Summary: [SUMO][TURKS] Launching War Thunder make GPU stuck, and then system is hard lockup Product: Mesa Version: 17.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: russianneuromancer(a)ya.ru QA Contact: dri-devel(a)lists.freedesktop.org Hello! Launching War Thunder make GPU stuck, and then system is hard lockup. This issue is starting to happen after upgrade from Mesa 17.2.2 with libdrm 2.4.83 to 17.3.0rc4 with libdrm 2.4.85 (from Padoka Stable PPA https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa ) on Kubuntu 17.10 x86_64. As soon as I rollback to Mesa 17.2.2 and libdrm 2.4.83, GPU lockup is no longer reproducible, but then there is another issue: bug 100387 Issue is reproducible on both of iGPU and dGPU. Please look into attached log. Hardware: Acer Aspire 7560G, AMD A8-3500M AMD Radeon HD 6620G iGPU, AMD Radeon HD 6650M dGPU. Software: Kubuntu 17.10 x86_64, Linux 4.14.1. radeon DDX and modesetting DDX was tested, no difference. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 103726] GPU crashes freezing the system and weird rendering issues on CAYMAN
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103726 Bug ID: 103726 Summary: GPU crashes freezing the system and weird rendering issues on CAYMAN 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: v10lator(a)myway.de QA Contact: dri-devel(a)lists.freedesktop.org I'm not really sure how to describe this bug. It is so random, sometimes I'm not sure if exists as nothing happens in weeks, then it happenes all 10 minutes. I'm hunting this bug for so long, can't tell if a year or two or even more. Some (if not all?) games are triggering weird behavior on a Radeon HD 6950. What happens is the screen changing to green with some check pattern (sorry for having no picture but screenshoting is impossible and I never had a camera at hand). Before the driver was able to do a GPU reset (now you get how old this bug is) it was staying there but with modern kernels the drivers seems to try a reset (monitor flickering for a moment) after some time and then all I get is a black screen (not no-signal, a black image) at that time the only way to recover the PC is by pressing the reset button. Now since a few days I'm playing Dead Island and it seems to be a good trigger for the bug ("good" means the game seems to trigger it in between a few seconds and 6 hours of gameplay. Make sure to have a lot of freetime if you try to recreate) so I decided to try to hunt it again. For that I started the game with R600_DEBUG=nosb,nohyperz and played for around 3 hours before I got bored. Then I switched back to the desktop and noticed that everything got broken: Flickering and/or invisible windows, hanging menue, the complete desktop hanging and so on (I tried to take a video but it's corrupted: [ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: moov atom not found) ). When the desktio corruted there's nothing in the logs except kernel: radeon_dp_aux_transfer_native: 32 callbacks suppressed but that should be harmless, shouldn't it? When the green screen comes there#s also nothing in the logs, but that's most likely because the system froze before it could flush it to disc as the logs are incomlete im that case. This bug might or might not be the same as https://bugs.freedesktop.org/show_bug.cgi?id=92555 - I really can't tell but if it's the same: Could it be a regresion introduced by splitting r600 and radeonsi? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 103654] GL_POINT_SMOOTH not handled
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103654 Bug ID: 103654 Summary: GL_POINT_SMOOTH not handled 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: webgeek1234(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 135359 --> https://bugs.freedesktop.org/attachment.cgi?id=135359&action=edit Glut test program for GL_POINT_SMOOTH I'm working on a legacy system with an RV730, reports as a Radeon E4690, on RHEL 6.9. The software I'm supporting tries to draw points on a globe (using the NASA worldwind map software). On fglrx, these render correctly; on mesa, they render as squares. Close as I can tell, r600 is not handling GL_POINT_SMOOTH correctly. I have tested on Fedora all the way to rawhide, which just built mesa 17.3 rc3 and the problem still persists. Attached is a simple glut test I threw together and tested against swrast, r600, and nva5. Swrast and nva5 render a circle, r600 renders a square. -- You are receiving this mail because: You are the assignee for the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019