From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 79980] Random radeonsi crashes Date: Wed, 29 Oct 2014 16:30:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0445030389==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 726CB6E78C for ; Wed, 29 Oct 2014 09:30:29 -0700 (PDT) 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 --===============0445030389== Content-Type: multipart/alternative; boundary="1414600229.3eA215.14534"; charset="UTF-8" --1414600229.3eA215.14534 Date: Wed, 29 Oct 2014 16:30:29 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D79980 --- Comment #194 from Marti Raudsepp --- (In reply to Alex Deucher from comment #193) > Unfortunately, this bug has become a dumping ground for any kind of > stability issue with radeonsi so I'm not really sure how useful it is > anymore. I suspect there are actually multiple issues that are now all > mixed up. What's the way forward? Shouldn't it be up to the developers to try and make sense of the reports and split up the bug entry appropriately? Should there be one report per affected user, or is there a better way to g= roup them together? Christian K=C3=B6nig from comment #175 made one suggestion, is that what we= should be doing? > In general you can split the issues into two categories one is with VM > faults in the logs and the other ones are without. --=20 You are receiving this mail because: You are the assignee for the bug. --1414600229.3eA215.14534 Date: Wed, 29 Oct 2014 16:30:29 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comme= nt # 194 on bug 79980<= /a> from = Marti Raudsepp 
(In reply to Alex Deucher from comment #193)
> Unfortunately, this bug has become a dumping gro=
und for any kind of
> stability issue with radeonsi so I'm not really sure how useful it is
> anymore.  I suspect there are actually multiple issues that are now all
> mixed up.

What's the way forward? Shouldn't it be up to the developers to try and make
sense of the reports and split up the bug entry appropriately?

Should there be one report per affected user, or is there a better way to g=
roup
them together?

Christian K=C3=B6nig from comment =
#175 made one suggestion, is that what we should
be doing?
> In general you can split the issues into two cat=
egories one is with VM
> faults in the logs and the other ones are without.

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