All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93649] [radeonsi] Graphics lockup while playing tf2
Date: Mon, 24 Oct 2016 19:54:35 +0000	[thread overview]
Message-ID: <bug-93649-502-HGE3SBzbX5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93649-502@http.bugs.freedesktop.org/>


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

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

--- Comment #49 from Marek Olšák <maraeo@gmail.com> ---
(In reply to Marek Olšák from comment #48)
> Does this fix the hangs?
> https://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=d4d9ec55c589156df4edc227a86b4a8c41048d58
> 
> It changes the HTILE (HyperZ) allocation function to
> r600_aligned_buffer_create. Without that, the hardware can hang on big GPUs
> (Tahiti/Pitcairn/Hawaii/Tonga/etc), but not APUs or small GPUs. The hang
> happens when TTM decides to move HTILE to a different location with an
> unaligned physical address (which is pretty random). The hardware tries to
> access the unaligned address and boom.

Actually, I think that commit only affects Hawaii and Fiji. Other GPUs might be
unaffected, which means the Tahiti hangs are due to a different bug.

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

[-- Attachment #1.2: Type: text/html, Size: 1874 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-10-24 19:54 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10  5:11 [Bug 93649] [radeonsi] Graphics lockup while playing tf2 bugzilla-daemon
2016-01-10  5:13 ` bugzilla-daemon
2016-01-10  7:09 ` bugzilla-daemon
2016-01-19 18:20 ` bugzilla-daemon
2016-01-24  5:30 ` bugzilla-daemon
2016-01-26  5:03 ` bugzilla-daemon
2016-01-26  5:18 ` bugzilla-daemon
2016-01-26 10:09 ` bugzilla-daemon
2016-01-26 16:07 ` bugzilla-daemon
2016-01-26 16:12 ` bugzilla-daemon
2016-02-07 20:17 ` bugzilla-daemon
2016-02-07 21:53 ` bugzilla-daemon
2016-03-18  0:59 ` bugzilla-daemon
2016-05-16 15:11 ` bugzilla-daemon
2016-07-23 14:29 ` bugzilla-daemon
2016-07-23 14:34 ` bugzilla-daemon
2016-07-23 14:50 ` bugzilla-daemon
2016-07-23 15:45 ` bugzilla-daemon
2016-07-23 16:32 ` bugzilla-daemon
2016-08-07 14:13 ` bugzilla-daemon
2016-08-10 22:00 ` bugzilla-daemon
2016-08-11  4:08 ` bugzilla-daemon
2016-08-11 17:12 ` bugzilla-daemon
2016-08-11 21:30 ` bugzilla-daemon
2016-08-31  6:32 ` bugzilla-daemon
2016-08-31  6:38 ` bugzilla-daemon
2016-08-31 13:27 ` bugzilla-daemon
2016-09-02 16:15 ` bugzilla-daemon
2016-09-02 16:17 ` bugzilla-daemon
2016-09-03 21:19 ` bugzilla-daemon
2016-09-03 21:23 ` bugzilla-daemon
2016-09-04 11:34 ` bugzilla-daemon
2016-09-04 14:01 ` bugzilla-daemon
2016-09-04 14:13 ` bugzilla-daemon
2016-09-04 14:15 ` bugzilla-daemon
2016-09-04 15:23 ` bugzilla-daemon
2016-09-04 17:13 ` bugzilla-daemon
2016-09-10 14:38 ` bugzilla-daemon
2016-09-14 14:08 ` bugzilla-daemon
2016-09-24 19:53 ` bugzilla-daemon
2016-10-02  4:52 ` bugzilla-daemon
2016-10-02 17:14 ` bugzilla-daemon
2016-10-14  5:35 ` bugzilla-daemon
2016-10-20  4:48 ` bugzilla-daemon
2016-10-21 19:01 ` bugzilla-daemon
2016-10-21 22:47 ` bugzilla-daemon
2016-10-22  1:34 ` bugzilla-daemon
2016-10-22 10:48 ` bugzilla-daemon
2016-10-24 17:56 ` bugzilla-daemon
2016-10-24 19:54 ` bugzilla-daemon [this message]
2016-10-24 20:10 ` bugzilla-daemon
2016-10-24 20:35 ` bugzilla-daemon
2016-10-24 20:52 ` bugzilla-daemon
2016-10-25  2:11 ` bugzilla-daemon
2016-10-25  4:45 ` bugzilla-daemon
2016-10-25 10:10 ` bugzilla-daemon
2016-10-25 11:26 ` bugzilla-daemon
2016-10-25 16:38 ` bugzilla-daemon
2016-11-02 20:18 ` bugzilla-daemon
2016-11-02 22:37 ` bugzilla-daemon
2016-11-14 19:06 ` bugzilla-daemon
2016-11-15 20:20 ` bugzilla-daemon
2016-11-23  3:34 ` bugzilla-daemon
2016-11-25  3:02 ` bugzilla-daemon
2016-12-08 18:40 ` bugzilla-daemon
2016-12-08 21:33 ` bugzilla-daemon
2016-12-09  0:24 ` bugzilla-daemon
2016-12-09  0:51 ` bugzilla-daemon
2016-12-09  2:22 ` bugzilla-daemon
2016-12-09  2:31 ` bugzilla-daemon
2016-12-09  3:05 ` bugzilla-daemon
2016-12-09  3:09 ` bugzilla-daemon
2016-12-09  3:23 ` bugzilla-daemon
2016-12-09 20:13 ` bugzilla-daemon
2016-12-09 22:12 ` bugzilla-daemon
2016-12-09 22:25 ` bugzilla-daemon
2016-12-11  5:47 ` bugzilla-daemon
2016-12-20 20:24 ` bugzilla-daemon
2016-12-22 17:48 ` bugzilla-daemon
2018-04-03  4:08 ` bugzilla-daemon
2018-11-26 23:37 ` bugzilla-daemon
2018-11-27 19:34 ` 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-93649-502-HGE3SBzbX5@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.