From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-100306-502-5mV63dLcEX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100306-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100306
--- Comment #38 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
Created attachment 133368
--> https://bugs.freedesktop.org/attachment.cgi?id=133368&action=edit
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 minutes
before doing so, to give dmesg time to record as much information as possible.
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.
[-- Attachment #1.2: Type: text/html, Size: 2228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-07 20:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-100306-502@http.bugs.freedesktop.org/>
2017-03-22 2:16 ` [Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted bugzilla-daemon
2017-03-29 19:43 ` bugzilla-daemon
2017-04-02 15:04 ` bugzilla-daemon
2017-04-06 2:45 ` bugzilla-daemon
2017-04-06 11:51 ` bugzilla-daemon
2017-04-07 0:01 ` bugzilla-daemon
2017-04-07 0:35 ` bugzilla-daemon
2017-04-11 5:13 ` bugzilla-daemon
2017-04-14 14:01 ` bugzilla-daemon
2017-04-18 1:31 ` bugzilla-daemon
2017-04-20 13:23 ` bugzilla-daemon
2017-05-09 22:17 ` bugzilla-daemon
2017-05-19 12:58 ` bugzilla-daemon
2017-05-19 13:10 ` bugzilla-daemon
2017-05-19 13:37 ` bugzilla-daemon
2017-05-21 11:30 ` bugzilla-daemon
2017-05-23 20:18 ` bugzilla-daemon
2017-05-23 21:54 ` bugzilla-daemon
2017-05-29 20:42 ` bugzilla-daemon
2017-06-07 21:04 ` bugzilla-daemon
2017-06-08 23:44 ` bugzilla-daemon
2017-06-18 18:59 ` bugzilla-daemon
2017-07-05 13:14 ` bugzilla-daemon
2017-07-05 18:21 ` bugzilla-daemon
2017-08-02 13:31 ` bugzilla-daemon
2017-08-03 13:18 ` bugzilla-daemon
2017-08-04 12:32 ` bugzilla-daemon
2017-08-05 12:24 ` bugzilla-daemon
2017-08-05 13:31 ` bugzilla-daemon
2017-08-07 20:52 ` bugzilla-daemon [this message]
2017-08-07 21:30 ` bugzilla-daemon
2017-08-07 21:31 ` bugzilla-daemon
2017-08-07 21:35 ` bugzilla-daemon
2017-08-31 18:17 ` bugzilla-daemon
2017-08-31 18:38 ` bugzilla-daemon
2017-11-12 15:04 ` bugzilla-daemon
2019-09-25 17:58 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100306-502-5mV63dLcEX@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).