[Bug 100712] ring 0 stalled after bytes_moved_threshold reached - CAPVERDE/HD7770 - TAHITI/W9000 - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-100712-502-FBPDuUdqbi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100712-502@http.bugs.freedesktop.org/>

[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100712

--- Comment #7 from Julien Isorce <julien.isorce@gmail.com> ---
I made 2 apitrace using Zach's test mentioned here
https://bugs.freedesktop.org/show_bug.cgi?id=100465#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_iFKrgCWYzBlZFFLQjgyRU0/view?usp=sharing

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

DISPLAY=: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 where I
added traces to debug ring N stalled issues. It prints the backtrace from where
it waits for the fence and it also prints the backtrace from where it has
emited that fence.

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2449 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel