From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111986] 5700 XT hangs entire system in games Date: Mon, 14 Oct 2019 20:17:36 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0182413565==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 14CA56E588 for ; Mon, 14 Oct 2019 20:17:38 +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 --===============0182413565== Content-Type: multipart/alternative; boundary="15710842572.83EC.20119" Content-Transfer-Encoding: 7bit --15710842572.83EC.20119 Date: Mon, 14 Oct 2019 20:17:37 +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=3D111986 --- Comment #11 from Pierre-Eric Pelloux-Prayer --- (In reply to Daniel Suarez from comment #10) > Created attachment 145736 [details] > Got by running sudo journalctl -b > dmesg.log >=20 > Thanks to the explanation by someone I believe I understand now what you > meant. I went ahead and reproduced the hang by running gfxbench and when = the > system hanged at around 3:23 I force shutdown seconds later, once I booted > in I ran "sudo journalctl -b > dmesg.log" and I am sending you the output= now You need to use "sudo journalctl -b -1 > dmesg.log" to get the logs from the previous boot (=3D the one that hanged). --=20 You are receiving this mail because: You are the assignee for the bug.= --15710842572.83EC.20119 Date: Mon, 14 Oct 2019 20:17:37 +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

Comme= nt # 11 on bug 11198= 6 from Pierre= -Eric Pelloux-Prayer 
(In reply to Daniel Suarez from comment #10)
> Created attachment 145736 [details]
> Got by running sudo journalctl -b > dmesg.log
>=20
> Thanks to the explanation by someone I believe I understand now what y=
ou
> meant. I went ahead and reproduced the hang by running gfxbench and wh=
en the
> system hanged at around 3:23 I force shutdown seconds later, once I bo=
oted
> in I ran "sudo journalctl -b > dmesg.log" and I am sendin=
g you the output now

You need to use "sudo journalctl -b -1 > dmesg.log" to get the=
 logs from the
previous boot (=3D the one that hanged).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15710842572.83EC.20119-- --===============0182413565== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0182413565==--