[Bug 96271] TF2: GPU lockup on HD 7950 - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96271] TF2: GPU lockup on HD 7950
Date: Fri, 28 Apr 2017 08:11:22 +0000	[thread overview]
Message-ID: <bug-96271-502-IMJgyAkSeG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96271-502@http.bugs.freedesktop.org/>

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

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

--- Comment #9 from Julien Isorce <julien.isorce@gmail.com> ---
Hi Stephen, if you still have the same machine/setup maybe worth to try the
apitrace 1) that I mentioned here
https://bugs.freedesktop.org/show_bug.cgi?id=100712#c7 . I wonder if it is the
same issue.

About "dmesg_after_hard_hang.txt" / "kernel_log_during_gdm_restart.txt" all
these exact same backtraces are happening because the ring 0(GFX) is still
stuck after gpu reset. So acceleration is marked as disabled. But then mesa
clear some buffers being cached before reset and it hits WARN_ON in
radeon_ttm_bo_destroy, see
https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/radeon/radeon_object.c?h=amd-staging-4.9#n72.
I recently submitted a patch to change it to a WARN_ON_ONCE.

But the real problem is the ring 0 stalled in the first place. For me I found
that setting R600_DEBUG=nowc workarounds the problem.

Also I have not found any full dmesg log in the attachments, especially infos
generated at startup.

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

[-- Attachment #1.2: Type: text/html, Size: 2218 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