From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 96271] TF2: GPU lockup on HD 7950 Date: Fri, 28 Apr 2017 08:11:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0057561649==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 8121F6E738 for ; Fri, 28 Apr 2017 08:11: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 --===============0057561649== Content-Type: multipart/alternative; boundary="14933670820.Bb7b.2980"; charset="UTF-8" --14933670820.Bb7b.2980 Date: Fri, 28 Apr 2017 08:11: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=3D96271 --- Comment #9 from Julien Isorce --- 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=3D100712#c7 . I wonder if it i= s 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/radeo= n_object.c?h=3Damd-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 fou= nd that setting R600_DEBUG=3Dnowc workarounds the problem. Also I have not found any full dmesg log in the attachments, especially inf= os generated at startup. --=20 You are receiving this mail because: You are the assignee for the bug.= --14933670820.Bb7b.2980 Date: Fri, 28 Apr 2017 08:11: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

Comment= # 9 on bug 96271<= /a> from Julien Isorce 
Hi Stephen, if you still have the same machine/setup maybe wor=
th to try the
apitrace 1) that I mentioned here
https://bugs.freedesktop.org/show_b=
ug.cgi?id=3D100712#c7 . I wonder if it is the
same issue.

About "dmesg_after_hard_hang.txt" / "kernel_log_during_gdm_r=
estart.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=3Damd-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 fou=
nd
that setting R600_DEBUG=3Dnowc workarounds the problem.

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

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