From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing Date: Wed, 20 Jan 2016 17:12:34 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2007061804==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 051AD6E061 for ; Wed, 20 Jan 2016 09:12:35 -0800 (PST) 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 --===============2007061804== Content-Type: multipart/alternative; boundary="14533099540.eB80.4680"; charset="UTF-8" --14533099540.eB80.4680 Date: Wed, 20 Jan 2016 17:12:34 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=91880 --- Comment #64 from Alex Deucher --- (In reply to Julian from comment #63) > At first I thought it was an issue with the writeback feature that caches > certain register values because it also caches an rptr value that is used in > the driver's gpu_lockup_check and is, to my knowledge, never actually > written to. More likely it never gets written because the GPU has hung due to something else. > > Buuut using radeon.no_wb=1 doesn't help. So if I've found a bug it is not > the culprit of the lockups. The no_wb option isn't really applicable on newer chips and most likely won't work. Newer hw does not support the necessary features to not support wb. It's mainly a leftover from the early radeons. -- You are receiving this mail because: You are the assignee for the bug. --14533099540.eB80.4680 Date: Wed, 20 Jan 2016 17:12:34 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 64 on bug 91880 from 
(In reply to Julian from comment #63)
> At first I thought it was an issue with the writeback feature that caches
> certain register values because it also caches an rptr value that is used in
> the driver's gpu_lockup_check and is, to my knowledge, never actually
> written to.

More likely it never gets written because the GPU has hung due to something
else.

> 
> Buuut using radeon.no_wb=1 doesn't help. So if I've found a bug it is not
> the culprit of the lockups.

The no_wb option isn't really applicable on newer chips and most likely won't
work.  Newer hw does not support the necessary features to not support wb. 
It's mainly a leftover from the early radeons.

You are receiving this mail because:
  • You are the assignee for the bug.
--14533099540.eB80.4680-- --===============2007061804== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============2007061804==--