From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted Date: Mon, 07 Aug 2017 20:52:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0318036839==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3B5C089F73 for ; Mon, 7 Aug 2017 20:52:41 +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 --===============0318036839== Content-Type: multipart/alternative; boundary="15021391610.eACedcDd.12158"; charset="UTF-8" --15021391610.eACedcDd.12158 Date: Mon, 7 Aug 2017 20:52:41 +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=3D100306 --- Comment #38 from MirceaKitsune -= -- Created attachment 133368 --> https://bugs.freedesktop.org/attachment.cgi?id=3D133368&action=3Dedit Output of "dmesg -w" (full) Full output of "dmesg -w", recorded by running "dmesg -w > filename.txt". T= he previous one was incomplete as it was subject to console line limitations, cutting off the moment when the crash actually occurs. I left the command running in a different runlevel; This time the crash didn't shut down the monitor after switching to it (Control + Alt + F1) so I was able to cleanly shut down dmesg then issue a normal reboot. I waited there for about 5 minu= tes before doing so, to give dmesg time to record as much information as possib= le. The crash appears to start at the following lines: [112873.658950] radeon 0000:03:00.0: ring 4 stalled for more than 10024msec [112873.658953] radeon 0000:03:00.0: GPU lockup (current fence id 0x000000000072f6bd last fence id 0x000000000072f6c1 on ring 4) --=20 You are receiving this mail because: You are the assignee for the bug.= --15021391610.eACedcDd.12158 Date: Mon, 7 Aug 2017 20:52:41 +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 # 38 on bug 10030= 6 from MirceaKitsune 
Created at=
tachment 133368 [details]
Output of "dmesg -w" (full)

Full output of "dmesg -w", recorded by running "dmesg -w >=
; filename.txt". The
previous one was incomplete as it was subject to console line limitations,
cutting off the moment when the crash actually occurs. I left the command
running in a different runlevel; This time the crash didn't shut down the
monitor after switching to it (Control + Alt + F1) so I was able to cleanly
shut down dmesg then issue a normal reboot. I waited there for about 5 minu=
tes
before doing so, to give dmesg time to record as much information as possib=
le.
The crash appears to start at the following lines:

[112873.658950] radeon 0000:03:00.0: ring 4 stalled for more than 10024msec
[112873.658953] radeon 0000:03:00.0: GPU lockup (current fence id
0x000000000072f6bd last fence id 0x000000000072f6c1 on ring 4)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15021391610.eACedcDd.12158-- --===============0318036839== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0318036839==--