From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1 Date: Mon, 14 Mar 2016 13:42:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1557438910==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2022589F9F for ; Mon, 14 Mar 2016 13:42:42 +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 --===============1557438910== Content-Type: multipart/alternative; boundary="14579629621.71296eed.14902"; charset="UTF-8" --14579629621.71296eed.14902 Date: Mon, 14 Mar 2016 13:42:42 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=93652 --- Comment #5 from Nicolai Hähnle --- Thanks for the reports. Those backtraces are typical consequences of a GPU hang and are unfortunately not helpful for isolating the root cause. One thing you could try is starting Steam with R600_DEBUG=nodcc from a terminal window. Also, if it doesn't take too long for the hang to occur (Wolfgang mentions a few minutes), you could try recording an apitrace, and see whether you also get a lockup when you replay the trace. Such a trace would be very helpful. -- You are receiving this mail because: You are the assignee for the bug. --14579629621.71296eed.14902 Date: Mon, 14 Mar 2016 13:42:42 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 5 on bug 93652 from
Thanks for the reports.

Those backtraces are typical consequences of a GPU hang and are unfortunately
not helpful for isolating the root cause.

One thing you could try is starting Steam with R600_DEBUG=nodcc from a terminal
window.

Also, if it doesn't take too long for the hang to occur (Wolfgang mentions a
few minutes), you could try recording an apitrace, and see whether you also get
a lockup when you replay the trace. Such a trace would be very helpful.


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