From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups
Date: Thu, 22 Feb 2018 00:06:11 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0306699500=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id B8EB76EADE
for ; Thu, 22 Feb 2018 00:06:11 +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
--===============0306699500==
Content-Type: multipart/alternative; boundary="15192579711.2F9ddCa.20189"
Content-Transfer-Encoding: 7bit
--15192579711.2F9ddCa.20189
Date: Thu, 22 Feb 2018 00:06:11 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D101672
MirceaKitsune changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |high
OS|All |Linux (All)
Hardware|Other |x86-64 (AMD64)
Version|17.1 |git
--- Comment #22 from MirceaKitsune -=
--
Wasn't sure whether to bump this same bug report, as the original issue has
clearly been fixed during nearly an year of countless Kernel + Mesa + driver
updates. Unfortunately I now experience a new issue acting just like what I
described here at the time: When certain 3D engines are running, there is a
chance that after a few minutes the machine instantly freezes and becomes f=
ully
unusable until powered off and back on. I don't know when the new crash was
implemented since I haven't played a lot of 3D games recently, but I'd assu=
me
somewhere within the last few months.
I now have Kernel 4.15.3 and Mesa 18.0.0. Again my video card is a Radeon R7
370 from Gigabyte (RadeonSI, GCN 1.0, AMD Pitcairn Islands). I'm running the
openSUSE Tumbleweed x64 rolling release distribution.
Can someone please explain a way to debug those instant system freezes as
they're added to the system components? I can't get an output at the time of
the crash as the entire machine stops working and becomes bricked until
restarted (likely including SSH), but maybe I can make it log info that I c=
an
retrieve after I reboot? Any useful info will help, just please nothing
dangerous that might permanently break my OS.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15192579711.2F9ddCa.20189
Date: Thu, 22 Feb 2018 00:06:11 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
MirceaKitsune
changed
bug 10167=
2
What |
Removed |
Added |
Priority |
medium
|
high
|
OS |
All
|
Linux (All)
|
Hardware |
Other
|
x86-64 (AMD64)
|
Version |
17.1
|
git
|
Comme=
nt # 22
on bug 10167=
2
from MirceaKitsune=
span>
Wasn't sure whether to bump this same bug report, as the origi=
nal issue has
clearly been fixed during nearly an year of countless Kernel + Mesa + driver
updates. Unfortunately I now experience a new issue acting just like what I
described here at the time: When certain 3D engines are running, there is a
chance that after a few minutes the machine instantly freezes and becomes f=
ully
unusable until powered off and back on. I don't know when the new crash was
implemented since I haven't played a lot of 3D games recently, but I'd assu=
me
somewhere within the last few months.
I now have Kernel 4.15.3 and Mesa 18.0.0. Again my video card is a Radeon R7
370 from Gigabyte (RadeonSI, GCN 1.0, AMD Pitcairn Islands). I'm running the
openSUSE Tumbleweed x64 rolling release distribution.
Can someone please explain a way to debug those instant system freezes as
they're added to the system components? I can't get an output at the time of
the crash as the entire machine stops working and becomes bricked until
restarted (likely including SSH), but maybe I can make it log info that I c=
an
retrieve after I reboot? Any useful info will help, just please nothing
dangerous that might permanently break my OS.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15192579711.2F9ddCa.20189--
--===============0306699500==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0306699500==--