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: Sat, 05 Aug 2017 12:24:40 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1032861949=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id AF02A6E44A
for ; Sat, 5 Aug 2017 12:24:40 +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
--===============1032861949==
Content-Type: multipart/alternative; boundary="15019358801.FC5B50d.31094";
charset="UTF-8"
--15019358801.FC5B50d.31094
Date: Sat, 5 Aug 2017 12:24:40 +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 #36 from MirceaKitsune -=
--
Created attachment 133254
--> https://bugs.freedesktop.org/attachment.cgi?id=3D133254&action=3Dedit
Output of "dmesg -w"
This is perhaps the most important piece of information I managed to gather=
on
the problem thus far. If you have a technical understanding of this data,
please take a look at the log and let us know what it says!
I was able to run a SSH session on my computer from another machine. In it I
left the command "dmesg -w" running. I toggled desktop effects last night to
provoke a crash today, which happened as expected and allowed me to conduct=
the
test. This is basically what dmesg is seeing in realtime as the system is
crashing.
I can't make sense of the information, but it definitely looks descriptive.
Although the computer seemed completely frozen locally, the output continued
flowing on the other machine printing new information every few seconds. I =
had
to wait in order to catch some of the red lines in the console.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15019358801.FC5B50d.31094
Date: Sat, 5 Aug 2017 12:24:40 +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 # 36
on bug 10030=
6
from MirceaKitsune=
span>
Created attachmen=
t 133254 [details]
Output of "dmesg -w"
This is perhaps the most important piece of information I managed to gather=
on
the problem thus far. If you have a technical understanding of this data,
please take a look at the log and let us know what it says!
I was able to run a SSH session on my computer from another machine. In it I
left the command "dmesg -w" running. I toggled desktop effects la=
st night to
provoke a crash today, which happened as expected and allowed me to conduct=
the
test. This is basically what dmesg is seeing in realtime as the system is
crashing.
I can't make sense of the information, but it definitely looks descriptive.
Although the computer seemed completely frozen locally, the output continued
flowing on the other machine printing new information every few seconds. I =
had
to wait in order to catch some of the red lines in the console.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15019358801.FC5B50d.31094--
--===============1032861949==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1032861949==--