From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100712] ring 0 stalled after bytes_moved_threshold reached - CAPVERDE/HD7770 - TAHITI/W9000 Date: Thu, 20 Apr 2017 15:23:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1268182892==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 871A46E5F9 for ; Thu, 20 Apr 2017 15:23:22 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1268182892== Content-Type: multipart/alternative; boundary="14927018020.94fCEc.28681"; charset="UTF-8" --14927018020.94fCEc.28681 Date: Thu, 20 Apr 2017 15:23:22 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D100712 --- Comment #7 from Julien Isorce --- I made 2 apitrace using Zach's test mentioned here https://bugs.freedesktop.org/show_bug.cgi?id=3D100465#c24 . This test is al= so good to reproduce this ring 0 stalled issue. 1: apitrace ideal for vram size 2048 (ex: HD7770) https://drive.google.com/file/d/0Bzat_iFKrgCWYzBlZFFLQjgyRU0/view?usp=3Dsha= ring 2: apitrace ideal for vram size 6144 (ex: W9000) https://drive.google.com/file/d/0Bzat_iFKrgCWczgzM2FzaVFTUXc/view?usp=3Dsha= ring DISPLAY=3D:0 apitrace replay thrash.trace Also I have attached the log (dmesg_W9000_with_custom_fence_debug.log) I get with my dev branch here https://github.com/CapOM/linux/commits/amd-staging-4.9_add_debug_fences whe= re I added traces to debug ring N stalled issues. It prints the backtrace from w= here it waits for the fence and it also prints the backtrace from where it has emited that fence. Also note that setting R600_DEBUG=3Dnowc avoids this ring N stalled (so the endless fence is signaled). --=20 You are receiving this mail because: You are the assignee for the bug.= --14927018020.94fCEc.28681 Date: Thu, 20 Apr 2017 15:23:22 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 7 on bug 10071= 2 from Julien Isorce 
I made 2 apitrace using Zach's test mentioned here
https://bugs.freedesktop.org/show_=
bug.cgi?id=3D100465#c24 . This test is also
good to reproduce this ring 0 stalled issue.

1: apitrace ideal for vram size 2048 (ex: HD7770)
https://drive.google.com/file/d/0Bzat_iFKrgCWYzBlZFFLQjgyR=
U0/view?usp=3Dsharing

2: apitrace ideal for vram size 6144 (ex: W9000)
https://drive.google.com/file/d/0Bzat_iFKrgCWczgzM2FzaVFTU=
Xc/view?usp=3Dsharing

DISPLAY=3D:0 apitrace replay thrash.trace

Also I have attached the log (dmesg_W9000_with_custom_fence_debug.log) I get
with my dev branch here
https://github.com/CapOM/linux/commits/amd-staging-4.9_add_debug_f=
ences where I
added traces to debug ring N stalled issues. It prints the backtrace from w=
here
it waits for the fence and it also prints the backtrace from where it has
emited that fence.

Also note that setting R600_DEBUG=3Dnowc avoids this ring N stalled (so the
endless fence is signaled).

You are receiving this mail because:
  • You are the assignee for the bug.
= --14927018020.94fCEc.28681-- --===============1268182892== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1268182892==--