All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1
Date: Mon, 28 Mar 2016 02:20:26 +0000	[thread overview]
Message-ID: <bug-93652-502-aqalKngmTl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93652-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Sebastian Jensen <s@gonx.dk> ---
I can also confirm this bug in form of a full system freeze on an AMD 380X on
the latest Mesa revision in addition to running the latest drm-next as of 27th
March 2016.

To put it short, setting R600_DEBUG=nodcc seems to alleviate the crashes, based
on a couple of hours of testing.

For some details, I can confirm the crashes in at least Dota 2, Portal,
Counter-Strike: Global Offensive - all native applications - and under WINE,
Starcraft II and Heroes of the Storm both crash within minutes.

On the contrary, the crash never occured in other programs, like Furmark,
Battleblock Theater, as well as Awesomenauts.

I also tried recording multiple apitraces where the issue occured, but none of
the traces would actually reproduce the hang.

However, what strikes me as most odd is that the hang generally never occured
in games in WINE when using the Gallium Nine patches, while the hangs would
occur within minutes otherwise.

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

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

  parent reply	other threads:[~2016-03-28  2:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 14:42 [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1 bugzilla-daemon
2016-01-10 17:26 ` bugzilla-daemon
2016-01-11  0:41 ` bugzilla-daemon
2016-02-19 21:14 ` bugzilla-daemon
2016-03-09  6:15 ` bugzilla-daemon
2016-03-14 13:42 ` bugzilla-daemon
2016-03-28  2:20 ` bugzilla-daemon [this message]
2016-03-29 19:18 ` bugzilla-daemon
2016-04-04  9:03 ` bugzilla-daemon
2016-05-10 20:16 ` bugzilla-daemon
2016-05-27 13:12 ` bugzilla-daemon
2016-06-27 13:28 ` bugzilla-daemon
2016-08-22  3:05 ` bugzilla-daemon
2016-10-30  1:34 ` bugzilla-daemon
2016-10-31 20:40 ` bugzilla-daemon
2017-01-14 14:32 ` bugzilla-daemon
2017-01-14 23:22 ` bugzilla-daemon
2017-01-14 23:43 ` bugzilla-daemon
2017-01-16  1:01 ` bugzilla-daemon
2017-05-20 15:51 ` bugzilla-daemon
2017-05-26 19:58 ` bugzilla-daemon
2019-09-17  3:00 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-93652-502-aqalKngmTl@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.